Difference between revisions of "QuickLaunchIcon"
(→Description) |
|||
| Line 9: | Line 9: | ||
===Description=== | ===Description=== | ||
# The name of the link file to detect, no path involved, [[AlgoPrefix|Algo-Prefixes]] allowed. {{AlgoPrefix}} | # The name of the link file to detect, no path involved, [[AlgoPrefix|Algo-Prefixes]] allowed. {{AlgoPrefix}} | ||
| − | # The name of the file the link needs to point to, [[AlgoPrefix|Algo-Prefixes]] and [[Path templates|path templates]] allowed. {{AlgoPrefix}} | + | # The name of the file the link needs to point to, [[AlgoPrefix|Algo-Prefixes]] and [[Path templates|path templates]] allowed. {{AlgoPrefix}} {{PathTemplates}} |
# You should specify [[Advanced file parameters|advanced file parameters]] as the third parameter to limit the detection by real file properties, since file names only can be quite ambiguous. | # You should specify [[Advanced file parameters|advanced file parameters]] as the third parameter to limit the detection by real file properties, since file names only can be quite ambiguous. | ||
Revision as of 16:29, 17 February 2008
Searches the quick launch icons for one linking to the given filename.
Usage
QuickLaunchIcon:[link name],[file name],<advanced parameters>
Examples
QuickLaunchIcon:"Our malware online.lnk","<$PROGRAMFILES>\OurMalware\Malware Online.url"
Description
- The name of the link file to detect, no path involved, Algo-Prefixes allowed. AP
- The name of the file the link needs to point to, Algo-Prefixes and path templates allowed. AP PT
- You should specify advanced file parameters as the third parameter to limit the detection by real file properties, since file names only can be quite ambiguous.
You might want to use File instead, using the <$QUICKLAUNCH> or <$COMMONQUICKLAUNCH> path templates, combined with the path template <$DESKTOP> and the advanced file parameter target[link], unless you depend on the link to find the actual file (in case it uses totally random names in totally random folders, for example).
