Monitoring Alternate Modules
Many Windows applications use pre-launchers, where one .EXE will load, launch
another application, and then go out of memory. For 32 bit applications,
LinkLaunch NT can keep track of alternate modules automatically. For 16 bit
applications, unless instructed to monitor an alternate module, LinkLaunch NT will
unmap the temporary drives when the first .EXE terminates.
There are two ways to cause LinkLaunch to monitor an alternate 16 bit module.
You can add a line to the AlternateModules section in the LLNT.INI file, or
add a special '-m expression' to the front of the command line. The .INI file
methods affects all instances of LinkLaunch NT, while the command line method
affects only the one icon. The command line method takes precedence over the .INI
method.
Example of the LLNT.INI method:
[AlternateModules]
123w.exe =123main.exe
In this case, temporary drive mappings created when 123w.exe was launched
would not be unmapped until, 123main.exe was shut down.
Example of the command line method:
LLNT -mtview.exe j:=\\service@group@org\dir1 wupdate.exe
In this case j: would not be unmapped until tview.exe was shut down.
You can use the 16 bit Module Spy utility to determine the correct name for an
alternate 16 bit module. LinkLaunch NT will accept the filename (without the
path) or the internal name for the alternate module. MODSPY reports both. If
a filename is being used, make sure to include the extension.
LinkLaunch NT will attempt to notify you when an alternate module is needed.
It does this by observing if an application is launched and immediately
terminated. If you receive a message, but are sure the alternate module is not
needed, specify -mNOMSG to disable the message.
For 32 bit applications, the -m expression is ignored.
See also:
LLNT.INI File
Entering LinkLaunch Commands
16 bit Module Spy
LinkLaunch NT Wizard