Hi everyone, I am a newbie with TI and have just installed TI 8.0 2 days ago. Actually, before came to TI, I have read many forums on Goback, RestoreIT, Image for Windows, and found them all having potential troubles. So I chose TI and I really love it. It ran smooth and very fast indeed. However, i still wonder if it is a real guarantee in case you need to restore back your drive? I do not have an external drive, so I created a Acronis Secure Zone and did a full backup of my C:, where I have XP SP1 and all other softwares installed. My Dell laptop has only one HDD and I devided it into 3 (C, E, and G). The Secure Zone is created from E (an extended partition using Partition Magic). on G (primary) I have another copy of my XP SP1 running on Windows multiboot. Now after successfully created the backup of C, I wanted to test if it is reliable and ran the restore manager from boot. I could do until I chose the image from Secure Zone, then it said Error, smth like "MFT Bitmap corrupted". I then clicked OK, it still went on to the next screen where I can choose wich drive i want to restore the image onto. I then stopped as did not want to get into trouble, and then came here an write this thread. My question is what is this error all about? and Why? I searched and read in this forum and learnt that maybe because I am running Diskeeper 9 (smart schedule) all the time, so after the creation of the image, my C: has changed, and thus the error. Did i understood it correct? If so, then is the error serious? Can I go on with my restoration without any potential trouble? Or how many percent of reliability is it? I must say I really dont like TI about the issue of defragmentation and incremental backup. If it cannot do a real incremental backup, why Acronis still keep it there? and what for? as everyone must defrag the HDD sometime. OK, as I dont need incremental backup, I stop the schedule. But then the MFT bitmap error, how reliable is TI really. I just want to have some thing which I can trust that if in case I need to restore my C: back, then I can. Thanks for any help or suggestion.