Installation guide

Appendix E Using the Network Application Starter 365
Case is not significant in section names.
[servers]
Each line in the optional [servers] section has an entry describing a list
of servers that support the named share. Each server should be
separated by a comma or a space. There is no limit to the number of
shares; however, there is a limit of 1024 bytes for each line of servers.
(Theoretically, 1024 bytes is
64 full-length servers per share. In practice, most server names are
not that long, so you could have even more.)
[options]
The [OPTIONS] section is optional and may contain any or all of the
following parameters:
LogFile
Provides the local or UNC path to a log file for logging system
events. When this parameter is used, each time a user enters an
application, the username, machine name, date and time, server
selected, and application are logged. The same information is
logged when the user exits the application. Any fatal errors are
also logged. If the user needs other types of tracking, the
LAN Manager auditing feature can be used to audit the actual file
usage.
LogMsgVerbose
Allows the administrator to specify how much information is sent
to the log file when an error occurs. A value of 1 causes appstart
to send all of the information it has. A value of 0 causes appstart
to send a simple message stating that the appstart command
failed. The default value is 1 (verbose).
UserMsgVerbose
Allows the administrator to specify how much information is
displayed to the user. A value of 1 causes appstart to display all of
the information it has. A value of 0 causes appstart to display a
simple message stating that the appstart command failed. The
default value is 1 (verbose).
LogMultiple
Specifies whether to log multiple instances of the same alias. For
example, if the user launches an application twice, without exiting,
both instances can be logged. The default is 1 (log multiple
instances).