Video summary

What's the fastest (officially supported) Windows 98 PC?

Main summary

Key takeaways

Technology

Summary: Fastest Windows 98–Supported PC Build (Tech Concepts & Findings)

Project goal

Build the fastest officially Windows 98–supported PC by using hardware from a “late window” period—when manufacturers were still shipping Windows 98–compatible components. The build deliberately prioritizes speed over maximum compatibility.

Core constraints / design choices

  • GPU interface: AGP

    • Stays with AGP because there are effectively no PCIe GPUs that provide direct Windows 98 benefits.
    • PCIe cards typically rely on an AGP-to-PCIe bridge, so there’s no meaningful speed/compatibility advantage for Windows 98.

  • CPU platform: Socket 775

    • Uses Socket 775, selecting a motherboard/chipset era that’s fast enough while still having workable Windows 98 drivers.

  • Motherboard CPU compatibility problem

    • Not all Socket 775 motherboards support all Socket 775 CPUs.
    • Compatibility depends on the motherboard’s CPU list/BIOS support.

Parts selection and rationale

Motherboard (key feature): ASUS P5PE-VM

  • Socket: 775
  • Graphics: AGP
  • Chipset: Intel 865G
    • Described as having “Windows 98–friendly” design choices.
  • Special requirement: Core 2 support
    • Needed to enable a faster CPU than a Pentium 4.

CPU attempt #1 (fails): Intel Core 2 Duo E8600

  • Model: E8600 (3.33 GHz)
  • Why chosen: Claimed to have top-tier single-threaded performance in Windows 98 benchmarking terms.
  • Failure cause:
    • The BIOS did not list/support the E8600.
    • Even with a BIOS update, support still didn’t match the E8600 release timing (update existed but predated the chip by months).

CPU downgrade (successful boot): Intel Core 2 Duo E6600

  • Model: E6600 (practical supported option)
  • Notes:
    • A faster “ceiling” option is mentioned: Core 2 Extreme X6800.
    • But it was considered too rare/expensive.
  • Net effect: still aims for “fastest possible” within real BIOS support.

GPU strategy: stability-first, then performance testing

Initial GPU: GeForce FX 5200 (AGP)

Not the ultimate choice, but used because:

  • High-end AGP cards were failing in the prior attempt.
  • The FX 5200 is common/cheap, reducing risk while troubleshooting the rest of the build.

Important finding: GPU choice strongly affects results

  • “Halo” was playable but limited.
  • Later, swapping to a rare AGP GeForce 6800 showed behavior that suggested:
    • Performance/visual behavior stayed similar enough to imply some bottlenecks were not purely GPU-limited.
    • The issues may instead be tied to drivers, textures, or settings.

RAM / storage / I/O approach

RAM

  • Dual-channel RAM requested.
  • Previously noted single-stick limitations, leading to a revised RAM setup.
  • Stability constraint: using >512MB can make Windows 98 unstable, so RAM configuration is adjusted accordingly.

Storage workflow

  • Windows 98 install: clean install planned.
  • Speed hack for installation: use an SSD for installer files
    • Copy the installer from CD to SSD to make installation extremely fast.
  • Drivers for external/modern storage:
    • NTFS support via Sysinternals tools (inject/enable NTFS access).
    • But NTFS write access is treated as risky/unstable, so storage for games/ISOs shifts to FAT32.

BIOS/boot flashing tooling

  • Old BIOS required external flashing.
  • Uses FreeDOS USB boot rather than floppy/DOS driver issues.

Windows 98 install, boot, and troubleshooting outcomes

First “doesn’t boot” stage: CPU incompatibility

  • With the E8600, the board wouldn’t boot.
  • BIOS POST happened only after swapping to a supported CPU.
  • Key lesson: even “perfect board + perfect CPU” can fail due to:
    • BIOS release timing
    • CPU support list limitations

Second major issue: system hangs / blue screens

  • Windows 98 installed quickly, but then failed to boot (freezes/blue screens).
  • Moral fix found: unplug the Blu-Ray drive
    • A multi-function IDE controller message about “corruption” appeared.
    • After reboot: system succeeded.

After it boots

  • Install mass storage drivers for flash drives.
  • Then successfully install sound and graphics drivers.
  • Driver resolution effects:
    • After graphics/chipset drivers, “unknown devices” are resolved.
    • Chipset driver redefines/configures IDE controllers.
    • System reaches a “fully set up” state, with one caveat:
      • DVD drive still unavailable due to missing IDE cables.

Performance + compatibility testing (games)

Mass validation (mostly works; ~2005–2006 cutoff)

  • Practical cutoff where games stop supporting Windows 98 or require newer OS components/drivers/libraries.

Examples tested

  • Halo (Windows 98)

    • With FX 5200: playable multiplayer, around ~20 FPS.
    • With AGP 6800 Ultra: still not “perfect.”
      • Behavior like texture changes led to instability.
      • Interpreted as driver/setting-related rather than raw CPU-only limitation.

  • LEGO Island

    • Hardware mode crashes.
    • Hardware acceleration appears broken.

  • DirectX troubleshooting

    • DXDIAG tests sometimes fail until updating DirectX.
    • After that, DirectDraw/3D acceleration becomes usable.

  • Trespasser (1998)

    • Runs well (often cited as ambitious/poorly optimized for its era).
    • Roughly ~60 FPS in both modes.

  • Sonic Heroes, Half-Life, GTA: Vice City, Driver

    • Largely workable and mostly smooth where tested.

DOS games

  • Often freeze/lock up.
  • Suspected causes: sound card emulation limitations
    • Windows 98 Second Edition emulates Sound Blaster, but DOS compatibility remained unreliable.
  • Video advice: for DOS gaming on 98, choose a DOS-compatible sound card.

Windows 98 vs Windows XP sanity check

On a separate SSD, Windows XP was installed to retest.

  • Halo and Driver: run “pretty much flawlessly,” generally feeling smoother/more comfortable.
  • Windows 98 behavior: gets progressively slower/less stable after more drivers/apps.
  • XP-specific pains for 98 hardware:
    • USB 2.0 drivers caused shutdown hangs “forever.”
    • Frequent boot lockups, blue screens, and instability made it effectively unusable outside the experiment.

Main conclusion: the hardware is newer than 98-era expectations, and XP drivers are just more mature.

Key takeaways / “analysis” conclusions

  • There’s no single “ultimate” Windows 98 PC.
    • Maximizing speed with “fast-but-98-supported” hardware trades away stability and compatibility.
  • The “correct” retro PC depends on:
    • the specific games and workflows you want
  • If drivers are the limiting factor (notably GPU/video drivers and BIOS CPU support),
    • raw hardware performance can’t compensate.

Main speakers / sources

  • Speaker: The video creator (single primary narrator)
  • Referenced resources/tools:
    • VOGONS (motherboard/CPU compatibility research)
    • Clonezilla (disk imaging)
    • GParted (partitioning)
    • DXDIAG / DirectX (graphics debugging)
    • Sysinternals (NTFS enabling)
    • KernelEx (9x compatibility layer)
    • SalC1 + Cortex (Minecraft-on-98 reference video)

Original video