- #Dosbox windows 3.1 drivers install
- #Dosbox windows 3.1 drivers drivers
- #Dosbox windows 3.1 drivers windows 7
It all works perfectly fine apart from the in-game music. I don't know why I am getting the videos from the disc but not the music. I then went to: Advisors > Consult High Council and once again I could hear the disc spinning away and I got the videos of them speaking. This option is not available unless the Civilization II CD is in the CDROM drive. The problem was when I was in the game there was no music and when I went to: File > Pick Music, It said:
![dosbox windows 3.1 drivers dosbox windows 3.1 drivers](https://joshmccarty.com/wp-content/uploads/2013/08/media-player-canyon.png)
All was good and I had music on the main menu. I could hear the disc spinning in the drive and then saw the opening video. I then started Civilization II, keeping in mind my disc was still mounted and in the drive. I went through the setup process with no problems whatsoever. I went back into Windows 3.1, went into file manager, and started setup.exe.
#Dosbox windows 3.1 drivers drivers
I then installed drivers for sound (Soundblaster 16) and video (256 colours).Īfter that, I put my Civilization II disc into the CD-ROM and mounted it in DOSBox with the following command:
#Dosbox windows 3.1 drivers windows 7
So, on my Windows 7 laptop I launched DOSBox and installed Windows 3.1 using an external USB floppy disk drive which I mounted in DOSBox as A: DOSBox-X is cool (and intended to be used in productivity applications) but I don’t find myself using it all that often either.The other day I picked up a copy of the classic version of Civilization II on CD-ROM. Qemu, and 86Box, are general computing applications (they can run DOS, they can run Linux, they can run NeXT) and for my money (and my time) that’s preferable to an overly-specialized program such as DOSBox.Īlso DOSBox is optimized for games, I’m not a gamer. My choice of using 86Box (or VirtualBox, or qemu) instead of DOSBox is intentional.
#Dosbox windows 3.1 drivers install
I did a clean install of windows and made sure “share” was running and that InDOSPolling=TRUE was added to system.ini before running win /3 for the first time -but when I did, it was fine.īefore I added “share” windows would reboot the computer when I ran win /3 -so if that’s happening to folks on 86Box, that’s something to rule out. Of course, it’s important to follow all of the steps in order -in particular I kind of skipped “fdisk /mbr” (which was vital) and adding share (who needs it? turns out this does). This entry was posted in 80386, FreeDOS, i386, windows 3.1 by neozeed. Also Win32s doesn’t work either, but still Sim City, Excel and Word run fine!Īs a follow up, 3.11 for workgroups or not doesn’t work either. 386 needs some versioning set, and 3.0 is convinced that the memory is too fragmented or that C: is really A. I should add that Windows/386 and Windows 3.0 don’t work. Windows 3.1 and later are all picky about what DOS they run on top of and will crash/halt/exit if youre using FreeDOS or DOSBoxs DOS emulation. ISA Cirrus card for sure!īeing able to run Windows 3.1 in 386 Enhanced mode has been one of those holy grails of compatibility. This wont work because most importantly the DOS emulation that DOSBox provides will NOT run Win95 - youll need to actually install a real MS-DOS version to install and later run Windows. I had much better luck with my mutated Qemu 0.90 fork thing. I should add that VMWare player didn’t work, nor did later versions of Qemu either. Turning off virtual memory let’s FreeDos run in a Window!Įven more amazing to me BattleTech 3025 can run CGA mode in a Window too! I haven’t looked at patching/building yet. Section handling and hopefully remove the need for the InDOSPollingĪnd sure enough I was able to reproduce Windows 3.1 from the binary.
![dosbox windows 3.1 drivers dosbox windows 3.1 drivers](https://911weknow.com/wp-content/uploads/2020/09/install-windows-3-1-in-dosbox-5.png)
I will be working on improving the code, specifically the critical Implementation of the necessary patches a decade ago 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 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, 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 Kernel *** requires patches, see below for source