New
#421
Same here!
But v4.2 has been working extremely well for me, plus I had just paid to register it before 5.0 came out. (Doh!) Mainly because I wanted the WinPE disc rather than the Linux one. :)
I'll keep an eye on 5.0 ... someday when the time comes to migrate my Windows 7 system to a new computer, I'll probably upgrade to 5.0 Pro and take advantage of the "restore to dissimilar hardware" feature.
That is what I don't understand and concerns me. I found the verify on restore option. I am assuming this verifies that the system image restored is the same as the system image restored from. Not a bad idea. But what is concerning me is that I want the original system image verified with the original system, so I know the image is correct and the same as the original data. This is the option I can't find on v5.0, so I uninstalled it, and reinstalled v4.2 and verified the previous system image I had last stored last week with v5.0. Until I can get Macrium's response, or find the verification of the system image I am saving, I just don't feel comfortable. Like I said, this is the only function I use on Macrium so I don't know but so far v5.0 has nothing to offer me and actually looses a feature??
Thanks for responding and assisting!
Glenn
Not quite following your terminology. Again it is just my guess, but I thought that the system image is created and then I would immediately verify it confirming that the system image was the same as the system that I just imaged. This I thought meant there was no, say corruption or difference between the saved image and the actual files and structure.
Then I thought the verify on restore would restore the system image and check it against the saved system image so as to check for corruption or differences.
I could be totally wrong, but that has been my take on it. I want to know that the system image I just made is exactly the same as the original file it imaged. Thus I know that the system image is the exact same as the system that I may have to restore. I don't want to hope the system image that I just did, might or might not be the same as the system files and structure, until I need to do a restore. Then find out that it was corrupted and I can't restore the system image to my computer with such a catastrophic disaster as to require a system image restore.
Am I making any sense or am I on the wrong track?
Glenn
As I say you can verify an image well after it has been created so the original data may be completely different to the current state of the source disk so cannot be relying on checking the image against that. Similarly it cannot check against a disk that has not yet been restored. There is an autoverify option in the paid version which runs just after the backup. I have not determined whether that rechecks the image against the source disk but I suspect not.
I don't know if I am making myself clear, sorry. With 4.2 as soon as the system image is finished, still in the program(Macrium), I chose the verify system image and did it immediately, before doing anything else. This is what I can't do in v5.0. Now I believe that, what you are saying is that this procedure is not the same as the autoverify?
Glenn