3DFX and 2428

[Malkosha 0]

I had some problems with 2419 and my Voodoo3 AGP card on my K62 system. When I installed the drivers it would reboot into a 4bit screen and I had to rollback (great feature BTW). I assume that it has to do with the MB chipset (VIA) in combo with the OS and 3DFX card. I also noticed that many others had this problem. Oh well thats what Beta's are about.

 

Has anyone had any problems like this with build 2428? Are the drivers more complete and functional than in previous builds? Any problems installing the Win2K drivers? While I'm aware that while 3DFX (nvidia now) is responcible for the drivers, the built in drivers should at least be able to perform some basic functions. If not then perhaps MS shouldn't include them at all. I think its to easy sometimes to blame the card companys for driver problems when in fact if the OS's where designed with driver compat in mind it would save everyone alot of work and headache. Then again, if everything worked great all the time I would be out of a job

[jdulmage 0]

funny thing is, I think that's only a prob with certain chipsets, because my friend and my cousin both have the voodoo 3 2000 and 3000 respectively and no problems running it since 2419

[Malkosha 0]

I agree, are they using intel chipsets? AGP or PCI? I wonder if its possible that the API calls in XP are slightly different than Win2k. Perhaps enough to cause certain combos like VIA chipsets and 3dfx chipsets to blow up with certain driver versions. I've seen the same "side effects" with certain software titles that don't play well together.

[SHS 0]

Malkosha what drv set are you useing ??

[Malkosha 0]

The latest and greatest ... I belive Win2k 1.04.00 and tools.

[SHS 0]

I hope you did try install 3dfx Tools if yes that the problem.

[Malkosha 0]

I thought of that to friend. Since you need to reboot after the driver change, and before the tool install just the drivers caused this problem. An earlier driver version maybe?

[SHS 0]

send me email bud

[Yearout 0]

I'm not sure if your are saying you can't get it to work but if you install the reg 3dfx 1.04 drivers or something like that, whistler will be in 4bit then install whistlers 3dfx drivers. Now go in dos or other OS and copy the files from driver2k(dll) but not 3DFXVSM.sys. I have 3dfx 3000pci on the other computer. So let me know. It works fine ,opengl , and glide.

[Malkosha 0]

First of all thx to everyone for their help. I finaly got it working with the exception of the tools. This is what I did:

 

I ran the driver update and installed the latest version of the Voodoo3 drivers. When I rebooted, it put me in 4 bit color mode. I rolled back the drivers and after that it worked fine. Q3 ran great as did my D3D apps. I didn't test any glide apps yet. More than likely, it always worked when I rolled back the drivers but I assumed (ya we know what that means) that since the drivers didn't work the roll-back returned my system to its default mode. This may be a false assumption. There seems to be new reg entries esp concerning the openGL drivers. It seems from this uncontroled test that the roll-back didn't competly revert the reg settings. Its almost like the roll-back only involved the entries/drivers that the original driver set "knew" about and ignored any setting that where not contained in the original inf/pnf. I'm going to try to re-install the OS again for a freah start and compare the 2 reg's for any chages during this proccess and make a more accurate recording of what happens. This is all speculation of course since I didn't document this proccess. Once again, thx for the help and ideas.