Can't remember the specifics TBH but Mech 2 3dfx definitely requires an older Glide DLL to be copied in when running under the latest reference drivers.

I recall downloading old Orchid drivers for my Righteous 3D to run MW2 I think. Probably for that old Glide.DLL.

I should just be able to drop one of the older glide.dll files into the game folder itself then right?

What about the resolution locking issue? Is that an issue with the Geforce4 or something to do with the voodoo blocking the higher modes?

About "glide2x.dll expected Voodoo2, none found" and "something I/O error".
I have fixed this in WinXp.
You need to set fxgpio and fxptl as core mode services.
Set the "Start" parameter from "2" to "1" in a registry.
I have attached the .reg file.

Mechwarrior 2 is one of the glide 2.1.1 games. It's using glide.dll and sst1init.dll.
Glide 2.1.1 isn't included in the last reference drivers.
IIRC you can run these games on Voodoo2 with v2_auto.inf environment variables.

senrew wrote:

Before I go on a mad shopping spree for new hardware, maybe someone could help me figure out my issues with the two voodoo cards […]
Show full quote

Before I go on a mad shopping spree for new hardware, maybe someone could help me figure out my issues with the two voodoo cards I have.

Everything below pertains to my win98 machine, geforce4 ti 4600, asus 45.23 driver, dx8.1a.

Voodoo2
Diamond Monster 3D II 8MB. I installed this in the P3 in my sig. I can install the drivers just fine, Windows 98 Device Manager sees it just fine and reports that the card is working, etc.

When I boot the machine, and windows loads, I get a pop up saying something like Diamond Monster not found when I have the Diamond drivers installed. If I switch over to the latest v2 3dfx reference drivers, I get some glide.dll something message at boot instead. The passthrough seems to work just fine as I can see things on my screen. However, when I have the monitor connected via vga from the geforce4 through the voodoo card, I can't raise the resolution beyond 640x480. The slider in display properties will move just fine, I can click ok to confirm my selection, but when the screen blinks to display the new resolution it's still at 640x480. If I kill the passthrough and plug the vga cable into the voodoo and a dvi cable into the geforce (monitor has dual on the fly switchable inputs), it'll correctly choose the dvi for main output. When I run a glide game, either the game will CTD or, if it appears to be running, I'll switch over to the vga input from the voodoo2 but the screen will just be blank.

I think the card itself is just fucked, or maybe it's something as simple as I'm just not putting it in the right pci slot (I've tried it in both slot 1 and 2, counting from the agp slot)

Voodoo1
This is a PowerColor CFX something or other card. I found the specific model number once but never again. It does work, however in one instance (and pretty much the reason I bought the card to begin with) it doesn't. This card usually lives in my DOS box (the first one in my sig). It works just fine there. Jetfighter Full Burn recognizes it and the game runs in accelerated mode beautifully.

I picked up the 3dfx version of Mech2. I installed it on the win98 machine. I stuck the v1 card in there, win98 recognized it with the built-in drivers. I added the latest refrence 3dfx drivers just in case. Mech2 installed just fine, however in the graphics options, I didn't see the option for selecting a resolution at all. If I try to run one of the mission from the cadet training, it just drops back to the menu. I swapped to the 3dfx reference drivers, and running mech2 again gives me 320x200 or 640x480 in the resolution option this time. I tried to jump into one of the training missions, and it CTD.

Kinda going nuts over this and I'm hoping I don't need to do anything drastic about buying all new hardware.

copy sst1init.dll and glide.dll to the game's directory

I have it running using Nglide and MechVM from mech2.org. No 3dfx Hardware present at all...

senrew wrote:

I should just be able to drop one of the older glide.dll files into the game folder itself then right?

What about the resolution locking issue? Is that an issue with the Geforce4 or something to do with the voodoo blocking the higher modes?

BTW, I was reading through the readme file included with those last reference drivers and it seems that Win98 hadn't recognized my specific monitor and was set to "unknown" in device manager. The readme file says to switch it to at least plug & play if not the specific driver for the monitor. That's what was locking the resolution even though I could switch it in the display properties.

Orchid Righteous3D gives this output on Direct3D PCPlayer Benchmark. It works fine with Glide (demos of NFS2SE, NFS3 and Descent 3dfx patch) and even WizMark works. I haven't done other DX testing with it.

What is wrong?

This is on ECS P6VAP-Me (VIA VT82C694X (NB) & VT82C596B (SB)), P3-800, 256MB, Win98SE and latest reference 3dfx drivers (this also happens with older Orchid drivers).