Jump to content

Wine (software)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Trek00 (talk | contribs) at 20:58, 16 June 2012 (added source for DLLs implemented by Wine). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Wine
Original author(s)Alexandre Julliard
Developer(s)Wine authors
(1,359)
Initial release4 July 1993 (1993-07-04)
Repository
Written inC
Operating systemUnix-like systems
PlatformCross-platform
Size18 MB (compressed)
TypeCompatibility layer
LicenseGNU LGPL v2.1+
Websitewww.winehq.org

Wine is a free and open source software application that aims to allow computer programs written for Microsoft Windows to run on Unix-like operating systems. Wine also provides a software library, known as Winelib, against which developers can compile Windows applications to help port them to Unix-like systems.[1]

Wine is a compatibility layer. It duplicates functions of a Windows computer by providing alternative implementations of the DLLs that Windows programs call,"Wine architecture". Wine HQ. Retrieved 16 June 2012.</ref> and a process to substitute for the Windows NT kernel. This method of duplication differs from other methods that might also be considered emulation, where Windows programs run in a virtual machine.[2] Wine is predominantly written using black-box testing reverse-engineering, to avoid copyright issues.[3]

The name Wine initially was an acronym for WINdows Emulator.[4] Its meaning later shifted to the recursive backronym, Wine Is Not an Emulator in order to differentiate the software from other emulators.[5] While the name sometimes appears in the forms WINE and wine, the project developers have agreed to standardize on the form Wine.[6]

In a 2007 survey by desktoplinux.com of 38,500 Linux desktop users, 31.5% of respondents reported using Wine to run Windows applications.[7] This plurality was larger than all x86 virtualization programs combined, as well as larger than the 27.9% who reported not running Windows applications.[8]

History

Bob Amstadt (the initial project leader) and Eric Youngdale started the Wine project in 1993 as a way to run Windows applications on Linux. It was inspired by two Sun Microsystems' products, the Wabi for the Solaris operating system, and the Public Windows Initiative[9] (an attempt to get the Windows API fully reimplemented in the public domain as an ISO standard, but rejected by the entity due to pressure from Microsoft in 1996).[10] Wine originally targeted Windows 3.x (16-bit) application software, but as of 2010 focuses on 32-bit and 64-bit applications. The project originated in discussions on Usenet in comp.os.linux in June 1993.[11] Alexandre Julliard has led the project since 1994.

The project has proved time-consuming and difficult for the developers, mostly because of incomplete and incorrect documentation of the Windows API. While Microsoft extensively documents most Win32 functions, some areas such as file formats and protocols have no official Microsoft specification. Microsoft Windows also includes undocumented low-level functions and obscure bugs that Wine must duplicate precisely in order to allow some applications to work properly.[12] Consequently, the Wine team has reverse-engineered many function calls and file formats in such areas as thunking.[citation needed] More recently some developers have suggested enhanced tactics such as examining the sources of extant free and open-source software.

The Wine project originally released Wine under the same MIT License as the X Window System, but owing to concern about proprietary versions of Wine not contributing their changes back to the core project,[13] work as of March 2002 has used the LGPL for its licensing.[14]

Wine officially entered beta with version 0.9 on 25 October 2005.[15] Version 1.0 was released on 17 June 2008,[16] after 15 years of development. Version 1.2 was released on 16 July 2010.[17] Development versions are released roughly every two weeks.

Version 1.4 was released on 7 March 2012.[18] The 1.4 release provides many improvements, such as the following (as quoted from the Wine HQ website)[18]: "This release represents 20 months of development effort and over 16,000 individual changes. The main highlights are the new DIB graphics engine, a redesigned audio stack, and full support for bidirectional text and character shaping. It also contains a lot of improvements across the board, as well as support for many new applications, notably Microsoft Office 2010."

Corporate sponsorship

The main corporate sponsor of Wine is CodeWeavers, which employs Julliard and many other Wine developers to work on Wine and on CrossOver, CodeWeavers' supported version of Wine. Crossover includes some application-specific tweaks not considered suitable for the WineHQ version, as well as some additional proprietary components.[19]

The involvement of Corel for a time assisted the project, chiefly by employing Julliard and others to work on it. Corel had an interest in porting WordPerfect Office, its office suite, to Linux (especially Corel Linux). Corel later cancelled all Linux-related projects after Microsoft made major investments in Corel, stopping their Wine effort.[20]

Other corporate sponsors include Google, which hired CodeWeavers to fix Wine so Picasa ran well enough to be ported directly to Linux using the same binary as on Windows; Google later paid for improvements to Wine's support for Adobe Photoshop CS2. Wine is also a regular beneficiary of Google's Summer of Code program.[21][22]

Architecture

ClamWin GUI

Wine implements the Windows API entirely in user space, rather than as a kernel module. Services normally provided by the kernel in Windows[23] are provided by a daemon known as the wineserver, whose task is to implement basic Windows functionality, as well as integration with the X Window System, and translation of signals into native Windows exceptions.

Although Wine implements some aspects of the Windows kernel, it is not possible to use native Windows drivers with it, due to Wine's underlying architecture. This prevents certain applications from working, such as some copy-protected titles.[clarification needed]

Wine is primarily developed for Linux, but the Mac OS X, FreeBSD, and Solaris ports are currently (as of January 2009) well maintained.[24] Wine is also available for OpenBSD and NetBSD, through OpenBSD Ports [25] and NetBSD pkgsrc, respectively. Since October 2010, Wine also works on the ARM platform when used as Winelib (which lets developers compile Windows code on Linux using Wine as a library).[26] Some versions of Wine's DLLs are available for Microsoft Windows,[27] but Wine does not fully compile or run on Windows yet.[28]

Functionality

An animation showing progress in application compatibility according to test results from Wine AppDB (click on the picture to see the animation).
  Software that runs flawlessly ("Platinum")
  Software that runs flawlessly with configuration ("Gold")
  Software with minor Issues ("Silver")
  Software with major Issues ("Bronze")
  Unusable software ("Garbage")

The developers of the Direct3D portions of Wine have continued to implement new features such as pixel shaders to increase game support.[29] Wine can also use native DLLs directly, thus increasing functionality, but then a license for Windows is needed unless the DLLs were distributed with the application itself.

winecfg is a GUI configuration utility included with Wine. Winecfg makes configuring Wine easier by making it unnecessary to edit the registry directly, although, if needed, this can be done with the included registry editor (similar to Windows regedit). Wine also includes its own open-source implementations of several other Windows programs, such as notepad, wordpad, control, iexplore, and explorer.

The Wine Application Database AppDB is a community-maintained database about which Windows applications work with Wine, and how well they work.

Backward compatibility

File:Wineon64bit.png
Wine running an old 16-bit Windows game called Chip's Challenge on an x86-64 (64-bit) computer.
A screenshot showing how Wine can be configured to mimic different versions of Windows, going as far back as Windows 2.0 as shown.

Wine ensures good backward compatibility with legacy Windows applications, including those written for Windows 3.1.[30] Wine can mimic different Windows versions required for some programs, going as far back as Windows version 2.0.[31] However, Windows 1.x and Windows 2.x support was removed from Wine development version 1.3.12 if DOSBox is installed on the system[citation needed] (see below on MS-DOS). You can nevertheless select "Windows 2.0" as the Windows version you want to emulate, but Wine still won't run Windows 2.0 programs.

Backward compatibility in Wine is superior to that of Windows, as newer versions of Windows can force users to upgrade legacy Windows applications. In many cases, Wine can offer better legacy support than newer versions of Windows with "Compatibility Mode". As illustrated by screenshot on the left, Wine can run 16-bit Windows programs on a 64-bit operating system, which uses an x86-64 (64-bit) CPU. 64-bit versions of Microsoft Windows cannot run 16-bit Windows programs.[32]

Wine partially supports Windows console applications, and the user can choose which backend to use to manage the console (choices include[33] raw streams, curses, and user32). When using the raw streams or curses backends, Windows applications will run in a Unix terminal.

64-bit applications

Preliminary support for 64-bit Windows applications was added to Wine 1.1.10, in December 2008.[34] This currently requires at least gcc version 4.4, and the Wine developers expect that it will take significant time before support stabilizes. However, as almost all Windows applications are currently available in 32-bit versions, and the 32-bit version of Wine can run on 64-bit platforms, this is seen as a non-issue.

The 64-bit port of Wine also has preliminary WoW64 support (as of April 2010), which allows both 32-bit and 64-bit Windows applications to run inside the same Wine instance.[35]

Third-party applications

File:Pegasus Mail Wine.png
Pegasus Mail running via Wine, version 1.1.42. (The font smoothing is enabled by using winetricks. You can see the smooth fonts in the picture when it's viewed at full size.)

Some applications require more tweaking than simply installing the application in order to work properly, such as manually configuring Wine to use certain Windows DLLs. The Wine project does not integrate such workarounds into the Wine codebase, instead preferring to focus solely on improving Wine's implementation of the Windows API. While this approach focuses Wine development on long-term compatibility, it makes it difficult for users to run applications that require workarounds. Consequently, many third-party applications have been created to ease the use of those applications that don't work out of the box within Wine itself. The Wine wiki maintains a page of current and obsolete third-party applications.[36]

  • CrossOver, proprietary software
  • Bordeaux is a proprietary Wine GUI configuration manager that runs winelib applications. It also supports installation of third-party utilities, installation of applications and games, and the ability to use custom configurations. Bordeaux currently runs on Linux, FreeBSD, PC-BSD, Solaris, OpenSolaris, OpenIndiana,[37][38] and Mac OS X computers.
  • Winetricks is a script to install some basic components (typically Microsoft DLLs and fonts) required for some applications to run correctly under Wine. The Wine project will accept bug reports for users of Winetricks, unlike most third-party applications. It is maintained by Wine developer Dan Kegel.[39]
  • QT4Wine is an open Gui for advanced setup of Wine.
  • Wine-Doors is an application-management tool for the GNOME desktop which adds functionality to Wine. Wine-Doors is an alternative to WineTools which aims to improve upon WineTools' features and extend on the original idea with a more modern design approach.[40]
  • IEs4Linux is a utility to install all versions of Internet Explorer, including versions 4 to 6 and version 7 (in beta).[41]
  • PlayOnLinux is an application to ease the installation of Windows applications (primarily games). There is also a corresponding Macintosh version called PlayOnMac
  • Wineskin is a utility to manage Wine engine versions and create wrappers for OS X.[42]

Windows CE

Wine will not run Windows CE programs. There is an ongoing project to port Wine to ARM processors, which may in the future be used as a base for a WineCE running Windows CE programs.[43]

MS-DOS

Early versions of Microsoft Windows run on top of MS-DOS and Windows programs may depend on MS-DOS programs being runnable. Wine does not have good support for MS-DOS, but starting with development version 1.3.12, Wine tries running MS-DOS programs in DOSBox if DOSBox is available on the system.[44] However, due to a bug, current versions of Wine incorrectly identify Windows 1.x and Windows 2.x programs as MS-DOS programs, attempting to run them in DOSBox (which does not work).[45]

Other versions of Wine

The core Wine development aims at a correct implementation of the Windows API as a whole and has sometimes lagged in some areas of compatibility with certain applications. Direct3D, for example, remained unimplemented until 1998,[46] although newer releases have had an increasingly complete implementation.[47]

CodeWeavers markets CrossOver specifically for running Microsoft Office and other major Windows applications, including some games. CodeWeavers employs Alexandre Julliard to work on Wine and contributes most of its code to the Wine project under the LGPL. CodeWeavers also released a new version called Crossover Mac for Intel-based Apple Macintosh computers on 10 January 2007.[48]

CrossOver includes now the functionality of both the CrossOver Games and CrossOver Pro lines therefore CrossOver Games and CrossOver Pro are no longer available as single products.[49]

CrossOver Games was optimized for running Windows video games. Unlike CrossOver, it didn't focus on providing the most stable version of Wine. Instead, experimental features are provided to support newer games.[50]

TransGaming Technologies produced the proprietary Cedega software. Formerly known as WineX, Cedega represented a fork from the last MIT-licensed version of Wine in 2002. Much like Crossover Games, TransGaming's Cedega was targeted towards running Windows video games. On 7 January 2011, TransGaming Technologies announced continued development of Cedega Technology under the GameTree Developer Program. TransGaming Technologies allowed members to keep using their Cedega ID and password until 28 February 2011.[51]

TransGaming has also produced Cider, a library for Apple–Intel architecture Macintoshes. Instead of being an end-user product, Cider (like Winelib) is a wrapper allowing developers to adapt their games to run natively on Intel Mac OS X without any changes in source code.

The Russian company Etersoft has been developing a proprietary version of Wine since 2006. WINE@Etersoft supports popular Russian applications (for example, 1C:Enterprise by 1C Company).[52] For 2010, Etersoft was going to issue WINE@Etersoft CAD, which is oriented towards CAD systems such as AutoCAD, Bricscad, and Compass-3D.

Other projects using Wine source code include:

  • ReactOS, a project to write an operating system compatible with Windows NT versions 5.x and up (which includes Windows 2000 and its successors) down to the device driver level. ReactOS uses Wine source code considerably, but because of architectural differences, ReactOS code (such as dlls written specifically for it, like ntdll, user32, kernel32, gdi32, and advapi) is not generally reused in Wine.[53] In July 2009, Aleksey Bragin, the ReactOS project lead, started[54] a new ReactOS branch called Arwinss,[55] and it was officially announced in January 2010.[56] Arwinss is an alternative implementation of the core Win32 components, and uses mostly unchanged versions of Wine's user32.dll and gdi32.dll.
  • Linux Unified Kernel, a project intended to be binary-compatible with application software and device drivers made for Microsoft Windows and Linux. This kernel imports all the key features of the Windows operating system kernel into the Linux kernel to support both Linux and Windows applications and device drivers.
  • Darwine, a port of the Wine libraries to Darwin and Mac OS X. Kronenberg.org stated "As some might have read on Wine-Devel, Darwine is dead for good. The OS X port of Wine formerly known as Darwine is now Wine." Kronenberg continues work on an Intel Mac version called Winebottler
  • Wineskin, an open source Wine GUI configuration manager for Mac OS X. Wineskin creates a wrapper around Wine in the form of a normal Mac Application. The wrapper can also be used to make a distributable “port” of software.[57]
  • Odin, a project to run Win32 binaries on OS/2 or convert them to OS/2 native format. The project also provides the Odin32 API to compile Win32 programs for OS/2.
  • E/OS, a project attempting to allow any program designed for any operating system to be run without the need to actually install any other operating system.
  • Rewind, a defunct MIT-licensed fork of the last MIT-licensed version of Wine.
  • Parallels Desktop 3 for Mac, a proprietary product that uses some Wine code for its DirectX handling.
  • VirtualBox v3.x, a virtual machine that uses some Wine code for its Direct3D handling.

Reception

The Wine project has received a number of technical and philosophical complaints and concerns over the years.

Security

Because of Wine's ability to run Windows binary code, concerns have been raised over native Windows viruses and malware affecting Unix-like operating systems.[58] Wine can run much malware, but programs running in Wine are confined to the current user's privileges, restricting some undesirable consequences. This is one reason Wine should never be run as the superuser.[59] Malware research software such as ZeroWine[60] runs Wine on Linux in a virtual machine, to keep the malware completely isolated from the host system.

Another security concern is when the implemented specifications are ill-designed and allow for security compromise. Because Wine implements these specs, it will also implement any security vulnerabilities they contain.[61]

Wine vs. native Unix applications

A common concern about Wine is that its existence means that vendors are less likely to write native Linux, Mac OS X, and BSD applications. As an example of this, it is worth considering IBM's 1994 operating system, OS/2 Warp. An article describes the weaknesses of OS/2 which killed it, the first one being:

OS/2 offered excellent compatibility with DOS and Windows 3.1 applications. No, this is not an error. Many application vendors argued that by developing a DOS or Windows app, they would reach the OS/2 market in addition to DOS/Windows markets and they didn't develop native OS/2 applications.[62]

The Wine project itself responds to these complaints on one of its Wiki pages:

For most people there remain a handful of programs locking them in to Windows. It's obvious there will never be a Microsoft Office ported to Linux, however older versions of programs like TurboTax won't be ported either. Similarly, there are tens of thousands of games and internal corporate applications which will never be ported. If you want to use Linux and rely on any legacy Windows application, something like Wine is essential... Wine makes Linux more useful and allows for millions of users to switch who couldn't otherwise. This greatly raises Linux marketshare, drawing more commercial and community developers to Linux.[63]

Also, the Wine Wiki page claims that Wine can help break the chicken-and-egg problem for Linux on the desktop[64]:

This brings us to the chicken and egg issue of Linux on the desktop. Until Linux can provide equivalents for the above applications, its market share on the desktop will stagnate. But until the market share of Linux on the desktop rises, no vendor will develop applications for Linux. How does one break this vicious circle?

Again, Wine can provide an answer. By letting users reuse the Windows applications they have invested time and money in, Wine dramatically lowers the barrier that prevents users from switching to Linux. This then makes it possible for Linux to take off on the desktop, which increases its market share in that segment. In turn, this makes it viable for companies to produce Linux versions of their applications, and for new products to come out just for the Linux market. This reasoning could be dismissed easily if Wine was only capable of running Solitaire. However now it can run Microsoft Office, multimedia applications such as QuickTime and Windows Media Player, and even games such as Max Payne or Unreal Tournament 3. Almost any other complex application can be made to run well given a bit of time. And each time that work is done to add one application to this list, many other applications benefit from this work and become usable too.

Have a look at our Application Database to get an idea on what can be run under Wine.

The use of Wine for gaming has proved specifically controversial in the Linux community, as some feel it is preventing, or at least hindering, the further growth of native gaming on the platform.[65][66]

Microsoft and Wine

Microsoft has generally not made public statements about Wine. However, the Microsoft Update software will block updates to Microsoft applications running in Wine. On 16 February 2005, Ivan Leo Puoti discovered that Microsoft had started checking the Windows registry for the Wine configuration key and would block the Windows Update for any component. Puoti wrote, "It's ... the first time they've broken radio silence on the project."[67]

The Windows Genuine Advantage (WGA) system also checks for existence of Wine registry keys. The WGA FAQ states that WGA will not run in Wine by design, as Wine does not constitute "genuine Windows".[68] When WGA validation detects Wine running on the system, it will notify users that they are running non-genuine Windows and disallow genuine Windows downloads for that system. Despite this, some reports have circulated of the WGA system working in Wine,[69][70] although this loophole has now been closed with the next WGA component update. In the case of Internet Explorer 7, Microsoft has since removed the WGA requirements.[71]

See also

References

  1. ^ "Winelib". Wine HQ. Retrieved 29 June 2008.
  2. ^ "Is Wine an emulator? There seems to be disagreement".
  3. ^ Mckenzie, James (26 December 2009). "Legal Issues". WineHQ Forums.
  4. ^ WINE FAQ Old meaning of the name even used until 1997
  5. ^ Wine Is Not an Emulator First proposal to change the meaning of the name WINE
  6. ^ "Why do some people write WINE and not Wine?". Wine Wiki FAQ. Official Wine Wiki. 7 July 2008. Retrieved 13 July 2008.
  7. ^ "2007 Desktop Linux Market survey". 21 August 2007. Retrieved 8 October 2007.
  8. ^ Vaughan-Nichols, Steven J. (22 August 2007). "Running Windows applications on Linux". 2007 Desktop Linux Survey results. DesktopLinux.
  9. ^ Amstadt, Bob (29 September 1993). "Wine project status". Newsgroup: comp.windows.x.i386unix. Retrieved 13 July 2008.
  10. ^ "Sun Uses ECMA as Path to ISO Java Standardization". Computergram International. 7 May 1999. Retrieved 13 July 2008.
  11. ^ Byron A Jeff (25 August 1993). "WABI available on linux or not". Newsgroup: comp.os.linux.misc. Retrieved 21 September 2007.
  12. ^ Loli-Queru, Eugenia (29 October 2001). "Interview with WINE's Alexandre Julliard". OSnews (Interview). Retrieved 30 June 2008. Usually we start from whatever documentation is available, implement a first version of the function, and then as we find problems with applications that call this function we fix the behavior until it is what the application expects, which is usually quite far from what the documentation states.
  13. ^ White, Jeremy (6 February 2002). "Wine license change". Retrieved 27 April 2010.
  14. ^ Alexandre Julliard (18 February 2002). "License change vote results". Retrieved 27 April 2010.
  15. ^ "Beta!". 25 October 2005. Retrieved 9 December 2010.
  16. ^ "Announcement of version 1.0". Wine HQ. 17 June 2008. Retrieved 1 September 2008.
  17. ^ Julliard, Alexandre (16 July 2010). "Release News".
  18. ^ a b "Wine Announcement". Retrieved 7 March 2012.
  19. ^ White, Jeremy (27 January 2011). "Announcing CrossOver 10.0 and CrossOver Games 10.0, The Impersonator". Codeweavers.com. Retrieved 28 January 2011.
  20. ^ Vaughan-Nichols, Steven J. (25 February 2002). "That's All Folks: Corel Leaves Open Source Behind". Linux.com. Retrieved 3 January 2009.
  21. ^ Kegel, Dan (14 February 2008). "Google's support for Wine in 2007". wine-devel (Mailing list). Retrieved 3 January 2009. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  22. ^ "Open Source Patches: Wine". Google. Retrieved 7 September 2008.
  23. ^ See the "Windows service" article
  24. ^ "Under what hardware platform(s) and operating system(s) will Wine(Lib) run?". Wine FAQ. Retrieved 3 January 2009.[dead link‍]
  25. ^ "OpenBSD Ports: emulators/wine". Openports.se. Retrieved 27 April 2010.
  26. ^ "The Wine development release 1.3.4 announcement". Winehq.org. Retrieved 15 October 2010.
  27. ^ "Wine Win32 Packages". Sourceforge.net. Retrieved 17 October 2010.
  28. ^ "The Official Wine Wiki: Wine on Windows". Wiki.winehq.org. Retrieved 27 April 2010.
  29. ^ "DirectX-Shaders". Official Wine Wiki. Retrieved 3 January 2009.
  30. ^ "Windows Legacy Application Support Under Wine" (PDF). Retrieved 9 December 2010.
  31. ^ Strohmeyer, Robert (6 April 2007). "Still need to run Windows apps? Have a glass of wine". Retrieved 9 December 2010.
  32. ^ Savill, John (11 February 2002). "Why can't I install 16-bit programs on a computer running the 64-bit version of Windows XP?". Retrieved 9 December 2010.
  33. ^ "Text mode programs (CUI: Console User Interface)". Wine User Guide. Retrieved 22 May 2010.
  34. ^ Lankhorst, Maarten (5 December 2008). "Wine64 hello world app runs!". wine-devel (Mailing list). Retrieved 15 December 2008. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  35. ^ "Wine64 for packagers". Official Wine Wiki. Retrieved 20 April 2010.
  36. ^ "Third Party Applications". Official Wine Wiki. Retrieved 3 January 2009.
  37. ^ "OpenIndiana Bordeaux announcement". OpenIndiana-announce mailing list. Retrieved 1 October 2010.
  38. ^ "Bordeaux group press release". Bordeaux group site. Retrieved 1 October 2010.
  39. ^ "winetricks". Official Wine Wiki. Retrieved 3 January 2009.
  40. ^ "Wine doors". Wine doors. Retrieved 27 April 2010.
  41. ^ "IEs4Linux". Tatanka.com.br. Retrieved 27 April 2010.
  42. ^ "Wineskin".
  43. ^ "ARM support". The Official Wine Wiki. Retrieved 20 August 2011.
  44. ^ [1]
  45. ^ [2]
  46. ^ Vincent, Brian (3 February 2004). "WineConf 2004 Summary". Wine Weekly News. No. 208. WineHQ.org. Retrieved 3 January 2009.
  47. ^ "Wine Status - DirectX DLLs". WineHQ.org. Retrieved 3 January 2009.
  48. ^ "CodeWeavers Releases CrossOver 6 for Mac and Linux". Slashdot. Retrieved 3 January 2009.
  49. ^ "CrossOver - Change Log - CodeWeavers". Retrieved 9 March 2012.
  50. ^ "Crossover Games site". Codeweavers.com. 6 January 1990. Retrieved 27 April 2010.
  51. ^ "GameTree Developer Program". gametreelinux.com. Retrieved 2 January 2011.
  52. ^ "WINE@Etersoft - Russian proprietary fork of Wine [[:Template:Ru icon]]". Pcweek.ru. 21 April 2010. Retrieved 27 April 2010. {{cite web}}: URL–wikilink conflict (help)
  53. ^ "Developer FAQ". ReactOS. Retrieved 25 May 2009.
  54. ^ "Creation of Arwinss branch". Mail-archive.com. 17 July 2009. Retrieved 27 April 2010.
  55. ^ "Arwinss at ReactOS wiki". Reactos.org. 20 February 2010. Retrieved 27 April 2010.
  56. ^ "Arwinss presentation". Reactos.org. Retrieved 27 April 2010.
  57. ^ "Wineskin FAQ". doh123. Retrieved 12 April 2011.
  58. ^ Matt Moen (26 January 2005). "Running Windows viruses with Wine". Retrieved 23 October 2009.
  59. ^ "Should I run Wine as root?". Wine Wiki FAQ. Official Wine Wiki. 7 August 2009. Retrieved 24 August 2009.
  60. ^ "ZeroWine project home page".
  61. ^ "Linux/BSD still exposed to WMF exploit through WINE!".
  62. ^ Michal Necasek. "OS/2 Warp history".
  63. ^ Bernhard Rosenkraenzer. "Debunking Wine Myths".
  64. ^ "Why Wine is so important". Retrieved 11 December 2011.
  65. ^ Ports vs. Wine Gamespot (Article by James Hills)
  66. ^ An Interview With A Linux Game Porter Phoronix, 3 July 2009 (Article by Michael Larabel)
  67. ^ Puoti, Ivan Leo (18 February 2005). "Microsoft genuine downloads looking for Wine". wine-devel (Mailing list). Archived from the original on 17 February 2005. Retrieved 23 January 2006. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  68. ^ "Genuine Windows FAQ". Microsoft Corporation. Retrieved 30 January 2006.
  69. ^ "Ubuntu Linux Validates as Genuine Windows". Slashdot. Retrieved 3 January 2009.
  70. ^ "WGA running in Wine". Retrieved 3 January 2009.
  71. ^ Foley, Mary-Jo (4 October 2007). "Internet Explorer 7 update: Now WGA-free". ZDNet. CBS Interactive. Retrieved 30 June 2011.

Further reading

Wikimedia Commons has media related to Wine (software).

Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Wine_(software)&oldid=497921914"