problem with voodoo 2 in VIA M/B

[McLaren]

I just purchased a new PC with the following specs

p3 733, ASUS geforce video, 128 RAM (133), Gigabyte 6vxe7+VIA M/B & win98. It seems to run fine until I try to install my old Creative Voodoo 2 card. The system then does the strangest lockup.

When it starts I can not open the start menu, and I cannot right click the mouse on the desktop to bring up screen properties. The system just hangs. I can however get into the control panel from "my computer", the device manager shows no conflicts, but all I can do is reset the computer by control-alt-del (because I cannot access the start menu to select shut down).

Some people have indicated it could be a problem with the VIA chipset motherboard. Anyone else heard of similar problems, or can you offer a suggestion.

Thanks

 

[ironwoode]

I doubt its a via problem. I have used via boards for a long time and never had that problem. The Voodoo2 is an add on PCI card with a pass thru cable. Plug the card in and windows may or may not recognize it. But if you have a Gforce card why the V2? Have you installed the V2 drivers? Is that when the computer goes nuts? Could be conflict between Asus and V2 drivers. I used a monster 3D (voodoo1) a while ago with no problems under win98 on a via board.

Maybe try 3dfx V2 drivers as opposed to Creative`s.

Thats the best i can do.

 

[birddog]

I've had no problems with a V2 I set up on a friends Tyan trinity mobo. Try the reference drivers for the V2. There is a possibility that your pass-through cable is bad. Try plugging the monitor into the regurlar video card (leave the v2 in the computer, just take off the pass-through cable). If it works OK after that, try a new pass thorugh cable. There will be no IRQ coflicts since the V2 does not use one.

 

[ogn]

You are getting registry corruption. The voodoo2 control panel tab is what's messing it up. I don't know what the exact fix for it is. I was able to remove all the registry settings involved with voodoo2, then reinstall the card, but eventually it came back. Yes it is VIA related. It doesn't happen to all boards. I've had it happen on Asus P3V4X and Epox 37VCA (I think that the name of it).