1) Term doesn't work! Why not!!

	This is one of the most tremendously useful questions I have
ever been asked. You will notice that it contains all the pertinent
information I might want to know, like what version of term they are
using, and exactly what the symptoms are, and what machine they are
running it on, and what they have tried, etc etc. However here are a
few things to try before mailing me with details. :)

	a) Create a ~/.term/termrc file at both ends with the two
lines "escape 0-31" and "escape 128-159" in it. Then try term. If this
work, try shortening the ranges as much as possible. Experience
indicates that most people will be able to get away with either
nothing, or "escape 17" and "escape 19", or escaping 17, 19, 145 and
147. 

	b) If 'a' doesn't work, it's possible that you have a
seven-bit line. Try using a termrc with the two lines.. "sevenbit"
and "escape 0-31" in it. It is important to know that the termrc at
each end must have 'sevenbit' in it.

2) Term doesn't run as fast as it should. Why not??

	Several ways to speed up term. Here are the most common...
	a) Escape as few characters as possible. escaping 32 characters will
cut thru-put by about 12-15%.

	b) If you escape a character on one end, add a corresponding 'ignore'
on the other. I.e. if you 'escape 17' on the remote end, put a 'ignore 17'
on the local end.

3) 'txconn' doesn't seem to work.

	a) Make sure you have 'xhost +' on both machines.

	b) X windows take awhile to open, be patient.

	c) Make sure you are running txconn on your remote machine, not your
local machine.

        d) Try instead "tredir 6009 6000"

4) X windows take a long time to open, and then run very slowly.

	a) Try picking up a copy of sxpc from sunsite.unc.edu.  Don't ask
me how to install it, I've never used it.

	b) Try compiling your favorite X applications on your home machine.

	c) X11R6 will contain its own compression protocol, so don't expect
'sxpc' to be incorporated into term.

5) Trsh just hangs when I execute it.

	Trsh is an endless source of problems.

	a) Try using something simple like:

	       	trsh -s echo trsh works in simple mode

	If this works, then you can use "trsh" with the "-s" option.  Try
defining NO_PTYEXEC in config.h and recompiling.

	b) Try using telnet instead.  i.e. Do once "tredir 4023 23".  Then
you should be able to connect with the command "telnet localhost 4023".  If
this works, you may wish to recompile telnet with the instructions in 
README.porting, so you don't have to do the tredir command every time you
establish a term connection.

6) Is there a Linux mailing list?  Yes there is, it is a channel of
the linux-activists stuff.  Try mailing:

  echo X-Mn-Admin: join term | mail linux-activists-request@niksula.hut.fi

A help file is available upon request from the same address.


