A likely scenario is that the active partition marking has shifted from the windows bootfile partition, presumably sda1, to a higher partition. If that happened then "fixmbr" correctly rewrites the generic code to the mbr but since that generic code essentially says "go find the active partition", booting will fail because the active partition is not correct for windows any more.
Originally Posted by ostrowlaw
Anyway, to check where the active flag is located now, put in the Suse boot dvd, boot and select to "Rescue System".
Then log in using name: root.
Then enter the command: fdisk -l (that's the letter l, not the numeral 1).
The console returns a list that has the active partition marked by an asterisk. The windows line should look a bit like this:
Note the asterisk. It marks the active partition. Where is your asterisk?
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1306 10490413+ 7 HPFS/NTFS