PE> Telix sees the dropping of the ?TS line and puts "F" on the
PE> screen. You probably wouldn't have seen an "F" if you had set
PE> your port speed to 2400, as opposed to telling your modem to
PE> only connect at low speed.

BL> I had ***BOTH*** my port and Modem set at 2400. How else do you want
BL> me to do it? 

The other way to do it is to keep the port speed at 19200 or whatever you
normally use, and send a string to your modem to force the connect rate to
2400.

BL> I expect that my modem keeps sending CTS/RTS because I am
BL> overdriving ***YOUR*** modem (where all the trouble is).

The main problem I am experiencing is sending stuff to others at low
speeds.  I actually suspect a timeout problem in binkley at this stage.

BL> And I suspect you have the same problem in the other direction (an
BL> overdriven buffer), except that your dopey modem is *not* sending
BL> CTS/RTS to your comm program and leaves zmodem at my end to struggle
BL> on as best it can.

BL> Get it in your head, Paul: there is nothing wrong at *my* end. We
BL> are trying to solve a problem at *YOUR* end.

This is news to me?  I've just had a thought, maybe I can set the port
speed to 38400 instead of 57600 to fix it.  I need a controlled experiment
though.  Michael is the best person to do that with, because he never
changes his calls.  But he's stopped calling!  Matthew would have been OK,
but (typically!) he's gone and hacked the code to solve the problem!  And
anyway, he'll be back to high speed soon.  Then there's you, who's too
cantankerous to stick with a test.  Sheesh!  BFN.  Paul. 
@EOT:

---