SB> 3) I don't get why the redirection of comp.in on the
SB> comp command line?
JS> COMP normally requires user interaction. It asks up
JS> to two Y/N questions. Redirecting stdin for COMP to
JS> the file has the effect of "answering" the two
JS> questions with 'N'. So no user interaction is necessary.
.... which is why the 32-bit replacement for it is better if one
is writing command scripts. By using it, you could have halved
the size of your script, and eliminated all of the redirection
(including that of standard output, since the 32-bit COMP command
also supports /U and /Q options).