LockResource16 in ole32.dll

Dmitry Timoshkov dmitry at baikal.ru
Sat Jan 24 21:56:51 CST 2004

"Ge van Geldorp" <ge at gse.nl> wrote:

> Just to be sure: if I understand you correctly you suggest doing the
> LockResource16 in LoadAcceleratorsA/W, then GlobalAlloc a new block of
> memory, copy the table to the new block and return the global memory
> handle as the HACCEL. Then in IsAccelerator use GlobalLock to get at the
> contents. Please correct me if I'm wrong.

I was suggesting to avoid using GlobalAlloc16 in LoadAcceleratorsW at all,
and use 32-bit GlobalAlloc instead.

Alexandre answered another part of your message. And yes, you are right
that support for sharing accelerator handles between processes will
require complete rewrite of that code.


More information about the wine-devel mailing list