To view parent comment, click here.
To read all comments associated with this story, please click here.
That made me curious, so I had a look at the Wine FAQ:
"Part of the rationale for these projects is to find out areas where Wine portability is lacking. This is especially true of the ReactOS project which is a reimplementation of the Windows kernel and should thus be able to reuse most of Wine dlls.
Another reason for pursuing these projects is to be able to replace a single Windows dll with its Wine counterpart. Besides being a good test for the Wine dll, this lets us detect cases where we made incorrect assumptions about how the dlls interact."
So it's mainly for helping with Wine development, but there could be actual use cases as well.
With Wine you could install and try a program as a limited user, and without having to touch C:Program Files or the registry. You can even have multiple fake Windows installations. Wine incurs less overhead than a full virtual machine, and it doesn't require additional licenses.
And some programs might actually run faster on Wine, because Wine libraries might be implemented better than the originals.






Member since:
2005-10-06
While I'm not exactly sure why it seems there is a Windows version of Wine. It's currently at 0.9.8 but it's bound to be updated to 0.9.9
You can find it here:
http://sourceforge.net/project/showfiles.php?group_id=6241&package_...