Windows NT 3.1 will install, however it does not have PCI support so you'll be restricted to the ISA machine. Also NT 3.1 cannot drive IDE CD-ROM's. So you would have to follow the network installation guide.

When NT 3.1 was released pentium CPU's were still beta, and the cpuid thing had not been finalized enough in the install script. You will have to fix the setup.inf script to always install the 486 path.

+

Windows NT 3.1 will install, however it is incompatible with IDE CD-ROM's. This is simply because they did not exist at the time. So you would have to follow the network installation guide. You will also want the [http://vpsland.superglobalmegacorp.com/install/WindowsNT3.1/pcnet.7z AMD Pcnet] driver, which is vastly better then the old legacy NE2000.

−

+

−

You need to edit a string in the files INITIAL.IN_ and SETUP.IN_

+

−

+

−

Open each one in notepad and search for:

+

−

[ProcessorVar]

+

−

+

−

Then change the string below it from

+

−

+

−

STF_PROCESSOR = "" ? $(!LIBHANDLE) GetProcessor

+

−

+

−

to

+

−

+

−

STF_PROCESSOR = $(ProcessorID_I586)

+

+

== CPU TYPE ==

+

When NT 3.1 was released pentium CPU's were still beta, and the cpuid thing had not been finalized enough in the install script. So as a precaution we will need to flag the 486 cpu type.

== MS-DOS prepare ==

== MS-DOS prepare ==

Line 29:

Line 17:

With MS-DOS installed and able to access a CD-ROM, you will need a blank floppy image, in addition to either an ISO image with NT 3.1 or a 3.1 CD-ROM.

With MS-DOS installed and able to access a CD-ROM, you will need a blank floppy image, in addition to either an ISO image with NT 3.1 or a 3.1 CD-ROM.

−

I'll be using my physical NT 3.1 CD with WIN32 SDK, and Qemu 0.10.5 which will allow me to set my cpu to an Intel i486 cpu so I won't have to worry about the inf files.

+

I'll be using my physical NT 3.1 CD with WIN32 SDK, and Qemu 0.10.5 which will allow me to set my cpu to an Intel Pentium CPU so I won't have to worry about the inf files.

And we'll be into the GUI phase of the install. Since we've got an AMD PCnet driver in the floppy drive we can do the network setup. Remember the AMDPcnet will need its driver installed from "A:\WINNT" ... Also you'll want to load it for TCP/IP, drop the NetBEUI, and configure the TCP/IP as follows:

−

+

−

Remember the ne2000 nic is 0x300 IRQ 2/9. Also you'll want to load it for TCP/IP, drop the NetBEUI, and configure the TCP/IP as follows:

+

*ADDRESS 10.0.2.15

*ADDRESS 10.0.2.15

Line 75:

Line 61:

The soundblaster can be configured, the port is 220, and the IRQ is 5.

The soundblaster can be configured, the port is 220, and the IRQ is 5.

+

+

The install will probably want to format your pcnet disk as an emergency disk, it doesn't matter at this point, and worst case you can always re extract your driver disk if you reinstall.

+

+

== Logging on for the first time ==

+

This is a little tricky on Qemu, as you have to do the following to simulate a CAD

+

+

CONTROL+ALT+2

+

sendkey ctrl-alt-delete

+

CONTROL+ALT+1

+

+

And now you should have the logon prompt.

+

+

You may want to setup an autologon via the registry. You can find more information via [http://support.microsoft.com/kb/97597 kb97597].

== Where to go from here ==

== Where to go from here ==

Line 80:

Line 79:

Well Windows NT 3.1 is more of a landmark for Microsoft's first homegrown 32bit OS, and at the same point it's interesting how much it's changed, and how little in some other ways. I would however recommand getting service pack 3 for NT 3.1

Well Windows NT 3.1 is more of a landmark for Microsoft's first homegrown 32bit OS, and at the same point it's interesting how much it's changed, and how little in some other ways. I would however recommand getting service pack 3 for NT 3.1

−

You can download it from [http://75.127.119.16/install/WindowsNT3.1/NT31-sp3.zip here]. You'll have to get creative with either MS-DOS & CD-ROM images to copy it in there, or some other method..

+

You can download it from [http://vpsland.superglobalmegacorp.com/install/WindowsNT3.1/WindowsNT%203.1%20servicepack%203%20i386.zip here]. You'll have to get creative with either MS-DOS & CD-ROM images to copy it in there, or some other method..

16 bit versions of Netscape *WILL* run on NT 3.1!

16 bit versions of Netscape *WILL* run on NT 3.1!

−

There is a nice little cache here: http://ftp.lanet.lv/ftp/windows/www/netscape3.0/?C=M;O=A

+

There is a nice little cache [http://ftp.lanet.lv/ftp/windows/www/netscape3.0/?C=M;O=A here]:

I recommend the [http://ftp.lanet.lv/ftp/windows/www/netscape3.0/n16e301p.exe n16e301p.exe]. You can install Video for windows after 'fixing' the setup program to not abort on NT 3.1 but it won't run correctly, nor will [[cooltalk]] run correctly.

I recommend the [http://ftp.lanet.lv/ftp/windows/www/netscape3.0/n16e301p.exe n16e301p.exe]. You can install Video for windows after 'fixing' the setup program to not abort on NT 3.1 but it won't run correctly, nor will [[cooltalk]] run correctly.

−

If you have access to Visual C++ 1.0 32bit you'll be in luck as you can rebuild a few things. In the transition from 3.1 to 3.5 the executable format changed.. You'll find that plenty of cli utilities will NOT run on 3.1.

+

By default Windows NT 3.1 will only detect 64MB of ram. This is a 'fault' of ntdetect.com & ntldr. You can however download servicepack 5 for Windows NT 3.51, and copy it's ntdetect.com/ntldr to see up to 3GB of ram! You can download service pack 5 right [http://vpsland.superglobalmegacorp.com/install/WindowsNT3.51/sp5_351i.exe here]. I recommend using Netscape from within NT 3.1. Make sure you have installed service pack 3 for NT 3.1 before you do this!!

−

You may also want to grab a copy of the Windows NT 3.1 resource kit: http://75.127.119.16/install/WindowsNT3.1/Resource%20Kits/

+

If you have access to [[Visual C++ 1.1]] or the [[Windows NT 3.1 SDK]] you'll be in luck as you can rebuild a few things. In the transition from 3.1 to 3.5 the executable format changed.. You'll find that plenty of cli utilities will NOT run on 3.1.

+

+

You may also want to grab a copy of the Windows NT 3.1 resource kit [http://vpsland.superglobalmegacorp.com/install/WindowsNT3.1/Resource%20Kits/ here]:

And for anyone interested you'll want to read [http://support.microsoft.com/kb/108581 this] MS article on how to configure the POSIX subsystem to run [[vi]] correctly.

And for anyone interested you'll want to read [http://support.microsoft.com/kb/108581 this] MS article on how to configure the POSIX subsystem to run [[vi]] correctly.

−

[[category:tutorials]] [[Category:Qemu]]

+

+

+

[[Category:QEMU Tutorials]] [[Category:Qemu]]

Latest revision as of 08:17, 25 July 2017

Windows NT 3.1 will install, however it is incompatible with IDE CD-ROM's. This is simply because they did not exist at the time. So you would have to follow the network installation guide. You will also want the AMD Pcnet driver, which is vastly better then the old legacy NE2000.

The first thing in MS-DOS I'm going to do is format the floppy to make sure it's blank to appease the installer.

format a:

Then change to the cdrom & run winnt.exe...

d:
cd i386
winnt /F /C

I'm going to skip the verifies for disk space & floppy writes.. When setup has completed it's job exit Qemu, and this would make a great time to boot back into MS-DOS, and alter the setup.inf & initial.inf files as mentioned above. You may have to expand them manually but it's really not that hard.

Install

Windows NT will boot from the floppy, and it will naturally detect NO SCSI drivers. I recommend changing the mouse to the "Microsoft Mouse Port Mouse (including BallPoint)" driver. It will then go thru the motion of copying files (yet again) and then it'll prompt to reboot. Quit Qemu as we won't need the floppy now.

And we'll be into the GUI phase of the install. Since we've got an AMD PCnet driver in the floppy drive we can do the network setup. Remember the AMDPcnet will need its driver installed from "A:\WINNT" ... Also you'll want to load it for TCP/IP, drop the NetBEUI, and configure the TCP/IP as follows:

ADDRESS 10.0.2.15

MASK 255.255.255.0

GATEWAY 10.0.2.2

DNS 10.0.2.3

The soundblaster can be configured, the port is 220, and the IRQ is 5.

The install will probably want to format your pcnet disk as an emergency disk, it doesn't matter at this point, and worst case you can always re extract your driver disk if you reinstall.

Logging on for the first time

This is a little tricky on Qemu, as you have to do the following to simulate a CAD

CONTROL+ALT+2
sendkey ctrl-alt-delete
CONTROL+ALT+1

And now you should have the logon prompt.

You may want to setup an autologon via the registry. You can find more information via kb97597.

Where to go from here

Well Windows NT 3.1 is more of a landmark for Microsoft's first homegrown 32bit OS, and at the same point it's interesting how much it's changed, and how little in some other ways. I would however recommand getting service pack 3 for NT 3.1

You can download it from here. You'll have to get creative with either MS-DOS & CD-ROM images to copy it in there, or some other method..

16 bit versions of Netscape *WILL* run on NT 3.1!
There is a nice little cache here:

I recommend the n16e301p.exe. You can install Video for windows after 'fixing' the setup program to not abort on NT 3.1 but it won't run correctly, nor will cooltalk run correctly.

By default Windows NT 3.1 will only detect 64MB of ram. This is a 'fault' of ntdetect.com & ntldr. You can however download servicepack 5 for Windows NT 3.51, and copy it's ntdetect.com/ntldr to see up to 3GB of ram! You can download service pack 5 right here. I recommend using Netscape from within NT 3.1. Make sure you have installed service pack 3 for NT 3.1 before you do this!!

If you have access to Visual C++ 1.1 or the Windows NT 3.1 SDK you'll be in luck as you can rebuild a few things. In the transition from 3.1 to 3.5 the executable format changed.. You'll find that plenty of cli utilities will NOT run on 3.1.

You may also want to grab a copy of the Windows NT 3.1 resource kit here:

And for anyone interested you'll want to read this MS article on how to configure the POSIX subsystem to run vi correctly.