Date: Thu, 10 Jul 1997 10:22:21 +0000
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: .
To: Perry <perry AT bart DOT hn DOT pl DOT net>
Cc: opendos AT delorie DOT com
Reply-to: billc AT blackmagic DOT tait DOT co DOT nz
Message-id: <33C4B7DC.5B9B@blackmagic.tait.co.nz>
Organization: Tait Electronics NZ
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <199707091118 DOT XAA01859 AT bart DOT hn DOT pl DOT net>
Precedence: bulk

Perry wrote:
> Also using a boot manager that can boot Linux would be a definate advantage.

I'm actually working on one myself right now.

> The boot manager can pass a "parameter" to the kernal, the same way that
> Linux does allowing for different config.sys and autoexec.bat's.
> This could be implemented by having some space at the beginning of the drive
> reserved for the bootmanager by playing with the "number of reserved sectors"
> in the boot sector.  OR: boot a "bootman.sys" in the root directory,
> modification of the boot sector would therefore be minor.  This program
> should be smart enough to display a logo, popup a nice menu with various
> levels.

Errp, I don't know if I can do the above as my boot manager fits in the
unused sectors on the hardisk (the first track), so it has to be <=
16k.  This still uses up a partition slot, but effectivly no space on
the harddrive (at least for dos systems). Also, my BM scans all
available hard drives (up to 4) for partitions it thinks it can boot,
pop's up a menu of the available partitions and boots the selected one. 
This assumes the OS in question can boot from (say) d:.  I've only got
to the scanning partitions stage so far.

Bill
-- 
Leave others their otherness.