VOGONS


Troubleshooting a Voodoo2, help wanted

Topic actions

First post, by vanseijen

User metadata
Rank Newbie
Rank
Newbie

I'm trying to get a Voodoo2 running on an old (German) Win98 system. It's an original system from 98. I haven't touched a windows machine for over a decade, but found some solid 90s games I used to play. So I thought investing in the machine would be worth it to get a trip down memory lane.

Here are the specs of the rig:
mohterboard: biostar M6TLC
CPU: Intel Pentium II Celeron 300a w. 64mb ram
Videocard 1: Diamond Viper v330 Riva 128
Videocard 2: Techworks Power3D Voodoo2 12mb

So here's what I'v done so far to get the Voodoo card working, without success I might add.

1. Installing card and driver using original driver cd that came with the card > card is listed in device manager, but upon further inspection no drivers seem to be installed.

16265480_1269011029852231_8424074318608682374_n.jpg?oh=82626be891e025bf103a394e3f634b7c&oe=59015F46
16195760_1269011353185532_8497718345295048929_n.jpg?oh=085bea8f1346e3cec05aaa101e14274f&oe=5910BA53

2. Removing card and re-installing it with FastVoodoo2_4.6 drivers yields same results (in list without drivers).
3. Removing card physically and installing it in another (English) Win98 rig (pentium 200MHz S3 Virge DX); again same behavior

16265890_1270489716371029_8118732391639121326_n.jpg?oh=b97b4757cac9a95af14e69a11754b35b&oe=59203C1F
16195914_1270490039704330_8661441569518682280_n.jpg?oh=68a09cd358c264bb15dcb6089c5d84fd&oe=5909C6A9
16142924_1270490169704317_7162530184227902832_n.jpg?oh=964c2008fb5f919dd4c3d02946b31b30&oe=59174844

4. Putting it back in the German build, reinstalling FastVoodoo drivers and trying 3DMark99 Max shows an interface where I'm unable to select the Voodoo card. The card shown is the other one in the pc.

16174940_1271357449617589_1798301393774542998_n.jpg?oh=411fcc2b8975e61b5977b644f8b292de&oe=59170105

This is driving me up the wall. Any help would be greatly appreciated.

Reply 1 of 20, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

Are you sure 3DMark99 is capable of running on a Voodoo2? (EDIT: This thread shows it, but that's SLI.)

Perhaps it would be better to try some other benchmark first. Offhand, rRootage would be worth a try. To use it on your Voodoo2, copy 3dfxvgl.dll (which should be in your Windows\System32 directory) to the game's folder and rename it to opengl32.dll.

Reply 2 of 20, by synrgy87

User metadata
Rank Member
Rank
Member

Try the latest official 3dfx voodoo 2 drivers, and that the VGA passthrough cable is connected.

Reply 3 of 20, by Jorpho

User metadata
Rank l33t++
Rank
l33t++
synrgy87 wrote:

and that the VGA passthrough cable is connected.

The presence or absence of the passthrough cable should make no difference to Device Manager or any dialog box in 3DMark.

Reply 4 of 20, by synrgy87

User metadata
Rank Member
Rank
Member

3D Mark 99 max does work with single voodoo 2, (and SLI of course)

The presence or absence of the passthrough cable should make no difference to Device Manager or any dialog box in 3DMark.

Yes you are correct.

Is there a possible resource conflict, maybe with a sound card, could be stopping the Voodoo card initialising properly.

edit: The card itself could be at fault

Reply 5 of 20, by meljor

User metadata
Rank Oldbie
Rank
Oldbie

3dmark 99 runs fine on a v2 (and would be much quicker than the riva 128). it even runs fine on a voodoo1.

Take the card out and inspect every chip and see if none of the tiny legs on the chips touch or even came loose. There are a LOT of them and they get damaged very easily often resulting in the hardware getting detected but not working, a black screen or artifacts depending on which chip is the problem.

I fixed a couple of them by straightening a bend leg (or two..) with a small needle and some patience. Cards worked fine after that.

If that isn't the problem and there is no other damage the card is probably dead.

asus tx97-e, 233mmx, voodoo1, s3 virge ,sb16
asus p5a, k6-3+ @ 550mhz, voodoo2 12mb sli, gf2 gts, awe32
asus p3b-f, p3-700, voodoo3 3500TV agp, awe64
asus tusl2-c, p3-S 1,4ghz, voodoo5 5500, live!
asus a7n8x DL, barton cpu, 6800ultra, Voodoo3 pci, audigy1

Reply 6 of 20, by meljor

User metadata
Rank Oldbie
Rank
Oldbie
synrgy87 wrote:
3D Mark 99 max does work with single voodoo 2, (and SLI of course) […]
Show full quote

3D Mark 99 max does work with single voodoo 2, (and SLI of course)

The presence or absence of the passthrough cable should make no difference to Device Manager or any dialog box in 3DMark.

Yes you are correct.

Is there a possible resource conflict, maybe with a sound card, could be stopping the Voodoo card initialising properly.

edit: The card itself could be at fault

Conflicts do not occur often, as the voodoo doesn't require an irq adress. Changing slots can sometimes help, don't know why, and always worth a try.

asus tx97-e, 233mmx, voodoo1, s3 virge ,sb16
asus p5a, k6-3+ @ 550mhz, voodoo2 12mb sli, gf2 gts, awe32
asus p3b-f, p3-700, voodoo3 3500TV agp, awe64
asus tusl2-c, p3-S 1,4ghz, voodoo5 5500, live!
asus a7n8x DL, barton cpu, 6800ultra, Voodoo3 pci, audigy1

Reply 7 of 20, by synrgy87

User metadata
Rank Member
Rank
Member
meljor wrote:
synrgy87 wrote:
3D Mark 99 max does work with single voodoo 2, (and SLI of course) […]
Show full quote

3D Mark 99 max does work with single voodoo 2, (and SLI of course)

The presence or absence of the passthrough cable should make no difference to Device Manager or any dialog box in 3DMark.

Yes you are correct.

Is there a possible resource conflict, maybe with a sound card, could be stopping the Voodoo card initialising properly.

edit: The card itself could be at fault

PCI slot weirdness is always fun 😁

Reply 8 of 20, by vanseijen

User metadata
Rank Newbie
Rank
Newbie

I've used the Voodoo in 2 separate Win98 systems with obviously different PCI slots and different sound cards. So changes of incompatibility with soundcards and pci weirdness are slim to none I would think. I'll take out the card and look for damage on the chips.

Reply 9 of 20, by vanseijen

User metadata
Rank Newbie
Rank
Newbie
meljor wrote:
3dmark 99 runs fine on a v2 (and would be much quicker than the riva 128). it even runs fine on a voodoo1. […]
Show full quote

3dmark 99 runs fine on a v2 (and would be much quicker than the riva 128). it even runs fine on a voodoo1.

Take the card out and inspect every chip and see if none of the tiny legs on the chips touch or even came loose. There are a LOT of them and they get damaged very easily often resulting in the hardware getting detected but not working, a black screen or artifacts depending on which chip is the problem.

I fixed a couple of them by straightening a bend leg (or two..) with a small needle and some patience. Cards worked fine after that.

If that isn't the problem and there is no other damage the card is probably dead.

Why would a damage card, a hardware issue, result in the inability to connect the right driver, a software issue?

Reply 10 of 20, by vanseijen

User metadata
Rank Newbie
Rank
Newbie
The attachment IMG_1708.JPG is no longer available

Reply 11 of 20, by vanseijen

User metadata
Rank Newbie
Rank
Newbie
The attachment IMG_1703.JPG is no longer available
The attachment IMG_1704.JPG is no longer available
The attachment IMG_1705.JPG is no longer available
The attachment IMG_1706.JPG is no longer available
The attachment IMG_1707.JPG is no longer available

Reply 12 of 20, by meljor

User metadata
Rank Oldbie
Rank
Oldbie

Looks fine to me too but i can not see every single leg on the foto's. Look only at the 3 chips with ''3dfx'' on them, every single leg of the chip. If they are not bend and short with another pin they are ok.

If there is a short circuit there is a hardware failure, if there is a hardware failure the software may not see the card, or fully recognise it. Simple as that.

Otherwise there can be all sorts of things (bad connection, chip failure etc.) and the card may just be dead.

asus tx97-e, 233mmx, voodoo1, s3 virge ,sb16
asus p5a, k6-3+ @ 550mhz, voodoo2 12mb sli, gf2 gts, awe32
asus p3b-f, p3-700, voodoo3 3500TV agp, awe64
asus tusl2-c, p3-S 1,4ghz, voodoo5 5500, live!
asus a7n8x DL, barton cpu, 6800ultra, Voodoo3 pci, audigy1

Reply 13 of 20, by SSTV2

User metadata
Rank Oldbie
Rank
Oldbie

I don't remember how driver tabs looks like in Win98 for a Voodoo2, but from what i can see, card was detected by the PC and drivers were installed (resource tab is present), what do you get when trying to run glide games?

Reply 14 of 20, by vanseijen

User metadata
Rank Newbie
Rank
Newbie
SSTV2 wrote:

I don't remember how driver tabs looks like in Win98 for a Voodoo2, but from what i can see, card was detected by the PC and drivers were installed (resource tab is present), what do you get when trying to run glide games?

The drivers arent' loaded, and running a glide game uses the riva 128 card. Also the benchmark tool doesn't see the Voodoo card.

Reply 15 of 20, by akula65

User metadata
Rank Oldbie
Rank
Oldbie

Is the OS build a clean one from scratch, or are you trying to install on an old, existing build? If it is an old build, then you might have old/conflicting Voodoo drivers that are causing you grief.

Reply 16 of 20, by SSTV2

User metadata
Rank Oldbie
Rank
Oldbie
akula65 wrote:

Is the OS build a clean one from scratch, or are you trying to install on an old, existing build? If it is an old build, then you might have old/conflicting Voodoo drivers that are causing you grief.

Gotta be it, installed card myself in Win98 machine with V2.10 drivers, didn't even had to restart PC for it to be detected by all games both in glide and D3D modes. That "No driver files are required or have been loaded for this device" line can be ignored in driver tab. Use 3dfx driver sweeper or manually delete all files associated with 3dfx, also delete driver info database from your previous installs in c:\windows\inf.

Good luck.

Reply 17 of 20, by synrgy87

User metadata
Rank Member
Rank
Member

Just noticed something in my own PII 450, 440BX chipset, Voodoo 2 SLI windows 98SE machine, I got a new(old) Geforce2 GTS card in today, so decided to check that out and run a benchmark.

Drivers installed fine, card seemed to be working(at least boot up, desktop, resolutions etc).

I fire up 3D Mark 99 MAX and it only lets my pick 3Dfx Voodoo 2, the Geforce2 isn't listed.

Just thought I'd post this back here, May be an issue with 3D Mark 99 rather than the Voodoo card itself, Will poke around a lot more tomorrow.

Reply 18 of 20, by akula65

User metadata
Rank Oldbie
Rank
Oldbie

In addition to things mentioned by SSTV2, "old/conflicting drivers" would also include registry entries created by manufacturers other than that of your Riva 128.

Reply 19 of 20, by vanseijen

User metadata
Rank Newbie
Rank
Newbie

It's an old build, so the next step will be an entire new clean install. Only then will I be sure that the change of conflicting drivers is zero.