[DimViesel]

My relative (who, to save him from potential shame, shall remain nameless) attempted to install XP onto a brand new OEM Samsung SP1614N (160GB, ATA133, 8MB chache - one of, if not the best 160GB non SATA IMHO).
So? Lucky SOB right?
It should have been. Trying to get XP Pro installed onto this HD.
It should have been a piece of cake... however he may aswell have eaten the cake as being less than informed about setting up current PC hardware he downloaded Ontrack Diskmanager from Samsung's site & ran the tool installing onto this previously untouched Hard disk.
According to 'Everest@home Edition' his mobo is the MSI K7T266PRO.
Looking at the BIOS updates there is a mention of an update to rectify an issue with 160GB IBM drives but that is all.
I presume that this mobo is modern enough to cope with 160GB Hard drive volumes(?)

The issue now is that once XP has finished extracting/copying all the files for setup upon attempting to reboot Ontrack's Diskmanager MBR loaded utility interrupts the process or is outright fouling it up, causing errors in XP setup routine.
I learned that destroying all Partitions including the Primary does not clear the info in the MBR or wherever Ontrack software has written itself too.
What is really tragic?
This tool is a correction for a BIOS with an upper 32GB limit...
What is the correct way to remove these bootloaders?