TIP: Click on subject to list as thread! ANSI
echo: aust_modem
to: Ian Smith
from: David Drummond
date: 1997-01-08 06:21:54
subject: Specifics on modem retraining

Ian, at 10:54 on Jan 06 1997, you wrote to David Drummond ...

LD>> The Courier has defined 'retrain disabled' to mean reject
LD>> remote request.

DD>> Disabled does mean not enabled doesn't it?

IS> In the case of Rockwells, it's not so binary.  Have an 
IS> anotated quote:

. . .[chomp]. . .

IS> [actually, modem will _request_ fallback, then do so if the 
IS> other end agrees.  What it doesn't mention is that the modem 
IS> will also respond to requests from the _other_ end to 
IS> fallback, but it will also respond to fallforward requests 
IS> (though it won't _initiate_ fallforward requests, differing 
IS> from %E2)]

. . .[chomp]. . .

LD>> My modem and others has defined 'retrain
LD>> disabled' to mean accept remote request but not initiate
LD>> request.

DD>> What's the point of that?

IS> Finer control, or allowing control by one end of a link, can 
IS> stop 'hunting', where the two modems are madly sending each 
IS> other fallback/forward requests, from differing perceptions 
IS> of the current line quality for a given bitrate.

LD>> Having the Courier hang up 'in disgust' seems to be quite
LD>> illogical compared to the way my modem handles it.

IS> That sounds the same or similar to the Rockwell %E0 
IS> behaviour, above, though I'm not sure that's what David 
IS> meant exactly.  This is just a terminology misunderstanding, 
IS> methinks ..

DD>> I guess the courier feels that if a retrain is necessary
DD>> and the other end can't comply, there is no point in
DD>> continuing the connection.

IS> Yes, and the Rockwell would do that too, if the Courier 
IS> refused its request, after trying 'x' retrains.  Not sure 
IS> what 'x' is, though I don't think it's externally adjustable 
IS> in the Rockwells .. is it in the Couriers?

DD>> I can't imagine why one would want to disable retrains (in
DD>> any form) anyway...

IS> As I've said a few times recently, disabling _fallforward_ 
IS> requests in some Rockwells (ie, using %E1 instead of %E2) 
IS> can and has solved problems on bad lines, especially 
IS> _really_ bad lines, which most 'slickers have never seen.

With ASL doesn't it make sense that both ends have some sort of control?

David
@EOT:

--- Msgedsq/2 3.10
* Origin: JabberWOCky CBCS +61 7 3868 1597 (3:640/305)
SEEN-BY: 50/99 54/99 620/243 623/630 681 640/201 206 230 305 306 311 702 820
SEEN-BY: 640/821 822 823 829 711/401 410 413 430 808 809 899 932 934 712/311
SEEN-BY: 712/407 505 506 517 623 624 628 704 841 888 713/317 714/906 772/20
SEEN-BY: 800/1
@PATH: 640/305 820 712/624 711/808 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™.