I feel silly for not thinking about this sooner, but I just now looked at my environment variables and found an entry that set the clock speed to 94 MHz.  I can't remember how it got there.  I probably put it there myself when I was trying to get the cards to work a few months ago.

In other words, nevermind.  Help someone with a REAL problem.  I'll be in the corner wearing a "dunce" cap if you need me.

Now that I have my Voodoo2 cards working properly in SLI mode on my Windows XP system, I've been experimenting with them a bit.  One thing I've discovered is that overclocking the cards doesn't impact the frame rate of games or demos!  I've clocked them as high as 105 MHz to no effect.  I am, of course, rebooting after making the change in the control panel, but there is still no change in speed.

Powerstrip reports the speed as matching that set in the control panel, but only after a reboot of course.  Also, Powerstrip allows you to make a change immediately without rebooting, but there is still no change in game or demo framerate.

Any ideas as to what may be happening?  Is this because of the SLI configuration perhaps?  (Powerstrip shows both cards in the "Options.../Adaptor information..." window, but it only has one entry for "Performance profiles ->/Configure...".)

I've read that the keypress combination CTRL-F9 can be used to toggle the passthrough function on Voodoo2 cards.  This would be useful to get back to the desktop when a Glide program crashes, for instance.  Of course this doesn't work under Windows XP.  Does anyone know of a small program that could be used to accomplish the same thing?

Thanks

You're welcome.

Hopefully this won't cause any problems with other systems out there!

Here's another link where you can download that driver package:

http://www.quantum3d.com/support/consumer/Ob2_6cf_nt.exe

I'm sorry I couldn't just post that glide2x.dll to this forum.

I tried to upload the glide2x.dll I found, but when I click on the file upload button I get a window that says that I must be logged in.  I tried setting my IE6 privacy settings to accept all cookies, but that didn't help.  In fact, the only way I'm able to post messages at all is by providing my username and password in the fields above the message box.  This is strange because no other message board gives me this problem.

Anyhow, if you have a driverguide.com membership ID you can follow this link to get the file:

http://members.driverguide.com/driver/detail.php?driverid=121653

If you don't have an ID, you can register for free.

Once you have the driver package, extract its contents using your favorite Zip program.

According to the "Uploader Notes", the driver package won't work for Windows 95/98/ME/2000 or XP, only NT.  But I find it interesting that the glide DLLs do work under XP once FastVoodoo2 4.0 XP GE is installed.

Wow!  Yes!  It works!

Diablo 2 plays perfectly.  However, Independence War had all sorts of texture errors.  So I took a look at the version numbers for the glide dll's in FastVoodoo2 4.0 XP GE and I noticed that the glide2x.dll was originally from the GlideXP package and the glide3x.dll was from Quantum 3D for their Obsidian2 card.  

Since GlideXP's glide2x.dll is essentially a wrapper sending glide2 calls to the glide3x.dll, I figured the problem was in the translation, so I went looking for the Quantum 3D drivers at driverguide.com and found them, Ob2_6cf_nt.exe.  I simply replaced the GlideXP glide2x.dll with the one from the Quantum 3D package (version 2.54.3.457, dated July 30, 1999) and all is well!  (Note, I did not install the Quantum 3D Obsidian2 drivers.  I just replaced that one dll by extracting it from the archive using PowerArchiver 2000 and copying it to my system32 directory.)

Thanks so much for fixing this problem for all us nForce2 users.

Glide,

No problem regarding the feedback, and I have to say that I admire your commitment to resolving this problem.

Looking at other threads regarding the mapmem error ("Voodoo2 and XP HELP!!!!!" and "Voodoo2 on XP Glide problem"), it appears that almost all the problematic systems use the nForce2 chipset: the Epox EP8RDA3+, the Epox 8RDA, the Abit NF7-S, and the ASUS A7N8X Deluxe have all been mentioned.  The one exception I saw was a PC Chips M810, which uses a SiS chipset.

Anyhow, I wish you luck in finding the problem.

Sincerely,
Olivaw

Hey, another NForce2 chipset user!  I wonder if our problem is caused by the chipset itself or because of the PCI-to-PCI bridge.  I tried all of the PCI slots on my motherboard, but they all use a bridge.  Anyhow, whether it's the chipset or the bridge, I'm afraid that this problem is way beyond a driver package fix.  I think it would need at least a binary patch.

In the good news department, I've managed to get Independence War to run in Glide using Zeckensack's Glide wrapper.  It only emulates Glide 2.4 and a Voodoo1 card, so I can't run in 800x600 mode, but 640x480 works well.  (According to the I-War readme, Glide 2.5 is needed for 800x600.  Damn, I'm just revision 0.1 away from having exactly what I need to run my favorite old game!)

So, for the time being, I've put the Voodoo2 card back into my wife's computer for SLI mode and I'm using the Glide wrapper.

No joy on the latest update.  I still get the mapmem error.  I even tried to lower my desktop's color resolution from 32-bit to 16-bit, but that had no impact.

Last night, I noticed that on my computer every PCI expansion card has a "PCI standard PCI-to-PCI bridge" covering the same memory range as each card.  I can see this in Device Manager by selecting "View/Resources by connection" on the menu.  Then I drill down by expanding "Memory" and then "[20000000 - FEBFFFFF] PCI bus".  On my wife's system the Voodoo2 driver is listed directly under the "PCI bus", but on my system there is a "[D8000000 - D8FFFFFF] PCI standard PCI-to-PCI bridge" that has to be expanded before you can see the Voodoo2 driver.

After noticing this, I installed a second copy of Windows XP on another partition of my computer and forced it to install the Standard PC HAL.  Unfortunately, the "PCI standard PCI-to-PCI bridge" was still there even before installing the nForce drivers.  I also tried to uninstall the PCI bridge, but that also uninstalled the Voodoo2 driver and the PCI bridge reappeared automatically on a reboot.

I have a very strong suspicion that the PCI bridge is the cause of my troubles.  Unfortunately, I can't seem to get around it.  The only PCI devices that aren't associated with PCI bridges are the built into the motherboard: They all have entries directly under "PCI bus".

I hope this information helps you to figure out what's wrong.

I am also having difficulty getting my Voodoo2 working properly under Windows XP on my system.  The error I receive upon starting any Glide application is, "Mapmem returned an error trying to map memory."  

I have an ASUS A7N8X Deluxe motherboard (NForce2 chipset) with an Athlon XP 2600+ (Barton core).  In addition to the Voodoo2, I also have installed a Prolink Pixelview GeForce4 Ti4200 AGP video card, a D-Link AirPlus DWL-520+ 802.11b+ PCI NIC, and a 3Com 3C410 HomeConnect HomePNA PCI NIC.  Windows XP was installed with the ACPI Uniprocessor PC HAL.  

The Voodoo2 card is installed as "3dfxzone.it FastVoodoo2 4.0 XP Gold Edition" under "Sound, video and game controllers" as shown in Device Manager, and it is occupying the D8000000 - D8FFFFFF memory range.  Device Manager reports, "This device is working properly."  Also, the "3dfx V2-1000" tab appears in the "Advanced" window in the Display Properties.

In contrast, the FastVoodoo2 4.0 XP Gold driver is working fine on my wife's computer, an MSI K7 Pro (AMD 750 chipset) with an Athlon 1 GHz (Thunderbird core).  In addition to her Voodoo2, she has a Built-by-ATI Radeon 8500 AGP video card, a Creative Audigy2 PCI sound card, and a Compaq NC3121 fast ethernet PCI NIC.  On this system Windows XP was installed with the Standard PC HAL.

Her Voodoo2 is occupying ED000000 - EDFFFFFF memory range, and is installed as "3dfxzone.it FastVoodoo2 4.0 XP Gold Edition" under "Sound, video and game controllers".

One final note, both Voodoo2 cards are Diamond Monster 3D II cards.  Before placing the Voodoo2 card in my system, I had it installed in my wife's computer in SLI mode with the one that remains in her system, so I know it works.

Any ideas?