Content deleted Content added
even more contradictions, and I give up |
|||
Line 1:
{{multiple issues|
{{refimprove}}
{{confusing}}
{{contradict}}
}}
{{Infobox Software
| name = Win4Lin
Line 18 ⟶ 21:
'''Win4Lin''' was a [[Proprietary software|proprietary]] [[software]] application for [[Linux]] which allowed users to run a copy of [[Windows 95]], [[Windows 98]], [[Windows Me]], [[Windows 2000]] or [[Windows XP]] applications on their [[Linux]] desktop.<ref name="sams"/> Win4Lin was based on [[Merge (software)|Merge]] software, a product which changed owners several times until it was bought by Win4Lin Inc. Citing changes in the desktop virtualization industry, the software's publisher, Virtual Bridges, has discontinued Win4Lin Pro.<ref name="w4l">{{Cite web|title=Win4Lin Pro|url=http://win4lin.com/wp/|publisher=Virtual Bridges|accessdate=Nov 14, 2012|archiveurl=http://www.webcitation.org/6CAhZoX9Q|archivedate=Nov 14, 2012|deadurl=no}}</ref>
==
{{expand section|Win4VDI}}
In 2006, 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|publisher=[[SAMS Publishing]]|accessdate=Nov 14, 2012|year=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.<ref name="suse"/>
* Win4Lin Pro offered users the ability to install a fully virtualized [[Windows 2000]] or [[Windows XP]].<ref name="suse"/>
Win4Lin Pro used "full" virtualization, whereas Win4Lin 9x was an example of [[paravirtualization]].{{cn}}
The Win4Lin 9x/Pro (henceforth the only technology discussed in this section) operates by running Windows applications in a [[virtual machine]].<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> 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|work=[[Computerworld]]|date=April 4, 2002|accessdate=Nov 14, 2012|pages=1–2}}</ref>
Line 33 ⟶ 39:
Win4Lin was initially based on [[Merge (software)|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., 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.
Virtual Bridges discontinued support for Win4Lin 9x in 2007. The Win4Lin Pro Desktop product ceased to be supported in March 2010.
| |||