SubInACL is a command-line tool that enables administrators to obtain security information about files, registry keys, and services, and transfer this information from user to user, from local or global group to group, and from domain to domain. For example, if a user has moved from one domain (DomainA) to another (DomainB), the administrator can replace DomainA\User with DomainB\User in the security information for the user’s files. This gives the user access to the same files from the new domain. subinacl.zip.
There are seven Run keys in the registry that cause programs to be run automatically:
Keys 1 through 7 apply to Windows 95, Windows 98, Windows 98 Second Edition, and…Keys 1 through 7 apply to Windows 95, Windows 98, Windows 98 Second Edition, and Windows Millennium Edition (Me).
Keys 1 through 4 also apply to Windows NT 4.0 and Windows 2000.
For Windows 98, Windows 98 Second Edition, Windows Me, Windows NT 4.0 SP3 or later, and Windows 2000, an additional rule is available; for keys 3 and 4, the value name can be prefixed with an asterisk to force the program to run even in Safe mode.
Keys 1 through 4 are run each time a new user logs in.
Keys 5 and 6 are run in the background when the logon dialog box first appears, or at this stage of the boot process if there is no logon. These keys are for background services such as remote registry service and are run only once per boot.
Key 7 is run as part of Setup’s first-boot activities, or after you use the Add/Remove Programs Wizard.
Under each of these keys is a series of values. The values are used to allow multiple subentries to exist without overwriting one another.
The data value for a value is a command line. By default, Run keys are ignored in Safe mode. For keys 3 and 4, the value name can be prefixed with an exclamation point to defer deletion of the value until after the command has been completed.
For keys 3, 4, and 6, the value is deleted before the command line is run unless overridden as noted above. As a result, if a RunOnce operation fails to run properly, the component that failed will not be asked to run again the next time you start the computer.
Key 7 is used only by Setup. This key displays the progress dialog box as the keys are run one at a time. For key 7, the name of the value is the name that is displayed in the dialog box.
Published under MSKB: Q137367
Definition of the four Run keys that are in the Microsoft Windows XP registry.
Run keys cause programs to automatically run each time that a user logs on. The Windows XP registry includes the following four Run keys:
Each of these keys has a series of values. The values allow multiple entries to exist without overwriting one another. The data value for a value is a command line.
There are some special considerations for the third and fourth keys in the list, the RunOnce keys:
Beginning with Windows XP, the values in the RunOnce keys are run only if the user has permission to delete entries from the respective key.
The programs in the RunOnce key are run sequentially. Explorer waits until each one has exited before continuing with normal startup.
By default, Run keys are ignored when the computer starts in Safe mode. Under the RunOnce keys, you can prefix a value name with an asterisk (*) to force the associated program to run even in Safe mode.
You can prefix a RunOnce value name with an exclamation point (!) to defer deletion of the value until after the command runs.
Without the exclamation point prefix, a RunOnce value is deleted before the command runs. As a result, if a RunOnce operation does not run properly, the associated program is not asked to run the next time you start the computer.
If more than one program is registered under any particular key, the order in which those programs are run is indeterminate. A program run from any of these keys should not write to the key during its execution. Doing so will interfere with the execution of other programs registered under the key. Furthermore, applications should use the RunOnce keys only for transient conditions (such as to complete application setup); an application must not continually re-create entries under RunOnce. Doing so will interfere with Windows Setup.
Published under MSKB: Q314866