Several weeks ago a window popped up on the screen when I booted the
computer. It informed me that information for the registry had been
recovered using a log or a file.
I presume something happened in the registry. What or how I do not
know as I don't fool around in there.
Is there anything I need to do or check? How can I be rid of the
little window from Windows with the information?
Thanks for your help.
Linda S

In news:ARbLe.93038$(E-Mail Removed),
Linda S <(E-Mail Removed)> had this to say:

My reply is at the bottom of your sent message:

> Several weeks ago a window popped up on the screen when I booted the
> computer. It informed me that information for the registry had been
> recovered using a log or a file.
> I presume something happened in the registry. What or how I do not
> know as I don't fool around in there.
> Is there anything I need to do or check? How can I be rid of the
> little window from Windows with the information?
> Thanks for your help.
> Linda S

Nope. You should be all set. If it keeps happening then post back with more
questions and a bit more detail but that's just Windows doing it's job.

Galen
--

"Chance has put in our way a most singular and whimsical problem, and
its solution is its own reward."

Sherlock Holmes

Galen wrote:
> In news:ARbLe.93038$(E-Mail Removed),
> Linda S <(E-Mail Removed)> had this to say:
>
> My reply is at the bottom of your sent message:
>
>
>>Several weeks ago a window popped up on the screen when I booted the
>>computer. It informed me that information for the registry had been
>>recovered using a log or a file.
>> I presume something happened in the registry. What or how I do not
>>know as I don't fool around in there.
>> Is there anything I need to do or check? How can I be rid of the
>>little window from Windows with the information?
>>Thanks for your help.
>>Linda S
>
>
> Nope. You should be all set. If it keeps happening then post back with more
> questions and a bit more detail but that's just Windows doing it's job.
>
> Galen
Hi,
Thanks for the reassurance.
Is there anyway to get rid of the little information window that
appears every time we turn on the computer?
Linda S

On Sat, 13 Aug 2005 14:09:35 GMT, Linda S
>Galen wrote:
>> Linda S <(E-Mail Removed)> had this to say:

>>>Several weeks ago a window popped up on the screen when I booted the
>>>computer. It informed me that information for the registry had been
>>>recovered using a log or a file.

>> You should be all set. If it keeps happening then post back with more
>> questions and a bit more detail but that's just Windows doing it's job.

> Thanks for the reassurance.
> Is there anyway to get rid of the little information window that
>appears every time we turn on the computer?

That's the trouble with reassurance.

The registry is your PC installation's nads, and the message you are
seeing is telling you that it got kicked really hard there. Wouldn't
you want to know if that was happening to you?

It's not normal for the registry to get corrupted. Even though it's
in constant use (and thus very exposed to "things going wrong"), it's
well protected by the system. For example, no process is allowed to
open the registry files as raw files, and do anything to them.

So if your registry is getting damaged "every time we turn on the
computer", that's a message you need to hear, not ignore.

As Galen says: "If it keeps happening then post back with more
questions and a bit more detail" - seconded!

On "that's just Windows doing it's job"; there are many jobs Windows
does automatically on your behalf, that maybe it shouldn't.

The equivalent of...

"Hey! Who's that dude walking off with my jacket!!"

' Oh, that guy? He often climbs through the window and takes your
stuff, I just thought that was normal - so when he asked for the keys
to the wardrobe, I helped him with that, as well as your credit card
details that he said he'd forgotten. Did I do something wrong? '

Some jobs should be done by a responsible adult :-)



>-------------------- ----- ---- --- -- - - - -
"If I'd known it was harmless, I'd have
killed it myself" (PKD)
>-------------------- ----- ---- --- -- - - - -

cquirke (MVP Windows shell/user) wrote:
> On Sat, 13 Aug 2005 14:09:35 GMT, Linda S
>
>>Galen wrote:
>>
>>>Linda S <(E-Mail Removed)> had this to say:
>
>
>>>>Several weeks ago a window popped up on the screen when I booted the
>>>>computer. It informed me that information for the registry had been
>>>>recovered using a log or a file.
>
>
>>>You should be all set. If it keeps happening then post back with more
>>>questions and a bit more detail but that's just Windows doing it's job.
>
>
>> Thanks for the reassurance.
>> Is there anyway to get rid of the little information window that
>>appears every time we turn on the computer?
>
>
> That's the trouble with reassurance.
>
> The registry is your PC installation's nads, and the message you are
> seeing is telling you that it got kicked really hard there. Wouldn't
> you want to know if that was happening to you?
>
> It's not normal for the registry to get corrupted. Even though it's
> in constant use (and thus very exposed to "things going wrong"), it's
> well protected by the system. For example, no process is allowed to
> open the registry files as raw files, and do anything to them.
>
> So if your registry is getting damaged "every time we turn on the
> computer", that's a message you need to hear, not ignore.
>
> As Galen says: "If it keeps happening then post back with more
> questions and a bit more detail" - seconded!
>
> On "that's just Windows doing it's job"; there are many jobs Windows
> does automatically on your behalf, that maybe it shouldn't.
>
> The equivalent of...
>
> "Hey! Who's that dude walking off with my jacket!!"
>
> ' Oh, that guy? He often climbs through the window and takes your
> stuff, I just thought that was normal - so when he asked for the keys
> to the wardrobe, I helped him with that, as well as your credit card
> details that he said he'd forgotten. Did I do something wrong? '
>
> Some jobs should be done by a responsible adult :-)
>
>
>
>
>>-------------------- ----- ---- --- -- - - - -
>
> "If I'd known it was harmless, I'd have
> killed it myself" (PKD)
>
>>-------------------- ----- ---- --- -- - - - -
Thanks for the heads up.]
I do not have any more details. I am not computer literate enough to
know what to look for or to run to fix a problem.
This computer, an e-machine T3065, came with Windows XP Home
installed. Large hard drive, etc. The tech that helped set it up at home
for us, took my old hard drive and installed it, too, rather than
transfer all the information or whatever is done at that stage. I had
not backed up my info to disks so he did it this way.
What else would you need to know or can you point me to some info that
I can read and, perhaps, learn how to fix this problem.
Thanks again,
Linda S

On Mon, 15 Aug 2005 13:10:30 GMT, Linda S
>cquirke (MVP Windows shell/user) wrote:
>> Linda S
>>>Galen wrote:
>>>>Linda S had this to say:

>>>>>Several weeks ago a window popped up on the screen when I booted the
>>>>>computer. It informed me that information for the registry had been
>>>>>recovered using a log or a file.

>>>>If it keeps happening then post back with more questions and
>>>>a bit more detail but that's just Windows doing it's job.

>>> Is there anyway to get rid of the little information window that
>>>appears every time we turn on the computer?

>> It's not normal for the registry to get corrupted. So if your
>> registry is getting damaged "every time we turn on the computer",
>> that's a message you need to hear, not ignore.

>Thanks for the heads up.]
> I do not have any more details. I am not computer literate enough to
>know what to look for or to run to fix a problem.

OK, let's get more on the general context.

Has the PC been reliable otherwise, aside from this problem? Or is it
prone to errors, spontaneous reboots, or lock-ups?

Do you shut down properly every time, or have you had problems that
either force you to reset or switch off, or had the system fail to
complete the shutdown process?

Do you ever have trouble switching the PC on and starting it up?

Now, for more on the problem: Does it happen on every startup, or only
sometimes? If sometimes, is there any link to anything that was done
in the previous Windows session? For example, "it only happens after
I had to reset" or "only if I was on the 'net during the last session"

> This computer, an e-machine T3065, came with Windows XP Home
>installed. Large hard drive, etc. The tech that helped set it up at home
>for us, took my old hard drive and installed it, too, rather than
>transfer all the information or whatever is done at that stage. I had
>not backed up my info to disks so he did it this way.

OK, that was quite a pragmatic approach :-)

> What else would you need to know or can you point me to some info that
>I can read and, perhaps, learn how to fix this problem.

What I'm after is whether your data and installation is at risk, to
the point that one should get this managed definitively, or whether
it's a single peculiarity in an otherwise healthy system.

Once we know it's the latter, then there's less to worry about, and we
can try this, guess that etc. in some comfort.

You can think about files in the system as rather like cells in the
body. You can lose a bunch of cells and never notice, e.g. if they
are in the middle of a big leg muscle. Or you could kill a cluster of
cells that happen to be the brain cells that handle speech, and then
you would notice very profoundly indeed.

In that sense, the regsitry is like seven or so brain cells that keep
Windows and programs breathing. And because they are often updated,
especially when shutting down, anything that goes generically wrong
(think of bad RAM, for example) in only 1 in a billion times is going
to bite those files sooner or later.

OTOH, if your registry's getting botched on every Windows startup,
that's like a life partner that stops breathing every night. Scary!



>------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
>------------ ----- ---- --- -- - - - -

cquirke (MVP Windows shell/user) wrote:
> On Mon, 15 Aug 2005 13:10:30 GMT, Linda S
>
>>cquirke (MVP Windows shell/user) wrote:
>>
>>>Linda S
>>>
>>>>Galen wrote:
>>>>
>>>>>Linda S had this to say:
>
>
>>>>>>Several weeks ago a window popped up on the screen when I booted the
>>>>>>computer. It informed me that information for the registry had been
>>>>>>recovered using a log or a file.
>
>
>>>>>If it keeps happening then post back with more questions and
>>>>>a bit more detail but that's just Windows doing it's job.
>
>
>>>>Is there anyway to get rid of the little information window that
>>>>appears every time we turn on the computer?
>
>
>>>It's not normal for the registry to get corrupted. So if your
>>>registry is getting damaged "every time we turn on the computer",
>>>that's a message you need to hear, not ignore.
>
>
>>Thanks for the heads up.]
>> I do not have any more details. I am not computer literate enough to
>>know what to look for or to run to fix a problem.
>
>
> OK, let's get more on the general context.
>
> Has the PC been reliable otherwise, aside from this problem? Or is it
> prone to errors, spontaneous reboots, or lock-ups?
Computer has been very reliable in the year that we have owned it.
>
> Do you shut down properly every time, or have you had problems that
> either force you to reset or switch off, or had the system fail to
> complete the shutdown process?
We shut down properly each time, usually in the evening. Do use the
"sleep" function during the day rather than turn it off and on. Husband
has the habit of leaving it on the 'net when he does this. Drives me
nuts. He says no problem. Guess who gets to try to find a solution to a
problem? Have had the system fail to shut down correctly once or twice.
Wait a reasonable amount of time, the light on the HD is no longer
flickering, and then shut off the power.
Have been kicked off the web several times for some reason that I
could never figure out.
>
> Do you ever have trouble switching the PC on and starting it up?
No trouble here.
>
> Now, for more on the problem: Does it happen on every startup, or only
> sometimes? If sometimes, is there any link to anything that was done
> in the previous Windows session? For example, "it only happens after
> I had to reset" or "only if I was on the 'net during the last session"
Every startup since it began happening. Over a month now, I think.
>
>
>> This computer, an e-machine T3065, came with Windows XP Home
>>installed. Large hard drive, etc. The tech that helped set it up at home
>>for us, took my old hard drive and installed it, too, rather than
>>transfer all the information or whatever is done at that stage. I had
>>not backed up my info to disks so he did it this way.
>
>
> OK, that was quite a pragmatic approach :-)
>
>
>> What else would you need to know or can you point me to some info that
>>I can read and, perhaps, learn how to fix this problem.
>
>
> What I'm after is whether your data and installation is at risk, to
> the point that one should get this managed definitively, or whether
> it's a single peculiarity in an otherwise healthy system.
>
> Once we know it's the latter, then there's less to worry about, and we
> can try this, guess that etc. in some comfort.
>
> You can think about files in the system as rather like cells in the
> body. You can lose a bunch of cells and never notice, e.g. if they
> are in the middle of a big leg muscle. Or you could kill a cluster of
> cells that happen to be the brain cells that handle speech, and then
> you would notice very profoundly indeed.
>
> In that sense, the regsitry is like seven or so brain cells that keep
> Windows and programs breathing. And because they are often updated,
> especially when shutting down, anything that goes generically wrong
> (think of bad RAM, for example) in only 1 in a billion times is going
> to bite those files sooner or later.
>
> OTOH, if your registry's getting botched on every Windows startup,
> that's like a life partner that stops breathing every night. Scary!

Definitely scary!
Does the above help any in pointing to a solution?
Thanks, Linda S
>
>
>
>
>>------------ ----- ---- --- -- - - - -
>
> The most accurate diagnostic instrument
> in medicine is the Retrospectoscope
>
>>------------ ----- ---- --- -- - - - -

On Thu, 18 Aug 2005 02:30:53 GMT, Linda S
>cquirke (MVP Windows shell/user) wrote:
>> On Mon, 15 Aug 2005 13:10:30 GMT, Linda S
>>>cquirke (MVP Windows shell/user) wrote:
>>>>Linda S
>>>>>Galen wrote:
>>>>>>Linda S had this to say:

>>>>>>>Several weeks ago a window informed me that information
>>>>>>>for the registry had been recovered using a log or a file.

>>>>>Is there anyway to get rid of the little information window that
>>>>>appears every time we turn on the computer?

>>>>It's not normal for the registry to get corrupted. So if your
>>>>registry is getting damaged "every time we turn on the computer",
>>>>that's a message you need to hear

>> Has the PC been reliable otherwise, aside from this problem? Or is it
>> prone to errors, spontaneous reboots, or lock-ups?

> Computer has been very reliable in the year that we have owned it.

OK, that's good to know. Folks' expectations do vary, so I'll have to
be tedious and confirm; no errors, spontaneous reboots, or lock-ups?

>> Do you shut down properly every time, or problems...?

> We shut down properly each time, usually in the evening. Do use the
>"sleep" function during the day rather than turn it off and on.

OK. Does that work OK, i.e. does it wake up OK, and also, does the
shutdown that ends that session work OK?

>Husband has the habit of leaving it on the 'net when he does this.
>Drives me nuts. He says no problem. Guess who gets to try to find a
>solution to a problem? Have had the system fail to shut down correctly
>once or twice. Wait a reasonable amount of time, the light on the HD
>is no longer flickering, and then shut off the power.

OK - that could be a problem. Some shutdown (and startup) pauses will
be waiting for something to happen (typically a hardware event) and
the HD will usually be off throughout this period, which can last
several minutes - especially if the thing that waits a minute is being
looped through 10 retries by some calling process.

One common scenario is for an active network connection to be broken
by suspending the system, or hibernating to disk. The process
maintains the state of RAM, HD etc. but loses the state of the
networking activity, which may time out and be disconnected from the
server side. When you "wake" the system, it's not aware the
connection no longer exists, and may wait forever for a response.

Many programs work like we would when jumping from stone to stone when
crossing a river. We expect to land on the next stone an instant
after leaving the last one - not wake up a week later, somewhere else.

So while the OS may suspend and wake just fine, YMMV when it comes to
the programs you run, or the things that you do. Accordingly, I'd
start by losing the suspend/sleep/hibernate thing for a trial period.

> Have been kicked off the web several times for some reason that I
>could never figure out.

See above?

>> Do you ever have trouble switching the PC on and starting it up?
> No trouble here.

OK, that's good. The saying is, "cold problems are mechanical, hot
problems are circuitry" and like most lightbulb sayings, it's not
always true - but quite often is.

>> Now, for more on the problem: Does it happen on every startup, or only
>> sometimes? If sometimes, is there any link to anything that was done
>> in the previous Windows session? For example, "it only happens after
>> I had to reset" or "only if I was on the 'net during the last session"

> Every startup since it began happening. Over a month now, I think.

That's nasty. I'd have guessed bad shutdowns (possibly caused by
session breakage caused by "sleep") were eating pending registry
changes, but then a simple "start Windows, immediately shutdown" test
should not show this problem - unless you have structural registry
file damage by now. I'm not sure how XP manages such problems.



>--------------- ----- ---- --- -- - - -
Dreams are stack dumps of the soul
>--------------- ----- ---- --- -- - - -

cquirke (MVP Windows shell/user) wrote:
> On Thu, 18 Aug 2005 02:30:53 GMT, Linda S
>
>>cquirke (MVP Windows shell/user) wrote:
>>
>>>On Mon, 15 Aug 2005 13:10:30 GMT, Linda S
>>>
>>>>cquirke (MVP Windows shell/user) wrote:
>>>>
>>>>>Linda S
>>>>>
>>>>>>Galen wrote:
>>>>>>
>>>>>>>Linda S had this to say:
>
>
>>>>>>>>Several weeks ago a window informed me that information
>>>>>>>>for the registry had been recovered using a log or a file.
>
>
>>>>>>Is there anyway to get rid of the little information window that
>>>>>>appears every time we turn on the computer?
>
>
>>>>>It's not normal for the registry to get corrupted. So if your
>>>>>registry is getting damaged "every time we turn on the computer",
>>>>>that's a message you need to hear
>
>
>>>Has the PC been reliable otherwise, aside from this problem? Or is it
>>>prone to errors, spontaneous reboots, or lock-ups?
>
>
>> Computer has been very reliable in the year that we have owned it.
>
>
> OK, that's good to know. Folks' expectations do vary, so I'll have to
> be tedious and confirm; no errors, spontaneous reboots, or lock-ups?
>
>
>>>Do you shut down properly every time, or problems...?
>
>
>> We shut down properly each time, usually in the evening. Do use the
>>"sleep" function during the day rather than turn it off and on.
>
>
> OK. Does that work OK, i.e. does it wake up OK, and also, does the
> shutdown that ends that session work OK?
>
Yes, the wakeup/shutdown works OK.
>
>>Husband has the habit of leaving it on the 'net when he does this.
>>Drives me nuts. He says no problem. Guess who gets to try to find a
>>solution to a problem? Have had the system fail to shut down correctly
>>once or twice. Wait a reasonable amount of time, the light on the HD
>>is no longer flickering, and then shut off the power.
>
>
> OK - that could be a problem. Some shutdown (and startup) pauses will
> be waiting for something to happen (typically a hardware event) and
> the HD will usually be off throughout this period, which can last
> several minutes - especially if the thing that waits a minute is being
> looped through 10 retries by some calling process.
>
> One common scenario is for an active network connection to be broken
> by suspending the system, or hibernating to disk. The process
> maintains the state of RAM, HD etc. but loses the state of the
> networking activity, which may time out and be disconnected from the
> server side. When you "wake" the system, it's not aware the
> connection no longer exists, and may wait forever for a response.
>
> Many programs work like we would when jumping from stone to stone when
> crossing a river. We expect to land on the next stone an instant
> after leaving the last one - not wake up a week later, somewhere else.
>
> So while the OS may suspend and wake just fine, YMMV when it comes to
> the programs you run, or the things that you do. Accordingly, I'd
> start by losing the suspend/sleep/hibernate thing for a trial period.

Thank you! Will do that for a week and see what the result is.
>
>
>> Have been kicked off the web several times for some reason that I
>>could never figure out.
>
>
> See above?
Wondered. I had been working right along, went to a new web page and
whammo-off the internet.
>
>
>>>Do you ever have trouble switching the PC on and starting it up?
>>
>> No trouble here.
>
>
> OK, that's good. The saying is, "cold problems are mechanical, hot
> problems are circuitry" and like most lightbulb sayings, it's not
> always true - but quite often is.
>
>
>>>Now, for more on the problem: Does it happen on every startup, or only
>>>sometimes?

Every start up.
If sometimes, is there any link to anything that was done
>>>in the previous Windows session? For example, "it only happens after
>>>I had to reset" or "only if I was on the 'net during the last session"

No links to anything in the previous session
>
>
>> Every startup since it began happening. Over a month now, I think.
>
>
> That's nasty. I'd have guessed bad shutdowns (possibly caused by
> session breakage caused by "sleep") were eating pending registry
> changes, but then a simple "start Windows, immediately shutdown" test
> should not show this problem - unless you have structural registry
> file damage by now. I'm not sure how XP manages such problems.
Me neither.

Thanks, Linda S
Grandkids are here, who knows what will happen now!
>
>
>
>
>>--------------- ----- ---- --- -- - - -
>
> Dreams are stack dumps of the soul
>
>>--------------- ----- ---- --- -- - - -