Editing Wine (software) (section)

==Functionality==
[[File:History Of WineAppDB.gif|thumb|300px|App compatibility progress over time, according to Wine AppDB test results.<br />
{{Legend|#ececec|Software works flawlessly}}
{{Legend|#fff600|Software works flawlessly after configuration}}
{{Legend|#c0c0c0|Minor problems with the software}}
{{Legend|#fcba0a|Major problems with the software}}
{{Legend|#999966|Completely non-functional software}}]]
[[File:WineHQ ratings.svg|thumb|300px|WineHQ application ratings over the time.]]
The developers of the [[Direct3D]] portions of Wine have continued to implement new features such as [[pixel shaders]] to increase game support.<ref>{{cite web
 | url          = https://wiki.winehq.org/DirectX-Shaders
 | title        = DirectX-Shaders
 | publisher    = Official Wine Wiki
 | access-date   = 3 January 2009
 | archive-url  = https://web.archive.org/web/20090101022401/http://wiki.winehq.org/DirectX-Shaders
 | archive-date = 1 January 2009
 | url-status   = dead}}</ref> 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.

Wine also includes its own open-source implementations of several Windows programs, such as ''[[Microsoft Notepad|Notepad]]'', ''[[WordPad]]'', ''[[Control Panel (Windows)|Control Panel]]'', ''[[Internet Explorer]]'', and ''[[Windows Explorer]]''.<ref name=list_of_commands>{{cite web |url=https://wiki.winehq.org/List_of_Commands |title=List of Commands |date=12 April 2016 |website=WineHQ |access-date=29 April 2017 |archive-date=17 March 2016 |archive-url=https://web.archive.org/web/20160317010958/https://wiki.winehq.org/List_of_Commands |url-status=live }}</ref>

The Wine Application Database (AppDB) is a community-maintained on-line database about which Windows programs works with Wine and how well they work.

===Backward compatibility===
Wine ensures good [[backward compatibility]] with legacy Windows applications, including those written for [[Windows 3.1x]].<ref name="winelegacy">{{cite web
 | url        = http://media.codeweavers.com/pub/crossover/case_studies/WinLegacySupport.pdf
 | title        = Windows Legacy Application Support Under Wine
 | access-date        = 9 December 2010
 | archive-date        = 8 July 2011
 | archive-url        = https://web.archive.org/web/20110708174152/http://media.codeweavers.com/pub/crossover/case_studies/WinLegacySupport.pdf
 | url-status        = live
 }}</ref> Wine can mimic different Windows versions required for some programs, going as far back as [[Windows 2.0]].<ref name="Wine Windows 2.0">{{cite news
 |url          = http://www.maximumpc.com/article/still_need_to_run_windows_apps_have_a_glass_of_wine
 |title        = Still need to run Windows apps? Have a glass of wine
 |first        = Robert
 |last         = Strohmeyer
 |newspaper    = Pcgamer
 |date         = 6 April 2007
 |access-date  = 9 December 2010
 |archive-date = 22 June 2011
 |archive-url  = https://web.archive.org/web/20110622002156/http://www.maximumpc.com/article/still_need_to_run_windows_apps_have_a_glass_of_wine
 |url-status   = live
}}</ref> However, [[Windows 1.0x|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|date=April 2012}} (see below on [[#MS-DOS|MS-DOS]]), Wine development version 1.3.12 and later nevertheless show the "Windows 2.0" option for the Windows version to mimic, but Wine still will not run most Windows 2.0 programs because MS-DOS and Windows functions are not currently integrated.

Backward compatibility in Wine is generally superior to that of Windows, as newer versions of Windows can force users to upgrade legacy Windows applications, and may break unsupported software forever as there is nobody adjusting the program for the changes in the operating system. In many cases, Wine can offer better legacy support than newer versions of Windows with "Compatibility Mode". Wine can run [[16-bit computing|16-bit]] Windows programs ([[Windows API#Win16|Win16]]) on a 64-bit operating system, which uses an [[x86-64]] (64-bit) CPU,<ref>{{Cite web|url=https://www.groovypost.com/howto/enable-16-bit-application-support-windows-10/|title=How to Enable 16-bit Application Support in Windows 10|last=Andre Da Costa|date=20 April 2016|website=groovyPost|language=en-US|access-date=9 April 2019|archive-date=20 February 2023|archive-url=https://web.archive.org/web/20230220142716/https://www.groovypost.com/howto/enable-16-bit-application-support-windows-10/|url-status=live}}</ref> a functionality not found in 64-bit versions of Microsoft Windows.<ref>{{cite web
 | url        = https://support.microsoft.com/en-us/kb/896458
 | title        = 64-bit versions of Windows do not support 16-bit components, 16-bit processes, or 16-bit applications
 | access-date        = 22 August 2015
 | archive-date        = 26 May 2016
 | archive-url        = https://web.archive.org/web/20160526135209/https://support.microsoft.com/en-us/kb/896458
 | url-status        = live
 }}</ref><ref>{{cite web
 | url      = http://windowsitpro.com/systems-management/why-cant-i-install-16-bit-programs-computer-running-64-bit-version-windows-xp
 | title      = Why can't I install 16-bit programs on a computer running the 64-bit version of Windows XP?
 | first      = John
 | last      = Savill
 | date      = 11 February 2002
 | access-date      = 9 December 2010
 | archive-date      = 4 March 2016
 | archive-url      = https://web.archive.org/web/20160304083829/http://windowsitpro.com/systems-management/why-cant-i-install-16-bit-programs-computer-running-64-bit-version-windows-xp
 | url-status      = live
 }}</ref> [[WineVDM]] allows 16-bit Windows applications to run on 64-bit versions of Windows.<ref>{{cite web| url = https://github.com/otya128/winevdm| title = 16-bit Windows (Windows 1.x, 2.x, 3.0, 3.1, etc.) on 64-bit Windows.| website = [[GitHub]]| date = 27 October 2021| access-date = 25 September 2019| archive-date = 9 November 2020| archive-url = https://web.archive.org/web/20201109015029/https://github.com/otya128/winevdm| url-status = live}} On GitHub.</ref>

Wine partially supports Windows [[console application]]s, and the user can choose which backend to use to manage the console (choices include raw streams, [[curses (programming library)|curses]], and [[Windows USER|user32]]).<ref>{{cite web | url = https://wiki.winehq.org/Wine_User%27s_Guide#Text_mode_programs_.28CUI:_Console_User_Interface.29 | title = Text mode programs (CUI: Console User Interface) | work = Wine User's Guide | access-date = 9 February 2023 | archive-date = 14 February 2023 | archive-url = https://web.archive.org/web/20230214014239/https://wiki.winehq.org/Wine_User%27s_Guide#Text_mode_programs_.28CUI:_Console_User_Interface.29 | url-status = live }}</ref> When using the raw streams or curses backends, Windows applications will run in a Unix terminal.

===64-bit applications===
Preliminary support for [[64-bit computing|64-bit]] Windows applications was added to Wine 1.1.10, in December 2008.<ref>{{cite mailing list
 |first        = Maarten
 |last         = Lankhorst
 |url          = https://winehq.org/pipermail/wine-devel/2008-December/070941.html
 |title        = Wine64 hello world app runs!
 |date         = 5 December 2008
 |mailing-list = wine-devel
 |access-date  = 15 December 2008
 |archive-date = 21 March 2022
 |archive-url  = https://web.archive.org/web/20220321202532/https://www.winehq.org/pipermail/wine-devel/2008-December/070941.html
 |url-status   = live
}}</ref> {{As of|2019|04}}, the support is considered stable. The two versions of Wine are built separately, and as a result only building wine64 produces an environment only capable of running x86-64 applications.<ref name="Build">{{cite web |title=Building Wine |url=https://wiki.winehq.org/Building_Wine |website=WineHQ |access-date=23 April 2019 |archive-date=27 July 2022 |archive-url=https://web.archive.org/web/20220727202220/https://wiki.winehq.org/Building_Wine |url-status=live }}</ref>

{{As of|2019|04}}, Wine has stable support for a [[WoW64]] build, which allows both 32-bit and 64-bit Windows applications to run inside the same Wine instance. To perform such a build, one must first build the 64-bit version, and then build the 32-bit version referencing the 64-bit version. Just like Microsoft's WoW64, the 32-bit build process will add parts necessary for handling 32-bit programs to the 64-bit build.<ref name="Build"/> This functionality is seen from at least 2010.<ref>{{cite web
 | url          = https://wiki.winehq.org/Wine64ForPackagers
 | title        = Wine64 for packagers
 | publisher    = Official Wine Wiki
 | access-date   = 20 April 2010
 | archive-url  = https://web.archive.org/web/20100425050000/http://wiki.winehq.org/Wine64ForPackagers
 | archive-date = 25 April 2010
 | url-status   = dead}}</ref>

===MS-DOS===
Early versions of Microsoft Windows run on top of [[MS-DOS]], and Windows programs may depend on MS-DOS programs to be usable. 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.<ref>{{cite web |url=https://winehq.org/pipermail/wine-users/2011-March/087629.html |title=[Wine&#93; Re: Wine sometime really surprise me |date=11 March 2011 |access-date=15 February 2013 |archive-date=24 March 2012 |archive-url=https://web.archive.org/web/20120324150458/http://www.winehq.org/pipermail/wine-users/2011-March/087629.html |url-status=live }}</ref> However, due to a bug, current versions{{Update inline|reason=This is sourced to a bug report from 2013, which versions exhibited this bug and has it been fixed?|date=April 2021}} 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).<ref>{{cite web |url=https://bugs.winehq.org/show_bug.cgi?id=26715 |title=WineHQ Bugzilla – Bug 26715 – Win1.0 executable triggers Dosbox |access-date=15 February 2013 |archive-date=4 September 2015 |archive-url=https://web.archive.org/web/20150904034613/https://bugs.winehq.org/show_bug.cgi?id=26715 |url-status=live }}</ref>

===Winelib===
Wine provides Winelib, which allows its shared-object implementations of the Windows API to be used as actual libraries for a Unix program. This allows for Windows code to be built into native Unix executables. Since October 2010, Winelib also works on the [[ARM architecture|ARM]] platform.<ref>{{cite web
 | url        = https://winehq.org/announce/1.3.4
 | title        = The Wine development release 1.3.4 announcement
 | publisher        = Winehq.org
 | access-date        = 15 October 2010
 | archive-date        = 4 October 2010
 | archive-url        = https://web.archive.org/web/20101004023254/http://www.winehq.org/announce/1.3.4
 | url-status        = live
 }}</ref>

===Non-x86 architectures===
Support for Solaris [[SPARC]] was dropped in version 1.5.26.

====ARM, Windows CE, and Windows RT====
Wine provides some support for [[ARM architecture|ARM]] (as well as ARM64/AArch64) processors and the Windows flavors that run on it. {{As of|2019|04}}, Wine can run ARM/Win32 applications intended for unlocked [[Windows RT]] devices (but not Windows RT programs). [[Windows CE]] support (either x86 or ARM) is missing,<ref>{{cite web
 | url        = https://wiki.winehq.org/ARM
 | title        = ARM support
 | publisher        = The Official Wine Wiki
 | access-date        = 22 April 2019
 | archive-date        = 17 April 2019
 | archive-url        = https://web.archive.org/web/20190417084608/https://wiki.winehq.org/ARM
 | url-status        = live
 }}</ref> but an unofficial, [[Software release life cycle|pre-alpha]] proof-of-concept version called WineCE allows for some support.<ref>{{Cite web|url=http://dawncrow.de/wine/winece.html|title=Wine wrappers and more|access-date=6 July 2016|archive-date=29 June 2016|archive-url=https://web.archive.org/web/20160629205920/http://dawncrow.de/wine/winece.html|url-status=live}}</ref>

====Wine for Android====
[[File:Wine-solitaire-on-android.jpg|thumb|right|WINE [[Klondike (solitaire)|Solitaire]] running on Android]]

On 3 February 2013 at the FOSDEM talk in Brussels, [[Alexandre Julliard]] demonstrated an early demo of Wine running on Google's [[Android (operating system)|Android]] operating system.<ref>{{cite web |url=http://phoronix.com/scan.php?page=news_item&px=MTI5MjA |title=Wine on Android Is Coming For Running Windows Apps |website=Phoronix |date=3 February 2013 |access-date=30 August 2013 |archive-date=28 August 2013 |archive-url=https://web.archive.org/web/20130828055759/http://www.phoronix.com/scan.php?page=news_item&px=MTI5MjA |url-status=live }}</ref>

Experimental builds of WINE for Android (x86 and ARM) were released in late 2017. It has been routinely updated by the official developers ever since.<ref name="dl.winehq.org" /> The default builds do not implement cross-architecture emulation via [[QEMU]], and as a result ARM versions will only run ARM applications that use the Win32 API.<ref>{{cite web |title=Android |url=https://wiki.winehq.org/Android |website=WineHQ |access-date=23 April 2019 |archive-date=23 April 2019 |archive-url=https://web.archive.org/web/20190423175854/https://wiki.winehq.org/Android |url-status=live }}</ref>

===Microsoft applications===
Wine, by default, uses specialized Windows builds of [[Gecko (software)|Gecko]] and [[Mono (software)|Mono]] to substitute for Microsoft's [[Internet Explorer]] and [[.NET Framework]]. Wine has built-in implementations of [[JScript]] and [[VBScript]]. It is possible to download and run Microsoft's installers for those programs through winetricks or manually.

Wine is not known to have good support for most versions of Internet Explorer (IE). Of all the reasonably recent versions, Internet Explorer 8 for Windows XP is the only version that reports a usable rating on Wine's AppDB, out-of-the-box.<ref>{{cite web |title=Internet Explorer |url=https://appdb.winehq.org/objectManager.php?sClass=application&iId=25 |website=WineHQ AppDB |access-date=23 April 2019 |archive-date=13 April 2019 |archive-url=https://web.archive.org/web/20190413195444/https://appdb.winehq.org/objectManager.php?sClass=application&iId=25 |url-status=live }}</ref> However [[Google Chrome]] gets a gold rating (as of Wine 5.5-staging),<ref>{{cite web |title=Google Chrome |url=https://appdb.winehq.org/objectManager.php?sClass=application&iId=8177 |website=WineHQ AppDB |access-date=9 September 2020 |archive-date=13 September 2020 |archive-url=https://web.archive.org/web/20200913172130/https://appdb.winehq.org/objectManager.php?sClass=application&iId=8177 |url-status=live }}</ref> and Microsoft's IE replacement web browser Edge, is known to be based on that browser (after switching from Microsoft's own rendering engine<ref>{{Cite web|title=Chromium browsers are black - WineHQ Forums|url=https://forum.winehq.org/viewtopic.php?t=33455&p=126413|access-date=9 September 2020|website=forum.winehq.org|archive-date=15 June 2022|archive-url=https://web.archive.org/web/20220615171028/https://forum.winehq.org/viewtopic.php?t=33455&p=126413|url-status=live}}</ref><!-- with "winetricks -q dxvk vd=1280x1024" I see response "I got it working, thank you!", unclear if applies to Edge or only Chrome, as question was "When I tried to install Microsoft Edge on Chromium, it was completly back. I also tried Google Chrome"   https://appdb.winehq.org/objectManager.php?sClass=application&iId=19516 -->). Winetricks offer auto-installation for Internet Explorer 6 through 8, so these versions can be reasonably expected to work with its built-in workarounds.

An alternative for installing Internet Explorer directly is to use the now-defunct [[IEs4Linux]]. It is not compatible with the latest versions of Wine,<ref>{{cite web |url=https://lists.ubuntu.com/archives/ubuntu-users/2012-June/261480.html |title=So far, I do not manage to install IES4Linux |date=22 June 2012 |access-date=15 January 2014 |archive-date=15 August 2014 |archive-url=https://web.archive.org/web/20140815155020/https://lists.ubuntu.com/archives/ubuntu-users/2012-June/261480.html |url-status=live }}</ref> and the development of IEs4Linux is inactive.