News - 05/01/2004: these packages have been updated.
>>> These packages are for:
- MS Windows 2000 and XP OS
- 3dfx Voodoo2 based cards
- FastVoodoo2 4.0 XP GE driver
- ONLY hardware systems that still give Mapmen returned an error when trying to map memory after FastVoodoo2 4.0 XP GE installation
>>> Download
[MS Windows 2000 Fix (http://www.3dfxzone.it/files/download/video/3dfx/voodoo2/fastvoodoo2/2kxp/02/fv2_fix_2k.exe)]
[MS Windows XP Fix (http://www.3dfxzone.it/files/download/video/3dfx/voodoo2/fastvoodoo2/2kxp/02/fv2_fix_xp.exe)]
Try this fix and report your results in this topic.
Tnx to all for contribution.
Well, it worked!. Anyways, I was in a mistake with the previus fix version. I was using the WickedGL driver, insted 3dfx one. I didn't know that I had to use 3dfx miniGL instead WickedGL.
I don't understand, sorry [:I]
Say me: is now all ok with FV2 4.0, fix and WickedGL?
;)
No, it does not work with WickedGL; it works with 3dfx miniGL dll's.
better than noyhing..[:I]
Of course. And it works very well to me!
Ok friend,
I'm happy for this: now you must (;)) post some game images to screenshots forum :)
Glide, I don't know why, but I can't capture screens [V]. Do you know a software that do this? [:p]
Hi Panoramix!
HyperSnap's the way to go for glide captures. It works well here but I've not tried it under Windows XP. Just remember to enable "Special Capture" on the Capture menu.
http://www.hyperionics.com/
Well, at last!!!. Here we go with Quake:
(//../public/uploaded/PanoramixDruida/200411222653_Quake1.jpg)
(//../public/uploaded/PanoramixDruida/200411222754_Quake2.jpg)
(//../public/uploaded/PanoramixDruida/200411222843_Quake3.jpg)
(//../public/uploaded/PanoramixDruida/200411222925_Quake4.jpg)
Motorhead:
(//../public/uploaded/PanoramixDruida/200411223721_Motorhead1.jpg)
(//../public/uploaded/PanoramixDruida/200411223758_Motorhead2.jpg)
(//../public/uploaded/PanoramixDruida/200411223838_Motorhead3.jpg)
(//../public/uploaded/PanoramixDruida/200411223930_Motorhead4.jpg)
Turok:
(//../public/uploaded/PanoramixDruida/200411224617_Turok1.jpg)
(//../public/uploaded/PanoramixDruida/200411224643_Turok2.jpg)
(//../public/uploaded/PanoramixDruida/20041122473_Turok3.jpg)
(//../public/uploaded/PanoramixDruida/200411224724_Turok4.jpg)
Unreal:
(//../public/uploaded/PanoramixDruida/200411225534_Unreal1.jpg)
(//../public/uploaded/PanoramixDruida/200411225614_Unreal2.jpg)
(//../public/uploaded/PanoramixDruida/200411225646_Unreal3.jpg)
(//../public/uploaded/PanoramixDruida/200411225716_Unreal4.jpg)
(//../public/uploaded/PanoramixDruida/200411225745_Unreal5.jpg)
Until now, I only have one problem. Every time I try to go out of Quake III, my PC freezes.
As you can see, every other game works very well!!!
Hi,
I had exactly the same Problem with my Voodoo2.
Now i managed to get it work with Unreal, but i#180;m a bit disappointed of the result. The textures lock nice, but the edges aren#180;t as smoth as i exspected.
Can I use some AntiAliasing methods? I use 1 V2, do u think its worth to get a second one and play in SLI Mode in higher Resolution?
Greets Phobos
Hexen II:
(//../public/uploaded/PanoramixDruida/200411615537_HexenII_01.jpg)
(//../public/uploaded/PanoramixDruida/200411615650_HexenII_02.jpg)
(//../public/uploaded/PanoramixDruida/200411615733_HexenII_03.jpg)
(//../public/uploaded/PanoramixDruida/200411615825_HexenII_04.jpg)
How are you Glide?. Are you planning to release a newer patch/driver set for nForce series chipset and Voodoo2/Windows 2000XP?
I am an owner of a Quantum X-24 and I have a problem with the Mapmem error.
My system is
AMD 2100 XP
MSI KT333 Ultra
512 DDR Cosair @ 333 Mhz
ATI All In Wonder 9700
Cat 4.4
SB LIVE 5.1
WinXP Pro SP1a
Direct X 9 b
Quantum X-24
I can not seem to get it to work with any drivers. It has to be a problem with my Radeon 9700 because I have installed a working Quantum X-24 on another machine
That system is
A7A Asus 266
512 Corsair @ 266 mhz
Radeon 9100 64mb
Cat 4.4
SBlive 5.1
Direct X 9.b
WinXp Pro SP1a
Quantum X-24
I use orignial 3dfx Referance drivers for windows NT but I use the last Quantum X-24 Glide2x.dll file The system works great!!! 100 Frames a second in all games I play.
I like to Play older 3dfx games like
Red Baron 3d UltraHLE Whiplash 3d
These all use Glide2x.dll
I've tried the latest Gold 4.0 release and the "fix" which seems to be just the quantum glide2x.dll file. No luck on my machine with the radeon 9700.
If you could please help me i just bought it off ebay and really want to use it. Thanks
Brain
ballen1@cox.net
Tried the fix. i installed it to a directory to see what was going in to the windows\system32. There are 3 files one is just a html.
When i copy files over the glide3x.dll was older than the version in there so i didnt copy that one other
the glide2x.dll was new version so i copied that over and i ran Quake
ran perfect no error.
so u just might need the glide2x.dll in there for it to work cause that all i needed
system :-
amd-k6tm-2 500 mhz running at 450mhz 75mhzfsb X 6 mulitplier
qdi P5I430TX titanium IB+ socket 7
fujitsu 40GB 5400rpm hard drive + 3Gb hard drive
2 X creative 3d blaster 12mb Voodoo 2 (sli)(4.0_xp_ge drivers + fix glide2x.dll)
1 X pci 4 Mb ati rage II+ dvd
196mb sdram
XP PRO + service pack 2
ess 1868 isa sound card
dvd rom
i installed the fix in \system32 dir, and all games work without error, but why any effects like lights are ping?
Hey, if you're getting pinkies in SLI, put
"SET SSTV2_VIDEO_24BPP" (without quotes) string with value of "0" into your glide environment (regedit -> hkey_local_machine\3Dfx Int.\Voodoo2\Glide). May this help you, Ent.
Sorry, no "set" in the string of course, already too late for typing... :)
So when will w know more [^]
I installed latest fastvoodoo2 Gold Edition drivers
and got gen io initialization error
i found on experts exchange that i sould goto device manager and select to see hidden items and set voodoo memory map and voodoo pci to system instead of automatic
and after that i got the memmap error
i installed the patch for xp on this forum
and im still getting the error
what to do now
helpppppp
i have a m812 sis6326 onboard video and monster 3d II 12mb
duron 750mhz and amr modem running on winxp pro sp2
helpppppp
read through this (http://www.shifter.sk/helppage/default_fix.htm#SLI) (also applies to single v2),and see if something helps.and try to use the edit button next time you want to add something.
thanks but the url you posted is not working
could you please check it ?
THANKS
i get a dns lookup error with that url
but when i put it into www.kproxy.com i am able to open it
its really slow though and Im not sure what to click there
QuoteOriginally posted by tarcis
i get a dns lookup error with that url
but when i put it into www.kproxy.com i am able to open it
its really slow though and Im not sure what to click there
Hum, the url is working for me [?]
At least, the text :
QuoteSetting up Two Voodoo2's in SLI (Scan Line Interleave)
First, some things you should know:
A Voodoo2 SLI setup will work fine in almost any system with 32-bit OS installed (win9x/ME/2000/XP are supported). Some systems may need additional tweaks or special drivers though. V2 SLI runs best under win9x/ME, XP drivers don't have D3D support (there are drivers in development that will fix this problem), there is only support for glide/opengl. Glide games will detect the V2 SLI and run without additional tweaks, but if you want to use opengl, you will always have to place a standalone opengl driver to the game's main folder (where the game's executable is located). If you won't do this the opengl game will run on your primary card or not at all (go here to see the list of available opengl drivers). Many new systems have problems with tearing artifacts while running games on the Voodoo2 cards (it is related to PCI latency, it should be set as low as possible in the BIOS, but many bioses simply cant tune it down), this can be fixed by installing the Voodoo2 Tweaker and enabling the sync buffer swaps to refresh rate option. Note that some opengl games don't like this if you run them on a glide3x based opengl driver, and lag as a result. To avoid this, always try to use Wickedgl or Minigl for your opengl games, these opengl drivers use glide2x and will run without lagging, so you can safely enable the sync buffer swaps to refresh rate option in the Voodoo2 Tweaker and there will be no tearing nor lag. That means stay out of 3dfx OpenGL ICD and MesaFX if you can. (common examples of such opengl games: Quake 1/2/3, Half-Life&mods etc.)
IMPORTANT: if you want to avoid the tearing problem completely, get a SIS 748 chipset based motherboard. These mobos will run voodoo2 SLI without problems.
In order to setup two Voodoo2's in SLI, you will need two Voodoo2 cards, a primary display adapter, a pass-through cable (which should have come with your Voodoo2, or you can just use a monitor extension cable), and a 34 pin SLI cable. It is highly recommended that not only should the two Voodoo2's used for the SLI have the same amount of memory, but also be from the same manufacturer; they should be identical cards. If you don't have the 34 pin cable, don't worry, as one can easily be made out of a floppy cable. Starting with a 34 pin (2x17) cable, pry the tabs on the sides of the black connectors away from the sides, and pull off the back covering. The cable has to be altered slightly; the 4 wires in the center have to be twisted (wires 16, 17, 18, and 19). Pull them out and twist them around so that now the wires go 1-15, 19, 18, 17, 16, 20-34. These four wires are the only ones that should be twisted. To see Fast Eddy's description, visit this page: Fast Eddy's Temp File Store.
Your primary display device should be working already (IMPORTANT: Set the AGP Aperture Size to 128MB or lower in your BIOS. Vodooo2 SLI may not work with a higher setting than that). Now, you will insert both Voodoo2's into open PCI slots. They do not necessarily have to be adjacent if your SLI cable is long enough. Connect the pass-through cable (not the SLI cable) from your primary display adapter's 15 pin Sub-D connector to the first Voodoo2's in. Now, connect your monitor's cable to the first Voodoo2's 15-pin Sub-D out. Inside the case, attach the SLI cable to the Voodoo2's, remembering that the red wire corresponds with the 1 pin. The SLI should auto-detect after you install your drivers and run without further setup whenever you normally would only have had one Voodoo2 running.
Note: Problems are sometimes reported when booting with Voodoo2's setup in SLI before installing the drivers. To remedy this, follow this alternate order: insert only the first Voodoo2 and connect the pass-through cable, boot up, install your drivers, shut down, install the second card and the SLI cable, and reboot.
Hi,
I have tried the fix, and now my Obsidian 200SBi works flawless. No more MAP MEMORY error.
Thanks,
Oscar
Hello all,
I installed FastVoodoo2 4.0 XP GE driver for my 2xVoodoo2 12Mb and I'm getting this famous "Mapmem driver initialization failure" when I try running NBA Live 99 or Unreal Tournament
Check the SS:
(http://img35.imageshack.us/img35/2554/mapmem.jpg)
Tried the fix but it didn't help...
What now?
My system:
ABIT BX133-RAID motherboard
Pentium III 1Ghz CPU
512Mb SDRAM Kingston CAS 2-2-2 memory
ATI Radeon 8500 AGP 64Mb (also tried with a SIS 6324 8Mb AGP, no luck)
2 x Voodoo2 (Creative Labs) 12Mb SLI
SoundBlaster Live! 5.1
3Com 10/100 ethernet card
Windows XP SP2
Thanks in advance!