Category : Utilities for DOS and Windows Machines
Archive   : DMBOOT.ZIP
Filename : README3.TXT
The easiest way to setup the dual boot option is to copy all the
files included here, except the text files, to a directory named
BOOT. The batch files included are set up to be in a directory
with that name. If you want to place them elsewhere, be sure to
modify DRBOOT.BAT and MSBOOT.BAT to reflect the different directory
name. An additional copy of all files should be kept on a floppy,
in case of future trouble. All MS-DOS files should be placed in a
directory called MSDOS, and DR-DOS files in a directory called
DRDOS. DEBUG must be patched to eliminate the DOS version check as
described in the file README2.TXT. To start setting up the dual
boot option, MS-DOS 5.0 must be the boot operating system. If you
have already installed DR-DOS, then you must boot with a bootable
MS-DOS 5.0 floppy and SYS the C: drive to return it to the MS-DOS
boot and system file condition. First, however, copy your
CONFIG.SYS and AUTOEXEC.BAT files to the DRDOS directory. If you
don't have a bootable 5.0 floppy, then you will have to run the DOS
5.0 install program. Once you have the system running MS-DOS 5.0,
you can change to the BOOT directory and make a copy of the boot
record by typing the following and pressing enter:
c:\msdos\debug < getmboot.scr
This will produce a file called MSBOOT which should be an exact
copy of the hard drive boot sector. Looking at it with a file
viewer should show "MSDOS5.0" near the start, and "Replace or press
any key when ready" near the end. This file should be copied to
the floppy containing the other dual boot files. If you just
changed back to MS-DOS, set up your CONFIG.SYS and AUTOEXEC.BAT
appropriately. A SHELL statement should be added to CONFIG.SYS to
point to the MSDOS directory, such as:
shell = c:\msdos\command.com c:\msdos /p
The BOOT and MSDOS directories should be added to your PATH
statement in AUTOEXEC.BAT. NOW copy COMMAND.COM, CONFIG.SYS and
AUTOEXEC.BAT to the MSDOS directory. Now DR-DOS 6.0 can be
installed, or if already installed, a DR-DOS boot disk (or the
install disk) can be booted. SYS C: (or the Install Program)
should be run. Now change to the BOOT directory and type, followed
by enter:
c:\msdos\debug < getdboot.scr
This will produce a file called DRBOOT which will be a copy of the
hard drive boot sector under DR-DOS. Also copy this file to the
floppy containing the other dual boot files. Now, if necessary,
set up the CONFIG.SYS and AUTOEXEC.BAT files for DR-DOS and copy
them to the DRDOS directory, if you haven't done so already. Add
a SHELL statement to CONFIG.SYS similar to that above referring to
the DRDOS directory, and add BOOT and DRDOS to your PATH. Copy
COMMAND.COM, CONFIG.SYS, and AUTOEXEC.BAT to the DRDOS directory.
Just before you are ready to try the dual boot procedure, delete
COMMAND.COM from your root directory. Now type MSBOOT, and press
enter. Wait until the message "OPERATING SYSTEM CHANGED TO MS-DOS"
appears, then press your reset button or CTRL-ALT-DELETE. With
luck, the system should boot MS-DOS. You can then try entering
DRBOOT, and after rebooting, you should be back to DR-DOS. Don't
hit reset or CTRL-ALT-DELETE too soon, since you could interrupt
the copy process and corrupt your boot sector. Typing MSBOOT runs
the batch file MSBOOT.BAT which uses the DEBUG script file
BOOTCHNG.SCR to copy the MSBOOT file to the hard drive boot area.
DRBOOT.BAT does the same for the DRBOOT file.
Should the system hang, you can always reboot with a floppy and run
the dual boot program, or SYS drive C:. If you have to boot from
the floppy, don't run any program that writes to the hard drive,
other than the dual boot program or SYS, since you could cause
major corruption if the boot sector has a problem. Now I repeat,
this is a risky procedure to set up, and backups are essential. It
is also important to keep the dual boot files on a floppy, just in
case something affects the copy operation when running the dual
boot operation.
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/