I understand that it is best not to uncheck startup items in msconfig but
even after going directly to the program that runs at startup and disabling
the "load at startup" option and then rebooting, those items still are
running at startup--what am I missing here?

I replied under you other post.
not good idea to post twice. Add comments to OP.

"Linda Williams" wrote:

> I understand that it is best not to uncheck startup items in msconfig but
> even after going directly to the program that runs at startup and disabling
> the "load at startup" option and then rebooting, those items still are
> running at startup--what am I missing here?

Use this http://www.mlin.net/StartupCPL.shtml





"Linda Williams" <LindaWilliams@discussions.microsoft.com> wrote in message
news:610805FE-7E6E-48B8-92B4-D38512894C95@microsoft.com...
>I understand that it is best not to uncheck startup items in msconfig but
> even after going directly to the program that runs at startup and
> disabling
> the "load at startup" option and then rebooting, those items still are
> running at startup--what am I missing here?

Well. maybe I didn't.

How to troubleshoot by using the System Configuration utility in Windows XP
http://support.microsoft.com/default...b;en-us;310560

How to perform a clean boot in Windows XP
http://support.microsoft.com/default...b;en-us;310353


"Dixonian69" wrote:

> I replied under you other post.
> not good idea to post twice. Add comments to OP.
>
> "Linda Williams" wrote:
>
> > I understand that it is best not to uncheck startup items in msconfig but
> > even after going directly to the program that runs at startup and disabling
> > the "load at startup" option and then rebooting, those items still are
> > running at startup--what am I missing here?

Hi Linda,

While it's best to check within a program's options, if it works to uncheck
it in msconfig then do it - no harm will come to you and your machine if you
do.

There are a myriad of places that something can be loading from. The best
thing to do is check exactly where in the startup frame of msconfig.
Shortcuts can be deleted, entries in the registry should be backed up
(exported) before removal. You may also find items that load from .ini files
and a few other locations, exactly how you remove them depends on where they
are.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org

"Linda Williams" <LindaWilliams@discussions.microsoft.com> wrote in message
news:610805FE-7E6E-48B8-92B4-D38512894C95@microsoft.com...
>I understand that it is best not to uncheck startup items in msconfig but
> even after going directly to the program that runs at startup and
> disabling
> the "load at startup" option and then rebooting, those items still are
> running at startup--what am I missing here?

sohtyel wrote:
> Use this http://www.mlin.net/StartupCPL.shtml
>
>
>
>
>
> "Linda Williams" <LindaWilliams@discussions.microsoft.com> wrote in message
> news:610805FE-7E6E-48B8-92B4-D38512894C95@microsoft.com...
>
>>I understand that it is best not to uncheck startup items in msconfig but
>>even after going directly to the program that runs at startup and
>>disabling
>>the "load at startup" option and then rebooting, those items still are
>>running at startup--what am I missing here?
>
>
>

uncheck startup items in msconfig does not stop services from running at
startup. If they are a service you might have to go into services (right
click on my computer, manage, service and applications, then services )
and then set the service to manual ( use caution: some services are
required by windows to function correctly ).

Sun, 4 Dec 2005 19:54:58 -0500 from Rick "Nutcase" Rogers
<rick@mvps.org>:
> While it's best to check within a program's options, if it works to uncheck
> it in msconfig then do it - no harm will come to you and your machine if you
> do.

Thank you!

I get so tired of seeing certain people post "don't use MSCONFIG to
make permanent change to startup -- it's a diagnostic tool." There's
a measure of truth to that, but it's not the whole story, and I think
it alarms people unnecessarily.

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com/
"If there's one thing I know, it's men. I ought to: it's
been my life work." -- Marie Dressler, in /Dinner at Eight/

Stan Brown wrote:

> Sun, 4 Dec 2005 19:54:58 -0500 from Rick "Nutcase" Rogers
> <rick@mvps.org>:

>> While it's best to check within a program's options, if it works to
>> uncheck it in msconfig then do it - no harm will come to you and
>> your machine if you do.
>
> Thank you!
>
> I get so tired of seeing certain people post "don't use MSCONFIG to
> make permanent change to startup -- it's a diagnostic tool." There's
> a measure of truth to that, but it's not the whole story, and I think
> it alarms people unnecessarily.


I'm with both of you. Although it *is* meant to be a diagnostic tool, it
also works fine for making permanent changes and I'm not aware of any real
downside to using it for that.

--
Ken Blake - Microsoft MVP Windows: Shell/User
Please reply to the newsgroup

Stan Brown wrote:

>
> I get so tired of seeing certain people post "don't use MSCONFIG to
> make permanent change to startup -- it's a diagnostic tool." There's
> a measure of truth to that, but it's not the whole story,


Actually, it *is* the whole story. Even in its first iteration in
Win98, MSConfig was designed and intended as a diagnostic tool.


> and I think
> it alarms people unnecessarily.
>


Why should a simple statement of fact, accompanied by advice on the
correct way of managing start up application, alarm anyone.


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH