Voodoo2 installation issues \ VOGONS

Voodoo2 installation issues

Topic actions

Post a reply

First post, by Aublak

Posted on 2020-07-08, 23:08

Aublak Offline

Rank Member

Rank: Member
Posts: 158
Joined: 2020-05-24, 00:07
Location: Ohio, USA

Hello everybody. New guy here.

I think Vogons is pretty great. I really like browsing the forums and seeing all of the interesting hardware for people to show off. I heard a lot about this place through Phil's Computer Lab.

Anyways, I bought a Diamond Monster II 8mb (first working Voodoo card) and everything seems fine with it at visual inspection. I'm using a passthrough cable with my Geforce3 ti200. I installed the official Diamond drivers. Restarted the computer. The Voodoo2 is detected in Device Manager. Fantastic. But it seeming it doesn't work beyond being detected. If I attempt to play Half-Life through the 3DFX mini driver, it just hangs there on a loading screen. Card doesn't seem to get hot at all.

If I go to Properties, I get an error saying 'Diamond Monster 3D II not found. Contact Diamond Technical Support.' Then another error saying 'cocreate instance failed' 'class not registered'.

I dunno. I never had an accelerator card before. Am I doing something wrong or is the card kaput?

Reply 1 of 6, by wirerogue

Posted on 2020-07-08, 23:29

wirerogue Offline

Rank Member

Rank: Member
Posts: 312
Joined: 2019-02-24, 01:24
Location: Southern California

try checking the box "disable voodoo2 direct 3d support" in your voodoo2 display properties, so the cards don't interfere with each other in D3D.

Filename

v2.properties.gif

File size

10.48 KiB

Views

691 views

File license

Fair use/fair dealing exception

Reply 2 of 6, by Aublak

Posted on 2020-07-09, 23:08

Aublak Offline

Rank Member

Rank: Member
Posts: 158
Joined: 2020-05-24, 00:07
Location: Ohio, USA

wirerogue wrote on 2020-07-08, 23:29:

try checking the box "disable voodoo2 direct 3d support" in your voodoo2 display properties, so the cards don't interfere with each other in D3D.
v2.properties.gif

Oh, thanks. I'll give it a shot. But now I have more questions.

It seems like I found another problem. Some components are missing here on C53. What are these? Diodes? I have recently been soldering capacitors back on so I might be able to fix it.

I also have a pair of broken Creative Labs V2 I could potentially cannibalize. One has broken PCB "connectors" and the other one has broken connectors on one of the main chips. I don't think either of these are salvageable, right? I can at least steal some of the ram chips to upgrade my 8mb Monster to a 12mb Monster, right? There's no penalty to mixing ram chips. I believe they all work the same way.

Attachments

Filename

IMG_20200709_073359.jpg

File size

1.26 MiB

Views

663 views

File license

Public domain
Filename

IMG_20200709_073323.jpg

File size

1.39 MiB

Views

663 views

File license

Public domain
Filename

IMG_20200709_073226.jpg

File size

1.29 MiB

Views

663 views

File license

Public domain

Reply 3 of 6, by Gamecollector

Posted on 2020-07-12, 08:00

Gamecollector Offline

Rank Oldbie

Rank: Oldbie
Posts: 1413
Joined: 2010-10-06, 22:17
Location: RU

1) HL and HL engine games freeze on the loading screen if a game was started from the autorun.
2) Use something simple to test the glide API. Tech demos as the example.

Asus P4P800 SE/Pentium4 3.2E/2 Gb DDR400B,
Radeon HD3850 Agp (Sapphire), Catalyst 14.4 (XpProSp3).
Voodoo2 12 MB SLI, Win2k drivers 1.02.00 (XpProSp3).

Reply 4 of 6, by Aublak

Posted on 2020-08-03, 00:45

Aublak Offline

Rank Member

Rank: Member
Posts: 158
Joined: 2020-05-24, 00:07
Location: Ohio, USA

wirerogue wrote on 2020-07-08, 23:29:

try checking the box "disable voodoo2 direct 3d support" in your voodoo2 display properties, so the cards don't interfere with each other in D3D.
v2.properties.gif

Alright. I got her working now. This is very cool. 😀

Which drivers are you using, Wirerogue? I'm not seeing the option to disable D3D. I believe I'm using the latest reference driver.

Attachments

Filename

Voodoo2 advanced settings.jpg

File size

44.92 KiB

Views

554 views

File license

CC-BY-4.0

Reply 5 of 6, by wirerogue

Posted on 2020-08-03, 15:03

wirerogue Offline

Rank Member

Rank: Member
Posts: 312
Joined: 2019-02-24, 01:24
Location: Southern California

Aublak wrote on 2020-08-03, 00:45:

wirerogue wrote on 2020-07-08, 23:29:

try checking the box "disable voodoo2 direct 3d support" in your voodoo2 display properties, so the cards don't interfere with each other in D3D.
v2.properties.gif

Alright. I got her working now. This is very cool. 😀

Which drivers are you using, Wirerogue? I'm not seeing the option to disable D3D. I believe I'm using the latest reference driver.

those were the monster 3d drivers.
you can accomplish the same thing with powerstrip if your voodoo drivers dont' have that option.

Reply 6 of 6, by Aublak

Posted on 2020-08-10, 19:45

Aublak Offline

Rank Member

Rank: Member
Posts: 158
Joined: 2020-05-24, 00:07
Location: Ohio, USA

wirerogue wrote on 2020-08-03, 15:03:

Aublak wrote on 2020-08-03, 00:45:

wirerogue wrote on 2020-07-08, 23:29:

try checking the box "disable voodoo2 direct 3d support" in your voodoo2 display properties, so the cards don't interfere with each other in D3D.
v2.properties.gif

Alright. I got her working now. This is very cool. 😀

Which drivers are you using, Wirerogue? I'm not seeing the option to disable D3D. I believe I'm using the latest reference driver.

those were the monster 3d drivers.
you can accomplish the same thing with powerstrip if your voodoo drivers dont' have that option.

very cool. I didn't even know about Powerstrip. This little program is a gamechanger.

the popups are annoying though.

Go to top of page Go to top of page

Back to General Old Hardware

Main menu

Common searches