@begin(header)
author: Eric Mandel
show_author: ShowNone
author_organization: Smithsonian Astrophysical Observatory
node_expert: eric@cfa.harvard.edu
expiration_date: 12/31/93
last_modifier: eric@cfa.harvard.edu
last_mod_date: 05/28/93
mod_num: 5
@end(header)
@b<This window will tell you about some ASSIST limitations and known bugs.>

The ASSIST does not properly handle IRAF commands which read from the
standard input, such as average. The user must still enter STDIN input
into the IRAF window.

Parameters should not be cached with the IRAF cache command.

The program adds an IRAF parameter flpar to each parameter file to
force the parameter file to be updated to disk as needed.  This
parameter should be ignored by users.

If an error occurs during an IRAF command and a second command is sent
before the error window is displayed, that second command will
occasionally assume that the error pertains to it and will
abort execution.  This will happen, for example, if one presses
the @b<Run> button, gets an error, and immediately presses @b<Q&A>
before the error window appears.  In this case, simply run the second
command again.  (It's pretty hard to be fast enough with button
presses to make this happen!)

The IRAF help display requires that the IRAF help command be run to
generate an ASCII help file.  If the file is not found, either in the
default assist directory, or in the user's uparm directory, it is
created in the uparm directory.  This can take several seconds, so
that response to a help request is not always immediate.