david, at 19:23 on Mar 19 1996, you wrote to Bill Grimsley...

BG> You're joking!  So doesn't the connect string appear on just one line
BG> then, the same as the USR?

db> With \V1, it does.  With \V9, you get:

Ah, right, that's what we saw, but then we had \V9 enabled as well.

db> You can't blame the M34F for all these dolts running around ignoring TFM?  
db> BTW, for those who didn't already know, the Programmer's Society at the 
db> University of Technology, Sydney (UTS) actually *publishes* TFM!  :-)

And they're not even worth the paper on which they're printed, if nobody
bothers reading them.  Indeed, all we had were the on-line help screens, no
manual in sight at all.

BG> In fact, how exactly IS it reported on the M34F?

db> See above - with \V1, you only get the last "CONNECT
28800..." line at the 
db> bottom.

OK, so it's just a straight DCE value, no EC or compression data at all.

BG> The on-line help screens actually detail a number of different
BG> methods which can be used, but that's an even worse "quirk" than the
BG> USR's ATZ anomaly.

db> It's called flexibility.  You want fewer options, then what for you using a 
db> USR, eh?  ;-)

All modems work much the same though, with the real differences being in
the manner in which their link diagnostics are reported.  And their
accuracy.  :)

BG> What if you'd been doing a sched pollfeed to say somewhere
BG> in Zone 1 or Zone 2?  Urk!

db> The joys of fucking with modem configs without actually checking them, 
db> before entrusting them to unattended mode.  :-)

Easy to condemn in retrospect, but we've all been guilty of something like
that at least once in our modemming lives...

BG> So your EQM is once again between 17-19, and Rx signal level is -50dBm.

db> No it's not.  Ignore it, it's broken.  As I said some weeks ago.

If I'd known at the time that I'd have been using an M34F within a week or
two, I'd have made a note of those inherent problems, but as I didn't... 
:(

db> Bill, you gave me the impression that you were using an M34F for a test, 
db> too;  no, lemme guess .. just relieving yourself, eh?  :-) 

Davdi Drummond borrowed it from BHP for an extended test period, and
brought it around here last Saturday night for a bit of local testing.

db> If not, can you give me the full EPROM/Rockwell version numbers please (DD, 
db> same for you too, please - and Paul again, too) as I want to see if there 
db> are any differences before I mention this to NetComm.

Whilst I didn't make a note of everything, I *DO* recall that the M34F's
EPROM revision was 2.61L (does that sound right?), and that it was only
about three weeks old.  Here is the active profile I used when testing the
M34F here that night:

----------------------------------------------------------------------------
ACTIVE PROFILE
B0  E1 L0 M1 T Q0 R0 V1 W2 X5 &B4 &C1 &D2 &G0 &H0
&K3 &L0 &M0 &N1 &P1 &R0 &S1
&T4 &X0 &Y0 \A3 \B3 \J0 \K5 \N3 \T0 \V0 \X0 #A2 #B0 #C0 #D0 #E0
#F0 #I0 #J1
#K1 #M0 #N0 #O0 #Q0 #U0 #V1 %C2 %D0 %E1 %F1 %G0 %H0 %K0 %L13 %M0 %N0 %P0 %R0
%S0 %T0 %U0 %W0 *C0 -Q0 :E0
S000:000 S002:043 S003:013 S004:010 S005:008 S006:004 S007:060 S008:004
S009:006 S010:018 S011:065 S012:050 S018:000 S025:005 S026:000 S030:000
S033:003 S042:000 S043:015 S045:098 S047:008 S066:010 S067:042 S069:060
---------------------------------------------------------------------------

The only changes from a normal AT&F. were as follows...

      L0 = Minimum speaker volume level
       T = DTMF Tone dialling
     &D2 = Modem follows state of DTR
     &K3 = CTS/RTS Flow Control (not &K9)
     %C2 = Enable V.42bis but disable MNP-5
     \V9 = Extended response codes & diagnostics
     #C0 = Disable V.25 Call-Indicate tones
S000=000 = Disable modem's auto-answer 
S007=060 = Increase carrier wait delay
S011=065 = Faster DTMF dialling (65mS is fastest speed accepted)

(Note also that I did NOT attempt to force fixed Tx levels at all)

Regards, Bill

--- Msgedsq/2 3.20