Download DUN 1.3 from Microsoft's Win95 site, or grab it off your
   CD-ROM in ADMIN\APPTOOLS\DSCRIPT, and install it from Add/Remove
   Programs/Windows Setup/Have Disk. Or install Microsoft Plus! This
   adds a Dial-up scripting tool to your Accessories group. If you
   re-install Win95, you will have to re-install this tool; Setup will
   over-write the Registry keys that hook DSCRPT into dial-up networking.
   
   4.00.950B users already have far better scripting options, and older
   versions can take advantage of them with the Dial-up networking
   update.
   
   NOTE: This will also add SLIP and CSLIP to the list of dial up server
   choices! However, you can only use TCP/IP over SLIP and no other
   protocol.
   
   Run the tool to list all of your dial up connections. Select your
   connection, then type a path/filename to a script. The script doesn't
   have to exist yet. Then hit "Edit", and you'll see Notepad. It'll ask
   you if you want to create a new file; do so. Here's a sample script:

proc main
       waitfor "Username:"
       transmit $USERID
       transmit "<cr>"
       waitfor "Password:"
       transmit $PASSWORD
       transmit "<cr>"
       delay 1
       transmit "ppp default<cr>"
       delay 1
endproc

   The $USERID and $PASSWORD come from whatever you fed the dial-up
   connection. I feed "ppp default" to the provider because a successful
   log in only gives me a Unix prompt. "ppp default" runs a program at
   the dial-up server which starts a PPP session, but it isn't necessary
   for all dial-up servers. I even know of one public dial-up server in
   Taiwan that doesn't even ask for a username and password! This is why
   you should perform one manual login ("Bring up terminal window after
   dialing") and learn how your provider prompts you for this info, and
   then write the script based on that.
   
   Microsoft Plus and DUN 1.3 include an improved scripter which allows
   some branching and IF/THEN programming, but it isn't necessary for all
   providers. The above example works with both Plus! scripting and the
   basic scripter on MS's web site.
   
   And finally, save this script and hit "Apply" to attach the script to
   the dial-up connection. You can turn on "Step through script" to test
   and debug the script, then turn it off when you know it works. Hit
   "Apply" to save any changes you make to a script attachment or
   settings.

     * 8.13.1. How can I issue a "modem break" in a dial-up script? 
       
   Some terminal servers require that you switch the server's pass
   through options (so 8-bit ASCII codes don't get mistaken for terminal
   control codes, for example.) Users of SLiRP will need to do this
   depending on how their dial-up server works.
   
   Here's a piece of script that Jeff Lawson uses to issue the break,
   then set his local options and then resume. I gather he'd then run
   SLiRP on the remote terminal and then continue SLIP processing in
   Win95.

   waitfor "jzl>"
   transmit "+++"
   waitfor "0"
   transmit "AT\\B0O0^M^M" (This part actually issues the break with AT\B0)
   waitfor "Local>"
   transmit "set session passall^M"
   waitfor "Local>"
   transmit "resume^M^M"
   waitfor "jzl>"          (Resume normal processing, such as run SLiRP)