>void ReceiveArea(WPARAM wParam, LPARAM lParam, int& x, int& y, int& w, int&
>h)
>{
> x = (wParam>>4) & 0x0FFF;
> y = ((wParam & 0x000F)<<8) | ((lParam>>24) & 0x00FF);
> w = ((lParam>>12) & 0x0FFF);
> h = lParam & 0x0FFF;
>}
>
>and in 'DdiDlgProc(HWND hdlg, UINT uMsg, WPARAM wParam, LPARAM lParam)'
> case DDI_BITBLT:
> {
> int x, y, w, h;
> ReceiveArea(wParam, lParam, x, y, w, h);
> wsprintf(szDdiString, "BitBlt:\tstart {%04d,
>%04d}, size {%04d, %04d}\r\n", x, y, w, h);
> break;
> }
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.
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? 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 really wish when Microsoft made a 32 bit operating system it would use 32
bit components...
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML Mail
[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
---------------------------------------------------------------------
