5 ms·
This 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-b
by jeroenhd 7y ago
This 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.
- frabert 7y agoExactly. I used a similar approach to install Space Empires III on a Windows 10 x64 machine which would not run its 16bit installer but would run the 32bit game itself just fine.
- julienfr112 7y agoDoes WSL work on wine ?
- std_throwaway 7y agoMaybe by using qemu? (Windows on qemu on Wine on Linux on Windows)
- jeroenhd 7y agoNo. 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.
- makomk 7y agoNope. WSL is basically a reimplementation of the Linux kernel's syscall layer (or at least the original version of it was - WSL 2 is an actual Linux kernel running in a VM). If you do a Linux syscall from within a Wine app it calls into the actual underlying Linux kernel and Wine itself makes heavy use of this within its libraries. WSL on Wine isn't possible and doesn't really make sense. I guess it might be possible to add support for WSL 2 since that's just a VM, but I'm not sure why you'd ever want to since it is just a VM.
- cyborgx7 7y agoThis project is only completed when you can recursively keep doing this forever, without it ever breaking.
- Danieru 7y agoAny CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
- Nullabillity 7y agoCygwin and Wine don't use virtualization. And even if they did, most hypervisors support nesting these days.
- ape4 7y agoBecause, of course, its not a emulator
- mschuster91 7y agoWhy? There's only one hypervisor involved for the initial "wine" environment.
- lnx01 7y agoNeither WINE nor WSLv1 use virtualisation. WSLv2 does use virtualisation however; but WINE still isn't a VM.
- mschuster91 7y agoI 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.
- intea 7y agoActually most modern hypervisors allow nested virtualization. https://www.linux-kvm.org/page/Nested_Guests https://www.linux-kvm.org/page/Nested_Guests https://communities.vmware.com/docs/DOC-8970 https://communities.vmware.com/docs/DOC-8970
- Crinus 7y agoYou can already do that with OTVDM: https://github.com/otya128/winevdm 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/otya128/winevdm https://github.com/otya128/winevdm [2] http://www.spiderwebsoftware.com/exile/winexile.html http://www.spiderwebsoftware.com/exile/winexile.html
- codetrotter 7y agoLooking 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 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.
- jeroenhd 7y agoMS 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.
- krylon 7y ago> 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. That would be so awesome! :)
- cambalache 7y agoIf you are a desperate bastard like me, you can install it with Windows build 18917 as described here : https://devblogs.microsoft.com/commandline/wsl-2-is-now-available-in-windows-insiders/ https://devblogs.microsoft.com/commandline/wsl-2-is-now-avai.... Caveat: I have not done it, but hopefully will do it during the weekend.
- teekert 7y agoThis is why I think we will always be able to run all software ever, just keep on piling up older virtualizers (or api translators).