BG> Given my own long-term results, and bearing in mind that
BG> everywhere else I call is at 28800 straight up, I suspect
BG> that there could be a line problem at PE's end.

RS> Clutching as straws Bill, particularly with
RS> a 2400 connect. Dont believe it. 14400 either.

BG> Then why has nobody else complained?  Given the number of Couriers in use 
BG> on BBSs these days, I'd have expected to see the odd similar complaint pop 
BG> up from time to time, but I haven't.  Not once.

Hey Brenton.  Remember when I had almost got to the stage of telling
the TCXL author that his mother was a whore, when NO-ONE would
listen to me that there was a bug in TCXL, which was evident in
EVERY SINGLE ONE of their bloody applications, and NO-ONE else
complained about it except me?  The cursor was jumping back and
forth in an input field.  After telling a few thousand people
that they were dickheads, I finally got someone else to see it,
and they told me to tell all my customers to use an AT instead
of an XT so that the cursor would jump too fast to see.

And for the author himself, I actually had to debug the code, find
the spot that was causing the problem, and then stick in a delay
so that he could see it for himself like dogs balls, and then I
came up with a coding solution as well, which THEN he implemented.

Jesus fucking Christ.

BG> Dunno if you read the USR_MODEMS echo, but I know you read AUST_MODEMS,
BG> and nobody else has EVER reported similar problems with the Courier.

Dunno if you've ever read the SPIRIT_SUPPORT echo, but nobody has
EVER reported double-sending to a Maestro SE 9600, and nobody had
EVER reported double-sending to ANY modem until I rocked up and
started whacking people with dead fish.  It's always the way,
Brenton.  There are some who call a dead fish a dead fish, and there
are others who live in cuckoo land.  BFN.  Paul.
@EOT:

---