PDA

View Full Version : How do I stop NOD from starting....


notageek
September 4th, 2003, 09:37 PM
How do I stop NOD from starting with my computer? It started happening after the new update.

MegaHertz
September 4th, 2003, 11:00 PM
Just curious, but does the way you did it before no longer work?

AFAIK you just need to disable both the Kernel service and the User Interface from starting. To disable the service on NT based OSes you can go to administrative tools. In Win9x it is easiest to use a program like startup control panel. To disable the UI from loading, same procedure regardless of OS, you can use msconfig or another utility.

notageek
September 4th, 2003, 11:43 PM
Nope it don't work the same way as before. If I disable the running kernal, my NOD won't update. I'm using NOD as a back up to my McAfee VS7.

MegaHertz
September 5th, 2003, 01:10 AM
What part of NOD do you not want to start? A better description of how you had it configured before the update would be very helpful. I belive you could just start the kernel and not the UI although I have never tried it, and I am not sure that the automatic updates will work without the control center running.

notageek
September 5th, 2003, 09:13 AM
I don't use the auto update at all. I manually update everything on my computer. ;) I have it set up so nothing on NOD loads up. The only thing that loads up is the things I need to update it when it's time to update.

MegaHertz
September 5th, 2003, 03:27 PM
The way I see it you have two options then:
Since you have to have the kernel running to update then you could just leave it set to start automatically, and then disable the control center from starting at bootup then only start it when it is time to update. If you really want absolutely no part of NOD32 running you can stop the kernel service from loading by disableing it, but then you'll have to start it, start the control center, then run the update, & finally shut them all down again. Hope this is what you were looking for.

notageek
September 6th, 2003, 12:14 AM
Thanks. I think I got it fixed now.