Difference between revisions of "IniValueChange"

From SpybotWiki
Jump to: navigation, search
(added info box)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{SbiCmdInfo
 +
|SYNTAX = IniValueChange
 +
|PENAME = SpybotSD.exe
 +
|PEVERSION = 1.5 or later
 +
|GROUP = Special File Formats
 +
|MINUPDATE = n/a
 +
|ADVFILEPARAMS = no
 +
|ADVREGPARAMS = no
 +
|ADVBUILDPARAMS = yes (seventh)
 +
|ADVSPECIALPARAMS = no
 +
}}Allows changes in ''.ini'' files.
 +
 
==Usage==
 
==Usage==
  IniValueChange:[description],[filename],[section],[value],[data],[new data],<advanced build parameters>
+
  IniValueChange:<description>,<filename>,<section>,<value>,<old data>,<new data>[,advanced build parameters]
  
 
===Examples===
 
===Examples===
Line 19: Line 31:
  
 
# The first parameter is a standard description; either plaintext, or better a [[Description templates|description template]], since that allows localization when displaying results to the user.
 
# The first parameter is a standard description; either plaintext, or better a [[Description templates|description template]], since that allows localization when displaying results to the user.
# The second parameter describes the file; you may use [[Path templates|path template]] here.
+
# The second parameter describes the file; you may use [[Path templates|path template]] here. {{PathTemplates}}
# The third parameter describes the section inside the INI file; [[AlgoPrefix|Algo-Prefixes]] are allowed here.
+
# The third parameter describes the section inside the INI file; [[AlgoPrefix|Algo-Prefixes]] are allowed here. {{AlgoPrefix}} {{PathTemplates}}
# The fourth parameter describes the name of the value; [[AlgoPrefix|Algo-Prefixes]] are allowed here.
+
# The fourth parameter describes the name of the value; [[AlgoPrefix|Algo-Prefixes]] are allowed here. {{AlgoPrefix}} {{PathTemplates}}
# The fifth parameter identifies the data the value has to match; [[AlgoPrefix|Algo-Prefixes]] are allowed here.
+
# The fifth parameter identifies the data the value has to match; [[AlgoPrefix|Algo-Prefixes]] are allowed here. {{AlgoPrefix}} {{PathTemplates}}
# The sixth parameter specifies the new data for the value.
+
# The sixth parameter specifies the new data for the value. {{PathTemplates}}
 
# Optionally, you may use [[Advanced build parameters|advanced build parameters]] in the seventh parameter.
 
# Optionally, you may use [[Advanced build parameters|advanced build parameters]] in the seventh parameter.
  
 
You might want to take advantage of the [[AlgoPrefix|Algo-Prefix]] ''<$REGMATCHn>'' result of previous ''<regexpr>'' checks here.
 
You might want to take advantage of the [[AlgoPrefix|Algo-Prefix]] ''<$REGMATCHn>'' result of previous ''<regexpr>'' checks here.
 +
 +
===Scan Results===
 +
* INI file entry.
  
 
==See also==
 
==See also==
Line 44: Line 59:
  
 
[[Category:SBI Commands]]
 
[[Category:SBI Commands]]
[[Category:SBI Commands (current)]]
 

Latest revision as of 13:54, 22 February 2008

IniValueChange
Group Special File Formats
Main Application Version 1.5 or later
Required Update n/a
File Parameters no
Registry Parameters no
Build Parameters yes (seventh)
Special Parameters no

Allows changes in .ini files.

Usage

IniValueChange:<description>,<filename>,<section>,<value>,<old data>,<new data>[,advanced build parameters]

Examples

IniValueChange:"A silly example","C:\Test.ini","TestMain","Greeting","Hello World","Hallo Welt"

Let's take a look at C:\Test.ini before this check has taken place:

[TestMain]
Greeting=Hello World

Now after this has been detected and fixed by the user, it would look like:

[TestMain]
Greeting=Hallo Welt

Description

This command changes the data of a value inside an INI file.

  1. The first parameter is a standard description; either plaintext, or better a description template, since that allows localization when displaying results to the user.
  2. The second parameter describes the file; you may use path template here. PT
  3. The third parameter describes the section inside the INI file; Algo-Prefixes are allowed here. AP PT
  4. The fourth parameter describes the name of the value; Algo-Prefixes are allowed here. AP PT
  5. The fifth parameter identifies the data the value has to match; Algo-Prefixes are allowed here. AP PT
  6. The sixth parameter specifies the new data for the value. PT
  7. Optionally, you may use advanced build parameters in the seventh parameter.

You might want to take advantage of the Algo-Prefix <$REGMATCHn> result of previous <regexpr> checks here.

Scan Results

  • INI file entry.

See also

Similar commands

Similar advanced file parameters