"Hylton Conacher (ZR1HPC)" <hylton@global.co.za> writes:

Sorry for the delay but to get final closure on this topic I need to clarify the actions that need to be taken.

[snip]

So the procedure would be, when I get the Windows CD's: 1) Boot from my Windows bootdisk 2) Install the sorry assed Windows and Quicken 3) Reboot with my SuSE bootdisk 4) Login as root and issue the command:

grub-install --root-directory=/boot /dev/hda

to get my linuc and its bootloader back again

That should do it.

...

grub-install --root-directory=/boot --recheck /dev/hda

After reading both the --recheck option under both the man and info pages on grub-install, I have decided it is unnecessary for this OS reloading action.

I agree -- it looks like it is only needed if you add disks, or change the boot order in a mixed IDE/SCSI system since the last time you installed grub.

Perhaps though it would fix the GRUB bootloader to load Windows, as opposed to chainloader errors, when the Windows option is chosen.

Thoughts?

There was another thread about a dual boot system where the user moved his original C drive and experienced chainloader errors when loading Windows off of it, but as I recall you never mentioned why your Windows partition needed to be reinstalled (except that the problem occurred after multiple installs of linux to drive hda, and that booting Windows from grub gave you chainloader errors). Have you ever decided what exactly caused your windows installation to break? (Not that any reason I can imagine at the moment would change the procedure you outlined above.)