I really don't understand why Microsoft didn't build this when they released 64 bit windows.
16 bit windows wasn't complicated, and a simple VM and API translation layer could have kept compatibility going back 30+ years for not many engineering hours.
Yet instead they dropped 16 bit windows support and probably spent more engineering hours to support all the ancient software trying to update, and users who held back upgrading windows because they needed said ancient software, etc
> Note that 64-bit Windows does not support running 16-bit Windows-based applications. The primary reason is that handles have 32 significant bits on 64-bit Windows. Therefore, handles cannot be truncated and passed to 16-bit applications without loss of data. Attempts to launch 16-bit applications fail with the following error: ERROR_BAD_EXE_FORMAT.
winevdm on Windows eschews that level of integration, but perhaps MS should have shipped WoW16 with limitations instead of nothing.
Installed MS Office 2.0 some months ago with it just for fun. It actually works pretty well apart from the dictionary files, for some reason those are not recognized
1, is it good enough for modern day to day word processing (mostly emails)? Yes it is
2, can the modern word processors (Office 365, LibreOffice, Google Docs) recognize and open the files created with it? (doc, rtf anything but plain text) Yes they can
For work, not due to other requirements, however for personal documents I fully agree with your first point, MS Office 2.0 is good enough to type in some snail letters, school reports or CVs.
Yes, however if you are only using them privately as a modern typewriter for stuff that is anyway going to be sent on paper, there is less of a concern.
Now sharing files with others is another matter, and I fully agree.
In related news, with the latest WINE on Linux 16 bits/32 bits applications are supported, so I was able to run my beloved Civilization 2 without problems.
I really don't understand why Microsoft didn't build this when they released 64 bit windows.
16 bit windows wasn't complicated, and a simple VM and API translation layer could have kept compatibility going back 30+ years for not many engineering hours.
Yet instead they dropped 16 bit windows support and probably spent more engineering hours to support all the ancient software trying to update, and users who held back upgrading windows because they needed said ancient software, etc
being able to transfer HANDLEs across the 16/32-bit boundary notably for COM/OLE integration becomes a lot more painful
Microsoft says at https://learn.microsoft.com/en-us/windows/win32/winprog64/ru...:
> Note that 64-bit Windows does not support running 16-bit Windows-based applications. The primary reason is that handles have 32 significant bits on 64-bit Windows. Therefore, handles cannot be truncated and passed to 16-bit applications without loss of data. Attempts to launch 16-bit applications fail with the following error: ERROR_BAD_EXE_FORMAT.
winevdm on Windows eschews that level of integration, but perhaps MS should have shipped WoW16 with limitations instead of nothing.
Installed MS Office 2.0 some months ago with it just for fun. It actually works pretty well apart from the dictionary files, for some reason those are not recognized
https://files.catbox.moe/dy4bqy.png
I’ve used it for a week just I was curious:
1, is it good enough for modern day to day word processing (mostly emails)? Yes it is
2, can the modern word processors (Office 365, LibreOffice, Google Docs) recognize and open the files created with it? (doc, rtf anything but plain text) Yes they can
For work, not due to other requirements, however for personal documents I fully agree with your first point, MS Office 2.0 is good enough to type in some snail letters, school reports or CVs.
Also there is security. I think, I just guess, these old 16bit file formats are all exploitable to some extent
Yes, however if you are only using them privately as a modern typewriter for stuff that is anyway going to be sent on paper, there is less of a concern.
Now sharing files with others is another matter, and I fully agree.
Doubt you'd be storing important ssh keys on the same VM
You would be surprised on how some offshoring projects go, which anyway has zero to do with what I was talking about.
And a refreshingly straightforward UI compared to modern behemoths.
Nice, I will be able to play Civ2 on Windows 11!
In related news, with the latest WINE on Linux 16 bits/32 bits applications are supported, so I was able to run my beloved Civilization 2 without problems.
Civ2 - well, at least its Test of Time incarnation - has specific patches to keep it running without external tools.
Oh my good, windows 3.1x.... good old times and a word application that never crashed!
>a word application that never crashed!
You must have lived in a different reality to me.
Finally, 16-bit Windows support for 64-bit Windows.
Winevdm has been out a while.