Ref: 10860030
Title: Some causes for "RDY Timeout" LCD error message
Date: 7/29/88

Copyright 3Com Corporation, 1991.  All rights reserved.

Here are some of the different situations that have been known to
produce the error message "RDY Timeout" on the LCD.  It's been known
to appear as the result of hardware and software problems alike, so
troubleshooting it has always been difficult.

1.  Using only Appletalk on a 3Server3 and not having a loopback on
the BNC connector.

2.  Using Token cabling on a 3Server3 and not having a loopback on the
BNC connector.

3.  Increasing the Eth buffers on a 3Server3 and over-allocating the
available memory.

4.  ACME hardware problem/failure.

5.  Badly seated 82186 and/or 82586 chips on ACME.

6.  Timing problem between the processor (82186) and coprocessor
(82586) chips.

7.  Problem loading the system files on a 3Server3 - similar to INT6
problem.

In one other case, RDY Timeout was caused by the following:  the
customer upgraded his 3Server to a 3Server3, had an old ADSI tape unit
with the jumper on J1 (should be J2) and no terminator on the back of
the unit (required terminator).  He was able to erase tapes and start
a backup but a couple of minutes into the backup it would die with a
RDY TIMEOUT.  He could usually recover by rebooting but one time had
to do a CHKDSK in Console in order to be able to reboot.  He had
"protected" his boot files from INT 6 by making them read-only (in
case this has any bearing).  When we changed the jumper and put the
terminator back on everything worked fine.  Before that the RDY TIME
OUT was always replicable.
