Look up wabi in Wiktionary, the free dictionary.
| Developer(s) | Sun Microsystems |
|---|---|
| Operating system | Solaris, AIX, Linux |
Wabi is a discontinued commercial software application from Sun Microsystems that implements the Windows Win16 API specification on Solaris and AIX; a version for Linux was also released by Caldera Systems. Wabi runs applications developed for Windows 3.1, Windows 3.11, and Windows for Workgroups.
The technology was originally developed by Praxsys Technologies as the result of discussions in 1990 with Interactive Systems Corporation. The assets of Praxsys were acquired by Sun in the fall of 1992. The name "Wabi" was chosen for two reasons: its meaning in Japanese of balance or harmony, which conjured the notion of a more peaceful coexistence between Windows and Unix software; and, the more obvious implication of it standing for Windows Application Binary Interface, although before its release Sun declared that the name was not an acronym.
Wabi 2.2B was licensed by Caldera for Linux,[1] together with the also licensed Merge.
Wabi development was discontinued in December 1997.
Wabi requires a licensed Windows 3.x installation, unlike similar software that endeavors to implement the entire Windows API, such as Wine or select versions of OS/2. Wabi implements the lowest layers of the Windows environment in the form of the user.dll, kernel.dll, and gdi.dll libraries. All other Windows dlls depend on these three modules, so cloning this functionality allows Windows software to execute correctly on a foreign host system. This approach, as opposed to a full replacement, was thought by the engineering team to be the only rational methodology for success given both the size of Microsoft's ever-expanding efforts and the difficulties of the emulation being precise enough to run commercial software.
Wabi was released for x86 and SPARC systems, and on PowerPC for AIX.[2] To run an x86 Windows environment on SPARC systems, a code translation layer dynamically converts x86 instructions upon first use into SPARC instructions.[3]
In conjunction with its development of the Wabi software, Sun initiated an effort to create an ISO standard, non-proprietary definition of the Windows API. The Public Windows Interface (PWI) was intended to define a public standard to help Sun and other companies clone the Windows environment (such as Willows TWIN,[4] another LGPL implementation of the API[5]), but despite Sun's contention that there was no intellectual property breach, this effort was lobbied against at ISO by Microsoft, being rejected in 1996.[6]