Actually this isn't true. 3dfxogl ICD requires GLIDE3x DLL's it uses these for handling many of the screen functions. KoolSmokey made an initial direct OGL 1.3 driver that didn't require it (3dhq is no longer around though). Any 'stock' 3dfx driver uses the GLIDE driver, even if it is just to set up the screen (which it's not), it's slow because it takes OGL functions and translates them to GLIDE and translates GLIDE too whatever was native with the 3dfx cards. 
Yeah, I know about Koolsmokey. Brilliant guy, I tell you; when it comes to understanding how Glide/OpenGL seems to work on 3Dfx cards. Back when I was tryin' to figure out why FF9 had major framerate drops when several character models were on screen (the exception was for battle scenes), someone suggested I use his Glide3x update, and when I tried it with his new Glide3x, the framerate drops disappeared. Not to mention, his hosting of the Glide source code was what allowed Lewpy to figure out why the VSA-100 option under "Draw Method" wasn't working correctly.
Here is a link to a DIRECT OGL ICD 1.2 using MESA on windows the directions are that you place this in the directory of the game NOT in your windows system directory (the reason for this is clear as it will load the 3dfx driver instead of the OGL driver by KoolSmokey.. it looks in the current directory first for DLL's).
A WORKING 1.2 ICD for 3Dfx cards?! This I gotta see.
There aren't really any 'modern' driver sets mostly hacked 3dfx drivers that are repackaged. The source code for there drivers is now widely available so it's really not a big deal. Koolsmokey though did a GREAT job of making his Win2K and XP drivers. These are what you see stuffed in a lot of those 'driver' sets. If it says 3dhq it's real otherwise it's pretty much what I said.. repacked stuff with some hacked fixes generally.
Yes, that is true. However, I think I have a problem with the language of my post when I said "modern". What I meant by "modern", are the driver sets that didn't need to rely on a game-dependent Mini-GL driver due to a complete lack of an ICD in ANY licensed form. Now, not much may have changed, but at least its improved to where you don't have to select "3Dfx OpenGL" to even get hardware accelerated OGL.

I've tried 8 different sets, of them the only ones that didn't give me the blue screen of death was 3dhq's 
Ouch. You know, I heard that the Amigamerlin drivers are using the most stable builds of the 3Dhq stuff (and the set seems to have 3Dhq's blessing which may not be surprising, because Amigamerlin was one of the members of 3Dhq anyway). But still, BSOD's were THAT common? What OS are you using; WinXP?!
True and yet untrue. It will do 2d rendering in 32-bit, but the 3d pathway won't allow it. Just had to revise that. OpenGL screensavers, if the desktop is in 32-bit mode, will slow to a crawl as they will use Microsoft's 'software' OpenGL rendering.
Exactly, Lord Kane. The "odd" screensaver behaviour was one of the first things that tipped me off that the V3 is incapable of 32-bit 3D rendering.
And, I suppose I had yet another problem with language there, as well. I have very rarely heard "rendering" used to refer to a 2D drawing operation, so when I said "rendering" I thought people would assume I was refering to 3D drawing operations as done with Glide/D3D/OGL. However, you are correct, as far as DirectDraw seems to be concerned, 2D "rendering" at 32-bit color is possible, otherwise it'd be impossible to run the windows desktop at 32-bit in the first place!

You are all wrong!
Ive decided that Voodoo3 renders in 64bit. All you have to do is run a 3d game or program, 4 times at the same time.
32 + 32 - 32 - 16 = 16 + 8 - 40 + 16 x 2 = 32 x 32 = 64
Not only that, but base times height I win!!!!!!!!!!!!!!
ROFLAMO!!!!!

Thanks, I needed that. Seriously.
-edit-
In case you're wondering where I got the smilie, I "borrowed" it from the x-3dfx forums, in the forum of an image link, LOL. I don't think this would be a problem, but if there's some policy that this is running up against, I'll understand it being taken down.
</disclaimer mode off>