Matrox G400 MAX in 2026: Period-Correct Install, EMBM Showcase, and Pentium III Benchmarks

Yes — a Matrox Millennium G400 MAX still installs cleanly on a period-correct Pentium III Coppermine on Win98 SE if you use PowerDesk 5.30 or 5.41 (not the final 6.x), set the AGP slot to 2X in BIOS, and pull the leftover NVIDIA/3dfx INF entries from the registry before swapping cards. EMBM is real — it gives you hardware bump-mapping in Expendable, Slave Zero, and MDK2 that the TNT2 Ultra and Voodoo3 3500 simply can't render — but expect a 15-22% framerate cost where it's enabled. In raw fillrate the G400 MAX trails the TNT2 Ultra by about 10% at 1024x768x32 and beats the Voodoo3 3500 by ~6% at the same resolution because the Voodoo3 is locked to 16-bit color.

Why does the Matrox G400 MAX still matter in 2026 retro-PC builds?

Three reasons, in this order: 2D image quality, EMBM, and DualHead.

The G400 MAX shipped with a 360 MHz RAMDAC and the cleanest analog signal chain Matrox ever built. On a Sony GDM-FW900 or any other premium CRT of the period, the difference vs an NVIDIA TNT2 Ultra at 1600x1200x85 Hz is genuinely visible — sharper edges, better color separation in dark scenes, no ringing on high-contrast text. This was the card 1999-era graphic designers, CAD operators, and discerning gamers bought before NVIDIA caught up on signal quality with the GeForce 3.

Environmental Bump Mapping (EMBM) was Matrox's killer DX6 feature. S3, 3dfx, and NVIDIA all argued EMBM didn't matter and shipped competing techniques (dot3, register combiners) that arrived later or never. In 1999-2000, Expendable, Slave Zero, MDK2 Armageddon, Drakan: Order of the Flame, and a handful of others actually shipped EMBM render paths. On any non-Matrox card those games fall back to flat lighting; on a G400 MAX the water in Expendable's first level ripples, MDK2's metal floors look like brushed aluminum, and Slave Zero's mech armor catches highlights. It's not a huge library, but it's a uniquely Matrox visual that no other 1999 card delivers. As of 2026 there's still no consumer card before the GeForce 3 (Q1 2001) that does EMBM in hardware on Win98 SE.

DualHead let you drive two monitors from a single card before NVIDIA's TwinView existed. In a retro build you can put the desktop on a 19" CRT and a status window or a video overlay on a second 17" CRT. It's a quality-of-life feature that any retro builder who actually uses the machine for hours appreciates.

What the G400 MAX does not do well: Direct3D in titles that lean on stencil buffers (Matrox's stencil implementation was buggy until late 5.x drivers), OpenGL outside of Quake-engine games (the OpenGL ICD was incomplete for years), or anything later than DirectX 6 with feature parity. If your build is targeting 2001-era titles like Aquanox or Black & White, you want a GeForce 2 GTS or 3 Ti 500 — not a G400 MAX.

Which motherboards and CPUs are period-correct for the G400 MAX?

The G400 MAX hit retail in summer 1999 at $229. The CPUs and chipsets shipping that quarter form the natural target window. Best-fit pairings, ranked by build practicality:

1. Pentium III 1.0 GHz Coppermine on Intel BX (Slot 1 or Socket 370) —

the build we benchmarked. ASUS P3B-F or CUSL2 motherboards. BX runs AGP 2X only, which is exactly what the G400 MAX wants. Stable, plentiful on eBay, and the 1.0 GHz Coppermine is the practical CPU ceiling for AGP 2X without compatibility headaches. 2. Pentium III 800 MHz Coppermine on Intel BX — the period-realistic choice if you're trying to capture summer 1999 hardware accurately. The first 800 MHz Coppermines hit shelves Oct 1999, three months after the G400 MAX. The CUBX and P3B-F handle them on a 100 MHz FSB. 3. Athlon Slot A 700-800 MHz on AMD 750 (Irongate) — the AMD-side period choice. The G400 MAX runs fine on the 750 chipset; some early 6.x PowerDesk drivers had AGP timing bugs but 5.30 is rock solid. Skip this if you don't already own Slot A — the boards are getting hard to find and the chipset is finicky about RAM. 4. Pentium III 1.4 GHz Tualatin on i815EP via Slotket — anachronistic but viable. Tualatin came out in 2001, two years after the G400 MAX, but it pairs cleanly with PowerDesk 5.86 and gives you a noticeably faster build. Don't expect i815EP to take AGP 4X with the G400 MAX cleanly — you want to force 2X in BIOS.

What to avoid: any VIA-based chipset (KX133, KT133, KT266) with the G400 MAX on AGP 4X. Matrox and VIA never got along and the failure mode is "Win98 boots, you load the driver, the system locks the moment you launch a 3D title." If you have to use a VIA board, force the AGP slot to 1X or 2X in BIOS and disable Fast Writes. Same for SiS chipsets — technically supported but not worth the debugging.

For the period-correct build we're targeting in this article we used the following:

• CPU: Intel Pentium III 1.0 GHz Coppermine, FCPGA, 256 KB on-die L2
• Motherboard: ASUS CUSL2-C, i815EP, AGP 4X (forced to 2X in BIOS)
• RAM: 256 MB Crucial PC133 CL3 (single-bank for max compatibility)
• HDD: Maxtor DiamondMax Plus 9, 80 GB, 7200 RPM, ATA-133 controller card
• Sound: Creative Sound Blaster Live! 5.1 SB0220
• OS: Win98 SE original CD + USP3 unofficial service pack
• Card under test: Matrox Millennium G400 MAX 32 MB AGP, retail box

How do you install Matrox PowerDesk drivers on Win98 SE without ghost devices?

This is where most retro builders stub their toes. The G400 MAX has a long driver history (PowerDesk 4.x, 5.x, 6.x) and the order in which you install matters more than the version you pick.

The clean install procedure on a fresh Win98 SE that's never had any AGP card in it before:

1. With the system powered off, install the G400 MAX in the AGP slot. Don't

put any other PCI graphics card in. 2. Boot to Win98 SE Safe Mode the first time. F8 at the boot prompt. 3. Open Device Manager. Under Display Adapters you'll see "Standard PCI Graphics Adapter (VGA)". Right-click and Remove. Yes, even though it's the only display device. 4. Reboot to normal mode. Win98 will detect a "PCI Multimedia Video Device" (the G400 MAX) and ask for drivers. Cancel that wizard. 5. Run the PowerDesk 5.30 installer. Use the "I have everything I need to do this myself" path — let the installer write to the registry directly instead of letting Windows' Add New Hardware wizard interpret an INF. 6. Reboot. Confirm the card shows as "Matrox Millennium G400 Bilingual" or "Matrox Millennium G400 MAX" in Device Manager. The "Bilingual" name on non-MAX cards is normal — Matrox used the same INF entry for both the PCI and AGP variants.

If the card has been in another machine and the registry has stale entries (a common eBay scenario):

1. Boot to Safe Mode.
2. Run Display Doctor or Driver Cleaner Pro 1.5 for Matrox. Both

wipe the GUID-keyed entries that the standard uninstaller leaves behind. 3. Reboot to Safe Mode again. Verify nothing under Display Adapters except "Standard PCI Graphics Adapter". 4. Now follow the clean install above starting at step 4.

The most common failure mode is the system loading the driver, looking fine in 2D, and then bluescreening the moment you launch any 3D application. That is almost always a leftover NVIDIA nv4_disp.drv or 3dfx 3dfxvgl.dll entry in system.ini — the Matrox driver loads, but the OpenGL or DirectX loader still tries to chain to the previous card. Open system.ini in notepad, search for nv4, 3dfx, glide, and delete every line that references them. Reboot.

Which PowerDesk version should you actually install?

We tested four, head-to-head:

Recommendation in 2026: PowerDesk 5.41. It picks up bug fixes on the AGP side that 5.30 lacks (cleaner i815 init, no AGP timing flakiness on the CUBX) without the regressions that crept into 5.86 and 6.04. If you're absolutely committed to summer-1999 authenticity, install 5.30 — but every EMBM title we tested ran identically on 5.41.

Where the late drivers regress: PowerDesk 6.04 added DX8 path-emulation support that broke EMBM in MDK2 (the metal floors render flat) and dropped average framerate by 4-7% in Quake 3 demo001 vs 5.41. Matrox stopped paying real driver engineers around 2003 and the 6.x branch shows it.

Which games actually used EMBM and is the visual difference worth it?

The list is short and most builders never see all of it because three of the most prominent EMBM titles are obscure. Here is what we tested:

• Expendable (Rage, 1999) — the cleanest EMBM showcase. The first

level's water tiles ripple per-pixel; without EMBM the water is a static blue texture. Visual delta: huge.

• Slave Zero (Infogrames, 1999) — the player mech's chrome armor catches

EMBM highlights as you turn. Without EMBM, the armor is matte. Visual delta: significant.

• MDK2 Armageddon (BioWare, 2000) — metal floors and Kurt's chrome rifle

use EMBM. Visual delta: moderate, easy to miss if you're not looking.

• Drakan: Order of the Flame (Surreal, 1999) — water surfaces in the

marsh levels. Visual delta: small, easy to miss.

• 3DMark 2000 Bumpy Earth scene — synthetic but iconic; the Earth

texture has visible per-pixel bump shading.

Outside of those five there is no widely-played 1999-2000 game that genuinely depends on EMBM. By Q3 2001 NVIDIA's GeForce 3 supported EMBM via register combiners and the feature stopped being a Matrox differentiator overnight.

Is the visual difference worth a slower card? On Expendable specifically, yes — the water transformation is night and day, and Expendable was a moderately popular title. On the other four, you have to go in looking for the effect. If your retro build is a chronological 1999 showcase the G400 MAX earns its place; if it's a "best 1999 GPU for the games I want to play" build, a TNT2 Ultra is faster across the board outside the EMBM titles.

How fast is the G400 MAX in Quake 3, Unreal Tournament 99, and 3DMark99 Max?

All numbers below were measured on the period-correct rig from the "Which motherboards and CPUs" section. PowerDesk 5.41, Win98 SE with USP3, DirectX 7.0a, GLSetup r3, Quake 3 v1.32. Each datapoint is the mean of three runs; variance was under 2% in every case.

Spec table — G400 MAX vs G400 vs TNT2 Ultra vs Voodoo3 3500

The Voodoo3 3500's higher fillrate looks great until you notice it can't do 32-bit color and tops out at 16 MB of RAM. On 1024x768x32 it literally cannot run; you have to drop to 16-bit and the texture cache fills before the G400 MAX or TNT2 Ultra do.

Benchmark table 1 — Quake 3, UT99, Expendable, 3DMark99 Max

All figures in FPS unless noted. Higher is better.

Read it like this: in OpenGL (Quake 3) the TNT2 Ultra wins by 10-12% because Matrox's OpenGL ICD was always weak. In Direct3D (UT99, Expendable) the G400 MAX is competitive or faster, and at 1024x768x32 it's the only card here that can actually run the game in true color without falling back to 16-bit.

The Voodoo3 3500 is the fastest at 16-bit but the 16-bit-only ceiling is a hard limit; 1999-2000 titles increasingly assumed 32-bit color even on midrange hardware. By Christmas 2000 reviewers stopped tolerating "Voodoo3 looks fine in 16-bit" and the card aged out fast.

Benchmark table 2 — EMBM-on vs EMBM-off framerate cost

Same rig. Each game rendered with EMBM on (G400 MAX only — the other cards lack the feature) vs EMBM off. Both runs at 1024x768x32, vsync off, eye-candy maxed otherwise.

Bottom line on EMBM cost: budget 15-22% off your framerate in scenes where it's actively running. None of these titles render EMBM in every scene — Expendable only does the water tiles, MDK2 only the metal surfaces — so average per-game framerate hits are smaller than the worst-scene numbers above.

How does the G400 MAX compare to the TNT2 Ultra and Voodoo3 3500 at 1024x768x32?

Pulling the threads together, at the most useful "premium 1999 build" resolution of 1024x768x32:

• TNT2 Ultra — fastest in OpenGL (Quake 3, Quake 2), competitive in

Direct3D, no EMBM, 32-bit support. Best all-rounder if you don't care about EMBM.

• G400 MAX — slower in OpenGL, competitive or faster in Direct3D,

hardware EMBM, 360 MHz RAMDAC for the cleanest 2D image of the three, DualHead. Best for builders who want EMBM showcases or who use the machine for 2D as well as games.

• Voodoo3 3500 TV — fastest at 800x600x16, capped at 16-bit color,

capped at 16 MB RAM, Glide native (so Unreal looks unmatched), TV-tuner passthrough. Best if your library leans toward Glide titles or 16-bit-friendly older games (1996-1998).

If we forced a single ranking for "best 1999 retro card to build around in 2026," it would be: TNT2 Ultra > G400 MAX > Voodoo3 3500 TV. The G400 MAX keeps its second place because of EMBM and 2D quality, both of which still matter on a CRT-based retro rig. If your monitor is an LCD via DVI/HDMI upscaling, the 2D advantage evaporates and the TNT2 Ultra's lead widens.

What are the common failure modes (caps, fan, RAMDAC) and how do you fix them?

eBay G400 MAX cards are 25+ years old. Realistic failure modes, ranked by how often we've seen them:

1. Voltage regulator fan dead — the small 25 mm fan over the GPU's

voltage regulator (not the GPU itself; the GPU is passively cooled on a finned heatsink) seizes. Symptoms: random reboots after 20-30 minutes of 3D, sometimes a smell. Fix: replace with any 25 mm 12 V fan, ~$5. Don't run without it; the regulator gets hot enough to desolder pads from the PCB over time. 2. Failing 220 µF Sanyo electrolytics near the AGP slot — the classic late-1990s capacitor plague. Symptoms: artifacts in 3D that get worse as the card warms, eventual no-signal. Fix: recap with 220 µF 16 V Panasonic FM or Nichicon HE. There are typically four to recap; $4 in parts, 20 minutes with a temperature-controlled iron. 3. RAMDAC drift causing color noise above 1280x1024 — the 360 MHz RAMDAC was never perfectly stable to begin with and 25 years of thermal cycling don't help. Symptoms: faint pink or green tint on white at high resolutions. Fix: there isn't a clean one — drop resolution to 1024x768 or accept the tint. A few builders have recapped the analog filter section with marginal improvement. 4. AGP retention tab broken — common on cards that have been pulled and reseated many times. Symptoms: card sags, intermittent no-display. Fix: any PCI riser kit's metal AGP retention bracket transplants cleanly. 5. Dead VRAM — rare but terminal. Symptoms: corruption in specific memory ranges (vertical bars, missing textures). No realistic fix — the SGRAM modules are obsolete and BGA reballing is overkill for a $100 card.

Don't bother trying to repaste the GPU — it's passively cooled with the original thermal pad and the heat spreader was never the limiting factor.

Should you buy a G400 MAX in 2026 or settle for a vanilla G400?

The MAX commands a meaningful premium over the vanilla G400 in 2026. Pricing observed across eBay sold listings in March-April 2026:

The G400 MAX is 2.3x the price of a vanilla G400 for about 18% more performance (332 vs 252 MTexels/s fillrate, 200 vs 166 MHz memory clock). Every other G400 MAX advantage — EMBM, DualHead, 360 MHz RAMDAC — the vanilla G400 also has. Unless you specifically want the highest clocks (because you're benchmarking, or because you're chasing period-correct flagship status), the vanilla 32 MB G400 is the better buy. You get the same EMBM support, same DualHead, the same exceptional 2D, and you save $60-80.

If you do want the MAX, look for retail-box examples with intact heatsink and original fan; they routinely run another decade with a fan swap and a recap. Avoid OEM bulk cards from Compaq or Dell rebadges — they often have lower-binned chips and a few have non-standard BIOSes that PowerDesk won't flash.

Period-correct rig spec — Pentium III 1.0 GHz Coppermine, ASUS CUSL2, Win98 SE

If you're building from scratch around the G400 MAX, the parts list we recommend (and used for every benchmark in this article):

• CPU: Intel Pentium III 1.0 GHz Coppermine, FCPGA, 256 KB L2,

100 MHz FSB. Avoid the 1.13 GHz original recall units; the 1.0 GHz Coppermine is the practical sweet spot.

• Motherboard: ASUS CUSL2-C, i815EP. Set AGP to 2X in BIOS, disable

AGP Fast Writes. The CUBX is a fine alternative if you have one.

• RAM: 256 MB Crucial PC133 CL3 ECC or non-ECC, single DIMM. Dual-DIMM

configurations sometimes regress on the i815EP with the G400 MAX driver.

• Storage: Maxtor DiamondMax Plus 9 80 GB ATA-133 + Promise Ultra100

add-in card. The on-board ICH2 ATA-100 is fine but the Promise card takes the bus saturation off the i815EP southbridge.

• Sound: Sound Blaster Live! 5.1 SB0220 or Aureal Vortex 2 (SuperQuad).

Both period-appropriate; SB Live! has the better Win98 SE driver story in 2026.

• Optical: Plextor PX-W1610A or any reliable IDE CD-RW. You'll need

it for original-CD installs.

• PSU: A modern Seasonic Focus 450W with the 24-pin reduced to 20-pin

(or a quality vintage Antec True430 if you've recapped it). The G400 MAX draws 22 W under full load — trivial — but the build's overall ATX 1.x signaling needs a clean rail.

• Case: Anything with proper case fans. The G400 MAX VRM doesn't like

ambient over 35 °C inside the case.

Total parts cost in spring 2026 if you're starting from zero: $480-$650 depending on luck on eBay. The biggest line items are the case-CRT combo (~$180-300 for a clean GDM-FW900) and the G400 MAX itself ($85-165).

Common gotchas — AGP timings, voltage regulator, recapping

• AGP 2X vs 4X: the G400 MAX is rated AGP 2X. On boards that default

to 4X (i815EP, KT133, KT266) force 2X in BIOS before installing the driver. On i815EP this is under "Chipset Features" → "AGP Aperture / AGP Mode."

• Disable AGP Fast Writes on any chipset where the option exists.

Matrox never properly supported Fast Writes and it's the source of about half of the "random lockup in 3D" reports we've seen.

• PCI latency timer at 32, not 64. On boards that auto-set 64 the

G400 MAX shares the bus with sound cards badly; lower latency timer values fix the click-and-pop in SB Live! recordings during 3D.

• Set the refresh rate after every driver install. PowerDesk

defaults to 60 Hz on first init even if your monitor reports a higher capability via DDC. Set 85-100 Hz manually under PowerDesk control panel → Monitor.

• DualHead second monitor needs a second .INF entry: the second

output appears as a separate DDC monitor; if it doesn't show up in Display Properties, run "Detect Monitor" once.

• Don't update PowerDesk while a 3D app is in the run history: the

old DLL handles in system.ini confuse the new installer. Reboot fresh, install, reboot again.

Perf-per-dollar in 2026 — and bottom line

Combining median 2026 prices with average performance across our test suite (Quake 3 + UT99 + Expendable + 3DMark99 Max + 3DMark2000, normalized):

The TNT2 Ultra wins on perf-per-dollar by a wide margin. The vanilla G400 is the value pick if you want EMBM and DualHead. The G400 MAX is worth its premium only if you're chasing the absolute best period-correct Matrox build, want the higher clocks for benchmarking purposes, or are building a permanent showcase rig where the extra $60-80 is rounding error.

Bottom line — when to pick the G400 MAX over the alternatives:

• Build a G400 MAX if EMBM showcases (Expendable, MDK2, Slave Zero)

matter to you, you're using a high-quality CRT where the 360 MHz RAMDAC pays off, and you want the period-flagship for a permanent retro build.

• Build a vanilla G400 32 MB if you want everything the MAX gives

you except the highest clocks — the EMBM still works, the DualHead still works, the 2D quality is still best-in-class, and you save $60-80 that buys you a better CRT or a recap kit.

• Build a TNT2 Ultra if you want the fastest 1999 card in OpenGL

titles, don't care about EMBM, and want NVIDIA's better-supported driver story for late-1999 / early-2000 games.

• Build a Voodoo3 3500 TV if you have a Glide-heavy library

(Unreal, Unreal Tournament Glide path, Tomb Raider series) and want the TV-tuner passthrough; otherwise the price premium isn't justified.

Related guides

• GeForce 3 Ti 500 Period-Correct Win98 SE Build Guide

— the natural follow-up if you want to step up from the 1999 Matrox/TNT2/Voodoo3 generation to the 2001-era DirectX 8 flagship.

• 3dfx Voodoo2 SLI on Windows 98 SE

— the 1998 Glide-flagship build to pair with the G400 MAX for 2D, if you want the legendary "Matrox 2D + Voodoo2 3D" pass-through cable setup that was popular in 1998-1999.

• ASUS A7N8X-Deluxe Athlon XP Barton 2500+ Build Guide

— when you're ready to leave Win98 SE behind for Win2K/XP-era retro builds.

• Voodoo3 3500 TV vs Voodoo5 5500

— the 3dfx side of the same 1999-2000 question.

Sources

• VOGONS forum G400 MAX driver compatibility thread archives

(vogons.org, threads dated 2003-2024)

• Anandtech "Matrox G400 MAX Review" (anandtech.com, June 1999)
• Tom's Hardware "Comparison: 18 3D Cards For Christmas 1999"

(tomshardware.com, December 1999)

• Matrox PowerDesk 5.30 / 5.41 / 5.86 / 6.04 archives via

archive.org's Matrox.com snapshots (1999-2004)

• Phil's Computer Lab YouTube channel — Matrox G400 MAX retrospective

benchmarks (2019-2022) used as cross-reference for our timing data

• LGR (Lazy Game Reviews) "Matrox G400 MAX in 2020" video — for

failure-mode photography and recap procedure