Jump to content

Win4Lin: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
cl ref
Line 23: Line 23:


==Overview==
==Overview==
Win4Lin operates by running Windows applications in a [[virtual machine]], but does so while allowing access to the native Linux filesystem.<ref name="sams">{{cite book|last=Hsiao|first=Aron|title=Sams teach yourself Red Hat Fedora 4 Linux: all in one|url=http://books.google.com/books?id=aTDAfvuTZ4IC&pg=PA678|accessdate=Nov. 14, 2012|date=July 7, 2005|publisher=[[SAMS Publishing]]|page=678}}</ref> Win4Lin came in three different versions, depending on the virtualization requirements of the user.<ref name="suse">{{cite book|last=McCallister|first=Michael|title=Suse Linux 10: Unleashed|url=http://books.google.com/books?id=P_mbgQfn3ZAC&pg=PA191|accessdate=Nov. 14, 2012|origyear=2006|pages=191–192}}</ref> Win4Lin 9x allowed the user to run a full copy of [[Windows 98]] or [[Windows Me]] inside a virtual machine.<ref name="suse"/> Win4Lin Home allowed users to only emulate applications. Win4Lin Pro offered users the ability to install a fully virtualized [[Windows 2000]] or [[Windows XP]].<ref name="suse"/> Unlike [[CrossOver Office]] or [[Wine (software)|Wine]], virtualization-based software, such as [[VMware]] or Win4Lin, require users to have a Windows license in order to run applications since they must to install a full copy of Windows within the virtual machine.<ref name="bushong">{{cite news|title=Windows Emulators for Linux: VMware, Win4Lin Face Off|url=http://www.computerworld.com/s/article/69849/Windows_Emulators_for_Linux_VMware_Win4Lin_Face_Off|first=Charles|last=Bushong|date=April 4, 2002|accessdate=Nov. 14, 2012|pages=1–2}}</ref> 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.<ref name="sams"/><ref name="bushong"/> In addition to the convenience this offers, [[Computerworld]] found that Win4Lin gained significant performance over VMware by using the native Linux filesystem.<ref name="bushong"/>
Win4Lin operates by running Windows applications in a [[virtual machine]], but does so while allowing access to the native Linux filesystem.<ref name="sams">{{cite book|last=Hsiao|first=Aron|title=Sams teach yourself Red Hat Fedora 4 Linux: all in one|url=http://books.google.com/books?id=aTDAfvuTZ4IC&pg=PA678|accessdate=Nov. 14, 2012|date=July 7, 2005|publisher=[[SAMS Publishing]]|page=678}}</ref> Win4Lin came in three different versions, depending on the virtualization requirements of the user.<ref name="suse">{{cite book|last=McCallister|first=Michael|title=Suse Linux 10: Unleashed|url=http://books.google.com/books?id=P_mbgQfn3ZAC&pg=PA191|accessdate=Nov. 14, 2012|origyear=2006|pages=191–192}}</ref> Win4Lin 9x allowed the user to run a full copy of [[Windows 98]] or [[Windows Me]] inside a virtual machine.<ref name="suse"/> Win4Lin Home allowed users to only emulate applications. Win4Lin Pro offered users the ability to install a fully virtualized [[Windows 2000]] or [[Windows XP]].<ref name="suse"/> Unlike [[CrossOver Office]] or [[Wine (software)|Wine]] which are emulation-based, 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.<ref name="bushong">{{cite news|title=Windows Emulators for Linux: VMware, Win4Lin Face Off|url=http://www.computerworld.com/s/article/69849/Windows_Emulators_for_Linux_VMware_Win4Lin_Face_Off|first=Charles|last=Bushong|date=April 4, 2002|accessdate=Nov. 14, 2012|pages=1–2}}</ref> 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.<ref name="sams"/><ref name="bushong"/> In addition to the convenience this offers, [[Computerworld]] found that Win4Lin gained significant performance over VMware by using the native Linux filesystem.<ref name="bushong"/>


The Win4Lin application in essence displayed a window on a Linux desktop which contained the Windows desktop environment. As an alternative, the Windows environment could be run full screen, outside of the desktop environment to save on desktop real estate.
The Win4Lin application in essence displayed a window on a Linux desktop which contained the Windows desktop environment. As an alternative, the Windows environment could be run full screen, outside of the desktop environment to save on desktop real estate.

Revision as of 15:48, 14 November 2012

Win4Lin was a proprietary software application for Linux which allowed users to run a copy of Microsoft Windows 95, 98, Me, 2000 or XP applications on their Linux desktop.[1]

Win4Lin
Operating systemLinux
TypeFull virtualization
LicenseProprietary

Overview

Win4Lin operates by running Windows applications in a virtual machine, but does so while allowing access to the native Linux filesystem.[1] Win4Lin came in three different versions, depending on the virtualization requirements of the user.[3] Win4Lin 9x allowed the user to run a full copy of Windows 98 or Windows Me inside a virtual machine.[3] Win4Lin Home allowed users to only emulate applications. Win4Lin Pro offered users the ability to install a fully virtualized Windows 2000 or Windows XP.[3] Unlike CrossOver Office or Wine which are emulation-based, 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.[4] 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.[1][4] In addition to the convenience this offers, Computerworld found that Win4Lin gained significant performance over VMware by using the native Linux filesystem.[4]

The Win4Lin application in essence displayed a window on a Linux desktop which contained the Windows desktop environment. As an alternative, the Windows environment could be run full screen, outside of the desktop environment to save on desktop real estate.

Win4Lin was designed with business users in mind, and as such, did not support features such as MDI, in favor of support for Microsoft Office-style application compatibility.

History

Win4Lin was based on Merge software developed by engineers at Locus Computing Corporation, founded by Gerald J. Popek and others in 1982, which was later taken over by a company called Platinum Technology. Merge was originally developed to run DOS/Windows 3.1 under UNIX System V Release 2 on an AT&T 6300+ personal computer that contained an Intel 80286 processor. AT&T announced availability on October 9, 1985, referring to the bundled Merge software as SimulTask. Later Merge was enhanced to make use of the VM86 mode provided by the Intel 80386 processor; that version was offered with Microport SVR3 starting in 1987, and subsequently with SCO Unix.

The Merge technology was then bought by a company called DASCOM which was in turn bought by IBM. A company called TreLOS was then spun off that continued the development of the virtual machine software and created Win4Lin. TreLOS and LastFoot.com merged in 2000 to form NeTraverse, Inc.

In early 2005 the assets of NeTraverse were purchased to form Win4Lin Inc. which introduced Win4Lin Pro Desktop: this was based on a 'tuned' version of QEMU and KQEMU, and it hosted [Windows NT]-versions of Windows. In June 2006, Win4Lin released Win4VDI for Linux based on the same code base. Win4VDI for Linux served Microsoft Windows desktops to thin clients from a Linux server. Win4Lin Pro used "full" virtualization, whereas Win4Lin 9x was an example of paravirtualization. Many users reported that the 9x version ran windows software at near-native speed, even on quite low-powered machines, such as Pentium-IIs.

Virtual Bridges discontinued support for Win4Lin 9x in 2007. The Win4Lin Pro Desktop product ceased to be supported in March 2010.

See also

References

  1. ^ a b c Hsiao, Aron (July 7, 2005). Sams teach yourself Red Hat Fedora 4 Linux: all in one. SAMS Publishing. p. 678. Retrieved Nov. 14, 2012. {{cite book}}: Check date values in: |accessdate= (help)
  2. ^ "Win4Lin Pro". Virtual Bridges. Archived from the original on Nov. 14, 2012. Retrieved Nov. 14, 2012. {{cite web}}: Check date values in: |accessdate= and |archivedate= (help); Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  3. ^ a b c McCallister, Michael. Suse Linux 10: Unleashed. pp. 191–192. Retrieved Nov. 14, 2012. {{cite book}}: Check date values in: |accessdate= (help)
  4. ^ a b c Bushong, Charles (April 4, 2002). "Windows Emulators for Linux: VMware, Win4Lin Face Off". pp. 1–2. Retrieved Nov. 14, 2012. {{cite news}}: Check date values in: |accessdate= (help)

External links