So, like any good geek solution, it doesn't actually solve the user's original problem at all.
Brilliant!
Wine on Windows 10
31–40 of 135 posts
Re: Wine on Windows 10
#32Earlier quoted context omitted.
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…
MS is already running a similar system to translate 32-bit applications to 64-bit mode (WOW64). Keeping compatibility with 16-bit would have big consequences for the NTVDM. The alternative would be to run NTVDM on top of WOW64 but such a system would be a recipe for disaster.
I don't think the compatibility with 16-bit systems is worth the headache/expense. As long as 32-bit Windows exists, you can still run the few relevant and compatible DOS applications so I doubt anyone is missing much aside from a few nostalgic gamers.
Re: Wine on Windows 10
#33Earlier quoted context omitted.
WSL is not a VM. The upcoming WSL2 might be, though.
I'm pretty sure WSL2 is going to use a user mode kernel
IIRC the NT kernel can run multiple kernels-or-something side by side. It could probably be used to co-run Linux kind of like CoLinux does.
IIRC also, MS can use the Windows HyperV infrastructure to run the Linux kernel too, like they do on Xbox One to segregate games "Exclusive" OS from apps "Shared" OS. In that sense it won't be user mode either like user-mode linux is.
My bet is on the latter.
https://en.wikipedia.org/wiki/Architecture_of_Windows_NT
https://en.wikipedia.org/wiki/Xbox_One_system_software
Re: Wine on Windows 10
#34This 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.
Does WSL work on wine ?
No. WSL is a part of the NT kernel (part of their modular architecture, quite cool to read about) and can't be replicated with an alternative program loader like Wine. You'd need to run a whole new copy of the kernel to get a second instance of WSL, which can already be done through virtualization.
Re: Wine on Windows 10
#35Earlier quoted context omitted.
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…
Virtual 8086 mode isn't available when running a 64-bit OS, so the virtual DOS machine code simply won't work there. This is less of a problem with most 16-bit Windows applications since the limited 16-bit functionality they need is still possible under a 64-bit OS but making this work requires some extremely hairy kernel code.
Re: Wine on Windows 10
#36This would be awesome...I have a bunch of old games that broke when I went to 64-bit Windows. Plus, VMware support for older OSes seems to be getting worse, so that's a less and less viable route.
Re: Wine on Windows 10
#37Earlier 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.
WSL2 is already available in the Windows Insiders Fast Ring. It is, indeed, a VM running on top of HyperV.
Re: Wine on Windows 10
#38Earlier quoted context omitted.
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.
I was referring to WSLv2 here, so technically there is a hypervisor involved at the root level hosting the first WINE instance in the chain.
Further recursion WINE => Cygwin => WINE however will not require more nesting of hypervisors.
Re: Wine on Windows 10
#39WSL2 is in beta now if anyone on HN feels like getting 32 bit apps to work.
Am I correct in thinking WSL2 needs Hyper-V to be enabled?
What's the advantage of it versus running Ubuntu in a VM and using putty?
Re: Wine on Windows 10
#40Hilarious. Props to author for not trying to give a reasonable looking motivation for this beyond "It would be funny". That's more than enough.
But there is a reasonable motivation. Some old games and some other software often don't run well on modern Windows (or sometimes at all). It can be possible to patch them to work but not always and even this relies on motivated and talented fans.