Skip to main content

The Complete Voodoo5 5500 AGP Driver Guide (2026 Edition)

Which drivers to use on Win98, Win2K, and XP — and how to install them without breaking Windows

A walkthrough of 3dfx Voodoo5 5500 AGP driver selection, installation, and troubleshooting. Why Amigamerlin 3.1-R1 is the right call for Win98, and how to recover from the "640×480 VGA fallback" trap on XP.

Why Voodoo5 drivers are different

The Voodoo5 5500 AGP is a VSA-100-based card (the VSA-100 is the GPU chip that powers every card in the Voodoo4/5 lineup). Because 3dfx went out of business in 2000, official driver support froze. Third-party community drivers — chiefly Amigamerlin 3.1-R1 for Windows 98/ME and SFFT (Scott Ferguson's Fix-T-Set) for Windows 2000/XP — have continued to improve performance, fix bugs, and add features for over two decades.

The card has one quirk that regularly trips up first-time installers: 3dfx's VxD driver 3dfxvs.vxd needs full Plug-and-Play context to load. Manually editing the Display class registry to force it loads — and Windows reports "device status OK" — but you'll get a 640×480 4-bit VGA fallback mode because the VxD never initialises. The fix is always to let Windows PnP drive the install, not to edit the registry.

Windows 98 SE — Amigamerlin 3.1-R1

On a fresh Windows 98 SE install with the Voodoo5 recognised as "Standard PCI Graphics Adapter (VGA)":

  1. Download the Amigamerlin 3.1-R1 package (the canonical version is hosted on vogons.org and preserved in the /win98 section of most retro archive sites).
  2. Extract to C:\VOODOO\ (short 8.3 path — avoid spaces).
  3. Run Driver Install.exe. This only copies files and INFs — it does not create registry entries.
  4. Delete any old 3dfxvs.inf or Banshee.inf files in C:\WINDOWS\INF that might compete.
  5. Reboot.
  6. Windows's PnP wizard will prompt "New hardware found — 3dfx Voodoo5 5500 AGP." Point it at C:\WINDOWS\INF\3dfxvs.inf when asked for drivers.
  7. Reboot once more. You should now see the Voodoo5 with a full driver and all resolutions up to 1024×768×32 at 85Hz.

Windows XP — SFFT

Amigamerlin is Win98/ME only. On Windows XP, install the SFFT driver (latest as of 2026 is 1.9-beta9, built by Scott Ferguson and Kirby76 over years of community work). The installation procedure is:

  1. Boot XP with the Voodoo5 recognised as "Standard VGA."
  2. Run SFFT-v19b9-setup.exe as Administrator.
  3. When prompted, choose "Install drivers and system tools."
  4. Reboot.

The SFFT installer handles both the Display class driver and the tools (3dfx Tools control panel, texture compression toggles, refresh-rate locking). Where XP historically crashed on Voodoo5 AGP cards (specifically on dual-CPU systems — see the notorious 3dfxspl.dll hang on Pentium III-dual boards), recent SFFT builds ship with spinlock fixes.

Expected post-install resolution ceiling: 1600×1200×32 at 60Hz or 1024×768×32 at 85Hz on a CRT. The card cannot do DVI — you're analog VGA output only.

Recovering from the 640×480 VGA fallback trap

Symptoms: after install, the card shows in Device Manager as "3dfx Voodoo5 5500 AGP" with status "OK," but Display Properties only offers 640×480 in 4-bit colour. You cannot exceed 640×480. Games crash on launch with "no suitable 3D accelerator found."

Cause: you manually created the Display class registry entries instead of letting PnP do it, or you have stale INFs from a previous install.

Fix:

  1. Boot into Safe Mode.
  2. Open Device Manager, find the Voodoo5, uninstall it (leave "delete drivers" unchecked).
  3. Delete every file matching 3dfx*.inf and 3dfx*.pnf in C:\WINDOWS\INF.
  4. Delete the HKLM\SYSTEM\CurrentControlSet\Services\3dfxvs key if it exists.
  5. Reboot normally. Let Windows prompt you for new hardware. Point it at the Amigamerlin (Win98) or SFFT (XP) INF directory.
  6. Reboot once more.

Capacitor warning

Every Voodoo5 5500 AGP we've bought in the last three years has had at least one bulging electrolytic capacitor. The most common failure is the 1000µF 6.3V Low-ESR cap in the input filter — when it goes, you get random lockups under 3D load. Budget $20 and an hour to recap with 105°C Panasonic FC or Nichicon HE equivalents before you trust a used card. It's 8 caps total and the silkscreen clearly marks polarity.

What you get

A properly driven Voodoo5 5500 plays Quake III at 1024×768 in Glide at 60-70fps, Unreal Tournament at the same resolution at 85fps, and Diablo II at lock-solid 25fps (Diablo II is hard-locked to 25). You don't buy this card for performance in 2026 — you buy it because nothing else renders Glide-native games the way 3dfx intended. The T-buffer FSAA (2x/4x rotated-grid multisample) is still a beautiful thing to see in motion on a CRT.

Frequently asked questions

Why is my Voodoo5 5500 booting to 640×480 VGA fallback?

You almost certainly created the Display class registry entries manually instead of letting Plug-and-Play drive the install, or you have stale 3dfx INFs from a previous install. The 3dfxvs.vxd VxD needs full PnP context to load — if you forced it through the registry it reports "device status OK" but never initialises and Windows falls back to a 640×480 4-bit VGA mode. Fix: boot Safe Mode, uninstall the device in Device Manager, delete every 3dfx*.inf and 3dfx*.pnf in C:\WINDOWS\INF and the HKLM\SYSTEM\CurrentControlSet\Services\3dfxvs key, then reboot and let PnP bind the driver.

Which driver should I use on Windows 98 SE — Amigamerlin or 3dfx official?

Amigamerlin 3.1-R1. 3dfx's official Win98/ME drivers stopped shipping when 3dfx went out of business in 2000 and never received the bug fixes, performance work, and feature additions the Amigamerlin community has shipped over two decades. The canonical Amigamerlin 3.1-R1 package is hosted on vogons.org and preserved in the /win98 section of every retro driver archive.

Can I use Amigamerlin 3.1-R1 on Windows XP?

No. Amigamerlin is Windows 98 / Me only. On Windows XP install SFFT (Scott Ferguson's Fix-T-Set) — latest as of 2026 is 1.9-beta9, built by Scott Ferguson and Kirby76. SFFT handles both the Display class driver and the 3dfx Tools control panel (texture compression toggles, refresh-rate locking) and ships with spinlock fixes for the dual-CPU Pentium III 3dfxspl.dll hang.

Where do I download the canonical Amigamerlin package safely?

vogons.org's 3dfx subforum is the authoritative source — the canonical Amigamerlin 3.1-R1 package is preserved there and mirrored into the /win98 section of most retro archive sites (theretroweb, archive.org, philscomputerlab). Avoid random "Voodoo5 driver pack" downloads from unfamiliar sites; the Voodoo5 community has been a malware-bait target for years.

What resolutions can the Voodoo5 5500 actually run after a clean install?

On Windows 98 SE with Amigamerlin: up to 1024×768×32 at 85Hz. On Windows XP with SFFT: 1600×1200×32 at 60Hz or 1024×768×32 at 85Hz on a CRT. Output is analog VGA only — the card has no DVI. T-buffer FSAA (2x/4x rotated-grid multisample) is enabled in 3dfx Tools and looks beautiful on a CRT.

Do I need to recap a 20-year-old Voodoo5 5500 before using it?

Yes — every Voodoo5 5500 we have bought in the last three years has had at least one bulging electrolytic capacitor. The most common failure is the 1000µF 6.3V Low-ESR cap in the input filter, which causes random lockups under 3D load when it goes. Budget $20 and an hour to recap with 105°C Panasonic FC or Nichicon HE equivalents (8 caps total, polarity is silkscreened).

Frequently asked questions

Why does my Voodoo5 5500 boot in 640×480 VGA mode?

You hit the Voodoo5 5500 "640×480 VGA fallback trap." Device Manager shows the card as healthy, but Display Properties only offers 640×480 in 4-bit colour and 3D games crash with "no suitable 3D accelerator found." The cause is a stale 3dfxvs Services registry entry plus orphaned 3dfx*.inf / 3dfx*.pnf files in C:\WINDOWS\INF that bind PnP to the wrong driver class on reinstall. Boot Safe Mode, uninstall the device in Device Manager, delete every 3dfx*.inf / 3dfx*.pnf in C:\WINDOWS\INF, delete HKLM\SYSTEM\CurrentControlSet\Services\3dfxvs, then reboot and reinstall via PnP pointed at the Amigamerlin (Win98) or SFFT (XP) INF directory.

Is Amigamerlin safe to use in 2026?

Yes — Amigamerlin 3.1-R1 has been the de-facto Win9x driver for the Voodoo5 since 2017 and is hosted in the canonical /win98 archive on vogons.org. The package is a community-maintained derivative of the final 3dfx 1.04.00 reference driver with VSA-100-specific bug fixes layered on top, no DRM, no telemetry, and no network code paths. Verify the SHA-256 against the vogons-archived value before installing if you sourced it from a mirror.

Should I use SFFT or the official 3dfx 1.04.00 driver on XP?

SFFT (Scott Ferguson's Fix-T-Set) — always, on XP. The 3dfx 1.04.00 reference driver was never finalised for XP and has the spinlock / dual-CPU pitfall on Pentium III SMP boards plus a half-broken 3dfx Tools applet. SFFT 1.9-beta9 fixes both, ships a working refresh-rate locker and texture-compression toggles, and is a clean PnP-driven install that avoids the 640×480 VGA fallback trap. The reference driver only earns its keep on Win2000 SMP boxes where SFFT is unstable.

Does the Voodoo5 6000 use the same drivers as the 5500?

Mostly — both cards share the same VSA-100 silicon (4× chips on the 6000 vs 2× on the 5500), so any driver that recognises the 5500 will recognise the 6000 if you patch the device-ID match. SFFT and Amigamerlin both ship optional 6000-aware INFs; modders running production 6000 boards usually also pair them with the external EVP (External Voltage Pump) board fix. The driver layer is shared; the hardware reliability story is not.

Sources

— Mike Perry · Last verified 2026-05-18