//flex table opened by JP

Click to See Complete Forum and Search --> : help with voodoo 2!!


stubbs
03-12-2000, 06:24 PM
Hello, I have a problem with the install of the monster 3d II. I have installed it exactly according to instructions. I have used only the latest 3dfx voodooII drivers for win98. version 3.02.02.
I installed everything correctly. Then when I did final reboot I get this message error box:
"GlideInitEnvironment:glide2x.dll expected voodoo^2, none detected"
This error box occurs on every bootup.
The voodooII accelerator is listed correctly in the device manager.
There is no second display listing in the direct X diagnostic tool, only my primary display adapter is listed,and I have the latest
directX version from the windowsupdate site already.
When I go to the display properties there is a tab called voodoo, and when I select that tab, I get a freezeup, and I have to
end task on the display properties to leave it. I am able to access all the other display tabs correctly, and my primary video
adapter is functioning correctly.
Does anyone have an answer?
I am about to sell two monster 3dII 12 meg as a pair for SLI if I can't get these drivers to work.
Help. Pulling out my hair.

bogie23
03-14-2000, 03:11 AM
delete all driver that has 3dfx and fxmemmap/vxd in c\windows\system. then delete inf diamond in c\windows\inf\other and any about 3dfx. right click on files and choose properties if diamond or 3dfx delete it. then restart comp install drivers.

Missing the point
03-14-2000, 07:10 AM
Thats wierd..... I just sold my Diamond Monster 3D II, and I never had any problems.. That was a really great card though, and I would recommend you try to get it to work, because you'll be glad you did!

stubbs
03-14-2000, 06:05 PM
Hi all! I have good news, I phoned Diamond, and also tried a last ditch thing right before I phoned them. What I did was to install the other matching mate to my voodooII card in the place of the one with the problem. On boot up, voila! it worked fine! with the newest 3dfx drivers! When I phoned Diamond, they said that the error I was getting probably meant a dead card, so I got an RMA and will be sending the dud back. Now I am running its mate solo, awaiting SLI....when the card returns from Diamond. Oh, note, Diamond does recommend the latest 3dfx drivers for the monster3dII card.