OldGuy said:
MRF == Macrium Reflect Free
Okay, got it.
(commonly talked about here).
I've been here quite a while. You might think MRF is a common topic. I
might think that EOL is a much more common and recent topic. Be careful
when using acronyms. It could limit the audience from which you are
attempting to cull for help.
I still remember a meeting a long time ago at work where it was mostly
listening to a manager's oration. At some point, maybe after 5 minutes,
there was a bit of snickering and he interrupted to ask why. We noted
that if it were not for the extremely select audience to which he spoke
that his speech would be meaningless. Every 3rd word was an acronym.
Even then we would sometimes have to mentally spell out an acronym to
figure out what he was talking about and that meant catching up on his
speech. We all knew the lingo but started laughing at ourselves at how
narrow is its audience: just those in the room. To others, even those
in our own industry, it would be gibberish.
MSI Live 5 updates to the latest drivers for the MB.
Live 6 is for Win 7 (maybe Vista but who cares).
Live 6 does not install on Win XP.
I found a download for Liev 5 and am going to try it out.
As I remember it nags for an option upgrade to Live 6 that always fails
so from now on I will just ignore the upgrade nag.
Does it have an option to enable or disable automatic update checking?
The nags might be part of that auto-check. You might get rid of the
nags by disabling the auto-check option; however, then it would be up to
you to decide when and if to check for updates (which has already been
belaboured upon as to why such usually frivilous updates are not
recommended).
The MB does not matter! Since I am uinsg MSI Live. MSI Live see which
MB and offers the lates drivers.
You asked US about the chipset updates, or so I thought. After reading
the jerky one-line-per-paragraph format of your original post, it looks
like you instead wanted to know how to revert to the prior version of
just the LiveUpdate program, not the drivers.
MRF does not seem to totally provide a perfect IMAGE.
It is probably 99.999% correct but i did have a few things to fix.
I did all that.
Not everything in the state of an OS is in a file. Some of it is in
memory. If you've made changes to the desktop, like icon layout, or
added toolbars to the Windows taskbar, and have not yet logged out and
back in (to write those changes into files) then they are not included
in a disk image. A memory image is not included in a disk image. Other
than guessing, I don't what were the other "few things" that were
different on an image restore.
Most seem to be registry glitches;
Applications that write to the registry are writing a memory copy of the
registry, not to the disk file copy. On startup, Windows loads the
registry into memory. Thereafter accesses to the registry are to the
memory copy. This keeps quick the access and update to the registry.
If Windows crashes or for whatever reason the memory copy of the
registry has not yet been written to the disk, and because image backup
programs save an image of the disk, they won't have any unsaved changes
in the memory copy of the registry. I don't know the algorithm used by
Microsoft as to when they sync the memory and disk copies of the
registry.
however, if you remember I said that
on first boot it would not boot, but on second boot it ask if i wanted
to try a previous working version.
The registry holds two, or more, past snapshots of the OS and hardware
configuration settings. You'll find them in the registry under:
HKEY_LOCAL_MACHINE\SYSTEM
with subkeys named
ControlSetXXX
where XXX is a number. One of those is the current config set. The
other is the last config (that worked okay in a prior Windows startup).
The CurrentControlSet key is merely a duplicate copy (pointer) to one of
the numbered ones; however, it makes it easy for the user to modify the
current config rather than have to visit the Select subkey to get the
value of the data item named Current.
In my current state, the Select subkey has:
Current = 1
LastKnownGood = 2
There are 2 same-level subkeys named:
ControlSet001
ControlSet002
So it's obvious which config set the Select key's data items are
pointing at. Because "1" is the value of Current under the Select key,
it is also to what CurrentControlSet points.
By electing to boot using the Last Known Good Configuration, you use the
config settings of a prior config set saved in the registry. When you
saved a backup image, you were running under whatever was the current
control set, not what was saved for a prior Windows configuration.
By the way, in regards to "if you remember I said", I cannot remember
what you haven't yet said. Nowhere before in this thread did you
mention Last Known Good or previous working version.
Anyway, all is well enough now. Still finding a thing here and there
to fix but it is manageble.
I don't recall such troubles when I last use MRF (I later switched to
Easeus ToDo and then back to Acronis True Image - notice that I did not
use acronyms for those). However, when I manually saved backup images,
it was my fault if I had made changes to the desktop which weren't saved
to disk by a logoff and logon so such loss of setup was my fault. I
closed all applications, even the startup programs, to make sure their
disk files were updated and static. I only ran a manual backup if I was
planning on a major change, like installing software that I might want
to later remove. Otherwise, my backups were scheduled to run at 4 AM
while I was sleeping and I don't leave any apps running other than the
the background ones (usually the startup progs).
Glad to see you recovered with only a few glitches, and that you got the
old LiveUpdate version 5; however, regarding LiveUpdate, you might have
to disable auto-update to eliminate the nags, or remove it as a startup
program and run it only when you choose to check for updates.
