Difference between revisions of "RegyValue"
(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== | ||
| − | RegyValue:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value(string)>[,advanced registry parameters] | + | RegyValue:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value(string)>[,advanced registry parameters[,advanced file parameters]] |
===Examples=== | ===Examples=== | ||
| Line 24: | Line 24: | ||
# The path to the value, starting with a backslash. {{PathTemplates}} | # The path to the value, starting with a backslash. {{PathTemplates}} | ||
# The name of the value to detect. You may use a [[AlgoPrefix|Algo-Prefix]] here. {{AlgoPrefix}} {{PathTemplates}} | # The name of the value to detect. You may use a [[AlgoPrefix|Algo-Prefix]] here. {{AlgoPrefix}} {{PathTemplates}} | ||
| − | # To refine detection, you can use [[Advanced registry parameters|advanced registry parameters]] to check the actual data of the value. You may use [[AlgoPrefix|Algo-Prefixes]] here. {{AlgoPrefix}} {{PathTemplates}} | + | # To refine detection, you can use [[Advanced registry parameters|advanced registry parameters]] to check the actual data of the value, as well as [[Advanced build parameters|advanced build parameters]]. You may use [[AlgoPrefix|Algo-Prefixes]] here. {{AlgoPrefix}} {{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}} | # 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}} | ||
Latest revision as of 15:08, 29 April 2008
| RegyValue | |
| Group | Registry |
| Main Application | Version 0.95 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 | no |
Searches for the defined registry value and adds it to the results list, if found.
Usage
RegyValue:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value(string)>[,advanced registry parameters[,advanced file parameters]]
Examples
RegyValue:"<$REG_SETTINGS>",HKEY_LOCAL_MACHINE,"\Software\Microsoft\Windows\CurrentVersion\","HidingSpywareValue"
Description
Detects a registry value and flags it for removal.
- 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 to detect. You may use a Algo-Prefix here. AP PT
- To refine detection, you can use advanced registry parameters to check the actual data of the value, as well as advanced build parameters. You may use Algo-Prefixes here. AP PT
- Starting with 1.5.3, advanced file parameters for Flow Control can be specified. PT
Scan Results
- The identified registry value(s).
See also
- Advanced file parameters
- Advanced build parameters
- Advanced registry parameters
- AlgoPrefix
- Description templates
