Microsoft is known for its outstanding backward compatibility. Will Wine take over that role?
Wine on Windows 10
21–30 of 135 posts
Re: Wine on Windows 10
#22The funniest thing would be Microsoft hiring Wine developers to make programs written for old Windows run on newer versions of it.
Re: Wine on Windows 10
#23Earlier quoted context omitted.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
Why? There's only one hypervisor involved for the initial "wine" environment.
Neither WINE nor WSLv1 use virtualisation. WSLv2 does use virtualisation however; but WINE still isn't a VM.
Re: Wine on Windows 10
#24Hilarious. Props to author for not trying to give a reasonable looking motivation for this beyond "It would be funny". That's more than enough.
Physics is like sex: sure, it may give some practical
results, but that's not why we do it.
Re: Wine on Windows 10
#25This can be very helpful in the future for playing games with strange 16-bit-mixed-with-32-bit installers that fail to run properly on modern Windows, even 32-bit versions. I hope WSL2 comes out soon. Now that installing wine in Linux on windows is possible, the next step becomes clear. We must compile and run cygwin on wine in Linux on Windows.
You can already do that with OTVDM: https://github.com/otya128/winevdm
Using it not only any 16bit installer works, but also most 16bit applications. As an example you can play Exile by Spiderweb[2] on your Windows 64 PC.
It even contains a .reg file that allows it to be installed system-wide so that you can run a 16bit .exe just by double clicking it in Explorer (or any other file manager).
Re: Wine on Windows 10
#26Earlier quoted context omitted.
This project is only completed when you can recursively keep doing this forever, without it ever breaking.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
WSL1 is not a "real" VM.
https://blogs.msdn.microsoft.com/wsl/2016/05/23/pico-process...
Re: Wine on Windows 10
#27The funniest thing would be Microsoft hiring Wine developers to make programs written for old Windows run on newer versions of it.
No, the funniest thing would Microsoft making Windows 11 a Linux distro with a custom version of WINE running ontop of it so that they need to maintain way fewer parts of their operating system themselves.
Re: Wine on Windows 10
#28Correct me if I'm wrong, but this is running Wine on Linux on Windows. Not running Wine on Windows.
Re: Wine on Windows 10
#29Earlier quoted context omitted.
WSL is VM. So it's pretty pointless to run application on Linux VM emulating WinAPI, indeed. But at least you don't need to care about licenses, that might be one reason.
WSL is not a VM. The upcoming WSL2 might be, though.
I'm pretty sure WSL2 is going to use a user mode kernel
Re: Wine on Windows 10
#30This can be very helpful in the future for playing games with strange 16-bit-mixed-with-32-bit installers that fail to run properly on modern Windows, even 32-bit versions. I hope WSL2 comes out soon. Now that installing wine in Linux on windows is possible, the next step becomes clear. We must compile and run cygwin on wine in Linux on Windows.
You can already do that with OTVDM: https://github.com/otya128/winevdm Using it not only any 16bit installer works, but also most 16bit applications. As an example you can play Exile by Spiderweb[2] on your Windows 64 PC. It even contains a .reg file that allows it to be installed system-wide so that you can run a 16bit .exe just by double clicking it in Explorer (or any other file manager). [1] https://github.com/ot…
Looking at the install.inf file, I saw that they first remove a key from the registry with the name VDM in it. So I wondered what VDM means.
> Virtual DOS machines (VDM) refer to a technology that allows running 16-bit/32-bit DOS and 16-bit Windows programs when there is already another operating system running and controlling the hardware.
https://en.wikipedia.org/wiki/Virtual_DOS_machine
So how come otvdm is needed I wondered.
Same Wikipedia article explains it.
> NTVDM is a system component of all IA-32 editions of the Windows NT family since 1993 which allows execution of 16-bit Windows and 16-bit / 32-bit DOS applications. It is not included with 64-bit versions. The Windows NT 32-bit user-mode executable which forms the basis for a single DOS (or Windows 3.x) environment is called ntvdm.exe.
But why did Microsoft not include VDM in 64-bit systems? I thought MS was all about that backwards compatibility.