Try putting the relevant glide dll's [for the card you want to use] in the game folder [where the game executable is].

Not working game Pandemonium on Voodoo 1 ((

What need driver Voodoo 1 for Windows 98 ?

What need DirectX for Windows 98 , for Voodoo 1 and Voodoo 3 ?

How to properly install the driver ,
Voodoo 1 then Voodoo 3 or Voodoo 3 then Voodoo 1 ?

Thanks

ratfink wrote:

Try putting the relevant glide dll's [for the card you want to use] in the game folder [where the game executable is].

This'll work.
Make sure you reinstall the Voodoo3 drivers AFTER the Voodoo (so Voodoo3 gets its voodoo back). Then, for Voodoo only games, just use the Voodoo's dlls (pull them out of the driver archive and put them in the games' exe folder)

I've tried this combination with a Voodoo2. Quite the noticable performance jump going directly from 2 to 3...

Best resource for official 3dfx drivers.

Some early 3dfx accellerated games use their own 3D drivers and just need a Voodoo 1 board installed to work - ie, no 'glide' drivers are needed. EF-2000 3dfx for example. In this case you just pop the Voodoo 1 board in alongside the Voodoo 3 and the game sees it. I did this with a Voodoo 5500 until I finally built retro boxes for the different Voodoo iterations.

You forgot to add - some early DOS 3dfx accelerated games. And they are using standard glide drivers, just statically linked in .exe.
3 Windows glide games are using glide 2.1.1 (glide.dll and sst1init.dll) only - Cybergladiators, Pandemonium! and OEM 3dfx version of Mechwarriors 2: 31st Century Combat. The .dlls are dated 21 Jan 1997, so - of course they will not work with anything except Voodoo1. AFAIK, you can tweak Voodoo2 or Voodoo3 with SST variables to work with these 3 games.

You are correct Gc - statically linked to the exe. But the end result is that in some cases you don't need to mess with Glide.dll at all. The easy test is to simply install the Voodoo 1 card withou drivers and try running games.

Adding SST variables to your boot files works in many/most cases but I always wondered if it degraded performance of the prime Voodoo card. Not a big deal if you only use the modded boot file selectively for particular gaming sessions that need it.

What file names pull out from driver archive and put them in the games' exe folder ?

Gamecollector wrote:

AFAIK, you can tweak Voodoo2 or Voodoo3 with SST variables to work with these 3 games.

For Mechwarrior 2, the SST batch file tweak only works on the Voodoo2.

"Voodoo 1 and Voodoo 3 in same PC"

Since nobody else asked, I will, why would you even need to do this?

Read above. Voodoo3 doesn't work with every glide thing under the sun. A Voodoo Graphics card would play a role as the 'gap filler'

Ok, I have found another glide 2.1.1 game. Scorched Planet. So, there are now 4 Windows Voodoo1-only games...

I think the 3dfx bundled version of Hyperblade also used Glide 2.1.1.

No. Hyperblade is D3d only.
There are 2 more games using glide.dll - Pod and Outlaws. But there are official patches to add glide2x.dll support for these games.
Plus several games are using glide 2.1.1 in the installer only (Voodoo card detection). As the example - F1 Racing Simulation...

leileilol wrote:

This'll work. Make sure you reinstall the Voodoo3 drivers AFTER the Voodoo (so Voodoo3 gets its voodoo back). Then, for Voodoo […]
Show full quote

ratfink wrote:

Try putting the relevant glide dll's [for the card you want to use] in the game folder [where the game executable is].

This'll work.
Make sure you reinstall the Voodoo3 drivers AFTER the Voodoo (so Voodoo3 gets its voodoo back). Then, for Voodoo only games, just use the Voodoo's dlls (pull them out of the driver archive and put them in the games' exe folder)

I've tried this combination with a Voodoo2. Quite the noticable performance jump going directly from 2 to 3...

Copy in folder game only glide.dll, of
driver Voodoo 1 ?

1) Three files - glide.dll, sst1init.dll, fxmemmap.vxd. Not sure about the fxmemmap.vxd, several games aren't including this file.
2) You can leave glide.dll and sst1init.dll in the system dir. Because Voodoo3 will not use glide 2.1.1 at all. And several installers are searching for these files.
3) To be more precise:
Cybergladiators - no glide 2.1.1 is included on cd. You must install glide 2.1.1 from another source.
Mechwarriors: 31st Century Combat 3dfx - no glide 2.1.1 is included.
Outlaws (with 1.1 patch) - no glide 2.1.1 is included.
Pandemonium! - glide 2.1.1 (from 21 Jan 1997) is included on cd and is installed in the gamedir. No fxmemmap.vxd is included.
Pod 2.0 - no glide 2.1.1 on the cd. You must install glide 2.1.1 separately because you can't even install the 3dfx version w/o glide 2.1.1 drivers.
Pod Gold is using glide2x.dll and don't need glide.dll and sst1init.dll in the system.
Scorched Planet - glide 2.1.1 (from 25 Jul 1996) is included on cd and is installed in the gamedir if Voodoo1 (Rush?) was detected.
Tigershark - no glide 2.1.1 is included.
Time Warriors - glide.dll and sst1init.dll (from 23 Jan 1997) are included.

Glide2x games with glide.dll/sst1init.dll on the cd: Asghan (glide.dll and sst1init.dll, 23 Jan 1997), Joint Strike Fighter (20 Jan 97).
Joint Strike Fighter have 2 versions of glide 2.1.1 - Win95 and WinNT. And there are 2 more files - genport.sys and mapmem.sys...
Plus there is Glide 2.1.1 SDK. Again there are genport.sys and mapmem.sys as the WinNT driver files...

Another strange case: Joint Strike Fighter.
The installer copy glide.dll, sst1init.dll and glide2x.dll in the Windows system dir. But the game itself is using glide2x.dll, so - why glide 2.1.1 files?

How to install ?
1) Windows 98

2) Direct X (What is needed Direct X ?)

3) Driver Voodoo 1
Please link on Driver Voodoo 1

4)Driver Voodoo 3
Please link on Driver Voodoo 3

GreatDragon wrote:

How to install ? 1) Windows 98 […]
Show full quote

How to install ?
1) Windows 98

2) Direct X (What is needed Direct X ?)

3) Driver Voodoo 1
Please link on Driver Voodoo 1

4)Driver Voodoo 3
Please link on Driver Voodoo 3

I usually take my drivers from here:
http://www.falconfly.de/3dfx.htm