My system is WXP Home - SP2 (fully up to date), AVG Free anti-virus and Sygate Personal Firewall. When I upgraded my system (new motherboard, replaced 10GB Fujitsu HDD with WD 80GB HDD and added WD 80GB External HDD USB2) about 15 months ago I divided the new HDD into 5 partitions and labelled them W98SE, WXPMAIN, WXPTEST, DATA PARTN (M and XPIMAGES (N and formatted each partition FAT32 using Partition Magic. One of the first three partitions becomes drive C: and the other two are hidden according to which OS to boot into is selected from Boot Magic. The multi-booting under BM has been running without any problems since the upgrade. Recently I re-installed the Fujitsu HDD, deleted all the contents and re-formatted the entire disk FAT32. I recently purchased a boxed copy of ATI and when I found it was Build 2302 I downloaded and installed the latest Build 3677. Subsequently I successfully made full images of WXPMAIN and Drive M: onto folders on the External HDD. I then wanted to test the Restore function, but in case anything ‘went wrong’ I did not want to restore to and overwrite the main OS on WXPMAIN, but wanted to prove what can be done if a disaster strikes, rather than wait till the disaster is upon me, so I restored to the Fujitsu disk - i.e. the restored image was all that was on the disk. I then configured BM (including Options > Advanced Partition Hiding in order to boot from a partition that is NOT on the FIRST HDD) to include the OS on the Fujitsu in its menu as XPBackup, but when I selected that option on a reboot it failed to boot up and went into a cycle of starting the boot process but failing to boot into the selected option. Researching the problem led me to these threads: - One, Two and Three and from my understanding of the points discussed I deduced that my problem might be resolved if the image was restored to a disk, the layout of which ‘mimicked’ that of the disk from which the image was first made. So with the aid of PM I created ‘dummy’ small but empty partitions on the Fujitsu, one before and three after the position occupied by the restored image. Unfortunately this made no difference and BM behaved in exactly the same way i.e. recycling through the boot process. As an aside to the main problem, one annoying feature of ATI is that it insists on changing the label of the target restore partition to that of the imaged partition so that one ends up with an identically labelled partition on BOTH HDD’s. If NOT restoring to the original partition it would be useful to have the option of cancelling the change of name. Has anyone experienced similar problems to those related above and found a solution? If not are there any suggestions for testing the restore procedure WITHOUT overwriting the partition from which the image was made?