First post, by Gmlb256
This seems pointless at first but over the years I have heard that very few DOS games that uses the Glide API usually doesn't work with Voodoo2 cards according to the compatibility matrix: Voodoo 2 DOS Glide compatibility matrix
This was the only reason to get the original Voodoo Graphics card aside from prices. Got this idea when it was possible to run games using older version of the Glide API by just setting the correct environment variables for the Voodoo2, then I got this crazy thinking: Would be possible to do the same thing with DOS Glide 2.4x?
For this process I hex-edited GLIDE2X.OVL that came with the Voodoo Graphics drivers, by replacing the value used to compare the PCI device id from 1 (Voodoo Graphics) to 2 (Voodoo2) in several places when verifying the card.
Some notes:
- Prior using this, make sure that it has the environment variables set for compatibility. Get it from V2-AUTO.INF file that comes with the Voodoo2 driver or from the following thread: Tomb Raider 1 - Voodoo 2
- It uses the Voodoo Graphics SST environment variables (not SSTV2 ones) for gamma and screen refresh rate.
- Glide 2.46 doesn't work with every DOS game, but it is the fastest one.
- Tested successfully on three different CPUs: PII-400, K6-2+/450 and Coppermine Celeron 600 without any tweaking. It can also work with faster CPUs, but reliability isn't guaranteed. On a VIA C3 Nehemiah CPU, the best results were setting the FSB to 100 MHz, changing the multiplier to 10.5x and disabling the branch predictor. In some cases, setting the FSB to 66 MHz (if available) does the trick.
Special thanks to Meatball and Spark for additional testing.
VIA C3 Nehemiah 1.2A @ 1.46 GHz | ASUS P2-99 | 256 MB PC133 SDRAM | GeForce3 Ti 200 64 MB | Voodoo2 12 MB | SBLive! | AWE64 | SBPro2 | GUS