Win XP issue RE: Tweaks thread
Enverex
Worcester, UK Icrontian
Spinner wrote:Open up the Windows Registry Editor by clicking Start -> Run and type regedit and press enter. Now locate HKEY_CURRENT_USER\Control Panel\Desktop\ - Once you've located this area find the value HungAppTimeout set to 5000 if it isn't already. Next up locate WaitToKillAppTimeout which is in the same folder and set it to 4000 from the default of 20000 - This is one of the key elements of decreasing the time it takes to shut down.
Finally for this tweak to work locate the following HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ and look for an option called WaitToKillServiceTimeout and change this to 4000.
Watch how quickly Windows XP shuts down for you now!
That is a REALLY bad idea unless you like losing work.
If you have word open or something and didn't notice that you hadn't saved, or you have some other program open that asks you something, you have 4 seconds to save and exit, otherwise the programs are killed and you lose anything that is open. Which is why it is set to 20 seconds, if there is anything open, there is enough time for it to ask you what to do and do it...
0
This discussion has been closed.
Comments
The same rules of shutdown apply when this tweak is performed, it just lowers the preset waiting value, if you have an unsaved document open, say in word, it will still prompt you to save it before it shuts down, it doesn't just close your document without saving, it will wait until you save it. I use this tweak on all my machines and all the machines I build, and I have never experienced any problems with it.
There is however a tweak that is sometimes included in transripts of the above quoted tweak that does in fact remove the function that prompts to save, but the tweak quoted above, on its own is harmless, at least in my experience.
You can delete these few posts laster or move them if you want.
The reason it isn't causing you any problems is because recently Microsoft changed their Office software so that it will actually halt the Shutdown proceedure completely then tell you programs are still open. Though if you have non-MS software open, then you don't get that liberty and the 4 second till-kill applies.
Okay, fair point, but you did specifically mention Word. Eitherway, is this problem really to be blamed on the tweak itself, or is the software that doesn't force a save prompt.
Thanks for pointing this out however.
The problem cannot be blamed on anything other than the tweak itself, as other programs DO display a message, but then get killed by Windows, hint why there is a Close and a KILL time-out. Microsoft software stops it because they know how to avoid everything in their own OS, but you won't see it with anything else.
The 2 timers are there for a reason, firstly, to allow programs to shutdown properly, and secondly, to allow for user inputting so save and such (the close is basically the same as hitting the X and getting the save and such messages). A Program takes so much time to shut down, what this is essentially doing is if the program doesn't close in X amount of time, it is removed and everything it was still doing gets lost. Basically, it's like saying "Windows, you have 4 seconds to shut down, if you don't, I'm hitting the power button". Not the best idea in the world. The only time it would ever be useful is if a program has hung, but that is the ONLY time it is useful, it is potentially dangerous to all other still-running software.
I also use the tweak on all my computers and I haven't lost any work because of it.
Next time you are using a non-office program, forget to save, and then lose it all because the program is killed, don't come crying to me.
I am just trying to point out the obvious issues with this "tweak". No need for "well just" comments.
Go ahead, delete the damn thread.
1. you should have auto saved configured...
2. office programs create a temp file in which it writes all the data before a save. When you finally save it writes this temp file to the actual file...
Most times you can recover your data from these temp files...
Gobbles
Nightshade'... Enverex... whatever, mate... I for one appreciate you reporting what problems you've had with this one particular tweak. There is nothing wrong with you letting people know what experiences you've had with something, thank you for posting this information. If I myself seemed a little irritated, it was only because you originally posted this in the 'Tweaks and Tricks Thread', and I am currently trying to house keep using a 56K connection.
Please accept my apologies if I seemed a little sharp. Everyone’s points in this thread have weight, it just depends on people’s situations and habits. However at the end of the day, the more information people are exposed to, there is less chance of accidents, such as losing work etc etc will happen.
I myself haven't lost any work to this tweak, but if it were someone else less rudimentary careful, then the tweak would act as a catalyst for a situation where work could be lost.
Please carry on this discussion, but please try and see the other person’s point of view.
That's all folks.
calm yo'selves
[/OT]
I don't think it's much of a problem cause I doubt alot of people shutdown in the middle of writing something. If they do I would guess they are smart enough to save their work.
Recieved but not checked ICQ messages
Icon creation software
Audio Editing software (easy to do when you have millions of tracks open at the same time)
Graphics editing (You may have loads of pictures loaded)
Explorer may have crashed, in which case, some programs may not have re-appeared if they were minimised to the system tray.
And you are all saying that at some point, you haven't gone "Oh, no point leaving my PC on, may as well turn it off". Go to shutdown, not realising that you have things un-saved, just assuming that it is all crap open.
All I was trying to do was point out potential flaws but apparently that was a bad idea. So i'll just shut up in future.
No mate, don't shut up, like I said there is nothing wrong with what you're saying.
If anything, this thread has served to highlight that caution is required when dealing with any tweaks that change the default stance Windows has with regard to software operations and behaviour.
I think everyone has got their point across, I'll add a link to this thread in the 'Tweaks and Tricks Thread' so people can be informed.
As for this thread, I think it's served its purpose.