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
useing, and exactly what the symtoms 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 escapeing 17, 19, 145 and
147. 

	b) If 'a' doesn't work, it's possible that you have a
seven-bit line. Try useing 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. escapeing 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) Term occassionally drops from 1650cps to 600cps for long periods of
 time.

	I really don't understand this problem, but there is a workaround.
I have this problem for outgoing data from my Linux box, and use the following
termrc to work around it:

window 9
timeout 35
chdir /
baudrate 17000
breakout 48
compress on
retrain on

The "retrain on" option recovers the modem after I have errors.  The 
"baudrate 17000" reduces the occurences of this error.

4) '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"

5) 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 it's own compression protocal, so don't expect
'sxpc' to be incorperated into term.

6) Trsh just hangs when I execute it.

	Trsh is an endless source of problems.

	a) First try defining NO_PTYEXEC.  If this works mail me a message
so I can update your OS definition to include this.

	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.termnet, so you don't have to do the tredir command everytime you
establish a term connection.

8) Why is term11x slower than term108???

	Try increasing your "window" value and "timeout", or using "retrain on".

9) Why doesn't "tredir" work anymore?

	a) If it reports 's = -1', chances are your /etc/hosts file is wrong.  If you have a network
connection, this file should list the correct IP #, otherwise it should list
127.0.0.1 as your IP #.

	b) If it reports "Port is already bound" then check for some other 
process or a listing in /etc/inetd.conf binding the socket.

10) What should I list in my local /etc/hosts file?

	If you don't have an Eathernet card, just list localhost and your
hostname with IP # 127.0.0.1.  Any host listed in /etc/hosts will not be
accessable by the local termnet library!!!


                                   Bill


