PC emulator comparisons

Main article: POS (Pong Consoles) CPUs and Other Chips#x86 CPUs

For emulators that run on DOS, see Emulators on legacy Microsoft products#DOS.

For emulators that run on Windows 3.x, see Emulators on legacy Microsoft products#Windows 3.x.

For emulators that run on Windows 9x, see Emulators on legacy Microsoft products#Windows 9x.

For emulators that run on Windows 2000, Windows XP and Windows Vista, see Emulators on legacy Microsoft products#Windows NT.

The PC architecture originates from the 1981, IBM PC / model 5150. Due to being designed with off-the-shelf hardware, clone manufacturers could produce compatible hardware and was only limited by the copyright on the PC's BIOS. To circumvent this, competitors such as Compaq created their own compatible BIOSes using clean-room reverse engineering. See, Compaq reverse engineered patented IBM BIOS code.

IBM PC is also the basis for the IBM PC compatible de facto standard. IBM PC compatible computers are technically similar to the original IBM PC, XT, and AT, all from computer giant IBM, that are able to use the same software and expansion cards. Such computers were referred to as PC clones, IBM clones or IBM PC clones. The term "IBM PC compatible" is now a historical description only, since IBM no longer sells personal computers after it sold its personal computer division in 2005 to Chinese technology company Lenovo. The designation "PC", as used in much of personal computer history, has not meant "personal computer" generally, but rather an x86 computer capable of running the same software that a contemporary IBM PC could. The term was initially in contrast to the variety of home computer systems available in the early 1980s, such as the Apple II, TRS-80, and Commodore 64. Later, the term was primarily used in contrast to Apple's Macintosh computers. During the 1990s, IBM's influence on PC architecture started to decline. "IBM PC compatible" becomes "Standard PC" in 1990s, and later "ACPI PC" in 2000s. An IBM-brand PC became the exception rather than the rule. Instead of placing importance on compatibility with the IBM PC, vendors began to emphasize compatibility with Windows.

While the PC is technically capable of running many different operating systems, most of the emulators on this page are intended for x86 computers running DOS software, some kind of DOS-based Windows and Windows 9x (see operating systems section). If you wish to run software intended for Windows 2000 and Windows XP or even a newer version of Windows it is suggested to use a "recommended solution" mentioned in their dedicated pages. Most emulators on this page requires an operating system to run, exceptions to this are DOSBox forks 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 fork you still need a Windows install though.

Keep in mind that due to DOS and Windows running on a range of different hardware, cycle accuracy is less crucial than for most systems covered by this wiki, as software could not rely on cycle timing of a particular chip without excluding a large part of the market.

Emulators

Tons of non-active obsolete DOSBox forks for Android exists, see this page for that.

See Category:x86-based page for other x86 based systems software emulation.

Name	Platform(s)	Latest version	Enhancements	Hardware support, features, and peripherals	Operating systems	License	Active	Recommended
x86
86Box		Dev 6.0 PCBox fork	~	✓	MS-DOS Windows 1.0~2000 and later	GPLv2 (Copyleft)	✓	✓
PCem		{{PCemVer} git git (macos)	~	✓	MS-DOS Windows 1.0~2000 and later	GPLv2 (Copyleft)	✓	✓
DOSBox and forks		2026.08.02 (DOSBox-X) 0.83.0 (DOSBox Staging) 1.0 preview 6 (DOSBox Pure) git (DOSBox-core) 0.74-3 (DOSBox) (obsolete)	~	~	MS-DOS Windows 1.0~3.11 (Staging) Windows 1.0~ME (DOSBox forks)	GPLv2 (Copyleft)	~	✓
DREAMM		4.0.0	~	~		Proprietary	✓	~
MartyPC		v0.4.1	~	~	MS-DOS Windows 1.0~3.0	MIT (Permissive)	✓	~
UniPCemu		2023/04/11 git	?	~		GPLv3 (Copyleft)	✓	~
VARCem		Builds git	?	~		BSD-3-Clause GPLv2	~	~
MAME		git artifacts 0.289 libretro core	~	~		GPLv2 BSD-3-Clause	✓	~
PCjs		git	✗	~		MIT (Permissive)	✓	✗
QEMU		11.1.0	✗	✗		GPLv2 (Copyleft)	✓	✗
Bochs		3.0	✗	✗		LGPLv2.1 (Copyleft)	✗	✗
ARM
DOSBox Pure		libretro core	~	~	MS-DOS Windows 1.0~ME	GPLv2 (Copyleft)	✓	✓
DREAMM		4.0.0	~	~		Proprietary	✓	~
UniPCemu		2023/04/11	?	~		GPLv3 (Copyleft)	✓	~
Magic DOSBox		1.0.84	?	~		Proprietary	✓	✗
Limbo		6.0.1 WinMobile build	✗	✗		GPLv2 (Copyleft)	~	✗
DOSBoxPPC		0.63	?	~		Proprietary	✗	✗
Bochs		2.6.11 git	✗	✗		LGPLv2.1 (Copyleft)	✗	✗
Consoles
DOSBox Pure		UWP libretro core	~	~	MS-DOS Windows 1.0~ME	GPLv2 (Copyleft)	✓	✓
UniPCemu		2023/04/11	?	~		GPLv3 (Copyleft)	✓	~
Bochs		2.3.5	✗	✗		LGPLv2.1 (Copyleft)	✗	✗

Descriptions

PCem/86Box/PCBox/VARCem: These emulators provides an excellent compatibility and hardware and peripheral support for DOS-based operating systems such as Windows 3.x, Windows ME/98/95 (and even NT-based XP, Vista or 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 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 (formerly known as PCem-X) is a fork of PCem which is 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. See this guide for more information.

DOSBox-X/DOSBox Pure/DOSBox-core/DOSBox Staging: DOSBox is another option for emulating many older computer games specially for pretty good performance with low-end computers but compatibility, accuracy and 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 "DOSBox forks" page of DOSBox Staging's GitHub wiki or here. 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 wiki which contains extensive documentation on DOSBox-X, and a summary of notable added features can be seen here. While DOSBox-X currently supports emulation of IBM PC/XT/AT, Toshiba AX/J3100, IBM PCjr/Tandy, and 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 FM Towns emulation in the event that other programmers want to add that functionality. 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 ( EmuVR support, 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. [ 0.9.5 version brings 3dfx emulation support. 0.9.8 version brings further improvements to the ATAPI CD-ROM emulation for Windows 9x games with CD copy protection, add support for uncompressed CHD version 5 CD images and add netplay for multiplayer games that used IPX, Ethernet or a modem over the internet. 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) DOSBox Staging is a DOSBox fork that focuses on ease of use, modern technology and best practices. 3dfx emulation is supported with the latest releases.

DREAMM is a new emulator that targets specific games rather than the PC platform in general. Notable features include reconstructing missing EXE and index files from digital releases, automated installation from disk images, GUI-based configuration of video and sound hardware, and 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.

UniPCemu The UniPCemu (Universal PC emulator) emulator, originally made to play games on the PSP, now built for Android, Windows, PSP, Nintendo Switch and PS Vita! Play your old classic PC games on Android! It's a cycle-accurate x86 emulator (previously called x86EMU before the rename, This isn't based on the other cpu-emulator called x86emu (lower case)). It's a 8086(IBM PC) up to Pentium II (Compaq Deskpro 386, Compaq Deskpro 386 with PS/2 mouse (adds PS/2 mouse to the Compaq Deskpro 386 chipset, optional BIOS ROM replacement (loading it instead, alternatively a i430fx Pentium or i440fx/i450gx Pentium Pro/Pentium II chipset with PS/2 mouse. A 85c496/7 chipset is also supported.) and seperate CMOS settings like the other architectures) emulator(with various, configurable hardware), with up to 80386 timings (80486SX and Pentium using 80386 timings or 1 cycle for newer/unknown timings/instructions, both having no floating point unit)). In basic CPU's, all generations in between are supported (8086/8088, 80186/80188, 80286, 80386sx/dx, 80486, Pentium, Pentium Pro and Pentium II. All without FPU emulated, other than software FPU emulation support using drivers). 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)! EMS is available using the Lo-tech 2MB EMS board on the XT and various EMM emulation software(e.g. JEMM386, EMM386) on IBM AT and up. For more information about UniPCemu use this link.

MartyPC: It's an open source emulator written in rust that aims to be cycle accurate for IBM PCs. Compared to other (also great) PC emulators like PCem/86box/DOSbox forks etc, MartyPC focuses on ultra accurate CGA and DMA emulation. It requires pixel perfect and cycle accurate CGA emulation as well as emulation of CRT properties like overscan. Developer "Glorious_Cow" said; Of course my next target is the 286, I think it would be interesting to try to make a cycle-accurate 286. The biggest challenge is the microcode for 286 hasn't been decoded yet, but there is a high resolution 286 die shot I'd love to get my hands on... My hope is that the 286 is a more 'regular' chip than the 8088. The 8088 turned out to have a lot of odd, poorly documented behavior. I guess we'll find out. 386 is sort of a long-term goal. I'll get there when I get there, but it might take another year for 286 I estimate before I tackle it. Now that I've accomplished Area 5150 I don't really have a "goal target" in mind other than running DOOM :) My 386 will not be slavishly cycle-accurate, after all, there were many variations of the 386 and clones, so which one would be accurate to? Besides the fact it's hard to write a cycle-accurate CPU at 40MHz... 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. With most end-users probably best served by using 86box, I figure my best niche going forward is being a 'retro-developer's' emulator of choice, so I am motivated to add any debug features people might request.

MAME: 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 ProjectMESS, many IBM PC/AT 5170 family PCs running the 286 CPU have preliminary support. MAME 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 compat list showing the sector for several IBM-type PC systems - most of which may work fine. - wiki.mamedev.org's search results for Pentium (e.g. 0.100u4, 0.103u4, 0.146u3, 0.148, 0.152, 0.156) - wiki.mamedev.org's list for MACHINE_NOT_WORKING (Few systems based on a Pentium CPU) - wiki.mamedev.org's list for MACHINE_IS_SKELETON drivers (Several PCs/systems based on a Pentium CPU)

Bochs: 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. 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.

QEMU Similar to Bochs, QEMU may not be the perfect x86 emulator, but its versatility, hypervisor capabilities, and vast platform support make it a powerful tool for anyone interested in exploring the world of 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 virtualization/VMs, if your focus is precise, reasonable and compatible x86 emulation, use alternatives like 86Box, PCem or even DOSBox forks.

Enhancements

Side note: Please don't bump/spam GitHub threads/issues and feature request pages.

Name		86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
Controls	Disguise peripheral support through Passthrough Tricking the software into think that the original controller was connected even those identify themselves with different device IDs. When a game tries to identify a connected 'nearly the same internally' controller, emulator will tell it that the equivalent original controller is connected instead, allowing it to work.	?	?	?	?	?	?	?	?	?
	Input lag-mitigating technique	✗	✗	✗	✗	?	✗	✗	?	✗
	Real peripheral support (Passthrough) Ability to passthrough USB HID devices or Bluetooth adapter for emulated system.	?	?	?	?	?	?	?	?	?
	Turbo button	?	?	?	?	?	?	?	?	?
Performance	Overclock, turbo button, and underclock Changing DRAM timings or CPU core frequency and CPU ring ratio using emulated BIOS just like using the real hardware or from GUI.	✓	?	✗	✗	?	✓	✗	?	✗
	Preload optical disc image to RAM For users with sluggish multi-platter HDDs or plagued by horrible seek times, this enhancement might offer smoother experience, potentially reduced power consumption; it also shines when disc images reside on a network drive. Although keep in mind that preloading image would take some time, and it will require additional amount of RAM capacity.	?	?	?	?	?	?	?	?	?
Post-processing	AI-powered filter compatible (Freestyle)	?	?	?	?	?	?	?	?	?
	Filters	✓	✓	✓	~	?	✓*	?	?	✓
	Inverse tone mapping compatible	?	?	?	?	?	?	?	?	?
	Post-rendering anti-aliasing (FXAA, TXAA and MLAA/SMAA)	?	?	~	~	?	?	?	?	?
	Post-rendering scaling (Sharp bilinear, Lanczos and FSR 1)	?	?	~	~	?	?	?	?	?
	Shader chain	✓[4]	✗	~	~	?	roadmap	✗	?	✓
TAS features	Fast-forward/turbo speed	✗	✗	✗	✗	?	✗	✗	?	✗
	Macros/Scripts/Lua	?	?	✗	✗	?	?	?	?	?
	Movie recording/playback	✗	✗	✗	✗	?	✗	✗	?	✗
	Rewind	✗	✗	✗	✗	?	✗	✗	?	✗
	Save states	✗	✗	✗	✗	?	✗	✗	?	✗
Quality of life	Automatic updater	~	?	?	?	?	?	?	?	?
	Big Picture Mode	✗	✗	?	~	?	✗	✗	?	✓
	Built-in custom resolution/CRTSwitchRes For using this on Windows OS you need CRT Emudriver. Another option is using EDID editor tool such as "Custom Resolution Utility".	Exclusive to libretro cores and GroovyMAME at the moment.
	Capable image format support	✓[5]	?	?	~	?	?	?	?	?
	Command line options	✓	✓	✓	✓	?	✓	?	?	✓
	File sharing Similar to "Shared Folder" enhancement for Type-2 hypervisors.	✓*	?	?	?	?	?	?	?	?
	On-screen display Showcases messages, controller input state which is useful for speedrunners, performance data, active settings, and various notifications.	?	?	?	~	?	?	?	?	?
	Pause/resume emulation	✓*	✓	?	~	?	?	?	?	?
	Portable and Stealth Useful enhancement feature for non-personal computer use or plug-and-play scenarios. However, it still requires necessary prerequisites and dependencies for your operating system.	✓	✓	?	?	?	?	?	?	?
	Streamable compression format	✓	✓	?	✓	?	?	?	?	✓
Misc.	AI service With the help of OCR and other techniques, the AI service can provide a live translation of a game, or text-to-speech capabilities for the visually impaired among other things, either on demand or automatically.	Exclusive to libretro cores at the moment.	?	?	?	?	?	?	?	?
	Debug features	?	?	?	?	?	✓*	?	?	?
	EmuVR support	Exclusive to libretro cores at the moment, this means that only DOSBox Pure supported. ( Demonstration)	?	?	?	?	?	?	?	?
	RetroAchievements	✗	✗	✗	✗*	✗	✗	✗	✗	✗

Operating systems

For virtualization of these legacy operating systems, see Windows NT 5.x emulators#Hypervisors.

For extensive list of OS support solely for 86Box emulator, see 86Box#OS_support.

Name	86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
OS/2
OS/2 1.0	✓	✓	✗	✗	?	✗	?	?	?
OS/2 v1.1 / v1.2 / v1.3	✓	✓	✗	✗	?	✗	?	?	?
OS/2 v2.0 / v2.1	✓	✓	✗	✗	?	✗	?	?	?
OS/2 Warp 3	✓	✓	✗	✗	?	✗	?	?	?
OS/2 Warp 4	✓	✓	✗	✗	?	✗	?	?	?
eComStation	✓	?	✗	✗	?	✗	?	?	?
ArcaOS	✓	?	✗	✗	?	✗	?	?	?
DOS-based
MS-DOS	✓	✓	✓	✓	?	✓	?	?	✓
Windows 1.0x	✓	✓	✓	✓	?	✓	?	?	✓
Windows 2.0 / 2.1	✓	✓	✓	✓	?	✓	?	?	✓
Windows 3.0	✓	✓	✓	✓	?	✓	?	?	✓
Windows 3.1	✓	✓	✓	✓	?	✗	?	?	✓
Windows 9x series	✓	✓	✓	✓	?	✗	?	?	✓
Windows NT
Windows NT 3.1	✓	✓	✗	~*	?	✗	?	?	?
Windows NT 3.5	✓	✓	✗	✗	?	✗	?	?	?
Windows NT 3.51	✓	✓	✗	✗*	?	✗	?	?	?
Windows NT 4.0	✓	✓	✗	✗*	?	✗	?	?	?
Windows NT 5.x	~	~	✗	~	?	✗	✗	?	✗
Windows NT 6.x	?	?	✗	✗	?	✗	✗	?	✗
Linux
Debian	?	?	?	?	?	?	?	?	?
Other x86 Operating Systems
Coherent	?	?	?	?	?	?	?	?	?
CP/M-86	?	?	?	?	?	?	?	?	?
Inferno	?	?	?	?	?	?	?	?	?
PC/GEOS	?	?	?	?	?	✓	?	?	?
NetWare	?	?	?	?	?	?	?	?	?
Solaris	?	?	?	?	?	?	?	?	?
Xenix	?	?	?	?	?	?	?	?	?

Hardware and peripheral support

For software that can run hardware features designed for PC-9800 system, see NEC PC-9800 series#Hardware features and peripherals.

For extensive list of hardware support solely for 86Box emulator, see 86Box#Hardware support.

For extensive list of hardware support solely for PCem emulator, see PCem#Hardware support.

Side note: Please don't bump/spam GitHub threads/issues and feature request pages. This list only includes parts and accessories that can be possible to emulated through software or will be possible in the near future. Including everything would result in an endless list.

x86 CPU's

• CMOV(Conditional Move): Critical for software post-1995 (e.g., Windows NT 4.0, games using optimized compilers). Emulators like 86Box and PCem support CMOV for Pentium Pro and later CPUs (e.g., Pentium II), but DOSBox forks (Pure, X, Staging) often lack full CMOV support, as they prioritize performance over accuracy (see our table’s footnote on DOSBoxForksCPU). This can cause compatibility issues with CMOV-dependent software.
• CX8(CMPXCHG8B): Essential for multitasking OSes like Windows 95/NT and multithreaded applications. Supported by most emulators for 486 and later CPUs (e.g., 86Box, PCem, UniPCemu, MAME), but DOSBox forks may simplify its implementation, risking compatibility with niche software.
• MMX and 3DNow!: Key for 1990s multimedia and games. DOSBox Pure lacks MMX support, limiting compatibility, while DOSBox-X and Staging offer partial support. 86Box and PCem handle MMX and 3DNow! well.
• SSE, SSE2, SSE3: Relevant for late 1990s to mid 2000s software (e.g., DirectX 7/8/9.0c games). PCBox has experimental SSE2, SSE3 and SSSE3 emulation support, but others don’t, as shown in the table (CPU emulation support). SSE2/SSE3, unsupported by most emulators (if not all) due to their focus on earlier CPUs.
• PAE: Supported by 86Box and PCem for Pentium Pro and Pentium II. DOSBox forks may not fully emulate PAE due to their simplified CPU emulation.

Name	86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
AMD
Am386	✓	✓	?	?	?	?	?	?	?
Am486	✓	✓	?	?	?	?	?	?	?
Am5x86	✓	✓	✗	✗	?	✗	✗	?	✗
K5	✓	✓	✗	✗	?	✗	✗	?	✗
K6	✓	✓	✗	✗	?	✗	✗	?	?
K6-II	✓	✓	✗	✗	?	✗	✗	?	?
K6-III K6-III+ K6-2+	✓	✓	✗	✗	?	✗	✗	?	?
Athlon Classic	✗	✗	?	~	?	✗	✗	?	?
Athlon XP	✗	✗	✗	✗	?	✗	✗	?	✗
Auctor
Maple	✗	✗	?	?	?	?	?	?	?
Advantech
EVA-X4150	✗	✗	?	?	?	?	?	?	?
EVA-X4300	✗	✗	?	?	?	?	?	?	?
Centaur Technology
Winchip C6	✗	✓	?	?	?	?	?	?	?
Winchip 2	✓	✓	?	?	?	?	?	?	?
Winchip 2A	✓	✓	?	?	?	?	?	?	?
Winchip 2B	✗	✗	?	?	?	?	?	?	?
Winchip 3	✗	✗	?	?	?	?	?	?	?
Chips and Technologies
Super386	✗	✗	?	?	?	?	?	?	?
Cyrix
Cx486SLC	✓	✗	?	?	?	?	?	?	?
Cx486SRx2	✓	✗	?	?	?	?	?	?	?
Cx486DLC	✓	✗	?	?	?	?	?	?	?
Cx486DRx2	✓	✗	?	?	?	?	?	?	?
Cx486	✓	✓	?	?	?	?	?	?	?
5x86	✓	✓	✗	✗	?	✗	✗	?	✗
MediaGX	✗	✗	?	?	?	?	?	?	?
6x86	✓	✓	✗	✗	?	✗	✗	?	✗
Cyrix III	✓	✓	✗	✗	?	✗	?	?	✗
DM&P Electronics
M6117D	✗	✗	?	?	?	?	?	?	?
Vortex86	✗	✗	?	?	?	?	?	?	?
Intel
8086	✓	✓	✓	~	?	✓	✓	?	✓
80286	✓	✓	✓	~	?	✗	✓	?	✓
386	✓	✓	✓	~	?	✗	✓	?	✓
486	✓	✓	✓	~	?	✗	✓	?	✓
RapidCAD	✓	✓	✓	~	?	✗	✓	?	✓
Pentium Pentium MMX	✓	✓	✓	~ (no MMX)	?	✗	✓	?	✗
Pentium Pro	✓	✓	?	✗	?	✗	✓	?	✗
Pentium II	✓	✓	?	~	?	✗	✓	?	✗
Celeron (P6)	✓	✓	?	✗	?	✗	?	?	✗
Pentium III	~	✗	?	~	?	✗	✗	?	✗
Pentium 4	✗	✗	?	✗	?	✗	✗	?	✗
Kombinat Mikroelektronik Erfurt
U80601	✗	✗	?	?	?	?	?	?	?
NEC
V20	✓	✗	?	?	?	✓	?	?	?
V30	✓	✗	?	?	?	?	?	?	?
V40	✗	✗	?	?	?	?	?	?	?
V50	✗	✗	?	?	?	?	?	?	?
NexGen
Nx586	✗	✗	?	?	?	?	?	?	?
Rise Technology
mP6	✗	✗	?	?	?	?	?	?	?
Transmeta
Crusoe	✗	✗	?	?	?	?	?	?	?
Efficeon	✗	✗	?	?	?	?	?	?	?
UMC
Green CPU	✗	✗	?	?	?	?	?	?	?
Unknown
K1810VM86	✗	✗	?	?	?	?	?	?	?
VIA Technologies
VIA C3	~	✗	?	?	?	?	?	?	?
VIA C7	✗	✗	?	?	?	?	?	?	?
VIA CoreFusion	✗	✗	?	?	?	?	?	?	?
VIA Eden	✗	✗	?	?	?	?	?	?	?
ZF Micro
ZFx86	✗	✗	?	?	?	?	?	?	?

Graphics Cards & GPU's

This table includes graphics cards and GPUs, as well as graphics chips used by third-party manufacturers who produced cards based on these chips. wip, any volunteer?

3D-capable

OpenGL 1.3 to 2.0, DirectX 7 and DirectX 8.1 T&L capable hardware will not be included (even though it is significant for late Windows 9x era) until significant advancements in development. Furthermore, DirectX 9.0a, 9.0b, 9.0c and shader model 3.0 hardware are critical for the Windows XP era, with DirectX 10.0, 10.1 and shader model 4.1 vital for Vista. However, given the current challenges with SSE, SSE2 and SSE3 CPU hardware emulation and the seemingly unattainable goal of DirectX 7 GPU emulation via LLE method, progress remains limited. Future developments, as discussed in the #Emulation issues and #References sections, may provide alternative methods to make this possible.

Name	86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
3Dfx
Voodoo Graphics	✓	✓	?	✓	?	✗	✗	?[6]	✗
Voodoo Rush (Alliance)	✗	✗	✗	✗	✗	✗	✗	✗	✗
Voodoo 2	~	~	✗	✗	✗	✗	✗	?[7]	✗
Voodoo Banshee	~	~	✗	✗	✗	✗	✗	?[8]	✗
Voodoo 3	~	~	✗	✗	✗	✗	✗	✗	✗
Voodoo Velocity 100	~	✗	✗	✗	✗	✗	✗	✗	✗
Voodoo 4	✗	✗	✗	✗	✗	✗	✗	✗	✗
Voodoo 5	✗	✗	✗	✗	✗	✗	✗	✗	✗
3Dlabs
3Dlabs GameGlint / 3D Blaster (Creative Labs)	✗	✗	✗	✗	✗	✗	✗	✗	✗
3Dlabs Permedia / C3000 (PowerColor)	✗	✗	✗	✗	✗	✗	✗	✗	✗
3Dlabs Permedia	✗	✗	✗	✗	✗	✗	✗	✗	✗
3Dlabs Permedia 2 / AccelSTAR II (AccelGraphics)	✗	✗	✗	✗	✗	✗	✗	✗	✗
3Dlabs Permedia 2 / Fire GL 1000 PRO (Diamond Multimedia)	✗	✗	✗	✗	✗	✗	✗	✗	✗
3Dlabs Permedia 2 / GLoria Synergy (ELSA)	✗	✗	✗	✗	✗	✗	✗	✗	✗
3Dlabs Permedia 2 / Graphics Blaster Exxtreme (Creative Labs)	✗	✗	✗	✗	✗	✗	✗	✗	✗
3Dlabs Permedia 2 / Winner 2000/Office (ELSA)	✗	✗	✗	✗	✗	✗	✗	✗	✗
ELSA GLoria-4 / GLINT 300SX	✗	✗	✗	✗	✗	✗	✗	✗	✗
Diamond Fire GL 3000 / GLINT 500TX	✗	✗	✗	✗	✗	✗	✗	✗	✗
ATI
3D Rage / Mach64 GT	✗	✗	✗	✗	✗	✗	✗	✗	✗
3D Rage II / Mach64 GT-B	✗	✗	✗	✗	✗	✗	✗	✗	✗
3D Rage II+ DVD / Mach64 GT-B	✗	✗	✗	✗	✗	✗	✗	✗	✗
3D Rage Pro	✗	✗	✗	✗	✗	✗	✗	✗	✗
Rage XL / Rage 3	WIP[9]	✗	✗	✗[10]	✗	✗	✗	✗	✗
Rage 128 / Rage 4	✗	✗	✗	✗[11]	✗	✗	✗	✗	✗
Cirrus Logic
CL-GD5464	✗	✗	✗	✗	✗	✗	✗	✗	✗
CL-GD5465	✗	✗	✗	✗	✗	✗	✗	✗	✗
Diamond Multimedia
Diamond Edge 3D / nVidia NV1	✗	✗	✗	✗	✗	✗	✗	✗	✗
Intel Corporation
i740	✗	✗	✗	✗	✗	✗	✗	✗	✗
810	✗	✗	✗	✗	✗	✗	✗	✗	✗
Matrox Graphics
Matrox MGA Ultima / Matrox IS-ATLAS	✗	✗	✗	✗	✗	✗	✗	✗	✗
Impression Plus / Matrox IS-ATHENA	✗	✗	✗	✗	✗	✗	✗	✗	✗
Millennium / Matrox IS-STORM	✓[12]	✗	✗	✗	✗	✗	✗	✗	✗
Millennium II	✓[13]	✗	✗	✗	✗	✗	✗	✗	✗
Millennium G100	✗	✗	✗	✗	✗	✗	✗	✗	✗
Millennium G200	✗	✗	✗	✗	✗	✗	✗	✗	✗
Millennium G400	✗	✗	✗	✗	✗	✗	✗	✗	✗
Mystique	✓[14]	✗	✗	✗	✗	✗	✗	✗	✗
Productiva G100	✗	✗	✗	✗	✗	✗	✗	✗	✗
Productiva G100-Quad	✗	✗	✗	✗	✗	✗	✗	✗	✗
NVIDIA
Riva 128	WIP	✗	✗	✗	✗	✗	✗	✗	✗
Riva TNT	✗	✗	✗	✗	✗	✗	✗	✗	✗
Riva TNT2	✗	✗	✗	✗	✗	✗	✗	✗	✗
Paradise Computers
Tasmania 3D	✗	✗	✗	✗	✗	✗	✗	✗	✗
PowerVR
Kyro II	?	?	?	?	?	?	?	?	?
PCX1	?	?	?	?	?	?	?	?	?
PCX2	?	?	?	?	?	?	?	?	?
Real3D
Real3D i700	✗	✗	✗	✗	✗	✗	✗	✗	✗
Rendition
Vérité V1000	?	?	?	?	?	?	?	?	?
Vérité V2100	?	?	?	?	?	?	?	?	?
Vérité V2200	?	?	?	?	?	?	?	?	?
S3
Savage3D	✗	✗	✗	✗	✗	✗	✗	✗	✗
Savage4	✗	✗	✗	✗	✗	✗	✗	✗	✗
Trident
3DImage 9750	✗	✗	✗	✗	✗	✗	✗	✗	✗
Blade 3D	✗	✗	✗	✗	✗	✗	✗	✗	✗
Cyber9397	✗	✗	✗	✗	✗	✗	✗	✗	✗
CyberBlade XP	✗	✗	✗	✗	✗	✗	✗	✗	✗
ProVidia9685	✗	✗	✗	✗	✗	✗	✗	✗	✗
VideoLogic
Neon 250	✗	✗	✗	✗	✗	✗	✗	✗	✗

2D-only

Name	86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
Alliance Semiconductor
ProMotion 3210	✗	✗	?	?	?	?	?	?	?
ProMotion 6410	✗	✗	?	?	?	?	?	?	?
ProMotion aT24	✗	✗	?	?	?	?	?	?	?
ProMotion aT3D	✗	✗	?	?	?	?	?	?	?
ATI
ATI 18800 (VGA Wonder)	✓	✓	?	?	?	?	?	?	?
ATI 28800 (VGA Wonder XL)	✓	✓	?	?	?	?	?	?	?
ATI Graphics / Mach64 GX	✓	✓	?	?	?	?	?	?	?
ATI Win / Mach64 CT	✗	✗	?	?	?	?	?	?	?
ATI Video Expression / Mach64 VT2	✓	✓	?	?	?	?	?	?	?
Cirrus Logic
CL-GD 5401	✓	✗	?	?	?	?	?	?	?
CL-GD 5402	✓	✓	?	?	?	?	?	?	?
CL-GD 5420	✓	✗	?	?	?	?	?	?	?
CL-GD 5422	✓	✗	?	?	?	?	?	?	?
CL-GD 5424	✓	✗	?	?	?	?	?	?	?
CL-GD 5426	✓	✗	?	?	?	?	?	?	?
CL-GD 5428	✓	✓	?	?	?	?	?	?	?
CL-GD 5429	✓	✓	?	?	?	?	?	?	?
CL-GD 5430	✓	✓	?	?	?	?	?	?	?
CL-GD 5434	✓	✓	?	?	?	?	?	?	?
CL-GD 5436	✓	✗	?	?	?	?	?	?	?
CL-GD 5440	✓	✗	?	?	?	?	?	?	?
CL-GD 5446	✓	✗	?	?	?	?	?	?	?
CL-GD 5480	✓	✗	?	?	?	?	?	?	?
Hercules Computer Technology
Hercules Text Card (WMA)	✗	✗	?	?	?	✗	?	?	?
Hercules Graphics Card (HGC)	✓	✓	?	?	?	✓	?	?	?
Hercules Graphics Card Plus	✓	✗	?	?	?	✗	?	?	?
Network Card Plus (HNC)	✗	✗	?	?	?	✗	?	?	?
Color Card	✗	✗	?	?	?	✗	?	?	?
InColor Card	✓	✓	?	?	?	✗	?	?	?
IBM
Monochrome Display Adapter (MDA)	✓	✓	?	?	?	✓	?	?	?
Color Graphics Adapter (CGA)	✓	✓	?	?	?	✓	?	?	?
Enhanced Graphics Adapter (EGA)	✓	✓	?	?	?	✓	?	?	?
Multi-Color Graphics Array (MCGA)	✗	✗	?	?	?	?	?	?	?
Professional Graphics Controller (PGC)	✓	✗	?	?	?	✗	?	?	?
Video Graphics Array (VGA)	✗	✓	✗	✗	✗	✗	✗	✗	✗
8514	✓	✗	?	?	?	?	?	?	?
InteGraphics Systems
IGA 1680_A	✗	✗	?	?	?	?	?	?	?
Intel Corporation
i750	✗	✗	?	?	?	✗	?	?	?
Kama SX094	✗	✗	?	?	?	?	?	?	?
Matrox Graphics
Impression	✗	✗	✗	✗	✗	✗	✗	✗	✗
Impression Pro	✗	✗	✗	✗	✗	✗	✗	✗	✗
NEC
μPD7220	✗	✗	?	?	?	✗	?	?	?
Orchid Technology
Orchid Graphics Adapter	✗	✗	?	?	?	?	?	?	?
Paradise Computers
Modular Graphics Card (MGC)	✗	✗	?	?	?	?	?	?	?
Autoswitch EGA	✗	✗	?	?	?	?	?	?	?
PVGA Plus	✗	✗	?	?	?	?	?	?	?
PVGA 1A	✓	✓	?	?	?	?	?	?	?
Plantronics
Colorplus	✓	✓	?	?	?	?	?	?	?
Quadram Corporation
Quadcolor I	✗	✗	?	?	?	?	?	?	?
Quadcolor II	✗	✗	?	?	?	?	?	?	?
S3
S3 86C911	✓	✗	?	?	?	?	?	?	?
S3 Vision864	✓	✓	?	?	?	?	?	?	?
S3 Vision868	✓	✓	?	?	?	?	?	?	?
S3 Trio32	✓	✓	?	?	?	?	?	?	?
S3 Trio64	✓	✓	?	?	?	?	?	?	?
S3 Trio64V+	✓	✓	?	?	?	?	?	?	?
S3 Trio64V2	✓	✓	?	?	?	?	?	?	?
Texas Instruments
Tigacard	✗	✗	?	?	?	?	?	?	?
Trident
Cyber9320	✗	✗	?	?	?	?	?	?	?
TGUI9420	✗	✗	?	?	?	?	?	?	?
TGUI9600	✗	✗	?	?	?	?	?	?	?
TVGA8200	✗	✗	?	?	?	?	?	?	?
TVGA8800	✗	✗	?	?	?	?	?	?	?
TVGA8900	✓	✓	?	?	?	?	?	?	?

Audio

Also see Shaders, filters, and sound#Audio, and Wrappers.

Name	86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
Sound Cards
Adlib	✓	✓	?	?	?	?	?	?	?
Adlib Gold	✓	✓	?	?	?	?	?	?	?
Aztech Sound Galaxy Pro 16	✓	✓	?	?	?	?	?	?	?
Game Blaster	✓	✓	?	?	?	?	?	?	?
Gravis Ultrasound	✓	✓	?	?	?	?	?	?	?
Innovation SSI-2001	✓	✓	?	?	?	?	?	?	?
Sound Blaster 1.x / 2.0	✓	✓	?	?	?	?	?	?	?
Sound Blaster Pro	✓	✓	?	?	?	?	?	?	?
Sound Blaster 16	✓	✓	?	?	?	?	?	?	?
Sound Blaster AWE32	✓	✓	?	?	?	?	?	?	?
Sound Blaster AWE64	✓	✗	?	?	?	?	?	?	?
Sound Blaster PCI 128	✓	✓	?	?	?	?	?	?	?
Creative Sound Blaster Live!	✗	✗	?	?	?	?	?	?	?
Aureal Vortex 1 (e.g., Turtle Beach Montego)	✗	✗	?	?	?	?	?	?	?
Aureal Vortex 2 (e.g., Diamond Monster Sound MX300)	✗	✗	?	?	?	?	?	?	?
Aureal Vortex Advantage	✗	✗	?	?	?	?	?	?	?
Creative Sound Blaster Audigy	✗	✗	?	?	?	?	?	?	?
Creative Sound Blaster Audigy 2	✗	✗	?	?	?	?	?	?	?
Creative Sound Blaster Audigy 2 ZS	✗	✗	?	?	?	?	?	?	?
Tandy PSSJ	✓	✓	?	?	?	?	?	?	?
Windows Sound System	✓	✓	?	?	?	?	?	?	?
PS/1 Audio Card	✓	✓	?	?	?	?	?	?	?
MIDI Synthesizer Modules / Interfaces
Roland MT-32	✓	✗	?	?	?	?	?	?	?
Roland MPU-401	✓	✗	?	?	?	?	?	?	?
External Audio Devices
Covox Speech Thing	✓	✓	?	?	?	?	?	?	?
Disney Sound Source	✓	✓	?	?	?	?	?	?	?

Network Cards

Using proxy projects for retro web browsing experience is recommended.

Name	86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
Novell NE2000	✓	✓	?	?	?	?	?	?	?
Realtek RTL8029AS	✓	✓	?	?	?	?	?	?	?
3Com EtherLink II	✓	✗	?	?	?	?	?	?	?
AMD PCNet-ISA	✓	✗	?	?	?	?	?	?	?
AMD PCnet-ISA+	✓	✗	?	?	?	?	?	?	?
Novell NE1000	✓	✗	?	?	?	?	?	?	?
Racal Interlan EtherBlaster	✓	✗	?	?	?	?	?	?	?
Realtek RTL8019AS	✓	✗	?	?	?	?	?	?	?
Western Digital WD8003E	✓	✗	?	?	?	?	?	?	?
Western Digital WD8003EB	✓	✗	?	?	?	?	?	?	?
Western Digital WD8003EBT	✓	✗	?	?	?	?	?	?	?
NetWorth EtherNext/MC	✓	✗	?	?	?	?	?	?	?
Western Digital WD8003E/A	✓	✗	?	?	?	?	?	?	?
Western Digital WD8003ET/A	✓	✗	?	?	?	?	?	?	?
AMD PCnet-VL	✓	✗	?	?	?	?	?	?	?
AMD PCNet-FAST III	✓	✗	?	?	?	?	?	?	?
AMD PCNet-PCI II	✓	✗	?	?	?	?	?	?	?
PLIP Network	✓	✗	?	?	?	?	?	?	?

MPEG hardware decoders

placeholder text https://www.vogons.org/viewtopic.php?f=46&t=34225&hilit=dvd+accelerators https://en.wikipedia.org/wiki/RealMagic

Mainboards

Name		86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
440BX	ABit AB-BF6	✓	?	✗	✗	?	?	?	?	?
	ABit AB-BH6	?	?	✗	✗	?	?	?	?	?
	ABit AB-BP6	?	?	✗	✗	?	?	?	?	?
Intel 815E	ABit AB-SH6	?	?	✗	✗	?	?	?	?	?

Human Interface Device (HID)

Assign these symbols in "tables" based on;

   ✓: Emulation of the peripheral, including methods mentioned below.
   ~: No emulation of the peripheral, but real peripheral supported through passthrough, or disguise peripheral support through passthrough.
   ✗: No emulation or passthrough support.

Name	86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
Mouse
	Recommended to overclock the PS/2 interrupt frequency to slightly higher value if you're emulating PS/2 device for pointing device on top of higher display refresh rate from emulated guest operating system. Use 86Box's new recompiler, Smaller frames for CPU frame size, OGL renderer, fullscreen it, set guest to 100hz so it runs in VRR in your host's higher refresh rate mode, install a logitech PS2 driver (or Logitech MouseWare) in guest that allows you to disable mouse acceleration and use a 100hz poll rate (Use 200Hz if you choose 2-button mouse). Also see Input lag section and 86Box Docs: Input.
Gamepads
Gravis PC Gamepad	?	?	?	?	?	?	?	?	?
Microsoft SideWinder Game Pad 1.0	?	?	?	?	?	?	?	?	?
	?	?	?	?	?	?	?	?	?
Joystick
Standard joysticks	✓	✓	?	?	?	?	?	?	?
CH Flightstick Pro	✓	✓	?	?	?	?	?	?	?
Microsoft SideWinder Pad	✓	✓	?	?	?	?	?	?	?
Thrustmaster Flight Control System	✓	✓	?	?	?	?	?	?	?

Floppy, CD-ROM and DVD-ROM drives

It's recommended to see Ripping, Home media players and Save disk space for ISOs pages. Also see Copy protection#Emulation section for middleware or disc-check emulation software tools.

• See this documentation for 86Box. There is no optical drive passthrough support for 86Box at the moment[15], so your only choice is using supported disc images. .ISO, MDS/MDF and BIN/CUE (inc. Audio tracks, CDDA) supported.
• DOSbox-X supports CD-ROM or DVD image files with the ISO-9660 (or High-Sierra) filesystem in .ISO, .CUE+.BIN, .MDF or .CHD. Similar to speed profiles for hard disks, up to 72x maximum transfer speed for the drive emulation supported. This way you can enjoy interactive features of your games that comes with notable installers.
• There is a feature request for adding MDF/MDS support to DOSBox-Staging.

Storage

• 86Box supports speed profiles for hard disk (only IDE and ESDI) images. Speed emulation takes the rotation speed, physical layout and cache size of an average period-correct drive into account. The RAM Disk profile runs the drive as fast as the host can manage.

Name	86Box	PCem	DOSBox	DOSBox Forks	DREAMM	MartyPC	UniPCemu	VARCem	MAME
Hard Drive Interface
Standard IDE	✓	✓	?	?	?	?	?	?	?
MFM/RLL	✓	✓	?	?	?	?	?	?	?
ESDI	✓	✓	?	?	?	?	?	?	?
SCSI	✓	✓	?	?	?	?	?	?	?
IDE-XTA	✓	✗	?	?	?	?	?	?	?
Controller Card
Adaptec AHA-1542C	✓	✓	?	?	?	?	?	?	?
Buslogic BT-545S	✓	✓	?	?	?	?	?	?	?
IBM ESDI Fixed Disk Controller	✗	✓	?	?	?	?	?	?	?
IBM SCSI Adapter with Cache	✗	✓	?	?	?	?	?	?	?
Longshine LCS-6821N	✓	✓	?	?	?	?	?	?	?
Rancho RT1000B	✓	✓	?	?	?	?	?	?	?
Trantor T130B	✓	✓	?	?	?	?	?	?	?
XTIDE	✓	✓	?	?	?	?	?	?	?
AT Fixed Disk Adapter	✗	✓	?	?	?	?	?	?	?
DTC 5150X	✓	✓	?	?	?	?	?	?	?
Fixed Disk Adapter (Xebec)	✗	✓	?	?	?	?	?	?	?
Western Digital WD1007V-SE1	✓	✓	?	?	?	?	?	?	?
ST-11M (MFM)	✓	✗	?	?	?	?	?	?	?
ST-11R (RLL)	✓	✗	?	?	?	?	?	?	?
Western Digital WDXT-150	✓	✗	?	?	?	?	?	?	?
Western Digital WD1002A-WX1	✓	✗	?	?	?	?	?	?	?
Acculogic XT-IDE	✓	✗	?	?	?	?	?	?	?
Adaptec AHA-1640	✓	✗	?	?	?	?	?	?	?
BusLogic BT-445C/S	✓	✗	?	?	?	?	?	?	?
BusLogic BT-640A	✓	✗	?	?	?	?	?	?	?
NCR 53C90	✓	✗	?	?	?	?	?	?	?

Emulation issues

A low-level approach seems to be impossible for DirectX 8/9, SSE 2/3 emulation from the Windows XP era. On the other hand, instead of using hardware-assisted-based virtualization approaches such as KVM; using QEMU TCG emulation approach (kind of like Xemu and QEMU's PPC-based macOS emulation?), with the help of projects such as SoftGPU, virtio-gpu, VirGL virtual adapter, various compatibility layers and wrappers, or even an API passthrough approach similar to QEMU 3dfx may be chosen by the developers in the future.

For more information about PC emulation and reverse engineering;

• DOSBox Pure: MMX Instruction Set Support issue page
• DOSBox-X: 3D Graphics Cards that aren't emulated yet
• DOSBox-X: KVM and Hyper-V issue page
• DOSBox-X: virtual GPU adapters such as VMware SVGA/SVGA II, VBoxVGA issue page
• softgpu: [16], [17]
• virtio-gpu: [18][19]
• PCem: Future graphics card emulation
• nt5src - Source code of Windows XP (NT5).

Other projects and emulated systems that have helped, or may potentially help, PC emulators in the future;

• PlayStation 3 emulators - Due to RSX GPU
• PlayStation 4 emulators - Same architecture
• PlayStation 5 emulators - Same architecture
• Xbox emulators - Due to Celeron, NV2A GPU, and is based on modified Windows NT 3.5 ([20], [21], [22])
• Xbox 360 emulators - Due to Xenos GPU and is based on Windows 2000
• Xbox One emulators - Same architecture
• Xbox Series X and Series S - Same architecture
• macOS - Using same GPUs
• Wrappers
• Compatibility layers
• Hypervisor's Virtual GPU Adapters for legacy operating systems
• libcdio, picogus and PCSX2's CDVD - Could be beneficial for implementing reading capability for capable image formats.
• ymfm

External links

• Tech Tangents: 86Box - An Introduction to PC Emulation
• wiki.softhistory.org - List of emulated hardware on 86Box
• VGAMuseum
• theretroweb

FPGA

Main article: MiSTer

---