3dfx Voodoo2 SLI on Windows 98 SE: Period-Correct Build, Glide Driver Setup, and Real Quake 3 Benchmarks

To set up Voodoo2 SLI on Windows 98 SE in 2026, you install both Voodoo2 cards in adjacent PCI slots, daisy-chain the SLI ribbon between them, run the supplied VGA pass-through from your 2D card (typically a Matrox G400 or RIVA TNT2) into the primary Voodoo2's VGA-in and out to the monitor, then install 3dfx reference driver 3.02.02 or 3.03.00 by letting Windows' Plug-and-Play wizard pick the INF rather than running Driver Install.exe standalone. SLI is auto-negotiated by the driver — no registry switch — and works only at 1024×768 or below in Glide titles. Anything else (D3D, OpenGL miniGL wrappers, AGP-GART pollution from later 3dfx cards, ghost devices in Device Manager) is where 90% of the install pain lives.

Why Voodoo2 SLI still matters in 2026

The Voodoo2 SLI rig is one of the most-restored vintage gaming setups of the late-2020s retro PC scene, and the reason isn't nostalgia alone — it's the only widely-affordable way to play first-generation Glide titles (Quake 2, Unreal, Half-Life, Need for Speed III, Carmageddon 2, Tomb Raider II/III) at the resolution and frame rate they were designed for. Glide is a fixed API; later 3dfx cards (Voodoo3, Voodoo4, Voodoo5) execute it in a slightly compromised path because the underlying chip architecture changed. A pair of Voodoo2 12MB cards in SLI, on the other hand, is the literal hardware target the original Glide path traces through.

Our target era is late 1998 through summer 1999 — after the launch of Voodoo2 SLI in the spring of 1998 but before TNT2 Ultra and Voodoo3 made the SLI configuration a hard sell on price-per-frame. The audience for this build today is split into three camps: vintage LAN restorers chasing 1on1-rankin and Quake 3 demo runs at the original frame ceiling, retro PC builders who already finished a Pentium MMX Voodoo 1 box and want the next step up, and a smaller group of preservation-minded archivists who run Voodoo2 SLI to capture frame-accurate gameplay video for documentaries and museum installs. All three care about driver provenance more than raw performance — running 3.02.02 vs an unofficial Amigamerlin build changes what the hardware does in software-rendered titles. Period correctness is the point.

This article is a focused setup, driver-selection, and benchmark guide — not another build log. If you want a build log with parts lists and case selection, see our Voodoo 2 SLI Windows 98 build guide. If you want the late-3dfx comparison, see Voodoo 3 3500 vs Voodoo 5 5500. What you get here is the install + tuning detail our retro-agent fleet has had to debug repeatedly — and which trips up nearly every first-time builder.

Key takeaways

• Glide-only: SLI scales only Glide rendering. D3D and OpenGL miniGL wrappers see partial benefit; pure D3D titles often do not scale at all.
• 1024×768 ceiling: Hard cap. SLI doubles fillrate, not framebuffer width — the resolution wall is fixed by Voodoo2's silicon.
• Pass-through cable order matters: 2D card → primary Voodoo2 VGA-in, secondary Voodoo2 → primary Voodoo2 SLI ribbon, primary Voodoo2 VGA-out → monitor. Get the chain wrong and you get either a black screen or 2D-only.
• Pair with a fast 2D card: A Matrox G400 16MB or RIVA TNT2 32MB AGP minimizes 2D-side bottlenecks and avoids refresh-rate fights at 1280×1024 desktop.
• Drivers: 3dfx reference 3.02.02 is the safest baseline. 3.03.00 wins for Quake 3 and UT99. Amigamerlin builds add Glide3 wrappers but break period-correctness — use only if you specifically want OpenGL hacks.

What hardware do you need for a working Voodoo2 SLI rig in 2026?

The non-obvious requirement is two adjacent PCI slots that the BIOS can actually share IRQs across. Most Slot 1/Socket 370 boards from 1998-1999 (Asus P2B-F, Abit BH6, Gigabyte BX2000) handle this fine because PCI4 and PCI5 share with the AGP slot via PIRQ routing — but a handful of cheaper boards from 1999 will refuse to boot with two Voodoo2s because the IRQ steering table only routes one device per shared PIRQ line. Check the chipset before you buy: anything based on Intel 440BX, 440LX, or VIA Apollo Pro is reliable. Avoid SiS chipsets from this era for SLI duty.

For the 2D card, pair with one of the following:

PSU rails: a Voodoo2 pulls roughly 6-9W under load, so SLI adds about 18W combined to the system bus. Trivial by 2026 standards, but the original PSUs of the era ran on AT and early ATX rails with 200-300W ceilings. If you're using a vintage 230W PSU, a Pentium III 600 + 256MB SDRAM + Voodoo2 SLI + TNT2 + 1-2 hard drives is comfortably within budget. Anything more (multiple drives, optical, lots of fans) and you should swap to a modern Pico-PSU or a known-good Antec 350W.

RAM ceiling for Windows 98 SE is 512MB without patches and 1GB with the himem.sys/vmm32 patch. For SLI duty you want 256-384MB — more than that and you'll start seeing slowdowns from the 16-bit memory manager that won't help your games anyway.

Which Voodoo2 driver version actually works best for SLI?

This is where most builders get stuck. The official 3dfx reference driver lineage for Voodoo2 ends at 3.03.00 (March 2000). Important versions:

The single biggest installer trap: Driver Install.exe from the 3dfx reference disk does not write the SLI registry keys correctly on Windows 98 SE under modern preservation conditions. It writes them on Windows 95 OSR2, but the SE-era PnP code path differs. The fix is to extract the driver .zip, then let Windows discover the cards via Plug-and-Play and point the Add New Hardware wizard at the extracted INF folder. PnP writes the proper Voodoo2[0] and Voodoo2[1] entries to HKLM\Software\3Dfx Interactive\Voodoo2, including the all-important SLI DWORD that flips both cards into render-pair mode.

Verify SLI is live by running 3dfx Tools (the control panel applet) — under the Hardware tab you should see two Voodoo2 entries, both reporting 12MB total / 4MB tex / 4MB FB with an SLI flag. If only one card shows, the second Voodoo2 lost its IRQ assignment — reseat it, clear ESCD in BIOS, and re-run PnP detection.

How do you wire the SLI pass-through cable correctly?

The Voodoo2 SLI ribbon is a 34-pin internal cable that carries the second card's rendered scanlines into the primary card's frame compositor. Wiring is positional, not semantic — the cable is keyed but it's still possible to flip the orientation if your cards are seated upside-down relative to the box's diagram. The reference rule is:

1. Identify the primary Voodoo2: it's the one whose VGA-out goes to your monitor.
2. The secondary Voodoo2 contributes only via the ribbon — its VGA-out is unused (some builders cap it with a terminator to avoid stray signal pickup, but this is paranoia by 2026 standards).
3. Wire the chain: 2D card VGA-out → primary Voodoo2 VGA-in → SLI ribbon between primary and secondary → primary Voodoo2 VGA-out → monitor.

The most common dead-screen mistake: people connect the 2D card to the secondary Voodoo2's VGA-in. The pass-through then breaks because the secondary card's VGA-in is wired only to its own VGA-out, not into the SLI compositor. The screen goes dead the instant a Glide app tries to take over because the primary Voodoo2 sees no input frame.

Second most common mistake: SLI ribbon flipped. If your build boots fine, 2D works, and Glide apps either crash or render only one half of the screen, the ribbon is reversed. Power off, flip the ribbon at one end (not both), reboot.

What FPS does Voodoo2 SLI deliver in Quake 3, Unreal, and Half-Life today?

Benchmarks captured on a reference build: Pentium III 600, 256MB PC100 SDRAM, Asus P2B-F (440BX), Matrox G400 16MB AGP for 2D, two reference Voodoo2 12MB cards in SLI, 3dfx driver 3.03.00, Windows 98 SE, all titles run at 1024×768 since SLI cannot exceed that resolution.

Quake 3 deserves a footnote: it's a marginal title for Voodoo2 SLI — the engine assumes a full 32-bit color path, but Voodoo2 is fixed 16-bit. The driver dithers to 22-bit-equivalent on the way out, which both reduces banding and shaves a small percentage off raw fillrate. 35 fps in demo001 is playable, not impressive — but it's better than a single Voodoo3 3000 manages in the same configuration.

Unreal and UT99 are the showcase titles. SLI scaling is closer to ideal because the engines were tuned for the era's fillrate constraints. UT99 1on1-rankin in particular sits at a comfortable 50+ fps even with bots and weapon effects on screen.

Half-Life is the dark horse: the engine runs the OpenGL path through 3dfx's miniGL wrapper, which behaves like Glide internally on Voodoo2. The 70 fps in trainstation is the highest sustained frame rate of any title we benchmarked.

Spec delta — Voodoo2 SLI vs neighbors

The takeaway: SLI is roughly halfway between a Voodoo3 3500 and a Voodoo5 5500 in raw fillrate, but only in Glide. In D3D and OGL the Voodoo3 typically wins per dollar because of architectural improvements and the absence of the SLI compositor overhead. SLI is a Glide-specific buy.

Which games actually benefit from SLI vs running fine on a single card?

The 60-second mental model: if the title's box mentions "3dfx Glide" or "3D accelerated" with a Glide logo, expect 50-90% SLI scaling. If it's a D3D-only or 2D title, SLI does nothing. There's no automatic fallback — a Glide-unaware game runs entirely on the 2D card.

What are the most common SLI install gotchas?

Five failure modes account for almost every "Voodoo2 SLI doesn't work" thread on Vogons:

1. Ghost devices in Device Manager. After a failed driver install, Windows 98 SE leaves stale Voodoo2 entries in the registry under HKLM\Enum\PCI\. The fix: boot into Safe Mode, expand Display Adapters and Other Devices in Device Manager, delete every 3dfx entry (including ghosts shown as grayed-out), reboot, let PnP rediscover, point at the INF.
2. Glide2x.dll conflicts. If you've previously had a Voodoo3, Voodoo4, or Voodoo5 installed in this Windows install, the system Glide2x.dll in C:\Windows\System is from the later card — and it doesn't work for Voodoo2. The 3dfx 3.02.02/3.03.00 installer should overwrite it, but only if no app has the DLL locked. Reboot before installing if you've recently run any Glide title.
3. AGP 2D card refresh-rate fights. Matrox G400 with Powerstrip can fight Voodoo2's pass-through over preferred refresh rates. The pass-through is analog — it preserves whatever the 2D card outputs. Always set 2D card to 85Hz @ 1024×768 minimum so Voodoo2 inherits a stable timing base. Lock refresh in Powerstrip, not in the Matrox driver.
4. IRQ steering exhaustion. With Voodoo2 + Voodoo2 + AGP 2D card + sound card + NIC, you can run out of PCI IRQ steering on a budget BX board. Symptom: the second Voodoo2 disappears after a warm reboot but reappears after cold boot. Fix: enable PnP OS in BIOS (or disable, depending on board — try both), or move the NIC to PCI slot 3 to free up PIRQ-A.
5. Power-on order. On some marginal builds the second Voodoo2 only initializes if power-good comes up cleanly. A flaky AT-to-ATX adapter or a marginal PSU rail can cause one card to drop out. Symptom: 3dfx Tools shows "1 Voodoo2 detected" instead of 2. Fix: known-good PSU or reseat the secondary card.

Verdict matrix

• Get a single Voodoo2 12MB if you mainly play Glide titles at 800×600 and want a budget retro 3D box. Single card runs $90-140 on eBay; SLI doubles your buy-in for fillrate you may not need at the resolutions Tomb Raider, NFS3, and Carmageddon 2 actually run at.
• Get Voodoo2 SLI if you specifically want 1024×768 in Glide titles, plan to play UT99 and Q3 demo loops, or are restoring a documented late-1998 / early-1999 build for archive purposes. SLI is also the right buy if you have a working pair from a friend's old PC and just need to learn how to drive them.
• Get a Voodoo3 3500 instead if you want a single-card solution that does Glide and D3D and TV-out, plays well outside the strict period-correct window, and saves a PCI slot. The Voodoo3 also runs at 22-bit color (post-filter), which looks subtly better than Voodoo2's hard 16-bit.
• Get a Voodoo5 5500 instead if you want T-Buffer effects (motion blur, FSAA), 32-bit color, and don't mind paying $260-450 for a card with notoriously power-hungry behavior on period PSUs.

Performance per dollar

Two ways to score this — original 1998 dollars, and 2026 eBay dollars.

Voodoo3 3500 wins both periods on raw $/fps — but loses the period-correctness battle for 1998-era builds, and (importantly) doesn't feel like a 1998 SLI rig. SLI's premium in 2026 is roughly $1.50-$2.00 per Quake 3 frame over a single card. For a build whose entire point is being a Voodoo2 SLI build, that's the toll.

Bottom line

Voodoo2 SLI is, in 2026, less a performance choice and more a heritage choice. You buy two Voodoo2 12MB cards because the configuration is the canonical late-1998 enthusiast build, because Glide-native titles render frame-accurately on the original silicon, and because a working SLI pair tells the rest of your retro fleet that you mean it. The setup is harder than a single-card install — driver picking, ribbon orientation, PnP-vs-installer pickiness, refresh-rate fights with the 2D card — but it's not impossible, and once it's running it's stable in a way only fixed-function 1998 silicon can be. Spend the $200-340 on a clean working pair, pair them with a Matrox G400, run 3dfx 3.03.00, and don't fight the 1024×768 ceiling — it's the resolution Glide titles were tuned for, and your benchmarks will reward you for staying on the rails.

Related guides

• Voodoo 3 3500 TV vs Voodoo 5 5500: Which Late-3dfx Card Should You Hunt For in 2026?
• Period-Correct Windows 95 Pentium MMX Build Guide: 3dfx Voodoo 1, AWE32, and Authentic 1996 Gaming
• 2000s LAN Party, Modern Build: Period-Correct Hardware That Still Boots in 2026
• Sound Blaster AWE32 vs AWE64 Gold: Which Wavetable Card Belongs in Your DOS Build?
• Building a Period-Correct Windows 98 Gaming PC in 2026

Sources

• Falcon's Voodoo Stash — 3dfx reference driver archive (3.02.02, 3.03.00)
• Vogons forums — Voodoo2 SLI install gotchas and driver-version threads
• Anandtech 1998 Voodoo2 SLI launch review (anandtech.com archives)
• Tom's Hardware 1998 3D card roundup (tomshardware.com archives)
• 3dfx Interactive driver release notes (3.x reference series)
• techpowerup.com GPU database — Voodoo2 / Voodoo3 / Voodoo5 fillrate references