Message-ID: <002f01c2c794$86709e90$d8dcfea9@diana>
From: "Teilhard Knight" <teilhk AT yifan DOT net>
To: <opendos AT delorie DOT com>
References: <Pine DOT LNX DOT 4 DOT 44 DOT 0301290033220 DOT 15336-100000 AT softcon DOT com>
Subject: Re: DR DOS
Date: Wed, 29 Jan 2003 04:46:20 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Reply-To: opendos AT delorie DOT com

> What do you mean it doesn't boot?
> Does it say non-system disk, replace and strike any key when ready:


Yes, that's what it says.


> 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)



Yes, of course, I made it active, otherwise, I wouldn't have any hope to
boot.



> 2. Is the operating system actually on the drive (sys c:)




Yes, it is, I checked it.



> 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.



I started with the disk blank. I have only tried to load DOS, so, I suppose
I am using the DOS MBR.




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



After I solve the issue with DOS, I plan to load other operating systems and
have Xosl, as multi-boot manager. I tried it with the broken DOS and with
WinXP, and it worked with WinXP, and not with DOS, because the operating
system wouldn't boot anyhow.


But let me stress the fact. I erased everything and I have a blank disk with
only DOS in it. Nothing else, no boot manager, no nothing.

Thank you for your feedback.

Teilhard.