VOGONS


Voodoo2 debugging

Topic actions

First post, by Macsbig

User metadata
Rank Newbie
Rank
Newbie

Hi guys, hope your all doing good.

Appologies in advance, posted this in the general hardware forum without any replies. Sorry for duplicating.

I'm currently repairing two Voodoo 2's. Got them both to the state of being recognised in DOS (Detect and Mojo) and windows device manager.

I am seeing cards being identified and all 12mb of memory. Both TMU's are also showing up, but the system is crashing when launching 3dmark.

I'm looking to use the debug mode (through Autoexec.bat) but I'm getting no output (using console output switch). Does anyone know of a good tutorial to get it working? I've put all the commands in Autoexec, but realise I must be missing a vital step(s). I'm just being stupid I'm sure. Been a long time since I've delved this deep into DOS/Windows 98!

Do I need anything else loading on boot for the debug mode to see the card?

Cheers guys

Mark

Reply 1 of 14, by Lostdotfish

User metadata
Rank Member
Rank
Member

Add these lines to your autoexec.bat (or just type them in the DOS prompt after booting)

set SST_INITDEBUG=1
set SSTV2_INITDEBUG=1
set SST_INITDEBUG_FILE=c:\sst1_3dfx.log
set SSTV2_INITDEBUG_FILE=c:\sst2_3dfx.log
set SST_DEBUGDAC=1
set SSTV2_DEBUGDAC=1

Then run mojo.exe

It will create sst1_3dfx.log and sst2_3dfx.log on your c: drive. Copy those files to some external media and post the output here.

Reply 2 of 14, by Macsbig

User metadata
Rank Newbie
Rank
Newbie

Hi, thanks for the reply.

I have all the SSTV2 entries in autoexec.bat, aren't the SST ones just for Voodoo 1, or am I missing something?

I actually had it outputting to console, though, but will try both ways later. Didn't run mojo after tho, so will give that a go.

Thanks!

Reply 3 of 14, by Macsbig

User metadata
Rank Newbie
Rank
Newbie

OK, so log is as follows...

Cheers

Reply 4 of 14, by Lostdotfish

User metadata
Rank Member
Rank
Member
Macsbig wrote on 2025-11-26, 17:27:

OK, so log is as follows...

Cheers

sst1Init Routines: InitCode $Revision: 8 $
sst1InitMapBoard(): BoardsInSystem = 1
sst1InitMapBoard(): vAddr:0x10400000 pAddr:0xde000008 Dev:0x9 Board:0
sst1InitRegisters(): Setting TREX-to-FBI FIFO THRESHOLD to 0x8...
sst1InitRegisters(): Setting PRELIM FT-CLK delay to 0x8...
sst1InitRegisters(): Storing TREX0INIT0=0x5441
sst1InitRegisters(): Storing TREX0INIT1=0xf420
sst1InitRegisters(): Storing TREX1INIT0=0x5441
sst1InitRegisters(): Storing TREX1INIT1=0xf420
sst1InitRegisters(): Storing TREX2INIT0=0x5441
sst1InitRegisters(): Storing TREX2INIT1=0xf420
sst1InitSetGrxClk(): Resetting TMUs after clock change...
sst1InitRegisters(): Setting up FAST DRAM Configuration
sst1DeviceInfo: Board ID: Obsidian GE
sst1DeviceInfo: FbiConfig:0x2, TmuConfig:0x8d1
sst1DeviceInfo: FBI Revision:2, TMU Revison:1, Num TMUs:2
sst1DeviceInfo: FBI Memory:4, TMU[0] Memory:4, TMU[1] Memory:4
sst1DeviceInfo: Dac Type: ICS ICS5342
sst1DeviceInfo: SliDetect:0
sst1InitRegisters(): LFB Writes go through memory FIFO...
sst1InitRegisters(): TEXTURE Writes go through memory FIFO...
sst1InitRegisters(): exiting with status 1...
sst1InitShutdown(): Shutting down SST-1 #0...
sst1InitShutdown(): Returning with status 1...

Not seeing any DAC debugging info in your log - but this all looks correct

Reply 5 of 14, by Macsbig

User metadata
Rank Newbie
Rank
Newbie

This should be better...

Cheers

Reply 6 of 14, by Lostdotfish

User metadata
Rank Member
Rank
Member
Macsbig wrote on 2025-11-26, 20:46:

This should be better...

Cheers

Nothing wrong in that log. That's exactly how a healthy card responds.

Reply 7 of 14, by Macsbig

User metadata
Rank Newbie
Rank
Newbie

Thanks, not sure why its crashing win98se when I start 3d Mark or Quake then. Odd. I'll keep searching

Cheers for your help

Reply 8 of 14, by leileilol

User metadata
Rank l33t++
Rank
l33t++

If you're using the later V2 drivers (Nov 99+), make sure you also have at least DirectX 7 installed.

apsosig.png
long live PCem

Reply 9 of 14, by Macsbig

User metadata
Rank Newbie
Rank
Newbie

Yeh, dx8c installed and tried both "official" drivers and fast Voodoo. I'll keep trying.

Cheers

Reply 10 of 14, by Lostdotfish

User metadata
Rank Member
Rank
Member
Macsbig wrote on 2025-11-27, 06:17:

Yeh, dx8c installed and tried both "official" drivers and fast Voodoo. I'll keep trying.

Cheers

Are both cards showing the same issue?

What display are you connecting to and how? Are you using a link cable? Are you using some sort of scaler?

What motherboard/CPU combo are you using?

Was it a clean Windows 98 install?

Does the Voodoo 2 setting panel work in Advance display settings?

Have you got another system you can test in?

Try taking Windows out of the equation. Find a copy of Tomb Raider (*cough*archive.org*cough*) and burn it onto a CDR.

Boot into DOS with CD support.

Install it then copy the voodoo rush patch from the link below into your /tomb directory.

https://www.philscomputerlab.com/tomb-raider.html

Run tombrush.exe

Reply 11 of 14, by Macsbig

User metadata
Rank Newbie
Rank
Newbie

The second card is being recognised now, but memory sizes are wrong. I wanted to get this card running before finishing repair on that one (may be the FBI chip faulty, job for another time).

Just using my LED screen, works with my Voodoo3 3000 and 2000. I'm not using a passthrough, just swapping cable for testing (one less thing to be a possible fault). No scalar that I'm aware of, I have tried both 640x480 and 800x600 with the same results.

I'm using an Asus p2b with a P2 400 at the mo, but have tried it on an Intel board with a piii 1ghz (running @ 750 on 100mhz bus) same results. I will try it again on this board tho, just to be sure. I also have a Gigabyte GA6 BXE, maybe I'll try that too!

I have reinstalled Win98se, but will do that again too, as I'm getting a 3dfx dll error on startup now.

3dfx panel shows logo and doesn't crash.

I'll have a good look at things again now, when I get a chance, as debugging seems to show up ok.

Thanks for all the help, I will post again when I have some info.

Cheers

Reply 12 of 14, by Lostdotfish

User metadata
Rank Member
Rank
Member
Macsbig wrote on 2025-11-27, 08:30:

Just using my LED screen, works with my Voodoo3 3000 and 2000. I'm not using a passthrough, just swapping cable for testing (one less thing to be a possible fault). No scalar that I'm aware of, I have tried both 640x480 and 800x600 with the same results.

Have you tried it with a passthrough cable (or at least 2 displays, one on your 2d card and one on the voodoo)? Not sure if the Voodoo 2 looks for resistance before outputting a signal (it does in SLI but not sure if it also does in single card mode). It might just not be sending out the signal and by the time you swap the cable over it may have given up...

Reply 13 of 14, by Macsbig

User metadata
Rank Newbie
Rank
Newbie

Thanks again, sounds plausible, I'll try this too!

Cheers

Reply 14 of 14, by nali

User metadata
Rank Member
Rank
Member
Lostdotfish wrote on 2025-11-27, 09:03:

Not sure if the Voodoo 2 looks for resistance before outputting a signal (it does in SLI but not sure if it also does in single card mode).

It doesn't, at least on mine (STB Systems BlackMagic) .
Before ordering a cable I just disconnected the cable from the 2D card and plugged it to the Voodoo while games were running.
But of course not all V2 are the same.