A friend has asked this ...

I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?

David B. wrote:
I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


It could be just about anything. There are actually a sillion things
that jam up at shutdown.

Thus, the following is a simple minded answer, based on
just one root cause.

This utility, "UPHClean", is a utility created around the WinXP
era, that fixed the open hives problem and accelerated shutdown. Later
OSes, the function was incorporated into the OS.

https://www.majorgeeks.com/files/det...p_service.html

Typically on WinXP, everything would be fine, the user would
install an ATI video driver, and suddenly there was an open
registry hive at shutdown and shutdown was slower than before the
driver was installed. UPHClean could fix it.

But something network-related can get wedged too, so it's
not like UPHClean can address them all.

Paul

On Sun, 09 Jun 2019 14:08:35 -0400, Paul
wrote:

David B. wrote:
I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


It could be just about anything. There are actually a sillion things
that jam up at shutdown.

Thus, the following is a simple minded answer, based on
just one root cause.

This utility, "UPHClean", is a utility created around the WinXP
era, that fixed the open hives problem and accelerated shutdown. Later
OSes, the function was incorporated into the OS.

https://www.majorgeeks.com/files/det...p_service.html

Typically on WinXP, everything would be fine, the user would
install an ATI video driver, and suddenly there was an open
registry hive at shutdown and shutdown was slower than before the
driver was installed. UPHClean could fix it.

But something network-related can get wedged too, so it's
not like UPHClean can address them all.

Paul

My wife "pulled the plug" (shut off the power strip) on her XT machine
for a decade with no adverse result other than a black screen when she
turned it back on and the W/7 machine in my pool bar gets dumped every
time it gets turned off. I understand if I was writing to an open file
it could be corrupted but the pool bar machine is really just an MP3
player. I know some day I might have a problem but I haven't seen it
yet. It does seem shutdown closes all open programs right away and I
am not sure what it is doing during that long process afterward.

David,

it seems to take longer than it should for
the shutdown window to show up

The shutdown dialog should pop up almost instantly, but the shutdown process
itself could take a while (for instance, when trying to reach remote
resources - drives on another computer).

I've never heard of the popup dialog itself taking a long time to appear
though, and no idea (other than wild guesses) to what could be causing it.

Regards,
Rudy Wieser

On 09/06/2019 19:08, Paul wrote:
David B. wrote:
I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up.Â* I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


It could be just about anything. There are actually a sillion things
that jam up at shutdown.

Thus, the following is a simple minded answer, based on
just one root cause.

This utility, "UPHClean", is a utility created around the WinXP
era, that fixed the open hives problem and accelerated shutdown. Later
OSes, the function was incorporated into the OS.

https://www.majorgeeks.com/files/det...p_service.html


Typically on WinXP, everything would be fine, the user would
install an ATI video driver, and suddenly there was an open
registry hive at shutdown and shutdown was slower than before the
driver was installed. UPHClean could fix it.

But something network-related can get wedged too, so it's
not like UPHClean can address them all.

Â*Â* Paul

Thank you, Paul. I've passed on your message.

On 09/06/2019 20:49, wrote:
On Sun, 09 Jun 2019 14:08:35 -0400, Paul
wrote:

David B. wrote:
I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


It could be just about anything. There are actually a sillion things
that jam up at shutdown.

Thus, the following is a simple minded answer, based on
just one root cause.

This utility, "UPHClean", is a utility created around the WinXP
era, that fixed the open hives problem and accelerated shutdown. Later
OSes, the function was incorporated into the OS.

https://www.majorgeeks.com/files/det...p_service.html

Typically on WinXP, everything would be fine, the user would
install an ATI video driver, and suddenly there was an open
registry hive at shutdown and shutdown was slower than before the
driver was installed. UPHClean could fix it.

But something network-related can get wedged too, so it's
not like UPHClean can address them all.

Paul

My wife "pulled the plug" (shut off the power strip) on her XT machine
for a decade with no adverse result other than a black screen when she
turned it back on and the W/7 machine in my pool bar gets dumped every
time it gets turned off. I understand if I was writing to an open file
it could be corrupted but the pool bar machine is really just an MP3
player. I know some day I might have a problem but I haven't seen it
yet. It does seem shutdown closes all open programs right away and I
am not sure what it is doing during that long process afterward.

I've done that many times myself on my old computers. Even now I
sometimes just power off my laptop (dual boot) by hitting the
start/power button - especially if I've booted up into Linux instead of
Windows 10! ;-)

On 09/06/2019 21:47, R.Wieser wrote:
David,

it seems to take longer than it should for
the shutdown window to show up

The shutdown dialog should pop up almost instantly, but the shutdown process
itself could take a while (for instance, when trying to reach remote
resources - drives on another computer).

I've never heard of the popup dialog itself taking a long time to appear
though, and no idea (other than wild guesses) to what could be causing it.

Regards,
Rudy Wieser

Thanks, Rudy. :-)

"David B." wrote in news:qdjb2e$457$1@dont-
email.me:

I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


Kaspersky virus protection will cause this, among other delays.


--
I love a good meal! That's why I don't cook.

On 10/06/2019 18:59, KenK wrote:
"David B." wrote in news:qdjb2e$457$1@dont-
email.me:

I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


Kaspersky virus protection will cause this, among other delays.

An interesting observation.

Thanks, Ken.

On 10 Jun 2019 17:59:31 GMT, KenK wrote:

"David B." wrote in news:qdjb2e$457$1@dont-
email.me:

I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


Kaspersky virus protection will cause this, among other delays.

So will most other AVs, screwed up registries, badly
fragmented drives, ramdisks that save an image, corrupted drivers etc.
The OP looks like he's just phishing. He didn't give a single
useful detail about hardware specs or software that was running.
He must be a noob on Usenet, didn't even read the FAQ about
posting. Or replying.
IMHO
[]'s

--
Don't be evil - Google 2004
We have a new policy - Google 2012

On 10/06/2019 21:40, Shadow wrote:
On 10 Jun 2019 17:59:31 GMT, KenK wrote:

"David B." wrote in news:qdjb2e$457$1@dont-
email.me:

I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


Kaspersky virus protection will cause this, among other delays.

So will most other AVs, screwed up registries, badly
fragmented drives, ramdisks that save an image, corrupted drivers etc.
The OP looks like he's just phishing. He didn't give a single
useful detail about hardware specs or software that was running.

I simply repeated the question - EXACTLY as asked!

He must be a noob on Usenet, didn't even read the FAQ about
posting. Or replying.
IMHO
[]'s

I read them he-

http://aumha.org/support.htm

Where did *YOU* read them Shadow?

--
David B.
Devon, UK

On Mon, 10 Jun 2019 23:31:05 +0100, "David B."
wrote:

On 10/06/2019 21:40, Shadow wrote:
On 10 Jun 2019 17:59:31 GMT, KenK wrote:

"David B." wrote in news:qdjb2e$457$1@dont-
email.me:

I have an old XP laptop, and it seems to take longer than it should for
the shutdown window to show up. I get this hourglass that sits there
for a while (couple minutes) before the the shutdown window opens up.

Is it just old, or is there a way to get it to shutdown quicker?


Kaspersky virus protection will cause this, among other delays.

So will most other AVs, screwed up registries, badly
fragmented drives, ramdisks that save an image, corrupted drivers etc.
The OP looks like he's just phishing. He didn't give a single
useful detail about hardware specs or software that was running.

I simply repeated the question - EXACTLY as asked!

Obviously you're not on speaking terms with your "friend" or
you would have asked him the basics before posting.

He must be a noob on Usenet, didn't even read the FAQ about
posting. Or replying.
IMHO

I read them he-

https://web.archive.org/web/20190603181837/http://tekrider.net/pages/david-brooks-stalker.php

Useful site. A public service. Seems you were phishing after
all.... and have been on Usenet for at least 15 years (under more than
42 fake nyms) so no noob. Sorry I called you a noob.

Where did *YOU* read them Shadow?

I use common search engines if I have any questions.

I looked up cyberstalking, and found this definition:

//Cyberstalking:

Cyberstalkers often claim that they are just flaming, but newsgroup
stalking is more than just dogging someone's posts with flames. This
behavior rises to the level of Cyberstalking when someone does it
consistently over an extended period of time.

Other actions that constitute Cyberstalking include:

doing extensive research on the victim's private life and using it
to intimidate or harass

making threats of continuing online harassment

threats to cause harm to someone in "real life"

using the internet to engage in activity that is intended to cause
harm to someone in "real life"

impersonating another person in newsgroups or chat rooms

repeatedly lying about someone to the extent that meets the legal
definitions of defamation or libel//

Sound familiar?
[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012

"Shadow" wrote in message
...
Obviously you're not on speaking terms with your "friend" or
you would have asked him the basics before posting.

It doesn't matter to ponder or query
The message on the server's source location copied and pasted to this group
and the cut and pasted message reply(from this group) reposted to that
server's source's location(s) no longer exist.


....w¡ñ§±¤ñ
ms mvp windows 2007-2019

On 14/06/2019 05:44, ...w¡ñ§±¤ñ wrote:
"Shadow"Â* wrote in message
...
Obviously you're not on speaking terms with your "friend" or
you would have asked him the basics before posting.

It doesn't matter to ponder or query
The message on the server's source location copied and pasted to this
group and the cut and pasted message reply(from this group) reposted to
that server's source's location(s) no longer exist.


...w¡ñ§±¤ñ
ms mvp windows 2007-2019

As always, I posted the truth, the whole truth and nothing but the truth.

It was a fishing exercise and you took the bait, '...winston'.

Thank you. :-)

It would have been helpful if you had explained WHY the original poster
who asked the question was not given an answer on the U2U group (which
you moderate) and why the answers which she WAS given (from the folk on
the 'm.p.w.g' - relayed by "me") were removed from the private server(s).

The question was asked on the newsgroups run on a PRIVATE server, not on
the Usenet - www.dogagent.com

https://www.virustotal.com/gui/url/e...2c9c/detection

Serving IP Address
212.56.88.149

OR on www.myplugbox.com

https://www.virustotal.com/gui/url/0...108d/detection

Final URL
http://plugbox.com/
Serving IP Address
185.53.178.6
Status Code
200
Body Length
1.59 KB
Body SHA-256
33ac0ab2402dd5d78454bfda8e1ac6f5a1e25e07ee551beb87 57bc0df7c6aba7
Headers
connection: keep-alive
content-type: text/html; charset=UTF-8
date: Fri, 14 Jun 2019 09:44:44 GMT
server: nginx
transfer-encoding: chunked
vary: Accept-Encoding
x-check: 3c12dc4d54f8e22d666785b733b0052100c53444
x-language: english
x-template: tpl_CleanPeppermint23_twoclick

==

Can anyone explain why the identical newsgroups are available on
whichever of these servers is used in one's newsreader?

Oh! Yes - WHY is there a need for two sources to supply the same newsgroups?

--
David B.

On Fri, 14 Jun 2019 10:57:46 +0100, "David B."
wrote:

On 14/06/2019 05:44, ...STALKING_TARGET wrote:
"Shadow"* wrote in message
...
Obviously you're not on speaking terms with your "friend" or
you would have asked him the basics before posting.

It doesn't matter to ponder or query
The message on the server's source location copied and pasted to this
group and the cut and pasted message reply(from this group) reposted to
that server's source's location(s) no longer exist.


...STALKING_TARGET



As always, I posted the truth, the whole truth and nothing but the truth.

It was a fishing exercise and you took the bait, 'ME_FAKING_A_STALKING_TARGET_TO_EXPOSE_YOU'.

Thank you.

You are most welcome

15 years STALKING and you can't spot a FAKE ?
You have over 42 #FAKE_NYMS, for fscks sake !!!!!
I knew you were a drunk, but didn't think drunk to the point
of idiocy !!!!

CUT_NAMES_OF_STALKING_TARGETS

Remember, DAVID BROOKS, every time you STALK, the bots pick up
your "special" page, and you get more hits on Google. Not as a *good
guy*.
https://web.archive.org/web/20190603181837/http://tekrider.net/pages/david-brooks-stalker.php
or
http://tekrider.net/pages/david-brooks-stalker.php
Your psychopathic behavior will soon be known to all.
[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012