Paul, at 22:50 on Jan 26 1996, you wrote to Bill Grimsley...

PE> I am now getting statistics, but I have to actually put those
PE> ATI commands on separate lines.  :-(  Also, would you care to
PE> explain the "2400" in the stats?  Oh, and a reason for the
PE> retrain failure would be nice too.  Considering two USRs and
PE> all that.  BFN.  Paul.

Something is VERY wrong at your end, Paul.

PE> # 26 Jan 22:19:29.40   CONNECT 28800/ARQ/V34/LAPM/V42BIS

OK so far.

PE> 26 Jan 22:23:05.75   CPS: 3346 (676027 bytes)  Efficiency: 116%

An excellent result, although Dave also runs a V.34+ Courier, so why not a
33k6 connect (or perhaps you got his Viper instead) ?

PE> 26 Jan 22:24:57.69   for some reason, ZCRCW is error
PE> 26 Jan 22:27:52.22   lost zmodem carrier
PE> 26 Jan 22:27:52.22   Zmodem Recv Problem  ???

I don't know what this means, nor which end would have dropped carrier.

PE> 26 Jan 22:27:52.40   string is ~~ATI11|~~ATI6|

Do you need the first CR character?  ~~ATI11~~I6| should work fine.

PE> # 26 Jan 22:27:56.69   Modulation               V.34+

Seems you did get Dave's Courier after all.

PE> # 26 Jan 22:27:56.72   Carrier Freq (Hz)        44672/44672
PE> # 26 Jan 22:27:56.72   Symbol Rate              48905/48905

Those figures are complete bullshit.  ISDN lines perhaps?  :)

PE> # 26 Jan 22:27:56.84   Recv/Xmit Level (-dB)    28/17

A tad low on Xmit, but still well within tolerance.

PE> # 26 Jan 22:27:56.87   Roundtrip Delay (msec)   0

That's bullshit too.  0mS delay is impossible.

PE> # 26 Jan 22:27:57.28   Speed                  21600/2400

The first figure is your receive rate, the other is sending speed.  Given
the rest of your stats, I wouldn't believe any of it, especially with the
cps rates you achieved, which were quite normal for a 28k8 connect.

PE> # 26 Jan 22:27:57.31   Disconnect Reason is Unable to Retrain

Don't believe that either.

It seems to me that there is something not quite right with your setup (I'm
very loath to immediately blame the modem, although I'd like to see you try
another one, to be absolutely certain).  Are you using SIO, and if so, what
version?  Some are said to be quite buggy, although I've had NO problems
with 1.40 or 1.45 here.  Also, are you using EXACTLY the same MODE command
as I mentioned earlier?  If not, try changing it.

Something else I'd be checking is your serial I/O card, just in case the
storm damaged it somehow when it took out your Spirit.  The bottom line is
that you are experiencing strange problems which nobody else has ever
reported, and whilst it's not inconceivable that the modem is faulty, the
fact that the 100s I tested (and used) at CHH lead me to believe that this
is probably not the case at all.

A serious suggestion:  Do you want to swap modems for a few days?  If my
Sportster exhibits similar problems at your end, that will virtually
eliminate the modem as being the cause, as I know for a fact that this
modem is rock-solid here (as have been the Couriers I've used here as
well).

Sorry, but I simply don't know what else to suggest.

Regards, Bill

--- Msgedsq/2 3.20