During restoration, ATI will ask to select backup, ask for the partition or freespace to be used for restoration. Once these have been selected it will itself boot out of the windows envoirement to carry out restoration on the chosen partition/free space, ie the destination partition. The first action during the restore process is to wipe out all data on the destination partition. After the partition is restored it will then reboot back into windows with the restored partition.

My problem is that the selection of the backup and the restoration partition/free space it comes up with the message that there is insuffcient space in the destination partition/free space. The process hangs up at that point. The only option left is to abandon the restore process. That is, close down ATI.

It is important to understand the logic of the AIT restoration process.

I have tried booting from the rescue cd with the same outcome. It's not a case of slow deletion. The process hangs up just prior to the deletion phase and indicates the destination partition/free space has insufficient room for restoration to proceed. My feeling is the problem has its roots in the image file. Strangely the image file came be mounted allowing individual files to be copied.

Dear A+ You are full of wild suppositions including perhaps your belief in a seemingly unbounded comprehension of Acronis systems. Let me put it simply. Mine is an experimental system which uses differently configured apps and OS's. I restore the relevent backup when neccessary. Your assumption the hd is failing is just that, an assumption. I can restore all images of various configurations that were made with Easeus' Todo system on the same partition. They restore without a hitch and run smoothly.

Dear Lord Nomi.- I will try your excellent suggestion tomorrow and get back to you after that. It's late where I am and need to sleep.

With thanks.

I have tried restoration on an:-- 1) Erased OS partition-- 2) Formatted OS partition-- 3) --An empty partition on another disk. All attempts failed in the same way I described initially.

To me the results point to a subtly corrupted/changed .tib image file especially as restoration in all above scenarios go through perfectly when using the Todo system and associated .PBD image files.

Tried everything you suggested but the problem remains even though the file validates ok.

I have carried out all checks you have put forward and come up with the same negative result. I am now convinced that unless the tib file can be fixed restoration from it will be impossible.

In your experience is it possible to carry out such a fix or use a workaround? I will catch up with your answer on monday as I am out of town tomorrow.

Thanks

Thanks for your comments. I am a little disappointed with the outcome. I was trying to avoid reinstallation of the OS, applications and massive transfer of data. Acronis support is a waste of time. By the way who is The A+ PCTech; are you working as a team?

It is a difficult problem that does not seem to have a quick fix. I am told that mine is not a unique incident. I do not now have the time to pursue the quick fix route and have to get on with a new installation of OS, apps and data transfer from mounted disks. Though not happy with the situation, I do thank you for your patient and logical approach.