Windows NT 3.1 Build 297 in Virtual PC 2004/2007

[SupernovaNick]

I am trying to install Windows NT 3.1 Build 297 (Preliminary Release for Developers) in Virtual PC. I follow the DOS2NT instructions perfectly (Install MS-DOS, run D:\DOS2NT\DOS2NT C: (path is set to C:\DOS, so xcopy copies files from the NT folder to the newly created C:\WINNT folder, in which case I change the Windows directory from C:\NT to C:\WINNT in BOOT.INI), edit the computer name and user name in REGISTRY.INI, and reboot. However, it hangs at the boot screen (the blue screen with the version name, build number, ram, etc. at the top). This happens in both Virtual PC 2004 and 2007. Is it at all possible to successfully install build 297 in Virtual PC? Are there any other fixes I need?

Thanks.

[Overdoze]

I guess this is another great opportunity to remind people that Virtual PC is horribly outdated by now and has a bunch of weird quirks that cause problems with various guest OSes.

Early NT 3.1 builds are also especially sensitive to certain hardware configurations and behaviour, so I'll give you the usual advice to just save yourself the trouble and use something else that causes less problems. Preferably an emulator.

[TheCollector1988]

Just use 86Box, as this emulator supports SCSI adapters that NT 3.1 297 likes, namely the Adaptec 154x series. In addition, use its dedicated 1.2M boot disk to install this build on this emulator.

[Beta12]

I guess this is another great opportunity to remind people that Virtual PC is horribly outdated by now and has a bunch of weird quirks that cause problems with various guest OSes.

Yeah, and Windows NT 3.1 is a super modern operating system

Dude, the author of the topic wants to launch the old operating system! I have not tested WinNT in VPC 2007 but it is ideal for Win9x, WinXP and even WinVista or Win7

[Overdoze]

I have not tested WinNT in VPC 2007

I can tell, since you've completely ignored OP's problem and failed to provide any advice whatsoever.

Now, as far as the particular issue goes, it probably depends on OP's host CPU. In which case it'd be worth trying it on some older machine, or do what I said in the first place.

[AlphaBeta]

Dude, the author of the topic wants to launch the old operating system! I have not tested WinNT in VPC 2007 but it is ideal for Win9x, WinXP and even WinVista or Win7

Why use a crumbling wooden hammer when you can use a hammer made of iron? There are now tools that can do the job even better than Virtual PC, namely 86Box and co.

[Beta12]

Is this version about - Microsoft Windows NT 3.1 (3.10.297) (6-28-1992) SDK (ISO) ??

[TwilyDev]

How to install this build (I tested this build too!)
1. Use VirtualBox and create virtual machine with Windows 3.1 as the operating system.
2. Use the boot disk that came with it for installation
3. Use SCSI CD-ROM drive (Storage>Remove Optical Drive at IDE Controller>Add SCSI Controller>Change SCSI type to BusLogic>Insert the Build 297 ISO.
4. Start the VM and Follow the instructions.

EDIT: Here's the results:





Note: 1. Weird looping startup sound, even after restart one more time. You should mute your VM.
2. Also, Never do video-capturing the VM. That will cause registry corruption, which is resulting on no program groups.

[TheCollector1988]

The loop is because the build, by default, sets the wrong IRQ for the Sound Blaster card.

[MSUser2013]

The loop is because the build, by default, sets the wrong IRQ for the Sound Blaster card.

Could that be fixed by changing the Sound Blaster IRQ setting by either changing the settings of the driver inside the OS (if permitted) or changing it in the virtual machine's settings?

[TheCollector1988]

It is fixable by using going to regedit.exe, services in HKLM/System, look for an entry called "sndblst", check its device properties, you'll find out it uses IRQ 7 instead of 5, change it to use IRQ 5.

[TwilyDev]

It is fixable by using going to regedit.exe, services in HKLM/System, look for an entry called "sndblst", check its device properties, you'll find out it uses IRQ 7 instead of 5, change it to use IRQ 5.

It's actually "HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001/Services/Sndblst"
Can you edit it?

And the sound is working properly now.Thanks.

[TheCollector1988]

HKLM is its abbreviation.