Why does D2_3DFX crash in the middle of a game and sometimes leave my screen in an unusable state?
D2_3DFX v1.02b has a known problem in which it will issue “Assertion Failures” at odd places in the game, resulting in you being kicked back out to DOS/Win95 without warning, and usually accompanied by a single-line error message. Please download v1.06b from the Patches Page to correct this problem. Note: Due to bugs in DOS4GW and in the original Descent2 code, the game may still crash, and it may leave your screen in an unusable state as a result. It was quite common to see DOS4GW errors occur in the middle of a game in the non-accelerated version of D2, but since your 3DFX card is active, you won’t see that text output if D2_3DFX crashes. Unless your Glide drivers are intelligent enough to tell when the program has finished running, you will probably be sitting there seeing the last thing it rendered while you attempt to regain control of your system. Currently the only known way to correct this problem is to reboot. (Unless you happen to have a switchbox or two monitors or something
D2_3DFX v1.02b has a known problem in which it will issue “Assertion Failures” at odd places in the game, resulting in you being kicked back out to DOS/Win95 without warning, and usually accompanied by a single-line error message. Please download v1.06b from the Patches Page to correct this problem. Note: Due to bugs in DOS4GW and in the original Descent2 code, the game may still crash, and it may leave your screen in an unusable state as a result. It was quite common to see DOS4GW errors occur in the middle of a game in the non-accelerated version of D2, but since your 3DFX card is active, you won’t see that text output if D2_3DFX crashes. Unless your Glide drivers are intelligent enough to tell when the program has finished running, you will probably be sitting there seeing the last thing it rendered while you attempt to regain control of your system. Currently the only known way to correct this problem is to reboot.
