Msconfig selective start and registry to remove programs

[Chad Harris]

A friend says that his OEM builder is adamant that when you want to remove a program that is using resources "in the notification area" from your box that you should use msconfig selective startup, delete the program from the registry, and then run normal startup from msconfig and that you should never run with msconfig in selective startup.

I told him that there were ways to remove programs from the notirication area in the first place, that just because they are in the notification area isn't indicative they will particularly use much in the way of resources. Many programs run in Task Manager's processes "in the background of course, and use considerably more resources and some programs can be exited or unloaded and they are no longer taking resources or showing in the notification area--besides, it's not necessary to uninstall many programs to keep them from starting or running. You could want to do something novel like use the program again.

I said that trying to just delete selective registry keys can incompletely uninstall or cause other problems, and that many programs have multiple files including .dlls and other extensions in multiple folders that might be missed by trying to go surgically to the registry.

Additionally, some programs have multiple areas of start-up as high as a dozen, according to Ed Bott's XP Inside Out.

Finally he said the OEM says you should never run with msconfig in Selective Startup Mode. I wanted to see if I could get some response to these opinions on selective start in msconfig (I understand the troubleshooting capacity) and using the registry to remove programs.

Thanks,

Chad Harris

 

[David Candy]

If the program doesn't do anything it will eventually use no memory whatsoever, cause it will get swapped out to the page file.. Your friend is taking a shortcut and is incorrect.

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

A friend says that his OEM builder is adamant that when you want to remove a program that is using resources "in the notification area" from your box that you should use msconfig selective startup, delete the program from the registry, and then run normal startup from msconfig and that you should never run with msconfig in selective startup.

I told him that there were ways to remove programs from the notirication area in the first place, that just because they are in the notification area isn't indicative they will particularly use much in the way of resources. Many programs run in Task Manager's processes "in the background of course, and use considerably more resources and some programs can be exited or unloaded and they are no longer taking resources or showing in the notification area--besides, it's not necessary to uninstall many programs to keep them from starting or running. You could want to do something novel like use the program again.

I said that trying to just delete selective registry keys can incompletely uninstall or cause other problems, and that many programs have multiple files including .dlls and other extensions in multiple folders that might be missed by trying to go surgically to the registry.

Additionally, some programs have multiple areas of start-up as high as a dozen, according to Ed Bott's XP Inside Out.

Finally he said the OEM says you should never run with msconfig in Selective Startup Mode. I wanted to see if I could get some response to these opinions on selective start in msconfig (I understand the troubleshooting capacity) and using the registry to remove programs.

Thanks,

Chad Harris

 

[Mike]

If you want to remove programs in startup, it is best to go to each individual program and see if there is a checkbox that will enable removal of the 'start at Windows startup' function..

A friend says that his OEM builder is adamant that when you want to remove a program that is using resources "in the notification area" from your box that you should use msconfig selective startup, delete the program from the registry, and then run normal startup from msconfig and that you should never run with msconfig in selective startup.

I told him that there were ways to remove programs from the notirication area in the first place, that just because they are in the notification area isn't indicative they will particularly use much in the way of resources. Many programs run in Task Manager's processes "in the background of course, and use considerably more resources and some programs can be exited or unloaded and they are no longer taking resources or showing in the notification area--besides, it's not necessary to uninstall many programs to keep them from starting or running. You could want to do something novel like use the program again.

I said that trying to just delete selective registry keys can incompletely uninstall or cause other problems, and that many programs have multiple files including .dlls and other extensions in multiple folders that might be missed by trying to go surgically to the registry.

Additionally, some programs have multiple areas of start-up as high as a dozen, according to Ed Bott's XP Inside Out.

Finally he said the OEM says you should never run with msconfig in Selective Startup Mode. I wanted to see if I could get some response to these opinions on selective start in msconfig (I understand the troubleshooting capacity) and using the registry to remove programs.

Thanks,

Chad Harris

 

[Wesley Vogel]

Mike is correct. That is the *best* way. However some programs do not have
that option.

InCD is an example. Why should InCD be running all the time when I only
burn a CD about every 2 to 3 weeks. It has no option to disable the
startup, I had to delete the entry from HKLM...CurrentVersion\Run. I also
had to create a shortcut to start it when I want.

Msconfig should not be used as a Startup Manager. It should just be used
for troublshooting. Too many people post with advice about using msconfig
to disable startups. *Not* a good deal. You can use it to locate where
something's starting from and then disable it from there, if there are no
other options.

StartMan is a GOOD Utility, I use it all the time, especially after
installing software. Everything you install wants to run at startup.
StartMan shows where something starts from. Check out the Help in StartMan
also! You can either have StartMan disable startups or just use it to find
where something is loading from. Running StartMan is quicker than manually
searching the registry.

[[StartMan is an extended 'msconfig' Startup Manager, designed to take
control of all those pesky programs and background services that load and
run at logon - most of which you probably don't need. As well as providing
the usual trouble-shooting options to enable or disable startups, StartMan
also permits the removal of startups.
Duplicate Detection and Removal, a unique feature of StartMan, can be
configured to remove all duplicates automatically, with or without
prompting.
Orphan Detection and Removal. As above, for orphaned startups.
Executable Detection and Removal. As above, for executables.
Includes a full range of sorting options to make it easier to locate a
specific startup - by name, by filename - even by command line parameter!]]

StartMan v1.3.96
http://www.pt.lu/comnet/desc/startman.html

===================

Removing an entry from one of these locations will only stop that program
from starting when Windows boots. It will *not* uninstall any programs.

With Windows XP Home, There are 13+ places that programs can start from and
they are executed in the following order:

Before Logon
1)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce
2) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices

After Logon
3)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup
4) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
5) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
6) WIN.INI [Windows] Load
7) WIN.INI [Windows] Run
8) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
9) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
10) C:\Documents and Settings\All Users\Start Menu\Programs\Startup
11) C:\Documents and Settings\Your Name Here\Start Menu\Programs\Startup
12) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
13) As a Scheduled Task set to run at startup.

 

[Mike]

InCD takes 1340k memory when not being used, and for those that like to use
the 'HD' facility. it may as well sit there.. I think that it is better to
install 512mb RAM or more, than to sacrifice every function in an attempt to
get XP to run well.. far too much emphasis is put on closing 'startup'
items.. it is a throwback to Win 9x, when system resources were 'hit for
six' by such things.. changing the look of XP back to 'classic' makes a huge
difference in how XP runs, far more effective than using MSCONFIG.. to each
their own..

Mike is correct. That is the *best* way. However some programs do not have
that option.

InCD is an example. Why should InCD be running all the time when I only
burn a CD about every 2 to 3 weeks. It has no option to disable the
startup, I had to delete the entry from HKLM...CurrentVersion\Run. I also
had to create a shortcut to start it when I want.

Msconfig should not be used as a Startup Manager. It should just be used
for troublshooting. Too many people post with advice about using msconfig
to disable startups. *Not* a good deal. You can use it to locate where
something's starting from and then disable it from there, if there are no
other options.

StartMan is a GOOD Utility, I use it all the time, especially after
installing software. Everything you install wants to run at startup.
StartMan shows where something starts from. Check out the Help in StartMan
also! You can either have StartMan disable startups or just use it to find
where something is loading from. Running StartMan is quicker than manually
searching the registry.

[[StartMan is an extended 'msconfig' Startup Manager, designed to take
control of all those pesky programs and background services that load and
run at logon - most of which you probably don't need. As well as providing
the usual trouble-shooting options to enable or disable startups, StartMan
also permits the removal of startups.
Duplicate Detection and Removal, a unique feature of StartMan, can be
configured to remove all duplicates automatically, with or without
prompting.
Orphan Detection and Removal. As above, for orphaned startups.
Executable Detection and Removal. As above, for executables.
Includes a full range of sorting options to make it easier to locate a
specific startup - by name, by filename - even by command line parameter!]]

StartMan v1.3.96
http://www.pt.lu/comnet/desc/startman.html

===================

Removing an entry from one of these locations will only stop that program
from starting when Windows boots. It will *not* uninstall any programs.

With Windows XP Home, There are 13+ places that programs can start from and
they are executed in the following order:

Before Logon
1)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce

2)

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices

After Logon
3)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup
4) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
5) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
6) WIN.INI [Windows] Load
7) WIN.INI [Windows] Run
8) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
9) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
10) C:\Documents and Settings\All Users\Start Menu\Programs\Startup
11) C:\Documents and Settings\Your Name Here\Start Menu\Programs\Startup
12) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
13) As a Scheduled Task set to run at startup.

--
Hope this helps. Let us know.
Wes

In

If you want to remove programs in startup, it is best to go to each
individual program and see if there is a checkbox that will enable
removal of the 'start at Windows startup' function..

A friend says that his OEM builder is adamant that when you want to
remove a program that is using resources "in the notification area"
from your box that you should use msconfig selective startup, delete
the program from the registry, and then run normal startup from
msconfig and that you should never run with msconfig in selective
startup.

I told him that there were ways to remove programs from the
notirication area in the first place, that just because they are in
the notification area isn't indicative they will particularly use
much in the way of resources. Many programs run in Task Manager's
processes "in the background of course, and use considerably more
resources and some programs can be exited or unloaded and they are no
longer taking resources or showing in the notification area--besides,
it's not necessary to uninstall many programs to keep them from
starting or running. You could want to do something novel like use
the program again.

I said that trying to just delete selective registry keys can
incompletely uninstall or cause other problems, and that many
programs have multiple files including .dlls and other extensions in
multiple folders that might be missed by trying to go surgically to
the registry.

Additionally, some programs have multiple areas of start-up as high
as a dozen, according to Ed Bott's XP Inside Out.

Finally he said the OEM says you should never run with msconfig in
Selective Startup Mode. I wanted to see if I could get some response
to these opinions on selective start in msconfig (I understand the
troubleshooting capacity) and using the registry to remove programs.

Thanks,

Chad Harris

 

[Harold]

changing the look of XP back to 'classic' makes a huge
difference in how XP runs, far more effective than using MSCONFIG.. to each
their own.. Are you saying that this uses less system resourses or more?



Thanks.



Harold

InCD takes 1340k memory when not being used, and for those that like to
use
the 'HD' facility. it may as well sit there.. I think that it is better to
install 512mb RAM or more, than to sacrifice every function in an attempt
to
get XP to run well.. far too much emphasis is put on closing 'startup'
items.. it is a throwback to Win 9x, when system resources were 'hit for
six' by such things.. changing the look of XP back to 'classic' makes a
huge
difference in how XP runs, far more effective than using MSCONFIG.. to
each
their own..

Mike is correct. That is the *best* way. However some programs do not have
that option.

InCD is an example. Why should InCD be running all the time when I only
burn a CD about every 2 to 3 weeks. It has no option to disable the
startup, I had to delete the entry from HKLM...CurrentVersion\Run. I
also
had to create a shortcut to start it when I want.

Msconfig should not be used as a Startup Manager. It should just be used
for troublshooting. Too many people post with advice about using
msconfig
to disable startups. *Not* a good deal. You can use it to locate where
something's starting from and then disable it from there, if there are no
other options.

StartMan is a GOOD Utility, I use it all the time, especially after
installing software. Everything you install wants to run at startup.
StartMan shows where something starts from. Check out the Help in StartMan
also! You can either have StartMan disable startups or just use it to find
where something is loading from. Running StartMan is quicker than manually
searching the registry.

[[StartMan is an extended 'msconfig' Startup Manager, designed to take
control of all those pesky programs and background services that load and
run at logon - most of which you probably don't need. As well as
providing
the usual trouble-shooting options to enable or disable startups,
StartMan
also permits the removal of startups.
Duplicate Detection and Removal, a unique feature of StartMan, can be
configured to remove all duplicates automatically, with or without
prompting.
Orphan Detection and Removal. As above, for orphaned startups.
Executable Detection and Removal. As above, for executables.
Includes a full range of sorting options to make it easier to locate a
specific startup - by name, by filename - even by command line parameter!]]

StartMan v1.3.96
http://www.pt.lu/comnet/desc/startman.html

===================

Removing an entry from one of these locations will only stop that program
from starting when Windows boots. It will *not* uninstall any programs.

With Windows XP Home, There are 13+ places that programs can start from and
they are executed in the following order:

Before Logon
1)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce

2)

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices

After Logon
3)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup
4) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
5)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
6) WIN.INI [Windows] Load
7) WIN.INI [Windows] Run
8) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
9) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
10) C:\Documents and Settings\All Users\Start Menu\Programs\Startup
11) C:\Documents and Settings\Your Name Here\Start Menu\Programs\Startup
12) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
13) As a Scheduled Task set to run at startup.

--
Hope this helps. Let us know.
Wes

In

If you want to remove programs in startup, it is best to go to each
individual program and see if there is a checkbox that will enable
removal of the 'start at Windows startup' function..

A friend says that his OEM builder is adamant that when you want to
remove a program that is using resources "in the notification area"
from your box that you should use msconfig selective startup, delete
the program from the registry, and then run normal startup from
msconfig and that you should never run with msconfig in selective
startup.

I told him that there were ways to remove programs from the
notirication area in the first place, that just because they are in
the notification area isn't indicative they will particularly use
much in the way of resources. Many programs run in Task Manager's
processes "in the background of course, and use considerably more
resources and some programs can be exited or unloaded and they are no
longer taking resources or showing in the notification area--besides,
it's not necessary to uninstall many programs to keep them from
starting or running. You could want to do something novel like use
the program again.

I said that trying to just delete selective registry keys can
incompletely uninstall or cause other problems, and that many
programs have multiple files including .dlls and other extensions in
multiple folders that might be missed by trying to go surgically to
the registry.

Additionally, some programs have multiple areas of start-up as high
as a dozen, according to Ed Bott's XP Inside Out.

Finally he said the OEM says you should never run with msconfig in
Selective Startup Mode. I wanted to see if I could get some response
to these opinions on selective start in msconfig (I understand the
troubleshooting capacity) and using the registry to remove programs.

Thanks,

Chad Harris

 

[Wesley Vogel]

Less. You can disable the Themes service.

Themes
[[Used to display all those new XP themes and colors on your desktop. If
memory conscious and does not care about the "new" XP look, disable this
service to save RAM. I have observed between 4 MB to 12 MB of RAM used for
the new themes.]]
http://www.blackviper.com/WinXP/service411.htm#Themes


--
Hope this helps. Let us know.
Wes

In

changing the look of XP back to 'classic' makes a huge
difference in how XP runs, far more effective than using MSCONFIG..
to each their own.. Are you saying that this uses less system
resourses or more?



Thanks.



Harold

InCD takes 1340k memory when not being used, and for those that like
to use
the 'HD' facility. it may as well sit there.. I think that it is
better to install 512mb RAM or more, than to sacrifice every
function in an attempt to
get XP to run well.. far too much emphasis is put on closing
'startup' items.. it is a throwback to Win 9x, when system resources
were 'hit for six' by such things.. changing the look of XP back to
'classic' makes a huge
difference in how XP runs, far more effective than using MSCONFIG..
to each
their own..

Mike is correct. That is the *best* way. However some programs do
not have that option.

InCD is an example. Why should InCD be running all the time when I
only burn a CD about every 2 to 3 weeks. It has no option to
disable the startup, I had to delete the entry from
HKLM...CurrentVersion\Run. I also
had to create a shortcut to start it when I want.

Msconfig should not be used as a Startup Manager. It should just
be used for troublshooting. Too many people post with advice about
using msconfig
to disable startups. *Not* a good deal. You can use it to locate
where something's starting from and then disable it from there, if
there are no other options.

StartMan is a GOOD Utility, I use it all the time, especially after
installing software. Everything you install wants to run at
startup. StartMan shows where something starts from. Check out the
Help in StartMan also! You can either have StartMan disable
startups or just use it to find where something is loading from.
Running StartMan is quicker than manually searching the registry.

[[StartMan is an extended 'msconfig' Startup Manager, designed to
take control of all those pesky programs and background services
that load and run at logon - most of which you probably don't need.
As well as providing
the usual trouble-shooting options to enable or disable startups,
StartMan
also permits the removal of startups.
Duplicate Detection and Removal, a unique feature of StartMan, can
be configured to remove all duplicates automatically, with or
without prompting.
Orphan Detection and Removal. As above, for orphaned startups.
Executable Detection and Removal. As above, for executables.
Includes a full range of sorting options to make it easier to
locate a specific startup - by name, by filename - even by command
line parameter!]]

StartMan v1.3.96
http://www.pt.lu/comnet/desc/startman.html

===================

Removing an entry from one of these locations will only stop that
program from starting when Windows boots. It will *not* uninstall
any programs.

With Windows XP Home, There are 13+ places that programs can start
from and they are executed in the following order:

Before Logon
1)

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce

2) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices

After Logon
3)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup
4)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
5)
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
6) WIN.INI [Windows] Load 7) WIN.INI [Windows] Run
8) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
9) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
10) C:\Documents and Settings\All Users\Start Menu\Programs\Startup
11) C:\Documents and Settings\Your Name Here\Start
Menu\Programs\Startup 12)
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
13) As a Scheduled Task set to run at startup.

--
Hope this helps. Let us know.
Wes

In Mike <[email protected]> hunted and pecked:
If you want to remove programs in startup, it is best to go to each
individual program and see if there is a checkbox that will enable
removal of the 'start at Windows startup' function..

A friend says that his OEM builder is adamant that when you want
to remove a program that is using resources "in the notification
area" from your box that you should use msconfig selective
startup, delete the program from the registry, and then run normal
startup from msconfig and that you should never run with msconfig
in selective startup.

I told him that there were ways to remove programs from the
notirication area in the first place, that just because they are in
the notification area isn't indicative they will particularly use
much in the way of resources. Many programs run in Task Manager's
processes "in the background of course, and use considerably more
resources and some programs can be exited or unloaded and they are
no longer taking resources or showing in the notification
area--besides, it's not necessary to uninstall many programs to
keep them from starting or running. You could want to do
something novel like use the program again.

I said that trying to just delete selective registry keys can
incompletely uninstall or cause other problems, and that many
programs have multiple files including .dlls and other extensions
in multiple folders that might be missed by trying to go
surgically to the registry.

Additionally, some programs have multiple areas of start-up as
high as a dozen, according to Ed Bott's XP Inside Out.

Finally he said the OEM says you should never run with msconfig
in Selective Startup Mode. I wanted to see if I could get some
response to these opinions on selective start in msconfig (I
understand the troubleshooting capacity) and using the registry to
remove programs.

Thanks,

Chad Harris

 

[Chad Harris]

Thanks r--

Very Glad to have the article and I'm reading it. I know I have seen the
tip that Classic mode saves resources several times all over the place, but
it seems that the degree to which it would conserve resources would depend
on a lot of variables like

Processor
RAM--How much and the type
Hard Drive Manufacturer, type SATA, ect. and speed
MOBO
Possibly which graphics card--and its efficiency
OS Build--NT vs. 2K vs. XP if the others besides XP allow switch to Classic
Mode

Chad Harris

 

[+-J]

| Mike: changing the look of XP back to 'classic' makes a huge
| difference in how XP runs, far more effective than using MSCONFIG.. to each
| their own.

| Are you saying that this uses less system resourses or more?

Harold,

Less system resourses!

I use XP 'classic' visual style and [Start]-menu, no animations, no wallpaper, etc.

I also use MSCONFIG in selective-startup mode to enable/disable applications which do not give the option to do so.

 

[Wesley Vogel]

System Configuration Utility
[System Configuration Utility (Msconfig.exe) allows you to *temporarily*
change the way Windows XP Professional starts by disabling startup programs
and services individually or several at a time.]
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_dxth.asp

======================

[[If you change any startup setting by using the System Configuration
Utility, Windows XP Professional displays the following message when you log
on:

You have used the System Configuration Utility to make temporary changes to
some of your system settings. To return to normal operations, choose the
Normal option on the General tab.

The preceding message and the System Configuration Utility continue to
appear each time you log on until you restore the original startup settings
by clicking Normal Startup under Startup Selection on the General tab. To
*permanently* change a startup setting, you must move or delete startup
shortcuts, change a Group Policy setting, or uninstall the application that
added the startup application.]]
Disabling Startup Programs by Using the System Configuration Utility
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmc_str_zsqb.asp

--
Hope this helps. Let us know.
Wes

In

Mike: changing the look of XP back to 'classic' makes a huge
difference in how XP runs, far more effective than using MSCONFIG..
to each their own.

Are you saying that this uses less system resourses or more?

Harold,

Less system resourses!

I use XP 'classic' visual style and [Start]-menu, no animations, no
wallpaper, etc.

I also use MSCONFIG in selective-startup mode to enable/disable
applications which do not give the option to do so. ---
Jan

 

[+-J]

Wes,

I know ...

| System Configuration Utility
| [System Configuration Utility (Msconfig.exe) allows you to *temporarily*
| change the way Windows XP Professional starts by disabling startup programs
| and services individually or several at a time.]
|
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_dxth.asp
|
| ======================
|
| [[If you change any startup setting by using the System Configuration
| Utility, Windows XP Professional displays the following message when you log
| on:
|
| You have used the System Configuration Utility to make temporary changes to
| some of your system settings. To return to normal operations, choose the
| Normal option on the General tab.
|
| The preceding message and the System Configuration Utility continue to
| appear each time you log on until you restore the original startup settings
| by clicking Normal Startup under Startup Selection on the General tab. To
| *permanently* change a startup setting, you must move or delete startup
| shortcuts, change a Group Policy setting, or uninstall the application that
| added the startup application.]]
| Disabling Startup Programs by Using the System Configuration Utility
|
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmc_str_zsqb.asp

.... but how is your alternative utility startup manager any *better* than using MSCONFIG in selective-startup mode to enable/disable
applications which do not give the option to do so?

---
Jan


| +-J :
| >> Mike: changing the look of XP back to 'classic' makes a huge
| >> difference in how XP runs, far more effective than using MSCONFIG..
| >> to each their own.
| >
| >> Are you saying that this uses less system resourses or more?
| >
| > Harold,
| >
| > Less system resourses!
| >
| > I use XP 'classic' visual style and [Start]-menu, no animations, no
| > wallpaper, etc.
| >
| > I also use MSCONFIG in selective-startup mode to enable/disable
| > applications which do not give the option to do so. ---
| > Jan
|

 

[Harold]

Thanks for the answers about the use of XP vs the Classic view.

Harold

System Configuration Utility
[System Configuration Utility (Msconfig.exe) allows you to *temporarily*
change the way Windows XP Professional starts by disabling startup
programs
and services individually or several at a time.]
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_dxth.asp

======================

[[If you change any startup setting by using the System Configuration
Utility, Windows XP Professional displays the following message when you
log
on:

You have used the System Configuration Utility to make temporary changes
to
some of your system settings. To return to normal operations, choose the
Normal option on the General tab.

The preceding message and the System Configuration Utility continue to
appear each time you log on until you restore the original startup
settings
by clicking Normal Startup under Startup Selection on the General tab. To
*permanently* change a startup setting, you must move or delete startup
shortcuts, change a Group Policy setting, or uninstall the application
that
added the startup application.]]
Disabling Startup Programs by Using the System Configuration Utility
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmc_str_zsqb.asp

--
Hope this helps. Let us know.
Wes

In

Mike: changing the look of XP back to 'classic' makes a huge
difference in how XP runs, far more effective than using MSCONFIG..
to each their own.

Are you saying that this uses less system resourses or more?

Harold,

Less system resourses!

I use XP 'classic' visual style and [Start]-menu, no animations, no
wallpaper, etc.

I also use MSCONFIG in selective-startup mode to enable/disable
applications which do not give the option to do so. ---
Jan

 

[Mike]

I think that the XP look sucks, and I changed to Classic look within minutes
of installing it.. I do have a wallpaper image, and I enable drop shadows to
make the icon text background transparent.. all of the other features slow
screen performance to a crawl.. this is what makes XP look and feel slow..

Bear in mind that everything that runs on a computer will take up
resources.. here are some instances that can be avoided without reducing
functionality:

1. Do not fill up the desktop with shortcuts.. there is no need for it..
memory is required for each shortcut, but the START popup already has memory
allocated for storing shortcuts.. one click on the START button or pressing
the 'Windows' key on the keyboard gets instant access to programs.. sort the
start menu into groups of programs for easy location access..

2. Do not download files/programs to the desktop because they are easier to
find.. It is easy enough to create folders/directories that one could find
as easily.. maintaining a shortcut is not so system intensive as maintaining
a program file..

3. Avoid 3rd party fun stuff.. some of it is badly written, often accessing
memory that is used by system functions.. the authors use parts of memory
that may hardly be used by the average user, but when they are, the system
will kick back.. they also introduce adware and spyware.. searchweb2 is
really difficult to remove, and it plays hell with the system, as does all
adware and spyware..

4. MSCONFIG is not there to be used as a shortcut to removing anything.. it
is there for diagnostic purposes.. use the program preferences to remove
unwanted start items..

5. Removing services is not the way to make a computer faster either..
sure, shutting down some will give a little extra, but then when you decide
to advance a little, you try to start or install something and some of the
background code that it needs is no longer running.. more questions in the
newsgroup.. why isn't this or that working?

Anti-virus programs use memory.. they have to because they are monitoring
everything that is on the computer.. they look for file changes, checksum
errors, incoming mail, outgoing mail, downloads.. I have heard some admit to
turning it off while on the net to get more speed.. ref #4, others take the
a/v and firewall out of start-up along with everything else because somebody
told them that Windows doesn't need anything there.. that is true.. Windows
doesn't need anything in start-up, AS LONG AS YOU DON'T CONNECT TO THE
INTERNET, OR PUT AN UNKNOWN FLOPPY DISK IN THE A DRIVE.. so connect with the
internet without a/v and firewall running and time how long it takes to get
a trojan or virus.. two minutes maybe, two milliseconds.. would those same
people remove the brakes from their cars to save weight and gain a little
increase in speed?..

Pretty is cool for some, personalization is cool for some, but everything
that you see on the screen requires memory to keep it there, and the more
complex stuff requires way more memory.. if a user prefers cool looks to
functionality, then they have to live with it or get more resources
installed.. it is suggested that XP will run in 128mb, but how fast, and
with what else running?.. 256mb is the base amount fitted to most new
computers these days.. but is that enough?.. it all depends on what else is
installed.. 512mb should be regarded as minimal really.. systems are sold
with the minimum amount installed that will enable them to work well.. if
more programs are installed, more memory should follow..

Thanks for the answers about the use of XP vs the Classic view.

Harold

System Configuration Utility
[System Configuration Utility (Msconfig.exe) allows you to *temporarily*
change the way Windows XP Professional starts by disabling startup
programs
and services individually or several at a time.]
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_dxth.asp

======================

[[If you change any startup setting by using the System Configuration
Utility, Windows XP Professional displays the following message when you
log
on:

You have used the System Configuration Utility to make temporary changes
to
some of your system settings. To return to normal operations, choose the
Normal option on the General tab.

The preceding message and the System Configuration Utility continue to
appear each time you log on until you restore the original startup
settings
by clicking Normal Startup under Startup Selection on the General tab. To
*permanently* change a startup setting, you must move or delete startup
shortcuts, change a Group Policy setting, or uninstall the application
that
added the startup application.]]
Disabling Startup Programs by Using the System Configuration Utility
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmc_str_zsqb.asp

--
Hope this helps. Let us know.
Wes

In

Mike: changing the look of XP back to 'classic' makes a huge
difference in how XP runs, far more effective than using MSCONFIG..
to each their own.

Are you saying that this uses less system resourses or more?

Harold,

Less system resourses!

I use XP 'classic' visual style and [Start]-menu, no animations, no
wallpaper, etc.

I also use MSCONFIG in selective-startup mode to enable/disable
applications which do not give the option to do so. ---
Jan

 

[Wesley Vogel]

Hi Jan,

Haven't seen you around for a while.

For those who do not wish to mess around in the registry, StartMan is a good
deal. It only runs when you start it. It does not have to run in the
background. It can remove the startups for you, not only just disable
them. Whether it's a link in a startup folder or a path in the registry.

From StartMan Help:
[[StartMan is a startup manager created to address some of the shortcomings
in Microsoft's original System Configuration Utility (MSCONFIG.EXE).
MSCONFIG is primarily a troubleshooting tool, not a startup manager, and as
such it does not permit the permanent removal of startups - they can only be
disabled. Under normal circumstances all startup items should be enabled as
it is difficult to troubleshoot a system's startup while some items are
disabled on a more permanent basis. Such non-essential items should be
removed completely, in order to both release MSCONFIG for its primary
purpose of troubleshooting, and to remove any confusion where duplication
occurs. Where an item is essential, the program that requires it will quite
often re-instate the item. But since it knows nothing of the disabled item,
you end up with a duplicate. A duplicate is simply an item that is both
enabled and disabled (not as impossible as it sounds, since enabled and
disabled items are stored in separate locations). {{{Doesn't have to be an
essential item, some scumware can and will re-enable their startup keys.
Wes}}}

MSCONFIG also doesn't show where each of the startup items are actually
located (versions previous to Windows Me's version). This can be an
important factor when determining whether a startup item is essential to the
system or not. {{{XP's version of msconfig does show the locations, but if
you're not familiar with the registry, they are hard to read. Wes}}}

StartMan addresses all these issues by displaying each group of startups
separately and by permitting the user to delete non-essential items as well
as temporarily disabling the essentials. It is fully-compliant with MSCONFIG
with regards the location of disabled items and, where a duplication occurs,
will automatically offer to remove the disabled item for you (a feature
unique to StartMan). StartMan also displays additional startup groups that
MSCONFIG simply doesn't touch.

IMPORTANT
The correct method for removing any startup is to use the program that
placed it there in the first place. The reason for this is that the program
would otherwise be unaware of the changes you'd made with StartMan or any
other startup managers, and some will actually restore their startups
automatically, thus creating duplicates. Therefore always check the main
program's own options or preferences, or the system tray icon's options (if
the program has one) before resorting to any startup manager - including
this one. Startup managers should ONLY be used to disable startups
temporarily - such as when troubleshooting - or to remove non-essential
startups that have no removal options whatsoever. ]]

Where an enabled startup might live >>
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Where a disabled item from that location gets stored >>
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run-

--
Hope this helps. Let us know.
Wes

In

Wes,

I know ...

System Configuration Utility
[System Configuration Utility (Msconfig.exe) allows you to
*temporarily* change the way Windows XP Professional starts by
disabling startup programs and services individually or several at a
time.]

http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_dxth.asp

======================

[[If you change any startup setting by using the System Configuration
Utility, Windows XP Professional displays the following message when
you log on:

You have used the System Configuration Utility to make temporary
changes to some of your system settings. To return to normal
operations, choose the Normal option on the General tab.

The preceding message and the System Configuration Utility continue
to appear each time you log on until you restore the original
startup settings by clicking Normal Startup under Startup Selection
on the General tab. To *permanently* change a startup setting, you
must move or delete startup shortcuts, change a Group Policy
setting, or uninstall the application that added the startup
application.]]
Disabling Startup Programs by Using the System Configuration Utility

http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmc_str_zsqb.asp

... but how is your alternative utility startup manager any *better*
than using MSCONFIG in selective-startup mode to enable/disable
applications which do not give the option to do so?

---
Jan

+-J :

Mike: changing the look of XP back to 'classic' makes a huge
difference in how XP runs, far more effective than using MSCONFIG..
to each their own.

Are you saying that this uses less system resourses or more?

Harold,

Less system resourses!

I use XP 'classic' visual style and [Start]-menu, no animations, no
wallpaper, etc.

I also use MSCONFIG in selective-startup mode to enable/disable
applications which do not give the option to do so. ---
Jan