Difference between revisions of "RegyRemove"
(→Usage: added var types, updated example) |
m (updated adv parameter stuff) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
|SYNTAX = RegyRemove | |SYNTAX = RegyRemove | ||
|PENAME = SpybotSD.exe | |PENAME = SpybotSD.exe | ||
| − | |PEVERSION = 1.4 or later | + | |PEVERSION = 1.4 or later<br />1.5.3 for adv. file |
|GROUP = Registry | |GROUP = Registry | ||
|MINUPDATE = n/a | |MINUPDATE = n/a | ||
| − | |ADVFILEPARAMS = | + | |ADVFILEPARAMS = yes (sixth) |
| − | |ADVREGPARAMS = | + | |ADVREGPARAMS = no |
|ADVBUILDPARAMS = yes (sixth) | |ADVBUILDPARAMS = yes (sixth) | ||
|ADVSPECIALPARAMS = no | |ADVSPECIALPARAMS = no | ||
| Line 12: | Line 12: | ||
==Usage== | ==Usage== | ||
| − | RegyRemove:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value(string)>,<data to remove>[,advanced | + | RegyRemove:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value(string)>,<data to remove>[,advanced file parameters] |
===Examples=== | ===Examples=== | ||
| Line 33: | Line 33: | ||
# The name of the value. An [[AlgoPrefix|Algo-Prefix]] is allowed here. {{AlgoPrefix}} {{PathTemplates}} | # The name of the value. An [[AlgoPrefix|Algo-Prefix]] is allowed here. {{AlgoPrefix}} {{PathTemplates}} | ||
# The data to be removed from the term. An [[AlgoPrefix|Algo-Prefix]] is allowed here. {{AlgoPrefix}} {{PathTemplates}} | # The data to be removed from the term. An [[AlgoPrefix|Algo-Prefix]] is allowed 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. Before that, only [[Advanced build parameters|advanced build parameters]] were supported, which are still of course. {{PathTemplates}} |
===Scan Results=== | ===Scan Results=== | ||
| Line 39: | Line 39: | ||
==See also== | ==See also== | ||
| + | * [[Advanced file parameters]] | ||
* [[Advanced build parameters]] | * [[Advanced build parameters]] | ||
* [[AlgoPrefix]] | * [[AlgoPrefix]] | ||
Latest revision as of 15:17, 29 April 2008
| RegyRemove | |
| 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 (sixth) |
| Special Parameters | no |
Removes data from a registry value.
Usage
RegyRemove:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value(string)>,[,advanced file parameters]
Examples
RegyRemove:"Example",HKEY_CURRENT_USER,"\Hello\World\","remove1","silly "
If you start with this registry entry:
[CURRENT_USER\Hello\World\] "remove1"="What a silly example."
You would end with
[CURRENT_USER\Hello\World\] "remove1"="What a example."
Description
This removes partial data from a registry value, keeping the value and the surrounding data intact. This makes sense only for REG_SZ, REG_EXPANDSZ and REG_MULTISZ values.
- 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. An Algo-Prefix is allowed here. AP PT
- The data to be removed from the term. An Algo-Prefix is allowed here. AP PT
- Starting with 1.5.3, advanced file parameters for Flow Control can be specified. Before that, only advanced build parameters were supported, which are still of course. PT
Scan Results
- A special entry that allows removal of parts of data during fixing.
