"Shachar Shemesh" <[EMAIL PROTECTED]> wrote:
> I'm not sure where, exactly. Things misbehave (sometimes) with this DLL
> present. You get Unicode data sent to ANSI functions and other strange
> stuff.
>
> The thing about this DLL is that it is very easy to implement in Wine
> (so things will n
Dmitry Timoshkov wrote:
"Shachar Shemesh" <[EMAIL PROTECTED]> wrote:
I'm having trouble with my unicows.dll implementation. I can trace this
problem down to forwarding entries not working, but I can't understand why.
Why do you need to add unicows.dll to Wine? That dll is not supposed
to
"Shachar Shemesh" <[EMAIL PROTECTED]> wrote:
> I'm having trouble with my unicows.dll implementation. I can trace this
> problem down to forwarding entries not working, but I can't understand why.
Why do you need to add unicows.dll to Wine? That dll is not supposed
to be a part of Windows, it's j
One more point. You can download the Windows program used to check this
(source+exec) from http://shemesh.biz/wine.
Shachar Shemesh wrote:
The second had to do with the forwarding call. I generated (using a
small perl script) the spec file for the DLL. It forwards all Unicode
calls to the releva
Hi list,
I'm having trouble with my unicows.dll implementation. I can trace this
problem down to forwarding entries not working, but I can't understand why.
I am attaching the diffs for my current unicows patch (not working
though it is). I'm trying to run it with a program I wrote. This program
i
Hi list,
I'm having trouble with my unicows.dll implementation. I can trace this
problem down to forwarding entries not working, but I can't understand why.
I am attaching the diffs for my current unicows patch (not working
though it is). I'm trying to run it with a program I wrote. This progra
