From Andrew Reid · 1996-03-30 14:37 · #72031 in ENET.SYSOP
Hello Neil, Replying to a message of Neil Atkinson to Mike Smith: NA> Ah, come on give the guy a chance, people moaned about CRC errors NA> whilst downloading there mail so what does this HUB do, he only goes NA> out and buys a US Robotics modem, this still did not cure the problem See below. NA> completely so he had BT out checking the lines. BT did their best but NA> still couldn't solve the problem. So guess what, the HUB paid for a NA> new digital line installed. FWIW, CRC errors aren't caused by poor lines or poor modems. CRC errors usually occurr when there's a problem with the serial port losing characters, which can be caused by lack of 16550UARTS, multitasking environments or incorrectly configured flow control. The only time you're likely to see bad lines give CRC errors is when you connect without error correction (MNP or V42bis), and that is *very* rare nowadays. Andrew. --- * Origin: QS, 01757-701785 (2:2502/18)