Editing PC Emulator Comparisons

 

 

 

Most emulators on this page requires an operating system to run, exceptions to this are DosBox and DREAMM, with the former having its own DOS implementation and the latter implementing both DOS and Win32 APIs. If you want to run Windows software in DosBox you still need a Windows install.

 

 

=[[FPGA]]=

 

 

:''Tons of non-active obsolete DOSBox forks for Android exists, see [https://emulation.gametechwiki.com/index.php?title=POS_(Pong_Consoles)_CPUs_and_Other_Chips&diff=70741&oldid=70740#x86_CPUs this page] for that.''

 

{| class="wikitable" style="text-align:center;"

! scope="col"|[[Recommended emulators|Recommended]]

!colspan="9"|PC / x86

|{{~}} ||{{✓}} || Windows 1.0-XP <ref group=N>Windows Vista and 7 will install and run in 86Box, but is discouraged due to poor performance on the emulated hardware</ref> ||{{✓}} ||{{✓}} ||{{✓}}

|[[PCem]]

|align=left|{{Icon|Windows}}<br/>{{Icon|Linux|macOS}}<abbr title="It should build on Linux and MacOS (Including M1) but no release builds for these platforms at the moment.">*</abbr>

 

These emulators provides an excellent compatibility and [[#Hardware_features_and_peripherals|hardware and peripheral support]] for DOS-based operating systems such as Windows 3.x, [[Windows_95/98/ME_emulators|Windows ME/98/95]] (and even NT-based [[Windows_2000/XP/Vista_emulators|XP/Vista]], Windows 7 supported but not recommended) that is beyond what "DOSBox forks" can offer but unlike "DOSBox forks" these emulators usually requires modest to top-notch [https://www.cpubenchmark.net/singleThread.html single thread performance of CPUs]. As of June 14, 2021, PCem's original developer, Sarah Walker, has stopped working on the project. It has now been taken over on December 18, 2021, by a new maintainer, Michael Manley. 86Box ([https://github.com/OBattler/PCem-X?tab=readme-ov-file#pcem-x- formerly known as PCem-X]) is a fork of PCem which is [https://github.com/86Box/86Box/issues/3577 developed more actively], while PCBox and VARCem are forks of 86Box.

:: One aspect commonly used to compare PCem and 86Box is the emulation performance. PCem v15 introduced a rewritten dynamic recompiler, which was primarily aimed at improving emulation performance in games; however, it also caused minor to severe performance regressions in other applications. 86Box uses the previous recompiler from PCem versions before v15, with optimizations performed by devs, as they have determined that the new one causes too many regressions to be adopted as a sensible default. There is a way for you to try out the new recompiler on 86Box, though. PCem’s emulation of some core system components, such as the Programmable Interval Timer (PIT), takes a few shortcuts to improve performance. These shortcuts are perfectly fine for games, which is what PCem targets; although, they have caused issues with the software preservation side of things. In addition to taking fewer shortcuts, 86Box also tries to follow the specifications of these components, rather than implement the minimum viable feature set, which is - once again - good enough for games, but not good enough for some other applications. Generally speaking, the more accurate a component’s emulation is made, the more host CPU horsepower it will require. In addition to taking fewer shortcuts, 86Box also tries to follow the specifications of these components, rather than implement the minimum viable feature set, which is - once again - good enough for games, but not good enough for some other applications. [https://86box.net/2022/01/07/pcem-migration-guide.html See this guide for more information].

:[[DOSBox]] is another option for emulating many older computer games specially for pretty good performance with low-end computers but compatibility, accuracy and [[#Hardware_features_and_peripherals|hardware support]] aren't as good as [[PCem]] or [[86Box]]. [[DOSBox]] is no longer updated but it has many "DOSBox forks" over the years. Windows 95/98/ME can be installed in "DOSBox forks" and also supports 3DFX Voodoo emulation. Even more forks are listed in the [https://github.com/dosbox-staging/dosbox-staging/wiki/DOSBox-forks "DOSBox forks" page of DOSBox Staging's GitHub wiki] or [[DOSBox#Forks|here]].

::'''[https://dosbox-x.com/ DOSBox-X]''' is vastly different from other "DOSBox forks" in that it aims to be a complete emulation package that covers all pre-2000 DOS and Windows 9x based hardware scenarios. It features more flexibility by way of config options and an accompanying frontend to customize the DOS VM further, and beyond games it also supports standard software for DOS, as well as DOS-based Windows including Windows 3.x and 9x/ME with 3D acceleration via 3dfx emulation. The project also has its own [https://dosbox-x.com/wiki wiki] which contains extensive documentation on DOSBox-X, and a summary of notable added features can be seen [https://dosbox-x.com/wiki/DOSBox%E2%80%90X%E2%80%99s-Feature-Highlights here]. While DOSBox-X currently supports emulation of [[#Intel_CPUs|IBM PC/XT/AT]], Toshiba AX/J3100, IBM PCjr/Tandy, and [https://emulation.gametechwiki.com/index.php/NEC_PC-9800_series NEC PC-9800 series] architecture, the maintainer, Jonathan Campbell, does not plan to add any other MS-DOS system. This limitation is mainly done to prevent bloating of the codebase, keeping it at a manageable level for himself while also staying organized. However, the codebase does contain stubbed source files for [https://emulation.gametechwiki.com/index.php/FM_Towns_emulators FM Towns] emulation in the event that other programmers want to add that functionality.<br/>

::'''[https://docs.libretro.com/library/dosbox_pure/ DOSBox Pure]''' is a new DOSBox fork specifically built for RetroArch/Libretro. According to its project description it aims for simplicity and ease of use just like DOSBox Staging. On top of that it has an advantage over other "DOSBox forks" because of libretro features ([https://www.youtube.com/watch?v=W8zCEf9prmQ EmuVR support], [[Shader_Presets#RetroArch.2FLibretro|Shader presets/Overlays]] and configs etc). Some of the other advantages are save-states, wider platform support (including Switch and Vita) and input auto-configuration fetched from the game database. It's good for users who want to experience their DOS games without too much hassle with settings, in a simple way akin to how console emulators deal with ROMs.

::'''[https://github.com/realnc/dosbox-core DOSBox-core]''' is an alternative core for RetroArch/Libretro, which focuses on being as close in use as upstream DOSBox. Its advantages include using .conf files to run games, ability to use external MIDI synths (like the Roland Sound Canvas VA, the Yamaha S-YXG50, or whatever else) so that you can get much higher quality MIDI music in dosbox-core, and has more configuration options befitting more advanced users. Its disadvantages are slightly worse input lag (like half a frame), lack of save-states and runs on less platforms (Windows, Linux, macOS and Android; consoles like Vita and Switch are unavailable)

|-

|[[DREAMM]] is a new emulator that targets specific games rather than the PC platform in general. As a Quality of Life feature, when running games that originally had manual or codewheel based copy protection DREAMM provides the correct answers for the user. Games run in the emulator's built in implementations of DOS, Win32 and FM Towns OS.

  It can run many IBM PC XT games, and also various 286(*) up to Pentium II games. Support for ATAPI CD-ROM (using VIDE-CDD.SYS, OAKCDROM.SYS or compatible ATAPI drivers) also works. Many graphics cards and sound cards can be used (MIDI using a Soundfont renderer inside UniPCemu (recordable by UniPCemu's sound recording functionality) or passthrough(passthrough on Windows only, which is not recordable by the emulator's own recording functionality)), from PC speaker up to Sound Blaster 2.0 and from IBM Monochrome Display Adapter up to ET4000/W32 SVGA(up to 16M colors (in True Color mode) using it's SC15025 DAC)!

  At that point I think MartyPC will be done chasing the hardware, I have no interest in following the CPU generations up into the Pentiums - that's probably best left to 86box - and I think I will probably turn my eye just to seeing what kind of interesting debugging features I can add. Save states and rewinding, an inline assembler or scripting language would be cool.

The emulation of various CPU types seen here regarding MAME are all over the place in the changelogs and seem confusing. However, MAME has preliminary support for the families of 286, 386/i386, 486/i486, and almost the entire range of Pentium CPUs. However, only the 286/386/486 emulation is acceptable at the moment. According to [http://www.progettoemma.net/mess/sysset.php ProjectMESS], many [http://www.progettoemma.net/mess/system.php?machine=ibm5170 IBM PC/AT 5170] family PCs running the 286 CPU have preliminary support. MAME [https://wiki.mamedev.org/index.php/MAME_0.146u3 0.146u3] (Jul 2012) added CPU types for Pentium MMX, Pentium Pro, Pentium II, Pentium III, and Pentium 4, but don't expect miracles.

::- [[MAME_compatibility_list#IBM|MAME compat list]] showing the sector for several IBM-type PC systems - most of which may work fine.

A full x86 PC emulator with a focus on development and test operating systems and other low-level software. Its lack of proper timing emulation makes it not useful, and it is often too slow for newer systems to be playable. It is thus not recommended to use Bochs. [https://sourceforge.net/p/bochs/discussion/39592/thread/17049d4e/#6bdd Bochs is not timing but functional emulator, it's emulates time in very trivial way] - one guest instruction emulated equal to one guest cycle. By tuning "IPS" setting you not anything in the way it emulates time - in opposite, you only giving a hint about emulation speed to Bochs which helps it to emulate devices like mouse or keyboard.

Similar to Bochs, QEMU may not be the perfect x86 emulator, but its versatility, [[Hypervisors|hypervisor]] capabilities, and vast platform support make it a powerful tool for anyone interested in exploring the world of [[Hypervisors|virtualization]]. Its commitment to open-source development and its vibrant community ensure its continued evolution and relevance in the ever-changing world of computing. While QEMU is versatile and great for [[Hypervisors|virtualization/VMs]], if your focus is precise, reasonable and compatible x86 emulation, '''use alternatives like 86Box, PCem or even DOSBox forks'''.

 

| [[Overclocking|Overclock]]<br/><small>Overclocking DRAM timings or CPU core frequency and CPU ring ratio '''using emulated BIOS just like using the real hardware'''.</small>

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✗}}

| {{✗}}

| rowspan=6 | Post-Processing

| {{✓}}

| [[Wikipedia:Comparison_gallery_of_image_scaling_algorithms|Post-rendering scaling]]<br/><small>(Sharp bilinear, Lanczos and [[Wikipedia:GPUOpen#FidelityFX_Super_Resolution|FSR 1]])</small>

| {{✓}}

| [[Shaders_and_filters|Filters]]

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{?}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{?}}

| {{?}}

| {{?}}

| {{?}}

| {{?}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| rowspan=6 | Quality of life

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{?}}

| {{?}}

| rowspan=4 | Misc

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}[https://github.com/dbalsom/martypc?tab=readme-ov-file#debugging-support *]

==Operating systems==

| {{~}}<ref group=N name=86BoxandPCemNT>86Box, PCem and PCBox supports these OS'es but even these emulators have limited [[#x86 CPU's]], [[#Graphics_Cards_.26_GPU.27s]] and [[#Mainboards]] support for more demanding NT-based operating systems, performance will be unbearable anyway. Recommended to use hypervisor solution for these OS'es (See [[Windows_2000/XP/Vista_emulators|Windows XP/Vista]] and [[Windows_95/98/ME_emulators|Windows 9x]] pages).</ref>

 

==Hardware & Peripheral Support==

| {{✗}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}<ref group=N name=PentiumIIIandAthlon>Pentium III emulation only available with [https://github.com/PCBox/PCBox/ PCBox fork], but do not expect miracles. Currently there is no processor available on the market that would be able to handle Pentium III or Athlon Classic emulation, considering that even the latest top-tier processors struggle with emulating fastest Pentium II/Celeron P6 processors. For more information about Pentium III emulation; [https://86box.net/2022/03/21/why-not-p3.html 86Box - Why Not Pentium III?].</ref>

| {{✗}}<ref group=N name=PentiumIIIandAthlon></ref>

! colspan=11 | Advantech

| EVA-X4150

| {{✗}}

| {{✗}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{Unknown}}

| {{✓}}

| {{✗}}

| {{✓}}

| {{✗}}

| {{✓}}

| {{✗}}

| {{✓}}

| {{✗}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{✓}}

| {{Unknown}}

! colspan=11 | Intel  

| {{✓}}

| {{✓}}

| {{~}}<ref group=N name=DOSBoxForksCPU><br/>Unlike emulators like 86Box or PCem which aim for accurate execution, DOSBox forks prioritize performance by [https://github.com/joncampbell123/dosbox-x/wiki/Guide:CPU-settings-in-DOSBox%E2%80%90X/d4205d856c3da5787fc39f845452d184fbcb8ec4#is-dosbox-x-cycle-accurate emulating one instruction per emulated-cycle]. This approach simplifies internal CPU mechanics and ignores real clock frequency or FLOPs of the emulated system. While this sacrifices perfect accuracy, it leads to significantly faster emulation and still has broader software compatibility compared to other emulators like QEMU or Bochs. However, some niche software may still encounter compatibility limitations. Therefore, DOSBox forks remain a powerful option for casual users and performance-intensive tasks, offering a balance between compatibility and speed. See DOSBox Pure: [https://github.com/schellingb/dosbox-pure/issues/301 MMX Instruction Set Support] issue page and [[#Descriptions]] section for more information.</ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{✓}}

| {{✓}}

| {{✓}}<ref>https://github.com/mamedev/mame/blob/master/src/devices/cpu/i86/i86.cpp</ref>

| {{✓}}

| {{✓}}

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{✗}}<ref group=N name=MartyPCCPU>Future goal, for more information see [[#Descriptions|Descriptions]] section.</ref>

| {{✓}}

| {{✓}}<ref>https://github.com/mamedev/mame/blob/master/src/devices/cpu/i86/i286.cpp</ref>

| {{✓}}

| {{✓}}

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{✗}}<ref group=N name=MartyPCCPU></ref>

| {{✓}}

| {{✓}}<ref>https://github.com/mamedev/mame/blob/master/src/devices/cpu/i386/i386.cpp</ref>

| {{✓}}

| {{✓}}

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{✗}}<ref group=N name=MartyPCCPU></ref>

| {{✓}}

| {{✓}}<ref>https://github.com/mamedev/mame/blob/master/src/devices/cpu/i386/i386.cpp</ref>

| {{✓}}

| {{✓}}

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{✗}}

| {{✓}}

| {{~}}<ref group=N name=MAMEPentium>Only the 286/386/486 emulation is acceptable at the moment. See [[#Descriptions|Descriptions]] section. [https://github.com/mamedev/mame/blob/master/src/devices/cpu/i386/i386.cpp (i386.cpp)]</ref>

| {{✓}}

| {{✓}}

| {{✗}}<ref>https://github.com/schellingb/dosbox-pure/issues/300</ref>

| {{✗}}

| {{✗}}

| {{✗}}

| {{✓}}

| {{~}}<ref group=N name=MAMEPentium></ref>

| {{✓}}

| {{✓}}

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{✗}}

| {{✓}}

| {{~}}<ref group=N name=MAMEPentium></ref>

| {{✓}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{~}}<ref group=N name=PentiumIIIandAthlon></ref>

| {{✗}}<ref group=N name=PentiumIIIandAthlon></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=DOSBoxForksCPU></ref>

| {{~}}<ref group=N name=MAMEPentium></ref>

| {{✓}}

| {{✗}}

| {{✓}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}

| {{✗}}