On Wednesday November 05 1997 at 13:52, John Ranger wrote to ALL, and Patrick 
McCullough:
 JR>> Init       v`^`&f&C1&D2X4
 CH>> No Binkley init string is going to do any good unless it's prefixed
 CH>> with 'at' and suffixed with a '|' symbol.
 JR> AAANHH! WRONG!
Absolutely not.  Use PMLM (or similar) to _watch_ exactly what Binkley sends 
to the modem.
init ATZ1
Bink sends: 'ATZ1'
Modem replies (echos back): 'ATZ1'
Notice that the modem never said OK, meaning that it hasn't processed the 
command.
init v`^`&f&C1&D2X4
Bink sends: (DTR down)(DTR up)&f&C1&D2X4
Modem replies: &f&C1&D2X4
There is no 'at'.  There is no OK, again meaning that the command was not 
processed.
init ATZ1|
Bink sends: ATZ1[CR]
Modem replies: ATZ1[CR][CR][LF]OK[CR][LF]
This time, there is both 'at' and OK, so the modem has processed the command.
init AT&f&C1&D2X4| will do what you expect, assuming it is a valid command 
for your modem.
You are wrong.  Period.
^^^^^^^^^^^^^^
 >> Prefix    ATDTX4
Isn't going to work.  Bink will send ATDTX4[phone number] when it tries to 
dial a system.  Most modems aren't going to like that very much.
 JR> To those that kept missing the DOCS portion of our program...
Setting up Binkleyterm is a black art.  While the docs are technically 
correct, they do not tell you everything you need to know.  BT-REF does not 
say that you must prefix your init with AT or end it with a CR (represented 
as |), because it is assumed that Bink users will have an IQ high enough 
above room temperature to figure it out for themselves.
 JR> ill think of you in my prayers...
And I'll burn a chicken for you.
--- GoldED/2 2.50 UNREG
---------------