86Box relies on a set of ROM dumps gathered from physical hardware to emulate it. This includes the system BIOS, as well as any option ROMs used by expansion cards.
The ROM set is organized into several directories for each device type, each of which contains futher subdirectories for each machine or device model or category.
The expected file names of the ROM dumps and their locations within the set are hardcoded in the emulator. If you rename them or add your own dumps with different file names, the emulator will not be able to make use of them.
The emulator utilizes a search path mechanism to locate ROMs. By default, the following locations are considered:
romssubdirectory in the VM path
romssubdirectory in the same directory as the emulator executable
A custom location can be specified by using the
--rompath command line argument, which then precedes any other considered locations.
The following locations are searched on Windows:
86Box honors the XDG base directory specification on Linux and other Unix-compatible platforms. The following locations are searched:
86Box/romssubdirectory in each path listed in
This usually resolves to
/usr/share/86Box/roms (in order).
The following locations are searched on macOS:
The list of all paths searched when loading ROMs is printed to the log and standard output when 86Box starts.