ModuleUsage: Difference between revisions
Jump to navigation
Jump to search
(added info box) |
(→Usage: added var types) |
||
| Line 12: | Line 12: | ||
==Usage== | ==Usage== | ||
ModuleUsage:< | ModuleUsage:<partialmodulename(string)>[,advanced build parameters] | ||
===Examples=== | ===Examples=== | ||
Latest revision as of 16:22, 22 February 2008
| ModuleUsage | |
| Group | Registry |
| Main Application | Version 1.3 or later |
| Required Update | n/a |
| File Parameters | no |
| Registry Parameters | no |
| Build Parameters | yes (second) |
| Special Parameters | no |
Searches for the Windows module usage setting for a special file.
Usage
ModuleUsage:<partialmodulename(string)>[,advanced build parameters]
Examples
ModuleUsage:"spyware/spyware.dll"
This will detect the following key:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ModuleUsage\C:/WINDOWS/SYSTEM/spyware.dll]
Description
- The first parameter can be any part of the whole key name, but should be descriptive. Algo-Prefixes will be supported after 1.5.2. AP PT
- The second parameter may contain advanced build parameters.
This command will also detect a CodeStoreDB if it is linked inside this entry. Please remember the keyname contains slashes, not backslashes!
Scan results
- The actually ModuleUsage registry key.
- The associated registry key for distributed program files (see CodeStoreDB), if existing.