Restored Image Not Bootable - How Do I Avoid This In Future?
11.7.50058 After I made a differential backup I tried making changes to my hard disk. They did not work out.
I deleted my partitions and then proceeded to restore my two partitions from the differential backup I had created a few hours before.
The OS backed up was Windows XP Pro 32 bit. The controller is a Marvell 88SE9172. Disk size is 1 TB. SATA
After restore I was presented with a boot time error message,
"Hal.dll is missing or corrupt."
After trying numerous workarounds including copying hal.dll from another drive, my only working solution was to use the original XP disc, go into recovery console, and bootcfg /rebuild
I am very unnerved by this all. I do not know if it was because of the Marvell controller, or if it was because I use Paragon GPT Loader sometimes. I do not know why Acronis failed to give me a bootable restore.
I did notice in the restore log that it said that it could not find a bios number for the hard disk. It appeared to be 0 and the Acronis program executed a bootability fix and made the bios number 128.
What does that mean?
Can anyone figure out what happened and how I can avoid its reoccurance?
TIA

- Log in to post comments