On Thursday August 01 1996, Vicki Crawford wrote to John Piper ...

 JP> I have a new user logging on now. He's just completed the new user
 JP> registration questionnaire, and when asked what sort of modem he has
 JP> he entered Spirit Viper V.34. Yet despite this, he only connected to
 JP> my Courier at 2400/ARQ/V34/LAPM.

 VC> He hasn't changed his dialling directory speed for his modem to 38400. The
 VC> /ARQ/V34/LAPM are the clues that he has a high-speed modem. The 2400 shows
 VC> he has his software speed set wrong.

There you go. Of course, the /V34 was an indication that the caller had a
V.34 modem, but I didn't realise the slow 2400 connect speed could be
attributed to
something as silly as an incorrect baud rate setting in a dialling directory.

Some terms are clumsy in that they don't adjust the default dialling
directory baud rate field when they detect a high speed modem.

I don't use any of these clumsy programs; I use FrontDoor 2.20c.mL's
terminal, and I dial systems straight from the nodelist. :-)

 JP> Has anyone else experienced such a slow connect speed between
 JP> Spirit Vipers and Couriers? Trev?

Trev didn't, BTW. :-)

 VC> Nothing to do with it. I just polled you with my Spirit Viper 33.6

 VC> 01 Aug 06:32:16 BINK Processing node 3:712/841 -- Lateline Bbs
 VC> 01 Aug 06:32:16 BINK Dialing 02-9579-6564
 VC> 01 Aug 06:32:38 BINK Carrier 31200
 VC> 01 Aug 06:32:38 BINK Protocol: Lap-M
 VC> 01 Aug 06:32:38 BINK Compression: V.42Bis
 VC> 01 Aug 06:32:38 BINK Connect 31200

 VC> We got a 31200 connection.

=  6:58:13  CONNECT 26400/ARQ/V34/LAPM/V42BIS
+  6:58:18  Computer Connection, 3:800/809

Reported here as 26.4k. You weren't connected long enough for the modems to
speed shift though. I wonder why our logs are reporting different speeds.

John (japp{at}mpx.com.au)

--- FMail/386 1.02+