https://bugzilla.novell.com/show_bug.cgi?id=450137 User sorenson2743@amtelecom.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c14 --- Comment #14 from Erik Sorenson <sorenson2743@amtelecom.net> 2008-12-01 11:48:56 MST --- It is not clear to me if "Please be carefull if you propose your partitions next time" is directed internally, or to the OP, or to me. All I can say is that the first partition on MY (only) HDD is a FAT16 2 gig (legal size) partition (system partition in MS-speak) that contains the NT loader programs inserted by the XP install (on the first extended/logical) partition when it found MS/DOS on the first partition. Fine. The MBR points to that first (active) partition and booting selections are carried out using the boot.ini file there. Vista is NOT on my PC. I don't have it at all. Every time I install a new OS into another partition, I do so carefully, specifying that "/" as the place to put Grub's bootloader code. I do so by booting into DOS on the "C:" partition, running Bootpart.exe, which puts a new entry into boot.ini referencing a 512-byte file that gets created to bring up the Grub boot screen for that partition. I like this technique since no Grub (or Lilo in the old days) "owns" the global loader situation. It has worked well, and immediately (as this problem log shows) points up where someone's OS installation/Grub/Lilo routines have misbehaved. I use a shareware utility to save and restore the MBR on the PC, on DVD backup, etc., to handle recoveries from situtations like this. OS 11.1RC1 is not the first, let me tell you. However, I see the problem log has been changed to "resolved". Good news for other users and the next release. Oh, and excuse me if I misinterpreted your comment quoted above. Thanks a lot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.