|  |  |
Tips & Resources for 3dfx Owners
Original 3dfx and 3rd Party Post 3dfx Drivers and Tweaks:
These are the Original Official as well as
various 3rd party drivers that try to help with the new operating
systems(XP/2000) and DirectX 8 versions can be found here.
3dfx Voodoo Card Tweaks and Tools.
- Various Utilities, Tools and Overclockers can be found here.
3dfx Voodoo Card Wrappers.
- Various wrappers for 3dfx cards can be found here.
Origninal Voodoo5 FAQ by 3dfx
- Various information about the Voodoo5 Card.
Origninal Word Documents and FAQ Release notes from 3dfx
Links to Message Boards.
Links to Tweak Guides and other 3dfx Resources.
Other Resources
Notes, Reviews, and Articles from reviews, emails, comments, and the VoodooBoard
- Voodoo2 and Windows NT/2000/XP Glide drivers by: James McLellan
Hello, As you may know
Voodoo2s only have refrance drivers in Windows NT/2000/XP which some games
cannot use (or to be more correct find). Games which usally work with Glide in
ME and 98 don't in Windows NT/2000/XP. This problem is caused by where Windows
places the drivers (Windows NT/2000/XP has a different foldering system for
drivers). Voodoo drivers are now placed in Windows System32 folder where in
Windows 9x they are placed in Windows System. So to get glide working in Windows
NT/2000/XP simply unpack your drivers and copy the glide drivers and place them
into your Windos System folder (you do run a risk by doing this). This will
allow some games to work under Glide. ...
I have not tested this theory but its worth a shot(VF)
- Possible Answers By: WorLord for WorLord V5500 XP AGR Drivers
Firstly, I'd like to thank all the people who have given me words of praise here -
I'm glad an old hack like me could make your XP / V5 5500 gaming experience a
little more workable. And, again, I'd like to mention that Cairey and Hujer_HoE
did the real work - I just lumped it together and crossed my fingers. ;-)
Now, on to the people still having the "BSOD / Reboot after Glide app exits" bug.
At least one of you has an Athlon system, and I think the other might as well.
Here are a few tips I can give, based on web docs and my own experience, to possibly help you guys.
People with VIA boards:
- DON'T install the 4-in-1 drivers if you're using XP.
The drivers that came with XP have proven to be more stable for me over two different
machines then the VIA-supplied ones if you must try the VIA stuff, avoid the IDE driver like the plague.
- Avoid Crative Labs soundcards.
They gave my machine gas and I had less stress just going out and buying a Hercules or
Turtle Beach card then trying to fix all the IRQ and sound issues (including BlueScreens)
associated with my Creative card.
- Read the "A7V Tome of Knowledge" (http://usit.shef.ac.uk/~aca00lad/).
Even if you don't own an Asus board, most of the BIOS tweaks / OS Install Fixes apply.
SiS People:
- DO install the new SiS drivers available on your mobo manufacturer's web site.
This fixed some random and game related BlueScreens for me on my one SiS-based Athlon system.
The BIOS fixes in the A7V tome also apply here.
All People with Athlons:
- Install the "AMD LargePageFile" fix. Really. This, by itself, will probably fix the problem.
http://www2.amd.com/us-en/Processors/ProductInformation/0,,30_118_756_759%5e871%5e2367,00.html.
- While we're on the topic of AGP bugs, PLEASE change the BIOS setting from AGP 4X to anything else (I use 2X).
4X doesn't visibly improve anything for me, but gosh, it sure does give any Athlon system I have serious gas.
- For the love of tapioca, don't let WinXP operate your computer as an "Advanced Power and Configuration Interface (APCI) PC".
This really creates some bad IRQ juju (as in, everything lists as IRQ 10 or 11
- which is what your AGP video card should be, usually).
If you didn't actively work to change this when you installed XP,
then you can change it by going into Device Manager, expanding the "Computer" entry,
selecting the "Advanced Power and Configuration Interface (APCI) PC" entry and updating the drivers.
Choose "Standard PC." I can't stress this enough; it's an important tweak that makes things much more
stable across the board, even on non-Athlon systems.
That's about all the important tweaks/fixes I can think of.
I've applied all of these to seven or eight different Athlon systems that were getting
BlueScreens either when entering/exiting games or just at random, and they've since been rock solid.
Let me know how things turn out for you guys.
--WorLord
There is a topic on the VoodooBoard with help on getting different games to run with these drivers as well, the link:
http://www.voodoofiles.com/forum/thread.asp?id=1305
- FIXING THE XP REBOOTING PROBLEM By: SSJ4Vegetasan for Hujer_HoE 3dfx Voodoo3/4/5 WinXP Drivers
Nice drivers...All you ppl that claim windows xp reboots when you
try to run certain games...there is an explanaition. By default, windows is set
up to reboot on errors...errors that may not necessarily be fatal. what you need
to do is right click on my computer, go to the startup and recovery tab (i
think) and UNCHECK reboot on error! your problem will be solved! have fun!!!!
- FIXING INSTALL PROBLEM By: ComradeF for Hujer_HoE 3dfx Voodoo3/4/5 WinXP Drivers
These are GREAT! Thank you VERY MUCH, keep up the excellent work!
Ah, and try to VisualReality for those of us with Voodoo3 3500 TV''s... :) For
those of you wondering about all the errors and junk that pop up when you
install it, I don''t know if this was posted anywhere else yet, but I figure
what the hell, I''ll just type it... Run setup.exe. Skip through all the errors,
ignoring, overwriting, etc... Reboot. Run setup.exe again, and this time click
Repair installation. It''ll install flawlessly. Reboot. TADA!
-
GHOST RECON WITH VOODOO3 (found this on a message board, its worth a shot...)
How did it work:
Well it was just the matter of reaching for the last possibility available. I had already tried everything else.
I remembered that I installed a third party drivers for my Voodoo3 3000 AGP-card and what I did was I went to http://www.voodoofiles.com/3201 and downloaded the file v3-w9x-1.07.00.zip.
Then I extracted and installed the 3dfx Tools (I didn't even remove the existing 3dfx Tools I had) and BOOM! It worked.
I played it safe and started with a miminum settings (640x400 16bit and all settings low and started going up ending with 800x600 and all settings high and it still kept on working...it was almost better than sex!!!)
So if any of you Voodoo3 owners still have any kind of third party drivers installed on your machine, forget them and download the official one from the url above. It supports DirectX 8 so that is not an issue either.
- RETURN TO CASTLE WOLFENSTEIN
There are a lot of people who have had trouble playing some 3D games on
Windows XP because the 3Dfx OPENGL is not compliant. I learned the hard
way when I tried to play the game RETURN TO CASTLE WOLFENSTEIN and it
wouldn't work. I was pretty upset because I spent almost $60.00 on the
thing. However I did discover a site where someone hacked into the OPENGL
files and now 3Dfx on Windows XP works. Here is the link with the
instructions on how to accomplish the tasks.
Go to Ansible Homepage for Instructions.
More of these to come....
|
 |  |
|
|
.
