Modifying .INI or Registry Settings
LinkLaunch NT can modify an .INI file setting or a registry setting on the fly
to reflect the drive letter for a dynamic mapping.
To modify an .INI file to reflect a dynamic drive mapping, insert an special
'-i expression' in front of the associated link expression:
LLNT -iexcel.ini\Section1\Entry1=_:\apps\excel \\server1\vol\apps excel.exe
The above example will make the following change to the users excel.ini file.
[Section1]
Entry1=x:\apps\excel
where x is the drive letter mapped to server1\vol1, dynamically selected by
LinkLaunch.
Another example:
LLNT -iexcel.ini\Section1\Entry1 \\server1\vol\apps excel.exe
In this case, LinkLaunch NT will examine the existing .INI entry, identify any
drive letters, and change them to the dynamically mapped drive.
You may include multiple -i expressions for the same dynamic drive mapping.
They are always associated with the next link expression on the command line. The
-i expressions must be separated from each other and the other link
expressions by one or more spaces.
You may specify a fully qualified name for the .INI file. If only the
filename is given, the file is assumed to be in the Windows directory. If the file
extension is omitted it is assumed to be '.INI'. To modify a file on a
dynamically mapped drive, a numeral representing the dynamic drive mapping index can be
used in place of the drive letter. (The index is 1 based. The dynamic drive in
the leftmost position on the command line corresponds to index 1.)
To modify a registry entry to reflect a dynamic drive mapping, the syntax is
very similar, except you must use the '-r' option:
LLNT -rHKEY_CURRENT_USER\Apps\MyApp\Dir=_:\netapps \\server1\vol1\netapps
or
LLNT -rHKEY_CURRENT_USER\Apps\MyApp\Dir \\server1\vol1\netapps\myapp.exe
See also:
Determining Which Drive Letter Is Used
LinkLaunch Wizard