|
Additional technical reasons for this weird crash, courtesy of the helpful guy on Usenet:
---------------------------------------------------------------------
btw. it's not obvious who's to blame for the Wizard & Warriors crash.
It's caused because the dynamically loaded old Indeo DLLs reset the
floating point state, causing floating point exceptions like divide by
zero errors not to be ignored. Since this is general problem, any
dynamically loaded DLL can do this, and one that the DirectX
documentation specifically warns about, you could blame Heuristic Park
for not taking steps to protect W&W from this behaviour. You could
blame Microsoft for the C runtime library initialization code that
resets the floating point state automatically. You could blame Intel
for not taking the necessary steps from preventing the Microsoft C
runtime initialization code from running automatically when the Indeo
DLLs are loaded. Finally you could blame Microsoft again for a
fundamentally flawed DLL system that allows this kind of thing to
happen.
---------------------------------------------------------------------
|