Simtel MSDOS 1992 June/SIMTEL_0692.cdr/msdos/zmodem/pips05.arc/MAN.PRT

Text File | 1988-10-29 | 35KB | 838 lines

                          pips - PC Pursuit Driver

             A Script and Support For Zcomm/ProYAM and PC Pursuit

                           Manual For Version 0.05













    Table of Contents

    I.   Release Notice

    II.  Introduction

    III. How PC Pursuit Works

    IV.  How to Install and Configure Pips

    V.   How to Use and Customize Pips

    VI.  Appendices


    I. Release Notes

    Acknowledgements

    First and foremost, Chuck Forsberg, whose superbly written, high
    reliability telecommunications tools gave me the means and
    inspiration to write pips.

    Secondly, those users, both registered and unregistered, who took
    the time to report bugs and suggest enhancements. One, Eric Smith
    has a particularly warm place in my heart as he SENT CODE.

    Thirdly, to those users whose constant questions "when is the next
    version going to be out?" shamed me into writing 0.05.

    Finally - because of an underwhelming number of registrations (a
    total of 3 as of this date) future support of pips is rather
    problematical. I may release a version at a later date that uses a
    few of the added features of ProYAM, but even that is undecided.

    Released October 1988

    pips04 and later REQUIRES ZComm 17.00a or later for all features to
    work properly.

    pips05 contains three major new features, and a number of more
    subtle enhancements that make its operation smoother.

    The major new features are:

    1) MNP and SET command options are now chosen in the pipslist entry
    for each BBS. The SET command for Zmodem uploads is no longer
    peresent in the main menu.

    2) Maintenance of separate passwords for each BBS is eased by
    supporting passwords in the pipslist file. These passwords are
    automatically assigned to function key 10. DO NOT USE THIS FEATURE






    FOR SENSITIVE PASSWORDS, AS IT IS NOT SECURE. If you wish to use a
    feature like this for sensitive passwords, I recommend that you
    purchase a copy of ProYAM and modify pips to use ProYAM's password
    encryption scheme.

    3) Construction of a list of BBS's to be called in a rotating
    fashion using the queue functions is now supported using the +
    option from the main menu. The user will be asked to choose which
    systems he would like to call, and pips will attempt to access a
    list of systems chosen by the user in rotating fashion. Once a
    session is completed with a system in the specified list, pips will
    resume attempting to access the remaining systems. Once all systems
    in the list are accessed, pips will return to the maim menu. Of
    course, the user can abort the list, or remove a system from the
    list "on the fly". During testing of pips I found this particular
    feature to be amazingly effective in maximizing on-line time when
    working PC Pursuit.

    These new features mean that the current pips user will need to
    reinstall the main pips module in his phones file, and rather
    extensively modify his pipslist file. The pipmenu should be updated
    to reflect the elimination of the SET commands, and the use of + to
    trigger the construction of a dialing queue. I think that the new
    features, particularly item 3 will make this worthwhile.

    This script was written by:

    Eric Larson
    2902 Falls Road
    Marcellus, NY 13108

    Copyright 1987, 1988 by Eric Larson all rights reserved EXCEPT -
    this software may be freely distributed on any BBS that does not
    charge an hourly connection fee, or by non commercial users of the
    program, so long as all pips files are packaged together in complete
    form, and are not modified in any way except by file compression
    utilities such as ARC.

    Commercial users, and organizations that distribute software, such
    as PC-SIG, Compuserve, etc. for profit, should write to the above
    address for distribution or use license terms. The latest version of
    this package should be available on Telegodzilla, and the Shockwave
    Rider BBS [phone] (Fidonet 260/330). If you have questions,
    comments, bug reports, suggested features, etc. please send US Mail,
    a message to the Shockwave Rider BBS.

    Please send complaints and flames to NUL:

    I'd enjoy hearing from you in any case.

    I intend to keep upgrading and fine-tuning this script over time. If
    you find this script useful, a contribution of $5 sent to the above






    address will give the author (me) incentive to spend more of my
    limited time developing this script.

    Design goals - highly automated, efficient dialing of Pursuitable
    BBS's with a script that can be used with any flavor of ZCOMM or
    Pro-YAM<tm>, Chuck Forsberg's and Omen Technologies' superb
    telecommunications tools.

    A word about Zcomm and ProYAM - very simply, these programs are not
    as popular as they should be. They do require more of an investment
    in intellectual effort to learn than PC-Talk, or it's decendants.
    But once that effort is made, the serious telecommunications user is
    rewarded with mastery of a tool unsurpassed in reliability and
    flexibility. If you want to a tool that will NEVER let you down when
    the going gets tough, then Zcomm and ProYAM are the programs of
    choice for you.

    Pips is written with announced future expansion of PC Pursuit in
    mind, so when 2400 bps service, universal outdial, and new city
    mnemonics are introduced pips will have the flexibility to make use
    of these features with minimal changes. In particular, pips does not
    *require* the use of submenus for each city, and the attendent file
    clutter this creates.

    Pips consists of several files, for the reason that it simplifies
    the installation and future updating of pips, and a modular, easy to
    maintain program structure.

    Pips tries to avoid a modal structure whenever possible. Menu driven
    programs get much of their bad reputation from the fact that they
    tend to be modal in nature. Modal menu driven programs become quite
    wearing on the user over time, because they do not recognize the
    user's growing expertise with a program. Pips avoids this trap by
    making its entire command set available at all times, irregardless
    of the menu display.  The pips menus are more in the nature of
    online help than a list of commands currently available.

    This version of pips should contain the following files:

    pips script files:

    Required:

    pips.t         is the dialing script
    pipsmenu.t     is the main menu
    pipslist.t     is the list containing the BBS information, and your
                      PCP name and id
    pipslink.t     contains a short bit of code linking pips menu(s) to
                      pipslist
    pipsnum.t      contains the local pcp node telephone number

    Optional:






    pipsb001.t     is a sample submenu file
    pipsfile.t     contains a menu listing Fkeys for file transfers
    pipslog.t      is a file containing custom logon routines

    II. Introduction

    Certain basic assumptions were made in putting together this script
    and the accompanying documentation. The first is that you have
    successfully installed Zcomm<tm> or ProYAM<tm> and a modem on your
    computer. If you haven't, package this won't do much for you.

    The second assumption is that you are at least slightly familiar
    with the jargon associated with telecommunications. The Rosetta
    Stone in the ProYAM/Zcomm manual is a good place to start if you
    feel lost with the terminology used in this document.

    The third assumption is that you are a PC Pursuit user looking for a
    way to cut through the busy responses and obtain the maximum
    possible communications speeds achievable over this network.

    In brief, pips is intended to be a tool which can be used to manage
    the telecommunications service known as PC Pursuit. PC Pursuit is a
    packet switched network, which can be accessed at reasonable cost
    during off- peak hours to provide inexpensive long-distance data
    telecommunications. Since it is a packet switched network, it is far
    more complex to work with than simple direct dial
    telecommunications.

    Pips is intended to help the user manage the network in such a way
    as to reduce the tedium associated with manual entering of the PC
    mnemonics, and utilizing some of the less well known PCP commands,
    to effectively increase the throughput and reliability of data
    transfer over the network.

    Pips' effectiveness springs from two primary sources. The largest
    contributor was Omen Technologies' superior telecommunications
    programs, with script languages and file transfer protocols having
    the power to deal with a system as complex as PCP effectively. The
    second source is my rather extensive experience as a user of PCP.
    This experience and continued testing of pips assures its rapid
    evolution and updating to keep pace with PCP.

    III. How PC Pursuit Works

    PC Pursuit uses the Telenet packet switched data network to transfer
    data economically over long distances.

    The primary advantage Telenet has over direct telephone connections
    is use of technologies that allow multiple users to share the same
    telephone line through the use of multiplexing equipment. Simply,
    what occurs in a Telenet-like environment is that a user first
    informs the network as to what connections he wishes to make, and






    the network attempts establish these connections. After these
    connections are established, the user and remote systems begin
    communications. Data is sent in bundles of varying sizes between the
    systems. Typically, each bundle will contain 128 bytes. Shorter
    bundles are allowed in cases where the user specifies the bundle be
    sent when a certain character is encountered in the data stream, or
    when a certain time has elapsed and the 128 bytes needed for a full
    packet have not been received. The sending and receiving of packets
    is controlled by PAD's, Packet Assembler/Disassemblers. These PAD's
    are intelligent, and obey a simple command language (the SET
    commands) which controls their actions.  Improper use of or
    ignorance of the SET commands will slow your data transmission
    rates, and may make it impossible for you to transfer files using
    certain protocols.

    The delays and "bursty" character of communications over networks
    like Telenet are the result of the packet nature of the network.
    This is the price you pay for the lower cost of the service. If you,
    as a PC Pursuit subscriber try to ignore the nature of this network,
    and use it like a direct dial service, it is guaranteed that your
    results will be poor. On the other hand, if you use the network in a
    way that accounts for its limitations and features, you can achieve
    results very close to, and perhaps even superior to those that can
    be obtained by direct dialing.

    Each byte of information you send is transferred from your modem
    through the local telephone system to the local Telenet modem (often
    called the indial modem), is processed by your local PAD, then is
    sent along with other users' packets along a high speed line to the
    PAD in the destination city, where it is disassembled and
    transferred to an outdial modem where it is sent along local
    telephone lines to the target system. Direct connect PC Pursuit
    sytems like the Portal and the Net Exchange BBS differ from systems
    you have dialed only in that the direct connect system has dialed
    into an indial modem, and has identified itself to Telenet. Thus
    when you are using PCP you are dealing with at least 8 separate
    pieces of telecommunications equipment, at least 5 of which are
    subject to commands that you can issue. These pieces of equipment
    are your modem, the indial modem, the two PAD's you are dealing
    with, and the outdial modem.

    Depending on factors such as the file transfer protocol you are
    using, the speed capabilities of your modem, and the capabilities of
    the system you are connecting to, the optimum configuration of this
    equipment will vary. Pips leaves the setup and control of your modem
    to you. You should customize the dial script in ZComm so that it can
    effectively make a local telephone call. Otherwise Pips issues the
    commands to effectively control the indial modem, the PAD's, and the
    outdial modem, and does so in a manner which achieves results better
    than any other dialing script that the author has seen.

     IV. How to Install and Configure Pips






    A. Quick Installation

    1. Create a disk or subdirectory containing the un-arced pips files,
    Zcomm, or ProYAM, and your PHONES file.

    2. Using a text editor, append pips.t to your PHONES file.

    3. Change the phone number in pipsnum.t to your local Telenet number

    4. Edit pipslist.t to reflect your PCP name and id.

    5. Log on to the drive or directory containing Zcomm/ProYAM and the
    script files.

    6. Run Zcomm (or ProYAM), and type "call pcp<cr>". The main pips
    menu should appear. If it doesn't, please let me know!

    7. Pick one of the BBS's in the menu, and try it out.

    B. After the Quick Installation

    Edit pipsmenu.t and pipslist.t to reflect the systems you wish to
    call. If the main pips menu is too small to hold a complete list of
    the systems you call, you can create submenus for the additional
    systems. Pips001.t contains a sample submenu, and the pipslink
    file illustrates the code needed to call it.

    Pips scans the ENTIRE command data list when a command is entered,
    so even if you are at a submenu, a BBS from the main menu can be
    called.  In addition, the utility commands can be issued at any
    time. When you are building your directories, keep in mind that pips
    uses the convention that commands with a..z and A..Z in them refer
    to BBS dial commands, commands with numbers in them refer to
    submenus, and commands with special characters in them refer to
    utility commands. Thus you should use aa, or AbC, or Z in setting up
    your pipslist.t, but not 0..9 and special characters like !@#$%^&.
    When you set up submenus, refer to them only with numbers, such as
    1, 2, 617, or 415. Do not mix 0..9 with a-Z, and !@#^%)*& as the
    result will be unpredictable.

    Users of versions of pips prior to 0.05 should update their menu to
    reflect the new use of the + command, and the move of the set
    options to pipslist. Since the changes to pipslist are fairly
    extensive, it might worthwhile for the 0.04 user to start with the
    0.05 pipslist, and modify that rather than try to save the 0.04
    pipslist.

    Edit the lines containing :\ in pips and pipslink to reflect the
    path(s) to the files it calls, or set the PIPS environment variable.

    Versions of pips later than 03 will use the enviroment variables
    PIPS, PIPSUL, and PIPSDL if available, to fetch the paths to the






    pips subfiles, to select a default upload directory, and a default
    download directory. If they are not present, pips uses the current
    active directory. The default file transfer directories are only
    used if you use the file transfer routines within pips rather than
    the direct Zcomm commands. Automatic Zmodem and Kermit recognition
    will download into the current directory.

    To use the environment variables, just add line(s) in your
    AUTOEXEC.BAT file: SET PIPS=C:\COMM\YAM\ where C:\COMM\YAM\ is the
    directory or volume containing the pips files. NOTE: Some versions
    of Zcomm/ProYAM may require / instead of \ as the path seperator. If
    you have trouble with pips locating your subdirectory, try using /.
    Also, the trailing seperator is required.

    V. How to Use pips

    A. How to Call

    Once pips is installed, its operation requires very little from the
    user. Just ">Zcomm call pcp<cr>" will cause the main menu to appear,
    and you'll be presented with a plethora of options.

    Normally, at this point, you'll select a BBS from the menu. Once you
    enter the character(s) associated with calling this BBS, pips takes
    over. Pips will check to see if the modem is on-line, and then begin
    either dialing the local PCP number, or start issuing PCP commands.
    If you happen to not be connected to Telenet, pips will detect the
    fact through lack of the expected responses from Telenet, and hang
    up and start over. Pips keeps a record of the city/modem speed you
    are connected to, and will not disconnect from that city/speed if
    you initiate a call with the same city/speed parameters. Pips will
    also detect carrier loss associated with Telenet's dropping carrier
    at odd intervals, and automatically re-call the indial modem.

    Once the local Telenet modem has been reached, and has been informed
    of the settings that pips likes, pips starts to try to reach the
    outdial city. Normally pips will try INDEFINITELY to reach this
    outdial city.  If, for some reason, carrier is lost, pips will sense
    the fact and redial the modem. If TELENET disconnects, line noise
    masks the response codes, or TELENET freezes up, pips will sense the
    fact, and respond by hanging up the modem and starting over. Pips is
    very persistant. The only thing that will cause pips to give up is a
    recalcitrant indial modem. If pips gives up on the indial modem, it
    will complain loudly.  During the cycling of attempts to conect to
    the outdial city, pips will give the user a chance to return to the
    main menu by showing a prompt "Type a to return to main menu" You
    have one (1) second to enter the a, and then pips will start another
    cycle.

    Once the outdial city has been connected to, pips will issue a SET
    command to configure the PAD's. This SET command is specified in the
    pipslist file. Two possibilities are given, one for systems






    supporting Zmodem, one for systems not supporting Zmodem. The Zmodem
    SET should be used for systems that you plan to upload to using
    Zmodem. If you use the Zmodem SET, do not attempt to upload using X
    or Ymodem, or other protocols not transparent to hardware
    handshaking.

    You may also specify that MNP be enabled at the outdial modem if you
    are using a 2400 bps outdial modem. Possible uses of this option are
    if you have a modem that supports MNP, call into a 2400 bps indial,
    call out at 2400 bps to a direct connect system or BBS with a MNP
    modem, you can establish a full MNP session over MNP. This will
    allow effective use of non-error correcting protocols such as Xmodem
    overdrive or Ymodem-G with systems that don't support the superior
    effectiveness of windowing protocols over PC Pursuit.

    After the SET command has been acknowledged, pips will then use
    Racal- Vadic modem commands to dial the local BBS. Again, pips will
    give the user a chance to return to the main menu before each
    dialing cycle.

    Please use discretion here. Pips will continue re-dialing until you
    tell it to stop. I have considerable misgivings about implementing
    pips in this fashion. DO NOT use pips to call any number that you
    are not absolutely sure is a computer. There have been many cases of
    human telephone numbers being distributed in BBS lists for various
    reasons. As a result, the FCC has been considering increasing
    restrictions on the redial capabilities of computer equipment.

    Once pips has connected to a BBS, it will alert the user of the fact
    both visually and audibly. To start your session, type any key.
    Once your session is complete, type F1, and you will be returned to
    the main menu. If you accidently are returned to the main menu, you
    can re- enter terminal mode by typing @. If you plan to upload using
    Zmodem under the conditions previously described, return to the main
    menu, and issue the SET for Zmodem command.

    B. Additional Commands

    Pips contains a menu which lists Fkeys that can be used to aid in
    file transfers. To display this menu, type <Alt>-F1 while in term
    mode.  Since these Fkeys are defined in the pips.t file, they are
    available at any time pips is in term mode, for example, while on
    line to a BBS. It is not necessary to display the menu before using
    these commands. While pips is in script mode, the Fkeys are
    inactive. To abort a file transfer, or any other Zcomm command in a
    graceful fashion, type <CTRL- BREAK>.

    To issue a Zcomm command while in a terminal session, type <Alt>-2,
    and a command prompt will appear. Any Zcomm command can be entered
    at this prompt. For the user new to Zcomm, the most useful command
    will probably be create filespec, where filespec is a path and
    filename.  This will open a capture file for your terminal session.






    To close the file, type <Alt>-2 and type close. Another important
    command is f -p filespec, which will send a text file with the -p
    option. This is useful in uploading messages to most BBS's that use
    : as the beginning of the line prompt in their editors. Other types
    of BBS editors will require other variations on the f command as
    described in the Zcomm manual.

    Pips has a selection of special commands that help the user manage
    his network session. These commands are available from the main
    menu, and are called using special characters like @ and #. The
    special commands are:

    @ - Enter term mode directly. Useful in resuming a session without
    redialing the BBS.

    # - Exit pips. Exits the pips script and returns to the Zcomm
    command line.

    * - Exit and bye. Hang up the modem, exit the script, and return to
    the Zcomm command line.

    ~ - Hang on to city. Do not issue a city disconnect, even if the
    city does not match the current status code. Useful for resuming
    after leaving pips.

    & - force a city disconnect on next call, even if calling back to
    the same city.

    ? - Manual mode. Allows the user to enter city codes and phone
    numbers not stored in the directory files. Useful for exploring new
    BBS's.

    ^ - Hangup outdial. Disconnects the outdial modem without
    disconnecting the target city. Very useful if you've hooked up to a
    crashed BBS, or a UNIX system not smart enough to disconnect after a
    session.

    > - Hangup. Hangs up YOUR modem. The penultimate panic button. The
    ultimate panic button is the power switch on your modem.

    + - Build a list of system to dial in succession - once this list is
    built, pips will manage a series of PC Pursuit sessions
    autmatically. If an error occurs during the execution of this queue,
    and the script aborts, call goto q should cause the script to
    resume. A maximum of 20 systems can be specified in the list. When
    using the + option, pips does not return to the main menu after F1
    is used to terminate a but instead starts attempting to connect to
    the next system in the queue.

    C. Special Features

    There are places in pips that may be a little confusing. In






    particular, when you log on to a local system, pips will go into a
    loop and start beeping. To exit this loop just type any key. To
    abort a call, you must enter the a on the same line the prompt is
    on. You have one (1) second to do this. Once you have completed the
    call and have logged off, F1 will end term mode and return you to
    the main menu. If you are in a submenu, just type <Enter> to return
    to the main menu. Every command defined in pipslist or pipslink can
    be entered at ANY menu. The menus are meant as an aid, not to
    restrict the user to modes.

    While on the BBS, use the Fkeys or ALT-2 to enter Zcomm or ProYAM
    commands. You can, of course, define your own Fkeys in your setup
    area.  I strongly recomend that F1 not be changed.

    You can call any BBS that is not defined in your pipslist file by
    using the Manual (?) command. For direct connect systems, just enter
    the system name and -1 for the local phone number.

    Pips is packaged into subfiles to relieve the user from the chore of
    editing the entire package on each new release. Each file will now
    have a version included in a comment, so if this version is the same
    as the version you have in use, it will not be neccesary for you to
    change your file.

    Through use of the s7 variable it is possible to customize treatment
    of any individual BBS as well as develop auto logons for BBS
    software types. Use of s7 is also the best method to set up an
    automatic capture file. One of the great benefits to using the s7
    parameter is that it allows the user to easily maintain an
    individual password for each BBS.  This gives improved security over
    using one password for many BBS's, and still frees the user from
    excessive record keeping.

    If you have an EGA or better monitor, some of the greater than 24
    line modes can give exceptional results with Zcomm. In fact, it was
    the ability to handle these modes that first attracted me to Zcomm.

    Some customization, i.e. display mode is possible in the BBS data
    lines in pipslist.t.

    Use <ALT>2, <CTRL-BREAK> and the Fkeys to enter and abort commands
    during terminal mode. Avoid <ALT>N as it may lose some infomation on
    your current Telenet/PCP status. If you use ALT-N, use call pcpr: to
    resume the script. Pips maintains a record of your current PC
    Pursuit status, and it will not re-initialize the string variables
    containing this information if you enter pips through pcpr:.

    I have found that running ZCOMM scripts from a RAM disk is very
    effective. On PC's, operations are faster, and on faster machines
    disk wear is reduced. It's very easy to change your AUTOEXEC.BAT and
    CONFIG.SYS files to support this, and to set up a Z.BAT file which
    copies the scripts to the RAM disk in addition to running the Zcomm






    main program. The ramdisk size need not be large, for most uses 64k
    should be ample. Many users have some form of E memory which can be
    set up as a RAM disk, so this strategy does not even exact a RAM
    penalty.

    If you can, use the m224 dialing script in the phodir.t distributed
    with Zcomm. I've found it more reliable than the simpler dial
    script.

    Use of the ! command to edit your phone directory while in Zcomm is
    a great time saver. Pips includes an implementation of this which
    also can be customized up to copy your updated phone directory to a
    RAM disk.

    One of the few things that I have not been able to work out so far
    is a good alternative to the use of the clumsy acceptl1 command to
    exit a call loop. The current implementation wastes one second every
    pass through the loop. ProYAM would allow me to lock the keyboard
    and check the buffer, but this is supposed to be a Zcomm script. All
    I can do at this point is suggest that ProYAM users make a few minor
    adjustments to the script at the points where I use acceptl1.

    The comment :* appears on or immediately after every line that the
    user _must_ edit to configure pips for his own use. The comment :\
    occurs on lines the user should edit if the script files are not in
    the default directory. These lines contain file names (pipsmenu and
    pipslist) that pips calls. Just modify these lines to reflect the
    files' path names.

    I have coded pips to run in 8g i mode when connected to the local
    BBS. If you don't like this default setting, you can either change
    it through the use of the s3 parameter, or edit pips, or lobby me to
    change it.

    Pips supports operation at 2400 bps in several ways. First, it makes
    no assumption as to the modem speed you are using, but instead it
    uses Zcomm's S numeric variable to determine the speed it is
    operating at. The reason for this is that PCP supports 2400 bps in
    various ways, which may suprise some of you. The first way that PCP
    supports 2400 bps is through in dial modems which have both 2400 bps
    and MNP capability.  Use of the 2400 bps indial modem requires a
    slightly different initialization sequence which this script
    supports. Use of 2400 bps for the local connection offers many
    advantages over 1200 bps as lost packets are less likely, and
    overall speed is 5-10% better for protocols like Xmodem and Ymodem,
    even though the outdial modem operates at 1200 bps. The second way
    that PCP supports 2400 bps is through systems that connect directly
    to PCP, like Portal, and soon Exec-PC. The reason that PCP does not
    universally support 2400 bps is that the outdial modems are limited
    to 1200 bps. Systems that link into PCP by calling indial modems
    can, and do support 2400 bps operation.







    Submenu capability has been added for those who call more than the
    number of BBS's that can be convieniently shown in one menu. The
    submenus are stored in the files pipsbnnn.t (if you need more than
    1000 submenus, see a shrink!), and are called from the main menu.
    Since there is only one pipslist.t file you will need to keep your
    character codes unique. One popular use might be to setup a submenu
    for each PCP city. Personally, I don't call enough BBS's to make
    submenus worthwhile. Be sure to use codes containing numbers for
    submenus, and all alpha codes for BBS's. pipslink.t assumes that
    anything with a number in it is a call to a submenu.

    For sysops...you can edit the hangup subroutine to take your modem
    off hook when pips hangs up the phone to prevent incoming calls from
    interrupting your session. It also will prevent your users from
    dialing an "unfriendly" modem.

    VI. Appendices

    A. List of variables used in pips

    s9 Last city accessed, used to determine if dcity should be executed
    This variable has three possible states..

    s9=1 is set either when the local Telenet node is dialed, or a city
    has just been disconnected. No city is connected.

    s9=000 is set when pips is entered. It implies that the local node
    may be connected, but the city is unknown. dcity will be executed.
    certain statements in pips may set s9 = 000 to force a city
    disconnect.

    s9=nnn, where nnn is an area code. Implies a city is connected.

    s8  Set s8 = 1 if you are calling pips from another script. Causes
    the menu to be skipped.

    s7 type of BBS software on other end

    0 = don't use custom routine 1 = Opus 2 = Fido 3 = PCBoard 4 = RBBS
    5 = Red Ryder Host

    Note: the custom routines provided at the end of pips are examples
    that have not been tested. Since developing a logon sequence is very
    simple, and covered well in the Zcomm documentation, I have left it
    as an exercise to the user at this time. If this doesn't suit you,
    let me know.

    s6 MNP flag - if s6 = 1, enable MNP in outdial modem.

    s5 local phone number, or -1 for direct connect

    s4 city code/speed, also user's response to BBS menu, or direct






    conect string

    s3 - Used to control toggle of graphics (8g) mode 1=disable 8g
    0=enable 8g

    s0, s1, and s2 will be used by pips only as temporary variables use
    these variables _only_ in commands or Fkeys that you execute while
    in pips.

    B. Modification History

    Version 0.05

    added codes for new PCP support BBS
    used n0...n9 for PCP variables
    added password and name fkey support
    fixed bad call error messages
    added dial-out queue support
    added MNP support
    made SET implementation for Zmodem smoother

    Version 0.04b

    fixed mites in 0.04, 0.04a
    support for new mnemonics
    support for hangup string to take modem off-hook
    fixed hang in FAILED CALL
    sleep 5 added between D and <cr> to improve dial in reliability
    function key menu added s3 no longer needed for id
    pips now dials using c d/city/12,name,id for improved speed
    t mode now uses i option so review shows ANSI graphics
    added ~ command to hold onto city
    Added Fkey Fa1 to call file transfer sub-script
    Started adding features 12/12/87
    Improved handling of "NO DIAL TONE"
    Improved processing of RINGING...FAILED CALL

    Version 0.03

    Checks for dialing... implemented
    swatted manual answer bug
    added returns to list for speed
    cut down on menu redraws
    added new SET options for Zmodem/Kermit handshaking..
    fix for uploads
    froze features 11/27/87 to start debugging
    pips now calls into PCP using new 8 bit support
    removed much text to reduce size
    reduced number of gosubs to conserve levels
    available, make script run more top to bottom
    manual entry of codes for "tryout"
    added submenu capability






    now shows connected city at main menu
    put logon routines, menu and BBS list in separate files
    reorganized, and hopefully clarified documentation
    moved statements user must edit to top of pips
    name and password are now kept in pipslist
    altered direct connect setup to reduce number of places PCP name appears
    now pips idles out RV mode when disconnecting from a city
    ZModem l parameter set to 1024 to prevent pad buffer overrun when
    dialing in at 2400 bps. This may not be the optimum value.
    pips no longer automatically hangs up after a direct connect system
    escape hatch now present in every loop
    commented out the edit section to simplify user installation

    11/16/87
    version 0.02 checked
    code for missing ;
    fixed MANUAL ANSWER recognition
    pH1 timeout bug in terminal mode fixed
    Speed enhancements made through use of pat i
    Support for 2400 bps dial in Structure of BBS list changed to allow
    varying baud rates over PCP
    Fixed 8g mode for direct connect BBS's like Portal
    New utility commands !, Z, @, # added to the main menu 11/7/87
    version 0.1 - Based on ideas taken from pcp.t by S. Millard This
    version is essentially an alpha test and may not be bug free. I am
    distributing it primarily to get people started, and to get feedback
    on its design.