Why Use LinkLaunch NT?

LinkLaunch NT improves your network in the following ways:

BULLET.gif No more running out of drive letters.

BULLET.gif No more user confusion over drive mappings.

BULLET.gif Simpler login scripts. With LinkLaunch there is no need to establish a complex arrays of drive mappings during login.

BULLET.gif Easier access to networked CD-ROM drives. No longer are users required to map CD's, manually. When CD based applications are shutdown connections to the CD server are automatically freed.

BULLET.gif In Banyan environments, reduced SPP connection usage.

BULLET.gif In Netware environments, reduced license usage. With LinkLaunch you are attached and authenticated to servers only while applications are using those servers. When the last application using the server is closed, the attachment is terminated.

BULLET.gif Reduced network traffic.

BULLET.gif Improved ability to set working directories. By itself, Windows NT does not support the use of UNC (Universal Naming Convention) for working directories. With LinkLaunch NT the working directory can be set to a dynamically mapped directory.

BULLET.gif The ability to set dynamic search drives. With LinkLaunch NT, dynamically mapped drives can be added to the DOS path.

BULLET.gif The ability to release idle connections. LinkLaunch NT can be configured to automatically terminate idle applications, thus freeing network resources.

Although LinkLaunch NT can be used on a single workstation, it is most valuable when used with shared group files, shared menus, or shared Windows shortcut files. In these environments, the network administrator can configure the program items.