> NP> That's what I am talking about.  CRC error at 25198
 > NP>                                  CRC error at 47910....etc

 > NP> They chances of their appearance depends on Who I am calling.
 > NP> From Teddy (same exchange) 4 crc errors in 90k
 > NP> From Brisbane             no crc errors in 2.8 MEG

 > Thats interesting. Corse its possible that its just Teddys
 > system thats fucking up too, not yours. You would think that
 > it would be yours since you see the problem with others tho.

 > NP> It appears to be WHO I call

On a second checking, it seems to relate to the time I am calling, which
gave the appoearance of who I was calling.  Definitely a line/exchange
problem.


 > Which also supports the proposition that its them. Particularly when
 > Paul now says they appear to have gone from his callers now. Are you
 > still getting CRC errors with Paul now that he has upgraded Bink ?

Not for two calls, then on the third it cropped up badly. CRC error and the
"Nonsense end of file received. Ignored"


 > RS> Are you saying you get them even with plain old single tasking DOS ?

 > NP> YEP !!!

Will check again this week.


 > NP> Down here, it appears to be more of a line problem
 > NP> than an operating system problem

 > RS> It shouldnt be if you achieving LAPM or MNP4 sessions. That error
 > RS> correction should be complete transparent between the modems and you
 > RS> shouldnt see any CRC errors at the file transfer protocol level at all.

CONNECT 14400 /LAPM/ v42 bis


 > Yes, but we dont know that thats due to LINE ERRORS. The should be being
 > transparently fixed between the modems by the LAPM error correction and
 > not visible as CRC errors on the ZedZap status screen at al.

They appear.  Teddy cps rate is always down 1500's.
 Others are 1615 - 1670 cps


 > NP> Doesn't the sportshoe internal have it own? or a virtual one oe sumfin?
 > Its got a real one, you can see it on the board.

Hadn't looked

 > NP> Anyway ... All 4 com ports have 16550's

 > Yeah, cant be that. There is a slight possibility that you have
 > an interrupt latency problem due to a cache particularly, but that
 > shouldnt normally give varying results depending on who you call.

Soon to have a dedicated 3meg HD cache on the controller.


 > Looks more likely it the system you are calling with the problem. And
 > pretty convincing evidence if you no longer get CRC errors with Paul.

Unfortunate they are still there occassionally.

Cheers
Niels Petersen

--- FMail/386 0.98