64
You can eliminate functions you may not need. For example, there may be drives you don’t need to
map, file servers you don’t need to attach to, or printer ports you don’t need to capture.
You can save time by running programs such as CAPTURE.EXE from your local hard disk rather
than from the file server.
To login using a local login script, use the following form of the LOGIN command:
LOGIN /S scriptpath servername/username
↵
↵
The
/S
switch indicates that the item that follows is the pathname of a login script. For example, to log in to
server BIGSERVER as user ALICE, using local login script LOGIN.DAT:
LOGIN /S C:\FLINK\LOGIN.DAT BIGSERVER/ALICE
↵
↵
Be sure to include the drive and full pathname of the local login script.
Creating a Local Login Script
Your FastLink II Administrator can help you set up a local login script.
Most login scripts consist primarily of ATTACH commands to connect to additional file servers, MAP
commands to create network drives, and CAPTURE commands to redirect printer ports to network printers.
Here’s an example of a simple login script:
ATTACH SERVER2/GEORGE
MAP J:=SERVER2/SYS:PUBLIC
#C:\FLINK\CAPTURE Q=PRINT_QUEUE NB TI=10 NFF
Note in the example above that ATTACH and MAP are script commands that are directly interpreted by the
LOGIN program. There is no directly interpreted CAPTURE command however, so CAPTURE.EXE must be
run as a DOS program by using the
#
prefix. Note also that the drive and full pathname of the CAPTURE
program are supplied, to ensure that the program is run from the local hard disk.
