First post, by ptr1ck
After building my Voodoo 2 SLI rig, I noticed the performance of the oft-recommended FastVoodoo 4.6 was not very good. SLI was not boosting performance of Direct3d for me any more than single card although the System Information tab said SLI was detected. I tested this on 98 and ME. I tested with identical cards and with mismatch. I then looked at the voodoo2.inf and noticed a pile of changes, like overclocking the cards to 93mhz and disabling vsync. To be blunt, I am not a fan of hidden tweaks just to enhance benchmark scores or inflate FPS at the cost of quality, which is what I got with the FastVoodoo 4.6, except I didn't have the performance.
The reference driver 3.02.02 also didn't act quite right for me either. This led me to piecing together a driver from the 3.02.02 reference which I included the "Athlon compatible" and "SLI Mismatched" files from the FalconFly website for Voodoo 2 drivers. The driver keeps factory clocks and does not disable vsync; there's literally an app for that. I have updated the included readme to more accurately reflect the driver changes.
The voodoo2.inf tweaks are as follows (referenced thread: Voodoo Environment Variables):
FASTMEM_RAS_READS are enabled for D3D and Glide.
FASTPCIRD is enabled for D3D and Glide.
Devices will be named "3Dfx Voodoo II PCI".
I have tested this driver some on both my machines (nforce2 and VIA KT133A) and it seems to work really well, much better than the FastVoodoo 4.6 for me. The image quality is good, and when I used the overclocking tool (not included) to disable vsync and bump my cards to 105mhz, I achieved the highest performance I've seen yet from the cards. I decided to call the driver Tribute as to pay homage to those who did the work in the files included. I do not claim to author any of the files included in this driver.
I posted just mainly to share with others an alternative solution to the FastVoodoo drivers. If this is not allowed, then I understand and will remove the attachment and only use this thread for discussion of how to build the driver yourself.