quixoticphantom

Quote: Quote: Services are designed to be system-wide so it doesn't matter who logs on or if anyone is logged on, they should always load. Also IMHO, if your system is semi-decent, unloading system services won't yield much of a performence gain. I completely disagree; they always should not be loaded. It's more about security -"Champion_R". The easiest way that I've done this is with a batch file. At www.sysinternals.com -they have a great command-line tool for controlling Services called SC (for XP and Win2k). This nice tool will also pause services (not native from the command line). I have found this tool more useful on Win2k servers, but there is a place for it too on XP systems. Oops, the tools is not from www.sysinternals.com. It's a MS resources kit tool.

Quote: Services are designed to be system-wide so it doesn't matter who logs on or if anyone is logged on, they should always load. Also IMHO, if your system is semi-decent, unloading system services won't yield much of a performence gain. I completely disagree; they always should not be loaded. It's more about security -"Champion_R". The easiest way that I've done this is with a batch file. At www.sysinternals.com -they have a great command-line tool for controlling Services called SC (for XP and Win2k). This nice tool will also pause services (not native from the command line). I have found this tool more useful on Win2k servers, but there is a place for it too on XP systems.