What the heck would cause that?! I do remember getting dos4gw errors, but not often. I think I only ever saw that happen twice? Once was a cover disc demo of something and the other was some cheap budget game.
That error code in the video is 0D, which according to the manual means "general protection fault". I.e. the program tried to access an invalid memory address. That can happen, for example, if you allocated a list of 5 and tried to access index 6
in this particular case, the error is in code segment (CS) 80h which is 16bit (USE16) which typically belongs to DOS/4GW itself (game itself uses USE32 segment 160h)
The thing is, even though program is 32bit, it relies on DOS API for things like I/O. DOS/4GW provided "syscalls" for that
A speculation: the crash happens during a cutscene. There's probably some code that loads animation and sound from disk and sends them to screen and sound card, basing on timer — at least part of it has to be in a USE16 segment. If a file is corrupt, unpacking data may go haywire - et voila!
Comments
On Linux, that's called a "segmentation fault"
The thing is, even though program is 32bit, it relies on DOS API for things like I/O. DOS/4GW provided "syscalls" for that