Hi, A friend of mine, that I convinced to try SuSE - in fact, we share the cost, thus my interest ;-) - complained that although he told yast to install grub on a floppy, his harddisk boot sequence is altered in such a way that windows does not longer boot. And me been his "local guru" and living at 150 Km distance, I don't have it too easy to check what is happening, nor knowing if he did something wrong. He said that something was written to his mbr and had to use windows "fdisk /mbr". At a second install trial, not even that worked (windows complained of "bad partition table"). In fact, what it happens is that if the floppy is removed, it doesn't start, but it does if he uses the grub menu. On investigation, it seems that grub modifies (clears) the "active" or "bootable" flag from partitions (his normal boot disk is disk is /dev/hdh). That behavior seems to be controlled by the "makeactive" line in "/boot/grub/menu.lst". Can that line be commented out safely? Is it proper for Yast to activate it, when the user requests "boot floppy", because he doesn't want to modify his normal boot sequence? Opinions? -- Cheers, Carlos Robinson