BG> Aftercall 28 ~~ATI11~~I6|

PE> Here is what I have, that gives me nothing more exciting than a 0...

PE> Port      3
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.  Suggest also 

I don't transfer uncompressed files, all my mail is prepacked.
57600 will not give me anything that 38400 won't.  Also, 38400
should be less strain on my computer I have been told.

BG> that you add the Predial and Preinit commands as well.

PE> Carrier   80
PE> Init      ATZ|
PE> TermInit  ATZ|
PE> Prefix    ATDT
PE> Busy      AT&D0 H1|

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.

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

PE> Answer    ATA|
PE> Aftercall 35 ATI6|

BG> Try running the Aftercall statement EXACTLY the same as mine is listed 
BG> above, bearing in mind also, that the first figure relates to the expected 
BG> number of lines in the logged response.  Note also the delay in the 
BG> command, which was put in for a reason (although I forget exactly what that 
BG> reason was now).  :)

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

BFN.  Paul.
@EOT:

---