Running Services

Printable View

April 15th, 2002, 11:18 AM
Capricorn

Running Services

Anyone tried disabling some of the Services that start automatic in XP Pro. I am told that several are not needed if you are a single user and not on a network. I thought that if I disable some of them I might not get so many Low Virtual Memory messages
April 15th, 2002, 11:29 AM
Radical Dreamer

The reason that you are getting low virtual mem messages is not because of this, its probable from one of the following.

You have virtual mem set to a fixed size rather than auto.

You have a virus.

Now, I doubt that it is a virus, its probable just the virtual mem set to a fixed size. (I have seen fresh installs have a set amount a virtual mem)
April 15th, 2002, 11:42 AM
Russ192

Agree with RadicalDreamer but if you should want to do your services <a href="http://www.blkviper.com/WinXP/servicecfg.htm" target="_blank">http://www.blkviper.com/WinXP/servicecfg.htm</a> is the place to look.
April 15th, 2002, 01:08 PM
Radical Dreamer

Forgot to mention above, but the one thing that shutting down these processes will do is speed up you os load time by a second or 2
April 16th, 2002, 12:04 PM
Capricorn

Thanks Guys. The Virtual Memory installed as 288 min 576 max, automatically when I installed XP Pro. I have tried setting it to System Managed Size, but I still got the messages. The <a href="http://www.blkviper.com/WinXP/servicecfg.htm" target="_blank">http://www.blkviper.com/WinXP/servicecfg.htm</a> Site is very helpfull though. The services I have disabled don't appear to have caused any problems, not yet anyway!
April 16th, 2002, 12:14 PM
Darren Wilson

One to definatly disable is the IMAPI service. Unless you want to use XP's CDR/W software, then this is best disabled as it can interfere with other CDR/W burning packages (mainly Nero).
April 16th, 2002, 01:48 PM
Radical Dreamer

[quote]Originally posted by Darren Wilson:
<strong>One to definatly disable is the IMAPI service. Unless you want to use XP's CDR/W software, then this is best disabled as it can interfere with other CDR/W burning packages (mainly Nero).</strong><hr></blockquote>

I have heard about this DW, but have not seen what it interferes with. What are the problems that it causes becaus I have yet to run into one
April 16th, 2002, 02:26 PM
Darren Wilson

[quote]Originally posted by Radical Dreamer:
<strong>

I have heard about this DW, but have not seen what it interferes with. What are the problems that it causes becaus I have yet to run into one</strong><hr></blockquote>

Any version prior to 5.5.7.0 (I think) will take around 45 seconds to load the Nero splash screen and then take another 20-30 seconds to actually start getting into the program. Turn the IMAPI service off and it loads instantly. Also as soon as the Burn process is started I noticed that the IMAPI service started up as well, which actually slowed the burn down by at least 2x (burning at around 22x instead of 24x)