Paul, at 12:27 on May 10 1996, you wrote to Bill Grimsley...

BG> Look what happened today; are you still running the Viper at your end?

PE> Indeed I am.  No adaptive answer either.

AA couldn't possibly have caused that problem anyway.

BG> # 10 May 06:39:31 BINK Connect 28800/V34/None

BG> Fucking weird, it worked fine for a week, then this.  Nothing in the stats 
BG> which would indicate a line problem either.  Anyway, at least the mail 
BG> packets transferred just fine both ways, no block or CRC errors, just a 
BG> slightly lower cps rate due to no bit-stripping (EC).

PE> Ok, all you're doing is confirming the same error I reported
PE> connecting to someone else's Viper. 

Same symptom, not necessarily the same error.  There is a difference.

PE> But don't worry, I reported the problem to USR technical support, and the 
PE> solution to the problem is to sing "Oh England, my
Lionheart" whilst 
PE> burying your head in the sand.  Apparently this fixes most of the other 
PE> USR problems too.  Certainly worth the $400 extra if you ask me.

Waddya mean EXTRA ?  The Courier cost me LESS than A$400 IN TOTAL !! 
Anyway Paul, as you profess to be so good at locating and curing bugs,
perhaps you'd care to explain why I've only ever seen 28800/NONE connects
with TML ?  I've called heaps of V.34 modems all over Australia (and a few
in the US), and have NEVER seen a non-EC connect anywhere but on your
board.  Same with DD as well, now that I think about it.  So what is
peculiar to YOUR situation that could possibly cause these non-EC connects,
I wonder ?

Don't worry, I'm not suggesting that the USR code isn't partly to blame,
but it does seem odd that it only happens with YOUR M34F and (very
infrequently) YOUR Viper, and so far, with nobody else's.  Poltergeists,
perhaps ?

Regards, Bill

--- Msgedsq/2 3.20