![windows 3.1 setup is unable to create the specified windows 3.1 setup is unable to create the specified](https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/media/task_trigger.png)
- WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED INSTALL
- WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED DRIVERS
- WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED DRIVER
- WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED ARCHIVE
- WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED WINDOWS
The Windows XP computer will automatically assign itself the IP 192.168.0.1 so if you go this route the NT 3.1 computer will need an IP from that range (e.
WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED ARCHIVE
You can then use Internet Connection Sharing on the XP computer to bridge the two adapters (see Q306126 from my Knowledge Base Archive for exact instructions). The way that I personally chose is to set up a second virtual machine with Windows XP, give it a second network adapter, change this network adapter to connect to an Internal network, then change the Windows NT 3.1 VM's network adapter to also connect to the same Internal network. * You will have noticed that getting files to the virtual machine is hard because Windows NT 3.1 has no browser whatsoever and the most primitive implementation of FTP ever (and of course, no working DNS when you use VirtualBox's NAT). Do this before installing Service Pack 3 or you will be in serious trouble.
WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED INSTALL
Then go to Windows Setup, choose to install a different display adapter, go to Other, select the floppy, choose the desired screen resolution and color depth, and click Ignore when an error about framebuf.dll comes up. Before you install this driver, you need to install framebuf.dll from the Windows NT CD (use Windows NT's EXPAND.EXE utility for that).
WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED DRIVER
There's a VirtualBox universal driver that you can get from here. * You will most certainly want to install a graphics card driver so you have more than 640x480. The rest of setup is easy and you should end up with a basic installation of Windows NT 3.1. Scroll to the end for a different solution. Note that Windows NT 3.1 seemingly does not like VirtualBox's implementation of DNS so you will be unable to use DNS this way, which means that you can't access sites like Google. If you use the NAT option under VirtualBox (which is the default) the gateway is 10.0.2.2 and your own IP should be 10.0.2.15 (or anything higher than that), subnet mask is 255.255.255.0. Since Windows NT 3.1 is completely brain-dead it has no DHCP support, which means you will have to manually set an IP.
![windows 3.1 setup is unable to create the specified windows 3.1 setup is unable to create the specified](https://ars.els-cdn.com/content/image/3-s2.0-B9781931836944500131-f07-02-9781931836944.jpg)
WINDOWS 3.1 SETUP IS UNABLE TO CREATE THE SPECIFIED DRIVERS
Continue to select a custom adapter, scroll all the way down to and insert the AMD PCnet driver floppy to continue (for reference the NT drivers are found under A:\WINNT if you use my linked floppy image). Once in the graphical portion of Setup, you will eventually reach Network Setup where Windows NT will detect no network adapters. Setup will run through and switch over to the graphical portion. Create a partition, choose whatever you want (the NTFS conversion consistently fails for me for some reason so might as well stay with FAT). Setup will load it and detect the CD-ROM drive. Windows NT will detect no SCSI drives, press S at this point and insert the ATAPI.SYS boot floppy linked above. Start the virtual machine with the boot floppy inserted. If you don't do this, you will screw yourself over when the graphical portion of Setup starts and have to restart from the beginning again with lots of wasted time. Replace "Windows NT 3.1" with whatever you called your virtual machine. There, type in this command (thanks to OS/2 Museum for this):Ĭode: Select all VBoxManage modifyvm "Windows NT 3.1" -cpuidset 1 00000543 00000800 00000209 078bf1bf The defaults set by VirtualBox are fine but you will need to add a floppy controller with a floppy drive (strangely enough this is not added automatically).īefore you first start the virtual machine (this is important), open a command prompt on the host and navigate to the folder where VirtualBox is installed. Once you have everything you need, create a new virtual machine and set it to Windows NT when it asks you to. (Or alternatively, just edit TXTSETUP.INF and delete the section at the very end.) Then, copy TXTSETUP.INF from the CD over the copy that is present on the boot floppy. * Delete the temporary folder that Setup has created (C:\$WIN_NT$.~LS).
![windows 3.1 setup is unable to create the specified windows 3.1 setup is unable to create the specified](https://i.stack.imgur.com/uvxqX.jpg)
Don't do this and instead reboot off the hard drive again (will still be the operating system as you left it). Setup will create a boot floppy, copy various files to the hard drive and then tell you to reboot from the floppy. * On the DOS prompt, switch to the CD-ROM drive, go to the I386 folder and type WINNT to start Setup. I used an old virtual machine with a pre-installed MS-DOS but I suppose you could use a boot floppy or even Windows 95/98. * Boot into any virtual machine that has a DOS prompt and CD-ROM support. If you don't have a Windows NT 3.1 boot floppy there's a cheap trick you can use: Noting this down as a personal scratchpad because I keep forgetting the steps, but it might be useful to others too.