MRUList: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(added info box) |
||
| Line 1: | Line 1: | ||
Used mostly for usage tracks, this clears all entries inside a specified registry keys. | {{SbiCmdInfo | ||
|SYNTAX = MRUList | |||
|PENAME = SpybotSD.exe | |||
|PEVERSION = 1.3 or later | |||
|GROUP = Registry | |||
|MINUPDATE = n/a | |||
|ADVFILEPARAMS = no | |||
|ADVREGPARAMS = no | |||
|ADVBUILDPARAMS = yes (fourth) | |||
|ADVSPECIALPARAMS = no | |||
}}Used mostly for usage tracks, this clears all entries inside a specified registry keys. | |||
==Usage== | ==Usage== | ||
Revision as of 13:57, 22 February 2008
| MRUList | |
| Group | Registry |
| Main Application | Version 1.3 or later |
| Required Update | n/a |
| File Parameters | no |
| Registry Parameters | no |
| Build Parameters | yes (fourth) |
| Special Parameters | no |
Used mostly for usage tracks, this clears all entries inside a specified registry keys.
Usage
MRUList:<description>,<rootkey>,<key>[,advanced build parameters]
Examples
MRUList:"Recent file list",HKEY_CURRENT_USER,"\Software\Ahead\Nero - Burning Rom\Recent file list"
Description
Designed for usage tracks, this command will clear a given key by setting all string entries inside it to blank. This avoids problems with programs which would behave faulty if those values would be missing.
- The first parameter should be a description. Use description templates if you want.
- The second parameter specifies the registry root key. HKEY_CURRENT_USER sounds like a single user here, but actually means that every users registry will be scanned.
- The third parameter tells the registry key path where all values inside will be cleared.
Scan Results
- The registry key if found and not empty; this will be cleared, not deleted, upon fixing, and is always a Usage tracks result.