Difference between revisions of "RegyChange"
(Added 1.5.3 advanced file parameters) |
m (updated adv parameter stuff) |
||
| Line 5: | Line 5: | ||
|GROUP = Registry | |GROUP = Registry | ||
|MINUPDATE = n/a | |MINUPDATE = n/a | ||
| − | |ADVFILEPARAMS = | + | |ADVFILEPARAMS = yes (sixth) |
|ADVREGPARAMS = yes (fifth) | |ADVREGPARAMS = yes (fifth) | ||
|ADVBUILDPARAMS = yes (fifth) | |ADVBUILDPARAMS = yes (fifth) | ||
| Line 12: | Line 12: | ||
==Usage== | ==Usage== | ||
| − | RegyChange:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=data> | + | RegyChange:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=data>[,advanced registry parameters[,advanced file parameters]] |
===Examples=== | ===Examples=== | ||
| Line 26: | Line 26: | ||
# The path to the value, starting with a backslash. {{AlgoPrefix}} {{PathTemplates}} | # The path to the value, starting with a backslash. {{AlgoPrefix}} {{PathTemplates}} | ||
# 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. [[AlgoPrefix|Algo-Prefixes]] are allowed for both value name and text data here. {{AlgoPrefix}} | # 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. [[AlgoPrefix|Algo-Prefixes]] are allowed for both value name and text data here. {{AlgoPrefix}} | ||
| − | # This field supports [[Advanced | + | # This field supports [[Advanced build parameters|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|advanced file parameters]] for [[:Category:Advanced_file_parameters_for_Flow_Control|Flow Control]] can be specified. {{PathTemplates}} | # Starting with 1.5.3, [[Advanced file parameters|advanced file parameters]] for [[:Category:Advanced_file_parameters_for_Flow_Control|Flow Control]] can be specified. {{PathTemplates}} | ||
Revision as of 15:12, 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 | yes (fifth) |
| 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 registry 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.
