Hi, first post here. This question concerns a PC system with SuSE 10 (64-bit) and Windows 2000 partitions. Windows was installed first, then SuSE with GRUB selected as the bootloader. I require the Windows partition to run work-related apps and of course a few favorite games.

The system ran fine and I was able to boot to the two operating systems as needed until last week, while I was home I allowed System Mechanic Pro 6 to defragment the Windows partition. I think that this was the first time that it had prompted me to perform system maintenance. When it completed, it restarted the system. But when the Windows boot is now selected from the GRUB menu the system goes to "chainloader (hd0,0)+1" and stops there. Selecting the SuSE Linux 10 menu choice starts Linux normally, and I can still browse the Windows NTFS partitions from there.

I am thinking that the utility changed something in the Windows boot area, but am not sufficiently familiar with the process to determine if my Windows installation can be salvaged, or if I have to wipe it and start over. It was kind of a pain to get set up with my work-related apps and I would prefer to save it, so would appreciate any pointers from the community here (beyond not letting the utility have it's way with my system again).

Thanks,
Tom

first, be sure you have a way of getting back into Linux......If you do not have a "live CD" for Linux: From the Linux installation, put GRUB on a floppy.

Boot up from your Windows CD--rescue mode, and run "fixmbr" at the command prompt. Then re-boot. This will tell you for sure if something has gotten glitched in the Windows install.

I am on the road for a few weeks so will try this when I get back home.

I assume that I need the live CD or GRUB floppy since the recovery console fixmbr command may/will trash my current GRUB install? At one point while flailing last week I did make a GRUB floppy from a Linux session, so I should be ready to move ahead with that.

Thanks pixellany.
:Tom