scanregw in msconfig

In the start up sequence within MSconfig, does the position of the scanregw
make a difference? We had lost it, now have installed it in the registry's
local machine/ software/ microsoft /windows/ current version /run folder. It
is backing up the registry daily, I was wondering if its sequence location
was critical.

Thanks wouldbee

"wouldbee" wrote in message ...
In the start up sequence within MSconfig, does the position of the scanregw
make a difference? We had lost it, now have installed it in the registry's
local machine/ software/ microsoft /windows/ current version /run folder.

That's the correct key. The value should be-
C:\WINDOWS\scanregw.exe /autorun
(assuming c:\windows)

It
is backing up the registry daily, I was wondering if its sequence location
was critical.

The order in the msconfig list, isn't the order that they are run. The order is
dependent on where in the startup "axis" the process is loaded. You're ok
there.

If I read you correct, WIN98 puts it in the right run order thanks.

"Bill Blanton" wrote:

"wouldbee" wrote in message ...
In the start up sequence within MSconfig, does the position of the scanregw
make a difference? We had lost it, now have installed it in the registry's
local machine/ software/ microsoft /windows/ current version /run folder.

That's the correct key. The value should be-
C:\WINDOWS\scanregw.exe /autorun
(assuming c:\windows)

It
is backing up the registry daily, I was wondering if its sequence location
was critical.

The order in the msconfig list, isn't the order that they are run. The order is
dependent on where in the startup "axis" the process is loaded. You're ok
there.

Yep. It's right.

"wouldbee" wrote in message ...
If I read you correct, WIN98 puts it in the right run order thanks.

"Bill Blanton" wrote:

"wouldbee" wrote in message ...
In the start up sequence within MSconfig, does the position of the scanregw
make a difference? We had lost it, now have installed it in the registry's
local machine/ software/ microsoft /windows/ current version /run folder.

That's the correct key. The value should be-
C:\WINDOWS\scanregw.exe /autorun
(assuming c:\windows)

It
is backing up the registry daily, I was wondering if its sequence location
was critical.

The order in the msconfig list, isn't the order that they are run. The order is
dependent on where in the startup "axis" the process is loaded. You're ok
there.

You have put it in the proper place. "StartupCop" would not move them
around for you in the Startup Group, but here is an interesting Help
screen from it...

http://www.pcmag.com/ 's StartupCop has "undo", and it is more than a
combination of "START, Run, MSInfo32, Software Environment, Startup
Programs" and "START, Run, MSConfig, Startup tab". It can even do a
permanent delete. You may create multiple "profiles" of Startup items.

.................Start.....of a StartupCop help screen.............
Windows loads startup items from three locations in the Registry, two
lines in WIN.INI, and two folders. Observation reveals that it always
loads the seven groups in the same order. Here they are, in order:

1. Registry (Machine Service) - Each value in the Registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\RunServices
defines a startup item. The value's data string is the command to be
executed at startup.
2. Win.ini (Load=) - The value of the Load= key in the [Windows] section
of WIN.INI consists of one or more startup program names, separated by
semicolons. Neither long filenames nor command-line arguments may be
used. (Windows NT users - see note below)
3. Win.ini (Run=) - The value of the Run= key in the [Windows] section
of WIN.INI consists of one or more startup program names, separated by
semicolons. Neither long filenames nor command-line arguments may be
used. (Windows NT users - see note below)
4. Registry (Machine Run) - Each value in the Registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run defines
a startup item. The value's data string is the command to be executed at
startup.
5. Registry (Per-User Run) - Each value in the Registry key
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Curre ntVersion\RunServices
defines a startup item. The value's data string is the command to be
executed at startup.
6. Common Startup Group - Each shortcut in the common startup group (by
default, C:\Windows\All Users\Start Menu\Programs\Startup) is launched
at startup. This group does not appear on the Start menu. Some Windows
installations will not have a common startup group.
7. Startup Group - Each shortcut in the Start menu's startup group (by
default, C:\Windows\Start Menu\Programs\Startup) is launched at startup.

Startup Cop displays each item's group number in the Priority column.
Within each group, enabled items are shown first, then disabled items,
and finally items that are ready for removal. The groups load in the
order specified, and enabled items within a group will load in roughly
the order shown, though this may vary. Because the order of the items is
significant, Startup Cop does not permit sorting into different orders
by clicking the column headings.
....snip
..................End......of a StartupCop help screen....

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"wouldbee" wrote in message
...
| If I read you correct, WIN98 puts it in the right run order thanks.
|
| "Bill Blanton" wrote:
|
| "wouldbee" wrote in message
...
| In the start up sequence within MSconfig, does the position of the
scanregw
| make a difference? We had lost it, now have installed it in the
registry's
| local machine/ software/ microsoft /windows/ current version /run
folder.
|
| That's the correct key. The value should be-
| C:\WINDOWS\scanregw.exe /autorun
| (assuming c:\windows)
|
| It
| is backing up the registry daily, I was wondering if its sequence
location
| was critical.
|
| The order in the msconfig list, isn't the order that they are run.
The order is
| dependent on where in the startup "axis" the process is loaded.
You're ok
| there.
|
|
|
|