>On Fri, 7 May 1999, Conrad Rockenhaus wrote:
>
>> Does anyone have any idea on how to correct the Modem Retraining issues
>> with these modems? Does the latest ComOS Fix these issues?
>
>The latest does not completely fix the problem. I use &N31&U14 in
>addition to the rest of my dial string to limit the top end connection so
>it doesn't constantly try to retrain above what works.
I can confirm this here, as well. I tried removing my &N## from the
dial string, and find that the blasted modem still tries to retrain
too high, giving periods of 2 to 20 seconds of flow-stoppage everytime
this happens (every few minutes).
It -does- seem to disconnect less often when this happens, though, although
I still need to do some tests with a non-upgraded unit to be sure I'm not
just imagining this. If that is the case, then 3.8.2c2 at least makes this
problem less annoying. It would not surprise me to discover that the rest
of the problem can only be fixed by USR/3Com, and their (annoying) modem
upgrade "wizard" continues to tell me there is no update available for my
modem (USR 56K Voice FaxModem, external).
I am also going to be doing some tests to see if the other "standard"
USR init string tweaks are still useful/needed. (I have been using
"S32=3D34S13=3D64&N29".)
Michael Bryan
pmu@ursine.com
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-modems' in the body of the message.