Wine on Windows 10

Post by josinalvo » Wed, Aug 07, 2019, 12:52 PM UTC

Crinus wrote: post #79

0-_-0 wrote: post #73

Earlier quoted context omitted.

Playing Exile 2 is exactly why I want to run 16 bit applications. I basically learned English from that game! I remember being frustrated being locked into the shareware version by Shareware Barriers, figuring out how to edit maps by using Norton Disk Edit on the game files, and digging new tunnels into the cave wall. I was about 12 and I still consider this my greatest hacking achievement...

You are in luck then, all three Exile games are free from the site :-) (you need to dig a bit to find them, go to the games, then old games then click on the icon for the windows version).

Post by coldpie » Wed, Aug 07, 2019, 12:57 PM UTC

jraph wrote: post #60

davidgerard wrote: post #45

Earlier quoted context omitted.

WSL is part of Windows 10, so I didn't feel the title was leaving out something important.

Well, you are right but I expected to find an article speaking about Wine running on native Windows without WSL, which would make it interesting in another way. I would not expect Wine not to run on WSL. What I learned from the article though is that WSL1 does not run 32 bit binaries (and that someone botched their registry trying to run Wine on Windows back in 2004, which I found funny).

Post by dsfyu404ed » Wed, Aug 07, 2019, 1:02 PM UTC

jeroenhd wrote: post #32

codetrotter wrote: post #30

Earlier quoted context omitted.

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…

Post by coldpie » Wed, Aug 07, 2019, 1:08 PM UTC

rat9988 wrote: post #84

coldpie wrote: post #82

Earlier quoted context omitted.

To tie this back to Wine, here is what we actually do during some parts of the Proton[1] build process: Run a Debian 9 VM, inside of which we run an Ubuntu 12.04 Docker container (the Steam runtime), which runs an Arch Linux chroot in order to gain a modern cross-compiler. It's a doozy[2]! [1] Proton is Valve's fork of Wine which ships with the Linux Steam client. [2] https://github.com/ValveSoftware/Proton/commit/d6…

May I ask why you need that many distributions? It really looks interesting.

Post by ygra » Wed, Aug 07, 2019, 1:20 PM UTC

dsfyu404ed wrote: post #85

jeroenhd wrote: post #32

Earlier quoted context omitted.

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…

>I doubt anyone is missing much aside from a few nostalgic gamers. There's tons of 16-bit SCADA stuff in the world that it would be nice to not have to run on a ~20yo version of windows.