In article <[EMAIL PROTECTED]> you wrote:
> Thanks to all who've made suggestions. Several suggested the fix I
> think will work for me: add a Debian stanza to Corel's lilo.conf. I
> installed Debian Linux today using a boot floppy to avoid destroying
> the MBR again. So as soon as I figure out wh
Thanks to all who've made suggestions. Several suggested the fix I
think will work for me: add a Debian stanza to Corel's lilo.conf. I
installed Debian Linux today using a boot floppy to avoid destroying
the MBR again. So as soon as I figure out what to put in the
stanza, I should be ready to go.
I don't know if this will help or not, but here it is anyway..
When I first mess around with multi boot, I mucked up the MBR
as well.
One solution was to boot up the system with a DOS bootup disk,
and runt "fdisk /mbr". That will put DOS back in control however.
Use this method if you use loadlin
On 5 Feb 00, at 14:33, Lane Lester wrote:
> For several hours I've been without a system that would boot to any
> OS. My goal was to move Corel Linux's lilo from the MBR to its boot
> partition so that I could add Debian and control everything with Win
> NT's boot manager.
>
> I thought I had a p
On Sat, Feb 05, 2000 at 02:33:03PM -0500, Lane Lester wrote:
> So I bit the bullet and reinstalled Corel Linux from scratch, and at
> least now I can run both it and Win 98 again. But that leaves me once
> again under the domination of Corel Linux's lilo with no way to add
> another Linux.
Huh?
For several hours I've been without a system that would boot to any
OS. My goal was to move Corel Linux's lilo from the MBR to its boot
partition so that I could add Debian and control everything with Win
NT's boot manager.
I thought I had a procedure figured out that would work... I was
wrong. I
6 matches
Mail list logo
