Difference between revisions of "RegyFix"

From SpybotWiki
Jump to: navigation, search
(Usage: added var types)
(Added 1.5.3 advanced file parameters)
Line 2: Line 2:
 
|SYNTAX = RegyFix
 
|SYNTAX = RegyFix
 
|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
Line 12: Line 12:
  
 
==Usage==
 
==Usage==
  RegyFix:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=change>[,advanced build parameters]
+
  RegyFix:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=change>[,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, and the proposed change. {{AlgoPrefix}} {{PathTemplates}}
 
# The name of the value, and the proposed change. {{AlgoPrefix}} {{PathTemplates}}
# This field supports [[Advanced build parameters|advanced build parameters]].
+
# 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. {{PathTemplates}}
  
 
===Scan Results===
 
===Scan Results===
Line 30: Line 30:
  
 
==See also==
 
==See also==
 +
* [[Advanced file parameters]]
 
* [[Advanced build parameters]]
 
* [[Advanced build parameters]]
 
* [[AlgoPrefix]]
 
* [[AlgoPrefix]]

Revision as of 14:59, 29 April 2008

RegyFix
Group Registry
Main Application Version 1.4 or later
1.5.3 for adv. file
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 file 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.

  1. First, a description. Using a description template instead of plain text is recommended so that the user will receive a localized version.
  2. The root key, where HKEY_CURRENT_USER stands for all users actually.
  3. The path to the value, starting with a backslash. PT
  4. The name of the value, and the proposed change. AP PT
  5. Starting with 1.5.3, advanced file parameters for Flow Control can be specified. Before that, only advanced build parameters were supported. PT

Scan Results

  • The registry values to be removed.

See also

Similar commands