V4500 Tools and Wierd Reg Error ???

To anyone who can help;

I have a Voodoo4 4500 - AGP, version 1.04.00 of the Win2k drivers, all of which worked perfect on Whistler 2296.1, but now build 2410 is giving me one hell of a time getting the 3D working !! I have tried all possible solutions, even the one posted on this WebSite, I follow the steps but when I go to install the 3DFx Tools, I am getting the following error, even in SafeMode;

Error 1904.Module C:\Program Files\3dfx Interactive\3dfx Tools\AdvTweak.dll failed to register.
HRESULT - 2147418113. Contact your support personnel.

Anyone else run into this error ? If so how do I get around this ? I am so disappointed that all was so good in the land of Beta, then the evil emporer arrived Help !!

------------------
=======================
Relic2K
Ottawa, Ontario, Canada
relic2k@ottawa.com
=======================

let's try this..

download latest beta v3 drivers then extract to a directory and DO NOT RUN SETUP.EXE then copy all .dll files in there except 3dfxvs.dll into your windows/system32 directory then load up regedit and in HKEY_LOCAL_MACHINE/software/microsoft/windowsnt/currentversion/opengldrivers add a new key called 3dfx and in there make a string call DLL and put the text "3dfxogl.dll" without quotations, then a DWORD with DriverVersion as 1 , a DWORD with Flags

V3 drivers ? I have a Voodoo4 4500 - AGP, this is kind of a step backwards isn't it ?

Still no luck. I am Win2k now, going to have a look at how the registry is laid out for the video card see what the hell is going on.

it's not backwards, just replace everyone sign of v3 with v4

Read the 3dfx FAQ page http://www.ntcompatible.com/3dfxfaq.shtml

Been there...done that. hehehehehe sorry but now you know how I feel, maybe I just have a bad copy of 2410, I am waiting for 2416 now, and I am praying to the Beta Gods that this problem will be fixed again. It was working fine in build 2296.1

------------------
=======================
Relic2K
Ottawa, Ontario, Canada
relic2k@ottawa.com
=======================

hmmm, fix worked here with v3 and v4 video cards...oh well, guess you'll really have to wait, hehe