On Sat, Jul 15, 2000 at 05:24:41PM +0200, Marcus Meissner wrote: > Hi, > > In the D2 installer it at one times a window procedure callback, which > comes across the function WINPROC_CallWndProc. It crashes in this function > right after proc( ... ) with an invalid ebx value. > > It appears proc() has corrupted ebx (which it should not). > > proc in this case is a WINPROC_THUNK_FROM16, which uses CallFrom16Long. > > I know that standard Win32 code should not touch ebx, but apparently this > one does. Should CallFrom16Long save & restore ebx? This has happened several times to me already (corrupted PIC EBX after winproc, to be precise). However adding a wrapper function did NOT always help. But of course this patch is a good beginning... Andreas Mohr
