BNU PHASE 4 status messages

There are six BNU PHASE 4 status messages. The following table decribes them.

Item	Description
`Startup Failed` `Remote reject after login`	After login, the uucico daemon is started on the remote system. If there is a problem initiating a conversation between the two systems, these messages are created. You might have also logged into the incorrect BNU account or the initial handshake failed.
`Wrong machine name`	A machine was called incorrectly or the machine name was changed.
`Bad login/machine combination`	The login to the remote system failed. The problem could be an incorrect phone number, an incorrect login or password, or an error in the chat script.
`Remote has a LCK file for me`	Both systems were simultaneously trying to call each other. The local request will fail temporarily.
`OK` `Talking`	These are informative messages only and do not indicate an error.
`LOGIN:` `PASSWORD:`	If the login or password prompt is in all capital letters, the modem might be in echo mode (E1 on Hayes compatibles). This causes the modem to echo back, or send, a RING to your system when an incoming call is received. The getty command receives the string and accordingly changes the `login:` or `password:` into all caps. Change the echo mode on the modem to off (use `ATE0` for Hayes compatibles). Note: Keep in mind that once this change is made, you should use `ATE1` in the chat script of your Dialers files, or you will not get the expected `OK` back from the modem. If the remote port is set for `delay` or `getty -r` and the chat script expects key input, then the ports set for `delay` are expecting one or more carriage returns before proceeding with the login. Try beginning the chat script on the dialing system with the following: `"" \r\d\r\d\r\d\r in:--in: ...` Interpreted, this chat script reads as follows: expect nothing, send return, delay, return, delay, return, delay, return.