Paul, at 13:34 on May 11 1996, you wrote to Bill Grimsley...

PE> Bill, this is a list of problems I found when trying to use the
PE> Viper, not a list of guaranteed Viper-at-fault ROM bugs.

I know, which is why I think it's rather unfair of you to be putting them
in a downloadable file, and suggesting that they're ALL bugs.  Just like
you did with the NetComm and the Courier.

PE> 2. A Netcomm M34F got a 26400 connect to me, whilst when I put
PE> an M34F online, it connects at 28800 all the time.

BG> Dunno that I'd actually call that a bug though.

PE> It is a problem.  What is the reason that I can't get 28800 solid?
PE> The lines certainly haven't changed just because I changed the
PE> modem.  That only leaves the modem to blame (could be either modem).

It may just be that one is slightly less aggressive then the other.  In
fact, I'd be pleased if the USR was like that too, as I'd sooner have a
26400/LAPM connect than a 28800/NONE.

BG> Don't quote me, but I read somewhere that you need to use the
"/" character 
BG> with AA in Bink.  I paid little attention at the time though, as I wasn't 
BG> interested.

PE> No, I was using a similar string with the Netcomm with no problem.
PE> No "/".

Does the manual offer any suggestions here?

BG> Most of those problems relate to the fuckwit who compiled the manual, and 
BG> it would appear that the modem itself is actually relatively bug-free.

PE> It's pretty good on the whole.  Even the non-EC connects from
PE> USRs at least succeed.

True, albeit at a slightly lower cps rate.  Not a problem when transferring
smallish mail packets though, and I can happily live with that (although
I'd STILL like to know exactly why it happens).

Regards, Bill

--- Msgedsq/2 3.20