Had this same thing on an ASUS P3B-F (rev 1.03) machine using Win98se- latest 440BX drivers, DX-7. Using the Matrox G400 video card and a pair of Diamond v2s in SLI. This is a P3 @ 600 - 524k cache

Right clicking to bring up the display properties box resulted in nothing. In fact the system seemed busy and Control Panel wouldn't open either- it seemed. But if given enough time the control panel would appear. Had the same "DDE Window Server not responding: dialogue.

My research suggested that the Matrox utilities (PD?) had some sort of a memory conflict with the Voodoo 2- I never tried any other Voodoo drivers other than the last available from Diamond and downloaded from Vogons.

Anyway, my impatience- after a couple of days being frustrated- resulted in my replacing the G400 with a Nvidia ti4200. Kind of cheating with the ti4200 but it supports glide quite well and the Voodoo 2 SLI setup is out of the machine altogether. I plan to add them to my Windows 95 box at some point.

An interesting aside is that I have a G200 in my Windows 95 machine with a Voodoo 1 card (Diamond) and they get along just fine. If it is the PD utility program conflicting with the V2 cards, I will know it quickly enough when the V2s go in- since I think the PD utilities may be the same regardless of G200 or G400.

Hope it helps-

That sounds EXACTLY like my issue JoeCorrado 😀

Will re-install Windows with a Geforce GeForce4 MX 440 and see if I can get these Voodoo cards going.

I used the fast voodoo drivers on my P4 with a 845 motherboard with the Intel on board graphics without any problem
Maybe the drivers will work for you as well?
Not sure about Voodoo 1 though

Ok so I tried with the MX 440 and I get the same issue. Really curious to find out what the issue might be.

How much RAM did you use? Mine has 512 MB. Might try a smaller stick.

Will try the FastVoodoo2 V4.0 Gold Edition drivers next...

Chinny22, guess what, these drivers worked fine 😀

they must address some fundamental system issue / resource conflict...

Some images:

Mau1wurf1977 wrote:

Chinny22, guess what, these drivers worked fine 😀

they must address some fundamental system issue / resource conflict...

I'll give the Fast drivers a shot when I re install the V2's as well.

JoeCorrado wrote:

Mau1wurf1977 wrote:

Chinny22, guess what, these drivers worked fine 😀

they must address some fundamental system issue / resource conflict...

I'll give the Fast drivers a shot when I re install the V2's as well.

Yea!

They miss the "disable VSync" tick boxes, but VSync seems disabled in the driver. All the scores are well over 60 fps.

Glad I could pass some help your way for a change 😀

JoeCorrado wrote:

Kind of cheating with the ti4200 but it supports glide quite well and the Voodoo 2 SLI setup is out of the machine altogether.

What ???

Davros wrote:

JoeCorrado wrote:

Kind of cheating with the ti4200 but it supports glide quite well and the Voodoo 2 SLI setup is out of the machine altogether.

What ???

kind of cheating in that I did not resolve the problem- I cheated by side stepping ... adding the ti-4200 and removing the V2 SLI setup entirely. After 2 days of wrestling with the issue.

Yea some of these issues take up so much of your time you just give up...

I'm glad that VOGONS exist and helped solve the problem 😀

From now on I will always use these fast drivers. I also have another tool installed, I believe it's called Voodoo 2 Tweaker. It allows changing the V-Sync settings, which the drivers don't.

I'm very happy now and waiting for a replacement Monster 3D II card to arrive (one of mine is faulty) and will do more benchmarking. This time with SLI on and off and also all resolutions.

I will remove Turok because it has no support for SLI though and might add UT99 as a more demanding game.

On a fast CPU I found SLI scales very well.

I also really like working with the P4 platform instead of late Socket 370 stuff. They P4 systems are more stable, easier to work with and you can scale past 1.4 GHz.

Even going from 2.4 to 3.2 GHz you can squeeze out more fps with a Voodoo 2 SLI setup.

P4 systems are also much cheaper and easier to find, support SATA and have CPUs as slow as 1.4 GHz available. I will do a lot more testing with P4 gear and more videos. Basically "promoting" it more. I see a lot of money getting pored into Tualatin builds, while the P4 is overlooked...

JoeCorrado wrote:

Davros wrote:

JoeCorrado wrote:

Kind of cheating with the ti4200 but it supports glide quite well and the Voodoo 2 SLI setup is out of the machine altogether.

What ???

kind of cheating in that I did not resolve the problem- I cheated by side stepping ... adding the ti-4200 and removing the V2 SLI setup entirely. After 2 days of wrestling with the issue.

The way you wrote it, it sounds like you said that the Ti4200 supports Glide without the Voodoo cards being in the system.

Which shouldn't be possible, since Glide is 3dfx's proprietary API.

So you could have meant or be using OpenGL or Direct3D.

Or you could intentionally/unintentionally be using a Glide wrapper.

I have a vague memory of a Voodoo 3-era GeForce card supporting Glide, and investigation showed that its drivers were bundled with a wrapper. Creative Unified, I think.

Can you explain...?

Nah he just gave up on glide and used the Geforce 😀

Mau1wurf1977 wrote:

I also have another tool installed, I believe it's called Voodoo 2 Tweaker. It allows changing the V-Sync settings, which the drivers don't.

This tool just edits FX_GLIDE_SWAPINTERVAL value. All Voodoos are configured through environment variables.

I do not get my Voodoo1 or Voodoo2 working on my P4 (D1321 I845) 🙁
I only get some green lines nothing more 🙁

I believe a P4 fried my previous one. It did work for a while however (and was noticably as slow as a Rage128)

I'm not a fan of the FastV2 drivers.

I use Win2k and the latest official-driver and the FastV2-driver do not work.
It must have been something with the Chipset or the Board, but I don't know for sure.
The Voodoo-Control-Panel is visable and functional (but I see only glide, no opengl/d3d)
"dxdiag" does not find the voodoo, it shows only the NV6200-agp.

OpenGL on a Voodoo2 is really an ICD to passthrough to Glide3x (which will work). There is no Direct3D support in V2 2k drivers and thus it will not show up as a DirectX display device. This is completely normal (more due to win2k's architectural changes to the driver model and how it treated secondary display devices)

If you want a Direct3D Voodoo on Win2k you'll have to go one model up at the least (Voodoo Banshee)