To mount a 90s CD-ROM ISO on Windows 98 without a physical optical drive, replace your Win98 boot drive with a CompactFlash card on a passive IDE-to-CF adapter, copy your ISO onto the card, and use a real-mode DOS driver plus a Win98 image-mount utility to expose the ISO as drive D:. The whole workflow lets you install and run big-box CD-based software on a period-correct retro PC that has no working CD drive.
Why period-correct rigs skip failing optical drives
Every 90s PC eventually loses its CD-ROM drive. The belts crack, the laser dims, the sled jams. Original-era optical drives that still work today are increasingly rare and increasingly expensive on the secondary market. A retro builder who wants their Pentium II or K6-2 rig running Diablo, Warcraft II, or Fallout has a real problem: the games shipped on CD, the drive is dead, and finding a period-correct working replacement is neither cheap nor guaranteed to last.
The workaround the retro-PC community converged on is CompactFlash on IDE. A CF card presents itself as an ATA/IDE device through a passive adapter — no drivers, no active electronics, just a physical pinout translation. Every 90s PC BIOS speaks ATA. Every 90s operating system treats the CF card as a normal hard disk. The card is silent, low-power, and — most importantly — actually available in 2026, unlike a working period-correct optical drive.
Once you've moved to CF for storage, mounting CD-ROM images (ISO or .cue/.bin) becomes the natural next step. You image your original discs to files, copy them to the CF card, and use a Win98-era mounting utility to expose the image as a CD drive letter without needing physical optical hardware.
Per the Vintage Computer forums at Vogons, this workflow has been standard practice in the retro-DOS/Win9x community for years. The tooling is mature, the compatibility is well-mapped, and the parts remain in production. Getting it working takes an afternoon; keeping it working takes essentially no maintenance.
Key takeaways
- CF card on IDE adapter replaces the hard drive — silent, reliable, cheap, era-appropriate.
- Image your CDs to ISO or .cue/.bin on a modern PC using a USB IDE adapter or your daily-driver optical drive.
- Real-mode DOS drivers (SHSUCDX + a virtual CD driver) handle image mounting under DOS and Win98 boot.
- Windows 98 sees the CF card as a normal HDD — jumper the adapter to Master, format FAT32, install Win98 normally.
- Watch the 32 GB Win98 FAT32 format limit and the 137 GB LBA/CHS boundary — most CF cards over 8 GB avoid the trouble zones.
- Some copy-protected CD titles refuse to run without a physical disc — check per-game compatibility on Vogons.
What you need: the parts list
For a complete CF-on-IDE CD-image workflow on a retro Win98 rig:
- A CompactFlash card, 4–16 GB — the Transcend CF133 4 GB is the community's canonical pick because Transcend cards handle the Win9x wear patterns reliably and the size fits comfortably under FAT32 and Win98's practical addressing limits.
- A passive IDE-to-CF adapter — a 40-pin IDE plug on one side, a CF slot on the other, plus a 4-pin Molex power connector. Available cheap from many vendors.
- A SATA/IDE-to-USB adapter on your modern PC for reading/writing the CF card and imaging original discs.
- The original CD-ROM discs you want to preserve, and a working optical drive on a modern PC (or a period-correct drive from another retro rig you can borrow temporarily).
- CD imaging software on the modern PC: ImgBurn or CDRWin for .cue/.bin, an ISO tool for simpler discs.
- A DOS/Win98 image-mount utility: SHSUCDX + VCDROM.SYS, or similar community tools documented on Vogons.
- A Win98 install source — the Peter Norton's Complete Guide to Windows 98 is the classic reference for troubleshooting the install, and its era-appropriate documentation still holds up.
- Basic ATA jumper knowledge — Master vs Slave, and cable-select behavior on some vintage boards.
Why CompactFlash + IDE beats a physical CD drive
| Attribute | CompactFlash on IDE | Original CD-ROM drive |
|---|---|---|
| Availability in 2026 | Widely stocked | Increasingly rare |
| Reliability | Solid-state, no moving parts | Aging mechanicals, belt failure common |
| Noise | Silent | Spinning + laser sled noise |
| Power draw | ~0.5 W | 8–15 W |
| Random access | Instant | 100–200 ms seek |
| Speed to install a game | Limited by IDE bus, ~15 MB/s effective | Limited by CD spin-up + seek, ~1.5–7 MB/s |
| Cost (2026) | $8–$20 for the card + $10 adapter | $40–$150 for a tested working drive |
| Maintenance | None | Regular re-lubrication, belt replacement |
| Compatibility | 100% ATA-compliant | Some drives don't detect on old BIOSes |
The only category where a physical CD wins is copy-protection: a handful of CD-based titles from the late 90s and early 2000s checked for a real disc using low-level TOC reads that image-mount utilities can't perfectly replicate. For those, either use a legitimate workaround (patched executables from the game's community — most publishers no longer enforce these checks) or keep one working CD drive around for occasional use.
Spec/compatibility table for CF cards
| CF card size | Win98 FAT32 support? | BIOS support (typical 1998–2000 era) | Recommended? |
|---|---|---|---|
| 128 MB | Yes | Yes | Too small for anything useful |
| 512 MB | Yes | Yes | OK for DOS-only builds |
| 2 GB | Yes | Yes | Good for lightweight Win98 |
| 4 GB | Yes | Yes (most BIOSes) | Sweet spot |
| 8 GB | Yes | Yes (most BIOSes) | Comfortable for Win98 + games |
| 16 GB | Yes (careful with format) | Some 1998-era BIOSes have issues | Test before committing |
| 32 GB | Yes (at the FAT32 format ceiling) | Late-90s BIOSes may not detect | Advanced use only |
| 64+ GB | Requires third-party format tools | Late 90s BIOSes generally don't support | Skip for period-correct builds |
A 4 GB or 8 GB card is the pragmatic pick. It's big enough to hold Windows 98, a handful of games, and several CD images. It's small enough that no BIOS gets confused by the geometry. The Transcend CF133 sits right in this range and has proven reliable in retro-PC use.
Imaging your original CDs safely
Working image formats:
- ISO 9660 — for simple data CDs with no audio tracks. One file, straightforward.
- .cue/.bin — for mixed-mode CDs (data + Red Book audio). Two files: the .bin contains the raw sector data, the .cue describes the track layout.
- .mds/.mdf — Alcohol 120% format, similar to .cue/.bin but with more metadata for subchannel data. Compatible with some but not all image-mount utilities.
For most game CDs, imaging tools like ImgBurn (freeware, well-maintained) create .cue/.bin sets that preserve audio tracks correctly. Insert the disc into a modern PC's optical drive, choose "Create image file from disc," pick the .cue/.bin format, let it read at 4× or 8× (slower reads are more reliable for aging discs), and move the resulting files to the CF card.
If the disc has visible rot, cloudiness, or read errors, image it multiple times and compare — some sectors may be recoverable on retry. Store the good image; the physical disc will eventually become unreadable.
The DOS-level driver step that most first-timers miss
Windows 98 boots into a real-mode DOS environment before starting the GUI. Loading a CD-ROM driver at DOS level is what lets Win98's setup process (or a DOS game launcher) see the mounted image as an accessible drive letter.
The two files that make this work:
- VCDROM.SYS (or a similar virtual CD driver) loaded via CONFIG.SYS with a
DEVICE=VCDROM.SYSline. Assigns a device name to the virtual drive. - SHSUCDX.EXE (or MSCDEX.EXE with a shim) loaded from AUTOEXEC.BAT with a
SHSUCDX /D:VCD0line. Assigns a drive letter to the virtual CD device.
You mount an ISO by pointing the driver at the file path on your CF card. In Win98 GUI mode, tools like Daemon Tools 4 (an era-appropriate build; modern Daemon Tools won't run on Win98) or CDVirtual let you swap images through a tray-icon UI.
If setup a fresh Win98 install from a CF card, extract the Win98 setup files (usually the \WIN98 directory from the install CD) directly to the CF card first. Boot from a Win98 boot floppy, mount the CF card as C:, and run \WIN98\SETUP.EXE — no CD driver required for this bootstrap.
Gotchas: the boundaries you must respect
The 137 GB LBA barrier. Late 90s BIOSes use 28-bit LBA addressing, which tops out at 137 GB. CF cards over ~120 GB may not be visible to the BIOS at all, or may be visible only up to 137 GB. Stay within 8–16 GB for maximum compatibility.
CHS vs LBA modes. Some very early Pentium BIOSes only speak CHS (Cylinder-Head-Sector). CF cards handle this fine at small sizes but can misreport geometry above ~8 GB on the oldest boards. If your BIOS pre-dates 1998, stay below 8 GB.
FAT32 vs FAT16. Windows 98 supports FAT32 for volumes above 512 MB. FAT16 tops out at 2 GB. Format FAT32 for anything above 2 GB. Newer format tools (Win10/11) refuse to FAT32-format volumes above 32 GB — use a Win98-era tool or the community-maintained FAT32FORMAT utility.
Drive-letter conflicts. A mounted ISO takes a drive letter. If your CF card is C: and your DOS CD driver assigns the virtual drive to D:, you're fine. If you have a physical CD drive attached too, it may fight for D: and cause boot-time issues. Explicitly assign letters in AUTOEXEC.BAT.
Adapter jumper settings. The IDE-to-CF adapter usually has a Master/Slave jumper. If your CF card is the only IDE device on that channel, jumper it to Master. If it's sharing a channel with another drive, one must be Master and the other Slave. Getting this wrong causes the drive to not appear in BIOS.
Card write endurance. CF cards have finite write cycles. For a Windows install that includes a swap file and constant writes, use a card with SLC or MLC NAND (Transcend industrial-grade cards) rather than modern TLC/QLC. For read-mostly use (game images, static installs), any current CF card lasts effectively forever.
Common pitfalls beyond the mechanical steps
Trying to use SD-to-IDE adapters instead of CF. They work but are less reliable — the CF pinout was literally designed as a physical layer for ATA, while SD requires an active translation chip that varies in quality.
Mounting an image that was made with UDF. Not all image formats are universally supported. Stick with ISO 9660 for data, .cue/.bin for mixed mode, and test each image on the modern PC before moving it.
Assuming Win98's built-in CD support handles images. It doesn't. Win98's native tools only see physical CD hardware. You explicitly need a third-party image-mount utility.
Forgetting to enable CD support in the Win98 boot floppy. If you're bootstrapping a fresh install, use a "Win98 Startup Disk" that has CD-ROM support baked in (a checkbox during creation). Otherwise your setup floppy can't read the CD image on your CF card.
Copying files to the CF card while it's not properly ejected. File-system corruption is easy. Always use "Safely Remove Hardware" on the modern PC before yanking the CF card.
When to keep one working CD drive around
Not everything runs from an image. Titles that use ancient copy protection (SafeDisc, StarForce, SecuROM in some configurations) can be picky. Regional audio CDs, mixed-mode discs with subchannel data, and a handful of edge-case setup routines expect a physical disc.
The practical retro-PC compromise: run 95% of your library from CF images, keep one tested working CD drive (in the case or as an external USB-IDE-adapter setup for occasional use) for the remaining 5%. The CD drive lives in a drawer most of the time; the CF card is the primary storage.
Bottom line: the reliable period-correct workflow
The recommended workflow for a fresh retro Win98 rig without a working CD drive:
- Buy a Transcend CF133 4 GB or 8 GB CompactFlash card and a passive IDE-to-CF adapter.
- Use a SATA/IDE-to-USB adapter on your modern PC to prep the card: format FAT32, copy Win98 setup files, copy your ISO/.cue/.bin images.
- Jumper the CF adapter to Master, install in the retro rig on the primary IDE channel.
- Boot from a Win98 startup floppy, run SETUP.EXE from the CF card.
- After Win98 installs, load VCDROM.SYS + SHSUCDX in CONFIG.SYS/AUTOEXEC.BAT for boot-time image mounting.
- In Win98, install a period-appropriate image-mount tool (Daemon Tools 4 or CDVirtual) for GUI-level image swapping.
- Consult The Retro Web for board-specific BIOS quirks if the card doesn't detect.
Once set up, this workflow is bulletproof. Games install and run from the mounted image just as they did from the original disc. The rig is quieter, faster to boot, and free of the "will the CD drive work today?" anxiety that defines maintaining decades-old optical hardware.
For any retro-PC build in 2026, CompactFlash on IDE is the correct answer for both hard drive and CD-ROM replacement. The parts are cheap, the workflow is documented, and the reliability is essentially perfect for a machine that's going to be running twenty-year-old software anyway.
Related guides
Citations and sources
- Vogons — Vintage Computing forums — canonical community reference for retro-PC hardware and software compatibility
- Transcend Information — CF card spec sheets and endurance ratings
- The Retro Web — vintage motherboard database with BIOS quirks and CF-adapter compatibility notes
This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.
