Lionel Ulmer [EMAIL PROTECTED] writes:
So now we have two choices: either say 'well, this is a broken application,
it does not run at all on modern Windows OSes' or add some special case when
we set Wine's version to be 'win95' or 'win98' (a bit like we already do on
instruction emulation
On Mon, Jun 14, 2004 at 04:30:28PM -0700, Alexandre Julliard wrote:
It may be that when the module handle is NULL Win95 falls back to a
thread-local hook, or does some other strange magic; NT refuses to set
a system-wide hook with a NULL module, so I'd expect your app to fail
on NT (except if
Lionel Ulmer [EMAIL PROTECTED] writes:
I have actually no idea what exactly is what Windows is doing there, but
this attached patch seems to do the trick. I have no idea if it's correct
though (as I do not know if what GetModuleHandle returns is really the same
thing as what SetWindowsHookEx
On Mon, Jun 14, 2004 at 12:58:55PM -0700, Alexandre Julliard wrote:
This doesn't look right, it doesn't make sense to create a system-wide
hook without an instance, since in that case there is no way to call
the function in other processes. This requires more investigation to
find out exactly
Lionel Ulmer [EMAIL PROTECTED] writes:
Anyway, what I know is that the application explicitely puts the NULL
parameter, so it's not a bug upstream. So either it's something that worked
on Windows95 and not anymore (as the application is quite old) or a problem
in Wine.
I will try to run
Lionel Ulmer wrote:
I have no idea if it's correct
though (as I do not know if what GetModuleHandle returns is really the same
thing as what SetWindowsHookEx expects as an HINSTANCE input).
Yes, it is. It's just used to grab the procedure address to call when
the hook is activated.
Index:
