| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Another oddity |
Had another example of an odd session this am, the first call I made today, at 06:24. I had seen one before, 07:33 24-Mar, but didnt realise it was odd till after it was over, past when I could watch the status on the first one. The important symptom is significantly reduced thruput, producing typically a 950cps thruput instead of the more usual 1650. On the previous occasion I wasnt completely sure that I had had a 14400 session right thru, but this time I am certain it was. The only real indication on the status display is that the Rx light is a continuously on with the dud calls. Normally its got a noticeable blink as the modem sends the received chars out to the PC in bursts of bytes at a rather higher baud rate than the 14400 over the phone line. Not at all clear whats actually happening to produce the slow thruput, and the second call of the day with nothing changed at all was normal. It affects BOTH directions too, so something is presumably odd about the the detail of the LAPM session the modems have defaulted down to. Odd too in that the uncompressed PKT from me to you is the SAME speed as the archived PKTs from you to me. Normally my outgoing ones are well over the 3000cps as the V42bis compresses them. I'm basically asking if the more detailed diag display at your end on what got negotiated has anything useful on that stuff. I've also had atleast two calls which managed to start off at 7200, and fell forward to 9600 and then to 14400 thru the call. One on 31-Mar, another at 07:16 19-Mar. I basically let these go to see what happens, and the M34F is rather slow to decide it can step up. It does so fine when it decides to tho. I didnt have any useful comments to make on the NETCOM.* file. Are the CRCs correlated with particular people ? That would presumably mean that either you always did have some with them, or their config has gone dud. Its not hard to generate interrupt latency CRCs, nothing to do with any modem problem tho. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.