jmcdev1
October 25th, 2006, 07:48 PM
Just bought ATI 9.0 to use with my Dell Inspiron 8600 laptop with 60GB internal HD, Win XP Home, with a SimpleTech 120GB USB External HD attached and only used for backups, not turned on all the time. I am confused and would like to ask for guidance. My wife gave me some (I told you not to buy that!) but not what I needed. She's usually right, of course. :) I trust you will prove her wrong.
I did a backup of entire disk C:/ to the external HD while in Windows OS, with validation immed. afterwards. How do you know if the validation was good? It just says the "Operation succeeded", no details that everything was good. Log shows error codes with each step of the validation.
Then tried to start the recovery, as if my internal HD had crashed: Booted from the retail ATI CD, selected full ATI, highlighted the file on the ext. HD to restore from, but ATI said it was "not an ATI archive or was corrupted file. Please select another file."
After researching the forum, I deleted the file on the Ext. HD, then booted from the ATI retail CD, and, again did a full backup of entire disk to the Ext. HD. This time, when running the restore wizard, the file is recognized as an ATI archive file in both modes, booting from Windows or booting from the ATI retail CD. Checked the option to validate the archive immediately afterwards, but I went ahead and had it verified again while still booted from the CD. Exited ATI and booted into Windows to check the Log and found that this validation process is not listed at all. No log of it. Sure would like to see it there and confirm that there were no error codes associated with it.
So, I repeated the validation in Windows. The log now shows the 3 steps of the validation process: started, pending and succeeded, but all steps have error codes listed with them as well! How do I know if the file was validated accurately? Can't find anything in the skimpy PDF manual about what the error codes signify.
So, why would ATI not recognize the .tib archive created in Windows, but have no trouble recognizing it when created while booted from the retail CD? Where can I find out what the error codes mean and if the validation is accurate and dependable?
Thanks for your kind help, folks.
Jeff
I did a backup of entire disk C:/ to the external HD while in Windows OS, with validation immed. afterwards. How do you know if the validation was good? It just says the "Operation succeeded", no details that everything was good. Log shows error codes with each step of the validation.
Then tried to start the recovery, as if my internal HD had crashed: Booted from the retail ATI CD, selected full ATI, highlighted the file on the ext. HD to restore from, but ATI said it was "not an ATI archive or was corrupted file. Please select another file."
After researching the forum, I deleted the file on the Ext. HD, then booted from the ATI retail CD, and, again did a full backup of entire disk to the Ext. HD. This time, when running the restore wizard, the file is recognized as an ATI archive file in both modes, booting from Windows or booting from the ATI retail CD. Checked the option to validate the archive immediately afterwards, but I went ahead and had it verified again while still booted from the CD. Exited ATI and booted into Windows to check the Log and found that this validation process is not listed at all. No log of it. Sure would like to see it there and confirm that there were no error codes associated with it.
So, I repeated the validation in Windows. The log now shows the 3 steps of the validation process: started, pending and succeeded, but all steps have error codes listed with them as well! How do I know if the file was validated accurately? Can't find anything in the skimpy PDF manual about what the error codes signify.
So, why would ATI not recognize the .tib archive created in Windows, but have no trouble recognizing it when created while booted from the retail CD? Where can I find out what the error codes mean and if the validation is accurate and dependable?
Thanks for your kind help, folks.
Jeff