Table of Contents
Advertisement
Occasionally, the modem gives a burst of errors.
The telephone line may be noisy or bad.
Hang up the call and try to connect again for getting a
better telephone line.
If there are other telephones on the same line that
your modem is using, someone may have picked up a
telephone on that extension.
Your telephone line may have the call waiting feature.
Try adding '*70,' to your ATDT dialing command line.
If it doesn't help, ask your telephone company how to
disable it temporarily.
The modem gets errors in transmitted data randomly.
Try to use V.42 or MNP1-4 if possible.
Connect the modems at a slower baud rate.
After you download a file, it was not stored on your
disk drive.
If both modems are using MNP or V.42 protocol, then
the flow control may not be enabled.
Configure your software to use RTS/CTS flow control.
That will cause your computer to pause long enough
for the file to be stored to disk.
The text on the screen is not legible.
Your software settings may not match the settings on
the remote site.
Make sure your data bits, stop bits, and parity settings
match the settings that the other computer is using.
The two most common settings are: 8 data bits, None
parity, and 1 stop bit (8,N,1) or 7 data bits, Even parity,
and 1 stop bit (7,E,1).
If the telephone line is very noisy, you may see
corrupted data on your screen.
Due to poor telephone line conditions, the modem
may have fallen back to a slower communication
speed. You may need to change the baud rate setting
in your software to match this slower speed. To return
- 26 -
Advertisement
Table of Contents
