Difference between revisions of "RegyFix"

From SpybotWiki
Jump to: navigation, search
(New page: ==Usage== RegyFix:[description],[rootkey],[keypath],[value & change],<advanced build parameters> ===Examples=== ===Description=== ==See also== ===Similar commands=== [[Category:...)
 
m (updated adv parameter stuff)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
+
{{SbiCmdInfo
 +
|SYNTAX = RegyFix
 +
|PENAME = SpybotSD.exe
 +
|PEVERSION = 1.4 or later<br />1.5.3 for adv. file
 +
|GROUP = Registry
 +
|MINUPDATE = n/a
 +
|ADVFILEPARAMS = yes (sixth)
 +
|ADVREGPARAMS = no
 +
|ADVBUILDPARAMS = yes (fifth)
 +
|ADVSPECIALPARAMS = ''value=change''
 +
}}Applies changes to the registry (TODO: this needs a better description).
  
 
==Usage==
 
==Usage==
  RegyFix:[description],[rootkey],[keypath],[value & change],<advanced build parameters>
+
  RegyFix:<description(string)>,<rootkey(enum)>,<keypath(string)>,<value=change>[,advanced build parameters[,advanced file parameters]]
  
 
===Examples===
 
===Examples===
Line 8: Line 18:
  
 
===Description===
 
===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.
 +
 +
# First, a description. Using a [[Description templates|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. {{PathTemplates}}
 +
# The name of the value, and the proposed change. {{AlgoPrefix}} {{PathTemplates}}
 +
# [[Advanced build parameters]] are supported in this field; verification through advanced registry parameters is not possible currently due to conflicts between the fix and verification codes.
 +
# 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===
 +
* The registry values to be removed.
  
 
==See also==
 
==See also==
+
* [[Advanced file parameters]]
 +
* [[Advanced build parameters]]
 +
* [[AlgoPrefix]]
 +
* [[Description templates]]
 +
 
 
===Similar commands===
 
===Similar commands===
 +
* [[RegyChange]]
 +
* [[RegyKey]]
 +
* [[RegyValue]]
 +
* [[RegyRemove]]
  
 
[[Category:SBI Commands]]
 
[[Category:SBI Commands]]
[[Category:SBI Commands (current)]]
 
[[Category:ToDo]]
 

Latest revision as of 15:14, 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 yes (sixth)
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 build parameters[,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. Advanced build parameters are supported in this field; verification through advanced registry parameters is not possible currently due to conflicts between the fix and verification codes.
  6. 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