![]() ![]() ![]() # TODO: You must specify your Win95 and Game drive names and geometries. # Drive Geometries - DOSBOX must know the drive geometry to properly install Win95 and boot it # cycles=max 80% is very fast but keeps my laptop fan from spinning wildly. # You need to set cputype=pentium_slow or Win95 thinks it's running on a 486 and won't install DirectX 8. # and can run at 1600x1200 or lower resolutions in high color modes. The S3 Trio 64 is the most modern GPU you can emulate, # 64MB is the maximum for normal DOSBox builds. # windowresolution=1600x1200 (if double the Win95 resolution, scaling this way looks fine) # output=ddraw seemed to provide the lowest GPU use with the ability to scale the output # DOSBox configuration file for Win95 on DOSBox Rather than replacing the steps in the same file, making a separate file for each different kind of boot makes it easy to go back and forth again later. This is the nf template I used for each step below. Instead, you can leave the Win95 image small and mount a second empty drive for each game that’s the right size to install the game to. I didn’t want to installing all of my games in the same Win95 image, which I could break easily, and I didn’t want a huge Win95 starting image to install each game. You have to boot from an “img” file in DOSBox to run Win95, but IMG files take up the whole drive size, not just the used space. Mount a second hard drive for each game # Instead, I copied my (trimmed) Win95 setup folder to an empty hard drive image and then mount it along with the DOS Boot Disk and target drive to start setup. The walkthroughs copy the install directory to the target hard drive, but that means the target drive must be larger. ![]() I couldn’t mount the Win95 ISO so a DOS boot disk would see it. My scripting in Step 1 below copies the correct file list. This also eliminated a few exceptions during the first boot. You can delete all of the files on the Win95C CD which aren’t on the Win95A CD to get the latest Win95 fixes, but without all of the optional software (IE, AOL, …). I saw the fewest unhandled exceptions and other problems with the last Win95 release. I’ve also packed up all of my DOSBox scripting, if you don’t want to copy and paste it from here. In addition to a Win95 CD ISO and key, you’ll need: Anyway, here are my terse, working steps for getting very nice Win95 DOSBox images. The walkthroughs online had some skippable steps and I ran into some problems, and then I got distracted optimizing it. Thus they don't really help out of context for what the screen looks like.I needed Windows to run SimTower, so I decided to try getting Win95 to run on DOSBox. I know it would probably help if I had screenshots, but every time I try to make one it only captures the colors that are off, with the rest of the in game screen being black. Running it in XP Compatibility Mode but couldn't get it to run. I think this is because Windows was automatically doing that anyway. Checking the "Run in 256 colors mode" option. It would also be great to be able to do this with any other old games I have (like Battleground Gettysburg). I know I've done it in XP before, but I can't remember what I did. I was wondering how to set it up to look better. Anyway when I play it it looks horrible.įor some reason I'm getting graphical output errors, mainly just with the FMVs, but there's also some minor ones during actual gameplay. I've downloaded and installed the first one for 64-bit (the download for 64-bit versions of Windows can be found on the installation instructions page). Recently EA released the first few Command and Conquer games for free on their website. ![]()
0 Comments
Leave a Reply. |