Hi guys,
I'm dropping off a new V2 (and Obsidian2) Glide driver kit for those who still keep the good 'ol 3dfx V2 hardware for occasional spins of their favorite glide2x,3x apps. The kit includes bleeding edge builds of 3dfx glide2x,3x drivers from http://glide.sourceforge.net/ and new win2k/xp/vista 32bit miniport drivers.
glide2x.dll 2.57.0.6528
glide3x.dll 3.4.0.6528
fxgpio.sys, fxptl.sys 4.3.0.1105
The glide driver uses 3dnow! and mmx optimizations. The miniport includes memmap fixes. Besure to read the readme.txt first. You have been warned.
Win2k/XP/VISTA 32bit: If the OS doesn't ask for a driver, install the drivers from the device manager.
Win9x/ME: Install the reference 3dfx V2 driver, then copy glide2x.dll and glide3x.dll to c:\windows\system.
For OpenGL, get Mesa for 3dfx Glide or Metabyte WickedGL or 3dfx MiniGL.
If you post feedbacks, remember to include a description of your pc setup, OS, app version, if the app uses glide2 or glide3, etc. And don't forget to thank the developers over at sourceforge.
Notes:
* Removed dirty hacks from the windows miniport driver. Fixes potential system hangs on modern systems.
* The driver inf will set SSTV2_RGAMMA, SSTV2_GGAMMA, SSTV2_BGAMMA to 1.00
* Added grStippleMode and grStipplePattern. Using Glide64, Mario will now do his dissolve trick properly.
* Includes fixes for memmap errors and desktop corruptions.
* Optimized for 3dnow! and mmx.
* FX_GLIDE_SWAPINTERVAL = 0 will force VSYNC off. V2 SLI may have problems syncing the scanlines when VSYNC is off.
* Alphablending dither subtraction is disabled by default. Set SSTH3_ALPHADITHERMODE = 3 to enable dither subtraction.
* 4x4 dither matrics is used when alphablending dither subtraction is enabled. Other wise it's always 2x2.
* Set SSTV2_MISMATCHED_SLI = 1 for mismatched SLI support. This may not work due to differences in V2 board design. If you have problems try swapping the PCI slot order of the V2 boards.
* If the screen goes blank but you still hear the application running in the background, reconnect your display and pass-through cable to the second V2 or set SSTV2_SWAPBOARDS = 1
* Win9x/ME: copy glide2x.dll and glide3x.dll to c:\windows\system
* Quantum3D Obsidian2 X-24, X-16, and similar SLI boards must have
the following set.
SSTV2_FT_CLKDEL = 5
SSTV2_TF0_CLKDEL = 7
SSTV2_TF1_CLKDEL = 7
SSTV2_TF2_CLKDEL = 7
SSTV2_SLIM_VIN_CLKDEL = 3
SSTV2_SLIM_VOUT_CLKDEL = 2
SSTV2_SLIS_VIN_CLKDEL = 3
SSTV2_SLIS_VOUT_CLKDEL = 2
SSTV2_GRXCLK = 90
-KoolSmoky
Download Attachment: (https://www.3dfxzone.it/enboard/images/icon_paperclip.gif) Voodoo2.zip (https://www.3dfxzone.it/public/uploaded/koolsmoky/201022018831_voodoo2.zip)
446 KB
KoolSmokey,
Good to see you are still around and working hard for all of us. Thank you for your hard work and time.
These are Voodoo2 drivers that work under WinXP?
If so will SLI work correctly?
Right now I have a dual boot and I'm running my 24Mb Voodoo2 SLI setup under Win98se. It would be great if I could totally get away from Win9x.
QuoteOriginally posted by ArchAngelCD
These are Voodoo2 drivers that work under WinXP?
If so will SLI work correctly?
Yep, they should work. Infact, I'm using them under WinXP. :D
KoolSmoky
Outstanding.... I'll give them a try ASAP and let you know how they work on my system. Thanks again...
I will test the driver ASAP.
I'm really happy there is a new release,this driver simply rules.fast,compatible,and almost no errors.only had problems with diablo2 rebooting my pc from time to time (the event viewer wrote this:
"The Voodoo2 Board Remapper service failed to start due to the following error:
The system cannot find the file specified."),the problem seemed to disappear when I loaded the original 3dfx memory mapper.
I wonder if the new version fixes it.anyway,you own.
my specs: athlonxp 3000/radeon9800p/512MB Ram/A-Trend Voodoo2 12MB matched SLI,running xp pro (and win98se;))
ok,gave a it a quick fly,this is what I got:
-the driver works fine.no random errors,etc.
-hitman1 (a glide3x game) finally runs with the beta glide3x (ver 3.3.0.40405).the previous version of beta glide3x (ver 3.3.0.40404) was unable to launch the game,I had to use the original 3dfx glide3x.the game looks damn sweet with the 2x2 dither matrix.
-counters strike (1.5 and 1.6 alike) still have that weird texture flickering problem,right after you join a game (or create a lan server) and you are in the team selection screen,the textures and mouse cursor flash wildly (black,grey,pink or green colour).the problem dissapiers once you enter the game.this is noticable (although hardly noticable I must add) in some other games as well,return to castle wolfenstein and undying for example.all those games use glide2x (natively,or via the wickedgl/minigl miniport).latest original glide2x doesnt have this problem.
I'll see if I can reproduce that diablo2 reboot.
again,awesome work[8D]
edit: any chance I could get the new 3dfx logo spinning when startin a glide app? I like it a lot..
Very fine so far - i noticed a speed improvement in Unreal Tournament (SLI), not saying about an excellent image quality as for a Voodoo2. What about that Diablo 2 issue? I decided to bring that old sleeping monster to live...with an old glide renderer,of course. We'll see. Anyway, great job, Koolsmoky, as always - please keep it that way, and we'll end up porting Half-Life 2 to glide rendering:-D
about diablo2-my system rebooted sometimes,mainly when exiting the game to the main menu (640*480 switches to 800*600),or when alt-tabbing the game,but the reboot was quite rare,say once a day (playing diablo2 for approx. 10 hours).this was with the previous version of koolsmoky's driver (a.k.a. the second release,the new one is third).no reboots so far,but I have to play more to be sure..
Speaking of Diablo 2 again - works 100% perfectly with this "night-build" driver, nice speed (1.02 glide renderer).
3DNow and MMX optimisations hey? Sounds pretty sweet!
So will I notice a difference in frame rate with my setup (see sig)?
Any plans for a DirectX interface?
Cheers,
Chips.
bump for sticky.
Sticky, done
..I still have occasional reboots when exiting games with the new memory mapper.doesnt happen with the old one (from 3dfx)..
Very nice versions of Glide!
They solve a problem that I had with the original 2.56 builds and my Miro Hiscore2 SLI set using Windows 98.
Using the original miro fxoem2x.dll from an older Miro Hiscore 2.54 driver, you could get TV-out to function using the newer drivers.
That even worked in windows 2000.
But there was a problem under windows 9x (strangly no problem in windows 2000) . If you used this fxoem2x with the original 3dfx 2.56 glides, you couldn't change the resolution or restart the game in a different display setting, this would crash the app (with a glide error, I forgot what)
You could try to use the older glide 2.54 versions, TV-out would function perfectly, but they only function if I set my Front side bus to 66 Mhz (PIII on a intel BX mainboard). A higher FSB makes the Voodoo horribly unstable using older glides.
But this new 2.56 Glide build solves my problem!!!
-works just as stable ad the original 2.56 3dfx glides, and the Miro TV-out is functioning perfectly!!! many thanks!!
I do have 1 problem with this new glide 2.56. It doesn't function with the Metabyte Wicked3D stereo wrapper if you set it in "Voodoo2" mode. It only works if it is set to "global 3dfx" modes.
If I play Quake3 using Wicked GL I get:
"Error" "PCI library not open." If the Wicked3d Glide2x stereo wrapper is set to "voodoo2"
Using Voodoo2 mode allows resolution override to strange resolutions like: 640x960 , that works wonderfully in stereo. So I would very much like to have this bug sorted out, so I post it here.
But very nice work!! I'll test it a bit more in the coming days
My system specs:
MSI K8N Neo2 Platinum motherboard
MSI NX6600 Diamond video card
2 x Diamond Monster 3D II 8Mb. each in SLI
AMD Athlon 64bits 3000+
1Gb RAM (2 x 512Mb)
Maxtor SATA II 6V200E0 200Gb HDD
WinFast TV 2000
Samsung CDRW
The driver works fine to me. No problems at all with games. I tested RedLine Racer, Quake and Unreal Tournament. The only bad thing I experienced, is that when I want to do Alt+Tab, they don't swith to the Windows Desktop, and the image freezes. I cannot get back to the game too.
system
athlon xp 3000+
36gig raptor
1gb ram
nforce chip set a7n8x-e deluxe mobo
2 x voodoo 2 sli config
I play alot of diablo 2 lod. I have always heard voodoo ran the game best.
It is true, this driver runs the game great. There are some odd happenings at game load up tho.
3dfx logo displays 3 times in a row at diablo launch
and every time you join a game.
Really odd.
besides that it works great.
Hi, im new in this forum.
here and today i found how to connect voodoo2 in sli(mismatched).1 hour of work with sli cable:)) Koolsmokys drivers work just fine with unreal (1024x768res). But with Ultima 9 its strange: it works, but my monitor view divides in 2 and i see same picture in each:)) what a ****?
One Question,
How do you tweak it since the tweak screen no longer shows up in display properties on the tabs?
I need to limit texture mem to 2 MB for Red Baron 3D.
Thanks
create a txt file in your red baron folder,edit it with notepad and type:
set FX_GLIDE_TMU_MEMSIZE=2
xxx.exe
save and exit (xxx.exe is your red baron executable),rename the file to run.bat and launch it (your system MUST be configured to view file extensions!).thats it..
Ok, should we set FX_GLIDE_NO_DITHER_SUB to 1 or 0 ?
depends,see this:
FX_GLIDE_NO_DITHER_SUB=0
(http://www.3dfx.cz/temp/screenshots/wot_v2sli/fx_glide_no_dither_sub-0.png)
FX_GLIDE_NO_DITHER_SUB=1
(http://www.3dfx.cz/temp/screenshots/wot_v2sli/fx_glide_no_dither_sub-1.png)
some games look better with dither enabled,others do not..this was Wheel of Time (http://forum.3dfx.cz/viewtopic.php?t=514&highlight=fxglidenodithersub) ;)
you should try SSTV2_VIDEO_24BPP=1,it improves the IQ quite a bit,but its not compatible with SLI.
you can try to use koolsmoky's glides (if you aren't running them already),they force a different way of dithering,and some games really like it (quake3 looks particularly good (http://forum.3dfx.cz/viewtopic.php?t=514#5756),especially when combined with SSTV2_VIDEO_24BPP=1)
Thanks for the clarification ps47. I'm already using koolsmoky's glides[8D]. Tried Q3, smoke and blood puffs looking great.
Still like my V3 better though [:(]
new V2 driver kit is up (first post has been edited 3 days ago,I almost didnt notice it).I will give it a spin later this week :D
tried this new driver,at least nfs porsche runs =) single voodoo 2 for now
I removed the old driver, installed the new one and once again - the "mapmem returned an error..." message appeared. I'm testing with the system in my signature. The only thing different is that the CPU is underclocked to 1.53 MHz - 1800+, but this doesn't matter, I guess.
I tried starting some 3dfx demos, NFS, Quake 3 and nothing. I can't get it working.
I was getting the same error with the old version (15.1.2005, I think) and the only sollution I've found was: disable the Radeon from device manager, insert an old S3 Virge DX board, start a glide application, restart, remove the S3 (from the computer), re-enable the Radeon and everything is fine until the next time.
Sometimes it magicaly fixed itself when the PC was restared, but I have no luck with the new driver and since I don't have the S3 anymore, I can't try to trick the PC, unfortunately. [:(]
Will there be a fix for this error anytime soon ?
QuoteOriginally posted by 4eRNoBiL
I removed the old driver, installed the new one and once again - the "mapmem returned an error..." message appeared. I'm testing with the system in my signature.
The Radeon is stepping on the space that the V2 uses. I can provide a fix, but cannot make any promises on a release date. The workaround for Radeon has to be done in the miniport driver. Glide2x.dll and glide3x.dll have nothing to do with this and have no problem.
-KoolSmoky
Well, If you know where the cause of the problem lies, that's perfect - I can wait until it's done. I don't have a choice, do I ? :D
Thanks in advance !
Core2Duo System
E 4300
Gigabyte 965P-DS3
2 Gbyte DDR2-RAM
Creative 3D Blaster Voodoo II SLI
perfect work with win xp
only driver allowing voodoo2 work with this system!
good work!
cu
feinripp
Core2Duo System
E6300
Asus P5B
2 Gb Gskill PC800 PK
Creative 3D Blaster Voodoo II SLI
workgs good in windows xp,till now I played ut and screamer 4x4 only.the iq seams very cool to me..
thanks for this drive
edit: tried nfs porsche..and this driver fixed hte in car "image" he game looks really really cool...thanks one more time!
I gave my new obsidian2 200SBi a quick spin nad the card is running smooth as butter,tested hitman1 (glide3x),incubation (glide2x) and q3 arena (glide2x via wickedgl minigl),everything running fine and looking better than ever (especialy fog in hitman1,yumm) :D
edit: the new memory mapper still causes BSODs from time to time,see attachment.no problem with the original 3dfx memory mapper (not sure about port mapper).
Download Attachment: (https://www.3dfxzone.it/enboard/images/icon_paperclip.gif) dump.zip (https://www.3dfxzone.it/public/uploaded/ps47/20079302130_dump.zip)
227.35 KB
QuoteOriginally posted by ps47
(...)only had problems with diablo2 rebooting my pc from time to time (the event viewer wrote this:
"The Voodoo2 Board Remapper service failed to start due to the following error:
The system cannot find the file specified."),the problem seemed to disappear when I loaded the original 3dfx memory mapper.(...)
Hello ps47, I'm have exactly this same error:
"The Voodoo2 Board Remapper service failed to start due to the following error: The system cannot find the file specified."
--> how to fix it? How to "load the original 3dfx memory mapper"? What is this?
Thanks!
its the fxptl.sys file,use the one from fastvoodoo2 and the problem should be fixed.
Hi. Just dropping off new drivers. Included are support for new glide features and fixes for the memmap errors reported in this thread. Sorry I hadn't released the files more earlier. I simply forgot for quite a long time. :P Anyway, check out the first post for details. I wish you all happy holidays and a prosperous new year.
-KoolSmoky
Koolsmoky,
many compliments and thanks a lot for this new gift to Voodoo 2 fans :).
Imho, the memmap errors fix is a very good news for V2 owners.
Bye bye
thanks for the drivers koolsmoky :)
I'll test them asap :)
good 2010 for you and the rest of 3dfx warriors :D
awesome [8D]
Excellent. Good to see the community is still alive and a Voodoo2 driver no less! Who would have thought a 12 year old card would still have a following. No one still makes drivers for Rage or TNT now do they! Any chance of a new VSA-100 driver in the future? It seems that SFFT is officially finished with his project and my V5 is getting anxious to try some new shoes on! Might hafta find a c++ class to take if I don't see fresh drivers soon :)! Anyway awesome to see the Voodoo2 get a fresh charge. Keep up the good work koolsmoky!
Dropping off a new V2 driver kit. This kit includes fixes for system hangs on modern systems. Also gamma will be set to 1.00 if you use the included driver inf to install the driver. I am currently running my trusty V2 along with an ATI Radeon.
Tips to run Need for Speed 2 SE on Windows 2K/XP/VISTA
1. Do NOT copy the glide2x.dll to the game's folder.
2. Use Microsoft's Application Compatibility Tool. Follow the excellent tutorial; http://www.youtube.com/watch?v=jy1qfZBFEWo.
-KoolSmoky
thanks,time to give my v2sli a spin or two.. :)
Well i've installed the drivers,
and since that time as i've imaged the drive incase i borked things up.
i've had to restore it to that state before ever installing any 3dfx drivers.
so far i've tried the drivers from this post, and they don't give a control panel in the display settings. also i've tried original gl quake and a few others and all yield results of a black screen.
i then removed the miniport from the quake folder that the video came up but gamma was really low. so the picture was very dark. i've tried a number of way s to get this working and a few other driver set's and i keep getting stumped.
i either get a blank screen and no game sounds. or ai get very low frame rate and very dark gamma. i know long ago i got this working and got a time demo of 80 fps but i'll be darn if i can recall what i did
only one that came out was an old build of Darkplaces quake engine
there is no control panel in the driver.try the Voodoo2 Tweaker V1.1 from here: http://www.falconfly.de/tools.htm ,it should help you to adjust the gamma.
as for quake,you will need a standalone opengl driver to get it working-for this game,I would recommend wickedgl: http://helppage.3dfx.sk/#wickedgl
QuoteOriginally posted by ps47
there is no control panel in the driver.try the Voodoo2 Tweaker V1.1 from here: http://www.falconfly.de/tools.htm ,it should help you to adjust the gamma.
as for quake,you will need a standalone opengl driver to get it working-for this game,I would recommend wickedgl: http://helppage.3dfx.sk/#wickedgl
rockin! yea shortly after i made that post i figured something like that. so i dug through my old archives and found a few opengl miniports plopped one in and voila! got the twear you suggested, SPOT ON works perfect and is alot easier then messing with other ways.
going to try that wicked GL miniport next, but timedemo so far in excess of 150fps with vsync off @ 1024x768
NICE!
Ok very interesting as well diffrent system win98se
loaded refrence drivers for a set of individual voodoo2 cards, then copied in the glide2x.dll and glide3x.dll as refrenced in the topic and the readme of the package. however when launching such as glquake is says to upgrade my version of windows as glide2x expected a diffrent version. i thought it clearly said for 98/me to copy these into the windows\system folder?
if anyone know how i can get a voodoo 2 to work in windows 7 please contact i know theres no current drivers and i dont know if anyone is making one im cheap right now but im computer doesnt handle any 3d.
QuoteOriginally posted by netbeast
if anyone know how i can get a voodoo 2 to work in windows 7 please contact i know theres no current drivers and i dont know if anyone is making one im cheap right now but im computer doesnt handle any 3d.
there are drivers that work in win7 32-bit fo2 the voodoo2
but if you are use a 64-bit win7 installment you will need to use my 64 bit driver
but I have not used/tested my driver in win7 yet
koolsmoky's driver works fine under win7 32bit,even sli is ok-I have tested it myself.
QuoteOriginally posted by ms-dos
QuoteOriginally posted by netbeast
if anyone know how i can get a voodoo 2 to work in windows 7 please contact i know theres no current drivers and i dont know if anyone is making one im cheap right now but im computer doesnt handle any 3d.
there are drivers that work in win7 32-bit fo2 the voodoo2
but if you are use a 64-bit win7 installment you will need to use my 64 bit driver
but I have not used/tested my driver in win7 yet
Where is the 64-bit driver? I want to try with Win7x64.
Hi koolsmoky! :)
I've tried many-many drivers for my mismatched 3dfx Voodoo 2 12 MB SLI under XP, but almost all of them failed in various situations, except yours! :)
I'm using your latest driver, that you've posted here, and it works great!
Will you make any further updates for it?
Thanks!! :)
Best wishes,
Dobfek
Hi Dobfék,
you're welcome here.
Many thanks for your report.
Bye bye
Hi there!
I was trying to use the X-24 in my old rig
P3 1GHz (core coppermine, 133mhz)
2x256MB Pc133
all mounted on a HP Vectra VL400 DT (desktop)
I've installed the official Q3D Obsidian2 Drivers 6CF but the system hangs
(I have two X-24 and both have the same problem but under Windows Xp both run well)
Sometimes I can't see the screen properties (with a strange error message) and sometimes I can see the properties without the Q3D panel
KoolSmoky seems to be less problematic but I still have no control panel and the games don't recognize the card.
Any idea?
Hi,
Was an other 3dfx card previously installed in your system ?
What is the error message ?
Hi Nightbird,
no, the system has been formatted, so the X-24 is the only 3Dfx card.
The recurring error is "Mutual exclusion prohibits this" when I try to open the screen properties tab but sometimes it starts well without showing the Q3D Panel. Rarely also the Q3D panel appear.
I can't figure out what's happening!
Edit: oh, well.. I'm using Windows 98 SE ;)
Thanks
Hey Max_R,
Have you already red this: http://www.falconfly.de/info/readme-quantum-winnt-obsidian2pf-v5p.txt ?
Quote---------------------------------------------------------------------
Q: When attempting to run an application, boot the computer, or
launch the Display Properties sheet, the error message "Mutual
Exclusion Error Prohibits This" come up?
A: There are various reasons this message may come up.
1. The card was not shut down properly, and is still active. Turn
your computer off, and then back on to resolve this error.
2. The drivers from a previous 3dfx Voodoo or Voodoo 2 card
were not properly removed. Please follow this procedure
<link to uninstall error> to remove our drivers and any
previous drivers.
3. Your system BIOS is not properly interpreting the PCI-to-PCI
bridge chip on the Obsidian2 200SB series of cards. Please contact
your motherboard manufacture to get the latest BIOS.
4. There is another Voodoo2 based video card in your system from a
different manufacturer that is causing a conflict. There can only be
one card based on this chip set. Please remove the other card.
5. Your card is not working properly. Return the card for a
replacement.
---------------------------------------------------------------------
Since both X-24s act the same way, I would try to change the platform.
EDIT: From the readings here and there this error seems to occurr as soon as another application is accessing to DirectX at the same time. I would try to change the 2D X24 companion, then select another video adapter too.
EDIT2: More details about the motherboard specs?
DirectX version?
Have you installed any kind of Win98 update?
Hi,
Can you do a ctrl-alt-del in order to see what is running ?
Indeed!
As I've said, the installation is clean and there are two active process: Rundll32 and Systray.
P.S.
The mainboard is a D9820-60009 mounted in the VL400 DT. DX9C and a Kyro2 are installed but I've also tried with the only integrated vga and DX6/7/8 with the same results.
Is your card listed twice in the device manager tab of the system properties ?
I know I'm a little late to the party here, but I just want to thank you for these drivers.
I've built myself a retro machine and spent countless days trying to get three mismatched Voodoo II's to run on it with the FastVoodoo drivers (Creative CT6670, PowerColor Evilking, Diamond Monster 3D II). None of them worked, most of the time my screen just turned itself off or the GUI was corrupted on Windows 98 with nothing happening.
These drivers have the same behaviour by default (screen turns off, nothing to see), but when I set the registry key SSTV2_MISMATCHED_SLI=1 they work reliably with every game I have on all of the cards I own.
This is awesome. I'll stay far away from FastVoodoo now and use the reference drivers with these patched glide.dll files.
And I really thought I'd have to buy a fourth Voodoo II. Thank god I don't. :D
Hi Schmatzler,
you're welcome and I'm sorry for my delay.
Many thanks to have shared your considerations and opinions. And I'm so happy you can enjoy your 3dfx Voodoo2 and launch Glide-based games with native hardware support! ;)
See you soon
QuoteOriginally posted by koolsmoky
* Win9x/ME: copy glide2x.dll and glide3x.dll to c:windowssystem
This does not work! :(
Tested on clean win98 and voodoo 2 sli and V3.02.02 reference drivers.