BG> After trying it for the first time a few moments ago, it would seem that 
BG> the short answer is NO.  As you can clearly see, I use a ModemTrans 

I see in the logs you connected to me fine.

BG> statement to alter the dialling string on STD calls to X1, as my mediaeval 
BG> exchange's STD pips are misinterpreted by the modem as a BUSY response, 
BG> which makes the modem drop carrier and redial.  Needless to say, it worked 
BG> as expected under the previous version.  Is there anything like an 
BG> "Afterdial" comment (or similar) which will allow me to
add two commas 
BG> after the phone number?  For example, ATDT024361785,, - which would also 
BG> solve the problem?

1. I don't know, I haven't done any work in that area.
2. The behaviour should therefor be the same as Binkley 2.60
3. I just looked at the doco for Binkley 2.60, and them said something
about needing to change your modemtrans, but I didn't understand it
4. Looking at the code, it seems a "/" separates a prefix and suffix.
5. Can you get Binkley 2.60 from David Drummond and tell me if that has
the same behaviour.
6. Can you read the Binkley 2.60 doco and tell me if you understand it.
7. Can't you make that your dialling prefix on all calls anyway?

BG> Finally, are there any other nasties lurking in my binkley.cfg below, which 
BG> is likely to bite me on the arse if I use it exactly as it stands?

BG> Ignore the statements which I've commented out, as I'm too lazy to tidy it 
BG> up (plus I used the same cfg file for 2.59 with EMSI anyway).

Basically if it works for 2.59, it should work for 2.60, unless they
have changed something in 2.60.  And I don't actually know if they
have, because I haven't read the doco, I just modified the bits that
I used.  BFN.  Paul.
@EOT:

---