From:	gpt20 AT thor DOT cam DOT ac DOT uk (G.P. Tootell)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: OpenDOS to be released next week!
Date:	18 Jan 1997 13:03:57 GMT
Organization:	University of Cambridge, England
Lines:	17
Sender:	gpt20 AT hammer DOT thor DOT cam DOT ac DOT uk (G.P. Tootell)
Message-ID:	<5bqhnt$q87@lyra.csx.cam.ac.uk>
References:	<Pine DOT LNX DOT 3 DOT 93 DOT 970116163216 DOT 11272G-100000 AT 206 DOT 172 DOT 218 DOT 60>
NNTP-Posting-Host:	hammer.thor.cam.ac.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

|> Problem 1:  The boot sector loads the kernel so to boot from the opendos
|> kernel, it would have to be called something else instead of MSDOS.SYS and
|> IO.SYS.  I assume it will be DRDOS.SYS and DRIO.SYS or OPENDOS.SYS,
|> OPENIO.SYS.  However this still leaves the problem of the bootsector
|> loading the kernel.  Looks like we're going to be installing LILO or some
|> other boot manager.
|> 
|> That brings me to a question I've been wanting to ask now for quite some
|> time.  What bootloaders are out there that are better than LILO?  I hate
|> LILO because it is too simple, plain and unfriendly.  I'd prefer a WHITE
|> on BLUE menu to pop up that lists all installed OS's.  Comments?

it would be nice to replace that annoying win95 menu thing i get with all those
useless options for 'safe mode' and such with a nice menu that just said 'msdos,
linux or opendos' as you say, lilo is usable but not the nicest of options.

nik

- Raw text -