I am trying to setup an older system I have with my Voodoo 2 it's an Athlon 600 running windows 98... I installed the drivers for Direct X 6.1 since I didn't have a copy of Direct X 7 nearby.  And it is finally stable with the 6.1 drivers... but I can't find any evidence except  System -> Multimedia whatever -> Voodoo 2 that the thing is even installed

  I ran Dxdiag and it said "Now 3d acceleration found"
  I don't know if it's supposed to give a hint to it's existance in Display properties... but I couldn't find any there either.   The thing theoretically seems to be installed. But when I try to run Total Annihilation it gives me the standard error that iHave come to believe means "no 3d installed"

  Any ideas as to how I can test whether my Voodoo is actually installed.  ???

  Well I loaded up good old trusty *cough* "shadows of the empire" I think that was the first 3d Acceleration required game... anyway, it didn't find any 3d cards.

  So I moved on through history to Mechwarrior 3... never loaded up... however the setup only detected my 2d card while installing... however... inside of mechwarrior 3 there is system info... and under display drivers inside system info... it saw a 3d card.  

  Oh the trouble of attaching a 3d card to a 2d... why 3dfx why...

Well, the actual Problem you noted right in your first Post :

If the Voodoo2 does not show up in the device Manager (Multimedia Device), it is not properly installed.

Don't bother trying 3D Applications before that.

If your Windows System did not detect it at first boot after installation, recheck the Bios Screen at initial Boot-Up.

Depending on Bios, you should (for a very short time) see a Hardware Summary at the Bottom (press "Pause/Break" Key to Pause the text display).

If that is also not present, re-check if the Bios is set to "PnP OS Installed = Enabled".
(or try Disabled to force detection at boot)

Last resort, move the Card to another PCI slot, and if even that fails, test it in another Machine.

Finally, if all that failed, the card might be defective after all  ::)
-------------------
Q : Why did 3dfx do the right thing, and made an Add-On card first ?

A : Because people were already gaming in 3D (Software Rendering) with their quite expensive and specialized 2D Cards w/ Vesa 2.0 & often full Windows GUI Accelleration.

At that time, there was no 2D Core existing, that 3dfx could have used to challenge the tremendous 2D Speeds of a Tseng Labs ET4000 or even the ET6000 chip, for example.

People loved their existing 2D Cards just like people today love their 3D Beasts, and sure did not want to exchange it for something far less capable in 2D, just to get the 3dfx 3D advantage.

(Bare in mind there were still alot of non-3d Accellerated Games out there, not even to mention the great, older ones still being played).

I ran my first Voodoo1 besides a Hercules Dynamite 128/Video PCI, which (when I bought it) was quite costly, and was on the performance King of the Hill for a long time ;)

The attachment of a completely separate 3D Card was (and still is) a very easy thing. It just needs to work in the first place, everything after that is almost failsafe.

Falconfly's right.

If it isn't under Control Panel, System, Device Manager, Sound Video and Game Controllers then it isn't installed.

Remove the card and reboot.  Refit the card and reboot again.  Window should detect a new device and allow you to point it at the drivers.

If Windows doesn't detect it then there's something very wrong with either the Voodoo2 card, the motherboard or the Windows install.

  Actually you misred.  I said I can't find any evidence except under device manager to it's existance.  I'll check my bios that sounds like a good track to follow

And how did you know i had a Tsung 4000... (You were joking about termendous speeds right? 2mb wonder can't even display 1024x768 in 16bit right now...)

Also... are 3dfx tools required to be installed?

Also... should dxdiag show any hint to it's existance if installed properly?

Oops, I'm getting old, didn't see it...

I was talking about 1997-type computers though, since you asked why 3dfx made it an Add-On card ;)
----------------
Anyway, so you say that the Card actually is installed under the device Manager... that's good.

What exact Driver did you use? (I hope an AMD Athlon compatible 3rd party Driver)

And what is your Primary VGA Card ?

When runnnig DXdiag, you usually need to select "Secondary Adapter", and so need to do all Games, in order to use the Voodoo2.

If your primary VGA Card has no 3D Capabilities, I believe all Games should automatically revert to the Voodoo2. If it has 3D capabilities (insufficient), however, the Games need to be setup to use the secondary Adapter.

Cards like the Matrox G100 or the Mystique were good examples. If not manually set otherwise, many Games simply used the poor primary 3D Adapter instead.

The Voodoo2 Drivers all come with their own "3dfx Tools", which are simply the additional Tabs in the Display Properties.
If those are not present, something went terribly wrong during the Driver Installation.

PS.
2MB are still good enough for 1600x1200 16bit Desktop ;)

Well apperantly somthing went terribly wrong...

I downloaded the Official 3dfx drivers for DirectX 6.1 don't remember the exact number... and then downloaded the DirectX 6 Athlon patch...
and installed the "newest 3dfx tools" but there is still no tabs in my display properties...

My primary is a Tseng ET6000 according to drivers... the card is so far out of memory I don't have a clue what it was when I bought it... ;)

When I had the DirectX7 drivers installed (Latest official drivers) it did have a voodoo tab I think....
but it would lockup whenever I touched it... which was what made me believe ineeded the older directX6.1 drivers for a fresh install of Windows 98 SE

Time to go burn my nteenth CD full of drivers...

Ah, okay.

Well, the "3dfx Tools" (standalone Download) is not meant for Voodoo1/2.
(at least I never tried it for these cards)

The Voodoo2 Property sheet handler should be in every Driver Release (3DfxV2ps.dll).

It also might be best to completely uninstall the Card's current Driver, and download one of the latest, complete Packages. (e.g. FastVoodoo2 V3.5)

That was the Driver I used when I tried one of my Voodoo2's in my main System (Win98SE) as well, worked perfect !
Since it's all in one package, no Driver patching required :)

PS.
Shame on me.
I rechecked the Listing of the 3dfx Tools, and I did not leave any statement that they're not to be used for Voodoo1/2 :P

Gonna fix this right now.

Glad to hear they arn't intended... because they aint doin nothin.

Well here is what I did.

I removed it the card in the Device Manager..
I removed th card.
rebooted.
Put the card in a new slot
installed DX 7.0
Installed Athlon Drivers 3.02.02
Installed apperantly needlessly the 3dfx tools
rebooted
the computer is stable... unlike the normal 3.02.02 or the 3dfxers or whatever they are called's drivers. and still DXdiag only sees one video card there is no "secondary display" option.  Shadows of the empire still doesn't detect it.  And there is still no tab under display properties...
Off to try the Fastvoodoo if this doesn't work... I the king of screwy problems Am going to shoot myself ;)

(Just to give you an example of how I attract these kinds of errors... I once had a computer that unless the keyboard was unplugged it wouldn't turnon... that was a hastle ;)

 WElll.... I tried installing the FastVoodoo 3.5 and nothing happened... I mean that it said "you must reboot for all effects to take place" and I rebooted... and the driver was still my old drive.r..and there was still no tab in my display properties...

I give up... I'm formatting and reinstalling windows...
back to stage 1.

Hmm...

Very odd, I ran my Voodoo2 for testing besides a Radeon 9700pro, and after installation (using an older FastVoodoo2 release back then), everything worked right from the beginning (?)

 Welll I formated... Reinstalled windows... Fresh install.   Tried running FastVoodoo 3.5 nothin happened still "unknown multimedia device" no drivers installed...

I tried installing the Athlon 3.02.02 drivers.. they installed it detected a "Voodoo 2" installed.... No tab in DisplayProperties....

Sooooo I checked the *.ini file and read through the registry entries... it deletes all old entries blah blah blah... and then enters in a set for the panel... I checked in the registry... all of them were infact installed and in their rightful places... what a shame... So I downloaded the new Cpanel... replaced the DLL... still nothin (after reboot of course)

Stable as can be... no crashing... no non detection in windows...   However... I never do see a Voodoo emblem in the bios... then again I don't ever remeber one when I last installed it...

I have absolutely no more ideas, not a one... Too bad there is no available tech support :) or a warranty.

Hm, are you sure it is a Voodoo2 ?

Because if it is not, this is the only reason I could imagine why all Drivers fail...

Do you have a Picture of the Card ?

  No doubts... it's a Voodoo 2 1000.  Only card I have with a passthrough cable. And 3dfx written all over it.

Hm, my tests with the Voodoo2 were done with DirectX 9.0 .

I'll keep an eye on 3dfxzone.it for updates concerning the FastVoodoo2 3.5.
(After all, it is only a few days old, maybe there's a Bug in it? )

...and I did test it quite a bit, Unreal Tournament, 3D Benchmarks (even 3D Mark 2001SE) etc.
Worked fine, so I believe it is not needed to stay on a DirectX 6.1 or 7.0 level.

Gavin said:

Quote:

When I had the DirectX7 drivers installed (Latest official drivers) it did have a voodoo tab I think.... but it would lockup whenever I touched it... which was what made me believe ineeded the older directX6.1 drivers for a fresh install of Windows 98 SE

Go back to this configuration.  Then go to Start, Run and type in "msconfig" (without the quotes).  Uncheck the Voodoo2 reference under the Startup tab.  Then reboot.

Now try to access the Voodoo2 tab in Display Properties.  And see if there's a "Display 2" tab under DXDiag.  Any better?

Thanks for the advice about using fastvoodoo 3.0  I found some forums on Google Groups about this... and I emailed the desperate brother abroad for hope and inspiration, hopefully someone has finally fixed it with the exact same problem.

Hmmm a Voodoo 5 5500 is only 18 bucks.... that sounds mighty nice about now.

 There is no Voodoo 2 option under msconfig... should there?

 I installed DirectX 8.0 and Fast Voodoo 3.0 (which actually worked this time) and to no avail... still the same. I even jiggled the monitor cable... still didn't work.

Hmm...

Well, unless your Card works fine in another System, I'd say it's either defective, or shows a rare incompatibility with your System (?)

How hot does it get when in the System ?