86Box is not another console emulator chasing frame-rate parity with a PlayStation or a Switch. It rebuilds entire vintage PCs, motherboard chipsets, BIOS chips, sound cards, and graphics adapters included, so that MS-DOS, Windows 95, Windows 98, and even Windows XP boot the way they did on real 1990s hardware. Version 86Box 6.0 shipped on May 31, 2026, adding a native Windows ARM64 build for Snapdragon and RTX Spark laptops and dropping support for macOS 10.13 High Sierra. Monthly search volume for “86box” sits at roughly 2,400 in the US with low competition, according to DataForSEO keyword data pulled in September 2026, which tells you plenty of people are hunting for a setup guide that actually works.
This tutorial walks through every step: choosing a machine profile, sourcing the ROM set legally, configuring a period-correct graphics card, installing Windows 98 from a virtual CD-ROM, and tuning performance on both Intel/AMD and Apple Silicon hosts. By the end you will have a working retro PC that can run Voodoo-accelerated Glide games, DOS-era productivity software, or a full Windows 2000 workstation, entirely inside a window on your modern desktop.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Is 86Box, and How Is It Different From DOSBox?
86Box descends from PCem, and its emulation model is fundamentally different from DOSBox’s. DOSBox recreates a DOS execution environment: it interprets DOS API calls and simulates a generic “DOS PC” without modeling specific hardware down to the chip level. That approach is fast and forgiving, which is why Tech Insider’s own DOSBox vs DOSBox-X vs DOSBox Staging comparison remains the right starting point for straightforward DOS gaming.
86Box takes the opposite route. It emulates the actual system board, BIOS ROM, chipset, storage controller, and peripheral cards of specific real-world machines, then boots whatever operating system you install onto that virtual hardware exactly the way the original PC would have. That means real MS-DOS, Windows 3.1, Windows 95, Windows 98, Windows ME, Windows 2000, and Windows XP all run unmodified. It also means you can select an actual S3 Trio64 or a 3dfx Voodoo2 card, install the period driver, and get Glide-accelerated 3D exactly as it behaved in 1998.
The tradeoff is complexity. Full hardware emulation, BIOS POST sequences and all, is heavier on the host CPU and requires more setup than mounting a floppy image in DOSBox. That is the gap this tutorial is built to close.
A Brief History: From PCem to 86Box
86Box started life as a fork of Sarah Walker’s PCem project, created to push machine-level accuracy and chipset coverage further than the original codebase was moving at the time. Over roughly a decade of development, the two projects have taken different paths: PCem stayed relatively compact and cycle-focused, while 86Box grew a much larger roster of motherboards, an active Discord-based contributor community, a companion ROM repository maintained as its own GitHub project, and, more recently, the graphical Manager application that turns machine creation from manual config-file editing into point-and-click setup.
That growth shows up directly in the release cadence relevant to this tutorial. 86Box 5.0 arrived in August 2025 with an integrated manager preview. 5.1 shipped in September 2025 after a bug-fix marathon, with OpenGL input scaling and portable mode. 5.2 followed in October 2025 with a searchable machine list and joystick improvements. 5.3 landed on December 22, 2025 with dynamic-recompiler optimizations for ARM and Apple Silicon hosts. 6.0, released May 31, 2026, folded all of that into a stable milestone and added the first official Windows ARM64 host support. That is a faster cadence than most emulation projects of comparable scope, which is part of why 86Box has become the default recommendation over PCem for most new retro-PC builders in 2026.
Where 86Box and Windows 98 Stand Today
The 86Box project describes itself as a low level x86 emulator that runs older operating systems and software designed for IBM PC systems and compatibles from 1981 through fairly recent system designs based on the PCI bus. That range includes the very first IBM PC 5150 from 1981 and the more obscure IBM PS/2 line of systems based on the Micro Channel Architecture, so the Windows 98 build in this guide is only one of many machines you can model. The official site lists v6.0, released on May 31, 2026, as the latest stable version, and the project’s repository is licensed under GPL-2.0.
Development builds exist, but the available official results do not identify a newer stable release than 6.0. The latest experimental build was b10246 in October 2026, with Windows ARM64 packages, and the official GitHub organization showed repository activity through October 21, 2026. For a dependable Windows 98 machine, stay on 6.0 and treat experimental builds as testing material, keeping a copy of your working portable folder before you try one.
The guest side is settled history. Microsoft confirms that Windows 98 launched on June 25, 1998, and it has been retired and unsupported since July 11, 2006, when extended support ended. Microsoft’s current supported-client documentation covers Windows 10 and Windows 11 instead, so treat a Windows 98 guest as a legacy environment for compatibility and preservation, and be careful about exposing it to the internet through the network options covered in Step 9b.
Prerequisites: What You Need Before Starting
Gather these before you download anything. Skipping a prerequisite is the single biggest reason first-time 86Box setups fail to boot.
| Requirement | Minimum | Recommended |
|---|---|---|
| 86Box version | 6.0 (May 31, 2026) | 6.0 or newer, check 86box.net for updates |
| Host CPU | 64-bit Intel Core 2, AMD Athlon 64, or ARMv8 | Modern quad-core, Apple Silicon M-series, or Snapdragon X |
| RAM | 4 GB | 16 GB, especially if running multiple VMs |
| Windows host | Windows 7 SP1 (Intel/AMD) | Windows 11 (ARM64 hosts need Windows 11+) |
| Linux host | Ubuntu 16.04 / Debian 9.0 or newer | Current LTS release |
| macOS host | macOS 10.14 Mojave | Apple Silicon Mac, macOS 14+ |
| Storage | 1-2 GB for the emulator and ROM set | 10+ GB per guest OS install with room for CD images |
| ROM set | Current 86Box ROM repository build | Full repository clone, kept in sync |
You will also need installation media for whatever guest operating system you plan to run, an MS-DOS boot disk image, a Windows 95/98 CD-ROM ISO, or a Windows XP install disc. 86Box does not ship any operating system, and it does not ship any BIOS ROM either; both have to come from sources you are legally entitled to use. More on that in the ROM section below.
Step 1: Download 86Box 6.0 for Your Platform
Go to the official 86Box project site and grab the build that matches your operating system. As of the 6.0 release, Windows users on Intel or AMD hardware use the standard 64-bit Windows build, while Windows-on-ARM laptops (Snapdragon X Elite, RTX Spark reference designs) use the new dedicated Windows ARM64 build introduced in this release. Linux users can pull 86Box from Flatpak, a distro repository, or the AppImage on the GitHub releases page. macOS users need Mojave 10.14 or newer; 6.0 formally dropped High Sierra support.
Extract the archive into its own folder. On Windows and Linux, 86Box runs portably out of that folder with no installer required, which makes it easy to keep multiple versions side by side if you ever need to roll back.
# Windows: extract the 86Box-Windows-64 zip anywhere, e.g.
C:\Emulation\86Box\
# Linux via Flatpak
flatpak install flathub net.86box.86Box
# Linux via AUR (Arch-based distros)
yay -S 86box
# macOS: mount the .dmg and drag 86Box.app to ApplicationsStep 2: Source a Legal ROM Set
86Box needs BIOS ROM dumps for whichever virtual machine you select, the same way a real motherboard needs its firmware chip. The project maintains an official 86Box ROM repository on GitHub that aggregates legally redistributable BIOS, SCSI controller, sound card, and video card firmware, with new machine and peripheral ROMs added throughout 2026 (recent additions include the Adaptec AHA-2940 and Adaptec AHA-2944UW SCSI controller BIOS files, added in 2026).
Download the ROM repository as a ZIP from GitHub, or clone it if you plan to keep it updated:
git clone https://github.com/86box/roms.git
# Place the extracted "roms" folder next to your 86Box executable,
# or point 86Box at it manually in Settings > Other > ROMs path86Box looks for the ROM folder in a handful of standard locations relative to its own executable. If it cannot find a matching BIOS for the machine you select in Step 4, the emulator will show the machine as unavailable in the dropdown rather than crashing, which is the easiest way to confirm your ROM path is wrong.
A note on legality, since this trips up newcomers more than any technical step. Motherboard BIOS firmware is copyrighted by the original manufacturer, the same as any other software. The 86Box project’s official ROM repository only distributes files its maintainers consider legally redistributable, generally because the original vendor released them freely, they were reverse-engineered open replacements, or the copyright holder has not objected to redistribution for preservation purposes. That is a meaningfully different legal footing from, say, downloading a commercial Windows 98 ISO from a random forum. Stick to the official repository for BIOS files, and source your guest operating system media the same way you would for a physical PC, from install discs you own or a license you hold.
Step 3: Set Up Portable Mode (Optional but Recommended)
Before creating your first virtual machine, decide whether you want 86Box running in portable mode, keeping all configuration, NVRAM, and hard disk images inside its own folder rather than scattered in your user profile. This matters if you plan to run 86Box from a USB drive, sync a VM between two computers, or simply keep everything self-contained for easy backup.
Portable mode, added in the 5.1 release, is enabled by placing an empty marker file in the same directory as the executable before first launch. If you skip this, 86Box stores configuration in your OS user directory instead, which is fine for a single permanent install.
Step 4: Create Your First Virtual Machine
Modern 86Box installs manage virtual machines through the 86Box Manager companion app, which handles creating, naming, and launching individual configurations instead of juggling loose config files by hand. Open the Manager, choose to create a new machine, and give it a name that reflects what you are building, for example “Win98-Voodoo2” or “DOS-SoundBlaster16.”
The 5.2 release added a searchable machine list, which matters because 86Box supports a genuinely large catalog of period-correct systems spanning early PC/XT and AT-class boards through 386, 486, Pentium, and Super Socket 7-era machines. Search for a family that matches your target OS. As a rule of thumb:
- MS-DOS or Windows 3.1: an early-to-mid 386 or 486 board is plenty
- Windows 95: a Pentium-class board with at least 16-32 MB of RAM
- Windows 98 or ME: a late Pentium or Pentium II/III board, 64-128 MB of RAM
- Windows 2000 or XP: a Pentium III/4-era board with 256 MB or more of RAM
Once you pick a machine, 86Box automatically loads the matching BIOS from your ROM folder. If the entry is greyed out, the required ROM file is missing, go back to Step 2.
It is worth resisting the urge to jump straight to the newest, most powerful machine profile on your first attempt. A late Super Socket 7 or Pentium III board pulls in more emulated chipset complexity, more BIOS quirks, and a longer list of things that can go slightly wrong on a first try. Building a simple 486 DOS machine first, confirming it boots, mounts media correctly, and shuts down cleanly, gives you a working mental model of the Manager before you tackle a Windows 98 Voodoo2 build with three separate cards and a dozen driver installs.
Step 5: Configure CPU, Memory, and Storage
Open Tools, then Settings, inside the running machine window (or the equivalent panel in the Manager before first boot). The Machine tab lets you pick the specific CPU model available for that motherboard family and set clock speed, for example a Pentium II at 300 MHz rather than a generic placeholder. Match the CPU to the games or software you intend to run rather than maxing it out by default, since some late-90s titles have timing bugs on CPUs that are too fast for their engine.
Under Storage Controllers, add an IDE or SCSI hard disk controller appropriate to your chosen machine, then create a new virtual hard disk image. 86Box supports several image formats; a plain HDI or VHD image of 500 MB to 4 GB is more than enough for a DOS or Windows 9x install, while a Windows XP build benefits from 8-20 GB.
# Typical Windows 98 configuration
Machine: Intel 440BX (Pentium II/III socket)
CPU: Pentium II 350 MHz
RAM: 128 MB
Storage: IDE hard disk, 2 GB HDI image
Video: Voodoo2 + a 2D card (see Step 6)
Sound: Sound Blaster 16 or AWE64Step 6: Choose a Graphics Card (S3, ATI, Voodoo, and More)
This is where 86Box earns its reputation among retro-PC enthusiasts. The Video tab lets you select from a genuinely deep roster of period graphics hardware, including S3 chipsets (Trio64, ViRGE), multiple ATI cards going back to the ATI 18800 and 28800-series VGA Wonder line, and Cirrus Logic SVGA parts, each emulated closely enough that the correct period drivers install and behave like the original silicon.
For 3D-accelerated Windows 95/98 gaming, add a 3dfx Voodoo or Voodoo2 as a secondary card alongside a standard 2D adapter, exactly how the real hardware shipped. The 5.3 release specifically improved multithreading for Voodoo and other video cards, which noticeably smooths out frame pacing on modern multi-core hosts. Install the Glide drivers from inside the guest OS the same way you would have on real hardware in 1998, then point any Glide-compatible game at the emulated Voodoo.
| Use case | Recommended video setup |
|---|---|
| DOS text/EGA software | Generic EGA or VGA |
| Early Windows 3.1/95 productivity | S3 Trio64 or Cirrus Logic SVGA |
| Glide-era 3D games (Tomb Raider, Quake) | 2D card + 3dfx Voodoo/Voodoo2 |
| Late Windows 98/2000 3D titles | S3 ViRGE or a period Direct3D-capable card |
Each card family behaves differently once you get into it. S3’s Trio64 line is a solid all-purpose 2D choice because Windows 95 and 98 both ship broad built-in support for it, so you often get a usable desktop before installing any third-party driver at all. The ATI Mach- and Wonder-series cards emulated by 86Box trade a bit of raw 2D speed for wider DOS game compatibility with titles that specifically checked for ATI hardware quirks. Cirrus Logic SVGA cards are the closest thing to a “safe default” for pure productivity software, since Cirrus chips were extremely common in real OEM PCs of the era and almost nothing fails to recognize them. Reserve the Voodoo and Voodoo2 selections specifically for Glide-native games; non-Glide software gains nothing from a Voodoo card since it only accelerates 3D rendering, not the 2D desktop.
Step 7: Configure Sound Hardware
Under the Sound tab, add a Sound Blaster 16, Sound Blaster AWE64, or Gravis Ultrasound depending on what your target games expect. DOS games in particular are picky about IRQ, DMA, and I/O port settings for Sound Blaster compatibility, and 86Box reproduces those quirks faithfully, which is a feature, not a bug, once you know the standard defaults: IRQ 5, DMA 1, port 220h is the classic Sound Blaster configuration most DOS installers expect out of the box.
The 86Box 5.2 update also added more floppy-drive audio recordings and joystick types under the input settings, and 5.3 bundled an asset pack specifically for floppy-drive sound effects and other larger resources, small touches that add authenticity if you care about the mechanical clatter of a period floppy seek. The 6.0 release in May 2026 also added Yamaha YMF715 sound to the NEC Mate NX MA23C, which matters if you are modeling that specific machine rather than a generic Pentium board.
Step 8: Mount Your Installation Media and Boot
With hardware configured, mount your installation media using the icons in the status bar at the bottom of the 86Box window. For a floppy-based MS-DOS install, click the floppy drive icon and select your boot disk image. For a CD-based Windows 95/98/XP install, click the CD-ROM icon and select your ISO file.
Power on the virtual machine from the Action menu. You should see the emulated BIOS POST screen, exactly like turning on a real PC, followed by your installer booting from the mounted media. From here the install process is identical to installing on real period hardware: partition and format the virtual hard disk, copy files, and reboot as prompted.
# DOS boot disk install sequence (typical)
FDISK # partition the virtual hard disk
(reboot)
FORMAT C: /S # format and transfer system files
(reboot from CD or floppy with installer)
SETUP.EXE # run the OS installerStep 9: Handle Keyboard Capture and Mouse Input
86Box captures your mouse cursor when you click inside the emulator window, the same way a full-screen game would. Release it with the documented hotkey, Ctrl+End by default, to get your cursor back for your host desktop. Fullscreen keyboard shortcut bugs affecting numpad keys were a known issue fixed in the 5.1 release, so make sure you are on 6.0 or newer if you hit that specific problem.
For DOS-era joystick support, game-port emulation gained more joystick types in the 5.2 release, useful if you are chasing accurate analog-stick behavior for flight sims or racing games from the mid-1990s.
Step 9b: Get Files In and Out of the Virtual Machine
Before you start installing software, decide how you will move files between your host desktop and the emulated PC, since copy-paste does not cross that boundary. The simplest method for most users is building a small ISO or floppy image on the host containing the files you want to transfer, then mounting it in 86Box exactly like an installation disc; free ISO-building tools are widely available on every host platform. For ongoing file transfer rather than one-off drops, add a network card under the Network tab, an emulated NE2000 or similar period Ethernet adapter is supported and pairs with 86Box’s built-in network bridging to your host, which lets a Windows 9x or XP guest reach a shared folder or even the internet for downloading period-appropriate patches, provided you configure TCP/IP inside the guest the way you would have in 1998.
If networking feels like overkill for a single-purpose DOS gaming box, skip it. Most users get by comfortably using virtual floppy and CD images as the sole transfer mechanism, and it avoids troubleshooting an entire extra emulated subsystem.
Step 10: Install Period-Correct Drivers Inside the Guest OS
Once your guest operating system is installed, it needs the correct drivers for the virtual hardware you configured, exactly as if you had built the real PC. Windows 9x generally auto-detects the emulated Sound Blaster and standard VGA/SVGA cards through Plug and Play, but Voodoo cards, SCSI controllers, and some sound cards need drivers sourced separately, typically archived period driver disks, since 86Box does not bundle any operating system software or third-party drivers.
Install drivers in this order for the smoothest result: chipset drivers first if the guide for your specific board calls for them, then video, then sound, then any SCSI or networking hardware last. Reboot between each driver install if Windows prompts you to, just like on real 1990s hardware.
Step 11: Tune Performance for Your Host Platform
86Box 5.3 optimized the dynamic recompiler specifically for ARM and Apple Silicon hosts and improved Windows performance through the Universal C Runtime, so Apple Silicon Mac and Windows-on-ARM users on 6.0 should see meaningfully better throughput than on 5.0 or earlier. If emulation still feels sluggish:
- Confirm the dynamic recompiler is enabled in CPU settings rather than the interpreter, which is dramatically slower
- Lower the emulated CPU speed if you selected a faster chip than your software needs; over-emulating a Pentium III when a 486 would run the target software fine wastes host cycles
- Switch the video renderer to OpenGL 3.0 Core if you are on the default software renderer, and use the input-scaling options added in 5.1 for sharper scaling
- Close other demanding applications; full hardware emulation is inherently heavier than DOSBox-style API translation
Step 12: Back Up Your Virtual Machine
Once you have a working install with drivers configured, back it up before installing anything risky, exactly like taking a snapshot before installing questionable 1998 shareware. In portable mode, this is as simple as copying the whole 86Box folder. If you are not running portable mode, locate your machine’s configuration and hard disk image through the Manager’s machine details panel and copy those files to a safe location.
Keep at least one clean, freshly-installed backup of each guest OS build so you can restore quickly if a driver install or game installer corrupts the virtual hard disk.
Step 13: Use the 86Box Manager for Multiple Machines
If you build more than one virtual PC, the 86Box Manager keeps them organized with a searchable list, right-click machine actions, and detail panels that remember window size and position between sessions. This is the practical way to maintain, say, a lean DOS gaming box, a Windows 98 Voodoo2 rig, and a Windows XP productivity machine side by side without hand-editing config files to switch between them.
For a broader menu of emulators beyond 86Box, including console options and general-purpose frontends, Tech Insider’s Best Emulators for PC roundup compares PCSX2, RPCS3, Dolphin, and others against each other.
5 Common Pitfalls When Setting Up 86Box
- Picking a machine before checking ROM availability. If the BIOS ROM for a machine is missing from your ROM folder, 86Box greys the entry out with no obvious error message, leading new users to assume the software is broken.
- Mismatching CPU speed to software era. A Pentium III at full emulated speed running mid-1990s DOS games can cause timing-dependent bugs, screen tearing, or games that run absurdly fast, because those titles were never designed to run on hardware that fast.
- Forgetting to install period drivers. A blank display after Windows 95/98 boots almost always means the video driver was never installed inside the guest, standard VGA works out of the box, but S3 or Voodoo acceleration requires a manual driver install.
- Confusing the interpreter and dynamic recompiler. Leaving the CPU core on the interpreter setting instead of the dynamic recompiler tanks performance, sometimes by an order of magnitude, particularly on Windows XP-class guest machines.
- Not backing up before installing software. Old install routines and cracked-era software occasionally corrupt a DOS or Windows 9x file system exactly like they could on real hardware; a snapshot habit saves hours of reinstalling.
Expected Output: What a Working Setup Looks Like
When everything is configured correctly, powering on the virtual machine should produce, in order: a BIOS POST screen showing the emulated motherboard’s boot logo and memory count, a boot device handoff to your mounted floppy or hard disk, and then your operating system’s normal boot sequence. A properly driven Windows 98 install with a Voodoo2 configured should show the 3dfx Voodoo control panel in Display Properties, and Glide-based games should report the Voodoo card correctly in their setup utilities rather than falling back to a software renderer.
# Healthy DOS-side confirmation that Sound Blaster is detected
C:\> DIAGNOSE.EXE
Sound Blaster 16 found at I/O 220h, IRQ 5, DMA 1... OK
# Healthy Windows 9x Device Manager should show no yellow
# exclamation marks next to Display Adapters, Sound, or StorageTroubleshooting: 8+ Common 86Box Issues
Most 86Box problems trace back to one of three root causes: a missing or mismatched ROM, a driver that was never installed inside the guest OS, or a performance setting left on its slower default. Work through the following list roughly in order of how often each issue actually comes up during a first-time setup.
- Machine entry is greyed out in the picker. The BIOS ROM for that machine is missing. Re-check your ROM folder path in Settings > Other, and confirm the ROM repository download completed fully.
- Black screen after boot. Usually a video driver issue inside the guest, or an OpenGL renderer problem on the host; switch the renderer to the software fallback temporarily to isolate the cause, a fix specifically addressed for invisible/transparent renderer output in the 5.2 update.
- Emulation runs extremely slowly. Confirm the dynamic recompiler is active rather than the interpreter, and check that your CPU selection is not paired with a legacy machine profile that forces software-only rendering.
- Mouse cursor stuck inside the window. Press the release hotkey, Ctrl+End by default, to free the cursor back to your host desktop.
- Sound Blaster not detected in DOS. Confirm the DOS-side environment variable (typically BLASTER=A220 I5 D1 T4) matches the IRQ/DMA/port values you configured in the Sound tab.
- Fullscreen keyboard shortcuts misbehave, especially numpad keys. This was a known bug fixed in 5.1; update to 6.0 if you are still on an older build.
- Screenshots come out solid black. This was fixed alongside the OpenGL shader-loading fixes in 5.2; update your build and confirm you are not using an unsupported custom shader.
- macOS High Sierra users can no longer update. 6.0 requires macOS 10.14 Mojave or newer; High Sierra users need to stay on 5.x or upgrade their OS to keep receiving updates.
- Windows-on-ARM build fails to launch or feels unstable. Confirm you downloaded the dedicated Windows ARM64 build introduced in 6.0, not the standard x86-64 Windows build under emulation.
Advanced Tips: Getting More Out of 86Box
Once your first machine is running reliably, a few advanced moves are worth the extra time. First, build a second, more powerful machine profile specifically for benchmarking Glide-era 3D games, a Pentium II or III with a Voodoo2, since that combination represents the sweet spot most 1997-1999 3D titles were actually built around, and it showcases 86Box’s hardware accuracy better than any DOS-only configuration.
Second, keep the ROM repository synced with a scheduled git pull if you cloned it, since new machine, SCSI, sound, and video ROMs are added on a rolling basis throughout 2026, and a missing ROM for a niche motherboard is the most common reason an otherwise-correct configuration fails to appear in the machine list.
Third, if you are chasing period-accurate audio beyond gameplay sound, enable the floppy-drive seek sound recordings added in 5.2 under the floppy drive’s Audio settings; it is a small touch but it noticeably changes the feel of an install sequence for anyone who remembers the sound of a 3.5-inch drive actually working.
Finally, if your workflow spans multiple systems, or you also maintain console emulators, Tech Insider’s guides to setting up MAME for arcade hardware and ScummVM for classic point-and-click adventures cover adjacent corners of the same retro-computing hobby and use similar ROM-sourcing principles.
Complete Working Project: A Windows 98 Voodoo2 Gaming PC
Putting the full tutorial together, here is a complete configuration that reliably runs late-1990s 3D games with period-correct behavior, start to finish.
| Component | Setting |
|---|---|
| 86Box version | 6.0 |
| Machine | Intel 440BX-based Pentium II/III board |
| CPU | Pentium II 350 MHz |
| RAM | 128 MB |
| Primary video | S3 Trio64 (2D desktop) |
| Secondary video | 3dfx Voodoo2 (Glide 3D acceleration) |
| Sound | Sound Blaster AWE64 |
| Storage | 2 GB IDE HDI image |
| Guest OS | Windows 98 Second Edition |
| Renderer | OpenGL 3.0 Core, dynamic recompiler enabled |
Build order: create the machine and confirm the BIOS loads, install Windows 98 SE from a mounted ISO, install the S3 display driver, install the Voodoo2 Glide drivers, install the Sound Blaster AWE64 driver, reboot after each step, then install a Glide-native game and confirm it detects the Voodoo card in its setup utility before launching. That sequence mirrors exactly how PC gamers assembled this configuration in 1998, which is the entire point of 86Box.
86Box vs PCem: Should You Use the Fork Instead of the Original?
86Box began as a fork of PCem, and the two projects have diverged significantly since. PCem remains focused on a narrower, hand-curated set of machines with an emphasis on cycle-accurate reproduction of specific historic PCs, while 86Box has expanded its machine catalog far more aggressively and added the Manager tool, portable mode, and the broader ROM repository model covered throughout this tutorial. For most users chasing Windows 9x gaming or general retro-PC experimentation, 86Box’s larger machine library and more active 2025-2026 release cadence make it the more practical starting point; PCem is worth exploring afterward if you need a specific board 86Box does not yet model.
Where 86Box Fits Alongside Console and DOS Emulators
86Box occupies a specific niche in a much larger retro-gaming toolkit. If your goal is simply to play a DOS game with minimal fuss, DOSBox Staging or DOSBox-X will get you there faster; the comparison in Tech Insider’s DOSBox vs DOSBox-X vs DOSBox Staging guide breaks down which fork fits which use case. If your target is a specific console rather than a PC, the console-focused setup guides for MAME and dozens of other systems cover that ground separately. 86Box earns its place specifically when DOS-level emulation is not enough, when you need Windows 95 through XP to actually install and run, when you want a specific graphics card’s exact rendering quirks, or when you are preserving or documenting how a particular piece of period software actually behaved on real hardware rather than on a generic compatibility layer.
Frequently Asked Questions
Is 86Box legal to use?
Yes, the emulator itself is open-source software distributed for free. Legality depends on how you source your BIOS ROMs and operating system installation media; the official ROM repository aggregates files the project considers legally redistributable, but you are responsible for owning a legitimate license for any Windows or MS-DOS installation you run inside it.
Do I need to own the original PC hardware to use 86Box?
No. 86Box emulates the hardware itself, so you do not need physical period hardware. You do need legitimate installation media and, in most cases, a valid license or product key for the operating system you install, the same requirement that applies to any virtual machine.
Can 86Box run Windows XP?
Yes, 86Box supports late-model machine profiles capable of running Windows XP, though performance and driver availability are generally smoother for Windows 9x and Windows 2000-era software, which is where most of the community’s driver archives and configuration guides focus.
Why is my emulated PC running slower than a real 1998 machine?
Check that the dynamic recompiler is active rather than the interpreter CPU core, confirm you are on 86Box 6.0 or newer for the Apple Silicon and ARM performance work landed in 5.3, and avoid pairing an unnecessarily fast emulated CPU with older DOS software that has fixed-speed timing assumptions.
What is the difference between 86Box and DOSBox for gaming?
DOSBox translates DOS API calls into modern equivalents and is faster and simpler for straightforward DOS gaming. 86Box emulates full period hardware including the BIOS, chipset, and specific graphics/sound cards, which supports Windows 95 through XP and period-accurate Glide 3D acceleration that DOSBox cannot replicate, at the cost of more setup and heavier CPU usage.
Does 86Box support Apple Silicon Macs natively?
Yes. 86Box runs on Apple Silicon under macOS 10.14 Mojave or newer, and the 5.3 release specifically optimized the dynamic recompiler for ARM and Apple Silicon hosts, improving performance over earlier builds.
Can I run multiple 86Box virtual machines at once?
Yes, each machine you create through the 86Box Manager is an independent configuration with its own hard disk image and settings, and you can run more than one simultaneously as long as your host has the CPU and RAM headroom for it.
Where do I get period-correct drivers for cards like the Voodoo2?
Community-maintained driver archives dedicated to retro PC hardware host period Voodoo, S3, and sound card drivers matched to the specific chip revisions 86Box emulates. Match the driver version to your emulated card model and the guest operating system for the smoothest install.
How is 86Box different from a general-purpose VM tool like VirtualBox or QEMU?
VirtualBox and vanilla QEMU are built to run modern operating systems efficiently and generally expose a small set of virtualized, not emulated, generic hardware. They can run old Windows versions in a pinch, but they do not model specific period chipsets, BIOS behavior, or legacy cards like S3 or Voodoo silicon. 86Box exists specifically to reproduce that older hardware layer accurately, which is why it is the better choice for period-correct gaming and software compatibility rather than general virtualization.
