Prevent applications from restarting XP

[Smilin]

Originally posted by: Sir Fredrick
I know that unattended means it won't prompt. But it doesn't necessarily mean it'll reboot your machine, either.

If the uninstallation requires a reboot to complete then an unattended installation of the same type will reboot automatically. How else will the uninstallation complete?

 

[Sir Fredrick]

Originally posted by: Smilin

Originally posted by: Sir Fredrick
I know that unattended means it won't prompt. But it doesn't necessarily mean it'll reboot your machine, either.

If the uninstallation requires a reboot to complete then an unattended installation of the same type will reboot automatically. How else will the uninstallation complete?

The documentation should have indicated that a reboot was necessary to complete. It did not.

I am not saying that I'm shocked that this happened. I was prepared for it, even though I had changed the policy to disallow reboots.

 

[Smilin]

Originally posted by: Sir Fredrick
I came here with a simple question, not to bitch or whine.

This used to be a place to come for help and advice on how to do things or prevent your computer from doing things you didn't want to. Apparently now it's a place for people to come and criticize you for wanting to do certain things.

You came here and asked your question. The answer was, "If you don't want your computer to reboot, don't do things that require it to reboot."

You didn't like the answer and got flamed a little bit for your trouble.

My last non-flaming answer for you:

There are certain installations and uninstallations that require a reboot. Services and updates often fall into this category. Some require a reboot to complete so the reboot is optional. Some require a reboot to maintain system stability so the reboot is not optional. These will always tell you beforehand about the reboot although you may not be reading the instructions well enough to notice (don't get "click next" happy). Some very poorly written apps my not tell you (although I've never seen one). You may wish to reconsider the use of these at all. In all cases it is simple common computer literacy and best practice to close all open applications before you begin.

That is my "answer". It is very simple advice. It is very sound advice. Since it is both simple and sound any bickering about it will frustrate me immensely and I'll probably say something rude. I'm not an inherently rude person by nature. I just find this thread incredibly dumb. The "unattended uninstall" thing literally made my jaw drop.

Sorry about biting your head off, but geez dude.

 

[Sir Fredrick]

I understand where you are coming from, but rebooting my PC on a regular basis is highly inconvenient.

As I have mentioned before, I tend to have a lot of things going on, and there is rarely a convenient time to reboot. Therefore, there would also rarely be a convenient time for me to install, uninstall or update an application. I'm sorry that is frustrating to you, but it is also frustrating to me. Especially when I know there are other operating systems that can go without rebooting for weeks or months even if you update, install or uninstall software on them, and since XP was designed as promoted as requiring less reboots.

I just posted because I was hoping someone had found a way to really make XP stay up until I speicifically command XP to reboot. Not until an application commands it to reboot, but until *I* command it to reboot. The answer, apparently, is no, nobody has found a way. That's fine. I was just curious.

I was not happy with the answer "If you don't want your computer to reboot, don't do things that require it to reboot." because it was not really the answer to my question; I already knew that answer, it's common sense. I was hoping to be able to get around that, however, and I don't think that desire should have earned me a flame. Especially since many things that claim to require a reboot truly do not.