Help with 3d Blaster Voodoo 2!!

[ArgonV]

Ive had this add-on accelerator for some time (Creative 3d Blaster Voodoo 2) and I decided to put it with my GeForce2 MX400 so I can have Glide support. (For Glide games I still play)

Well the darn thing wont show up properly!! In the control panel under system it tells me there are no drivers installed and it wont show up in the display properties. (These are with the updated drivers from Creative) and when I install the drivers that came on the CD, if I overwrite this one file explorer crashes and if I dont overwrite it, the card still doesnt work properly... http://www.sysopt.com/forum/frown.gif

Any ideas? I REALLY want Glide support back...

Thanks!!!!!! http://www.sysopt.com/forum/smile.gif

[NDD]

Post specs of your system. If you have AMD Ahtlon/Duron based machine, you'll need mismatched drivers for your V2 : http://tempest.xcl-clan.com/

Best Regards ...

[ArgonV]

Im running a:

-AMD 1.2 Ghz CPU
-ASUS A7V133 MB w/VIA Apollo KT133A North Bridge System chipset
-Sb Live! X-Gamer sound card
-GeForce2 MX400 AGP card
-Creative 3D Blaster Voodoo 2 (Doesnt currently work correctly)
-256 MB of PC100 SDRAM

What do you mean mismatched drivers?

Another question, which one of these downloads should I get?!?

Thanks for your help!! http://www.sysopt.com/forum/smile.gif

[This message has been edited by ArgonV (edited 06-28-2001).]

[Brian48]

Don't use the Creative drivers. They do not work with Athlons at all. Just use the last reference drivers released. They should still be available over at 3dfx.com. 99% of the time, you don't even need the special "hacked" Athlon drivers either. Most of the problems with crashes upon startup and the control panel applet is caused by the rundll32 command in the startup.

Simply do a clean install using the reference drivers, HOWEVER when prompted to restart the computer, select NO instead. Run REGEDIT and follow the path:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Run

Delete the reference to the V2, exit REGEDIT, and reboot. That should take care of the problem.

[ArgonV]

Thanks guys!!!!!!!!!! Worked like a charm. http://www.sysopt.com/forum/biggrin.gif