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.

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

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

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

119%?  I'd like to see that.  Did you do your stats on a large
(500k) file to get proper stats?

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

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

He agreed that it was more strain?  But can still cope anyway.  I
agree, I doubt that it would put >1% extra strain on my computer.
The main reason was I didn't think there was any point, even for 1%.

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.

BG> No, it applied equally to all of my Sportsters.

A generic USR bug then.  What a pity you didn't document it.

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.

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

Nah.  That stuff is completely independent.  BFN.  Paul.
@EOT:

---