Date: Wed, 29 Jan 2003 00:38:14 -0500 (EST)
From: Travis Siegel <tsiegel AT softcon DOT com>
To: opendos AT delorie DOT com
Subject: Re: DR DOS
In-Reply-To: <00bf01c2c705$248bc9a0$d8dcfea9@diana>
Message-ID: <Pine.LNX.4.44.0301290033220.15336-100000@softcon.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: opendos AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: opendos AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

What do you mean it doesn't boot?
Does it say non-system disk, replace and strike any key when ready:
or does it say something like
command.com not found, system halted

Need to be a bit more spacific.
However, first things to check are
1. is the partition that has drdos active? (use fdisk to ensure it iis)
2. Is the operating system actually on the drive (sys c:)
3. Is the mbr loader drdos or something else? Some of the boot loaders
won't work if it isn't their mbr in place.  Depending if you're using lilo
or the drdos loader this will make a difference.

Which of ocurse brings up another question.
What method are you using to make the multi-boot work?