From: EagleIce
The windows disk was primary master disk named hda1. It has normal dos MBR. The linux disk was secondary master. Boot is hdc1, swap is hdc2 and root is hdc3. I was switching disks originally by switching the cmos from disk to disk. When the linux was installed on the second disk it was installed as the only operating system on computer, used the full hard disk, yast2 did formatting for me., yast2 choose lilo configuration for me.
when trying to boot now lilo prints "LI" and freezes. This change occured after trying the method in the recent SLE letter "need help" Did my typing fdisk/MBR from a dos fdisk program damage hdc1? No it didn't.
Your /etc/fstab 'could' look something like this: _____________________________________________________ /dev/hdc3 / ext2 defaults 0 0 /dev/hdc2 /swap swap defaults 0 0 /dev/hdc1 /boot ext2 defaults 0 0 /dev/hda1 /mnt/windows vfat noauto,user 0 0 none /proc proc defaults 0 0 and then your cdrom & floppy or whatever _____________________________________________________ In this case your /etc/lilo.conf 'could' look something like this: _____________________________________________________ initrd=/boot/initrd boot = /dev/hda vga = normal read-only prompt # If you want a timout at the boot promt, 300 = 30 sec timeout = 300 message = /boot/message # image = /boot/vmlinuz.suse label = suse root = /dev/hdc3 initrd = /boot/initrd.suse # other = /dev/hda1 label = windows _____________________________________________________ It is quite harmless to test different variations in both fstab and lilo.conf as long as you run lilo from a terminal afterwards, it will tell you if there's something wrong in fstab. And you should of course first save a copy of the files before making any changes at all. Good luck, ei -- @~~ EagleIce ~ gnu4u@linux.nu ~~@ @~~ Running GNU/Linux & KDE ~~@