[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Booting Linux and DOS on a boot cd with GRUB
From: |
Felix Miata |
Subject: |
Re: Booting Linux and DOS on a boot cd with GRUB |
Date: |
Thu, 24 Jan 2008 13:53:04 -0500 |
User-agent: |
Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.1.11) Gecko/20071129 SeaMonkey/1.1.7 (PmW) |
On 2008/01/24 08:36 (GMT-0600) Weinberg, Jon apparently typed:
> I currently have an iso of Helix (uses knoppix) and I'm trying to modify
> the grub menu to add an option for booting to a DOS environment. I have
> all the DOS boot files in the iso however whenever I boot the cd, grub
> returns an "Error 15," file not found. Unfortunately it doesn't specify
> which file(s). Here's the only modification I've made to grub, and it's
> in the menu.lst file:
> I added:
> title Asset Delete & PDWipe
> root (cd)/boot/pdwipe/
> kernel (cd)/boot/pdwipe/COMMAND.COM
> chainloader (cd)/boot/pdwipe/MSDOS.SYS
> chainloader (cd)/boot/pdwipe/IO.SYS
> I'm pretty sure this is wrong, but I've not found a single resource that
> explains how to do exactly what I'm doing. I've also attached the
> menu.lst file as a whole if that helps. I greatly appreciate anyone's
> help with this.
I don't know the answer, but maybe what I do know will help you figure it out.
COMMAND.COM is equivalent to /bin/sh, a command interpreter dependent on an
already loaded kernel.
Depending on the DOS version, either IO.SYS and MSDOS.SYS together function
as a kernel, or IO.SYS functions alone as a kernel. In any event, the normal
loading order for DOS is the reverse of the order you have listed.
To see which file is not found, load those commands from a grub prompt
instead of menu.lst.
Mounting and examining an ultimatebootcd iso file might prove instructive
too. Maybe what you really want is isolinux rather than grub.
--
"In the beginning was the Word, and the Word was
with God, and the Word was God." John 1:1 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://mrmazda.no-ip.com/