>>> 'tycom9900' problem from jchung -- Tue Jul  4 13:35:00 1989 <<<

This is the same problem reported by bob as in terminals.
The tycom does not function.  No programs can be loaded
or tubes monitored either from the terminal or over the remote connection.

>>> 'tycom9900' problem from jchung -- Tue Jul  4 13:38:04 1989 <<<

Disregard previous message.
The tycom9900 is up and running.

Sorry for the confusion

>>> 'tycom9900' problem from field -- Fri Jul 21 13:34:28 1989 <<<

Can not look at status of furnace using remote option.  It's been
this way for about an hour.
I get an error message about tytalk instead of a connection.

>>> 'tycom9900' problem from bob -- Fri Jul 21 14:39:43 1989 <<<

tytalk, and the terminal in the front of the lab and the office are
all talking. The origin of Leslies complaint cannot be traced. 
tycom9900 is up.

>>> 'tycom9900' problem from voros -- Fri Jul 21 15:06:04 1989 <<<

Leslie tried tytalk from a terminal in 373, where it did not work.

>>> 'tycom9900' problem from mudie -- Fri Jul 21 16:54:30 1989 <<<

krypton was down earlier this afternoon; I rebooted it and tytalk
came back.

>>> 'tycom9900' problem from field -- Tue Feb  6 16:17:59 1990 <<<

I notice that today when the tycom terminal by the tylans is
asked for a host task to give the status of all the furnaces 
it gets some sort of system error as soon as it has listed the
status of tylans 1-3 and can not complete the task.

>>> 'tycom9900' problem from evan -- Wed Feb  7 14:16:16 1990 <<<

problem: Equipment Communications on tytalk aborting on a system status readout
at tylan4.
cause: tylan4 in reset STNBY.  this gives ********* as the process id.
       this must confuse the tytalk program.
solution: loaded START4 in tylan4.  tytalk working again

This problem will be reported on equipcom problems so programmers can fix the
software.
