Running Windows 98 in a modern virtual environment typically requires the QEMU emulator, which uses the QCOW2 (QEMU Copy-On-Write) disk format. This format is efficient because it only grows as data is added to the virtual disk. 1. Preparing the Virtual Hard Disk
You first need to create a blank virtual disk image using the qemu-img tool. Command: qemu-img create -f qcow2 win98.qcow2 4G
Size Note: A 4GB to 8GB disk is standard. While 600MB is technically enough for a base install, larger images allow room for software and games. 2. Recommended QEMU Launch Settings
Windows 98 is sensitive to modern hardware speeds and features. Use these specific flags for the best stability:
CPU & RAM: Emulating a pentium3 with 256MB or 512MB of RAM is the "sweet spot." Allocating more than 512MB can cause the OS to crash or fail to boot.
Graphics: Use -vga cirrus or -vga std for basic compatibility.
Audio: The -device sb16 (Sound Blaster 16) is the most compatible audio hardware for this era.
Example Installation Command:qemu-system-i386 -cpu pentium3 -m 256 -hda win98.qcow2 -cdrom win98se.iso -boot d -soundhw sb16 -vga std 3. Essential Post-Installation Fixes
Windows 98 "out of the box" will have limited resolution and may run slowly.
32-bit Color & High Res: Install the VBEMP (Universal VESA) or SoftGPU drivers to unlock 1024x768 resolution and 32-bit color.
Stability Patches: Use projects like the Windows 98 QuickInstall or unofficial Service Pack 3 to fix common QEMU-related hangs and crashes.
Networking: If the default network card isn't found, try forcing an ISA model with -net nic,model=ne2k_isa. 4. Where to Find Pre-Configured Images
If you prefer not to install from scratch, several communities provide pre-made QCOW2 or VM images: installing windows 98, windows xp, and starcraft in qemu
The flicker of the virtual machine console felt like a time machine. There, encapsulated in a single file named win98_gaming.qcow2 , lived an entire era of computing history. For Elias, this wasn't just an exercise in virtualization
; it was a digital rescue mission. He had spent the afternoon configuring QEMU, carefully allocating 64 MB of RAM—a luxury compared to the minimum 16 MB
the OS originally demanded—and setting up the emulated SoundBlaster 16 card.
format was the secret sauce. Unlike the rigid raw images of the past, this "QEMU Copy-On-Write" format allowed him to use thin provisioning. The disk image started small, only growing as Elias filled it with abandonware classics and the iconic teal wallpaper windows 98 qcow2
. He could take snapshots before installing experimental drivers, knowing that if the dreaded Blue Screen of Death appeared, he was only one click away from a perfect state. startup sound
chimed—a majestic, synthesized wave of nostalgia—the pixelated "Start" button appeared. Inside this Linux-hosted container, Windows 98 SE was breathing again. Elias opened the command prompt, the familiar
blinking expectantly. In this sandbox, the year was forever 1998, the internet was a lawless frontier, and the only limit to his digital world was the size of a single virtualized file. How to Build Your Own "Time Machine" If you want to create your own image for a Windows 98 setup, here are the essential steps: Create the Image QEMU-img tool to create a sparse file. qemu-img create -f qcow2 win98.qcow2 2G Gather Your Media : You’ll need a Windows 98 SE ISO
and potentially a boot floppy image if your ISO isn't bootable. Launch the VM
: Run the emulation with a focus on older hardware compatibility.
qemu-system-i386 -m 64 -hda win98.qcow2 -cdrom win98se.iso -soundhw sb16 -vga cirrus -boot d
: Once installed, look for "Universal VESA" drivers to get higher resolutions beyond standard VGA. If you’d like, I can help you: Troubleshoot
driver issues (like getting sound or high-color graphics working). the technical benefits of over other formats like
your QEMU command for better performance on your specific OS. Let me know which part of the setup you're stuck on!
Creating or using a Windows 98 virtual machine (VM) in modern computing environments often involves converting old installations or ISOs into virtual disk formats compatible with contemporary virtualization software. QEMU's QCOW2 is one such format. Here’s some useful content on how to work with a Windows 98 VM in QCOW2 format:
-cpu pentium), reduce RAM, or enable single-core.Networking: Windows 98 might have issues with modern network settings. Ensure you use an appropriate network card in the VM settings and configure it to use a compatible protocol.
Sound: Sound in Windows 98 VMs can be finicky. Ensure you're using a compatible sound card.
Virtualization Extensions: For better performance, use KVM (for Linux) or ensure that your CPU supports virtualization extensions if you're on another OS.
Guest Additions/Drivers: For better integration (like shared folders, better graphics), install guest additions if available. For QEMU, you can manually install VirtIO drivers.
Enough theory. Let's build the image. You will need QEMU installed (available via winget, Homebrew, or your distro’s package manager).
The windows 98 qcow2 stack is not for the impatient. You will face IRQ conflicts, missing VXDs, and the dreaded "Windows Protection Error." But after you hear that startup chord echo through your speakers, watch the taskbar fade in, and successfully run Age of Empires via IPX network emulation, you understand why we preserve this. Running Windows 98 in a modern virtual environment
QEMU’s qcow2 format offers the most flexible, snapshot-friendly, and accurate replication of the Windows 98 environment available in 2025. It transforms your $3,000 ultrabook into a time machine back to 1998.
Final Command: Save that QEMU launch script as play_win98.sh. Keep a clean snapshot named base_snapshot.qcow2. And never, ever, click on "Active Desktop Update."
You will find many "ready-to-run" windows 98 qcow2 files on torrent sites and retro gaming forums. The temptation is high. Here is the risk assessment:
Pros:
Cons:
The Safe Approach: If you download a pre-made .qcow2 (e.g., "Win98SE_Gamer_QEMU.qcow2"), cheat by mounting it read-only to extract drivers, then build your own from scratch.
# Mount a foreign qcow2 without giving it network or clipboard access
qemu-nbd -c /dev/nbd0 windows98_prebuilt.qcow2
mkdir /mnt/win98
mount /dev/nbd0p1 /mnt/win98
# Copy the C:\WINDOWS\SYSTEM\*.VXD files you need
Here is the typical workflow to install Windows 98 onto your new QCOW2 file.
qemu-system-x86_64 \
-drive file=win98se.qcow2,format=qcow2,index=0,media=disk \
-cdrom win98SE.iso \
-boot d \
-m 512 \
-cpu pentium2 \
-vga cirrus
The critical flags explained:
-m 512 : Windows 98 crashes with more than 1GB of RAM. 512MB is the sweet spot.-cpu pentium2 : Tells Win98 it isn’t running on a quantum computer.-vga cirrus : The Cirrus Logic GD5446 is the most compatible video chip for Win98.During installation, when FDISK asks if you want large disk support, say Yes. When formatting, use format c: /s. The QCOW2 driver inside QEMU handles the translation.
Using QCOW2 for Windows 98 gives retro users a practical, space-efficient, and snapshot-friendly way to run and preserve legacy software. Favor IDE, Cirrus video, and SB16 audio emulation for best compatibility, keep drivers and install media archived, and manage snapshots to balance convenience with performance. With appropriate configuration, Windows 98 can run reliably inside modern virtualization stacks while remaining easy to snapshot, move, and preserve.
Bringing the 90s Back: Installing Windows 98 on QEMU (qcow2)
If you’re looking to relive the glory days of StarCraft, Age of Empires II, or simply the iconic startup sound, running Windows 98 Second Edition (SE) in a modern virtual machine is the way to go. Using QEMU, an open-source emulator, and the flexible qcow2 disk format, you can get a vintage desktop running on your modern hardware. 1. Preparation
Before starting, ensure you have an ISO image of Windows 98 SE. The Internet Archive is a popular resource for locating these legacy files. 2. Create the Virtual Disk
The qcow2 format is ideal because it only occupies the space actually used by the guest OS. Since Windows 98 is tiny by modern standards, a 1GB to 2GB disk is plenty. Run this command in your terminal: qemu-img create -f qcow2 win98.qcow2 2G Use code with caution. Copied to clipboard 3. Launching the Installation
To boot from the CD-ROM and start the setup, use the following configuration. Note the use of the pentium2 or pentium3 CPU type, as modern CPU instructions can sometimes crash older installers.
qemu-system-i386 \ -m 256 \ -cpu pentium3 \ -drive file=win98.qcow2,format=qcow2 \ -cdrom win98se.iso \ -boot d \ -vga cirrus \ -soundhw sb16 \ -net nic,model=pcnet -net user Use code with caution. Copied to clipboard 4. Navigating the Setup Initial Boot: Choose "Boot from CD-ROM" when prompted. Installer hangs or BSODs:
FDISK: You’ll need to initialize the virtual disk. Use the fdisk utility provided by the installer to create a primary DOS partition.
Format C:: After restarting the VM, run format c: to prepare the file system.
The Wait: The GUI installer will take about 20–30 minutes. 5. Essential Post-Install Fixes
The default installation often lacks modern luxuries like high-resolution graphics or smooth mouse movement.
Video Drivers: The default "Standard VGA" is limited to 16 colors. Use a freeware VBE driver to enable 32-bit color and higher resolutions.
Memory Management: While Windows 98 can run with more, it is generally not designed to handle more than 1GB of RAM, which can lead to instability. Stick to 256MB to 512MB for the best experience.
Software Transfer: Sharing folders can be tricky. A common workaround is creating a temporary ISO file containing your drivers and games and mounting it as a second CD-ROM. Final Boot Command
Once installed, you can drop the -boot d flag to boot directly from your new virtual hard drive:
qemu-system-i386 -m 256 -cpu pentium3 -drive file=win98.qcow2 -vga cirrus -soundhw sb16 Use code with caution. Copied to clipboard
Here’s a sample review for a Windows 98 QCOW2 image (typically used with QEMU/KVM).
I’ve written it from the perspective of a retro computing enthusiast or developer testing legacy software.
Title: Nostalgic and surprisingly usable – but expect to tinker
Rating: ⭐⭐⭐⭐☆ (4/5)
I downloaded the pre-built Windows 98 SE QCOW2 image to run under QEMU on a Linux host. Here’s my honest take after a few days of testing.
Pros:
qemu-system-x86_64 -hda win98.qcow2 -m 256. No installation wait.-cpu host,-hypervisor), Windows 98 ran without the infamous “BSOD on startup” I recall from real hardware.Cons:
-cpu 486 or limiting speed) otherwise some games run too fast. Memory >512 MB can cause issues.Verdict:
If you’re a retro enthusiast, developer testing legacy software, or just want to relive the ’98 experience without hunting for installation CDs and product keys – this QCOW2 image is a huge time-saver. Just be ready to tweak QEMU parameters and accept the limitations of a 20+ year old OS.
Tip: Use qemu-img to resize the disk if 2 GB isn’t enough, but keep FAT32 limits in mind. And always back up the original image before making changes.