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

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.

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

PE> 9. When I try to put either of these commands into binkley.cfg,
PE> to answer the phone with adaptive answer...
PE> Answer AT+FCLASS=2;+FAE=1;+FCR=1;A|
PE> Answer AT+FCLASS=2;+FAA=1;+FCR=1;A|
PE> it fails to recognize a data call.  In other words, adaptive answer
PE> does not appear to work as "documented".

BG> I'm not surprised.  You followed the manual (which is clearly wrong), and 
BG> also appear to have entered the command strings incorrectly.  Don't quote 
BG> me, but I read somewhere that you need to use the "/"
character with AA in 
BG> Bink.  I paid little attention at the time though, as I wasn't interested.

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

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.

It's pretty good on the whole.  Even the non-EC connects from
USRs at least succeed.  BFN.  Paul.
@EOT:

---