Looking at the remaining 32-->16 call:

HGLOBAL16 WINAPI NE_DefResourceHandler( HGLOBAL16 hMemObj, HMODULE16 hModule,
                                        HRSRC16 hRsrc )

Given the above signature for this function,  its abundant use of 16-bit calls
(AllocResource16, GlobalLock16, GlobalRealloc16 - twice for the last two), and the fact
that the NE stuff deals with Win16 executables, is this really a 32-bit function?
Does it need conversion?

-- 
Andrew :-)

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html

"Windows is the one true OS. MS invented the GUI. MS invented 
   the 32 bit OS. MS is open and standard. MS loves you. We have 
   always been at war with Oceania." 

Attachment: msg17107/pgp00000.pgp
Description: PGP signature

Reply via email to