GUI setup will say it doesn't work with the current processor. So you are forced to modify Initial.inf and Setup.inf if you want to use Windows NT 3.1 on modern pc.
I think that's the problem, VPC doesn't and so Windows Setup sees the A64, or whatever, can't tell what it is and so blocks installation to prevent you from installing Windows on a processor that may not support it, thus preventing a potentially unusable system.
I think that's the problem, VPC doesn't and so Windows Setup sees the A64, or whatever, can't tell what it is and so blocks installation to prevent you from installing Windows on a processor that may not support it, thus preventing a potentially unusable system.
-Q
My installation of Windows nt workstation 3.1 not 3.51 works fine.
You can install nt 3.51 fine without modification, but you have to modify the setup files to install nt 3.1 or 3.50 on modern pc's or in virtual pc.
Actually Windows 3.51 has problems with the ATAPI and ATDISK drivers that I describe work arounds for in another post. Old OS's working on modern (even emulated) hardware will always have some glitching that needs work arounds
So describe in detail your workaround and where you researched it please for the future readers
Comments
-Q
So virtual pc virtualizes the host processor?
It does no processor emulation whasoever....
-Q
You can install nt 3.51 fine without modification, but you have to modify the setup files to install nt 3.1 or 3.50 on modern pc's or in virtual pc.
I have 1.6 GHz celeron M processor.
So describe in detail your workaround and where you researched it please for the future readers