Hi John,

JP> I am attack-dialling Paul Sanders's Dragon now to see what sort of
JP> connect my Courier manages to his modem.

JP>----------  Sun 22 Dec 96, FD 2.20c.mL; Task=1
JP>+  0:21:12  Event 0-{at}
JP>-  0:21:13  Preparing outbound mail
JP>+  0:21:17  Calling Dark Crystal #1, 3:639/104, 03-9761-8371
JP>=  0:21:23  RINGING
JP>=  0:21:36  CONNECT 31200/ARQ/V34/LAPM/V42BIS
JP>+  0:21:39  Dark Crystal, 3:639/104

JP>Not bad at all. I'm frankly surprised I connected at 31200. Given the
JP>distance between us, and the uncertainty of line wuality, that was quite
JP>a good connect to achieve from here to Basywater. I was hoping for
JP>33600, but 31200 was still quite desirable. Since I was only dropping
JP>off netmail, I wasn't connected for long enough to experience a speed
JP>shift, and even so, my mailer was in session at the time.

JP>Paul, what did your log report?
--------  Sat 21 Dec 96
22:49:33  Event 0-{at}
23:24:48  RING
23:25:01  CARRIER 33600
23:25:02  PROTOCOL: LAP-M
23:25:02  COMPRESSION: V.42BIS
23:25:02  CONNECT 33600
23:25:04  Lateline BBS (FMail Australia), 3:712/841
23:25:04  SysOp: John Piper
23:25:04  Using: FrontDoor 2.20c.m/AX0002B0
23:25:06  Rcvd C:\IM\FILE\UNSECURE\01005A93.PKT
23:25:06  Efficiency 39% (1339 bytes), 1339 Cps.
23:25:13  From 3:712/841,  0:09, 0.
(note the time difference - I do not use daylight saving on the BBS,
its in a time warp :) (oh, and my BBS runs a few minutes fast, must
fix that one day :)

It is more than likely that a speed shift would have happened if your
connect was for a little longer....


 cya later,

 Paul.

... Sad fact about Windows bashing is it's all true.
--- Ezycom V1.48g0 00f90034