Windows 3.1 setup disk
![windows 3.1 setup disk windows 3.1 setup disk](https://www.howtogeek.com/wp-content/uploads/2015/10/img_560dd7225d78f.png)
![windows 3.1 setup disk windows 3.1 setup disk](https://jtlog.files.wordpress.com/2011/04/win-disks.jpg)
VirtualBox Guest Additions don't support any version of Windows older than Windows 2000/XP, so shared folders won't work. The Legacy PC Project - guides for installing MS-DOS and Windows for Workgroups on old PCs.
#WINDOWS 3.1 SETUP DISK INSTALL#
Instead, download all the components and install it yourself. I'm no longer hosting the bundled tarball that contains all the files + a VirtualBox preinstalled disk image to clean up disk space on my server.
#WINDOWS 3.1 SETUP DISK DRIVER#
Find a video driver that supports more than 16 colors (more info here).Disable hardware virtualization (in the System/Acceleration tab in the VM settings).Start Windows in standard mode ( win /s).If you have issues with erratic mouse movement within Windows 3.1 on VirtualBox, some solutions are (from here): If you want to download the components separately (DOS, Windows for Workgroups 3.11 and the drivers) you can find individual links on my MS-DOS page. Sometimes you'll have to go to the previous disk instead. When you get a "Can't read file" error, you'll usually swap in the next numbered disk and hit enter. Windows 3.1 can still be installed from these images, it will just require more disk juggling. I got ahold of this version of Windows 3.1 from a CD image instead of floppies, so I had to convert them to floppy images myself, and not all the files fit on all the disks (there should only be 6 disk images but there's 7 in this tarball). The version of Windows in this tarball is 3.1 - not Windows for Workgroups 3.11 (for that, download it separately from my MS-DOS page). WQGHLT to make Windows not consume 100% CPU (Floppy Image).DOSIDLE to make DOS not consume 100% CPU(Floppy Image).I have some downloads for the following things: You can download everything from my MS-DOS page. What's more, virtual floppy disks are write-protected.For a limited time only, files for installing MS-DOS 6.22 and Windows 3.1! I tried manually copying these three files to a physical floppy in the Windows 3.1 VM, but I was met by errors. A long Google search has provided me with nothing.Īs far as I know, the Windows 3.1 startup disk contains only autoexec.bat, config.sys and, but they all must be the correct version. So, if somebody could provide a Windows 3.1 startup floppy image in. I have tried multiple times to create a startup floppy in Windows 3.1 using a physical floppy drive and floppy, but every attempt has resulted in failure.
![windows 3.1 setup disk windows 3.1 setup disk](https://i.ebayimg.com/images/g/rQIAAOSw5z1d9~jh/s-l300.jpg)
![windows 3.1 setup disk windows 3.1 setup disk](https://live.staticflickr.com/4104/5431952829_42d3ed6fc9_b.jpg)
You would be greeted by COMMAND.COM relatively quickly, and you could simply type 'win' to get to Windows, instead of the full path name. I understand that Windows 3.1 originally used a startup floppy, which your system would boot with.
#WINDOWS 3.1 SETUP DISK DRIVERS#
Everything works fine, but the only way I can start up Windows is to boot the virtual floppy and type the full path of win.exe ( C:\windows\win), and the image contains unnecessary drivers and third-party modifications which take a while to load upon booting. I installed Windows 3.1 on a virtual machine in VBox using a virtual MS-DOS 6.22 floppy boot disk (.img floppy image file).