Windows 64-bit - 16-bit application is a native experience?
Windows 64-bit - 16-bit application is a native experience?
I rely on an outdated application named otvdm. It enables you to execute 16-bit programs on a 64-bit Windows system. You'll need to go through some research to get it running. All the links are now broken, so I've shared it here: http://s000.tinyupload.com/index.php?fil...3289076545
I'm using a 64-bit operating system and it's a 16-bit installer. It looks like it's now fully supported in Windows 10 64-bit, but I'm not sure how this came about. Still, I'm really happy it's working.
It seems you're checking if someone understands what made the transition to native support for installing a 16-bit app on a 64-bit Windows 10 system. The update likely occurred after the release of a specific Windows build that enabled this functionality without needing additional tools.
I'm using the newest and best version of Windows 10 from the public Insider Program channel. I tried a 16-bit application, but it didn't work. It seems the system might be running as a 32-bit version even though it appears older. That's probably why it doesn't launch properly.
I understand that x86-64 processors generally can't execute 16-bit programs during booting in 64-bit mode. It seems unlikely that both AMD and Intel will keep supporting those older modes in the future. Beyond FreeDOS, it makes little sense to rely on such outdated operating systems in 2020...
When executing the program, check Task Manager for any running processes. You should notice entries like (*32bit) indicating a 32-bit application, similar to what would appear for a 16-bit process. As mentioned earlier and verified by @whm1974, a 64-bit processor cannot execute 16-bit code in 64-bit mode. This suggests that if the program is capable of running on a 64-bit system, it likely relies on emulation. Running the application should probably generate two additional processes, offering further insight into its operation. Review Task Manager to identify any extra processes that appear during execution.
Yes, 16-bit programs would still feel outdated today. Windows 3.x.x actually included 32-bit compatibility starting around the early 1990s, so many 16-bit apps were still running well into the late 1990s and beyond.
64-bit processors easily handle 16-bit programs. The issue isn't the hardware—it's the operating system. Microsoft chose not to include 16-bit compatibility on their 64-bit chips, effectively ending support for older systems.
Just for informational sakes. Here is a open source project that I found that claims to allows 16-bit programs to run under Win10 64-bit, I have not tried it to know if it really works, and the creator English needs work, but something to know. as a possible option to add to my list: https://github.com/otya128/winevdm