Wine on Windows 10 • Hacker News Board

Re: Wine on Windows 10

#131

Post by skissane » Wed, Aug 07, 2019, 11:29 PM UTC

monocasa wrote: post #116

makomk wrote: post #35

Earlier quoted context omitted.

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.

You could just run it in an emulator. And microsoft has written a virtual 8086 emulator for virtual PC. Virtual 8086 mode was just a virtual machine anyway.

NTVDM used to contain an x86 emulator included for running DOS programs under Windows NT on non-x86 platforms (Alpha, MIPS, PowerPC). There is no reason in principle why they couldn't have used that existing code on x86-64. But, I assume they decided that the cost of doing that (in developer time/etc) wasn't worth the benefit. (Running DOS programs has little commercial relevance any more, and the small minority who still have a need for that are better served by more fully-fledged virtualisation solutions such as Hyper-V, VMware or VirtualBox.)

Re: Wine on Windows 10

#132

Post by skissane » Wed, Aug 07, 2019, 11:32 PM UTC

intea wrote: post #16

Danieru wrote: post #12

Earlier quoted context omitted.

Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.

Actually most modern hypervisors allow nested virtualization. https://www.linux-kvm.org/page/Nested_Guests https://communities.vmware.com/docs/DOC-8970

Not even just modern hypervisors. The IBM mainframe hypervisor z/VM (and its predecessor VM/CMS) has supported nested virtualisation for decades. It was an important tool to support its own development (especially considering that mainframes were expensive and not even IBM could afford to give every mainframe OS developer a whole mainframe to themselves.)

Re: Wine on Windows 10

#133

Post by yellowapple » Thu, Aug 08, 2019, 2:09 AM UTC

hollerith wrote: post #65

utouq wrote: post #57

Earlier quoted context omitted.

LTSC 2019 contains the WSL and is supported until January 9, 2029

Isn't that short for "Windows 10 Enterprise LTSC 2019"? Am curious how an individual would get access to Windows 10 Enterprise .

If you're not averse to "sailing the high seas", so to speak, the ISOs are readily available online and don't require activation to be fully usable (as long as you're able to tolerate the Windows activation nag watermark and the lack of theme personalization, though I'm sure there are ways to "fix" both of those).

Re: Wine on Windows 10

#134

Post by yellowapple » Thu, Aug 08, 2019, 2:15 AM UTC

jsjohnst wrote: post #92

hollerith wrote: post #65

Earlier quoted context omitted.

Isn't that short for "Windows 10 Enterprise LTSC 2019"? Am curious how an individual would get access to Windows 10 Enterprise .

One easy way is to sign up for MSDN.

I think that only gives you the 90-day trial versions, no?

Re: Wine on Windows 10

#135

Post by sieabahlpark » Thu, Aug 08, 2019, 3:54 PM UTC

mschuster91 wrote: post #126

sieabahlpark wrote: post #125

Earlier quoted context omitted.

Anyone who is using that old of software through a VM to conduct business is wasting more money maintaining that setup than if they migrated somehow. I don't believe this is a good business strategy.

It's not just for business, it's also relevant for old games fans - and will become ever more important for those of us who refuse to buy the "new" games that require a whole ssd for space, are plagued with drm and bugs and to top it off are pay2win upon paying 40€+.

But for those games you don't really need to setup the works of a business layout. Just keep your stuff within the VM no need to share folders.