This may be valuable information to someone. A horror story with a happy ending. I hope it helps. I did a full image of my HP laptop harddrive a few days ago, saved it to a Maxtor 300 GB external drive (USB). The image was a little over 30 GB. Two days later, something very bizarre occurred with my computer, not sure what, but it hosed the OS (WinXP Pro) when I powered off. It appeared to be locked up just prior to my turning off the power and I didn't know what else to do. The laptop blue screened on reboot. Thinking it was the harddrive, I called HP on my support plan. They had me reformat the drive to see if the drive was okay, and if okay, I would then restore my drive image. The format went fine. The restore didn't go so well. No luck. I got the dreaded corrupted TIB file, restore failed, image corrupted type message. I tried this forum and got completely freaked out that my chances of restoring were slim to none. Some of the suggestions included get the latest build (I was using 2273). So I downloaded the latest build - 3677. Still no joy - same corrupt archive messages. So this is what I did that was successful: 1) Installed the Maxtor 300 GB on computer #2 (a Dell desktop). 2) I went to the command prompt and copied the 30GB file from Maxtor 300GB to a Buffalo 400GB drive. It took several hours for this operation to complete. But my faith in the old DOS copy command is very high and I'm sure there is plenty of error checking to ensure a perfect copy. 3) Then I used the latest build boot CD and I did a verify and restore from the networked Buffalo drive. This entire process took about 12 hours. It worked. So I'm back in business. Some of the messages on the forum were frightening that there is so little hope, that these error messages indicate what they say (i.e., if it is says corrupt, it probably is). But something didn't make sense to me. If the backup went without error, the file should be okay, shouldn't it? This is what I expect of drive image software: 1) it is bullet-proof - no excuses 2) it does what it promises to do 3) it doesn't lead you down a wrong path. Why give an error message that is, in my case, demonstrably incorrect? I was told my archive was corrupt. It wasn't. The error message is plain, flat out wrong. How about a message like "your file may be corrupt. It could also be blah or blah or blah." Point #3 to me is inexcusable in TI and it needs to be fixed. As it stands, I could have easily blown away a good archive, lost a lot work, lost a lot of time and so on. I'm quite soured on this because Acronis got paid for their software. Yes, it did do the job it in the end, but it also didn't help me along the way and in fact, it misled me along the way and it was only through my own persistance that this story has a happy ending.