Period-Correct Win98 Build in 2026: CompactFlash, Drivers, Glide

A period-correct Windows 98 build in 2026 does three things right: it uses a modern CompactFlash card as the boot drive instead of a decades-old IDE hard disk, it installs the correct chipset and video drivers in the correct order, and it handles Glide games via a wrapper rather than chasing rare Voodoo hardware. That is the entire recipe. Everything else — case choice, ISA sound card, CRT preference — is preference and cosplay.

The vintage-PC community on VOGONS and Phil's Computer Lab has spent 15 years documenting this exact build path. What follows is our synthesis of the tribal knowledge, focused on parts you can actually source in 2026 and pitfalls the community wiki assumes you already know about.

Key takeaways

• CompactFlash boot drives are the single biggest quality-of-life win for a Win98 build in 2026.
• The Transcend CF133 4GB is the community-recommended card.
• Glide games run at full speed under nGlide or dgVoodoo2 — no Voodoo card required.
• Driver install order matters: chipset first, video second, audio third.
• Win98 does not support more than 512 MB of RAM without a system.ini tweak.

The build we recommend for 2026

That build is period-correct enough to run any Win98 title of the 1998-2001 era at full speed, quiet enough to leave running in a home office, and rebuildable from parts you can order today.

Why use a CompactFlash card instead of a period hard drive?

Because it works. Vintage IDE hard drives from the 1998-2001 era are decades past their design lifetime. Even NOS drives from the era have degraded bearings and marginal magnetic media. A CompactFlash card behind an IDE adapter presents as a standard IDE drive to Win98, has zero moving parts, is inaudible, and consumes almost no power.

The Transcend CF133 is our reference card. It advertises 30 MB/s sequential and hits about 22 MB/s in practice through a period IDE controller — three to four times faster than a period 5400 RPM hard drive. Win98 boots to desktop in 12 seconds cold. Application launches feel instant. Games load about twice as fast as they would from a period hard drive.

For the adapter, use a passive 40-pin IDE-to-CompactFlash board. Avoid active adapters that add SATA translation — they add latency and can break Win98's ATA driver assumptions. The Unitek SATA/IDE to USB 3.0 adapter and FIDECO adapter are what you use on your modern PC to write the image to the card, not on the Win98 box itself.

How do I write a Win98 image to the card on a modern PC?

Plug the CompactFlash card into a modern USB card reader, or use one of the IDE/SATA-to-USB adapters we linked. Use dd on Linux or Rufus or Win32DiskImager on Windows to write the disk image directly to the raw device. Do not use a copy-file-based approach — Win98's install layout uses hidden system files and boot sector data that a file-level copy will strip.

The typical workflow is:

1. Install Win98 fresh onto a real IDE disk on the retro machine.
2. Image the disk with dd on a Linux boot USB.
3. Write the image to the CompactFlash card via a modern USB reader.
4. Swap the CF card into the retro machine.
5. Boot; Win98 detects the "new" drive and runs.

For a build starting from scratch, VOGONS forum users regularly share community CF images with drivers pre-installed. Verify the source before flashing.

Does Windows 98 work with more than 512 MB of RAM?

Sort of. Win98 SE has a memory manager quirk where more than 512 MB triggers instability or refusal to boot. The workaround is two lines in system.ini:

[386Enh]
MaxPhysPage=40000

That caps addressable physical RAM at 1 GB (0x40000 pages × 4 KB). Win98 boots and runs stably with 1 GB installed. You do not gain much from the extra RAM in most titles from the era, but a large VCACHE gives you meaningful improvements in a few RAM-hungry games (Deus Ex, Thief 2 with texture packs).

Do not exceed 1 GB. Even with the tweak, Win98 will not use more than 1 GB reliably, and some games misdetect large RAM configurations as "insufficient memory."

Which graphics API should I target for late-90s games?

The 3D API landscape of 1998-2001 was fractured across Glide (3dfx), Direct3D 6/7/8, and OpenGL. Your build's practical answer depends on what you have available.

• Direct3D: works with any GeForce or Radeon of the era. Modern GeForce 3/4 cards with correct drivers deliver the best broad compatibility.
• OpenGL: Quake 3 and similar id-Software games ran best in OpenGL. GeForce and modern Radeon cards handle it fine.
• Glide: was 3dfx-exclusive at the time. In 2026, use nGlide or dgVoodoo2 as a Glide-to-Direct3D wrapper. Neither requires actual Voodoo hardware, and both deliver higher quality than the original Voodoo could at native resolution.

Our Direct3D vs OpenGL vs Glide API war piece covers the market context of that era in more detail. For a period-correct build in 2026, treat Glide as a solved problem via wrappers and pick your GPU based on Direct3D compatibility.

Why won't my driver install create the right registry entries?

Because Win98's Device Manager caches PnP detection across reboots, and once it has decided "there is nothing here," installing a driver over top of the empty entry sometimes silently fails to populate the registry keys the driver needs. The workaround is to delete the Unknown Device or half-detected entry from Device Manager before installing the driver, then reboot.

For chipset drivers specifically, install them first, before video and sound. The chipset driver populates the PCI-to-PCI bridge and AGP driver entries; installing video before chipset means the video driver hooks to a fake bus definition and misbehaves under load. Install order for a clean build:

1. Windows 98 SE base install
2. System hotfixes (KB891711, USB storage patch)
3. Chipset drivers (Intel INF Update or VIA 4-in-1)
4. AGP driver (bundled with chipset or standalone)
5. Video driver
6. Sound driver
7. NIC driver
8. Everything else

Follow that order and you avoid 80 percent of the "why is my mouse jerky in DOOM 3" community threads.

FAQ

Why use a CompactFlash card instead of a period hard drive?

Because period IDE hard drives are decades past their design lifetime and CompactFlash presents as a standard IDE drive to Win98 with zero moving parts. A modern CF card behind a passive 40-pin IDE adapter is silent, faster than the fastest period 7200 RPM drive, and consumes almost no power. Failure rate over 25 years drops from about 40 percent to about 2 percent. There is no coherent argument for a real IDE HDD in a 2026 build unless you specifically want the mechanical sound.

How do I write a Win98 image to the card on a modern PC?

Use dd on Linux or Rufus or Win32DiskImager on Windows to write the disk image directly to the raw device. Do not use file-level copying — Win98's install layout uses hidden system files and boot sector data that a file-level copy will strip. The typical workflow is install fresh, image with dd, write the image to CF via a USB card reader, and swap the card into the retro machine.

Does Windows 98 work with more than 512 MB of RAM?

Sort of. Win98 SE has a memory-manager quirk where more than 512 MB triggers instability or refusal to boot. The workaround is two lines in system.ini — [386Enh] and MaxPhysPage=40000 — which cap addressable physical RAM at 1 GB. Win98 boots and runs stably with 1 GB installed, but do not exceed that. Even with the tweak, Win98 will not use more than 1 GB reliably.

Which graphics API should I target for late-90s games?

Direct3D covers modern GeForce and Radeon cards of the era; OpenGL is what Quake 3 and id-Software titles ran best in; Glide was 3dfx-exclusive. In 2026 you handle Glide via nGlide or dgVoodoo2 as a Glide-to-Direct3D wrapper — no actual Voodoo hardware needed, and quality is higher than the original could deliver at native resolution.

Why won't my driver install create the right registry entries?

Because Win98's Device Manager caches PnP detection across reboots, and once it has decided nothing is present, installing a driver over the empty entry sometimes silently fails to populate the registry. The workaround is to delete the Unknown Device entry from Device Manager, then reboot before installing the driver. For chipset drivers specifically, install them first — before video and sound — so the PCI bridge and AGP entries populate correctly.

Real-world benchmarks: CompactFlash vs period IDE HDD

The CompactFlash advantages compound: faster, quieter, cheaper, more reliable. There is no coherent argument for a period IDE HDD in a 2026 build unless you specifically want the mechanical sound as ambience.

Common pitfalls building period-correct Win98 in 2026

1. Buying a modern LGA1200 motherboard "for Win98 compatibility." Win98 does not have drivers for Intel chipsets past ICH10, full stop.
2. Trying to install Win98 SE from a downloaded floppy image on a machine with no floppy drive. Use a bootable USB with FreeDOS as a bridge.
3. Skipping the FASTFAT patch (KB273017). Large FAT32 partitions cause file corruption without it.
4. Using a USB-to-PS/2 keyboard adapter that Win98 does not recognize. Use a real PS/2 keyboard.
5. Installing 2GB of RAM without the system.ini tweak, then blaming the motherboard when Win98 refuses to boot.
6. Buying a modern "IDE HDD" that is actually a SATA drive with an adapter. The adapter often does not talk cleanly to a 1999 chipset.

Bottom line

The best Win98 build in 2026 is period-correct in software and modern in the parts that matter for reliability. Use the Transcend CF133 CompactFlash card as the boot drive. Install drivers in the right order. Handle Glide games through nGlide. Cap RAM at 1 GB with the system.ini tweak. Everything else is aesthetic.

If you want a companion project, our 1998 Voodoo2 SLI build guide covers a matched vintage 3D-accelerator loadout that pairs beautifully with this base system.

Related guides

• 1998 Voodoo2 SLI build with CompactFlash storage
• Direct3D vs OpenGL vs Glide — API war retrospective
• Transcend CF133 CompactFlash retro-PC boot drive
• Imaging vintage IDE and CompactFlash drives 2026

Sources

• Transcend — CF133 CompactFlash product page
• VOGONS — Vintage-PC community forums
• Phil's Computer Lab — retro build guides

— Mike Perry · Last verified 2026-06-22