After several attempts to install Generic OEM XP Pro on a new Maxtor 100 GB PATA HD (NTSF) and several (Webroot) disk "wipes" in-between, I think I may have damaged the HD MBR. The OS still installs but I get two or three error warnings during installation and the OS doesn't function properly.
I orginally tried a repair install as suggested here in the forum, but was unable to find the point in the install process where I would press "R" for repair. While installing XP Pro, the first error message says something like, the OS needed to "change the MBR" with the choice to allow or abort the change. The other message says, "an unexpected error (769) occurred at line 5218 in d:\xpsprtn\base\boot\setup\setup.c." and the final error message is the same as the first if abort was selected initially.
I've tried first aborting the MBR change and on another attempt, allowing the change, either way the OS says, "processing auto configuration" when loading and eventually shows the desktop without any icons, buttons, or functions. I've had the HD up-and-running with the new OS but the aforementioned issue became too problematic.
Have I blown-up the HD MBR or MFT and if so, can I fix it cheaply? I would have thought that zeroing-out the disk and reformatting would have taken care of the issue.
Thanks for any help.
I orginally tried a repair install as suggested here in the forum, but was unable to find the point in the install process where I would press "R" for repair. While installing XP Pro, the first error message says something like, the OS needed to "change the MBR" with the choice to allow or abort the change. The other message says, "an unexpected error (769) occurred at line 5218 in d:\xpsprtn\base\boot\setup\setup.c." and the final error message is the same as the first if abort was selected initially.
I've tried first aborting the MBR change and on another attempt, allowing the change, either way the OS says, "processing auto configuration" when loading and eventually shows the desktop without any icons, buttons, or functions. I've had the HD up-and-running with the new OS but the aforementioned issue became too problematic.
Have I blown-up the HD MBR or MFT and if so, can I fix it cheaply? I would have thought that zeroing-out the disk and reformatting would have taken care of the issue.
Thanks for any help.