LILO

[rir at mediaone.net]

On Sun, 29 Aug 1999, Jerry Feldman wrote:

> I just installed LILO in the MBR to use as my boot manager rather than 
> System Commander. After I did this, I found that my disk types got changed 
> in the partition table.
> /dev/hda4, Linux native was made bootable.
> /dev/hda1 (WINDOZ) was changed to non-bootable, type 1c (unknown). 
> 
> The result was that I was unable to boot into Windows from LILO. I 
> corrected this by running the Linux fdisk utility. I also found that the 2 
> additional drives were set up as hidden.
> 
> I was unaware that LILO would make these changes. I would expect an MS 
> product to do this.
> 
> Once I booted successfully into Windoz, system commander reinstalled 
> itself, so I rebooted into Linux (had to use floppy), turned commander off, 
> ran /sbin/lilo, and found my partitions changed again. This is just a minor 
> annoyance,  but I was wondering if anyone else has experienced this.

I have never seen this behavior.  I've been using lilo version 21, lately.

I would suspect that System commander is quietly changing the partition
types every time you change OSes.  This is PQ's Partition Magic's behavior.

As you describe things, you are seeing changes only after SC has twiddled
things.  You don't say that you checked your partitions after
boot linux & before running lilo.

I have never used any booter but lilo (PM once) on several dual boot
machines.  I doubt lilo is your problem.

rob
rir at mediaone.net

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).