Allen said:
Not much surprises me about MS these days. Out of curiosity I was
responding to their pre configured nag about backing up every Sunday
and watching the DVDs pile up. I figured why not use an internal drive
when I encountered this failed procedure. Then upon reading the
countless threads I decided it was simple entertainment at best.
You know, I've made backups using their stuff, with the express purpose
of getting .vhd files (I'd sooner do that and store it on another hard
drive, than make DVDs). I have a .vhd image of my laptop, loaded in
virtual PC 2007 on this WinXP machine. That's how I can see what files
are on the laptop, without booting the laptop. By mounting that .vhd
in a Linux virtual machine, I can even see the vsscache files that Windows
is so careful to give an "access denied" message for. (They take space
on the disk, but don't seem to be conventional files. So it's not like
there is something of value in them. A checksum of one of the files,
came out to exactly "00000", meaning all the data was zeros!)
Now, I notice, my W7 backup thing is broken. It's one of the reasons
I'm monkeying around with the laptop now, trying to fix it. I thought
it might be a context menu issue, but that's not it (I used the Nirsoft
shell extension viewer thing, to disable some of them). About the only
thing that might have changed over the months, is a few "patch
Tuesdays".
Well, that's why we get these computers with the new OSes on them.
It's like getting a newspaper, for the daily puzzle page
The reason things like this break, is they're too decoupled,
and rely on the health of too many subsystems and widgets. If
a person was to write a hundred pages of assembler code, that
just copies a hard drive to a DVD or copies a hard drive to
an external hard drive, that would *never* break. In fact, I'm
willing to bet that a lot of people in this newsgroup, could
write their own backup application that would work better than the
one we're bashing right now.
For comparison, I used this utility last year, as a test of taking
a physical machine and loading it into a virtual machine. (I copied
my current WinXP machine, and tried to run it in virtual PC on the
same machine. Of course, activation would be broken, but it did
actually boot up.) This relies on the Volume Shadow Service too,
which is why it could take a copy of WinXP while it was running.
And this didn't cause me any problems. So this is very similar
to a backup in Windows 7 (a .vhd), but isn't exactly the same,
as it keeps more than one partition in the image. The .vhd
files Windows 7 makes are one partition per file.
http://technet.microsoft.com/en-us/sysinternals/ee656415
Paul