Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
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. -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix user group http://www.blu.org - 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).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |