Install Windows 3.1 in DOSBox to run old 16-bit Windows. Install Windows 3.1 in DOSBox to run old 16-bit Windows games on 64-bit versions of Windows, Mac OS. Perform a new install of Windows 8.1.
Requires VirtualBox. 1) In VirtualBox, create a virtual machine and install MS-DOS 5 or later and Windows 3.1 on it. 2) Create another virtual machine and install Windows NT 4.0, 2000, XP, Vista, or 7 on it (it doesn't really matter; it just has to be a Windows OS that VirtualBox supports with guest additions). 3) On the new machine, install the VirtualBox guest additions. 4) On your local hard drive, create a folder named 'VBoxShared' (the name or location doesn't really matter). 5) For the virtual machine with guest additions installed, create a shared folder which links to this new folder you just created (C: VBoxShared). 6) Attach the Windows 3.1 virtual hard disk to the machine with the shared folder.
7) Boot the machine with the shared folder, and copy the WINDOWS directory from the Windows 3.1 VHD to the shared folder (shown as a network drive in the guest OS). 8) C: VBoxShared now contains the WINDOWS directory. 9) Open DOSBox and type. Or, you take some shortcuts, and just install Windows 3.1 directly in Dosbox.
Step by step for the installation in Dosbox' official forum (this guide has all the little steps that go into your step 1) Sorry, for shooting this down but I couldn't believe how many steps you take just to get it to work in Dosbox. My first comparison was: it's like breaking open the windows of your locked car, jump starting it, driving it through your living room window door, just to get to your phone to call a locksmith service because you forgot your keys in the house. Or, you take some shortcuts, and just install Windows 3.1 directly in Dosbox. It seems harder. Then take a closer look. It's actually simpler if you subtract the usual steps for installing Windows 3.1x (which aren't mentioned in the OPs post).
In that guide is almost no Dosbox exclusive instructions. The Dosbox approach is even easier because you can just have everything ready in a mounted folder. To install Windows 3.1x on VirtualBox you will have to jump through much more loops to install all that stuff. Sorry, for shooting this down but I couldn't believe how many steps you take just to get it to work in Dosbox. My first comparison was: it's like breaking open the windows of your locked car, jump starting it, driving it through your living room window door, just to get to your phone to call a locksmith service because you forgot your keys in the house How did you compare that to this tutorial? Oo Because the OPs guide takes a couple of insane steps that are not necessary at all to install Windows 3.1x on Dosbox. Yeah, installing Windows 3.1 in DOSBox is pretty simple.
Install Windows 3.1 In Dosbox For Mac Windows 10
If you use, you can also browse the Internet by loading a and installing in Windows (run ne2000.com 0x65 3 0x300 and winpkt 0x65 before starting Windows). Don't install MS TCP/32, that won't work with plain DOSBox - you need to create a disk image with MS-DOS for that. This here is the only report of a successful win3.1 network setup on dosbox I've found anywhere on the Internet. In my experience both ne2000 0x65 3 0x300 and winpkt 0x65 work fine, however net start returns Error 73: (null) and Windows says on bootup that the network driver could not be loaded. Display posts from previous: Sort by Page 1 of 1 19 posts.
As an file sharing search engine DownloadJoy finds windows 3.11 dosbox files matching your search criteria among the files that has been seen recently in uploading sites by our search spider. With our unique approach to crawling we index shared files withing hours after Upload. When you search for files (video, music, software, documents etc), you will always find high-quality windows 3.11 dosbox files recently uploaded on DownloadJoy or other most popular shared hosts. If search results are not what you looking for please give us feedback on where we can/or should improve. Our goal is to provide top notch user experience for our visitors.