You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like quitting the program before it initializes causes some sort of memory corruption, leading to an endless loop of invalid opcode interrupts since it's trying to execute an MMX instruction that doesn't exist.
This shouldn't happen... except when it fails to initialize, for example because it didn't find any files, like running directly from the Borland C IDE.
PS: How do I build using a shareware executable?
EDIT: Go to Options->Compiler->Code Generation, and Define UPLOAD. Then it Just Works, almost like ID used that for the shareware... I wonder if the game can automatically detect the correct game type at runtime and use those variables.
The text was updated successfully, but these errors were encountered:
It seems like quitting the program before it initializes causes some sort of memory corruption, leading to an endless loop of invalid opcode interrupts since it's trying to execute an MMX instruction that doesn't exist.
This shouldn't happen... except when it fails to initialize, for example because it didn't find any files, like running directly from the Borland C IDE.
PS: How do I build using a shareware executable?
EDIT: Go to Options->Compiler->Code Generation, and Define
UPLOAD
. Then it Just Works, almost like ID used that for the shareware... I wonder if the game can automatically detect the correct game type at runtime and use those variables.The text was updated successfully, but these errors were encountered: