VOGONS


First post, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

I moved my 2x Voodoo 2's from a Gigabyte GA-5AA (2x Voodoo 2's working perfectly in DOS) to a AOpen AX59 Pro, including the SDCard running DOS.

Now I've got a really strange issue I've never come across before. If I have two Voodoo 2's installed on the AOpen AX59 Pro, when you run a 3dfx game in DOS (even with the SLI cable disconnected), just a black screen appears. You can hear the games sound through the speakers so nothing has crashed. This happens with Tomb Raider and Descent 2. As soon as you remove one of the Voodoo 2's then then both games run perfectly. Each card works perfectly when installed solo. Mojo is also happy with each card.

In Windows 98 SE, with both cards installed. Everything runs perfectly. Quake 2 @ 1024, Quake 3 @ 1024 and 3DMark99. Fantastic FPS and Score!

Specs below;

AMD K6-2+ 550 / Memory: 128MB
AOpen AX59 Pro rev 3.1
S3 ViRGE/GX2 4MB (Diamond Stealth 3D 4000)
2x 3dfx Voodoo 2 12MB (Diamond Monster 3D II) in SLI rev A & B
Creative Sound Blaster AWE64 Gold
Network: NE-12 (UMC9007F)

I removed the sound and network card in case there some weird memory address conflict but that hasn't helped. I've also tried the Voodoo 2's in all the other PCI slots but no luck.

Has anyone come across this before?

Last edited by zuldan on 2025-02-28, 23:03. Edited 3 times in total.

Reply 1 of 15, by Horun

User metadata
Rank l33t++
Rank
l33t++

Probably a bios issue causing it. The Aopen was never retail in my area but the Giga was so that makes me think bios compatibility. Probably wrong but my 2 cents worth....

Hate posting a reply and then have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. Stuff: https://archive.org/details/@horun

Reply 2 of 15, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

I’ll try playing with this BIOS settings and see what happens. I’ll also change the AGP card and maybe the PSU as well. Although if it’s working under Windows then changing those components shouldn’t make a difference.

Looks like someone else here had a very similar issue 3Dfx Voodoo 2 SLI Black screen

Maybe changing the Fast PCI reads would help Re: Voodoo 2 SLI Black Screen

Reply 3 of 15, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

Update on everything I’ve done so far;

- Removed all ISA cards
- Bypassed config.sys and autoexec.bat
- Tried all PCI slots
- Changed AGP card
- Changed PSU
- Changed monitors
- Tried every single BIOS option
- Reverted to previous BIOS version
- Set SSTV2_FASTPCIRD to 0

For a sanity check I installed the Voodoo 2's and DOS SDcard back in the GA-5AA and Tomb Raider and Descent 2 are working perfectly.

Both Voodoo 2’s work perfectly solo in the AOpen AX59 Pro in DOS but as soon as they are installed at the same time I just get a black screen in 3dfx games. SLI in Windows 98 is working perfectly.

I wonder if it’s something like the PCI registers need to be changed? Re: Voodoo 2 difficulties.

If anyone has any other ideas, I'm all ears

Reply 4 of 15, by buckeye

User metadata
Rank Oldbie
Rank
Oldbie

Try a slower cpu? When I had problems with TR1 and Descent 2 running a voodoo sli dropping from a 800 P3 down to a 350 P2 fixed it.

Asus P5N-E Intel Core 2 Duo 3.33ghz. 4GB DDR2 Geforce 470 1GB SB X-Fi Titanium 650W XP SP3
Intel SE440BX P3 450 256MB 80GB SSD Asus V7700 GF2 64mb SB 32pnp 350W 98SE
MSI x570 Gaming Pro Carbon Ryzen 3700x 32GB DDR4 Zotac RTX 3070 8GB WD Black 1TB 850W

Reply 5 of 15, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie
buckeye wrote on 2025-02-24, 18:02:

Try a slower cpu? When I had problems with TR1 and Descent 2 running a voodoo sli dropping from a 800 P3 down to a 350 P2 fixed it.

I ran setmul to slow it right down but no luck. The games run fine in SLI with the exact same CPU in the GA-5AA. Thanks for the suggestion though. I’ve spent too much time on this issue. Might be time to give up 🤣

Reply 6 of 15, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

Spent a couple more hours but still no luck. I’ve set SSTV2_INITDEBUG=1 and SSTV2_INITDEBUG_FILE=C:\debug.txt before running the games but the debug.txt file never gets generated.

I’m starting to think the AOpen AX59 Pro is incompatible with using two Voodoo 2’s in DOS. Maybe something specific to Rev 3.1?

Reply 7 of 15, by Socket3

User metadata
Rank Oldbie
Rank
Oldbie
zuldan wrote on 2025-02-26, 11:52:

Spent a couple more hours but still no luck. I’ve set SSTV2_INITDEBUG=1 and SSTV2_INITDEBUG_FILE=C:\debug.txt before running the games but the debug.txt file never gets generated.

I’m starting to think the AOpen AX59 Pro is incompatible with using two Voodoo 2’s in DOS. Maybe something specific to Rev 3.1?

That's not it. I've used a couple of CT6670 (12MB V2) cards in SLI together with geforce 2 mx and a K6-III 400 in my AX59 pro and had no issues getting 3dfx games to run in dos, with one or 2 cards - once I patched the games to work on a voodoo2 that is.

Reply 8 of 15, by maxtherabbit

User metadata
Rank l33t
Rank
l33t

Have you tried connecting the video cables to the other card?

Reply 9 of 15, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie
Socket3 wrote on 2025-02-26, 18:54:
zuldan wrote on 2025-02-26, 11:52:

Spent a couple more hours but still no luck. I’ve set SSTV2_INITDEBUG=1 and SSTV2_INITDEBUG_FILE=C:\debug.txt before running the games but the debug.txt file never gets generated.

I’m starting to think the AOpen AX59 Pro is incompatible with using two Voodoo 2’s in DOS. Maybe something specific to Rev 3.1?

That's not it. I've used a couple of CT6670 (12MB V2) cards in SLI together with geforce 2 mx and a K6-III 400 in my AX59 pro and had no issues getting 3dfx games to run in dos, with one or 2 cards - once I patched the games to work on a voodoo2 that is.

May I ask what revision your AX59 Pro is?

Reply 11 of 15, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

The issue has been resolved! A MASSIVE thank you to the Voodoo guru sdr. He was very generous in answering my personal call out for help. I'm a bit embarrassed as I should have thought to try playing with the cables. The solution was to connect the VGA card furthest away. I've always connected the VGA card to the closest Voodoo card. I guess you learn something new everyday.

The attachment Voodoo 2 SLI Setup.png is no longer available
The attachment TR.JPG is no longer available

Reply 12 of 15, by maxtherabbit

User metadata
Rank l33t
Rank
l33t
zuldan wrote on 2025-02-28, 23:02:

The issue has been resolved! A MASSIVE thank you to the Voodoo guru sdr. He was very generous in answering my personal call out for help. I'm a bit embarrassed as I should have thought to try playing with the cables. The solution was to connect the VGA card furthest away. I've always connected the VGA card to the closest Voodoo card. I guess you learn something new everyday.

The attachment Voodoo 2 SLI Setup.png is no longer available
The attachment TR.JPG is no longer available

This is literally what I suggested two posts ago 🤣

Reply 13 of 15, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie
maxtherabbit wrote on 2025-03-01, 01:24:

This is literally what I suggested two posts ago 🤣

You are 100% correct. I didn’t see your post. I read the PM from sdr, got so excited then responded to this thread. Sorry about that. Thank you maxtherabbit!

What I find strange is that DOS only accepts one type of cable configuration and Windows accepts both types. I’ve never heard of this before.

Reply 14 of 15, by maxtherabbit

User metadata
Rank l33t
Rank
l33t
zuldan wrote on 2025-03-01, 01:33:
maxtherabbit wrote on 2025-03-01, 01:24:

This is literally what I suggested two posts ago 🤣

You are 100% correct. I didn’t see your post. I read the PM from sdr, got so excited then responded to this thread. Sorry about that. Thank you maxtherabbit!

What I find strange is that DOS only accepts one type of cable configuration and Windows accepts both types. I’ve never heard of this before.

The underlying cause is that when SLI is supported by the drivers (your windows case) the two cards use a presence detection circuit to determine which one is connected to the video cabling and make that one the primary. When you use environment vars to make stubborn DOS games work (which typically include the one which disables SLI) the primary card then becomes which ever one is enumerated first.

Reply 15 of 15, by Socket3

User metadata
Rank Oldbie
Rank
Oldbie
zuldan wrote on 2025-02-26, 19:56:
Socket3 wrote on 2025-02-26, 18:54:
zuldan wrote on 2025-02-26, 11:52:

Spent a couple more hours but still no luck. I’ve set SSTV2_INITDEBUG=1 and SSTV2_INITDEBUG_FILE=C:\debug.txt before running the games but the debug.txt file never gets generated.

I’m starting to think the AOpen AX59 Pro is incompatible with using two Voodoo 2’s in DOS. Maybe something specific to Rev 3.1?

That's not it. I've used a couple of CT6670 (12MB V2) cards in SLI together with geforce 2 mx and a K6-III 400 in my AX59 pro and had no issues getting 3dfx games to run in dos, with one or 2 cards - once I patched the games to work on a voodoo2 that is.

May I ask what revision your AX59 Pro is?

....as far as I know there is only one revision of the AX59 Pro... I might be wrong... I have two boards, they are both identical, and looking around I can't find a "1.0" or "rev x.x" anywhere on either of my two boards.

Glad to see you got it working.