*** Connect request: call1 [via call2[,call3...,call9]]
Your PK-232 has received but not accepted a connect request from a
distant station.
*** DISCONNECTED: (call sign)
Your PK-232 has switched to the disconnected state. This message may
be preceded by a message explaining the reason for the disconnect.
*** Retry count exceeded
*** DISCONNECTED: <call sign>
Your PK-232 has been disconnected because of a retry failure, rather
than a disconnect request from one of the stations.
*** <call sign> busy
*** DISCONNECTED: <call sign>
Your connect request was rejected by a busy signal from another
station.
FRMR sent: xx xx xx or FRMR rcvd: xx xx xx
Your PK-232 is connected but a protocol error has occurred. Your
PK-232 is trying to re-synchronize frame numbers with the distant
station's packet system. The string xx xx xx is replaced with the hex
codes for the three bytes sent in the FRMR frame.
A.4.5 MailDrop Error Messages
The following messages appear as a result of entering an invalid or
unrecognized command to the PK-232's MailDrop.
*** What?
You have entered a command that the MailDrop does not recognize.
*** Need callsign.
You have tried to send a message but not specified who you want to
send it to.
*** Message not found.
You have tried to List or Read message(s) that the MailDrop could not
find. This also appears if you try to List messages when there are no
messages in your MailDrop.
*** No free memory.
You have tried to send a message, but the MailDrop does not have any
memory for more messages. You must Kill messages to make room.
*** Not your message.
A remote user will get this when trying to read a message number that
is addressed to another station.
4/91 A-7
