Do you hear the relay clicking in to indicate the 3dfx output become active?

it's a monster3d, so there is no relay.

like I said, direct3d works, only both unreals show only dark screen

Try these : http://www.falconfly.de/downloads/voodoo1-30100.zip

voodoo1 reference driver, same issue as with diamond drivers

Oh yeah. I used to have problems with some games and drivers too.
Try these then : http://www.falconfly.de/downloads/voodoo1-30001.zip
http://www.falconfly.de/downloads/voodoo1-216.zip

If these fail as well, then maybe you installed the first one incorrectly and it has affecter all further installations. I suggest you fully remove the card both from Add/Remove Programs and the Device Manager and then go to Windows\inf\Other and delete the inf file that refers to the Voodoo 1 and then do a clean install.
Hope that helps!

Also, any other games having problems? Have you tried inserting the VGA cable from your monitor directly to the card when Unreal/Unreal Tournament runs? Try Direct 3D on both GeForce 4 and Voodoo 1 as well and tell us the results. Finally, I think the GeForce 4 could be causing you trouble and it may be best if you could replace it with a TNT 2 or something similar.

tried all of them, all work well with direct3d, but no glide in unreal 🙁

That's bizarre. Voodoo 1 really does work with Unreal and UT99. 😉

The most obvious possibility is some sort of hardware conflict. Try pulling cards and even try a different primary graphics card.

Also can try getting some other Glide game or demo to try. FalconFly has the 3dfx demos like Wizard's Tower and the Anubis fighting game.

Out of curiosity, are you using something like 3DCC to choose which D3D card games use?

I use the gamestar direct3d benchmark, you can chose the card there.

the diamond display control page has a test page where you can see some geometric figures turning, but I don't know if that is done through glide

blast, I removed all SET SST_* settings from the autoexec.bat, now it works without problems. now I have to check which setting(s) caused the error.

anyway, thank you for your answers 😀

Just a question, What is the FSB of the system your voodoo 1 is on? Looks like its the K6-III 400 which can be 66 or 100MHz FSB.

RogueTrip2012 wrote:

Just a question, What is the FSB of the system your voodoo 1 is on? Looks like its the K6-III 400 which can be 66 or 100MHz FSB.

Seeing he managed to put a GF4 in there, I'll bet it's an AGP board, which usually are Super 7 (denoting it's 100Mhz FSB) 😉

actually the board is FSB100 capable, but since I tend to underclock I have set the FSB to 66MHz so I can dynamically switch the CPU from 133 (2,0) - 400 Mhz (6,0) using K6DOS.SYS device driver

schlang wrote:

actually the board is FSB100 capable, but since I tend to underclock I have set the FSB to 66MHz so I can dynamically switch the CPU from 133 (2,0) - 400 Mhz (6,0) using K6DOS.SYS device driver

Thanks for the reply 😉

Still interested in learning what board you used in there (and also what revision). Might be useful info as it apparently works with a GF4

it's a DFI K6XV3+/66 Rev. B1