VOGONS


First post, by auron

User metadata
Rank Oldbie
Rank
Oldbie

when trying to run PCP D3D bench 2.10 (diamond 1.10 driver from 1998), it would complain about needing directx5 when selecting the voodoo in the dropdown menu. after updating to dx5, IIRC the voodoo option disappeared and the benchmark will only run on the matrox millennium. in fact, this is also mentioned in the driver readme. on falconfly i'm seeing a "Tweek for Voodoo!" tool apparently claiming to be able to switch the card used for D3D. is this the only method to do this or did the 3dfx reference driver address this issue?

Reply 2 of 4, by auron

User metadata
Rank Oldbie
Rank
Oldbie

yes, totally forgot about that one. it doesn't work though with the monster 3d and 1.10 diamond driver, whether i select secondary or primary, or reboot after selecting, D3D always runs on the matrox card. need to test some different drivers later.

Reply 3 of 4, by auron

User metadata
Rank Oldbie
Rank
Oldbie

it's indeed a problem with the diamond driver, as after updating to the 2.16 reference driver, the 3dfx card will show as a dx5 directdraw device when secondary device is selected in 3DCC. updating under win95 was a bit of a hassle though as the diamond installer gave it a 2025 date, so windows would ignore any attempts to install another driver. deleting the .inf in the windows folder fixed that.

Reply 4 of 4, by auron

User metadata
Rank Oldbie
Rank
Oldbie

i've had more trouble with this, when swapping between the diamond 1.10 and 2.16 reference driver, even though i was on the latter one, D3D would not work, evidently because of driver remnants from a standard deinstall method. the reference driver itself leaves its control tab as a remnant when normally uninstalling the card.

i was never able to get driver cleaner pro 1.5 (same with 1.2 too) to work under windows 95 to this day due to oleaut32.dll issues, the standard file in osr2 is outdated for it and any other i tried is too new, so i got the 3dfx uninstaller tool from 2000, which can be obtained on falconfly. this would recognize a voodoo graphics but prompted me to uninstall a 3500TV, which did nothing. however the tool also updates certain system files and lo and behold, this is the oleaut32.dll that works under 95 osr2. so that uninstaller is the best way to obtain that .dll, which probably comes in handy with some other software as well. after a DCpro run everything works as expected, so this is a must along with a manual .inf delete from the windows/inf/other folder, so it won't prompt to install a previous driver upon boot.

edit: DCOM95 1.3 (download) updates that file to a slightly older version than the 3dfx uninstaller, but still new enough to make DCpro 1.5 work.