I would like to hear your comments. -1------------------------------------------------------------------ title Windows rootnoverify (hd0,2) chainloader (hd0,0)+1 The rootnoverify should point to (hd0,0) as so far i know it tells GRUB not to verify windows partition. Currently it seems not needed by grub on desktop and laptop, but it will make problem if someone needs it. -2------------------------------------------------------------------ The other problem I can't see myself as my menu.lst on multiboot is on partition 3 and it is not updated by perl-Bootloader, but I have seen current 10.3 installation with this: title openSUSE 10.3 - 64 (boot) root (hd0,2) kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-...-part3 vga=0x31a resume=/dev/sda5 splash=silent showopts initrd /boot/initrd title openSUSE 10.3 - 64 root (hd0,2) kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-...-part6 vga=0x31a resume=/dev/sda5 splash=silent showopts initrd /boot/initrd Above is example where I have 'root (hd0,5)' but configured with YaST it inserts 'root (hd0,2)'. What is the problem? If kernel versions are not the same on installation used as home for /boot directory, and the second installation, then the second installation will have problem to boot. I found that using menu.lst changed as above when kernel versions did not match, system booted, but with lot of complains about missing modules. -3------------------------------------------------------------------ On kernel update additional entry added by perl-Bootloader is exact kernel file name. I'm not sure where this might be helpful when another entry with symlink already exist, and symlink is changed to point to the same file. It just crowds menu.lst with redundancy. -- Regards, Rajko. See http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org