XP64 SP1, TImage WS 9.1 b3718 eval, PATA Boot Disk on IDE0, SATA NVidia Raid0 array partitioned:- Primary - XP64 - NTFS - 20GB Logical - Vista - NTFS - 20GB Logical - Linux - EXT3 - 10GB Logical - VM - NTFS - 98GB Logical - DATA - NTFS - 303GB Logical - GAMES - FAT32 -16GB Created Rescue CD & booted from it. Created image of XP64 partition to spare partition on PATA disk and verified without problem. Rebooted to CD and restored image to original location without problem. Rebooted to disk and selected XP64 from windows boot.ini screen. OS attempts to load from XP64 partition but errors with "Windows could not start because the following file is missing or corrupt .... ntoskrnl.exe ...". Installed & booted from Recovery Manager - same problem. Booted from TI Home b3677 eval rescue CD, image restores without problem & reboots into Winows as expected! Checking the SATA disk with a partion manager after a failed restore shows the primary partion as an empty Linux partion. Attempts to fix the MBR/Boot partition with XP64 Recovery console give a "directory enumeration" error. After various combinations, I find WS b3718 will only give successfull restores when run from within Windows and also causes restore corruption with known good images (created with Home b3677) when run from CD or Recovery Manager. In contrast, Home b3677 (run from Win/CD/Recovery) is able to restore all images created with WS b3718 without problem. Anyone know why this is happening?