What a response file is
You can use a separate file to give LWED the commands it needs. Such a file
contains the same information as LWED would get from the command line. What
you gain is the possibility to supply longer commands and parameters to
LWED than the command line would permit.
Typically, the COMMAND.COM command line cannot take more than 128
characters. If you need to supply, say, 120 characters, it would be
hard to do with LWED, since the program name and the switches (or commands)
would take some space from the available 128 bytes.
Under other environments it would be possible to increase the command
line length to much higher values, but a response file could still be
useful.
You use a response file by giving its path and name to LWED as
first parameter, lead by a '@' character. Example:
LWED @MYRESP.TXT
LWED @E:\LIB\CCT.RF
The first command would use the file MYRESP.TXT int the current directory
for command input, the second would use E:\LIB\CCT.RF since full path to
the file is given.
Any additional parameters supplied to LWED after the response file
specifier parameter will be ignored.
Each line in the response file contains one 'word' from an imaginate
command line. Suppose you have an LWED command like this:
LWED r c:\windows\win.ini desktop wallpaper
A command line using a response file named LWEDR.TXT in the current
directory would look like this:
LWED @LWEDR.TXT
and the contents of this file:
r
c:\windows\win.ini
desktop
wallpaper
In addition to parameters, you can comment your parameters. Any line
starting with a ';' character will be skipped by LWED. Empty lines are
also skipped, so it's possible to have a response file like this:
; my settings: bla bla bla
-w
;
; bla bla blabla bla blabla bla blabla bla bla
T.INI
;
;bla bla blabla bla bla
foo
bar