Windows 10: How does Windows identify 16 bit apps

My question is: how do I make windows run a program when it knows its a 16 bit app on a 64 bit PC.
I know it reads the exe pe header, but instead of displaying the "This app cant't run on your PC" banner. I would like it to load another program - like in the attached picture.





It's more of a curiosity, because all I have to do is right click the mouse button. (its Win311/DosBox)
I've tried to copy the ntvdm files & registery entries from Win10 x32 to Win10 x64, but it completly ignores them ;(

P.S. I dont want to associate all the .exe files with another program before I run them. That's just like a really inefficient virus.

:)

 

Brand new computer windows 10 64 bit

Windows 10 64 bit does not have a 16 bit subsystem, only the 32 bit version does. So, compatibility mode will not work.

Your best option for running older 16 bit applications is through a virtual machine.

Run Older or Incompatible Software on Windows 10 in a VM

Learn more about 16 bit subsystem and application compatibility.

How to Enable 16-bit Application Support in Windows 10 - groovyPost

 

Compatibility mode in Windows 10

Looks like the game may be 16 bit.

Here's what I don't understand. in the program compatibility wizard it applies a fix which in this case is to run it in Windows XP SP3 compatibility mode, but if it is a 16 bit application and the windows version is 64 bit, the compatibility wizard should
identify the program as 16 bit and display a message stating the 16 bit program cannot be made to run.

What I don't get is why 64 bit versions of Windows did away with 16 bit compatibility.

From what I understand incompatibility with some older programs and hardware keeps some from buying new Windows versions.

As it is now if I want to play the older DOS based games I have to use a separate program such as Dos box.

DOS box can make most 16 bit programs run in 64 bit Windows versions so surely it isn't that hard for Microsoft to allow those programs to run either natively or through an app.

In a way it bothers me that I have to keep an older PC running just to use programs that will not run on Windows 10.

 

There is no way a 64 bit OS can run 16 bit software outside some kind of virtual machine, such as DosBox. Essentially a 64 bit CPU has 2 operating modes, 64 bit and 32 bit, plus a few not relevant to the situation. A 64 bit OS must run in 64 bit mode where it can run either 64 or 32 bit software, but not 16 bit. In 32 bit mode, for a 32 bit OS, it can run either 32 or 16 bit software.

I don't know how to do what you want. It may require third party software.

 

I probably would fire up my 80386-40MHz or 80486-25OD75 computer to run the 16-bit programs.

 

I had one of those, I think it was a Cyrix

 

I had the Intel 486. I think my 386 was Cyrix.

 

Hi there

If you want to run 16 bit software I suggest you run it in a VM -- you can install say Windows 98 as a Virtual machine easily enough -- there's a generic key on the Net just google for it.

If you can't find it it's here (released by Ms itself so not Pirated !!!).

VP9VV-VJW7Q-MHY6W-JK47R-M2KGJ

Keep the VM isolated from the Internet though -- the best way to do this if you have to share files with your Host Pc is simply to use HOST ONLY networking when creating the VM . It's usually in the config files.

You can use VMware player, or VBOX for creating a Virtual machine with FREE software or if you have W10 pro or enterprise you can use HYPER-V. Kari has excellent tutorials on creating Virtual machines using HYPER-V -look in the tutorial section.

In fact using a Virtual Machine is the recommended (and safest) way of using legacy hardware and software.





Cheers
jimbo

 

oh I think I figured it out... if anyone is interested.
I used the 16 bit setup in windows 64 bit option.....
Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NtVdm64\X-LAST-FAILOVER] "InternalName"="*" "MappedExeName"="C:\\blaa-blaa-blaa\\DOSBox-Win31\\run-as-16bit.exe" "ProductName"="*" "ProductVersion"="*" "CommandLine"="%m"[/quote] But it only worked with some .exe files (like NE). Not with .com. I have not done any detailed tests.