[Last updated 4/5/93]
What to do when things go wrong in strn.
(May be changed to "If..." in beta testing :-)

	Things *will* go wrong for some people.  Here are a few tips.

Compilation:
	* Can you compile plain trn on your system?  If not, strn is
unlikely to work.  You can disable almost all the modifications by
changing #ifdefs at the end of config.h (generated by Configure).
Most of the new code is controlled by the SCAN and SCORE
defines (at least most of the code which could cause problems).

	* If you don't understand why STRN fails to compile, or don't
have the time for detective work, just mail me the error output of the
compiler.

Running:
	* Have you backed up your .newsrc recently?  If not, do so.
	  (1/8 :-)
[1/10/93: change the above to 1/32768 :-]

	* First of all, are you sure it's a bug?  Look at the online
help and the documentation files for more information on a command.
Some of the commands may seem counterintuitive at first, and with all
the new modes in STRN there is bound to be some confusion.

	* Next, if possible, try to reproduce the error.  Even just
knowing that an error is reproducible is very helpful.  

	* A good bug report should consist of enough information so
that I know what went wrong, and hopefully enough information to fix
it.  Please tell me what you *thought* should have happened, so that I
can know when I've fixed the problem (or if the problem is really a
feature :-).
