Windows200 FAQ for new Retail 3Dfx drivers
This is a discussion about Windows200 FAQ for new Retail 3Dfx drivers in the Windows Hardware category; 1: You must have Evaluation 2195 or Retail 2195 for the drivers to install. 2: The new Retail drivers are newer then the Beta. Retail drivers 3dfxOGL. dll 1. 0. 0. 514 3DfxSpl2. dll 1. 0. 0. 4 3DfxSpl3.
1: You must have Evaluation 2195 or Retail 2195 for the drivers to install.
2: The new Retail drivers are newer then the Beta.
----Retail drivers----
3dfxOGL.dll 1.0.0.514
3DfxSpl2.dll 1.0.0.4
3DfxSpl3.dll 1.0.0.4
3dfxvs.dll 5.0.2195.17
3dfxvsm.sys 5.0.2195.17
glide2x.dll 2.60.0.523
glide3x.dll 3.10.0.523
----------------------
-----Beta drivers-----
3dfxOGL.dll 1.0.0.513
3DfxSpl2.dll 1.0.0.4
3DfxSpl3.dll 1.0.0.4
3dfxvs.dll 5.0.2195.9
3dfxvsm.sys 5.0.2195.9
glide2x.dll 2.60.0.522
glide3x.dll 3.10.0.522
----------------------
3: You may need this.
Uninstall instructions for all Beta & Retail 3Dfx drivers. http://ntgamepalace.3dfiles.com/3dfxfaq.htm
4: Don't exstect every games to run some will need a PATCH.
5:
Q: Why dose 3dfx Tools not install nor by runing setup.exe.
A: You need do follow frist
"Update the drivers"
or
"Driver Installation"
make sure you are you desktop is set 16bit color after that, then you can
install the 3dfx Tools
-------------------------------------------Driver Installation from the
readme.txt
-------------------------------------------
1) Open Control Panel; then open the System applet.
2) Click the "Hardware" tab, then click "Device Manager".
3) Expand "Display Adapters", right click on "Voodoo3" or "Voodoo Series..."
then click "Properties".
4) Click the "Driver" tab then click "Update Driver".
5) When the Upgrade Device Driver Wizard initially appears, click "Next".
6) In the Upgrade Device Driver Wizard, select the "Display a list..."
option then click "Next".
7) Click "Have Disk" then enter the path to where you extracted the driver
files. Click "Next".
8) When asked to choose a device, select "Voodoo Series Driver" Click
"Next".
9) Windows 2000 will copy the drivers.
10) When prompted, restart your computer.
6: Don't worry about WHQL Certification
2: The new Retail drivers are newer then the Beta.
----Retail drivers----
3dfxOGL.dll 1.0.0.514
3DfxSpl2.dll 1.0.0.4
3DfxSpl3.dll 1.0.0.4
3dfxvs.dll 5.0.2195.17
3dfxvsm.sys 5.0.2195.17
glide2x.dll 2.60.0.523
glide3x.dll 3.10.0.523
----------------------
-----Beta drivers-----
3dfxOGL.dll 1.0.0.513
3DfxSpl2.dll 1.0.0.4
3DfxSpl3.dll 1.0.0.4
3dfxvs.dll 5.0.2195.9
3dfxvsm.sys 5.0.2195.9
glide2x.dll 2.60.0.522
glide3x.dll 3.10.0.522
----------------------
3: You may need this.
Uninstall instructions for all Beta & Retail 3Dfx drivers. http://ntgamepalace.3dfiles.com/3dfxfaq.htm
4: Don't exstect every games to run some will need a PATCH.
5:
Q: Why dose 3dfx Tools not install nor by runing setup.exe.
A: You need do follow frist
"Update the drivers"
or
"Driver Installation"
make sure you are you desktop is set 16bit color after that, then you can
install the 3dfx Tools
-------------------------------------------Driver Installation from the
readme.txt
-------------------------------------------
1) Open Control Panel; then open the System applet.
2) Click the "Hardware" tab, then click "Device Manager".
3) Expand "Display Adapters", right click on "Voodoo3" or "Voodoo Series..."
then click "Properties".
4) Click the "Driver" tab then click "Update Driver".
5) When the Upgrade Device Driver Wizard initially appears, click "Next".
6) In the Upgrade Device Driver Wizard, select the "Display a list..."
option then click "Next".
7) Click "Have Disk" then enter the path to where you extracted the driver
files. Click "Next".
8) When asked to choose a device, select "Voodoo Series Driver" Click
"Next".
9) Windows 2000 will copy the drivers.
10) When prompted, restart your computer.
6: Don't worry about WHQL Certification
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Feb 18
Feb 19
0
5 minutes
Responses to this topic
None the less they arent any different. I just did a size comparison. All files but 2 were the exact same size in bytes.
3dfxOgl
3dfxSpl2
3dfxSpl3
3dfxvs
glide2x
the 2 files that were changed
3dfxvsm
glide3x
were only off by like 300 bytes or something.
Point is they are basically the betas. Maybe minor modification. Your not going to see any different results then they beta though. Why did they say they had to wait for certification I wonder? Do you think that they probobly just released they betas to keep 3dfx customers happy and are still waiting for WHQL?
3dfxOgl
3dfxSpl2
3dfxSpl3
3dfxvs
glide2x
the 2 files that were changed
3dfxvsm
glide3x
were only off by like 300 bytes or something.
Point is they are basically the betas. Maybe minor modification. Your not going to see any different results then they beta though. Why did they say they had to wait for certification I wonder? Do you think that they probobly just released they betas to keep 3dfx customers happy and are still waiting for WHQL?
OP
Jonny just because you don't see a diff that don't mean any thing I see drivers change just changeing the code with change the size of it.
Thats rediculous! Your telling me that when you change code the byte size stays exactly the same? Im sorry man but I may not be that smart but I used program code in assembler. 1 byte is very small. If you change 1 line of code your going change in bytes. forget that if you change 1 machine instruction your going to get a change in bytes.
When I say exactly the same I dont me roughly the same. I mean the EXACT same size in bytes. The odds of changing a .dll or .sys file and getting the exact same size in bytes is high. I dont know how high but I imagine its way up there. Somebody tell me Im wrong.
OP
Yes in most case it go up or down in size
here a SAMPLES code change with out a size change
old code
PatBlt(hMemoryDC, 0, 0, 64, 16, BLACKNESS);
new code
PatBlt(hMemoryDC, 0, 0, 64, 24, BLACKNESS);
here a SAMPLES code change with out a size change
old code
PatBlt(hMemoryDC, 0, 0, 64, 16, BLACKNESS);
new code
PatBlt(hMemoryDC, 0, 0, 64, 24, BLACKNESS);
The only conern is that you must be downloading from their offical server, 3dfxgamers, so that security issue is not paramount with regard to digisign unaccompliashment.
This is really a rush release, even the included 1.1 OpenGL ICD is a beta version called retail.
This is really a rush release, even the included 1.1 OpenGL ICD is a beta version called retail.
jonny - use FC from the command line - it does a binary file compare....
Yes, different versions of a file can be the same size...
Yes, different versions of a file can be the same size...
I understand that. Im happy with the drivers. ( sortof I was hoping for some bad ass ones better then the betas I was using. =P ) I dont care though because they work. Fine. I guess I should keep my mouth shut. But I cant help analyzing the fact that they told everybody that they were waiting because they couldnt post them unless ms whql certifies them. Then they post them today uncertified. So who knows maybe they are still waiting on ms and decided to post some to be cool. And I stand corrected about the files not being different. In fact they were very different. Thx yuppiescum. Sorry SHS.
