pacterew.blogg.se - Setting for windows 3.11 dosbox

Setting for windows 3.11 dosbox install#
Setting for windows 3.11 dosbox zip file#
Setting for windows 3.11 dosbox archive#
Setting for windows 3.11 dosbox download#

Click the “Options” menu in the Windows Setup window and select “Change System Settings.”Ĭlick the “Display” box, scroll down to the bottom, and select “Other display (Requires disk from OEM).” In Windows 3.1, double-click the Main program folder and double-click the “Windows Setup” icon. For example, it would make sense to put these files in the “C:\dos\s3” folder.

Setting for windows 3.11 dosbox zip file#

zip file to a folder inside your DOSBox C: drive folder.

Setting for windows 3.11 dosbox download#

You can download the S3 video driver from the Classic Games website.

Setting for windows 3.11 dosbox install#

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. By default, it’s set up to emulate S3 Graphics. However, it also supports some other types of graphics. RELATED: PCs Before Windows: What Using MS-DOS Was Actually LikeĭOSBox supports standard VGA graphics. When you restart DOSBox, you can launch Windows 3.1 by running the following commands in order: When it’s done, close the DOS system by clicking “Reboot” in the wizard.

Setting for windows 3.11 dosbox archive#

If you unpack the archive to c:\dosgames\windows, you are doing it wrong because the package already contains the required directory structure and will give an error message like the one you described.Go through the Windows 3.1 setup wizard to install Windows 3.1 in DOSBox. If you unpack the archive to c:\dosgames, mount that as the C drive in DOSBox and then enter windows, the package will start correctly. Let's assume you have a c:\dosgames you are mounting as the C drive in DOSBox. But he is right that this is a likely cause.

A screenshot of the Windows directory inside thatĪnd yes, Eagle is a bit incomprehensible today.

A screenshot of the directory you are mounting as your C drive in DOSBox.

The version number of the DOSBox copy you are using.

The information about your mounts (if they are not defined in the config file).

A copy of your DOSBox configuration file (if you modified it from the default one, including any changes to the section).

If it doesn't work, then you did something wrong.Īs I said before, to actually troubleshoot your problem I need to have the following: I unpackaged everything just like in the description, but when I try to run windows.bat I get a message that says cannot find a device file that may be needed to run windows. Up to 800圆00 the color depth can be set to up to 24-bit (16,7 million colors), up to 1024x764 to 16-bit (65 thousand colors), the higher resolutions (up to the highest supported 1600x1200) only permit 8-bit color depth. If you want, you can change that under Main > Windows Setup > Options > Change System Settings > Display. * The display is set to a 640x480 resolution with 8-bit color depth (256 colors). I found it caused some issues with MIDI music in Windows games. * You might consider disabling MPU-401 emulation in DOSBox. * Dragging & Dropping the batch file over DOSBox executable probably won't work. It most likely will not work properly in older versions. * This package is meant to be used with DOSBox 0.73 and newer. * Again, do not unpack this to the root of your system drive. Unpack to the Windows directory (the one from the above package, not the one where your computer's actual operating system is installed), optionally also the game directory and see if it works. This is an experimental fix that should solve problems with games requiring a Borland DPMI server: You don't want to overwrite your copy of Windows, trust me on that.įrom now on, all it will take to run Windows 3.11 in your DOSBox is - once you mount the directory you extracted the package into - entering windows.bat from the command line.

All you have to do is unpack the thing to the location you mount as DOSBox' virtual C drive, unless that location is the root of your system drive.