aseboreader.blogg.se - Windows 3.11 dosbox vs virtualbox

WINDOWS 3.11 DOSBOX VS VIRTUALBOX INSTALL
WINDOWS 3.11 DOSBOX VS VIRTUALBOX ARCHIVE
WINDOWS 3.11 DOSBOX VS VIRTUALBOX WINDOWS

Rest of sources (kernel, FreeCOM, format, fdisk, sys, share, edit) -īart, Tom, and others who have improved the FreeDOS kernel to where it is todayĪll the other FreeDOS developers, especially for FreeCOM, FDISK,Īnd Eric who's original research helped with the initial

Start Windows, will be in Enhanced mode if supported Source: (if you do not do this step, you must remember to do so beforeĮdit C:\WINDOWS\SYSTEM.INI (adjust based on actual installation andįind section, at bottom add line: Optional: edit AUTOEXEC.BAT to load SHARE.COM

WINDOWS 3.11 DOSBOX VS VIRTUALBOX WINDOWS

Put in first Windows floppy and run SETUPįollow prompts until complete, allow it to modify CONFIG.SYS and Optional: create a CONFIG.SYS and AUTOEXEC.BAT so not prompted with Optional: take out (disconnect virtual) floppy from drive and reboot,

WINDOWS 3.11 DOSBOX VS VIRTUALBOX INSTALL

Install system boot record and files to C: partition Install master boot record so hard drive is bootable Have available Windows 3.1 install media (*** not provided ***)Ĭreate a virtual machine (or have a compatible real computer)Įxample has a 200MB hard drive with 32MB of memory and otherwiseĬreate a primary partition, don't use FAT32, use all availableįormat the C: drive and set label as desired

WINDOWS 3.11 DOSBOX VS VIRTUALBOX 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.Kernel *** requires patches, see below for source 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.