1/29/2024 0 Comments Ms dos 6.22 floppy images download![]() ![]() My rule of thumb in this regard is: use a maximum of TWO IDE devices for virtual hard disks, add more via the SATA controller. So if you're trying to add more than four devices to the IDE controller, you're SOL you'll have to add a SATA controller. The rules apply now as they did then: you cannot add more than four devices per IDE controller, and DOS does not support SATA in native mode (SATA in IDE mode works VirtualBox seems to apply this mode automatically, so you can add more drives to a single SATA controller if you need to). Hit Next then Create.Ĭaveat: since this is a virtual appliance, you might be forgiven for thinking that you can just pile drive upon drive, but you need to remember that you're emulating an old APM system. It might be an idea to give the new disk an identifiable label as well, like "DriveD". Select Dynamically Allocated, and in the next screen adjust to 2.00GB or less (a reminder: DOS CANNOT handle a partition larger than 2.00GB). Click on "Create New Disk" and advance two screens. With the VM shut off, go into Settings->Storage and add another virtual hard disk (as shown). In fact, you don't even have to pop the cover on your computer! ![]() This procedure is a lot simpler than adding a new hard drive. Recovery is as simple as deleting the old broken clone and copying from the known-good spare (which I know you have!). So please, don't ask me how to rescue a DxxSpace-broken appliance, because it cannot be done. IMPORTANT caveat: Dblspace/Drvspace compression WILL NOT WORK on these appliance volumes, in fact attempting to deploy DxxSpace on a VirtualBox DOS appliance will BREAK IT. You are now ready to install applications using CDROM images instead of swapping out floppy images! You should see a new drive (drive D:) pop up. Next step is to add this line to your CONFIG.SYS:ĭEVICEHIGH=C:\DOS\OAKCDROM.SYS /D:MSCD001 Do a search for an OakCDROM floppy image, and load it like you did the DOS install images, then in your VM go to drive A: and xcopy all the files to your /DOS folder. Simplest way (the only way at this point!) is to download a CDROM driver floppy image. The next thing to do, before you do ANYTHING ELSE, is to clone the VM as it sits, use the clone for testing software before you commit the installation process to the original VM (potentially BREAKING STUFF if it goes wrong!), this way if you break a fully populated VM instead of having to rebuild and remember how you did it, you can just simply clone a spare. ![]() If the restart causes the system messages to appear on one line at the top of the screen, simply reset the VM. When the VM asks you to restart, remember to remove the disk image from the virtual drive or it'll throw a non system disk error!īy the end of it you'll have a very basic DOS environment, ready to go. It'll go through the motions to install and eventually will ask for Disk 2.ĭon't panic, here's what you do: go to Devices->Floppy Devices->Choose A Virtual Floppy Disk File and select Disk 2. Click OK and start the VM.Īs it's a DOS VM it will first look for a floppy controller from which to boot. Next add a Floppy Device (click the disk next to the new controller that just popped up) and choose the first disk in the installation images when asked. Scroll down to Line 68 (or thereabouts) and find the line that begins $_hdimage = freedos:ro" and place a hashmark (#) in front of it.ġ1.Step 4: Building the Appliance 1. Download the CD version of msdos622 from the web or use your floppies and copy/paste everything from attrib.exe to xcopy.exe to your /home/username/.dosemu/dos622 folder.ġ0. Here's how I did it after dosemu was already installed from the repositories and working, but I required a private MSDOS622:Ģ. It seems to break in SVGA mode when using the Trident drivers recommended here įinaly, how can I install my copy of MS-DOS 6.22 inside DOSEMU? I have it on original floppies (no floppy drive on my laptop), in VirtualPC floppy disk format and in folders containing the files found on each disk. I have even installed Windows 3.1 inside DOSEMU and this works well too in VGA mode. Is there some way I can force DOSEMU to request full elevation everytime I start it on the console? Pr every time I start it period? Or should I just keep using sudo? $ sudo dosemu -s <- this gets me the mouse Does starting DOSEMU with -s not elevate to the same “level” as running it with sudo? When I start DOSEMU using the -s parameter (on the console) I do not get access to my mouse. Most DOS apps look right running on the console. I am running DOSEMU on the console for the most part as this is the closest experience I can get to good old-fashioned DOS. I have got it running and it works GREAT. I have been playing (I say “playing” because I have no real business reason to be doing this) with DOSEMU and getting my vintage copy of WordPerfect 5.1 running. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |