On 8/2/2011 2:13 PM, Felix Miata wrote:
On 2011/08/02 13:44 (GMT+0800) george olson composed:
1. booted with a live linux cd 2. opened a terminal with ctrl-alt-f2 3. typed in the system login: root (no password) 4. went to the grub command system by typing the command "grub" 5. found the partition with the GRUB boot loader with the command find /boot/grub/stage1 6. the partition was noted as (hd0,1) - that is GRUB syntax for the first hard disk, 2nd partition 7. set the GRUB root device to the partition above by typing the command root (hd0,1) 8. installed GRUB on the MBR of the hard drive with the command setup (hd0)
So now you've set yourself to go through the same process all over again next time Windows needs reinstalling. If instead you did 'setup (hd0,1)', left the standard MBR code put there by Windows intact, and changed the active partition (one bit move) in the partition table from the Windows partition to the Linux partition, then next time Windows installation was completed you'd only need to boot something to merely move the active partition bit once again, even Windows, using its FDISK. And, you wouldn't even need to do that much if you create a chainload menu entry in Windows' boot.ini that loads the Linux partition's boot sector stored as a 512 byte file on the Windows boot partition.
Yes that is true, I will have to go through all that again if I want to load windows again. Ultimately I do not really want a dual boot system, but I want to run suse alone and for my few windows applications run them on a windows platform installed in virtualbox. I have seen that some people do that from time to time. In any case, thanks again for your help! I think I learned a lot about grub, the mbr, chainloaders, and things like that. George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org