Script or command files
When large numbers of commands are needed or the same command sequence is
repeated many times it is helpful to place the commands in a script or command
file. Interactive mode script file names are prefixed with a "$" on
the SLINK command line, whereas command line mode script files are prefixed
with an "@". Commands taken from script files are presented in the
same form as that used when entering commands from a command prompt in
interactive mode or from the command line. For example,
will tell SLINK to take its commands from a file called MYPROG.INF and that the
command format is interactive mode, whilst
will tell SLINK to take its commands from a file called MYPROG.LNK and that the
command format is command line mode.
Note that the file suffixes .INF and .LNK are purely conventional and do not
affect how the commands will be interpreted - you may use suffixes of your own
choosing if you wish.
As a special case, for interactive mode command files, the $ before the file
name can be omitted. In this case, if the file is not recognised as a COFF
object, it will be opened as a script file. For this reason, COFF objects
specified on the command line must have the correct filename extension as SLINK
will not complete the filename itself.
More than one script file may be specified on the command line but script files
may not themselves contain script files.