RegyRemove: Difference between revisions
Jump to navigation
Jump to search
(New page: ==Usage== RegyRemove:[description],[rootkey],[keypath],[value],[value to remove],<advanced build parameters> ===Examples=== ===Description=== ==See also== ===Similar commands=== ...) |
No edit summary |
||
| Line 1: | Line 1: | ||
Removes data from a registry value. | |||
==Usage== | ==Usage== | ||
| Line 5: | Line 5: | ||
===Examples=== | ===Examples=== | ||
RegyRemove:"Example",HKEY_CURRENT_USER,"\QATests\SBI\RegyRemove\","remove1","silly" | |||
===Description=== | ===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 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. | |||
# The name of the value. An [[AlgoPrefix|Algo-Prefix]] is allowed here. | |||
# The data to be removed from the term. An [[AlgoPrefix|Algo-Prefix]] is allowed here. | |||
==See also== | ==See also== | ||
* [[AlgoPrefix]] | |||
* [[Description templates]] | |||
===Similar commands=== | ===Similar commands=== | ||
* [[RegyChange]] | |||
* [[RegyFix]] | |||
* [[RegyKey]] | |||
* [[RegyValue]] | |||
[[Category:SBI Commands]] | [[Category:SBI Commands]] | ||
[[Category:SBI Commands (current)]] | [[Category:SBI Commands (current)]] | ||
[[Category: | [[Category:SBI Commands supporting AlgoPrefix]] | ||
Revision as of 10:19, 17 February 2008
Removes data from a registry value.
Usage
RegyRemove:[description],[rootkey],[keypath],[value],[value to remove],<advanced build parameters>
Examples
RegyRemove:"Example",HKEY_CURRENT_USER,"\QATests\SBI\RegyRemove\","remove1","silly"
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.
- The name of the value. An Algo-Prefix is allowed here.
- The data to be removed from the term. An Algo-Prefix is allowed here.