Information about this driver:  It overclocks your Voodoo2 from 90 =>93MHz.  This might not be an issue for some of you, but I have 4 PC's on a LAN, all with GF4's and V2's, and one of my V2's hated the overclock and locked up continuosly.  It wasn't until I installed the overclocking .dll that comes with these drivers that I realized they were overclocking the cards by default.  Personally, I think stability is the most important thing in gaming, thus I have all my V2's set back to "default."  It would have been nice if this overclock would have been mentioned in the readme, as it would have saved me many hours in troubleshooting.  

Thanks, but I doubt I'll need it.  Running the Geforce4 is MUCH faster for D3D/OpenGL, I'm using the Voodoo2's for GLIDE goodness.  No matter how fast the friggin video card, there are just some games that run better on a 3dfx card using GLIDE.  Diablo2 is a good example of this.  BTW I'm putting together a 4th rig for another player, so we'll have a quad Voodoo2 gaming LAN, lol.  Rune, UT, Diablo2 - what else ya need?  

Okay, I fixed Quake3!    I had to rename the 3dfxVGL.dll (to 3dfxVGL.old), which disabled the opengl for the V2 just like suggested.  The dummy files did NOT work, as the game still used the VGL.dll file and ran, switching from the GF4.  But now it works fine, and since the GF4 is so much faster running OpenGL anyways, it's no loss at all.  

So far, no other game seems to be exhibiting this behavior, although I though Baldur's Gate2 was but it turns out it is fine.  Thanks again for the help.

QuoteOriginally posted by 4eRNoBiL

Select "Default OpenGL" driver in the Quake 3 options menu and make sure "config.cfg" is not read-only, so that the game could save settings. Or delete the file, start Q3 and set the options you wish. It should save the driver settings, and not switch back again.

I do select the default opengl, but it switches back to the voodoo card anyways if I adjust any video setting.  The way I was fixing it was to delete the quake config file, then uninstalling the v2 drivers.  That would force it to stay on the Geforce no matter what.  Then I would reinstall the v2 drivers once I got it the way I wanted it.  

I may have to try the dummy .dll trick.  I'm hoping Quake is the only game with this behavior, otherwise I guess I'll try and disable everything else except for GLIDE if thats possible.

I used the easiest method possible to cool my Voodoo2's:  single small fan attached with double sided tape so that it cools the v2 chip.  This method is illustrated on my very old 3dfx website for a V5 5500, but same principle (please turn pop up blockers ON!):

http://nightstormer.tripod.com/voodoo_article7.htm

My Voodoo2's were locking up constantly at OEM clocking, but with this mod they work perfectly

Hi everyone, just put together a gaming LAN thrown together with old parts and stuff.  3 PC's that have P3's, GF4 MX440s, and V2 1000's (single card).  All PC's are networked running Win98SE with all updates, video cards are running nVidia 77.82 and FastVoodoo2 4.6.  I have them all in one room on a router so that we can play fun old games like Diablo2, BG2, Rune, Q3A, etc.  It's great!  

The problem I'm running into is that sometimes a game will default to using the Voodoo2 instead of the Geforce for games that I don't want it to run.  A classic example of this is Quake3 - If I change the resolution or any video setting in the game, it will immediately change from using the GF4 to using the V2.  It doesn't exit or crash, it just changes to the Voodoo card.  It's really weird, lol.  I have to uninstall the V2 drivers and change resolutions and then reinstall drivers.

I guess my question:  Is there a utility or other method by which I can force the Voodoo2 to ONLY run GLIDE games and nothing more?  Any driver files I need to delete so that Voodoo2 won't run D3D or OpenGL?  Thanks in advance, having a great time with my old hardware.  

P.S.  Hi Arch, long time no see.  

Let me first say hello, and cheers to the guys making these great drivers.  Just wondering, will you guys be making a set for those of us who have 2 different Voodoo2 cards, but want to run them in SLI?  I remember someone had drivers for mismatched SLI back in the day, and I was curious.  I have an STB Black Magic V2 12MB and a 3dfx V2 1000 12MB I would like to SLI together in XP.

Also, I put together a little system recently and popped in a Voodoo2 and did some testing in UT.  I originally posted this at x3dfx, but I wanted you guys to see it as well:

Tyan S2390B Trinity KT-A (KT133A)
Athlon XP1600+ (Palomino)
384MB Micron PC133 SDRAM
S3 Virge 2MB PCI
STB Black Magic Voodoo2 12MB PCI
SoundBlaster AWE ISA
3Com PCI 10/100
WinXP SP1 (all updates)
FastVoodoo2 3.5 XP (default settings)

Unreal Tournament v4.36 (GLIDE)
CityIntro.unr (opening flyby) high detail world/skin
640x480 = Min: 52.82, Max: 128.10, Avg: 75.29
800x600 = Min: 33.52, Max: 93.35, Avg: 52.61

These drivers work great!  No freezes, no problems.  Thanks!