Difference between revisions of "RegyChange"
m (updated adv parameter stuff) |
m (updated to make clear that adv reg prms are not supported) |
||
| Line 6: | Line 6: | ||
|MINUPDATE = n/a | |MINUPDATE = n/a | ||
|ADVFILEPARAMS = yes (sixth) | |ADVFILEPARAMS = yes (sixth) | ||
| − | |ADVREGPARAMS = | + | |ADVREGPARAMS = no |
|ADVBUILDPARAMS = yes (fifth) | |ADVBUILDPARAMS = yes (fifth) | ||
|ADVSPECIALPARAMS = ''value=data'' | |ADVSPECIALPARAMS = ''value=data'' | ||
| Line 12: | Line 12: | ||
==Usage== | ==Usage== | ||
| − | RegyChange:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=data>[,advanced | + | RegyChange:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=data>[,advanced build parameters[,advanced file parameters]] |
===Examples=== | ===Examples=== | ||
Revision as of 15:15, 29 April 2008
| RegyChange | |
| Group | Registry |
| Main Application | Version 1.4 or later 1.5.3 for adv. file |
| Required Update | n/a |
| File Parameters | yes (sixth) |
| Registry Parameters | no |
| Build Parameters | yes (fifth) |
| Special Parameters | value=data |
Looks wether the given registry value has another value then the given one.
Usage
RegyChange:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=data>[,advanced build parameters[,advanced file parameters]]
Examples
RegyChange:"Folder history",HKEY_CURRENT_USER,"\Software\Microsoft\Internet Explorer\Main\","Save Directory="
Empties the registry value Save Directory.
Description
This command checks whether a specified value has known data, to be able to correct that data back to the known one should it have been changed.
- 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. AP PT
- An entry that is used to assign new data to a value. You can use a simple value=newdata; or for numeric values, value=dword:0815. Binary is possible as well. Algo-Prefixes are allowed for both value name and text data here. AP
- This field supports advanced build parameters. Verifiers are not supported, since the change code conflicts with the verification code currently.
- Starting with 1.5.3, advanced file parameters for Flow Control can be specified. PT
You should keep in mind that even system registry values may differ between Windows versions.
Scan Results
- A special result that allows to change the value back to the known data upon fixing.
