Shutdown Settings - Is there an Easier Way?

[Guest]

Had to jump thru some convoluted hoops just to turn off start up programs and
services in order to allow XP to logoff users or shut down without contending
for time from other apps (i.e Norton) and thereby causing slow shut downs and
manual ending of programs.

Is there a GUI way to extend the time XP waits or even have XP figure out
when it is OK for it to start shutting down after all other apps have closed ?

Right now I am surprised at how weak XP is when it comes to monitotring
multi-tasked programs. Appreciate any help.

 

[Wesley Vogel]

76. Right hand side
Auto End Tasks to Enable a Proper Shutdown

http://www.kellys-korner-xp.com/xp_tweaks.htm

BTW, Norton sucks.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Not sure what "76 Right Hand Side" means ?

Problem is not just Norton (appreiate you comment) and origianlly startd
with Black Ice but need to constantly be in rocket scientist mode to use it
(good backend prduct but front end could use a lesson from Norton.) Can't
seem to run any other programs withou XP throwing a fit.

Can you be more specific ? Sounds like you have a solution.

 

[Wesley Vogel]

Click this link or paste it into the Internet Explorer Address bar.
http://www.kellys-korner-xp.com/xp_tweaks.htm

Read the instructions at the top of the page. Scroll down to 76. On the
right hand side is Auto End Tasks to Enable a Proper Shutdown - Undo, click
on Auto End Tasks to Enable a Proper Shutdown.

shutdown.reg is the file that will be downloaded.

In the registry shutdown.reg sets AutoEndTasks to 1, this ends processes
automatically instead of the system having to wait until the process ends,
and, if the process takes more time than the value of the HungAppTimeout
entry, the End Task dialog box appears, stating that the application cannot
respond to the End Task request.

The HungAppTimeout entry specifies how long the system waits for user
processes to end after the user clicks the End Task command button in Task
Manager. If this threshold is exceeded, the End Task dialog box appears,
stating that the process did not respond.

In the registry shutdown.reg also sets WaitToKillServiceTimeout to 1000
(1000 Milliseconds or 1 second). WaitToKillServiceTimeout determines how
long the system waits for services to stop after notifying the service that
the system is shutting down.

When the value of this entry expires, the system notifies the user that the
service has not stopped. The user can either force the service task to stop
or continue to wait. If the user waits, this value specifies the interval
between repeated user notices that the service has not stopped.

If all services stop before this value expires, the system shuts down; it
does not wait for this value to expire.

AutoEndTasks
http://www.microsoft.com/resources/...s/2000/server/reskit/en-us/regentry/34615.asp

HungAppTimeout
http://www.microsoft.com/resources/...s/2000/server/reskit/en-us/regentry/34625.asp

WaitToKillServiceTimeout
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/26734.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Thanks. Very detailed . As a software developer / systems engineer ou
supplied some good reading. I will give it a try... but may want to extend
the parms a bit because I still think XP is a let down. Microsoft needs to
focus on some artificial intell. to properly host other MS / non-MS programs
to truly be a general consumer OS. I fell sorry for Apple Mac users now that
IBM/Motorola outsourced the joint chip program now yielding the MAC to Intel
chipset.

But your support helps .

Would be great if the registry would truly "listen" to the "databus"
(remember that term) and tune itself (by all parms you mention) to
accomodate the average consumer. But then there is profit in $35 support
calls to spagetti code. Humor.

 

[Wesley Vogel]

IMO, XP isn't the let down, it's the poorly written programs.

XP cannot be everything to everyone.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Guess it is what side of the fence and how far into the woods one is. My
perspective is that the host OS is responsible for certifying programs and
proper technical communications with business associates to make sure things
run.

To that end XP fails.