Win4Lin

This section needs expansion with: Win4VDI. You can help by adding to it. (February 2014)

In 2006, Win4Lin came in three different versions, depending on the virtualization requirements of the user.^[4]

• Win4Lin 9x allowed the user to run a full copy of Windows 98 or Windows Me inside a virtual machine.^[4]
• Win4Lin Home allowed users to only emulate applications.^[4]
• Win4Lin Pro offered users the ability to install a fully virtualized Windows 2000 or Windows XP.^[4]

The Win4Lin 9x/Pro (henceforth the only technology discussed in this section) operates by running Windows applications in a virtual machine.^[2] Unlike Wine or CrossOver which are compatibility layers, virtualization-based software such as VMware or Win4Lin require users to have a Windows license in order to run applications since they must install a full copy of Windows within the virtual machine.^[5]

Unlike VMware, however, Win4Lin provides the virtual guest operating system with access to the native Linux filesystem, and allows the Linux host to access the guest's files even when the virtual machine is not running.^[2][5] In addition to the convenience this offers, Computerworld found in their 2002 review that Win4Lin gained significant performance over VMware by using the native Linux filesystem, but also noted that this approach (unlike VMware's) limited the installation of only one version of Windows on a Win4Lin machine.^[5]

When the Win4Lin application starts it displays a window on the Linux desktop which contains the Windows desktop environment. Users can then install or run applications as they normally would from within Windows. Win4Lin supports Linux printers, internet connections, and Windows networking, but as of 2000^[update], does not support DirectX and by extension most Windows games.^[6]

They also offered Win4BSD for FreeBSD.^[7]

Win4Lin was initially based on Merge software originally developed at Locus Computing Corporation, and which changed hands several times until it ended in the assets of NeTraverse, which were purchased in 2005 by Win4Lin, Inc.^[8][9] Later that year, they introduced Win4Lin Pro, which was based on a “tuned” version of QEMU and KQEMU, and it hosted Windows NT-versions of Windows.^[10]

In June 2006, Win4Lin released Win4Lin Virtual Desktop Server,^[11] later named Win4VDI based on the same code base. Win4VDI for Linux served Microsoft Windows desktops to thin clients from a Linux server.^[12] It was integrated into VERDE on March 9, 2009.^[13]

Win4Lin, Inc. discontinued Win4Lin 9x on May 30, 2006.^[14] The Win4Lin Pro Desktop product ceased to be supported in March 2010.^{[citation needed]}

This section needs expansion with: reviews from the EL section. You can help by adding to it. (February 2014)

Many users reported that the 9x version ran windows software at near-native speed, even on quite low-powered machines, such as Pentium-IIs.^{[citation needed]}

Nicholas Petereley praised Win4Lin in two of his columns in the year 2000, for its significantly faster performance than its competitor VMware.^[6][38]

• x86 virtualization