New
#21
It's got nothing to do with ME being "confused."
What it's got to do with is all the user posts here complaining that Win 7 system images failed them - for whatever reason.
Did they screw up and not follow exact procedures? Probably.
I already addressed the portability issue, and I just confirmed what I found when I tested this a couple years ago.
Here's how it went.
Clean system, no Win 7 generated images or backup sets.
Selected drive D: as backup destination.
Ran a backup letting Win choose (and I know what that means)
Uninstalled 2 programs, rebooted.
Ran another backup. Verified the incremental set was there (manage space/view backups)
Uninstalled 2 more programs, rebooted.
Ran another backup. Verified the incremental set was there (manage space/view backups)
Booted to recovery disk and verified 3 image sets there.
Didn't bother restoring. I know it works.
Booted back to Win 7.
Copied WindowsImageBackup folder to E:
Deleted WindowsImageBackup folder from D:
(This is basic portability, moving images around, failed HD's, etc.)
Booted to recovery disk.
ONLY THE LATEST IMAGE WAS FOUND.
That's a fail for me. Anybody can reproduce that.
I did get back to the original image - to before I uninstalled the 4 programs.
After I restored the unwanted image, and rebooted to the recovery disk.
Then it saw all image sets, though it misstated the drive letters.
I'm not going to get into the obvious weeds with this. Not my aim.
For the "common" non-business user here, who wants a simple user-named full image that can be found where ever he put it or moved it, IMO this isn't the tool.
Too much babysitting, like telling them to do a rename unless they want an incremental next time they hit the backup button.
For those needing incrementals, it might be fine, or might not be. I'm not going to test that more than I have, because I already found a deal-breaker - for me.
It's pretty slow too.