Follow TV Tropes

Following

History UsefulNotes / WINE

Go To



There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows support to 64-bit versions of Windows. So far it has had success with productivity programs (like ''Atlus [=PageMaker=]'' and ''Creator/{{Broderbund}}'s Print Shop series''), simpler games like the Windows Entertainment Pack libraries of games, and even more advanced titles like VideoGame/FullTiltPinball[[note]]yes, you can have the digital equivalent of the reach-around- running a 16-bit build of a game that was bundled with 32-bit versions of Windows on 64-bit Windows[[/note]]. However more advanced titles like Myst[[note]]relies on add-ons like Quicktime 1.0 and probably [=WinG=][[/note]] will most likely still fail.

to:

There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows support to 64-bit versions of Windows. So far it has had success with productivity programs (like ''Atlus [=PageMaker=]'' and ''Creator/{{Broderbund}}'s Print Shop series''), simpler games like the Windows Entertainment Pack libraries of games, and even some more advanced titles like VideoGame/FullTiltPinball[[note]]yes, you can have the digital equivalent of the reach-around- running a 16-bit build of a game that was bundled with 32-bit versions of Windows on 64-bit Windows[[/note]]. However more advanced titles like Myst[[note]]relies on add-ons like Quicktime 1.0 and probably [=WinG=][[/note]] will most likely still fail.Windows[[/note]].


There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows support to 64-bit versions of Windows. So far it has had success with productivity programs (like ''Atlus [=PageMaker=]'' and ''Creator/{{Broderbund}}'s Print Shop series'') and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles, or VideoGame/{{Myst}}) still fall flat when tried.

to:

There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows support to 64-bit versions of Windows. So far it has had success with productivity programs (like ''Atlus [=PageMaker=]'' and ''Creator/{{Broderbund}}'s Print Shop series'') and series''), simpler games like the Windows Entertainment Pack libraries of games, but and even more advanced titles (for example, VideoGame/LivingBooks titles, or VideoGame/{{Myst}}) like VideoGame/FullTiltPinball[[note]]yes, you can have the digital equivalent of the reach-around- running a 16-bit build of a game that was bundled with 32-bit versions of Windows on 64-bit Windows[[/note]]. However more advanced titles like Myst[[note]]relies on add-ons like Quicktime 1.0 and probably [=WinG=][[/note]] will most likely still fall flat when tried.fail.


There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles, or VideoGame/{{Myst}}) still fall flat when tried.

to:

There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows support to 64-bit versions of Windows. So far it has had success with productivity programs (like ''Atlus [=PageMaker=]'' and ''Creator/{{Broderbund}}'s Print Shop series'') and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles, or VideoGame/{{Myst}}) still fall flat when tried.


There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles still fall flat when tried).

to:

There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles titles, or VideoGame/{{Myst}}) still fall flat when tried).tried.


There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows 3.1 support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles still fall flat when tried).

to:

There's also a derivative of Wine for ''Windows'' itself. ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows 3.1 support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles still fall flat when tried).


There's also a derivative of Wine for ''Windows'' itself. ''WineVDM'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows 3.1 support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles still fall flat when tried).

to:

There's also a derivative of Wine for ''Windows'' itself. ''WineVDM'' ''[=WineVDM=]'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows 3.1 support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGame/LivingBooks titles still fall flat when tried).


There's also a derivative of Wine for ''Windows'' itself. ''WineVDM'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows 3.1 support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGames/LivingBooks titles still fall flat when tried).

to:

There's also a derivative of Wine for ''Windows'' itself. ''WineVDM'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows 3.1 support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGames/LivingBooks VideoGame/LivingBooks titles still fall flat when tried).
tried).

Added DiffLines:

There's also a derivative of Wine for ''Windows'' itself. ''WineVDM'' (formerly OTVDM) was created with the intend of restoring 16-bit Windows 3.1 support to 64-bit versions of Windows. So far it has had success with productivity programs and simpler games like the Windows Entertainment Pack libraries of games, but more advanced titles (for example, VideoGames/LivingBooks titles still fall flat when tried).


Wine implements the Windows API and application binary interface (ABI) in userspace, i.e. the region where most applications run on a typical operating system on top of low-level code like the kernel. This is done for security reasons, no thanks to Windows being susceptible to malware, but it comes at a cost of not being able to run certain games or applications which rely on strong CopyProtection or anti-cheat middleware such as [=StarForce=], [=PunkBuster=] or [=GameGuard=]. Don't be surprised if the developers would deem a bug report as non-fixable, as they definitely wouldn't touch kernel-mode stuff with a ten-foot pole for the reasons mentioned above.

to:

Wine implements the Windows API and application binary interface (ABI) in userspace, i.e. the region where most applications run on a typical operating system on top of low-level code like the kernel. This is done for security reasons, no thanks to Windows being susceptible to malware, but it comes at a cost of not being able to run certain games or applications which rely on strong CopyProtection or anti-cheat middleware such as [=StarForce=], [=PunkBuster=] or [=GameGuard=]. Don't be surprised if the developers would deem a bug report as non-fixable, as they definitely wouldn't touch kernel-mode stuff stuff, or in the case of [=PunkBuster=], strict API checks,[[note]][=PunkBuster=] thoroughly screens the Windows API if it is "byte-for-byte equal to the Windows implementation", and fails if the API libraries have a different checksum from what the anti-cheat expects; since Wine is a libre implementation of the Windows API and as such are bound not to plagiarise from Microsoft code, adding support for it is next to impossible without resorting to less-than-legal means.[[/note]] with a ten-foot pole for the reasons mentioned above.


Creator/{{Valve}} has also come up with their own fork, named [[https://github.com/ValveSoftware/Proton Proton]] to allow Linux users to play Windows-exclusive titles via the UsefulNotes/Steam service (though it isn't restricted to Steam games), all without having to maintain a separate Windows partition or a virtual machine. Proton also includes libraries from other Open Source projects, such as DXVK, [=D9VK and VKD3D=], which are, respectively, [=DirectX=] 10/ 11, 9, and 12 translation layers that converts calls from those API's to Vulkan, which '''greatly''' improves the performance of games running under Proton. F-Audio is also included, which is a drop-in replacement for Microsoft's "X-audio" software.

One team even took Windows compatibility UpToEleven by developing a free software alternative to Windows called [=ReactOS=], which aims to be a drop-in replacement while still providing a familiar application and user experience to an average end-user without having to resort to any *nix-style OS. [=ReactOS=] shares much of its userspace code with Wine, [[AlreadyDoneForYou saving them the trouble]] of having to redo everything from scratch. However unlike Wine, which is more or less feature-complete despite being in PerpetualBeta, [=ReactOS=] is still too unstable for daily use, either lacking crucial functionality or hanging up in certain scenarios. This is due to [=ReactOS=]' goal being more than just running Windows apps, but to become a complete drop-in solution for Windows XP/Server 2003 R2, including supporting all Windows' drivers, and having a fully custom kernel that is compatible with Windows system calls instead of just using the Linux kernel with a translation layer[[note]]The project has also been hit by [[MovingTheGoalposts perpetually moving goalposts - at this point, the developers have agreed to lock on to getting Windows XP/2003 support stable first before starting with Windows 7 support- only to be pushed by the financial backers to add Windows 7 support anyway due to Microsoft dropping support for Windows 7, and obliging]], as well as all sorts of delays and setbacks[[/note]]. Additionally, certain Wine userspace libraries are not used by [=ReactOS=] either due to licensing, or due to incompatibilities with the way the other parts of [=ReactOS=] are implemented.[[note]]There is however an experimental branch called Arwinss which use slightly-modified versions of Wine's [=GDI32=] and [=USER32=] libraries in order to take better advantage of Wine's existing software compatibility.[[/note]] Unlike the developers of Wine, [=ReactOS=] developers considers low-level kernel issues a must-fix.

to:

Creator/{{Valve}} has also come up with their its own fork, named [[https://github.com/ValveSoftware/Proton Proton]] to allow Linux users to play Windows-exclusive titles via the UsefulNotes/Steam UsefulNotes/{{Steam}} service (though it isn't restricted to Steam games), all without having to maintain a separate Windows partition or a virtual machine. Proton also includes libraries from other Open Source projects, such as DXVK, [=D9VK and VKD3D=], which are, respectively, [=DirectX=] 10/ 11, 9, and 12 translation layers that converts convert calls from those API's [=APIs=] to Vulkan, which '''greatly''' improves the performance of games running under Proton. F-Audio is also included, which is a drop-in replacement for Microsoft's "X-audio" software.

One team even took Windows compatibility UpToEleven by developing a free software alternative to Windows called [=ReactOS=], which aims to be a drop-in replacement while still providing a familiar application and user experience to an average end-user end user without having to resort to any *nix-style OS. [=ReactOS=] shares much of its userspace code with Wine, [[AlreadyDoneForYou saving them the trouble]] of having to redo everything from scratch. However unlike Wine, which is more or less feature-complete despite being in PerpetualBeta, [=ReactOS=] is still too unstable for daily use, either lacking crucial functionality or hanging up in certain scenarios. This is due to [=ReactOS=]' goal being more than just running Windows apps, but to become a complete drop-in solution for Windows XP/Server 2003 R2, including supporting all Windows' Windows drivers, and having a fully custom kernel that is compatible with Windows system calls instead of just using the Linux kernel with a translation layer[[note]]The project has also been hit by [[MovingTheGoalposts perpetually moving goalposts - at this point, the developers have agreed to lock on to getting Windows XP/2003 support stable first before starting with Windows 7 support- only to be support - but they were pushed by the financial backers to add Windows 7 support anyway due to Microsoft dropping support for Windows 7, and obliging]], as well as all sorts of delays and setbacks[[/note]]. Additionally, certain Wine userspace libraries are not used by [=ReactOS=] either due to licensing, or due to incompatibilities with the way the other parts of [=ReactOS=] are implemented.[[note]]There is however an experimental branch called Arwinss which use slightly-modified versions of Wine's [=GDI32=] and [=USER32=] libraries in order to take better advantage of Wine's existing software compatibility.[[/note]] Unlike the developers of Wine, [=ReactOS=] developers considers low-level kernel issues a must-fix.


Creator/{{Valve}} has also come up with their own fork, named [[https://github.com/ValveSoftware/Proton Proton]] to allow Linux users to play Windows-exclusive titles via the UsefulNotes/Steam service (though it isn't restricted to Steam games), all without having to maintain a separate Windows partition or a virtual machine. Proton also includes libraries from other Open Source projects, such as DXVK, D9VK and VKD3D, which are, respectively, [=DirectX=] 10/ 11, 9, and 12 translation layers that converts calls from those API's to Vulkan, which '''greatly''' improves the performance of games running under Proton. F-Audio is also included, which is a drop-in replacement for Microsoft's "X-audio" software.

to:

Creator/{{Valve}} has also come up with their own fork, named [[https://github.com/ValveSoftware/Proton Proton]] to allow Linux users to play Windows-exclusive titles via the UsefulNotes/Steam service (though it isn't restricted to Steam games), all without having to maintain a separate Windows partition or a virtual machine. Proton also includes libraries from other Open Source projects, such as DXVK, D9VK [=D9VK and VKD3D, VKD3D=], which are, respectively, [=DirectX=] 10/ 11, 9, and 12 translation layers that converts calls from those API's to Vulkan, which '''greatly''' improves the performance of games running under Proton. F-Audio is also included, which is a drop-in replacement for Microsoft's "X-audio" software.



Unfortunately, Wine can be a headache to set up for a program, and even more so if said program requires additional libraries or other fixes in order to work. Because of this, many frontends have been developed to automate these tasks, being primarily focused on gaming. One of the original popular frontends was PlayOnLinux, which handled running executables and installing extra dependencies. However, due to development stalling, PlayOnLinux quickly fell out of popularity. Another frontend used today, even with other frontends, is Winetricks, which helps install other libraries. As of 2019, the most popular frontend is Lutris, which relies on community scripts to automatically install games with the proper Wine versions, libraries, and other fixes. Additionally, Cedega and [=CrossOver=] come with their own proprietary frontend.

to:

Unfortunately, Wine can be a headache to set up for a program, and even more so if said program requires additional libraries or other fixes in order to work. Because of this, many frontends have been developed to automate these tasks, being primarily focused on gaming. One of the original popular frontends was PlayOnLinux, [=PlayOnLinux=], which handled running executables and installing extra dependencies. However, due to development stalling, PlayOnLinux [=PlayOnLinux=] quickly fell out of popularity. Another frontend used today, even with other frontends, is Winetricks, which helps install other libraries. As of 2019, the most popular frontend is Lutris, which relies on community scripts to automatically install games with the proper Wine versions, libraries, and other fixes. Additionally, Cedega and [=CrossOver=] come with their own proprietary frontend.


Owing to its open-source nature, Wine, or parts of it, has been used as the basis for numerous forks, such as Cider, a proprietary library/wrapper for developers to adapt existing Windows games to [[UsefulNotes/MacOS OS X]] with next to no changes in source code (as a matter of fact, this has been [[NotTheIntendedUse used]] by intrepid hackers to "port" various games and/or applications to Apple's operating system, simply by copying the game's installation folder to the Cider .app directory and tweak the configuration files if necessary), and [=CrossOver=], a premium version of Wine developed by the same team behind the project. Aside from Crossover, there used to be another paid version of Wine called [=WineX=] (later rechristened to Cedega, and lastly as Game Tree Linux before being laid to rest) from [=TransGaming=], the company who also developed Cider. The company eventually discontinued the product to focus on Cider. There is also a free Cider-like framework called Wineskin, allowing end-users and developers alike to do Windows-to-OS X conversions of software, without the legal issues associated with taking an existing Cider wrapper. Creator/{{Valve}} has also come up with their own fork, named [[https://github.com/ValveSoftware/Proton Proton]] to allow Linux users to play Windows-exclusive titles without having to maintain a separate Windows partition or virtual machine. Proton also includes libraries from other Open Source projects, such as DXVK, a [=DirectX=] 10,11 and 12 translation layer that converts calls form those API's to Vulkan, which greatly improves the performance of games running under Proton.

to:

Owing to its open-source nature, Wine, or parts of it, has been used as the basis for numerous forks, such as Cider, a proprietary library/wrapper for developers to adapt existing Windows games to [[UsefulNotes/MacOS OS X]] with next to no changes in source code (as a matter of fact, this has been [[NotTheIntendedUse used]] by intrepid hackers to "port" various games and/or applications to Apple's operating system, simply by copying the game's installation folder to the Cider .app directory and tweak the configuration files if necessary), and [=CrossOver=], a premium version of Wine developed by the same team behind the project. Aside from Crossover, there used to be another paid version of Wine called [=WineX=] (later rechristened to Cedega, and lastly as Game Tree Linux before being laid to rest) from [=TransGaming=], the company who also developed Cider. The company eventually discontinued the product to focus on Cider. There is also a free Cider-like framework called Wineskin, allowing end-users and developers alike to do Windows-to-OS X conversions of software, without the legal issues associated with taking an existing Cider wrapper.

Creator/{{Valve}} has also come up with their own fork, named [[https://github.com/ValveSoftware/Proton Proton]] to allow Linux users to play Windows-exclusive titles via the UsefulNotes/Steam service (though it isn't restricted to Steam games), all without having to maintain a separate Windows partition or a virtual machine. Proton also includes libraries from other Open Source projects, such as DXVK, a D9VK and VKD3D, which are, respectively, [=DirectX=] 10,11 10/ 11, 9, and 12 translation layer layers that converts calls form from those API's to Vulkan, which greatly '''greatly''' improves the performance of games running under Proton.
Proton. F-Audio is also included, which is a drop-in replacement for Microsoft's "X-audio" software.


Due to the complexity of setting up Wine to prepare it to run just one game, several frontends have been created to automate the task. The most popular of them is as of 2019 ''Lutris'', which despite itís name is not a Tetris clone. Previously [=PlayOnLinux=] was popular, but fell out of use when development stalled. Alternatives include Vineyard, and the oldest of the frontends, Winetricks. Additionally, Cedega and [=CrossOver=] comes with their own proprietary frontend.

to:

Due to the complexity of setting up Unfortunately, Wine can be a headache to prepare it set up for a program, and even more so if said program requires additional libraries or other fixes in order to run just one game, several work. Because of this, many frontends have been created developed to automate these tasks, being primarily focused on gaming. One of the task. The original popular frontends was PlayOnLinux, which handled running executables and installing extra dependencies. However, due to development stalling, PlayOnLinux quickly fell out of popularity. Another frontend used today, even with other frontends, is Winetricks, which helps install other libraries. As of 2019, the most popular of them frontend is as of 2019 ''Lutris'', Lutris, which despite itís name is not a Tetris clone. Previously [=PlayOnLinux=] was popular, but fell out of use when development stalled. Alternatives include Vineyard, relies on community scripts to automatically install games with the proper Wine versions, libraries, and the oldest of the frontends, Winetricks. other fixes. Additionally, Cedega and [=CrossOver=] comes come with their own proprietary frontend.


One team even took Windows compatibility UpToEleven by developing a free software alternative to Windows called [=ReactOS=], which aims to be a drop-in replacement while still providing a familiar application and user experience to an average end-user without having to resort to any *nix-style OS. [=ReactOS=] shares much of its userspace code with Wine, [[AlreadyDoneForYou saving them the trouble]] of having to redo everything from scratch. However unlike Wine, which is more or less feature-complete despite being in PerpetualBeta, [=ReactOS=] is still too unstable for daily use, either lacking crucial functionality or hanging up in certain scenarios. This is due to [=ReactOS=]' goal being more than just running Windows apps, but to become a complete drop-in solution for Windows XP/Server 2003 R2, including supporting all Windows' drivers, and having a fully custom kernel that is compatible with Windows system calls instead of just using the Linux kernel with a translation layer[[note]]The project has also been hit by [[MovingTheGoalposts perpetually moving goalposts - at this point, the developers have agreed to lock on to getting Windows XP/2003 support stable first before starting with Windows 7 support]], as well as all sorts of delays and setbacks[[/note]]. Additionally, certain Wine userspace libraries are not used by [=ReactOS=] either due to licensing, or due to incompatibilities with the way the other parts of [=ReactOS=] are implemented.[[note]]There is however an experimental branch called Arwinss which use slightly-modified versions of Wine's [=GDI32=] and [=USER32=] libraries in order to take better advantage of Wine's existing software compatibility.[[/note]] Unlike the developers of Wine, [=ReactOS=] developers considers low-level kernel issues a must-fix.

to:

One team even took Windows compatibility UpToEleven by developing a free software alternative to Windows called [=ReactOS=], which aims to be a drop-in replacement while still providing a familiar application and user experience to an average end-user without having to resort to any *nix-style OS. [=ReactOS=] shares much of its userspace code with Wine, [[AlreadyDoneForYou saving them the trouble]] of having to redo everything from scratch. However unlike Wine, which is more or less feature-complete despite being in PerpetualBeta, [=ReactOS=] is still too unstable for daily use, either lacking crucial functionality or hanging up in certain scenarios. This is due to [=ReactOS=]' goal being more than just running Windows apps, but to become a complete drop-in solution for Windows XP/Server 2003 R2, including supporting all Windows' drivers, and having a fully custom kernel that is compatible with Windows system calls instead of just using the Linux kernel with a translation layer[[note]]The project has also been hit by [[MovingTheGoalposts perpetually moving goalposts - at this point, the developers have agreed to lock on to getting Windows XP/2003 support stable first before starting with Windows 7 support]], support- only to be pushed by the financial backers to add Windows 7 support anyway due to Microsoft dropping support for Windows 7, and obliging]], as well as all sorts of delays and setbacks[[/note]]. Additionally, certain Wine userspace libraries are not used by [=ReactOS=] either due to licensing, or due to incompatibilities with the way the other parts of [=ReactOS=] are implemented.[[note]]There is however an experimental branch called Arwinss which use slightly-modified versions of Wine's [=GDI32=] and [=USER32=] libraries in order to take better advantage of Wine's existing software compatibility.[[/note]] Unlike the developers of Wine, [=ReactOS=] developers considers low-level kernel issues a must-fix.


Due to the complexity of setting up Wine to prepare it to run just one game, several frontends have been created to automate the task. The most popular of them is as of 2019 ĎíLutrisíí, which despite itís name is not a Tetris clone. Previously [=PlayOnLinux=] was popular, but fell out of use when development stalled. Alternatives include Vineyard, and the oldest of the frontends, Winetricks. Additionally, Cedega and [=CrossOver=] comes with their own proprietary frontend.

to:

Due to the complexity of setting up Wine to prepare it to run just one game, several frontends have been created to automate the task. The most popular of them is as of 2019 ĎíLutrisíí, ''Lutris'', which despite itís name is not a Tetris clone. Previously [=PlayOnLinux=] was popular, but fell out of use when development stalled. Alternatives include Vineyard, and the oldest of the frontends, Winetricks. Additionally, Cedega and [=CrossOver=] comes with their own proprietary frontend.

Showing 15 edit(s) of 36

Top

How well does it match the trope?

Example of:

/

Media sources:

/

Report