Try to manually set PCI bus frequency @default.

Just found again this stupid thread...
LOL!

I got this email from the same fake member as well.

200W PSU was only a generic suggestion to use a more balanced and dimensioned PSU; you can find 300W PSU from Seasonic as well that can do the job magnificently and although not fanless they are silent enough.

Which controller is used on your SATA-IDE adapter BTW?

There are several things that I would inquire.

- Different BIOS settings as already suggested
These below are BIOS optimizations, but you can try them anyway to get stability:
In the BIOS, if available, set to ENABLED:
1) Snoop Ahead
2) Host Bus Fast Data Ready
3) PCI 2.1 Support

Set to DISABLED instead:
1) PCI/VGA Palette Snoop

Set to 0 'PCI Latency Timer'
Disabling 'Power Management' is also suggested
- Different PCI slots combos as already suggested
- Swap the Voodoo2 each other; maybe one would prefere to be MASTER, while the other would prefere to be SLAVE. Usually if you own two identical card there is no particular preference but you never know...
- You must try the Voodoo2 on another and more conventional system, test them singularly then again in SLi (as already suggested)
- Last but not least: if both cards separately are working properly but together in SLi not, you may have a bad SLi ribbon cable. It's self-built? BTW, check the cable links.

I don't think that the SSD, if working as I suppose, could interfere in that way, but yes, try with an old HDD. To be honest (and meticulous) that PSU (very good Seasonic PSU) is overkill, I would swap it with an old 200W PSU. Actually the system's load is too low and the PSU is working inefficiently, generating more heat than power. That's no good in a long run.

P.S.
I'm very curious about the way you used to link the SATA SSD to the old PATA motherboard. Could you share some details please?
Thanks

Nope, sorry.
No way to put two Voodoo5 in SLi. This would require additional electronics wich is not present on board.

How much you underclocked the card?

In short:

Glide/OpenGL games: You force 3Dfx acceleration putting proper glide/opengl library in the game directory.

D3D games: If more than one D3D accelerator is present in the system and you are going to play any D3D games, you should be able to select any of the D3D accelerators in the list of a 3D setup launcher (e.g. Fifa99). Otherwise I think you can force the game to choose the 3Dfx adding proper strings to the game shortcut.

You are wrong about CoD.
The game has been developed around the Quake3 Team Arena core (id Tech3 engine) but it has been highly modified then.

Minimum system requirements tell of 3D hardware accelerator card required with 100% DirectX 9.0b compatible, 32MB and hardware T&L-capable video card with latest drivers.

There aren't any clues to make me think the game could run with a Voodoo3 out of the box.

Source: http://support.activision.com/articles/en_US/FAQ/Call-of-Duty-Minimum-System-Requirements

It has to do with bios (hardware level), so no drivers (software level) compatibility issues should be involved at that point.

Check your bios settings, for any resource conflicts (I/O Address, IRQ, etc.) and in particular be sure you don't have any of the following features enabled in the CMOS:

#Video BIOS shadow or cache
#VGA Palette Snoop or DAC Snoop
#Hidden Refresh
#Byte Merge

It has been discussed many and many times but the Voodoo3 is strictly limited to 16MB.

3dfx reference drivers, the last official release from 3dfx for Win98.

Here you go: 3dfx 1.07.00 WHQL

Don't forget to install DirectX 7.0 if you haven't done yet.

I have already seen that aluminum cooler; maybe someone at VA board made it.

Oh plz...
That is embarassing.

Nope.
It's a custom I/O analogue video connector.