Difference between revisions of "RegyFix"
(added info box) |
(→Usage: added var types) |
||
| Line 12: | Line 12: | ||
==Usage== | ==Usage== | ||
| − | RegyFix:<description>,<rootkey>,<keypath>,<value=change>[,advanced build parameters] | + | RegyFix:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=change>[,advanced build parameters] |
===Examples=== | ===Examples=== | ||
Revision as of 16:34, 22 February 2008
| RegyFix | |
| Group | Registry |
| Main Application | Version 1.4 or later |
| Required Update | n/a |
| File Parameters | no |
| Registry Parameters | no |
| Build Parameters | yes (fifth) |
| Special Parameters | value=change |
Applies changes to the registry (TODO: this needs a better description).
Usage
RegyFix:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=change>[,advanced build parameters]
Examples
Description
Used to handle a registry value that is set to a specified data. Using RegyValue plus a verifier may lead to the same result.
- First, a description. Using a description template instead of plain text is recommended so that the user will receive a localized version.
- The root key, where HKEY_CURRENT_USER stands for all users actually.
- The path to the value, starting with a backslash. PT
- The name of the value, and the proposed change. AP PT
- This field supports advanced build parameters.
Scan Results
- The registry values to be removed.
