On Tue, 20 Jun 2006 12:49:25 +0200, Jan-Espen Pettersen wrote:
Can a win32 program expect that it has write access to the memory pointed to by the return value of LoadResource with module 0x00400000? Should LoadResource in some cases copy the memory and return a writeable copy of the resource?
The SEH handling code should catch this case and un-protect the resource section. At least it does for InstallShield ... I'm not sure why it's not working here.
thanks -mike