That was the error message (or paraphrased version of the error message) that I got when I tried to restore an archive that was successfully created and has maintained its integrity up to this day.

There isn't a whole lot to mess up when imaging a hdd with True Image so why did this Hal.dll become corrupt?

Click to expand...

Please note that this problem is most likely related to the boot.ini file which has not been imaged properly. This usually happens because of the conflict with some other software (e.g. partitioning software).

In order to avoid this problem in the future I would recommend you to create images when your PC is booted from Acronis True Image Bootable Rescue CD, since there is no operating system or any other applications running in this case.

Also, if I upgrade to v.9 (from v. will I be able to browse the image for the folders I erased when I was forced to perform a fresh install after my Image didn't load?