Alternatively you may select Do not add a virtual hard disk and create a hard disk to the desired size after the VM had been created. Again as we’ve chosen Windows 3.1, VirtualBox has suggested the recommended size of the hard disk to be 1 GB. As we don’t have one yet, we will select the Create a virtual hard disk now option and choose Create. Now the option is regarding a hard disk for the VM. DOS and Windows 3.1 will happily run on the lowest option of 4 MB, though anything above 32 MB is considered overkill. By default as Windows 3.1 had been selected, the recommended memory size is 32 MB. The following option now is to choose the amount of RAM. Setting up a new Windows 3.1 virtual machine.
You may either select the Windows version as shown below, or type Windows 3.1 and the drop-down selection will automatically change. A Create Virtual Machine dialog box will appear allowing you to select which operating system it will be using for this virtual machine (VM). Microsoft Network Client 3.0 for MS-DOS Download.Unlike newer versions, Windows up to version 3.x would typically sit on top of some variation of DOS such as MS-DOS or PC-DOS which was the operating system. Windows 3.1 wasn’t technically an operating system in itself, though common perception is that it was. VirtualBox isn’t my first preference for emulation, however it’s free to obtain. For this guide I’m using Oracle VirtualBox 5.1.4 (the latest at the time) on a Windows 10 machine. Wolverine stack was an early version of the TCP/IP stack that would later ship with Windows 95, and provided an early testbed for the 16-to-32-bit compatibility layer that was crucial to Windows 95's success.įollowing the release of MS-DOS 6.22 in 1994, WFW 3.11 largely replaced Windows 3.1 for OEM installations on new PCs due to its improved capabilities and greater stability.Installing DOS and Windows 3.x is relatively straightforward, though configuring both to perform the best they can can be a little more tricky.
However, it was only compatible with Windows for Workgroups 3.11, and lacked support for dial-up. Usually third-party packages were used, but in August 1994, Microsoft released an add-on package (codenamed Wolverine) that provided TCP/IP support in Windows for Workgroups 3.11. Wolverine was a 32-bit stack (accessible from 16-bit Windows applications via WinSock Thunk), which gave it superior performance to most of the third-party TCP/IP Windows stacks available. WFW 3.11 dropped standard mode support and requires a 386 machine to run.Ī Winsock package was required to support TCP/IP networking in Windows 3.x. It supported 32-bit file access, full 32-bit network redirectors, and VCACHE.386 file cache, shared between them. Windows for Workgroups 3.11, (originally codenamed Snowball) was released on August 11, 1993, and shipped in November 1993, by Microsoft.
0 kommentar(er)
