#INSTALL WINDOWS 3.11 DOSBOX WINDOWS#
you have to restart DosBOX and starting Windows manually again.Įrror is fixed by disabling EMS in the CONF file for DOSBox. And if you change to DOS, DOSBox becomes a graphic problem. Under DosBOX 0.72 it runs very well, but there's no sound and I can't make graphics better than 640x480 and 4 Bits (16 colors). For sound, I use the standard Soundblaster 1.5 driver, works great for WAVE and MID sound. When I installed the S3 864 video driver, I can even use 1200x1600 resolution, fully functional with 16.7M colours. The graphics problem that DOSBoxRocks described, is due to the standard graphics driver. In DosBOX 0.72, Windows 3.11 runs perfectly. Yes Win3.11 works well in dosbox072, but when exe ms-dos and return on windows, its a bug and end dosbox =( When i try run run share.exe from dos 6.22- it return a error and not starts. so, it's impossible to run MS Office (5 or 6) in Win 3.11 at dosbox (0.73). It is unavailable to run applications, with needs share.exe dos service. You can mount a CD or A Floppy and windows 3.11 will detect it (AWSOME). The game work very well but I didn't tested the program. I only have 1 game for Windows 3.11 and 1 program. The only problem, like Dominus say in the guide, is that program that use share.exe will not be able to run. Windows 3.11 is working very well using Dominus Guide. I used a program emulator called FAKESHAR.EXE and I was able to run it and save my work I recently encountered the problem with Printshop Gold Edition.
#INSTALL 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.Where can I download Windows 3.11? (DOSBOX 0.74 compatible) 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.
0 kommentar(er)
