https://techcommunity.microsoft.com/t5/ask-the-performance-t...
Wine is however able to run 16 bit executables on 64 bit hosts using their version of NTVDM.
[1] http://bytepointer.com/resources/old_new_thing/20060525_178_...
And it would cost a lot too.
But you don't have to imagine -- early amd64 Linux could do it, and there was a patch floating around that kept that feature all the way to 2.6.2x series.
These days vm86 is borked even in 32-bit kernels.
Might be worth checking out for you. Though I see only one Nancy Drew game there.
The main reason was so they could our timecard software. We could have just gave them a $2 RFID card like the production employees, but then they would have to walk down to the time clock and "punch in".
I think they also ended up using it for the Windows version of Outlook because there was some feature they wanted to use that the Mac version did not have.
The amazing stuff was that that vm ran circles around my previous windows laptop, which at that point was three years old. Just way faster than that ever was. Virtual machines and emulators are a good solution for legacy applications. Much easier than pretending ancient APIs are still supported. MS could have saved themselves a lot of grief by just embracing that decades ago and breaking compatibility with each new windows version. Just run the old crap in some vm or emulator. Apple has done that a few times when they switched CPU architectures and when they introduced OS X. They of course removed legacy support as well. But the point is valid: emulation works great.
And it works well enough with Linux support in windows these days; so why not apply that for legacy stuff as well. There's no reason why you wouldn't be able to run everything from the DOS era forty years ago up until now on a modern laptop. And there's no reason to burden modern APIs with all that crap.
[1] https://news.ycombinator.com/item?id=28731534
So, as a customer you got a free properly sized monitor with your software purchase. True story.