koolsmoky's driver works fine under win7 32bit,even sli is ok-I have tested it myself.

QuoteOriginally posted by ms-dos

QuoteOriginally posted by netbeast

if anyone know how i can get a voodoo 2 to work in windows 7 please contact i know theres no current drivers and i dont know if anyone is making one im cheap right now but im computer doesnt handle any 3d.

there are drivers that work in win7 32-bit fo2 the voodoo2

but if you are use a 64-bit win7 installment you will need to use my 64 bit driver

but I have not used/tested my driver in win7 yet

Where is the 64-bit driver? I want to try with Win7x64.

Hi koolsmoky!

I've tried many-many drivers for my mismatched 3dfx Voodoo 2 12 MB SLI under XP, but almost all of them failed in various situations, except yours!

I'm using your latest driver, that you've posted here, and it works great!

Will you make any further updates for it?

Thanks!!

Best wishes,
Dobfek

Hi Dobfék,

you're welcome here.

Many thanks for your report.

Bye bye

Hi there!
I was trying to use the X-24 in my old rig
P3 1GHz (core coppermine, 133mhz)
2x256MB Pc133
all mounted on a HP Vectra VL400 DT (desktop)
I've installed the official Q3D Obsidian2 Drivers 6CF but the system hangs
(I have two X-24 and both have the same problem but under Windows Xp both run well)
Sometimes I can't see the screen properties (with a strange error message) and sometimes I can see the properties without the Q3D panel
KoolSmoky seems to be less problematic but I still have no control panel and the games don't recognize the card.
Any idea?

Hi,
Was an other 3dfx card previously installed in your system ?
What is the  error message ?

Hi Nightbird,
no, the system has been formatted, so the X-24 is the only 3Dfx card.
The recurring error is "Mutual exclusion prohibits this" when I try to open the screen properties tab but sometimes it starts well without showing the Q3D Panel. Rarely also the Q3D panel appear.
I can't figure out what's happening!

Edit: oh, well.. I'm using Windows 98 SE
Thanks

Hey Max_R,

Have you already red this: http://www.falconfly.de/info/readme-quantum-winnt-obsidian2pf-v5p.txt ?

Quote---------------------------------------------------------------------
Q:  When attempting to run an application, boot the computer, or
launch the Display Properties sheet, the error message "Mutual
Exclusion Error Prohibits This" come up?
A:  There are various reasons this message may come up.
1. The card was not shut down properly, and is still active.  Turn
  your computer off, and then back on to resolve this error.
2. The drivers from a previous 3dfx Voodoo or Voodoo 2 card
  were not properly removed.  Please follow this procedure
  <link to uninstall error> to remove our drivers and any
  previous drivers.
3. Your system BIOS is not properly interpreting the PCI-to-PCI
  bridge chip on the Obsidian2 200SB series of cards.  Please contact
  your motherboard manufacture to get the latest BIOS.
4. There is another Voodoo2 based video card in your system from a
  different manufacturer that is causing a conflict.  There can only be
  one card based on this chip set.  Please remove the other card.
5. Your card is not working properly.  Return the card for a
  replacement.
---------------------------------------------------------------------

Since both X-24s act the same way, I would try to change the platform.

EDIT: From the readings here and there this error seems to occurr as soon as another application is accessing to DirectX at the same time. I would try to change the 2D X24 companion, then select another video adapter too.

EDIT2: More details about the motherboard specs?
DirectX version?
Have you installed any kind of Win98 update?

Hi,
Can you do a ctrl-alt-del in order to see what is running ?

Indeed!
As I've said, the installation is clean and there are two active process: Rundll32 and Systray.

P.S.
The mainboard is a D9820-60009 mounted in the VL400 DT. DX9C and a Kyro2 are installed but I've also tried with the only integrated vga and DX6/7/8 with the same results.

Is your card listed twice in the device manager tab of the system properties ?

I know I'm a little late to the party here, but I just want to thank you for these drivers.

I've built myself a retro machine and spent countless days trying to get three mismatched Voodoo II's to run on it with the FastVoodoo drivers (Creative CT6670, PowerColor Evilking, Diamond Monster 3D II). None of them worked, most of the time my screen just turned itself off or the GUI was corrupted on Windows 98 with nothing happening.

These drivers have the same behaviour by default (screen turns off, nothing to see), but when I set the registry key SSTV2_MISMATCHED_SLI=1 they work reliably with every game I have on all of the cards I own.

This is awesome. I'll stay far away from FastVoodoo now and use the reference drivers with these patched glide.dll files.

And I really thought I'd have to buy a fourth Voodoo II. Thank god I don't.

Hi Schmatzler,

you're welcome and I'm sorry for my delay.

Many thanks to have shared your considerations and opinions. And I'm so happy you can enjoy your 3dfx Voodoo2 and launch Glide-based games with native hardware support!

See you soon

QuoteOriginally posted by koolsmoky
* Win9x/ME: copy glide2x.dll and glide3x.dll to c:windowssystem

This does not work!
Tested on clean win98 and voodoo 2 sli and V3.02.02 reference drivers.