Monitoring Alternate Modules

Many Windows applications use pre-launchers, where one .EXE will load, launch another application, and then go out of memory. Unless instructed to monitor an alternate module, LinkLaunch will unmap the temporary drives when the first .EXE terminates.

There are two ways to cause LinkLaunch to monitor an alternate module. You can add a line to the AlternateModules section in the LL.INI file, or add a special '-m expression' to the front of the command line. The .INI file methods affects all instances of LinkLaunch, while the command line method affects only the one icon. The command line method takes precedence over the .INI method.

Example of the LL.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:

LL -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 Module Spy utility to determine the correct name for an alternate module. LinkLaunch 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 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.

See also:

LL.INI File

Entering LinkLaunch Commands

LinkLaunch Module Spy

LinkLaunch Wizard