>OK, I had definitely misinterpreted what the wParam and lParam
parameters
>in the message meant. I had assumed that the original stack
parameters
>going through the DDI interface had been either protected or copied
into
>protected memory, and that wParam and/or lParam was a pointer to
this
>protected memory.
I tried (long hours, sleepless nights, etc.) but couldn't really get
my head
round 32<-->16 bit thunking, and I couldn't find anyone who had done
something similar (the knowledge must have been to dusty even back
then).
>Since the hook dll is designed to do the parameter parsing and
repackage
>the parameters into the message parameters, I would need to be able
to
>recompile the dll code after adding parameter management to the
other
>cases. Does anyone know of a freely available (or inexpensively
available)
>16bit Windows compiler?
Until someone comes up with a compiler, you can just send me the
changes
and I'll send you a fully compiled DLL back. (Does that make me a
freely
available / inexpensive compiler?)
>This would also be necessary for this technique to
>be released under the GPL, since people have to be able to
recompile all
>the code. If such a compiler is not available, then the SetDDIHook
>technique cannot be used (since it requires a 16bit DLL to hold the
hook),
>which would really depress me.
I'm sure we'll be able to find something here. I've got the
environment to
build the DLL with 16-bit Visual C++ at the moment, but given time
and
enough interest from others, I could port it to the Borland Turbo
C++
compiler (that should be gathering dust somewhere) and is still
being
sold.
Keith
([EMAIL PROTECTED])
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
