The bugs with retrains and "flashing 3's" appeared in earnest in 1.440-09
and 1.440-4 or -7 were the least problematic and didn't have the 9600 problem.
>Second, if you call Supra, and press 0, be nice :) Michelle is the girl who
>usually answers and I know her personally. She is very nice, and good
>looking too. *big smile*
Never called, but I got one of the more knowledgable types via e-mail.
Response time less than 2 hours back and forth serveral times.
>Basically, the 1440-22's (23 is out now too) works pretty well here on the
>few modems we are using it on. The 1440-12's STINK! :)
Currently I have found that 1440-18 is the best. My prior message to David
stated that 16 out of 50 were hung "flashing 3's" and I did say that I could
consider it 16 out of 40. The other 10 were flashed to 1.440-12 via flasher
and then x-modem'd up to -18, but the others were x-modem'd to -23 and later
x-modem'd to -18 due to the fact that -23 was worse.
One thing that will state is that if you are downgrading, do so to the last
flasher and if you are downgrading to previous beta DO NOT x-modem.
Considering the possible combinations that I have tried it didn't work prior
to -12 and still does not work this way. Sure 2 steps is a hassle, but the
problems are not worth the easy way.
Upgrading does not have the same problem.
Those 10 running -18 experience almost no retrains that drop and almost
never go "flashing 3" at any time.
Some other observations:
After a user disconnects, the modem will reset itself (&D3) and immediate go
"flashing 3."
Following up on that. Modems that are in a "flashing 3" state immediate on
disconnect can have a PPP Term Req in the log.
Setting the +ms to 11,1,9600,33600 has absolutely no effect on the "flashing
3" problem.
In the past I was wondering if the "flashing 3" phenomena was due to some
interaction with the PM's, but I have 10 that work just fine. Same every
thing except for my prior oberservations on flashing them up and down.
Adding to the prior statement, there have been 2 times that I have reset the
ports (or a port) on a PM and modems started "flashing 3" after the 'res al'
and in one case I had just taken the cover off the PM (for a memory upgrade)
and reset the ports prior to pulling the plug (so that there would a be
terminate log). At the time 2 users were connected and after the 'res al'
suddenly 4 modems were "flashing 3" and none of the 4 were modems that the 2
users were connected to.
While not as much of a problem, retrains started late in the 33.6 beta and
are still present in -23, but seems much less frequent in -18 and will
sometimes hang past the 90 second limit imposed with -16, I believe.
The PM's involved are running 3.3.2c1 and there was no change with 3.3.3
which has 30 of the more prolematic 40 Supras.
AT&F2M0Q2W2&D3S0=1S2=255S25=50&W&W1 is the current IS that I use and +MS is
set manually port by port to 11,1,9600,33600 for the reason that it will not
"take" if added to the string, even if it were AT&F2+MS=11,1,9600,33600.
The S25 setting made no significant difference. The W2 is only usefull when
I dial out/in for testing (I do know what the DTE is, senseless default) and
the Q2 could be dropped, but I prefer the modems to send response codes only
when the PM sends commands.
I do not keep the modem setting on, but so a 'set al mo' after set the IS.
Otherwise the +MS settings would clear.
All ports are set to 115200 and setting them to 57600 made no difference.
This is by no means a complete list of all the possibilities I have ever
tried, but 10-20 modems would be tried for various flashes and IS changes
for at least a week.
Quite simply I am all flashed out, but would consider any others feedback
usefull when I contact Supra about what appears to be a DTR toggle problem.
Otherwise if you want 33.6 on a Supra use 1.440-18, as some of the prior
version had incorrect display problem. Like a 21.6/31.2 connect, while
possible, not very plausable.
Any of those from Livingston that frequent the list and have heard anything
would be much appreciated. While I don't think the PM causes this, it *may*
have something to do with the problem when it toggles DTR.
After I run the 10 that will be retrograding to -12 and then -18 have run
this week, Supra will be hearing from me with what I have observer. Just
hope that no new ROM is out or I know what they will say.
"They've been flashed so many times it doesn't even faze them."
------------
Jeff Mountin
sysop@mixcom.com
MIX Communications
Serving the Internet since 1990
Sure my business card says "Senior Network Administrator"
They still make me do just about anything.