News for hackers. Stuff that matters.
Re:Windows NT vs. Unix: A design comparison by sedatk on Monday September 09, 2024 @09:00PM (#41496097)
True. I just assumed that 16-bit support got dropped since Windows 11 was 64-bit only.
Re:Windows NT vs. Unix: A design comparison by EvanAnderson on Tuesday September 10, 2024 @01:02AM (#41497306)
Microsoft decided not to type "make" for NTVDM on 64-bit versions of Windows (I would argue arbitrarily). It has been unofficially built for 64-bit versions of Windows as a proof-of-concept: https://github.com/leecher1337/ntvdmx64
Re:Windows NT vs. Unix: A design comparison by badgersnake on Tuesday September 10, 2024 @02:40AM (#41497843)
That’s okay, and if people want to test their specific use case on that and use it then great.

It’s a pretty different amount of effort to Microsoft having to do a full 16 bit regression suite and make everything work and then support it for the fewer and fewer customers using it. And you can run a 32 bit windows in a VM pretty easily if you really want to.

Re:Windows NT vs. Unix: A design comparison by Timwi on Tuesday September 10, 2024 @04:15AM (#41498434)
Or you can run 16-bit Windows 3.1 in DOSBox.
Re:Windows NT vs. Unix: A design comparison by badgersnake on Tuesday September 10, 2024 @06:11AM (#41499208)
Sure, but again that’s on you to test and support.
Re:Windows NT vs. Unix: A design comparison by skissane on Tuesday September 10, 2024 @08:13AM (#41499957)
> Microsoft decided not to type "make" for NTVDM on 64-bit versions of Windows (I would argue arbitrarily).

I recently discovered that Windows 6.2 (more commonly known as Windows 8) added an export to Kernel32.dll called NtVdm64CreateProcessInternalW.

Not sure exactly what it does (other than obviously being some variation on process creation), but the existence of a function whose name starts with NtVdm64 suggests to me that maybe Microsoft actually did have some plan to offer a 64-bit NTVDM, but only abandoned it after they’d already implemented this function.