> >>MBR issue: run linux expert at the boot prompt, and when you get into the > >>install, before you start installing the packages, hit alt+f2 to switch to > >>the second console. dd if=/dev/hda of=/root/mbr bs=512 count=1 should > >>save your MBR into /root/mbr. Hit alt+f7 to go back to your install (i'm > >>assuming you are running graphical install). After all the packages have > >>been installed and before you reboot, go back into the console, and cat > >>the saved mbr into /dev/hda. > > > > > > That is great, thanks! > > So with this I can get my bootprogram in the MBR back the way it was. > > > > But now i'm puzzled: how does one get a new bootrecord in the > > bootpartition so that one can chainload to boot into FC4t1? > > > > Tino > > > If you are using GRUB from another Linux partition, boot that system, > mount the partition for FC4T1, open its /etc/grub.conf in an editor and > insert the appropriate lines from it into the /etc/grub.conf for the > system that is controlling the MBR. Alright, I see what you mean: you boot directly into the testpartition with the grub in the MBR. The corresponding lines in grub.conf can be found in the test-installation itself, so I have to copy them over into the grub.conf for the MBR. The situation I had was this: When I boot the computer, it will first execute my regular GRUB in de MBR, then it will chainload to the GRUB in the boot partition of my test installation. A fairly common situation as I have gathered. > If this isn't your case, some more explicit description may prompt > someone to provide a suitable answer. > > Hope this helps. Yes it did, thank you very much! In future I will be more explicit in my descriptions. Tino