🚀 go-pugleaf

I did not see the origional problem, but from the responses, it seems to 
sound like a problem I had on my 3B2/400.

Symtoms:

At all terminals including console - Characters you type would not be echoed
back (i.e. not read).  Repeated typing of a character might echo 1 in 10 times.
When echoing occured, sometimes groups of 3 & 4 characters would go through
at one time.

Cause:
We had a US Robotics modem connected to the contty port.  The modem was set
to echo characters sent from computer to pace the dialing strings.  The DCD
line was tied high so the 3B2 would talk to the modem.  If the current user
broke the connection without ^D (i.e. did not log off) the computer could
not tell since the DCD line was tied high.  The modem echoed DISCONNECT^m.
The computer echoed DISCONNECT not found -- which was echoed back by the
modem -- which was echoed back by the computer in addition to another
DISCONNECT not found -- .............
Soon there is a olympic caliber event to see who will give up first, the
computer or the modem.  The result to the rest of the users on the system is
no input buffers to read into.

Solution:
1. If this happens, check to see if the transmit are recieve lights are on
	solid while the OH (off hook) light is out.  If this is the case, turn
	off teh modem for a while to wait for the 3B2 to flush its buffers.
	Everything should come back to normal.

2. Turn of the command echo in the modem.  I don't think you need it anyway.
	The session will still be live after the connection is broken, but after
	the DISCONNECT not found, the line is idle.

This had caused me no end of headaches until i figured it out.  Any comments
on what I observed are welcome.

Metro T. Sauper, Jr.
ihnp4!ll1!bpa!asi!metro