Paul, at 21:44 on Feb 03 1996, you wrote to david begley ...

PE>> No, I expect that David Begley would have managed to get at
PE>> least one 28800 connect though, instead of locked it at 
PE>> 26400 first time every time.  BFN.  Paul.

db>> I've tried disabling calling tones, disabling V.34 (V.FC 
db>> only), locking originating speed to 28.8Kbps .. no go, it 
db>> either fails to connect or connects at a lower speed.

PE> Ok, well at least that stuff was just testing then!

db>> I'm using the top-of-the-line NetComm with the newest EPROM 
db>> revision.  I can connect not only to other NetComms at top 
db>> speed, but also to the whacky V.34 chips in the AscendMAX 
db>> boxes.

db>> Connection to USR modems at 28.8Kbps seems a lost cause, 
db>> though.  As has 

PE> You see, I have an additional problem.  If I buy a Netcomm,
PE> then I would like it to connect to the REAL WORLD modem
PE> called "USR Courier".  Which means regardless of who is to
PE> blame, the Netcomm is already not up to scratch.  Which 
PE> means I would have to try again, by getting an unknown
PE> brand modem for $300.  It's a tough call.  However, the
PE> modem in ANSWER mode is what is most important in this
PE> case, and I have no data on how the Netcomm fares in answer
PE> mode, except for the tests done by the ISP I know.

db>> been said already, connect speed is not necessarily an 
db>> indication of the connection speed for the entire session, 
db>> though.

PE> The USR stats tell me that, and it is indeed 26400 
PE> throughout. BFN.  Paul.

One of my downfeeds has a yum-cha "Active" branded external V.34
modem.  It connects here 98% of the time at 28,800 V.34.  The first one he
got wouldn't connect at V.34 (only V.FC) so he swapped it for another.  I
don't know if it connects with Netcomms at 28,800 V.34 

He is quite happy with it.

David
@EOT:

--- Msgedsq/2 3.10