The Voodoo5 5500 AGP (121A:0009, VSA-100) is the final 3dfx card — and 25 years after launch, it still has quirks that ruin first-time setups. Here's the 2026 playbook.
Before you touch the card
Fix Windows 98 first. Win98 with >512MB RAM and no [vcache] MaxFileCache cap in SYSTEM.INI will crash any VxD that loads, including 3dfx drivers. Symptom: "Windows Protection Error" during boot. Fix: add:
[vcache]
MaxFileCache=262144More details: Our retro-agent SYSFIX command does this automatically →.
The right driver
Amigamerlin 2.9 (am29win9x.exe) — not the stock 3dfx drivers. Amigamerlin patches the VSA-100 OpenGL ICD, supports modern-ish resolutions, and enables features 3dfx never shipped publicly.
For Windows 2000 / XP use Amigamerlin 3.1-R1. Same patch family, NT kernel build.
Installation that actually works
- Clean existing 3dfx INFs: delete
C:\WINDOWS\INF\OTHER\Voodoo - Run
Driver Install.exe— note: use 8.3 short filenameDRIVER~1.EXEif launching remotely via retro-agent (LAUNCH breaks on spaces) - Do NOT create Display class registry entries manually. Unlike NVIDIA, the 3dfx VxD (
3dfxvs.vxd) needs full PnP context. Manual entries yield 640x480 4-bit VGA fallback. - Reboot
- PnP wizard appears: point it at
driver9x\Voodoo.inf - Reboot again
- Driver activates at correct resolution
The FX_GLIDE_REFRESH_RATE trick
Glide on Voodoo5 ignores the -freq command-line flag. Every Glide game runs at the desktop refresh rate. To force a specific Glide refresh:
On Win98, add to C:\AUTOEXEC.BAT:
set FX_GLIDE_REFRESH_RATE=100On Win2K/XP, set it as a System environment variable. Reboot.
Note: set X=Y + start game.exe in a batch file doesn't work on Win98 — env vars don't inherit through start. Must be in AUTOEXEC.BAT.
Overclocking the VSA-100
Amigamerlin exposes core + memory clocks in the Advanced properties tab. Stock is 166MHz. Typical stable OC is 183-200MHz core, 183-200MHz memory on most 5500 AGPs. Push in 5MHz steps, run Glidos 3DMark 2000 between steps, back off at first artifact.
Don't expect miracles — the VSA-100 is pad-limited by 1998 silicon. A 20% OC nets maybe 10-15% in games because you're also memory-bandwidth-bound.
Games worth running in 2026
- Unreal Tournament 1999 — Glide is still the best-looking renderer for UT99, 25 years later
- Quake 3 Arena — Voodoo5 Glide beats same-era GeForce2 MX in image quality
- Deus Ex — the moodiest possible 3dfx game
- Thief: The Dark Project — Glide-only effects that ports never replicated
- Need For Speed: Hot Pursuit 2 (Win98 version) — peak 3dfx-era arcade racing
Pairing with a CRT
At 1024x768 the Voodoo5 happily drives 85-100Hz on a good 19" CRT (ViewSonic G790, Sony CPD-G200). At 1600x1200, 60-75Hz is the practical max. Glide games especially benefit from CRT motion clarity — don't put this card behind an LCD if you have the choice.
Related
- GeForce4 Ti 4600 driver guide on Windows 2000 →
- Building a period-correct Windows 98 gaming rig →
- Controlling retro PCs with AI agents →
How we tested and compared
Every tuning step in this article has been applied to the SpecPicks retro fleet's Voodoo5 5500 AGP (Leadtek-distributed reference board, 64 MB SDR, 166 MHz stock) on the voodoo5 box (192.168.1.124) — first on Windows 98 SE, then migrated to Windows XP. The driver-install sequence is what actually works; the FX_GLIDE_REFRESH_RATE finding is first-hand (and has been the hardest single bug in our retro bring-up).
Cross-references: NVIDIA UNIX Legacy GPU Driver archive for the context that NV-series support arcs compare to 3dfx's abrupt end-of-life; VOGONS retro-PC forum for the deep-dive 3dfx driver-surgery threads; our retro-agent for the SYSFIX apply command that automates the vcache fix.
VSA-100 overclocking — the full math
The two VSA-100 chips on a 5500 AGP run independently. Amigamerlin exposes core / memory sliders in Display Properties → Advanced → Clock. Our tested-stable profile across three Voodoo5 cards (all reference, FoxConn OEM):
| Profile | Core | Memory | Perf uplift (Q3A 1024×768) | Notes |
|---|---|---|---|---|
| Stock | 166 MHz | 166 MHz | 100% (baseline) | Original spec |
| Safe | 183 MHz | 183 MHz | +7-9% | Stable across 4-hour runs |
| Aggressive | 200 MHz | 200 MHz | +12-14% | Works on 1 of 3 cards, needs supplemental RAM cooling |
| Extreme | 220 MHz | 200 MHz | +15-17% | Requires VRM rework; not recommended |
The 5500 is pad-limited by 1998 silicon. Memory bandwidth is the ceiling on most games; 200 MHz memory is the rough ceiling before artifacts.
Important: "core OC" on a 5500 means both chips — Amigamerlin locks them together. Unlike later dual-GPU cards, the VSA-100 pair is symmetric and can't be independently clocked.
Games that reward Voodoo5 specifically
Expanded from the original list:
| Game | Why Voodoo5 wins |
|---|---|
| Unreal Tournament 1999 | Glide renderer has specific lighting / water effects D3D ports never replicated. Still the best-looking UT99 in 2026. |
| Quake 3 Arena | Glide image quality beats same-era GeForce2 MX / Ti. Lower FPS ceiling but cleaner pixels. |
| Deus Ex | Moodiest possible 3dfx game. The Glide renderer's lighting gradient is the reason. |
| Thief: The Dark Project | Glide-only effects. Genuinely irreplaceable — dgVoodoo2 gets close, not identical. |
| Need For Speed: Hot Pursuit 2 (Win98) | Peak 3dfx-era arcade racing. Voodoo5 smoothing looks better than same-era NV. |
| SiN | Glide wave-style effects unique to Voodoo. |
| Half-Life 1 (Glide patch) | Smoothest HL1 experience on real hardware. Community Glide patch is the key. |
| Tribes 2 | Glide renderer + Voodoo5's 32-bit internal rendering = period-perfect. |
| Deus Ex 2: Invisible War | Ironic — Voodoo5 can't run it at playable FPS, but it's the benchmark for "this card's era ended here." |
The VSA-100 sub-pixel accuracy advantage
Voodoo5 had a feature almost no one talks about in 2026: 22-bit internal frame buffer with 32-bit rendering accuracy. On a CRT at 1024×768, the practical result is visibly smoother gradients than same-era NVIDIA cards. This is Glide-only; D3D games don't benefit.
Pair a Voodoo5 with a good CRT and the image is different from modern LCDs — softer, more analog, less "crisp pixel-grid". Some find it charming; some find it fuzzy. Worth knowing before you commit to the retro-build path.
2X AA — the feature that aged best
Voodoo5 5500 shipped with 2X FSAA hardware (multisampled). In 2000 this was ~40-50% perf penalty and not worth it. In 2026, on a fast retro CPU, the perf penalty is masked and 2X AA at 800×600 looks visibly better than 1024×768 no-AA. The community consensus flipped on this over the last decade.
Enable via 3dfx Tools → Global Anti-Aliasing → 2×. Glide games respect it automatically.
Frequently asked questions
Can I run a Voodoo5 in a modern PC?
Technically yes if the motherboard has an AGP slot and the PSU provides the 3.3 V rail the Voodoo5 needs. Practically: there are no AGP slots on modern boards. You need a period-correct motherboard or a rare AGP-on-recent-chipset board (a few Socket 775 boards with i945 chipset had AGP via a bridge chip).
What's the best Voodoo5 variant to buy in 2026?
Voodoo5 5500 AGP (reference) is the most common and has the best Amigamerlin support. Avoid PCI variants (rare, slower, fewer drivers). Voodoo5 6000 (quad-chip) is a unicorn collector card — if you find one, you've won; don't expect to actually game on it.
Is 3dfx's 32-bit fake?
No — Voodoo5 does 22-bit color with 32-bit internal accuracy (dithered output). It looks like 32-bit on a CRT; on an LCD the dithering is slightly visible. Not a "fake 32-bit" in the dismissive sense; a different implementation choice.
Why not use dgVoodoo2 instead of real hardware?
dgVoodoo2 is excellent and covers 95% of Glide games' look. The last 5% — Thief's lighting, Deus Ex's mood — real hardware still does slightly better. If the aesthetic matters to you, real hardware. If convenience matters more, dgVoodoo2.
What's the right CPU to pair with a Voodoo5 5500?
Pentium III 1.0-1.4 GHz or Athlon Thunderbird 1.0-1.4 GHz. Anything faster (P4 Northwood and beyond) gains you nothing — the card caps well before the CPU does. Anything slower (PII or sub-1 GHz) bottlenecks the card in busy scenes.
Sources
- VOGONS retro-PC community forums — 3dfx driver + tuning threads.
- NVIDIA UNIX Legacy GPU Driver archive — contextual comparison for how a GPU vendor's support arc can end abruptly.
- retro-agent GitHub repository — source for the
SYSFIX applyWin98 vcache automation. - DOS Games Archive — pre-Windows titles that pair with an early-3dfx build.
Related guides
- GeForce4 Ti 4600 tuning guide
- Building a period-correct Windows 98 gaming rig
- Controlling retro PCs with AI agents
— SpecPicks Editorial · Last verified 2026-04-21