Install Windows 3.1 in DOSBox to run old 16-bit Windows games on 64-bit versions of Windows, Mac OS X, Linux, and anywhere else DOSBox runs. This is particularly useful as only 32-bit versions of Windows can run those 16-bit applications.
Windows 3.1 was actually just an application that ran on DOS, and DOSBox is an emulator designed to run DOS and DOS applications. Windows 3.1 in DOSBox is an ideal combination for running old Windows 3.1-era applications.
Install Windows 3.1
First, you’ll need to create a folder on your computer. This folder will contain the contents of the “C:” drive you’ll provide to DOSBox. Don’t use your actual C: drive on Windows for this. Make a folder like “C:\dos”, for example.
Create a folder inside the “C:\dos” folder — for example, “C:\dos\INSTALL” — and copy all the files from your Windows 3.1 floppy disks to that folder. Windows 3.1 is still under Microsoft copyright, and can’t legally be downloaded from the web, although many websites do offer it for download and Microsoft no longer offers it for sale.
You can use Windows 3.1 or Windows for Workgroups 3.11 — whichever you have available.
Next, install and launch DOSBox. At the DOS prompt, type the following command and press Enter to mount the folder you created as your C: drive in DOSBox:
mount c c:\dos
(If you named the folder somewhere else or placed it at another location, type that location instead of c:\dos.)
Switch to the C: drive by typing the following two characters and pressing Enter:
Next, enter the folder containing your Windows 3.1 installation files:
(If you named the folder something else, type that instead of install.)
Finally, launch the Windows 3.1 setup wizard:
Go through the Windows 3.1 setup wizard to install Windows 3.1 in DOSBox. When it’s done, close the DOS system by clicking “Reboot” in the wizard.
When you restart DOSBox, you can launch Windows 3.1 by running the following commands in order:
mount c c:\dos
Install Video Drivers
DOSBox supports standard VGA graphics. However, it also supports some other types of graphics. By default, it’s set up to emulate S3 Graphics. For best graphics support, you’ll want to install the S3 graphics drivers and configure Windows 3.1 to use a higher resolution and more colors.
You can download the S3 video driver from the Classic Games website. Unzip the .zip file to a folder inside your DOSBox C: drive folder. For example, it would make sense to put these files in the “C:\dos\s3” folder.
In Windows 3.1, double-click the Main program folder and double-click the “Windows Setup” icon. Click the “Options” menu in the Windows Setup window and select “Change System Settings.”
Click the “Display” box, scroll down to the bottom, and select “Other display (Requires disk from OEM).”
Type the path to the S3 drivers. For example, if you unzipped them to the C:\dos\s3 folder, you’d type “C:\S3” here.
Choose your preferred resolution and colors. We recommend choosing 800×600 with 256 colors. This is the highest resolution and number of colors many games will support.
Click OK several times. Windows will install the drivers and you’ll be prompted to restart it. After you do, you’ll see your new graphical settings in effect.
If Windows won’t work properly after you select a display mode, run the following command after using the “cd windows” command to enter the Windows directory:
You’ll then be able to select a different video mode.
Install Sound Drivers
There’s one more driver issue to take care of. Windows 3.1 doesn’t include sound drivers that will work completely with the SoundBlaster sound hardware DOSBox is emulating. You’ll want to install those, too.
As with the S3 video driver, you can download the Sound Blaster 16 Creative Audio Driver from the Classic Games website. Unzip the downloaded archive into a folder like c:\dos\sb
Exit Windows 3.1 by clicking “File” and selecting “Exit Windows” if it’s open in DOSBox. Run the following commands to launch the Sound Blaster 16 driver installer, assuming you unzipped the folder to c:\dos\sb
Press Enter to install the drivers, select Full Installation, and press Enter again. By default, you’ll see the line: “Microsoft Windows 3.1 path : None”.
Select “Microsoft Windows 3.1 path” with the arrow keys and press Enter.
Enter the default path, which is C:\WINDOWS, and press Enter. Press Enter again to continue.
On the next screen, select the “Interrupt setting: 5” value and press Enter. It’s set to 5 by default, but DOSBox’s default is 7.
Select “7” for the Interrupt Setting and press Enter. You can then press Enter to continue. Allow the installation process to finish and “reboot” your DOS system by closing DOSBox and reopening it.
Launch Windows 3.1 again and you’ll have full sound support, including support for MIDI audio. You should hear a sound as soon as you launch Windows 3.1 again.
Install and Run Games and Other Applications
To actually use an application, download it (or copy it from old disks) and place it in a folder inside your c:\dos folder. For example, you might want to place it in c:\dos\gamename.
You can then create a shortcut to the game’s .exe file by clicking File > New and browsing to its .exe file. Double-click that shortcut to launch the game.
The game should just work, launching within the DOSBox window as if it were running on Windows 3.1 — after all, it is.
You don’t have to go through this entire setup process again in the future, either. Just take that c:\dos folder — or whatever else you named it — and back it up. Move it to another computer and you can use it after installing DOSBox. Because we haven’t configured DOSBox at all and have just used its default settings, you won’t even have to tweak your DOSBox settings before it will work.
- › How to Easily Play Classic DOS Games on Your Mac with Boxer
- › How to Fix Windows and Linux Showing Different Times When Dual Booting
- › How to Install Windows 3.1 on an iPad
- › How to Install Windows 95 in a Virtual Machine
- › Why You Should Always Install 64-bit Windows
- › Windows 3.0 Is 30 Years Old: Here’s What Made It Special
- › Apple Hates Fun, Says No More Windows 3.1 on iPads
- › Remembering VRML: The Metaverse of 1995