Compatibility layer

Examples include:

• Wine, which runs some Microsoft Windows binaries on Unix-like systems using a program loader and the Windows API implemented in DLLs
• Windows's application compatibility layers to attempt to run poorly written applications or those written for earlier versions of the platform.[1]
• Lina, which runs some Linux binaries on Windows, Mac OS X and Unix-like systems with native look and feel.
• KernelEX, which runs some Windows 2000/XP programs on Windows 98/Me.
• Executor, which runs 68k-based "classic" Mac OS programs in Windows, Mac OS X and Linux.
• Anbox, an Android compatibility layer for Linux.
• Columbia Cycada, which runs Apple iOS applications on Android systems
• Hybris, library that translates Bionic into glibc calls.
• Darling, a translation layer that attempts to run Mac OS X and Darwin binaries on Linux.
• Windows Subsystem for Linux, which runs Linux binaries on Windows.
• Cygwin, a POSIX-compatible environment that runs natively on Windows.[2]
• 2ine, a project to run OS/2 application on Linux[3]

Compatibility layer in kernel:

• FreeBSD's Linux compatibility layer, which enables binaries built specifically for Linux to run on FreeBSD[4] the same way as the native FreeBSD API layer.[5] FreeBSD also has some Unix-like system emulations, including NDIS, NetBSD, PECoff, SVR4, and different CPU versions of FreeBSD.[6]
• NetBSD has several Unix-like system emulations.[7]
• Windows Subsystem for Linux provides a Linux-compatible kernel interface developed by Microsoft and containing no Linux code, with Ubuntu user-mode binaries running on top of it.[8]
• The PEACE Project (aka COMPAT_PECOFF) has Win32 compatible layer for NetBSD. The project is now inactive.
• On RSTS/E for the PDP-11 series of minicomputers, programs written to run on the RT-11 operating system could run (without recompiling) on RSTS through the RT-11 Run-Time System having its EMT flag set, meaning that an RT-11 EMT instruction that matches a RSTS EMT is diverted to the RT-11 Run-Time System which translates them to the equivalent RSTS EMT. Programs written to take advantage of RSTS directly (or calls to RSTS within the Run-Time system itself) signal this by having a second EMT instruction (usually EMT 255) immediately before the actual RSTS EMT code.

A compatibility layer avoids both the complexity and the speed penalty of full hardware emulation. Some programs may even run faster than the original, e.g. some Linux applications running on FreeBSD's Linux compatibility layer may perform better than the same applications on Red Hat Linux. Benchmarks are occasionally run on Wine to compare it to Windows NT-based operating systems.[9]

Even on similar systems, the details of implementing a compatibility layer can be quite intricate and troublesome; a good example is the IRIX binary compatibility layer in the MIPS architecture version of NetBSD.[10]

A compatibility layer requires the host system's CPU to be (upwardly) compatible to that of the foreign system. For example, a Microsoft Windows compatibility layer is not possible on PowerPC hardware because Windows requires an x86 CPU. In this case full emulation is needed.

Hardware compatibility layers involve tools that allow hardware emulation. Some hardware compatibility layers involve breakout boxes because breakout boxes can provide compatibility for certain computer buses that are otherwise incompatible with the machine.

• Hypervisor
• Paravirtualization
• Emulator
• Cross-platform virtualization
• Computing platform
• Shim (computing)
• Driver wrapper
• Glue code

• Windows XP Application Compatibility Technologies (Dave Morehouse and Todd Phillips, Microsoft Corporation, 1 June 2001)