[ HOME ]    [ RADIO ]    [ COMPUTERS ]    [ FIELD STATION ]    [ ABOUT ]    [ MODERN MODE ]
=== SETTING UP 86BOX ON WINDOWS AND LINUX: BUILDING A 1997 WIN95 OSR2.5 VM ===

[SYS] Emulating vintage hardware accurately down to the clock cycle is essential when testing legacy software, digital ham radio tools, or period-correct operating systems. Unlike general hypervisors (such as VirtualBox or VMware), 86Box emulates real motherboard chipsets, sound cards, graphics accelerators, and expansion buses.

This guide covers installing 86Box on both Linux and Windows, configuring a period-accurate 1997 machine setup, and properly configuring audio drivers in Windows 95 OSR2.5.

1. Prerequisites & File Preparation

Before starting, acquire the following assets:

  • 86Box Executable: Download the latest stable build for your host OS.
  • 86Box ROM Set: The matching roms directory containing extracted motherboard, BIOS, video, and peripheral ROM images.
  • OS Media: Windows 95 OSR2.5 ISO image and a Windows 95 Boot Disk image (.img or .ima).
  • Sound Drivers: Sound Blaster AWE64 Gold PnP driver ISO or disk set (S95UP.EXE / Creative AWE64 installation package).

2. Installing 86Box on Host Operating Systems

Installing on Linux (Ubuntu / Debian / Related Distros)

[PC] On Linux, 86Box can be run via AppImage or built/installed directly.

  1. Download the latest 86Box-Linux-x86_64.AppImage release.
  2. Open a terminal and make the binary executable: 
    chmod +x 86Box-Linux-x86_64.AppImage
  3. Create your local 86Box configuration directory structure: 
    mkdir -p ~/.config/86Box/vm-win95
cd ~/.config/86Box/vm-win95
  4. Clone or extract the 86Box roms folder into your working directory or path: 
    ls -la ./roms
  5. Launch 86Box: 
    ./86Box-Linux-x86_64.AppImage

Installing on Windows

  1. Extract the downloaded 86Box-Windows-x64-*.zip archive to a dedicated folder (e.g., C:\Emulators\86Box\).
  2. Extract the roms ZIP folder directly into the root folder where 86Box.exe resides (C:\Emulators\86Box\roms\).
  3. Run 86Box.exe to launch the manager and interface.

3. Creating and Configuring the 1997 Virtual Machine

Launch 86Box and navigate to Tools $\rightarrow$ Settings to configure the target hardware profile.

Category Hardware Setting Selection / Value
Machine Machine Type [Socket 7]
Machine Machine [i430HX] ASUS P5A or FIC PA-2012 / Shuttle HOT-557
Machine CPU Type Intel Pentium MMX
Machine Speed 200 MHz or 233 MHz
Machine Memory 64 MB EDO RAM
Display Video Card [PCI] S3 ViRGE/DX or Matrox Millennium II
Input Mouse Standard PS/2 Mouse
Sound Sound Card 1 [ISA16] Sound Blaster AWE64 Gold
Sound FM Synth Driver Nuked (more accurate)
Network Network Controller [PCI] Novell NE2000 or 3Com EtherLink III (3C509B)
Storage Hard Disk IDE Primary Master (Create .vhd image, e.g., 2000 MB)
Storage CD-ROM IDE Secondary Master (ATAPI CD-ROM)

4. Installing Windows 95 OSR2.5

  1. In 86Box, go to Media $\rightarrow$ Floppy drive 3.5" $\rightarrow$ Image… and attach your Windows 95 Boot Disk.
  2. Go to Media $\rightarrow$ CD-ROM $\rightarrow$ Image… and attach the Windows 95 OSR2.5 ISO.
  3. Power on the VM.
  4. Partition and format the virtual hard disk using DOS tools: 
    fdisk
    (Create Primary DOS Partition, set active, reboot VM) 
    format c: /s
  5. Run the setup program from the CD-ROM drive (typically D:): 
    D:\WIN95\SETUP.EXE
  6. Complete the standard Windows 95 installer steps and reboot when prompted.

5. Resolving Audio Hardware Drivers (SB AWE64 Code 2 Fix)

[SYS] A common issue when running Windows 95 OSR2.5 with a Sound Blaster AWE64 in 86Box is seeing a yellow exclamation mark in Device Manager with Code 2:

Device failure: Try changing the driver for this device. (Code 2)

This occurs because Windows 95’s stock, in-box drivers only install basic Sound Blaster 16 compatibility and fail to initialize the Plug and Play (PnP) EMU8000 wavetable synthesizer node.

[Device Manager Status]

  • Sound, video and game controllers
    • Creative AWE64 16-bit Audio (OK)
    • Creative AWE64 Gold Wavetable MIDI (AWE32 compatible) [!] -> Code 2 Error

Resolution Steps

  1. Mount the Creative Sound Blaster AWE64 Basic Installation Disk / Web Update ISO in 86Box (Media -> CD-ROM).
  2. Run SETUP.EXE from the driver media inside Windows 95.
  3. Allow the installer to deploy the official Creative PnP Configuration Manager (CTCM) and AWE wave synthesis drivers.
  4. If Code 2 persists after installing drivers:
    • Restart Windows 95 and press F8 at boot to enter Safe Mode.
    • Open Control Panel -> System -> Device Manager.
    • Expand Sound, video and game controllers and delete all duplicate or failed sound entries.
    • Reboot back into normal mode to allow Windows 95 to auto-detect the card clean.

Once resolved, both digital audio playback and hardware AWE MIDI synthesis will function properly without resource conflicts.


W4DXR Retro Terminal | Station Log & Technical Notebook