4 ms·
Funny you gloss over the most important part: > Legacy applications that run in Virtual 8086 mode or use hardware task management will not work in this mode.
by deaddodo 1y ago
Funny you gloss over the most important part:
> Legacy applications that run in Virtual 8086 mode or use hardware task management will not work in this mode.
That being said, this isn't worth arguing over. If you can provably run late 1980s-early 1990s 16-bit code in AMD64 compatibility mode, with full execution protections and support of even most not all commercial software; that goes against the general understanding of those architectures. Document it and add it to the academic sphere to expand the knowledge.
- jcranmer 1y agoI can see that DOS applications might require Virtual 8086 mode, but from what I can tell, almost no Win16 applications require it nor require hardware task management (I'm not even sure I'm aware of any application that uses hardware task management!). Granted, Win16 is not an especially long period of active application development, but I would expect that the vast majority of Win16 applications would work perfectly fine in x86-64 compatibility mode. I know that the ones I have played with do.
- Agingcoder 1y agoI love your answer. It’s honest, and actually typical of this kind of problem space where what’s possible exceeds what was expected. It reminds me of what coders did with older atari st machines to achieve overscan and a whole bunch of other tricks. The manuals explicitly stated that some things were not possible or would cause machine resets … except that there was a way.