Paul, at 12:02 on Jan 26 1996, you wrote to Bill Grimsley...

PE> Baud      38400

BG> Why only 38400 ?  OS/2 is quite happy with 57600, and you then won't be 
BG> restricting uncompressed files to a maximum rate of 3840 cps. 

PE> I don't transfer uncompressed files, all my mail is prepacked.

But when I start calling at 33600 once my EPROM arrives, I won't be able to
DL at 4000 cps, because your port will be restricting it to a max of 3840
cps.

PE> 57600 will not give me anything that 38400 won't. 

Of course it will - it'll allow you to transfer compressed data at full
speed with 33600 connects (I've already logged speeds in excess of 4000 cps
here).

PE> Also, 38400 should be less strain on my computer I have been told.

That's crap Paul.  It's true on XTs perhaps, but not with the faster 486s,
which will happily MT with port speeds of even 115200.  Ask Rod.

BG> Why a Busy statement?  The modem should respond to BUSY on its own (mine 
BG> does).  I'd be highly inclined to comment this out and see how it goes.

PE> That is for when I exit Binkley and go and process mail.  That is
PE> so that YOU get a BUSY signal rather than having it RING out.

OK, I should have read the docs, I guess.  :)

BG> Note also the delay in the command, which was put in for a reason (although 
BG> I forget exactly what that reason was now).  :)

PE> A bug in the USR Courier I would assume.

No, it applied equally to all of my Sportsters.

PE> I have dialled manually, under both DOS and OS/2, and do get stats after a 
PE> call.  I have therefor added a delay to my string, and will see the results 
PE> of that.  I have adjusted the "bug list" appropriately.

Could it be anything to do with your running binkley with full logged stats
enabled?  All that info spewing forth...

Regards, Bill

--- Msgedsq/2 3.20