




                    WWW     WWW WWW     WWW III VVV   VVV
                    WWW     WWW WWW     WWW III VVV   VVV
                    WWW     WWW WWW     WWW III VVV   VVV
                    WWW  W  WWW WWW  W  WWW III  VVV VVV
                    WWW WWW WWW WWW WWW WWW III   VVVVV
                     WWW   WWW   WWW   WWW  III    VVV

                             BBS Documentation
                               For the Sysop



            Copyright (c) 1998-2000, WWIV Software Services, LLC
                    Copyright (c) 1991-1995, Wayne Bell
                Portions, Copyright (c) 1990, Will Daystrom















   Comments and suggestions should be sent to WWIV Software Services.
Your comments and suggestions are welcome.  We hope that you find these
             documents useful as you use WWIV BBS software.






















                           Table of Contents


     Section               Title                           Page
     ==========================================================
        1   End-User License Agreement (EULA) ............. 1-1

        2   Introduction .................................. 2-1

            2.1 Registration Procedures ...................
            2.2 Upgrade Information .......................
            2.3 Registration Transfers ....................
            2.4 Documentation .............................
            2.5 Accessories ...............................
            2.6 WWIV Software Services ....................
            2.7 Historical Developments ...................

        3   Quick Start ................................... 3-1

            3.1 Quick BBS Setup ...........................
            3.1 Quick Multi-Instance Setup ................
            3.2 Updating a Current Installation ...........

        4   Full Installation ............................. 4-1

            4.1 Initialization using INIT.EXE .............

                4.1.1  System Information .................
                4.1.2  Paths ..............................
                4.1.3  Com Port Settings ..................
                4.1.4  Auto-Detect Modem ..................
                4.1.5  Modem Selection ....................
                4.1.6  External Protocols .................
                4.1.7  External Editors ...................
                4.1.8  Security Levels ....................
                4.1.9  Auto-Validation Settings ...........
                4.1.10 Archiver Configuration .............
                4.1.11 Configuring Networks ...............
                4.1.12 Changing Max Subs and Directories ..
                4.1.13 Languages Configuration ............
                4.1.14 Registration Entry .................

            4.2 WWIV.INI ..................................
            4.3 Directories and Standard Files ............
            4.4 Menu System Setup .........................
            4.5 Multi-Instance Setup ......................





                                  i

        5   Operating the BBS ............................. 5-1

            5.1 Starting the BBS ..........................

                5.1.1 Startup Batch File ..................
                5.1.2 Command Line Arguments ..............

            5.2  Waiting for Caller (WFC) Screen ..........
            5.3  Logging On ...............................
            5.4  User Online Keys .........................

                5.4.1  F1 - QuickEdit User Account ........
                5.4.2  F2 - Toggle Top Screen Information .
                5.4.3  F3 - Disable COM ...................
                5.4.4  F4 - Turn off Chat Call ............
                5.4.5  F5 - Hang up on User ...............
                5.4.6  F6 - Sysop Alert ...................
                5.4.7  F7 - Increase Time Online ..........
                5.4.8  F8 - Decrease Time Online ..........
                5.4.9  F9 - Temp Sysop ....................
                5.4.10 F10 - Enter Chat Mode ..............
                5.4.11 Alt-F Keys .........................
                5.4.12 Home ...............................

            5.5  Top Screen Information ...................

                5.5.1 System Status Top Screen ............
                5.5.2 User Status Top Screen ..............
                5.5.3 Abbreviations used in the Topscreen .

            5.6  Message System ...........................

                5.6.1 BoardEdit ...........................

            5.7  Email System .............................
            5.8  Transfer System ..........................

                5.8.1 DirEdit .............................
                5.8.2 ALLOW.DAT and AllowEdit .............

            5.9  Chains (Door) Setup ......................

                5.9.1 Chain Editor ........................

            5.10 General Files (GFILES) Setup .............

                5.10.1 GFile Editor .......................

            5.11 Menu System ..............................

                5.11.1 Menu Editor ........................
                5.11.2 Menu Elements ......................
                5.11.3 Required Files .....................
                5.11.4 Optional Files .....................
                5.11.5 Support Files ......................

            5.12 Events Management ........................

                5.12.1 Event Editor .......................
                5.12.2 System Events ......................

            5.13 Instance Management ......................
                5.6.1 InstanceEdit ........................
            5.14 Chatroom Setup ...........................
            5.15 Multiple Languages .......................

                                   ii

        6   Modem Information and Setup ................... 6-1

        7   For New Sysops ................................ 7-1

        8   WWIV on the Internet Telnet and PPP ........... 8-1

	=========================================================
    	Appendicies

        A   Forms ......................................... A-1
        B   Technical Support and Resources ............... B-1
        C   Frequently Asked Questions (FAQ) .............. C-1
            WWIV with Win95 and Win98 .....................
            WWIV with Win3.1x and WFWG 3.11 ...............
            WIWV with OS/2 ................................
            Chains FAQ ....................................
        D   Common Protocol Settings ...................... D-1
        E   Source Code ................................... E-1
        F   Credits and Thanks ............................ F-1
        G   WWIV Software Services Operational Policy...... G-1



	=========================================================


                                  iii


=======================================================================
1.   END-USER LICENSE AGREEMENT FOR WWIV SOFTWARE (01/30/00)
=======================================================================

    WWIV v4.30 is distributed as SHAREWARE.

    1-1.  Definition of SHAREWARE: Shareware is a software
    distribution method that allows the end user to
    install, use and conduct a thorough evaluation of the
    software for a specified period of time to determine if
    the software meets the needs of the user and its
    fitness for continued use.
  
        1-1.1.  GENERAL.  READ CAREFULLY: This End-User
        License Agreement (EULA) is a binding legal
        agreement between you and WWIV Software Services,
        LLC (WSS) and applies to WWIV v4.30 which includes
        all software and documentation contained in the
        distribution archives as provided by WSS
        (SOFTWARE).  WSS prosecutes violators of this
        license agreement to the fullest extent of both
        federal and state civil and criminal laws and
        statutes.
 
         1-1.2.  SOFTWARE LICENSE. THIS SOFTWARE IS
         LICENSED, NOT SOLD.IF YOU DO NOT AGREE TO THE
         TERMS AND CONDITIONS OF THIS EULA, DO NOT INSTALL
         OR USE THIS SOFTWARE! YOU ARE BOUND BY, AND
         INDICATE YOUR EXPLICIT ACCEPTANCE OF, THE TERMS
         AND CONDITIONS OF THIS AGREEMENT UPON FIRST
         EXECUTION OF INIT.EXE FILE.  THIS SOFTWARE IS
         PROTECTED BY US COPYRIGHT LAWS AND INTERNATIONAL
         COPYRIGHT TREATIES, AS WELL AS INTELLECTUAL
         PROPERTY LAWS AND TREATIES.

         1-1.3.  General License Grant. WSS grants to you
         a personal, non-exclusive license to install one
         operational copy of the SOFTWARE.  This
         installation is for the sole purposes of evaluating
         the capabilities and features of the SOFTWARE for a
         trial period not to exceed sixty (60) days.


         1-1.4.  Termination of License.  Your license to
         use the SOFTWARE terminates on the sixtieth day
         following the date of first installation of the
         SOFTWARE unless sooner registered. Upon such
         termination, you must remove all operational copies
         of the SOFTWARE you installed and discontinue all
         use of the SOFTWARE.
                         
        1-1.5.  Documentation. This EULA grants you, as an
        individual, a personal, nonexclusive license to
        make, use, and make available for electronic
        download, an unlimited number of copies of the
        documentation included in the distribution archive
        provided such copies are not modified in any way and
        contain the original copyright information.

        1-1.6.    Storage and Electronic Transfer of
        Distribution Archives.  You may store and make
        available for electronic download, in unmodified
        form, a copy of the WWIV v4.30 archive as
        distributed by WSS containing the original PKZip(r)
        Authenticity Verification code #XLD658.
 
        1-1.7.  De-compilation and Reverse Engineering.
        You agree not to make any attempts to de-compile,
        reverse engineer, or disassemble the executable
        portions of the SOFTWARE to avoid the requirement
        to register, modify copyright displays, or the
        operational aspects of the SOFTWARE.

 
    1-2. LIMITED WARRANTY. WSS warrants that the SOFTWARE
    will perform  as described in the included documentation
    for a period of sixty (60) days from the date of first
    installation.  Any technical support provided by WSS
    shall be as described in the  included  documentation
    provided to  you  in  the distribution archive.  WSS
    will make reasonable efforts to solve any problem not
    covered in the included documentation. To the maximum
    extent allowed by applicable law, implied warranties on
    the SOFTWARE, if any, are limited to sixty (60) days.
    No other warranties are expressed or implied. To the
    maximum extent allowed by applicable law, WSS disclaims
    all other warranties and conditions, either express or
    implied, including but not limited to, implied
    warranties, merchantability and/or fitness for a
    particular purpose, with regard to the SOFTWARE and the
    provision of or failure to provide technical support.
    This limited warranty gives you specific legal rights.
    You may have other rights, which  vary  from
    jurisdiction to jurisdiction.
          
    1-3.  CUSTOMER REMEDIES.  Your exclusive remedy shall
    be to notify WSS of a suspected failure to meet the
    specifications of the LIMITED WARRANTY.  The entire
    liability of WSS will be replacement of the SOFTWARE
    with an updated version if available.
                              
=======================================================================
2   Introduction.
=======================================================================

    Wayne Bell originally wrote WWIV BBS software and developed it
    until 1997.  In 1998, WWIV was purchased by WWIV Software
    Services, LLC (WSS) and is now supported, developed and distributed
    by WSS and authorized Source Distribution Sites (SDS).  It is the
    BBS system of choice for thousands of sysops world-wide who
    appreciate having a rock-solid BBS system to rely upon and who like
    the fact that it is dynamic and evolving software.

    WWIV is available in two basic forms. The first is shareware, which
    permits the user to use a fully functional copy of WWIV for a trial
    period of 60 days.  If the user likes the software, he must register
    or terminate its use within the 60-day trial.  The other version is
    the registered version which includes access to the source code and
    license to modify the BBS to suit user needs within the limits of
    the Source Code EULA (Appendix. F)  This is a feature not found in
    any other BBS and is what makes WWIV so unique.

    WWIV also allows the registered user to upgrade the node capacity
    of the BBS to handle more than two instances on all platforms.
    Multi-instance refers to the ability of the software to have
    several instances in use simultaneously using the same BBS.EXE
    and accessing the same data files.  This multi-instance ability
    permits systems to be both multi node and multi-line.

    The software offers many features commonly found in BBS software
    selling for many times as much.  It also retains the ability to
    be easy for a sysop to install and operate.  Thus the combined
    features of versatility, power, and ease of use make WWIV one
    of the most prominent and dynamic, BBS programs available.

        2.1  Registration Procedures - As stated in the EULA, when
        registering, the user is purchasing a license to use WWIV
        BBS software and to use the network software indefinitely.
        WSS retains ownership of the software itself.  Also included
        with registration is the (separately licensed) source code
        to the BBS and selected supporting programs. Registration
        entitles the user to free upgrades to all releases under the
        major revision registered.  For example,if a user registered
        version 4.10, s/he is entitled to free upgrades to all 4.xx
        releases of the same platform. Upgrade fees for major
        revisions may be charged and if applicable, will be
        published well in advance of major releases. Pricing for
        upgrades to other platforms may be made available at a later
        date. Pricing will be published as they are released.  There
        are three methods of registration are available:

            2.1.1  Online Registration: $90.00 (US) for the DOS
            platform of the BBS Software. (Available in the near
            future at http://wss.wwiv.com/register.htm)
            Registration numbers and passcodes will be issued at
            the time of purchase.

            2.1.2   Mail-In Registration: $80.00 (US) for the
            DOSplatform of the BBS Software.  Pricing for other
            platforms will be published as they are released.

            2.1.3  Registration Payment Plan: WSS offers a
            payment plan for the purchase of DOS platform BBS
            registrations consisting of four payments of $25.00
            (US).  Each payment extends the users trial period
            by sixty days. ALL PAYMENTS ARE NON REFUNDABLE. If a
            user fails to make scheduled payments on time or to
            complete the payment plan within 240 days (8 months),
            the account will be in default, the payment plan will
            be terminated and no refund will be issued.
            Registration numbers and passcodes are not issued nor
            is the user registered until all payments have been
            made.  WSS will notify network administrators of
            payments received and extensions of the trial period
            at the request of the user.

    2.2  WSS processes Mail-In registrations and accessory
    product orders once a week, normally on Saturdays.  Disk
    mailers with the products ordered, registration papers,
    and letters are normally mailed the following Monday.
    Thus, if you send in an order, allow a few days for the
    post office to do its work and then assess the schedule
    above to determine when you should get a response. If you
    have not gotten a response by one week after that date,
    please contact us and ask about the status of your order.
    When inquiring about the status of an order, please give
    your real name and address at the time of registration as
    our files are indexed and verified using this
    information.
   
    2.3  Upgrade Information - The unregistered shareware
    version allows the user to run a single instance of the
    BBS software and registered versions allow two instances.
    At the time of registration or at a later date, upgrades
    may be purchased to allow the operation of more
    instances.  The upgrade order form is in Appendix B.
    Upgrade pricing is as follows:
   
    +--------------------------------------------------+
     Upgrade From    1/2    4     8    16    32  
    +---------------+------+------+------+------+------
     Upgrade to 4   $20                          
     Upgrade to 8   $45   $25                    
     Upgrade to 16  $80   $60   $35              
     Upgrade to 32  $120  $100  $75   $45        
     Unlimited      $220  $200  $175  $145  $100 
    +--------------------------------------------------+
   
    2.4  Registration Transfers - Some registered users may,
    at some point, decide to terminate their use of WWIV
    and desire to transfer their registration to someone
    else.  There is a specific process to be followed to
    legally transfer the registration number. REGISTRATIONS
    MAY ONLY BE TRANSFERRED BY WWIV Software Services.
    Transfer requests must include Old Owner and New Owner
    Transfer forms; a new registration form completed by the
    new owner and a check or money order for $25.00 (US).
    It is up to the parties involved as to who pays the
    transfer fee. Any sales price beyond the transfer fee
    are the concern of the parties involved and are not the
    responsibility or concern of WSS. The necessary forms
    for transfers are contained in Appendix B.  Transfers
    will not be processed until all completed forms and fees
    are received. All entitlements to source code and SDS
    Access for the Old Owner are terminated upon the proper
    execution of the transfer.
   
    2.5  Documentation - The documentation for WWIV is available
    in several categories and formats. All are available on
    ftp.wwiv.com/wwiv/docs and will be included with the CDROM
    distribution of WWIV when available. It is separated into
    the following functional areas by format:

        430SYSTX.ZIP - v4.30 Sysop Docs in ASCII text
        430SYSAR.ZIP - v4.30 Sysop Docs in Acrobat format
        430SYSMS.ZIP - v4.30 Sysop Docs in MS-Word format

        430USRTX.ZIP - v4.30 User Docs in ASCII text
        430USRAR.ZIP - v4.30 User Docs in Acrobat format
        430USRMS.ZIP - v4.30 User Docs in MS-Word format
       
    2.6  Accessories - At present, WSS develops, distributes,
    and supports the following add-on accessories:

        NET37   (Proprietary Networking Package)
        COST        : Free with WWIV v4.30 registration
                      $25 (US) for stand-alone use
        DISTRIBUTION:  Pre-compiled only.
        DESCRIPTION : Proprietary networking software for
        WWIV-based networks.  Provides password secured
        two-way transmission of email, messages, and
        files. Dean Nash, Lead Programmer

        NetUp  (Network Updater)
        COST        : $100
        DISTRIBUTION: Restricted
        DESCRIPTION : NetUp sends and receives RSA
        encrypted data file updates to all systems in the
        network and designated network officials. Operates
        only on the network for which it is purchased.
        Dean Nash, Lead Programmer.

        NGTrans  (Internet Newsgroup Import / Export)
        COST        : $50.00
        1YR LEASE   : $15.00
        DISTRIBUTION: Purchase or Lease, precompiled only
        DESCRIPTION: NGTrans is an Internet newsgroup
        import / export utility.  Written in C, NGTrans
        was originally developed by Wayne Bell. Chuck
        Bensinger, Lead Programmer.

        WWIVedit  (Full-Screen Editor for WWIV)
        COST        :  $20.00
        DISTRIBUTION:  Shareware, pre-compiled only
        DESCRIPTION :  WWIVedit is a full-featured full
        screen editor for WWIV.  It is written in PASCAL
        and was originally developed by Adam Caldwell.
        WWIVedit is now owned, developed, and distributed
        by WSS. Arthur Johnston, Lead Programmer. (All
        previous registrations honored)

///////////// NOT YET AVAILABLE /////////////////////////
//
//  WWIVchat (WWIV ChatRoom)
//  COST        :  $25.00
//  DISTRIBUTION:  Shareware, pre-compiled only
//  DESCRIPTION :  WWIVchat is a full featured chat room
//  for WWIV.  Fully configurable with CB style chat or
//  windowed rooms.  Specifically designed for multi-node
//  systems. Originally developed by Joe Barbara, WWIVchat
//  is now owned and developed by WSS.   Dean Nash, Lead
//  Programmer.(All previous registrations honored)

    2.7  WWIV Software Services, LLC - In 1998, WWIV Software
    Services, LLC was formed as a corporate entity to continue
    development, support and distribution of WWIV and associated
    software.  We established a set of core beliefs upon which
    we conduct business:
     
    The sole reason for our existence is the registered user.
    Open, responsive lines of communication are essential.
    Registered sysops deserve fast, efficient service.
    Trial users deserve the highest level of support.
    Development requires end user input; listen to it.
    Our mission to support registered users never ends.

    You can reach WWIV Software Services, LLC via the
    following methods:

    Send E-mail to 1@50 on most major WWIV-based networks.
    Send E-mail to wss@wwiv.com via the Internet
    Point your web browser to http://wss.wwiv.com
    Call "The Mountain Empire" Home of WWIV at (931) 431-6467

    Send regular US Mail to:

               WWIV Software Services, LLC
               120 Judson Drive
               Gray, Tennessee 37615


    2.8  Historical Data - WWIV was originally written by Wayne
    Bell.  Wayne began work on WWIV when he was a teenager.  It
    was first written in BASIC on a TRS-80.  Wayne soon
    recognized the limitations of the BASIC language for BBS
    operations and he re-wrote the program in PASCAL.  At that
    time, the BBS could be registered by donations of $25.  The
    last PASCAL version was v3.21d. Many modern day PASCAL BBS
    systems are based wholly or in part upon this early version
    of WWIV. All v4.xx releases of WWIV have been written in C.
    With this language, WWIV has developed into a multifeatured
    BBS system supporting one of the most trouble-free hobbyist
    networks in the world.  WWIVnet, the network founded by
    Wayne, began as a local based network in Los Angeles,
    California with 25 charter members.  In the early 1990's,
    the network grew to over 1,500 members located around the
    world. Because many sysops wanted to run their own networks
    for various reasons, Wayne added a feature which allowed the
    BBS system to participate in multiple WWIV-based networks
    and developed the networking software to support such
    multiple network usage. At the peak, there were some 100
    WWIV based networks offering a range of topics and
    supporting a multitude of various interests.

    In January of 1998, Dean Nash purchased WWIV and WWIV
    Software Services from Wayne Bell.  WSS was reformed as
    a Tennessee Limited Liability Company with a full
    corporate posture. Craig Dooley was appointed Support
    Coordinator and supervises the Support Board System and
    Source Distribution Sites.

    The documentation for WWIV has also developed overtime.
    It began as a short 3-page document written by Wayne.
    Later, with v4.10, William Daystrom wrote a complete
    set of documentation for use with WWIV. Beginning with
    v4.20, Filo added additional comments to some of the
    documentation files written by Will and completely
    rewrote others.  The documentation was again completely
    rewritten by Filo for v4.23 and updated for the v4.24a
    release. With the release of v4.30, the documentation
    was updated to reflect all code changes and was
    converted to several different formats for your
    convenience.

=======================================================================
3. Quick Start.
=======================================================================

    3.1 Setting up WWIV for the first time is very simple and
    should take only a matter of minutes.  The first thing to do
    is to create a directory for the BBS.  This should be a
    directory created off of the root directory of any drive.  To
    create such a directory, you can use the DOS MD (make
    directory) command.  Most people name their main BBS directory
    either WWIV or BBS.

    Step 1: Make the BBS Directory

        cd\         (change directory) slash gets you to the
                    root directory of the drive.
        md WWIV     creates the WWIV directory.

    Step 2: Unzip the Archive. The next step is to unzip the BBS
    files into the WWIV directory that you just created.
    Assuming that your WWIVxxx.ZIP  file is on drive "A", the
    appropriate steps would be:

        cd\WWIV                     (change directory) to WWIV
        pkunzip a:\wwiv4xx.zip      this will unzip the archive
                                    into the current directory
                                    (i.e. the WWIV directory)

    You must have PKZip (TM) somewhere in your path in order
    to use the PKZip commands.  All files distributed by WSS
    are compressed using PKZip and contain PKWare's Authenticity
    Verification. If you do not see a -AV by each file as they
    are decompressed, or the lines:

    Authenticity Verified:
    WWIV Software Services   #XLD658

    the archive is not authentic or has been modified in some
    way. DO NOT USE THESE FILES!  Obtain a fresh archive from
    ftp.wwiv.com/wss or an authorized Support Board.

    Files included: You should check the FILES.LST contained
    with the archive to determine the complete files list
    shipped with the current version.  If any files are missing,
    your BBS may not run properly or perhaps not run at all.
    To view the FILES.LST, you can use the DOS type command:

        type files.lst

    Step 3: Run the initialization routine. If all files are
    present, your next step is to run the INSTALL.BAT file.  The
    batch file will type out a couple of messages and then run the
    INIT program.  The first screen you will see is:

    Ŀ
     WWIV v4.30 Initialization/Configuration program.           
     Copyright (c) 1999 by WWIV Software Services, LLC          
                                                                
                                                                
     CONFIG.DAT NOT FOUND.                                      
                                                                
                                                                
                                                                
     Perform initial installation?                              
    

                                    3-1

    You should answer Y. INIT will then proceed to install the
    necessary files and directories for WWIV to run. You should
    note that all directories will be made as sub-directories
    of the current working directory, so be SURE that your
    current directory is the one you want to use as your main
    WWIV directory, when you first run INIT.

    INIT.EXE will automatically create some directories for you on
    the hard drive and put certain files in some of these
    directories.  Although each version of WWIV may have slightly
    different files, you should expect to see something like this
    as the directory tree that is created:

    X:\WWIV
      
      \ATTACH
      
      \DATA
       \REGIONS
       -\ZIP-CITY
      
      \DLOADS
       \SYSOP
       -\MISC
      
      \GFILES
       \MENUS
              -\WWIV
      \MSGS
      \TEMP1
      \TEMP2

    A number of files will be placed in DATA when you finish the
    INIT program, and a number of *.msg files will be created in
    or moved to the GFILES directory.  These files are system
    screens and  may be edited to suit your preferences.

    Step 4: Configure the modem. The first time that you run INIT,
    the program will attempt to detect your modem type and
    configure it for use with the BBS.  There are a plethora of
    modems and WWIV could not possibly detect each and every one
    properly so it will make the best choice it can based on the
    information it has.  If the modem type that is selected does
    not work well, you can select the SELECT MODEM TYPE from the
    menu and choose the one that most closely represents your own
    modem.  More details about modem selection and modem use is
    in the section of the documentation dealing with modems.
    (Appendix. ???)

    Step 5: Configure the system. After your modem has been
    configured there are certain items of information requested by
    INIT that you will definitely want to fill in immediately.
    Other items may be left at the default values until you are
    more familiar with WWIV.

    You will be told that your system password has defaulted to
    SYSOP.  The system password is a password that should only be
    known by the primary system operator.  The system password is
    required whenever you  see the "SY:" prompt. You will need to
    enter the system password when you run INIT, or run more
    sensitive sysop functions from the BBS. After you are told what
    the system password is, you will be given the "SY:" prompt, and
    you will need to enter the system password, SYSOP.

    After correctly entering the system password, you will be in
    the Initialization/Configuration program. You will presented
    with menu options that are described later in order. If you
    don't fully understand some of the options, just leave them as
    they are, and their use will probably become clear after
    playing with the system a bit, or reading further in this
    document.

    For a fast setup, change the following items in Option 1 to fit
    your system:

    System PW  (Should be changed IMMEDIATELY)
    System Name (the name you want for your BBS)
    Sysop Name (what you want to be called on the BBS)

    The rest of the settings can be altered later after you learn
    more about how WWIV operates.

    Step 6:  You must now edit create a batch file with which to
    run the BBS.  WWIVBAT.SAM is an example which contains several
    command lines for FOSSIL Drivers and the proper sequence for
    loading the BBS.  It must be renamed with an extension of .BAT
    to function.  You must install a FOSSIL driver (i.e. X00,
    ADF, WinFossil) for v4.30 to work properly.  More information
    on FOSSIL Drivers is contained in Appendix. ???.

    Step 7:  Establishing your user account.  You must now load the
    BBS using the batch file you just created and log on as NEW to
    establish your user account.  Once the Waiting for Caller (WFC)
    screen comes up, hit the space bar.  You will be presenting with
    the Logon? prompt.  Hit Y.  Answer the following questions as
    they are posed to you.  When you have finished logging on, you
    should hit the F1 key to edit your user account while online.
    Since you want all powers and features, enter 255 as your SL
    and DSL.  For ARs and DARs, enter the letters A through P or
    just hold the space bar down.  If restrictions are shown remove
    them by pressing the letter of the restriction. For exemptions,
    enter 31.  When you exit the online user edit function, you
    should see your time increase dramatically.  You are now a sysop
    with an operating BBS.  Have a friend call from his computer to
    test it out.

    Summary:  There is much more to learn, but you are better off
    learning through experimenting with the BBS and reading further.
    Thoroughly reading the documentation is recommended within the
    first 60 days of operation to ensure you can make an informed
    choice as to whether you wish to continue using WWIV as your BBS
    software.

    3.2 Multi-Instance Quick Start: Beginning with v4.23 it is possible
    to run more than one instance of WWIV.  This may be done in
    situations where you are  using multitasking software and/or a LAN.
    This permits more than one user  to be using an "instance" of the
    BBS at the same time.  In order to utilize more than one instance,
    you must do the following for EACH instance (other than the first).

    Step 1: Run INIT.EXE for the instance. Run INIT using the
    following command:

        INIT ,x   (Where x is the instance you wish to configure)

    which enables you to create the "second instance". If the second
    instance is only for local keyboard use (i.e. no modem attached),
    there are no changes required in INIT.  INIT will automatically
    create the subdirectory TEMP2 off the main BBS directory and
    set that as the instance temporary and batch directory.  You may
    wish to check to ensure the com port for the instance is set to
    0 for local instances under option 3.

    If the second instance is attached to a modem, then it will be
    necessary to define the COM port for that modem and select a
    modem type for it.

    Step 2: Configure instance batch file

    For a local logon, you need a batch file that can be used to logon
    to the second instance.  This will be invoked by your multi-
    tasking software in a multi-tasking environment or may be used
    over a LAN.  The batch file should look something like this:

        REM --- BBS Batch file for instance 2
        @echo off
        REM --- Goto BBS drive and directory
        c:
        cd\WWIV
        REM --- Set the instance environment variable
        SET WWIV_INSTANCE=2
        REM --- Run the BBS:
        REM --- -m  = ignore modem
        REM --- -i2 = designates instance to run on
        BBS -m -i2


    If the second instance is attached to a modem and you wish to use
    the modem on that instance, you should make a copy of WWIVBAT.SAM
    and edit the file as described previously for this instance.  The
    -m parameter used above is only for local logons. The i2 is
    necessary to tell the BBS that it is instance 2 that is being run.

    You will need to install SHARE.EXE or be using some form of "share"
    via your network software if you are on a LAN in order to have
    multi-instance capability. If you are using Windows 95/8 or OS/2
    as your multi-tasking software you will NOT need share. Additional
    information for multi-tasking may be found in Appendix. ???.

    3.3 Updating a Current Installation.  If you are upgrading from a
    previous version of WWIV, the process has been greatly simplified
    for you using an included batch file named UPGRADE.ME.  You may be
    required to edit the file if you have a non-standard setup.

    It is highly recommended that you make a backup of your current
    setup since nothing is infallible.  We have tested the upgrade
    process, however, it is possible that individual configurations
    could fail.

    The batch file places the file WWIVINI.430 in the main BBS
    directory. It is imperative that you integrate the new INI settings
    contained in WWIVINI.430 with your old settings.  Failure to add
    the new settings will prevent the BBS from operating.

    The file MODEMS.430 is placed in your DATA directory.  You may
    be able to continue using your current file, but it is
    recommended that you use the new version as some settings have
    changed.

    As the final step in the process, INIT is run to upgrade and
    convert some data files to the current format.  DO NOT run
    BBS.EXE until INIT has been run for the first time.  Your data
    files will be corrupted and rendered useless.

    You may choose to print the file out and then enter the commands
    manually.  The file is well commented so this should be a
    rather simple task.

=======================================================================
4 Full Installation
=======================================================================

	 4.1 Initialization using INIT.EXE. Once INIT is run, and after you
	 have correctly entered the system password, you will be presented
	 with a menu listing fifteen options as shown here:

		[insert INIT screen shot ]

	 This section describes each of above options and how to edit and
	 modify the configuration of your BBS.

		4.1.1 System Information

			4.1.1a	System password. The system password defaults to
			SYSOP, but you should be sure to change it to something
			else, hopefully something that other people will have a
			difficult time guessing.  Selecting your own personalized
			system password prevents other people from gaining
			unauthorized access to your BBS. When you type the
			password it will show on screen as XXXXX.

			Note that with the release of v4.24, an added security
			measure has been added that allows you to enter a system
			password on the command line when you start up your BBS.
			See the setup section for details.

			4.1.1b	System name. This should be set to the name of your
			BBS, but if it isn't set correctly, nothing bad will happen.
			You should give considerable thought to selecting a name
			for your BBS.  To avoid duplication of other names that
			might be in use on other BBSs, you are encouraged to check
			the network listings for the various WWIV based networks
			and perhaps FidoNet systems as well.


			4.1.1c	System phone. This should be set to the phone number
			of your BBS. This isn't critical information UNLESS your
			board is a member of a WWIV network.

			4.1.1d	Closed System. If your system will not be allowing
			users to dial up and establish accounts on your system, set
			this to Yes.  If someone does dial up a closed system, they
			will be presented with a short message telling them it is a
			closed system and does not accept new users.

			4.1.1e	Newuser PW. This is the password users will have to
			enter in order to log on as new users. If there is no
			Newuser password, anyone may log on as a new user. This
			should only be used if you wish to operate a "private"
			system where you only allow people you know to log on.

			4.1.1f	Newuser restrict. This sets the restrictions that
			all new users are given.  This should probably be left
			as-is until you fully understand what the restrictions are
			used for. See "Restrictions" for more details. The default
			restriction of M means that any messages that the user
			posts, will not be seen by anyone else until you have
			validated the messages.

			4.1.1g	Newuser SL. This sets the security level that all
			new users are given. The default is 10. This should also be
			left alone until you understand what the different security
			levels do, and even then, most sysops will probably want to
			leave this set to 10.

			4.1.1h	Newuser DSL. This sets the download security level
			that all new users are given. The default is zero. New
			users are severely limited in what they can do on the BBS
			until you have 'validated' them which usually involves an
			increase in their SL and DSL as well as possibly the
			assignment of some Access Restrictions (AR's) and Download
			Access Restrictions (DAR's).

			4.1.1i	Newuser gold. WWIV keeps track of an amount of
			"gold" for use in online games, if needed. This sets the
			default amount new users are given. The regular
			distribution version of WWIV does not use gold for
			anything. If you have registered your BBS and obtained
			the source code, modifications are available which can
			allow you to use gold, for example, to regulate downloads
			or game use by requiring that the caller "earn" a certain
			amount of gold by posting.

			4.1.1j	Sysop name. At a few points in the BBS, the system
			will need to print out the name of the system operator.
			This is where you can set what that name will be.  You may
			use your real name, but many sysops use "handles" or
			aliases instead. This is totally up to you.

			4.1.1k	Sysop low time. The sysop low time and sysop high
			time set the time limits that the sysop is available to be
			chatted with.  If, for example, you don't want people to be
			able to request a chat between 11pm and 7am, then your chat
			hours would be 7am to 11pm.  The low time (when chat hours
			begin) would then be 7am, and the high time (when chat hours
			end) would be 11pm. You enter the time in the standard
			24-hour format, where 7am is 07:00 and 11pm is 23:00.

			Normally, the scroll lock key determines when the sysop is
			available for chat. If sysop hours are defined, the system
			ignores the status of scroll lock during the hours the
			sysop is supposed to be unavailable. In other words, if you
			followed the above example and chose available hours to be
			from 7am to 11pm, callers will not be able to request chats
			with you from 11pm to 7am, regardless of the scroll lock
			setting.

			During the sysop hours (7am to 11pm), scroll lock IS
			monitored, and will determine whether or not the sysop is
			available for chat.  If the scroll lock is on, callers will
			be told you are available, and if they request a chat, a
			chat alarm will be sounded (unless you have turned the beep
			off.

			4.1.1l	Up/Download ratio. Many sysops want to have
			up/download ratio requirements. This allows you to set them.
			A caller's ratio is defined to be the number of kilobytes
			(k) (1024 bytes) of files uploaded divided by the number of
			kilobytes of files downloaded. So, if you want a caller to
			be able to download 5k for every 1k uploaded, the required
			ratio would then be 1/5=0.2, so you would set the ratio
			required to be 0.200. This way, when a caller has violated
			the ratio (downloaded over five times what he/she uploaded),
			the caller would not be allowed to download again until the
			caller uploaded enough data to clear the ratio.

			4.1.1m	Post/Call ratio. Similar to the Up/Download ratio,
			this restricts users from downloading if they do not meet
			the minimum ratio established.

			4.1.1n	Max waiting. Each caller may have a number of pieces
			of mail waiting. This allows you to set the maximum number
			of pieces of mail a caller can have waiting. NOTE: The sysop
			(SL=255) can have 5 times this number of mail waiting. So,
			if, for normal callers, 20 is the maximum, then 100 would be
			the maximum for the sysop. If the sysop has more than 254
			pieces of email waiting, only the first 254 will show up at
			the mail prompt, but the rest will not be deleted. After the
			sysop reads some email, the software will make more of the
			waiting email available, but will still only show the first
			254 pieces at the mail prompt.

			4.1.1o	Max users. The BBS requires you set the maximum
			number of users that can be on the system. This defaults to
			500, but you may increase or decrease it. The absolute
			maximum is 32,767, but 2,000 is probably about the limit
			for performance reasons (i.e., the system slows down the
			more users you have).

			4.1.1p	Caller number. If you have converted to WWIV v4 from
			another BBS (possibly an earlier version of WWIV), you may
			set the current caller number with this option. This counter
			is incremented each time the system receives a non-network
			call unless the remote caller is the sysop.

			4.1.1q	Days Active. Again, if you converted from another
			BBS, you can set the number of days your BBS has been
			active here.


		4.1.2 Paths. If you have more than one hard disk, you may wish
		to split up the BBS files among your hard disks, in order to
		better use the space. Using this option, you may change the
		directories that the BBS looks to for certain things.  Please
		note that changing any of the options here will only change
		where the BBS looks for the data; IT WILL NOT ACTUALLY MOVE ANY
		FILES OR DIRECTORIES. The following rules should be observed
		when assigning or changing directories:

			1. Never use the root directory of any drive to store BBS
			files; the root directory can only hold a fixed number of
			files, while any sub-directories may hold an unlimited
			number of files in them.

			2. Always have a backslash on the end of the path/directory
			name. The software will normally add this backslash for you
			but there may be occasions where it is required.

			3. The directory may be specified relative to the main BBS
			directory, or as a full pathname. In other words, "MSGS\"
			is recognized as a sub-directory of the main BBS dir.  In
			most instances, however, you won't need to change the
			default directories.   For security reasons, you are
			strongly advised to use complete paths to these directories.
			If you choose to have directories located on another drive,
			you MUST include a drive letter in the pathname.

			4.1.2a Messages Directory. Information regarding all e-mail
			and posts is stored here.

			4.1.2b GFILES Directory. The Directory where the BBS text
			files are stored. These files can be read by users while
			they are on line. If you have any GFILE sections (described
			later), the BBS will create sub-directories of the GFILES
			directory, i.e. "gfiles\section1\". See[????] for
			information on G-Files.

			4.1.2c	DATA Directory. Data files used by the BBS are
			stored here.

			4.1.2d	DLOADS Directory. This directory is used to set the
			default directory for new file sections.

			4.1.2e	TEMPx Directories. This area is used to temporarily
			store files for the BBS.  In a multi-instance setup you will
			need a separate temporary directory for each instance that
			you have.  The INIT program will create a temporary
			directory for each instance the first time it is run for
			that instance.	The default name is TEMP<inst num>.
			You may change this, but remember to create the directory
			as INIT will not automatically do this for you.
			Please note also that any files found in the temporary
			directory when the BBS is run will be DELETED. If you
			point the temporary directory to your root directory, or
			the BBS directory, ALL THE FILES IN THAT DIRECTORY WILL
			BE ERASED. Therefore, have the temporary directory be one
			that doesn't contain any files you care about.

			4.1.2f	BATCH Directory. This directory is used to
			temporarily store files that are batch uploaded (defaults
			to the defined TEMPx directory).  Make sure this directory
			has adequate disk space for files being batch uploaded (at
			least 5 MB recommended). After batch uploads are completed,
			the BBS will automatically move the files into the
			appropriate drive and directory and delete the uploaded
			files.


		You may freely change DLOADS, TEMPx and BATCH to whatever you
		want without hurting anything. HOWEVER, the TEMPx and BATCH
		directories MUST exist. You may choose to have the temporary
		directory exist as a RAM disk. If the TEMPx directory is a
		sub-directory of a RAM disk, MAKE SURE that the directory is
		created BEFORE the BBS is run. In other words, run the BBS in
		a batch file that first creates the temp directory.

		The others (messages, gfiles, data), however, will have files
		in them that the BBS needs to find in the appropriate
		directories.  If you change the Messages, GFILES, or DATA
		directories, you must:

			 1. Go to DOS and create the new directory.
			 2. Move all files from the old to the new directory.
			 3. You should then probably erase the old files and old
			 directory, to ensure you aren't confused by multiple
			 copies later on.
			 4. You will then need to create subdirectories, of the
			 new directories, with THE SAME NAME, and copy all files
			 from the old subdirectories to the new ones.

		4.1.3  Com port info (port, IRQ, base address, etc

			4.1.3a	Com Port. This sets the com port number that your
			modem is connected to. If this is set to zero, the result
			is that the BBS will not use a modem at all (same as /m
			parameter). Initially, the com port is identified and set
			with the auto-detect features of the INIT program.

			4.1.3b	Interrupt. This allows you to manually change the
			interrupt used by the BBS. You will probably not need to
			modify this.

			4.1.3c	Base address. This sets the com base address used
			by the BBS, and is dependent upon the com port number.	It
			is set automatically when you change the com port option,
			and you will not normally need to change this setting.

			4.1.3d	Slow UART. The INIT program automatically detects
			the presence of the 16550 buffered UART chip for the com
			port listed.  "Y" indicates INIT has detected a 'slower'
			UART chip and the "Unbuffered UART on COMx" message will
			be displayed.

		4.1.4  Auto-Detect Modem. INIT will scan the available com
		ports and select the proper configuration for some more
		prevalent modem types on first run. This may or may not work
		with your modem. If your modem type is not detected, a generic
		definition may be selected. If you are not satisfied with the
		auto detect choice, select a definition manually.

		4.1.5  Select modem type. This option allows the manual
		selection of the modem type to be used by the BBS. Modem
		definitions are listed in alphabetical order. Use the UP/DOWN
		arrows, and PgUp/PgDn keys to scroll to the modem type that
		most closely describes your modem; press enter, and a new
		MODEM.DAT file will be compiled and placed in the DATA
		directory. It is this file that contains all modem information
		the BBS needs. MODEM.DAT is a data type file that cannot be
		altered or changed. The source for the MODEM.DAT file is a
		configurable text file called MODEMS.MDM. MODEMS.MDM is a
		compilation of known, working modem setups that is located in
		the DATA subdirectory following installation. It is very
		unlikely that you ever need to change the data stored in
		MODEM.DAT, but if it ever became necessary (changing a result
		code or such), the place to do so is in MODEMS.MDM, then
		re-select that modem type and a new MODEM.DAT file will be
		compiled. For more information on modems and modem setup,
		consult Chapter 5.

		4.1.6  External Protocols. Using this option, you will be able
		to insert, delete, and modify external protocols for the BBS to
		use.  A full range of protocol settings are contained in Chapter
		8.	Note that these settings are for up/downloads on the BBS
		itself, NOT the network software.

		4.1.7  External Editors. A full screen editor (FSED) allows you
		and your callers (with ANSI) to write email and posts using an
		editor that is not restricted to the line-by-line approach used
		by the internal line editor.  Some editors allow the use of
		function and arrow keys to move the cursor about the screen, in
		much the same manner as a regular word processor.  Full screen
		editors tend to be awkward for callers to use, however, as while
		the sysop might use the arrow keys to move the cursor, the
		caller must almost always use control-key combinations to
		achieve the same thing.  Still, there are some great advantages
		to using a full screen editor, especially from the sysop's point
		of view, and so provision is made in WWIV for their use.  The
		full screen editor must do all I/O through DOS calls.

		WWIVedit, another WSS product, is probably the most preferred
		FSED and is written specifically for use on WWIV BBS systems.
		WWIVedit is self installing and requires very little
		intervention during installation. WWIVedit is available on all
		Support Boards and on the Internet FTP site.

		The following are Command lines for other full screen editors.
		You should read the documentation that is distributed with the
		editor in depth and adjust these commands to your liking:

		Description : FSED
		Filename to run remotely
		fsed +dosansi.cfg +wordstar.cfg -w%2 -h%3 -l%4 %1
		Filename to run locally
		fsed +console.cfg %1

		Description : FEdit 1.1
		Filename to run remotely
		FEDIT %1 %2 %3 %4
		Filename to run locally
		FEDIT %1 %2 %3 %4 %5

		4.1.8  Security Levels. For each security level (SL) there is a
		set of data that determine what a caller with this SL may do.
		These levels are numbered 0 through 255. You may change the
		default settings to suit your particular situation but most
		find the default setup satisfactory. If you should desire to
		change the settings, use {,},[,], to scan through until you
		find an SL you want to change. Then, hit enter to edit the data.
		You can then alter:

			4.1.8a	Security level. Changing this field moves you to
			the entered security level.  The other data on the screen
			is appropriately changed.  Any data changed for the
			previous SL is saved.

			4.1.8b	Time per day. This gives the time, in minutes, that
			a caller with that SL is able to be logged on the system per
			day, regardless of the number of calls.

			4.1.8c	Time per logon. This gives the time, in minutes,
			that a caller with that SL is able to be logged on to the
			system per call.  Normally, the time per day is 2.5 times
			the time per logon.  Normally, the time allowed on is
			limited by the time per logon, but after the second call
			that day, the time per day may cut down the total amount
			of time on. Of course, the time allowed on may be affected
			by uploads, chat time, and extra time allowed by the sysop.

			4.1.8d	Messages read. This sets the number of messages that
			can be read (per call) by a caller with that SL.

			4.1.8e	Emails per day. This sets the maximum number of
			pieces of mail that a caller with that SL can send, per day.

			NOTE: Email excludes feedback. All callers are allowed to
			send up to five pieces of feedback per day.

			4.1.8f	Posts per day. This sets the maximum number of posts
			a caller with that SL can post per day.

			4.1.8g	Post anony. If set, this means that a caller can
			post anonymously on any message base.

			4.1.8h	Email anony. If set, this means that a caller can
			send anonymous e-mail on the system.  No network emails may
			be sent anonymously.

			4.1.8i	Read anony posts. If set, a caller with this SL can
			read the names on anonymous posts.

			4.1.8j	Read anony email. If set, a caller with this SL can
			read the names on anonymous e-mail.

			4.1.8k	Limited co-sysop. If set, a caller with this SL can
			validate and delete messages from any caller.  Normally,
			callers can only delete messages they have written.

			4.1.8l	Co-sysop. If set, a caller with this SL has access
			to all co-sysop functions.


		4.1.9  Auto-Validation Configuration. The sysop can set the
		Alt-F keys (Alt-F1 through Alt-F10) to set certain data for a
		caller.  This function allows you to change that data.	You may
		set the SL, Download Security Level (DSL), Access Restriction
		(AR), Download Access Restriction (DAR), and System
		Restrictions.  Then, when a caller is on-line, you may press
		any ALT-F key combination to immediately change that caller's
		access levels and restrictions.  This may be useful for
		validating a user that is online.  You can, for example, just
		hit Alt-F1, and if you have that configured to give the caller
		standard access, the caller will immediately receive the
		configured access. It all happens very quickly, and there is no
		immediate indication on the caller's side that anything has
		happened, save perhaps a dramatic increase in the time-left
		display.  The Alt-F10 key combination is used if you have
		configured the optional Simple Auto-Sysop Validation ASV.
		The first four (Alt+F1-F4) settings are used in the optional
		Advanced ASV system.  See Section 4.1.15 for more information
		on ASV.

		CAUTION: If you are logged-on locally, and hit an Alt-F key
		combination, your user account will be altered as well.  This
		would do no permanent damage, but it will cause an annoyance
		as you have to reset your own access levels again.

		4.1.10	Archiver Configuration. You may configure up to 15
		supporting archiver formats. ZIP, ARJ, PAK, LHA, and RAR are
		pre-configured on first installation. The first archiver
		record is the default archive on the system. The first four
		are also copied into the pre 4.30 archiver structure for
		backward compatibility with other supporting programs.	For
		most users, you will not need to adjust these settings.
		The standard DOS replacement parameters %1 and %2 are used for
		source and destination filenames. To navigate through the
		archiver records, use the bracket keys [ and ].  To edit a
		record, hit enter.

		CAUTION: It is *HIGHLY* recommended that you edit the command
		lines of all archivers and specify a complete path and
		filename to the program to run (i.e. c:\bat\pkzip.exe -a %1 %2).
		It is possible, though very unlikely, that malicious user
		could upload a batch file or compiled executable with an
		archiver name that may do harm to your system if run.

			4.1.10a  Archiver Name. This is a recognizable name you can
			assign to the archive type.

			4.1.10b  Archive Extension. This is the three letter
			extension applied to files of this particular type. This
			setting is how the BBS identifies archives.

			4.1.10c  Archive List. This command lists the archive to
			the screen without actually extracting the files.

			4.1.10d  Archive Extract. This command extracts the archive
			to the temporary directory for the current instance.

			4.1.10e  Archive Add. This command adds a file to an
			archive.

			4.1.10f  Archive Delete. This command deletes a specified
			file or list of files from the current archive.

			4.1.10g  Archive Comment. This command applies a BBS
			comment to the selected archive. %K substitutes
			GFILES\COMMENT.TXT for commenting.

			4.1.10h  Archive Test. This command tests the selected
			archive for validity and integrity.

		4.1.11	Network Configuration. If you have installed the
		NETxx.ZIP archive in the BBS directory, this option will allow
		configuration of networks. The prompts are self explanatory.
		For details on network configuration, see NETxx.DOC in the
		distribution archive.

		The only setting that affects the BBS itself is the Network
		Type.  This setting tells the BBS and the network software how
		to handle the particular network. There are currently three
		network types: WWIV, Fido, and Internet.

			4.1.11a  WWIV network type. This type is processed
			normally and entirely by the NETxx package.

			4.1.11b  Fido and Internet network types. These types
			implement internal hooks for pre-processors and tossers
			such as WWIVtoss and the PPP Project to convert native
			type messages and email to WWIV format and vice versa.

		4.1.12	Change Max Subboards/Directories. This is a system
		tuning parameter.  These items require runtime memory thus
		the higher they are set, the less memory is available when
		shelling to DOS or running external programs.  You should NOT
		select more than you think that you will actually need, for
		more memory is required as the number is increased.  This
		setting may be modified later if you require more subs or
		directories.

		4.1.13	Language Configuration. WWIV has the ability to offer
		users multiple languages through the use of string files. To
		configure languages, all that is required is to define the
		directory where the language string and menu files are
		located. See Chapter 9 for more information.

		4.1.14	Registration Information. When you register WWIV,
		this is where you will enter your registration number,
		passcode, name and address information. A registration
		passcode is required for v4.30 for the BBS to operate beyond
		the 60 day trial period.  Previously registered sysops will be
		issued a passcode at no charge at:

		   http://wss.wwiv.com/passcode.htm.

		The name field is required. Enter the same name you used to
		register the software. The address fields are optional and are
		for your information only. You may be required to provide the
		address information at the time you registered at some point
		in the future.

	4.2  WWIV.INI. The INI or Initialization file is probably the most
	enigmatic part of WWIV. It provides quick access to the core of
	configurable options and allows a quite diverse array of system
	tuning parameters.	The file is well commented and should be fairly
	easy to adjust to your particular situation. The default file is
	setup for a generic BBS and should be sufficient for most
	applications.

	4.3 Directories and Standard Files. INIT creates the
	following directory tree on first run:

	X:\WWIV
	  |-\DATA
	  | |------\REGIONS
	  | |------\ZIP-CITY
	  |
	  |-\DLOADS
	  | |------\SYSOP
	  | |------\MISC
	  |
	  |-\GFILES
	  | |------\MENUS
	  | |------\WWIV
	  |-\MSGS
	  |-\TEMP1
	  |-\TEMP2

	A general description of each directory and the files contained
	therein is covered here:

		4.3.1  DATA. This directory contains the core data files for the
		BBS. User records, subboard and transfer directory data,
		archiver, color, and menu configurations, are all stored here.

		NOTE: If you don't backup your data regularly, you should start
		now with this directory. Disk or data errors here will devastate
		your BBS and you will find yourself starting over from scratch.

		The subdirectories REGIONS and ZIP_CITY contain area code and
		zip code information for deriving locational information.
		Regular updates to these files are on the WSS web site and
		Support Boards.

		4.3.2  DLOADS. This is the base directory for files that you
		will make available to your users. You may choose to store a
		majority of your files on other drives or partitions.  It is
		recommended that you *DO NOT* move the SYSOP subdirectory.
		This is the directory where files that only you have access to
		are stored.  You may also have set options that force all
		uploaded files into this directory.

		4.3.3  GFILES. This is the "General Files" directory.  Basic
		menu and text files are stored here. Subdirectories are created
		here when GFILE sections are added.  You will need to move the
		text files you want your users to have access to via the GFILES
		section there.

		New to v4.30 are configurable menu sets. The subdirectory
		MENUS contains subdirectories consisting of complete Menu
		Sets and a single file named DESCRIPT.ION. This should be the
		only file in MENUS and is NOT editable. The subdirectory
		MENUS\WWIV contains the default WWIV Menu Set. See
		Section 4.7 for information on Menu Sets.

		4.3.4  MSGS. This is where all messages and email is stored.
		As with your DATA directory, these files should be backed up
		regularly.

		4.3.5  TEMP<inst>. As described earlier, the TEMP directories
		are used to store runtime and working files.  These directories
		are purged at logoff.


	4.4 Menu System Setup. WWIV comes with a default menu setup that is
	installed for you by INIT.	You can make modifications to the menu
	system easily using the internal Menu Editor or an optional external
	editor for Windows. [???]

	4.5 Multi-Instance Setup. Many have wondered why WWIV is called
	"multi-instance" instead of multi-line or multi-node.  The reason
	is simple; it is both multi-line and multi-node and we wanted a way
	to convey this.  WWIV uses a single USER.LST that can be accessed
	simultaneously by instances that may be on a Local Area Network, a
	single machine that is multi-tasking, or from remote locations via
	modems over multiple phone lines.  Because WWIV literature has
	always referred to BBSs on WWIV-based networks as nodes, we wanted
	to avoid the confusion that could result from use of that term and
	we wanted to convey that it was much more than merely multi-line.

		4.5.1 Multi-Instance Requirements. WWIV is distributed as a
		two-instance BBS. The registered sysop is entitled to use these
		two instances as two remote lines, two local instances (no
		telephone line) or a combination of the two.  The unregistered
		sysop is expected to use it with no more than one telephone line
		connected to it although it may be used with a local access and
		a telephone line.  Persons wanting to have more than two lines
		and who are registered sysops are referred to the Upgrade
		information contained in Section [???].  The costs of upgrading
		to more instances is contained there along with information
		regarding how to obtain this upgrade.

			4.5.1a	Registration Requirement. To have more than one
			phone line connected to your BBS OR have more than two
			local instances (assuming no remote lines), you are required
			to register the software.  With registration and an upgrade,
			you can increase the number of instances up to a theoretical
			maximum of 999 instances. This is referred to as a
			theoretical maximum because, to our knowledge, no one has
			tested the software on more than 38 instances.

			4.5.1b Hardware Requirements. The hardware required to run
			multiple instances is largely a function of the type of
			setup that you have and the type of additional software
			that you may be using. For example, to run WWIV using
			OS/2(TM) or Windows (TM) as your multi-tasking or operating
			system, you will need more memory available than if you were
			to run the BBS on multiple computers connected on a LAN.
			After all other software is loaded, you need a minimum of
			580k of free lower memory to successfully run most
			operations.  Other sections of this documentation provide
			advice from sysops who have operated WWIV in various
			environments.

				Windows (TM) - See Section [???]
				Windows for Workgroups - See Section [???]
				OS/2 - See Section [???]
				OS/2 Warp - See Section [???]
				Novell Netware - See Section [???]
				Lantastic - See Section [???]

			4.5.1c	Software Setup. INIT must be run for each instance
			that you wish to use. You are able to identify which
			instance you are working with by the following command to
			INIT:

				INIT.EXE ,x

			where x represents the number of the instance you wish.
			If the instance has a modem attached to it, you should
			define the comport and select the modem type. If there
			is no modem attached, you may ignore the comport and
			other modem options.

			The path to the TEMP directory is set by default to
			TEMP<instance> and the directory is created for you.
			If you want to use another directory or name, you will
			have to rename the directory both in INIT and in DOS.
			If batch downloads are permitted for this instance, you
			must define a batch directory. To avoid confusion, use
			the same directory defined as your TEMP directory.

			INIT.EXE will permit you to run it with any number
			following it; however, it will only create a viable setup
			for you if you have upgraded your software (See
			UPGRADE.FRM), to have that number of instances enabled.

		4.5.1d Instance Batch files.  To invoke multiple instances of
		the BBS, you will need to create a batch file for each
		instance or use the universal example.	Here are several
		commented examples:

		WWIV.BAT
		========
		@ECHO OFF
		REM - Batch to invoke an instance
		REM - This is a univeral batch that is called with the instance
		REM - to invoke and any other parameters from the commandline.
		REM - Examples:
		REM - WWIV 1	   ; Startup Instance 1
		REM - WWIV 2 -U1   ; Startup Instance 2 with User #1 logged on

		REM Change drive/directory to BBS location
		X:
		cd \BBS

		REM Define the Instance environment variable
		SET WWIV_INSTANCE=%1

		REM Add commands here to initialize the fossil driver

		:LOOP
		bbe.exe -i%1 -o -n0 -a2 %2 %3
		if errorlevel 2 goto END
		goto LOOP

		:END
		REM Add commands here to terminate the fossil driver

		TELNET.BAT
		==========
		@ECHO OFF
		REM - Batch to invoke a telnet instance
		REM Change drive/directory to BBS location
		X:
		cd \BBS

		REM Define the Instance environment variable
		SET WWIV_INSTANCE=3

		REM - No fossil setup required if using COM/IP

		:LOOP
		bbs.exe -i3 -o -n0 -a2 %2 %3
		if errorlevel 2 goto END
		goto LOOP

		:END

		LOCAL.BAT
		=========
		@ECHO OFF
		REM - Batch to invoke a local only instance
		REM Change drive/directory to BBS location
		X:
		cd \BBS

		REM Define the Instance environment variable
		SET WWIV_INSTANCE=2

		:LOOP
		bbe.exe -i2 -o -n0 -a2 -m
		if errorlevel 2 goto END
		goto LOOP

		:END



=======================================================================
5  Operating the BBS.
=======================================================================

   This chapter covers basic operation of the BBS and system editors.
   With v4.30, the BBS uses FOSSIL based communication with the com
   ports.  Prior to starting the BBS, you must install a Revision 5
   compliant FOSSIL driver.  Known working drivers include X00, BNU,
   ADF, COM/IP, and WinFossil.  See the driver documentation for setup.

   5.1 Starting the BBS.  Once the FOSSIL driver is installed, you
   are ready to start the BBS. The use of a batch file is recommended
   since there are various settings and commands that must be issued
   prior to the BBS actually running.

    5.1.1 Startup Batch File.  A normal batch file may look
        as follows:

        @ECHO OFF
        REM ***** Sample batch file for running the BBS on Instance 1:
        REM ***** First, set the environment variable for the instance:
        SET WWIV_INSTANCE=1
        REM ***** Change drive and directory to the location of the BBS
        d:
        cd \bbs
        REM ***** Looping the BBS to include a reload of the fossil
        REM ***** driver is recommended after every user.
        :LOOP
        REM ***** Load the fossil driver in the beginning of the loop.
        REM ***** X00 or BNU work fine in DOS or a DOS box.
        REM ***** WinFossil or ADF will work well for Windows.
        REM ***** X00 command lines are used for an example.  You will
        REM ***** have to adjust these for your system.
        REM ***** Setting of TX/RX buffers is NOT recommended for any
        REM ***** fossil driver.  Allow the fossil to set them.
        REM
        REM X00.EXE E B,1,115200
        REM             
        REM              rate of your com port
        REM           com port -1 COM1=0 COM2=1 etc...
        REM          baud settings
        REM         Eliminates the X00 info splash
        REM     X00.  Must be in the BBS dir or path
        REM
        REM  Next call XU.EXE, the runtime interface for X00.  It has
        REM  to be called twice, once to turn the port on, again to
        REM  lock the port.
        REM
        REM XU.EXE PORT:<x>:<ON | OFF>
        REM                  
        REM                    turns port ON or OFF
        REM              com port -1 COM1=0 COM2=1 etc.
        REM          addresses command to the port
        REM     interface while X00 is active
        REM          locks baud rate of port
        REM              com port-1 COM1=0 COM2=1 etc.
        REM                  baud rate to lock port at
        REM                       sets parity on port
        REM                     
        REM XU.EXE LOCK:<x>:<baud>:8N1
        X00.EXE E B,1,115200
        XU.EXE PORT:1:ON
        XU.EXE LOCK:1:115200:8N1
        REM ***** Load the BBS  -o  = Exit after one user
        REM *****               -n0 = Error level 0 on normal exit
        REM *****               -a2 = Error level 2 on abnormal exit
        REM *****                %x = Allows passing of other parameters
        REM *****                     on the command line (i.e. WWIV -m)
        bbs.exe -o -n0 -a3 %1 %2 %3
        REM ***** If the BBS exits abnormally go to the specified label.
        if errorlevel 3 goto ABNORMALEND
        REM ***** Errorlevel 2 is a normal quit or escape from the BBS
        if errorlevel 2 goto END

        REM ***** Otherwise, turn of and unload the fossil driver
        XU PORT:1:OFF
        X00.EXE
        REM ***** And go back to the top of the loop to reload.
        goto LOOP

        REM ***** Actions to be performed if the BBS exits abnormally
        :ABNORMALEND

        REM ***** Nothing goes below this label
        :END

        5.1.2 Command line Arguments.  The BBS accepts 14 different
        command line options:

          /B - someone already logged on at rate (modem speed)
          /S - used only with /B, indicates com port speed
          /N - normal exit level
          /A - abnormal exit level
          /R - specify max # minutes until event
          /O - quit WWIV after one user done
          /H - don't hang up on user at log off
          /M - don't access modem at all
          /F - pass full result code (CONNECT 9600/ARQ/HST/HST/V.42BIS)
          /C - enable CTS/RTS flow control
          /P - Set System Password to <password>
          /U - pass user number online
          /E - load for beginday event only;
          /? - display command line options

    5.2 Waiting for Caller (WFC) Screen.  New to v4.30 is an optional
    full screen WFC that provides information to the sysop whenever the
    BBS is idle.  The screen looks as follows:

Ŀ
 Date: 02/20/2000  Time: 11:33:00   Multitasker: Windows 98          

Ŀ
           Activity and Statistics of My New WWIV BBS Node 1          
Ĵ
 Calls Today....... 0               WWIV Version... WWIV v4.30       
 Feedback Waiting.. 1               Net Version.... 37               
 Uploads Today..... 0               Total Users.... 1                
 Messages Today.... 0               Total Calls.... 1                
 Local Msgs Today.. 0               Call/Day Ratio. 0.01             
 Email Today....... 0               Chat Status.... Not Available    
 Feedback Today.... 1               Modem.......... USR Courier v.Ev 
 Mins Used Today... 1  Mins (0.5%)  Modem Status... Waiting For Call 
Ĵ
 Hard Disk Space Left:       Last User:                              
 Drive C..    2047.7 Megs    New Sysop #1                            
                            Ĵ
                             Instance Monitor - Node 1               
                             User.... Waiting for Call               
                             Status.. Offline                        

Ŀ
                                                                      


    Also included is a definable screen saver.  See WWIV.INI for
    enabling and disabling these features.

    5.3 Logging on.  From the keyboard, local logons are initiated from
    the WFC using the SpaceBar.  You will see the "Logon?" prompt.  If
    this is your first logon, hit Y and follow the prompts to establish
    your account.  If you have already    established your account, hit
    F for a "fast" logon or Y to logon normally.  SL255 users numbered
    1 through 10 may use a fast logon by hitting the SpaceBar and their
    user number.

    Note: This feature only works for SL255 users.

    Once this logon process is complete, the last few callers and
    user information screens will be presented and you will be
    located at the Main Message Base prompt.

    5.4 User Online keys.  User online keys are used to perform
    certain actions on the system or the user while he or she is
    online.

        5.4.1   F1 - QuickEdit User Account.  Pressing the F1
                key while a user is online will produce a pop
                up box containing the current users access levels,
                restrictions and other pertinent information.  You
                can tab through the fields an edit this information
                as needed.  Pressing F1 again closes the pop up.
                A [WAIT] prompt is displayed to the user while
                editing and all caller input is ignored. This is
                the first User online key you will use.  After
                logging on and establishing your sysop account, hit
                this key and give yourself maximum values as displayed
                below:

  Ŀ
   SECURITY LEVEL    : 255           MESSAGE AR  : ABCDEFGHIJKLMNOP   
   D/L SECURITY LEVEL: 255           DOWNLOAD AR : ABCDEFGHIJKLMNOP   
   EXEMPTIONS        : 31            RESTRICTIONS:                    
  Ĵ
   SYSOP SUB : 999                   TIME BANK  : 0                   
   ASS POINTS: 0                     GOLD POINTS: 0                   
  Ĵ
   KB UPLOADED     : 0               KB DOWNLOADED   : 0              
   FILES UPLOADED  : 0               FILES DOWNLOADED: 7              
   MESSAGES POSTED : 0               NUMBER OF LOGONS: 1              
  Ĵ
   NOTE: The SysOp!!                                                  
  

            5.4.1a  Shift+F1 - Toggle Global Session Capture.  Toggles
            the capture of all online activity to GFILES\GLOBAL.TXT.
            Press the key combination again to turn the capture off.

            5.4.1b  Ctrl+F1 - System Shutdown. Notifies all online users
            of a system-wide shutdown in three minutes.  At the end of
            the three minute period, all users are logged off.

        5.4.2   F2 - Toggle Top Screen Information.  There are three
        toggles of the Top Screen with F2; System Status, Caller Status,
        and none. SL255 users locally logged on default to no Top
        Screen.  If you want to turn it on, hit the F2 key.

            5.4.2a  Shift+F2 -
            5.4.2b  Ctrl+F2 -

        5.4.3  F3 - Disable COM.  Suspends all user input until the F3
        key is pressed again.

            5.4.3a  Shift + F3.
            5.4.3b  Ctrl  + F3.

        5.4.4  F4 - Turn off Chat Call.  Turns of the Sysop chat call
        sound.

            5.4.4a  Shift + F4.
            5.4.4b  Ctrl  + F4

        5.4.5  F5 - Hang up on User.  Hangs up on the user online with
        no warning.

            5.4.5a  Shift + F5 - Line Noise Hang up. Outputs random
            characters to the comport and hangs up on the user.
            5.4.5b  Ctrl  + F5 - Timeout Hang up. Sends the user a "Call
            back when you are there." message and hangs up on the user.

        5.4.6  F6 - Sysop Alert.  Toggles an alert sound for the sysop
        when the user logs off.

            5.4.6a  Shift + F6.
            5.4.6b  Ctrl  + F6.

        5.4.7  F7 - Increase Time Online. Adds 5 minutes to users time.

            5.4.7a  Shift + F7.
            5.4.7b  Ctrl  + F7.

        5.4.8  F8 - Decrease Time Online. Subtracts 5 minutes from users
        time.

            5.4.8a  Shift + F8.
            5.4.8b  Ctrl  + F8.

        5.4.9  F9 - Temp Sysop. Grants Temporary Sysop status to the
        user online.  Use caution with this key.  The SL of the user
        online is changed to 255 giving the user full access to the BBS.
        System passwords are still required just as if you were online.
        You may type in the system passwords where required but they
        will not be echoed to the users screen.  The 255SL is terminated
        when you press the F9 key again or when the user logs off.  You
        may want to use this key in concert with the F3 key to disable
        com input.

            5.4.9a  Shift + F9.
            5.4.9b  Ctrl  + F9.

        5.4.10 F10 - Enter Chat Mode.  This key activates the
        selected chat mode.  You may select "split screen" chat by
        setting the 2WAY_CHAT INI option to Y.

            5.4.10a  Shift + F10 - DOS Shell. Invokes a local DOS
            shell while user is online.  A [WAIT] prompt will be
            displayed to the user and all remote user input is
            suspended.

            5.4.10b  Ctrl  + F10. Change Chat User.  Allows the
            sysop to change the name used in chat mode then invokes
            the chat session.

        5.4.11 Alt-F Keys.  Hitting any Alt-F key combination
        while a user is online will apply the validation template
        assigned in INIT to the users account.

        ***CAUTION An Alt-F key combination while you are online
        will apply the template to your account.  No permanent
        damage will be done, but you will have to reset all access
        levels for yourself manually.

        5.4.12 Home - While in chat mode, you can use the Home key to
        capture the entire chat session to GFILES\CHAT.TXT.

    5.5 Top Screen Information.  The local sysop's screen can show two
    screens of information, which may be toggled with the F2 key. The
    first screen is System Status. The second screen is User
    Status of the current user online.

        5.5.1 System Status Top Screen.  The system status topscreen
        information shows the following data about the status of the
        system.  The first line contains the BBS name and today's date.
        The second line indicates the total number of users, total calls
        to date, calls today, and number of posts today. The third line
        displays the current user's name (alias) and number, time the
        system has been active today, percent of time today the system
        has been used, and amount of e-mail sent today. The latter
        statistic as well as the number of posts today includes both
        local and network information, if the board happens to be
        participating in the network. The fourth line shows the current
        user's security level, download security level, time left,
        feedback waiting for the sysop, files uploaded today, and
        feedback sent today.

        5.5.2 User Status Top Screen.  This top screen shows
        various information concerning the current user online.
        The first line contains the user's name (alias) and number, mail
        waiting for user, uploaded files and kilobytes, security level,
        total logons, and posts.  The second line contains the user's
        real name, phone number, callsign, downloaded files and
        kilobytes, download security level, total time on, and e-mail
        sent.  The third line contains the user's AR and DAR,
        restrictions, exemption, logons today, and feedback sent. The
        fourth line shows the user's note, sex, age, computer, time
        left, and feedback waiting for the sysop. A fifth line may
        appear after a caller requests a chat.  This line would give
        the reason the caller entered for wanting to chat. The border
        line at the bottom of the topscreen information may also show
        the following flags to alert the sysop of the current status of
        the user and system:

            5.5.2a Temp Sysop flag.  This flag appears when the sysop
            has toggled temporary sysop status with F9.

            5.5.2b Capture flag.  This flag appears when the sysop
            has toggled the global capture with Shift-F1.

            5.5.2c Alert Flag.  This flag appears when the sysop has
            pressed F6 to be informed when the caller hangs up. When
            Alert has been toggled on, the computer will beep after the
            current user logs off, and will not return to WFC so that
            the sysop can log on locally.

            5.5.2d Comm Disabled flag.  This flag appears when the
            sysop has pressed F3 to prevent the caller from typing.

            5.5.2e Available flag.  This flag is displayed when the
            sysop has toggled the sysop available for chat option
            with scroll-lock key.

        5.5.3  Abbreviations used in the Topscreen Information.

        W  - Mail waiting for caller    SL - Security Level
        R  - User restrictions          DL - Download Security Level
        AR - User AR/DAR                PO - Total # of posts
        LO - Total number of logons     ES - Total e-mails sent
        TO - Total minutes on           FW - Feedback waiting for sysop
        FS - Total feedback sent        EX - User exemptions
        UL - Kilobytes uploaded         DL - Kilobytes downloaded

    5.6  Messaging System.  Message bases are sometimes referred to as
    "subs".  These are areas on the BBS where messages related to
    particular subject areas may be kept.  Any topic you can imagine
    may be used for a sub. Common examples include politics, science
    fiction, entertainment, sports, trivia, etc.  WWIV based networks
    have subs on every imaginable topic.  You may want to join such a
    network to offer a more diverse array of topics in your message
    bases.

    The very first sub on your BBS should be one where you alone can
    post messages.  This is your place to make announcements concerning
    your system etc.  You can force users to read this sub any time
    there are new messages using the USE_FORCE_SCAN and
    FORCE_SCAN_SUBNUM INI settings.  See WWIV.INI for more information
    on these settings. Users who have the appropriate SL and ARs can
    read the message bases and post on them. These messages are not
    private and may be read by anyone else who has the appropriate SL
    and ARs.

    *** NOTE:   Because the more message bases and directories that you
    create, the more memory is required for pointers and so forth, it
    is advisable to set the number of message bases to the next highest
    multiple of 32 over the number that you actually intend to use.
    This will help conserve memory.

    Message bases are setup by using the BOARDEDIT feature. This
    feature may be accessed in the following ways:

        [1]  From WFC, enter B and then enter the system
             password when prompted for it.

        [2]  From the main menu, enter //BOARDEDIT and then
             enter the system password when prompted for it.

        [3]  From the main menu, enter //BE (short form for
             BOARDEDIT and the system password when prompted
             for it.

        5.6.1 BoardEdit. Using BoardEdit, you can delete, insert, and
        modify subs.  The default installation sets up one sub-board
        named General.

        The first thing that is seen when BoardEdit is accessed is a
        Substring? prompt. If you wish to go directly to an existing
        subboard, enter a portion of the name, otherwise hit enter for
        a complete listing.

        You will see a screen that looks like the following after you
        have chosen to insert or modify your listing.  A description of
        each setting is included below:
        Ŀ
           Subboard      : 0                              
           A. Name       : General                        
           B. Filename   : GENERAL                        
           C. Key        : None.                          
           D. Read SL    : 10                             
           E. Post SL    : 20                             
           F. Anony      : No                             
           G. Min. Age   : 0                              
           H. Max Msgs   : 50                             
           I. AR         : None.                          
           J. Net info   : Not networked.                 
           K. Storage typ: 2                              
           L. Val network: No                             
           M. Req ANSI   : No                             
           N. Disable tag: No                             
           O. Description: None.                          
                                                          
           Which (A-O,[,],Q) ?                            
        

        A.  Name. Each sub-board needs a name, describing what type of
        messages are expected on that sub-board. If your BBS is a
        member of a WWIV network, the software will insert either <Net>
        or [Net] preceding the sub-board name when the sub listing is
        obtained.  The difference between these two uses of NET is
        discussed below under the Network Validation Option.

        B.  Filename. Each sub-board also needs a UNIQUE filename. If
        two subs have the same filename, BOTH SUBS WILL REFER TO THE
        SAME MESSAGES.  The filename can be whatever you want (up to 8
        letters in length), but it must not contain an extension.  For
        example, WSSYSOP would be a legal name to enter, but
        WSSYSOP.SUB would be illegal because it uses an extension.  It
        is recommended that you develop a naming convention for your
        networked message bases to identify the file that belongs to a
        particular sub.  Using the sub above, if you subscribed via
        WWIVnet, you may want to name the file WWSSYSOP.  The prepended
        W identifies the file as subtype WSSYSOP on WWIVnet.

        C.  Key.  Normally, all sub-boards are assigned a number (in
        ascending order, starting at one for your first sub-board)
        which callers can press to immediately access them. If you
        would prefer that a sub-board be referred to by a key (such
        as %,&,#, etc) instead of a number, setting the key to that
        character will do so. This option will not normally be used.

        D.  Read SL. This setting determines the minimum SL required to
        allow a caller to read messages on the sub-board. If the read
        SL for a sub is 40, and a caller's SL is 39, that caller will
        never know that the sub-board exists.

        E.  Post SL. This setting determines the minimum SL required
        for a caller to post on the sub. The post SL should be greater
        or equal to the read SL. Having the post SL greater than the
        read SL would allow callers to read messages on the sub, but
        not post any.  This type of setting is often useful on some
        network subs where anyone may be permitted to read the sub, but
        posting may be only by certain persons (perhaps the sysop
        and/or the co-sysops.)

        F.  Anony.  Setting the anony (no, yes, forced, dear abby)
        determines whether or not messages posted on that sub can be
        anonymous. No means no anonymous (unless the caller has a
        security level which permits it); yes means the caller has the
        option of posting anonymously, regardless of security level;
        forced means the post is always anonymous; dear abby means that
        the caller will be presented a choice of "signatures" for
        his/her post: their name (alias), Abby, or Problemed Person.
        In effect, the "dear abby" option does the same thing as
        setting anony to yes, but it gives the caller two options on
        which name will represent the author of the post.  This option
        is ignored on all networked message bases.

        G.  Min age.  This will allow you to specify the minimum age of
        callers on that sub.  If, for example, you set the minimum age
        to 18 (years), anyone under 18 would not know the sub existed.
        This setting is normally used for adult-oriented subjects.

        H.  Max msgs.  This sets the maximum number of messages that
        can be on the sub at one time. This is usually set to 50 or
        100, but can be up to 999.  When the maximum number is reached,
        the oldest post in the sub is rotated off (deleted) as each new
        post is entered, unless a post has been given permanent status.
        A post with permanent status means that it will not be erased.
        This is useful if you have posted the sub rules or something as
        the first message on the sub.  To give permanent status to a
        post, you hit N after reading the post.  You will see the
        message, "This post will NOT be auto-purged.

        I.  AR.  This allows you to specify the AR for that sub. AR is
        used to allow specific people to access specific subs when
        other sub limitations (age, post SL, etc) are not sufficient
        for your needs. As an example, suppose you have a group of
        Amiga callers on your BBS. You want to give them their own area
        to talk about Amigas. Age and SL restrictions would be
        cumbersome and inefficient.  That is where AR comes into play.
        There are 16 different AR flags that can be used, A through P.
        To give the Amiga callers their own sub, you would use this
        setting to assign an AR to the sub.  You can use any letter
        (A-P) you wish, as long as it isn't in conflict with another
        sub which doesn't concern the Amiga people (you can use the
        same AR on different subs, but realize that anybody with the
        same AR flag set would be able to access all subs with the
        identical AR).  For this example, you could set the AR flag to
        A. Then you would go into UEDIT and activate each Amiga
        caller's A flag.  Now, all Amiga callers would be able to
        access the Amiga sub (as long as SL and age requirements, if
        any, were met) and nobody else would know the sub exists.

        J.  Net info. Used with WWIV network software on network subs
        to properly allocate messages. If the sub you are editing is not
        a WWIV network sub, leave this blank.  If you select this
        option, you will get a sub-menu asking for information
        regarding Network, Type, Host, and Flags. As you enter the
        information, you will receive helpful prompts.  The Networks
        that are recognized are those that you have setup in the INIT
        program.

        NOTE:  When setting up a networked message base, this is the
        first  setting you should enter.  Some of the fields will be
        filled out for you if you have a current SUBS.LST file for
        the specified network.

        TYPE refers to the Subtype.  Under WWIV v4.21a and NET31 or
        earlier, these subtypes had to be integer values; under NET32
        and WWIV v4.22, you may use 7 letter character names for the
        subtype.  This option is referred to in WWIV literature as
        "sub-by-name".

        HOST refers to the network host of the sub; if you host it,
        the information will display HERE; otherwise, the host's
        network node number will be shown.

        SUBS refers to the number of subscribers on the sub and is
        displayed only when you are the sub host.

        FLAGS refers to whether the sub is auto-requestable and whether
        or not the information about the sub should be reported in the
        SUBS.LST distributed on each network. For more information on
        this, refer to the WWIVnet Documentation that accompanies the
        Network Software.

        There will also be an appended category on subs you host.  If
        this is chosen, a list of  available categories (distributed
        by the NC for the network) will be given.  The purpose of this
        is to allow the sysop to select the most appropriate category
        (for that sub information) for listing in the Subs List that
        is distributed by each network.

        K.  Storage type.  There are 2 main ways messages can be
        stored, either with each message in its own file, or with all
        messages in that message base in one large file. 0 means each
        message will be in its own (text) file, 2 means all messages
        in that sub will be in one large (non-text) file.

        L.  Val Network. This option may be toggled on or off.  If
        toggled on, sub-board that are network subs, will have the
        network name enclosed in brackets (i.e. [WWIVnet]) in front of
        the name and the sysop will need to validate the messages
        received there before the messages will be sent over the
        network.  If the option is toggled off, the sub will have
        the network name enclosed in v-brackets (i.e. <WWIVnet> in
        front of the Sub-Board name.  Because many network subs have
        various restrictions (such as no ANSI posts, or posts from #1
        on the BBS only, etc), network validation is a means of
        insuring that posts originating from this BBS are in compliance
        with the sub-host's rules.

        M. Req. ANSI.  The sysop can require that the user have ANSI
        enabled in order to view this sub.  This option is particularly
        useful if the sub is one of ANSI pictures drawn with The Draw or
        some other ANSI editor.  An example of an all ANSI sub is the
        WWIVnet Sub known as The ANSI Art Gallery.

        N. Disable Tag. This option, if toggled on, will disable
        taglines in the messages. This may be useful if a network sub
        host does not permit posts which have taglines added to them.

        O. Description. This option permits you to supply a
        description of a sub that you host.  This description will
        be used in the SUBS.LST file maintained by the network. The
        entry in this field makes it possible for subs you host to
        be included in the SUBS.LST without your intervention; the
        only requirement is that the auto-info option in FLAGS be set
        when the sub is set up.

    5.7  Email System.  The email system in WWIV allows the sending
    of email to other users on the system as well as other users in
    WWIV based networks you participate in and even to Internet
    users if you have the appropriate add on software installed.
    Sending email is as easy as hitting th E key at the WFC or
    online.  You can email a local user by name or number.  For
    sending WWIV based network mail, see the network documentation
    for addressing.  If you have installed the PPP Project,
    Internet email addressing is standard.

    5.8  Transfer System.  The Transfer system allows you to make
    files available to your users for downloading.  Two default
    directories are created upon installation, Sysop and
    Miscellaneous.  The Sysop directory is accessible only to
    SL255 users by default.   It should be used for storage or
    uploading of files prior to cataloging.  You may wish to setup
    many directories or only a few based on your setup.

    Transfer directories are setup by using the DIREDIT feature. This
    feature may be accessed in the following ways:

        [1]  From WFC, enter D and then enter the system
             password when prompted for it.

        [2]  From the main menu, enter //DIREDIT and then
             enter the system password when prompted for it.

        [3]  From the main menu, enter //DE (short form for
             DIREDIT and the system password when prompted
             for it.


        5.8.1 DIREDIT. The first thing that is seen when the
        directory editor is accessed is a Substring? prompt.
        If you wish to go directly to an existing directory, enter a
        portion of the name, otherwise hit enter for a complete
        listing.  The listing of the directories will appear like this:

        Ŀ
         NN   DAR Name                     FN       DSL AGE FIL PATH  
         ==== --- ======================== -------- === --- === ------
         0     Sysop                    SYSOP    100 0   50  DLOADS\SY
         1     Miscellaneous            MISC     10  0   50  DLOADS\MI
                                                                      
         Dirs: D:elete, I:nsert, M:odify, S:wapDirs, Q:uit, ? :       
        


        The commands are relatively straight forward and work in a
        fashion similar to BOARDEDIT.  Swap directories allows the sysop
        to change the order in which  directories are listed.

        When a particular directory is selected for modification, the
        following is seen:

        Ŀ
           Directory     : 0                              
           A. Name       : Sysop                          
           B. Filename   : SYSOP                          
           C. Path       : DLOADS\SYSOP\                  
           D. DSL        : 100                            
           E. Min. Age   : 0                              
           F. Max Files  : 50                             
           G. DAR        : None.                          
           H. Require PD : No                             
           I. Dir Type   : 65535                          
           J. Uploads    : Allowed                        
           K. Arch. only : No                             
           L. Drive Type : HARD DRIVE                     
           N. //UPLOADALL: Yes                            
           O. WWIV Reg   : No                             
                                                          
           Which (A-M,[,],Q) ?                            
        

        A. Name. The name would be the name that you want the users to
        see.  Sysops generally find it useful to create categories that
        will have like type of files grouped together in the directory.

        B. Filename. This should be a dos legal (i.e. 8 characters or
        less) filename.  The BBS software will append the DIR extension
        to it, store it in the DATA directory and use it to keep
        information in binary format for the board's use.

        C. Path.  The path is the path to the directory.  The path may
        be specified complete or in relationship to the main BBS
        directory.  The example shows one where DLOADS would be a
        subdirectory of the BBS.  If you wanted to put the directory on
        a different drive, you might have something like D:\DLOADS\MISC.

        D. DSL.  The DSL is the download security necessary to have
        access to the directory.  Anyone with that level of DSL or
        higher will have access to the directory unless an upper limit
        is placed on the DSL in the Conference editor by the sysop.

        E. Minimum Age. This allows you to restrict access to people of
        a certain age.

        F. Maximum Files.  This sets the maximum number of files that
        can be held by this directory.

        G.  DAR.  This setting allows you to set an Access Requirement
        on the directory so that the person must have that DAR in order
        to see or access the files in that directory.

        H. Require PD.  This setting asks the user if the file about to
        be uploaded is Public Domain.  If they answer No, it will not
        permit them to upload the file.

        I. Directory Type. This setting allows you to set a directory
        type for this directory.  At the present time, WWIV itself does
        not make use of this variable, but some of the utilities written
        by third parties do make use of it.  In a future version of
        WWIV, this field will allow you to "subscribe" to file areas in
        much the same way as subboards.

        J.  Uploads Allowed.  This setting may be toggled to indicate
        that uploads are not permitted.  Many sysops will leave this as
        allowed and require that uploads go to the sysop using the INI
        setting to force all uploads to the Sysop directory.

        K. Archive Only. Setting this will allow you to require a
        certain type of file extension and no other type may be
        uploaded.

        L.  Drive Type.  This permits the sysop to toggle between HARD
        DRIVE and CD-ROM as permissible types.  If a CD-ROM is used, its
        use will be optimized (i.e. the board will work better and
        faster) if it is identified as a CD-ROM.

        N. //UPLOADALL.  This is a toggle which allows or disallows the
        use of the //UPLOADALL command to function on this file area.

        O.  WWIV Reg.  This is also a toggle and if set to Yes, will
        only allow access to this file are to users with a WWIV
        Registration number defined in the user record.

        5.8.2 ALLOW.DAT and AllowEdit (AE).  This option applies to
        registered sysops only and is associate with the OPT_FAST_Search
        setup.  A program is available called WWSORT.EXE which should be
        run first.  This program creates your original ALLOW.DAT file
        which will permit a fast search for duplicate file names.  The
        ALLOWEDIT option gives the sysop the ability to add or remove
        file names from the binary file.  A sysop might want to add the
        name of a non-existent file if he did not care to have that file
        uploaded to him.  For example, sysops frequently get a "scam"
        uploaded to them called FASTCASH. This "scam" is like a chain
        letter for BBSs. Putting FASTCASH as a file name would prevent
        someone's uploading a file by that name.  By the same token, if
        the sysop needs to remove a filename from the binary list, he
        has the option to do so by using the ALLOWEDIT option.

    5.9  Chains (Door) Setup.  The designation of online programs as
    "chains" originated in Turbo Pascal versions of WWIV when the BBS
    literally "chained" to the program. Although WWIV no longer operates
    in that fashion and is no longer written in Pascal, the CHAINEDIT
    terminology has remained.

    Not all files can be run as external programs from WWIV. Only those
    files that do all I/O through DOS calls can be run. This means that
    Wordstar, WordPerfect, the Norton Utilities, and most other graphics
    programs cannot be run from WWIV unless a redirector such as
    DoorWay (r) is used.

    Chains are setup by using the CHAINEDIT feature. This feature may be
    accessed in the following ways:

        [1]  From WFC, enter C and then enter the system
             password when prompted for it.

        [2]  From the main menu, enter //CHAINEDIT and then
             enter the system password when prompted for it.

        [3]  From the main menu, enter //CE (short form for
             CHAINEDIT and the system password when prompted
             for it.

        5.9.1  ChainEdit (CE). The ChainEdit function is also quite
        similar to the BoardEdit function.  The ChainEdit is a means
        of adding, deleting, or modifying on-line programs.  The
        information presented here should be sufficient to enable the
        sysop to setup many on-line programs.

        When ChainEdit is run, a summary of the chains currently
        available, if any, is presented as a listing. Available options
        are:  Insert, Delete, Modify and Quit. When a new chain is
        inserted or an old entry is modified, the sysop is given a
        chance to change the following data:

        Ŀ
           A. Description  : ** NEW CHAIN **              
           B. Filename     : REM                          
           C. SL           : 10                           
           D. AR           : None.                        
           E. ANSI         : Optional                     
           F. DOS Interrupt: Used                         
           G. 300 Baud     : Allowed                      
           H. Shrink       : No                           
           I. Disable pause: No                           
           J. Local only   : No                           
           K. Multi user   : No                           
           L. Registered by: AVAILABLE                    
           M. Usage        : 0                            
           N. Age limit    : 0 - 255                      
                                                          
           Which (A-N,[,],Q)?                             
        

            A. Description. The description of the chain, printed out
            for callers. For example, you might have something like
            "Food Fight" or "TradeWars."  Many sysops put the version
            number of the game after its title so that users will know
            whether or not a "new" version that they may have seen
            elsewhere is running on this BBS.  Many users will upload
            the "latest" version to the Sysop if that version is not
            currently running.

            B. Filename. The filename actually executed. The program to
            be used can have either an EXE, COM, or BAT extension.
            Programs with a BAS or CHN extension cannot be run from
            WWIV.

            If the game requires a dropfile as a parameter, you can
            use one of the following replacement parameters:

                %1 - CHAIN.TXT
                %A - CALLINFO.BBS
                %C - CHAIN.TXT
                %D - DOORINFO1.DEF
                %O - PCBOARD.SYS
                %R - DOOR.SYS

            These parameters are replaced with a full path and filename
            of the specified text file the bulletin board creates
            holding data about that caller, such as the caller's name,
            security level, time left, etc.  For most programs
            explicitly written for WWIV v4, the parameter should be
            placed after the filename. If you do not, you will see a
            "Parameter file not found" error message. If you see that
            message when running a chain, add the parameter as in
            "tw2002 %C".  If the program is not specifically made for
            WWIV, it may be necessary to run it from a batch file to
            setup other environment variables or settings.  See the game
            documentation for more information.

            C. SL. The SL (security level) required in order to run the
            chain. Most sysops will set this at the level of validated
            users or higher.

            D. AR. The AR required in order to run the chain.  The
            sysop can allow only certain people to play the game by
            adjusting the AR.  This may be particularly useful if the
            game is limited to a certain number of players.  People can
            sign up to play the game and those chosen for the first
            round can be given the appropriate AR.  When the game ends,
            a different group of players can then be given the AR for
            another game.

            E. ANSI. If ANSI is required in order to run the chain.
            Because some games or on-line programs make extensive use of
            ANSI screens, those users who do not have ANSI may
            experience significant problems with the game.  This feature
            allows you to screen out the people who do not have ANSI
            capability.

            F. Intercept DOS calls. Many programs run remotely will not
            have built in code for accessing the modem.  For these
            programs, the BBS should be set to intercept the DOS calls,
            and "re-direct" the output to go to the modem, as well as
            the screen. It is possible, however, that you will have a
            program that will do its own modem access, in which case it
            should be set so that the BBS won't intercept DOS calls.  In
            most cases, you WILL want the BBS to intercept DOS calls.
            If the game does not seem to operate properly, you may need
            to experiment with this setting.  As a general rule, you
            should try having the BBS intercept DOS calls for those
            games designed specifically for WWIV and try having the BBS
            not intercept DOS calls for those games designed to be run
            on other systems.  These settings may still need to be
            changed, but the general rule is sound advice for what to
            try as the initial setting for this variable.

            G. 300 Baud. Some programs use ANSI graphics to such an
            extent that the display rate with 300 baud connections
            would be intolerable.  With this setting, the sysop can
            prohibit 300 baud callers from using the chain.

            H. Shrink. The Shrink feature was introduced in WWIV v4.10.
            This option handles memory very differently from the way it
            is handled if this feature is not used.  With Shrink set to
            off, the BBS remains in memory when you run an external
            program, thus restricting the maximum size of the program
            you can use.  With Shrink set to on, the BBS will
            essentially unload from memory, allowing larger external
            programs to be run.  Shrinking reduces the amount of memory
            the BBS occupies to around 4k.  Other than this different
            way of handling memory, chains run with Shrink operate just
            as they do without Shrink - except for a slight delay when
            entering and exiting the program. If memory is a problem on
            your system, use Shrink.  Otherwise, it isn't necessary to
            use it.  Generally, the larger the program to be run is,
            the more desirable it will be to use the shrink feature.

            I. Disable Pause. This feature was added in v4.20.  Some
            games, such as the on-line program TETRIS, do not work well
            when the BBS attempts to pause the screen.  If the user has
            pause toggled ON in the defaults, then the BBS will attempt
            to pause after the number of lines of vertical height that
            the user had specified.  This option allows the sysop to
            disable the user's pause option as he enters that particular
            program.  When the user exits, the pause status will be
            reset as it was before the program was run.

            J. Local only.  This toggle defines the chain to be run in
            local mode only or unrestricted.

            K. Multi user.  This toggle allows users on different
            instances of the BBS to run the chain simultaneously.  The
            chain itself must support multiple users.  Check the
            documentation for the chain for proper configuration.

            L. Registered By.  If CHAIN_REG = Y in WWIV.INI, you can
            allow users to sponsor chains for your BBS by paying the
            registration fees or some other method you may choose.  You
            can change the sponsor here.

            M. Usage.  The is the number of time the chain has been run.

            N. Age Limit.  This allows chiain access to be limited by
            age.

    5.10 GFILES System.  The GFILES (General Files) section allows you
    to place text files online for your users to read.  Good examples of
    G-Files include the user documentation for the BBS, online games,
    download protocols, editors, or just about any other text file you
    may find useful for your users.  The text files are maintained in
    subdirectories of the GFILES directory.

    G-Files are setup by using the GFILEEDIT feature. This feature may
    be accessed in the following ways:

        [1]  From WFC, enter G and then enter the system
             password when prompted for it.

        [2]  From the main menu, enter //GFILEEDIT and then
             enter the system password when prompted for it.

        [3]  From the main menu, enter //GE (short form for
             GFILEEDIT) and the system password when prompted
             for it.

        5.10.1 G-File Editor (GE).  When the editor is first run, there
        will be no sections present.  To create a new section, choose
        Insert.  The editor will bring up a a screen that looks as
        follows:

        Ŀ
           A. Name       : *NEW SECTION*                  
           B. Filename   : REM                            
           C. SL         : 10                             
           D. Min. Age   : 0                              
           E. Max Files  : 99                             
           F. AR         : None.                          
                                                          
           Which (A-F,Q) ?                                
        

        A. Name.  Enter the name of the G-File section as you want it to
        appear to your users.

        B. Filename.  Enter the name of the data file you wish to
        assign to this section.  The data file will be created in the
        DATA directory to contain all the information on this section.
        You will be asked if you wish to create a directory for the
        section.  It is recommended that you always answer Yes to aid in
        maintenance of the files unless this is to be a single file
        rather than a section of like oriented files.  If this is a
        single file, all you need do is place the text file you want to
        be available in the GFILES directory and rename it with the GFL
        extension. Otherwise, a directory with the name you specify will
        be created as a subdirectory of GFILES.  This is where all of
        the files you want to make available in this section must be.

        C. SL. Minimum SL required to view this section.

        D. Min Age.  Minimum age required to view this section.

        E. Max Files. Maximum number of files allowed in this section.

        F. AR.  AR required to view this section.

    5.11 Menu System.  The menu system has been dramaticly changed in
    WWIV 4.30.   The system is a highly configurable hybrid of the text
    file based menu system of pre 4.30 WWIV and a scripted menu system
    and includes a pull down style menu as an option for your users.
    A list of available menu commands is included in MENUS.TXT in the
    distribution archive.  It is strongly recommended that you print
    the file out and keep it handy when editing your menus.  The menu
    system may appear cryptic at first but rest assured, you will pick
    it up quickly by expirimenting with it.  This feature will allow
    great flexibility to those registered sysops who do not have the
    skills (or desire) to modify the BBS.

    Menus are setup by using the EDITMENUS feature. This feature may be
    accessed in the following ways:

        [1]  From WFC, enter ! and then enter the system
             password when prompted for it.

        [2]  From the main menu, enter //EDITMENUS and then
             enter the system password when prompted for it.

        [3]  From the main menu, enter //EM (short form for
             EDITMENUS and the system password when prompted
             for it.

        5.11.1 Menu Editor. (EM) When the Menu Editor is run, you will
        be presented with a list of available menu sets and will need to
        enter the name of the menu set you wish to edit.  The default
        menu set is named WWIV.  After selecting the menu set, you will
        be presented with a list of available menus in the set.  The
        display will look something like this:

        Ŀ
           WWIV Menu Editor                               
                                                          
           Available Menus Sets                           
           ============================                   
           WWIV     WWIV v4.30 Stock Menus                
                                                          
                                                          
           Enter menuset to edit ?=List : WWIV            
                                                          
           Available Menus                                
           ===============                                
           MAIN                                           
           SYSOP                                          
           VISSYS                                         
           XFER                                           
                                                          
                                                          
           Enter menu file to edit ?=List :               
        

        You will then be able to select the menu to edit.  In the
        default menu set, you can edit the following existing menus:

            MAIN    - The main Message Menu
            SYSOP   - The Sysop Menu
            VISSYS  - The Visiting Sysop Menu
            XFER    - The Transfer Menu

        To create a new menu in the set, enter the new menu name.
        Once the menu has been selected or created, the editor window
        will come up with the menu settings.  The first line (0/105)
        indicates the current record and the total number of records
        in the menu.

        Ŀ
           (0/105)                                              
              Menu Version         : 1.0                        
           0) Menu Description     : WWIV v4.30 Stock Menus     
           1) Deleted              : No                         
           2) Main Menu            : Yes                        
           A) What do Numbers do   : Set sub number             
           B) What type of logging : Key entered                
           C) Force help to be on  : Not forced                 
           D) Allowed menu type    : Regular/Pulldown           
           E) Pulldown menu title  : WWIV Main Menu             
           F) Enter Script         :                            
           G) Exit Script          :                            
           H) Min SL               : 0                          
           I) Min DSL              : 0                          
           J) AR                   : 0                          
           K) DAR                  : 0                          
           L) Restrictions         : 0                          
           M) Sysop                : No                         
           N) Co-Sysop             : No                         
           O) Password             :                            
           P) Change pulldown colors                            
                                                                
                                                                
           0-2, A-O, Z=Add new Record, [=Prev, ]=Next, Q=Quit : 
        

        The following are the settings and what they do:

        0. Menu Description.  This is the name of the menu set to which
        this menu belongs.  This is the description users see when
        selecting a menu set.

        1. Deleted.  If you do NOT want this menu to be available to
        users, set this to Yes.

        2. Main Menu. If this is the main menu for the BBS, set this to
        Yes.

        A. What do Numbers do.  This defines what number keys do in this
        menu.  It can be set to:

            Set sub number
            Set dir number
            Nothing

        B. What type of logging.  This defines what will appear in the
        sysop log when the user executes the commands.  Settings are:

            Key Entered         - Key pressed
            Desc of Command     - Description of the command
            Command Executed    - Hardcoded command executed
            No Logging          - None

        C. Force Help to be on. Self explanatory

        D. Allowed Menu Type.  Defines what menu types are allowed for
        all users.  Choices are:

            Regular             - Regluar menus only
            Pulldown            - Pulldown menus only
            Regular/Pulldown    - Allows user selection

        E. Pulldown menu title.  Title shown in pulldown.

        F. Enter Script.  Not implemented yet

        G. Exit Script.   Not implemented yet

        H. Min SL.  Minimum SL to allow access

        I. Min DSL.  Minimum DSL to allow access

        J. AR.  AR required for access

        K. DAR.  DAR required for access

        L. Restrictions.  Restrictions required for access

        M. Sysop. Toggle for Sysop only menu.  If set to Yes, only SL255
        has access to this menu.

        N. Co-Sysop. Toggle for Co-Sysop menu. If set to Yes, only SL100
        and above have access to this menu.

        O. Password. You can password protect a menu by defining one
        here.  You may also require the system password for the menu by
        entering *SYSTEM in the Password field.

        P. Change pulldown colors.  Self explanatory.

        To navigate the menu, use the [ and ] keys.

        5.11.2  Menu Elements.  Menu elements have the same basic
        configuration as the menu itself and the screen will look much
        the same.

        1) Deleted        : Is command deleted?
        A) Key            : Key(s) to execute command
        B) Command        : Command to execute from MENU.TXT
        C) Menu Text      : What to show on generated menu
        D) PD Menu Text   : What to show on pulldown menu
        E) Help Text      : One line help for command
        F) Inst Msg       : Instance message to send to all users
        G) Sysop Log      : What to show in sysop log
        K) Min SL         : Min SL for command
        L) Max SL         : Max SL for command
        M) Min DSL        : Min DSL for command
        N) Max DSL        : Max DSL for command
        O) AR             : AR required for command
        P) DAR            : DAR required for command
        R) Restrictions   : Restriction required for command
        S) Sysop          : Sysop only?
        T) Co-Sysop       : Co-Sysop only?
        U) Password       : Password for command
        V) Hide text from : Option to hide from menus
        W) Pulldown flags : Set all to Yes for most commands
        X) Extended Help  : Name of extended help file for command

        5.11.3  Menu System Required Files.  There are four basic files
        required for each menu to function.  They must be located in
        the directory defined for the menu set.  Below is a list of
        the files and their function:

        GFILES\MENUS\WWIV\*.IDX, *.MNU -  These binary files are
        generated by the menu editor and MUST NOT be edited using a text
        editor.

        GFILES\MENUS\WWIV\*.PRO, *.PDP - These are the prompts
        associated with the menus.  The *.PRO files are the prompts for
        the regular menus and the *.PDP files are for the pulldown
        menus. Standard WWIV MCI codes are used for the information
        contained in the prompts.  These files may be edited to suit
        using any text based editor.  When creating your own menu sets,
        you must create your own prompt files.  You are advised to start
        with a copy of the prompts from the default menu set and work
        from there.

        5.11.4 Menu System Optional Files.  Text based menus may be
        added for each menu and must also be located in the menu set
        directory.  The file name must be the same as the menu to which
        it is releated and the extension must be *.MSG.  We have
        included a set of text based menus in the default menu set to
        maintain the traditional WWIV look.

        5.11.5 Menu System Support Files.  Support files for the menu
        system are located in the Language directory as defined in
        INIT.EXE.  A majority of these files are those that were
        located in MENUS.ANS and MENUS.MSG in previous versions.  These
        files have been separated into individual files for easier
        maintenance.  Here is a list of the support files and where they
        are diplayed:

        CHAT.MSG     - ChatRoom Menu
        CMDPARAM.MSG - Command parameters for Events Editor
        CS-EMAIL.MSG - Co-Sysop Email Menu
        EDITOR.MSG   - Internal Editor Command Menu
        EMAIL.MSG    - User Email Menu
        LPFREQ.MSG   - File request menu for offline files
        LPSYSOP.MSG  - Sysop Menu for full screen file section
        MBMAIN.MSG   - Messagebase Main Menu
        MBSLASH.MSG  - Messagebase Slash Command Menu
        RS-EMAIL.MSG - Restricted Email Menu
        SMAIN.MSG    - Sysop Main Menu Command Menu
        SMBMAIN.MSG  - Sysop Messagebase Command Menu
        SONLINE.MSG  - Sysop User Online Command Menu
        SRESTRCT.MSG - Sysop User Restriction Menu
        STRANS.MSG   - Sysop Transfer Section Command Menu
        SUEDIT.MSG   - Sysop User Editor Command Menu
        SWFC.MSG     - Sysop WFC Command Menu
        SY-EMAIL.MSG - Sysop Email Menu
        TARCHIVE.MSG - Transfer Section Archive Command Menu
        TBATCH.MSG   - Transfer Section Batch Command Menu
        TSLASH.MSG   - Transfer Section Slash Command Menu
        TTAGGING.MSG - Transfer Section File Tagging Menu

        You may create raw ANSI versions of these files for your ANSI
        users using a third party editor and naming the files with an
        extension of ANS.

    5.12 Event Management.  Also new in version 4.30 are multiple system
    events.  The system events defined in INIT.EXE in previous versions
    have also been moved to the Event Editor.

    Events are setup by using the EVENTEDIT feature. This feature may be
    accessed in the following ways:

        [1]  From WFC, enter H and then enter the system
             password when prompted for it.

        [2]  From the main menu, enter //EVENTEDIT and then
             enter the system password when prompted for it.

        [3]  From the main menu, enter //EE (short form for
             EVENTEDIT and the system password when prompted
             for it.

        5.12.1 Event Editor (EE).  When executed for the first time, the
        event list will be empty.  From this menu, you have the option
        to Insert, Delete, or Execute and event.  The Execute command is
        made available for you to test your event to ensure it performs
        as you expect it to.  When choosing to test the event, you must
        make sure the event meet all the criteria for running at the
        time of the test.  For example, if the event is not set to run
        on Tuesday and you try to test it on Tuesday, it will not run.
        To create a new event, select Insert and the Event Editor will
        be displayed as follows:

        Ŀ
           A. Event Time......: 00:00                     
           B. Event Command...: **New Event**             
           C. Phone Off Hook?.: No                        
           D. Already Run?....: No                        
           E. Shrink?.........: No                        
           F. Force User Off?.: No                        
           G. Days to Execute.: SMTWTFS                   
           H. Node (0=Any)....: 0                         
                                                          
           Which? [A-H,[,],Q=Quit] :                      
        

        A. Event Time.  Set the time for the event based on the 24 hour
        clock.

        B. Event Command.  Set the command to execute.  You will
        normally want to use a batch file to run events but can use any
        executable file as a command.  You may also provide parameters
        to include system based information on the command line.  A list
        of command line parameters for system based information is
        available by pressing the ? key.

        C. Phone Off Hook?.  If you want the system to take the phone off
        hook, during the event, set accordingly.

        D. Already Run?.  If the event has already run for the current
        time period, this will be Yes.  You can change it to No to have
        the event run again if desired.

        E. Shrink?.  If your event requires a large amount of memory,
        set this to Yes to have the BBS shrink out of memory prior to
        event execution.

        F. Force User Off?.  If you want to force all users off the
        system prior to the event running, set accordingly.  Note that
        ANY event that touches the user records, configuration or status
        data files, should have this set to yes.

        G. Days to Execute.  Select the days you want the event to
        execute here.

        H. Node.  Set the node number for the event to run on.  If there
        is only one node operational, the event will run on that node.
        If more than one node is operational, and no specific node is
        specified, the event will run on the first available node.  Note
        and any events that process network data must be run on node 1
        in a multi-instance environment.

        You can use the [ and ] to navigate between events.

        5.12.2 System Events.  Selecting System Events from the opening
        screen of the Event Editor will open the System Events Editor.

        Ŀ
           System Events Configuration                    
                                                          
           1. Terminal Program     :                      
           2. Shrink for terminal? : No                   
           3. Begin Day Event      :                      
           4. Logon Event          :                      
           5. Logoff Event         :                      
           6. Newuser Event        :                      
           7. Upload  Event        :                      
           8. Virus Scanner CmdLine:                      
           Q. Quit                                        
                                                          
           Which? <Q, 1-8, ? = Help>                      
        

        1. Terminal Program.  If you wish to be able to access your
        terminal program by hitting T from the WFC Screen, configure to
        commandline for the program here.

        2. Shrink for Terminal.  If your terminal requires a large
        amount of memory, toggle this to Yes to have the BBS shrink
        prior to executing the command.

        3. Begin Day Event.  The begin day event will run at midnight
        every day.  This is a great place for game maintenance routines
        and other programs that need to run once every day such as
        AutoSend or NFT's cleanup routines.

        4. Logon Event. This event runs each time a user logs on.

        5. Logoff Event. This event runs each time a user logs off.

        6. Newuser Event. This event runs each time a new user logs on.
        
        7. Upload Event.  This event runs each time a user uploads a
        file or a batch of files to the BBS.

        8. Virus Scanner CmdLine.  this is the commandline for your
        virus scanner.

        Again, replaceable commandline parameters are available and the
        list is accessed by hitting ? in the System Events Editor.


    5.13 Instance Management.  Multi Instance or multi-node operation
    allows WWIV to handle multiple callers simultaneously.  In the
    shareware and standard registered versions up to two instances
    of the BBS are available.  Up to 999 instances may be purchased as
    an upgrade.  Pricing information on upgrades is in Appendix B.

        5.13.1 INSTEDIT (IE). This option give the sysop limited editing
        ability on active instances and permits the sysop to shut down
        all instances immediately if necessary.  This can be handy in a
        LAN type operation where all instances may not be visible. Since
        certain types of maintenance (such as those affecting qscan
        pointers or new scan pointers) should not be run if a user is
        on-line, this gives the sysop the ability to give users a 10
        second warning and then shut down the system.

    5.14 Chatroom Setup.  Some will recognize the upgraded Chatroom in
    v4.30 as the chat program WMChat.  The original author, Jeff
    Kronlage donated the WMChat code to WSS for inclusion in this
    and any future releases.  The ChatRoom is configured via the
    CHAT.INI file.  You may edit this file to suit your needs with any
    text based editor.  The file is well commented and should provide
    you with enough instruction to modify the ChatRoom to your liking.

    5.15 Multiple Languages. Beginning with v4.23, WWIV offered the
    sysop the ability to offer multiple languages.  In order to do
    this, the sysop must define the languages and the directories where
    the language is to be found in the INIT program.  For example, one
    might have French and Spanish in addition to English.  English is
    the default language and the menus and help files for it should be
    placed in the GFILES directory.  The menus and help files for each
    of the other languages that you chose to support should be placed
    in the directory that you identified in G-FILES.  If you have
    multiple languages supported, the user will be asked to chose his
    language.  The user may also change language in the Default area of
    the BBS.  In the past, Sysops have volunteered to create and
    maintain language files for certain languages and these are
    available on most of the support BBSs.  Be forewarned that Language
    packages for prior versions of WWIV are not compatible with v4.30.
    New language string files should be available soon after the release
    of 4.30.

=======================================================================
6  Modem Information and Setup.
=======================================================================

  Ŀ
   NOTES:                                                             
                                                                      
   1.  This section of the documentation has not been completely      
   updated but is still technically correct in application.           
                                                                      
   2.  If you arrived here looking for help in trying to set up a     
   WinModem of any type, look no further.  WWIV WILL NOT operate      
   with a WinModem. You are advised to purchase either a US Robotics  
   ZOOM, or Hayes EXTERNAL modem for the best chance of successfully  
   setting up the BBS.                                                
                                                                      
   3. You need not try to set up your modem to connect above 33.6.    
   56k modems will only connect above that speed to an ISP.  The best 
   possible speed connecting two 56k modems over POTS (Plain Old      
   Telephone System) is 33,600 bps.                                   
                                                                      
   4. It is IMPERATIVE that all speeds match when setting up your     
   modem, the BBS and a FOSSIL driver.  Default MS and CS settings    
   must coincide with the locked rate of the FOSSIL driver and the    
   port speed settings if running Windows or OS/2.                    
                                                                      
   5. If you are unable to locate a modem file and have to develop    
   your own configuration, PLEASE send WSS a copy of the final        
   working version.                                                   
  

    This section is provided because so many people have problems
    getting their modems and the BBS to communicate properly.  It is an
    attempt to better describe modems, and how they need to be
    configured in order to run optimally with WWIV. Additionally, this
    describes how WWIV v4.20 and later handle the modem, and how to
    add support for additional modem types.

    6.1  Hayes Compatability.  The first thing you need to be aware of
    is that just about every modem manufactured for the IBM claims to be
    "100% Hayes compatible."  This doesn't actually mean that it is 100%
    compatible, but only that it is relatively close (would you buy a
    modem that is advertised as 99% compatible?).  With 9600 and faster
    modems, Hayes compatibility means very little.  Each modem handles
    high speed differently, and special support may be needed for each
    brand of modem.

        6.1.1 Modem Cables. For external modems, one important feature
        is your modem cable. In order to work correctly with WWIV, the
        following pins need to be connected from the modem to the
        computer (all are pin numbers on the DB-25 connected to the
        modem): 2,3,7,8,20.  If any of these are not connected, the
        modem probably won't work correctly, so you'll need a new modem
        cable. Fortunately, just about all straight serial cables
        manufactured correctly connect these pins. If your modem cable
        has sealed connectors on the ends, don't tear it apart; it is
        probably fine.  However, If you made up your own cable (or had
        someone else make you up one), you might want to check it out.

        6.1.2  Carrier Detect (CD). For both external and internal
        modems, the first important setting you need to have on your
        modem is the carrier detect.  Most modems have two settings for
        carrier detect (or CD).  Either CD is ALWAYS ON, or CD tracks
        the state of the carrier.  Using the second setting, WWIV is
        correctly able to tell if a remote caller is connected by
        checking the CD lead.  But, for some damned fool reason, most
        modem manufacturers set it to default to the always on state.

        6.13  Dip Switches.  On some modems, there will be a physical
        switch that you will need to check (and probably change).  On
        some modems (such as Hayes external), you'll need to pop off
        the face-plate and use a pencil or something to flip the DIP
        switch.  Other external modems may have the DIP switches located
        on the back panel.  So, pull out your modem manual, and check
        which switch affects the CD or DCD lead, and have it set so that
        it ISN'T ALWAYS ON.  Internal modems that have DIP switches
        place the switches on the modem card.

        With some modems, there are "logical" (changed via the keyboard)
        switches that determine the CD status.  The keyboard command for
        the Prometheus 2400G, for example, is &&C1.  The WWIV modem
        configurations default to &&C1 for all 2400 or faster modems.

        6.1.4 Data Terminal Ready (DTR). The second important setting is
        the data terminal ready line (DTR), which is like the CD lead.
        The DTR lead is what WWIV uses to send a 'hang up' command to
        the modem. Usually, the DTR lead is ON until WWIV turns the
        DTR lead OFF, at which time the modem should hang up.  Most
        modems can be set so that the modem will completely ignore the
        DTR status.  Also, by some quirk in the Universe, it is also
        usually set by the manufacturer to ignore DTR status instead of
        correctly looking at it.  So, if you have physical switches on
        your modem, whip out your manual again, and find which switch
        you need to check so that the modem will hang up when DTR is
        dropped.  For the modems without physical switches, you need to
        find the command for that setting.  For the 2400G, the correct
        command is &&D2, which is described as, "Modem goes on-hook,
        assumes command state and disable auto-answer with ON-to-OFF
        transition."  Fortunately, (again), the WWIV modem
        configurations default to setting &&D2 for all 2400 or faster
        modems.

        6.1.5  Options Available if MODEMS.MDM does not work. Contained
        in the WWIV software ZIP file is a file named MODEMS.MDM.  This
        file contains setups (or configurations) for most modems.  The
        .MDM file is what INIT reads to create a modem data file, which
        is what the BBS uses.  If none of the standard configurations
        in the MODEMS.MDM seem to work for your speed/make/type modem,
        you have several options:

        1.  You can 'tweak' an existing configuration in the
        MODEMS.MDM file

        2.  You can build your own configuration and add it to
        the end of the MODEMS.MDM file

        3.  You can create your own .MDM file (file name can
        be named any legal DOS file name, but MUST have
        the .MDM extension

        4.  Login to a WWIV Support Board and look for a file.  New modem
        files are written regularly and most are submitted to SB's for
        inclusion in their file libraries.

        5. Post all pertinent information concerning your modem on
        alt.bbs.wwiv.  There is a large base of WWIV sysops there and more
        than likely, someone has the modem file you need.

        6.  Write WSS for help

        Modem configurations are placed in the BBS data directory, and
        the data itself is stored in text format (for easy editing with
        any ASCII editor). Only the file MODEMS.MDM can contain more
        than one configuration.  Any other *.MDM file can contain only
        one configuration, and does not require a "FILE:" line, as the
        file name (before the .MDM) is the name.  Don't worry, that will
        be explained later. Also, the MODEMS.MDM file is the only file
        that can contain auto-selection lines.

        Described below are examples of the above options.


        WWIV defaults to the optimal setup for most non-MNP 300, 1200
        and 2400 baud modems.  These are the "H0300", "H1200" and
        "H2400" configurations, which are described below. Some modems
        are a bit slow to respond after they send the RING result code,
        and do not properly answer the phone when it rings (despite
        WWIV saying that it has answered the phone).  If the BBS does
        not answer the phone when it should, try one of the "S"
        configurations - "H1200S" or "H2400S". This should take care of
        the problem.  The only difference between the "S" configurations
        and the normal ones is that the "S" configurations have a
        different ANSR: string, which as a "~" (tilde) at the beginning.
        The tilde causes about an 0.5 second delay, giving the modem
        some time before the "ATA" is sent.  If this still doesn't work,
        try editing the appropriate configuration file, and adding an
        additional tilde on the beginning.

        In any case, if you have to modify a part of the default
        configuration file to get your modem to work, please send the
        updated configuration section (be sure to update the modem name
        and description also) to WSS, so that we may include that
        configuration in future releases of WWIV. This will help other
        sysops who purchase the same model modem.

        Some MNP and 9600+ modems require special configuration.
        Fortunately, most of the high-speed modems on BBS's (that I know
        of) are USRobotics modems, and WWIV already knows how to handle
        most USRobotics high-speed modems.

        If WWIV does not currently support the type of high speed modem
        that you have, you can try building your own configuration
        section for it.  However, unless you are VERY familiar with how
        the modem works, I'd suggest not trying that.  Even if you are
        able to use your high-speed modem perfectly with your terminal
        program, the same configuration will NOT work for the BBS.  The
        reason is, in the terminal program, you (the user) are sitting
        there, and are able to interpret the result codes and fix things
        if problems occur.  There is nobody around to help a BBS if it
        gets confused.  Also, the BBS needs very specific information on
        the modem (including flow control, buffering, baud rates, result
        codes, etc.) in order to work properly for the variety of
        callers and modems that connect with it.

        If you are unable to get your own configuration to work (or
        don't want to try), you'll pretty much have to use one of the
        methods described above.  There is a good chance someone will
        already have the configuration file for your modem, and can
        forward it (e-mail) it to you.  When contacting anyone about
        your modem, BE SURE to include as much information about it
        as possible.  Telling someone only that it's supposed to be a
        Hayes compatible modem just won't do it.  They need
        manufacturer, model number, maximum speed and what the modem
        returns when you enter 'AT'<enter> and 'AT0'<enter>
        when in a terminal program.

        If no one has a configuration file for it, then WSS will need
        a fair amount of information on the modem to get it to work.
        In all likelyhood, if you call up technical support for your
        modem manufacturer, and ask them to send WSS (a developer) a
        copy of the manual, they probably won't mind.  With a manual,
        we can probably work it out from there (at no cost to you).
        If you send WSS YOUR copy of the manual, include sufficent
        return postage, return address labels and mailing materials to
        mail it back.  While we will make every effort to help with
        modems at no charge, we will not absorb any costs of doing so.

        If your modem type is not currently supported, we REALLY WOULD
        like to get a configuration setup for that modem and support it
        in WWIV.  Please do not think that we are unwilling to support
        all types of modems.  We want to support them, and will put in
        the time necessary to get your modem working. But remember: we
        will need quite a bit of info on your modem type.

    6.2 About MODEMS.MDM.  Creating a new section of the modem
    configuration file does not require any programming knowledge;
    it only requires in-depth, intimate knowledge of how the modem
    works.  It is not suggested that anyone try to set up their own
    modem configuration section from scratch; rather, take one of the
    existing configurations, and tweak it as necessary.

    Modem configurations are stored in text format (for easy editing
    with any ASCII editor), in *.mdm files in the data directory.  The
    file 'modems.mdm' contains the default configurations (multiple
    configurations).  Any other *.mdm file can contain only one
    configuration, and does not require a "FILE:" line, as the file
    name (before the .mdm) is the name.  Don't worry, that'll be
    explained later. Also, the 'modems.mdm' file is the only file that
    can contain auto-selection lines.

        6.2.1 Explanation of a sample modem file in MODEMS.MDM.  Let's
        start out with a sample configuration (for a 2400 baud modem),
        and explain the various parts of it (this configuration is from
        the MODEMS.MDM file).

        ##########################################################
        #
        # Hayes compatible 2400 baud modems.
        #

        FILE: "H2400"
        NAME: "Hayes compatible 2400"
        NOTE: "If the BBS doesnt answer the phone, try H2400S"
        NOTE: " configuration."
        SETU: "AT&&C1&&D2Q0V1{"
        INIT: "ATC1E0F1H0M0Q0V1X4S0=0S2=1{"
        ANSR: "ATA{"
        PICK: "ATH1{"
        HANG: "ATH0{"
        DIAL: "ATDT"
        SEPR: ""
        DEFL: MS=2400 CS=2400 EC=N DC=N AS=N FC=N
        RESL: "OK"              "Normal"        NORM
        RESL: "RING"            "Ring"          RING
        RESL: "NO CARRIER"      "No Carrier"    DIS
        RESL: "ERROR"           "Error"         ERR
        RESL: "NO DIAL TONE"    "No Dial Tone"  NDT
        RESL: "NO DIALTONE"     "No Dial Tone"  NDT
        RESL: "BUSY"            "Busy"          DIS
        RESL: "NO ANSWER"       "No Answer"     DIS
        RESL: "RINGING"         "Ringing"       RINGING
        RESL: "VOICE"           "Voice"         DIS
        RESL: "CONNECT"         "300"           MS=300   CS=300   CON
        RESL: "CONNECT 1200"    "1200"          MS=1200  CS=1200  CON
        RESL: "CONNECT 2400"    "2400"          MS=2400  CS=2400  CON


        6.2.2  Three Groups.  As you can see, the modem configuration
        is made-up of three groups: The STRING lines (FILE, NAME, NOTE,
        SETU, INIT, ANSR, PICK, HANG, DIAL, SEPR), the DEFAULT SETTINGS
        (DEFL), and the RESULT CODE lines (RESL).

        The "FILE" line gives the "file name" of the configuration.  If
        you took the configuration above (minus the FILE: line), copied
        it from the MODEMS.MDM file, and put it in a "H2400.MDM" file in
        the DATA directory, everything would work exactly the same.  The
        "FILE" entry just allows you to put multiple configurations into
        the MODEMS.MDM file, and not clutter up your data directory with
        lots of *.MDM files that you don't need.

        Each of the strings allows control characters and delays to be
        specified.  A "{" is converted to a carriage-return. A "~" is
        converted into an 0.5 second delay.  Any string such as "^J" is
        converted into the specified control character (here, control-J,
        or a linefeed).  Any string such as "\^" or "\~" quotes the
        character after it, allowing you to put a ^ or a ~ into the
        string.  Also, each string is terminated by either a single or
        double quote. If you need to actually have a ' or " in the
        string, you will need to 'quote' the quote, as in \' or \".

        "NAME:" gives a textual name/description of the modem, which is
        displayed in INIT section 5, along with the file name, which is
        used to help select the correct configuration.

        "NOTE:" A note that is printed out for the user when the
        specific modem configuration is selected, giving any caveats for
        the configuration.  Multiple NOTE: lines may be specified, however
        you will need to end each line with "^M^J" (carriage-return/
        line-feed), so it looks nice for the user.

        "SETU:" gives the setup string for the modem.  This string is
        sent out once each time the BBS is loaded and run.

        "INIT:" gives the initialization string for the modem. This is
        sent out to the modem when the BBS is first run (but after the
        SETUp string), and after each caller hangs up.

        "ANSR:" gives the string sent to the modem to tell it to answer
        the phone (such as after the RING result code is received).

        "PICK:" gives the string to pick up the modem (take the phone
        off-hook), to prevent users from calling and getting a ring
        (thus thinking the BBS is down).

        "HANG:" gives the string to hang up the phone (after the PICK
        string is sent).

        Most any modem will probably use the same strings for ANSR,
        PICK, and HANG.  (Except, some modems (as noted earlier) are
        slow, and need the answer string to be "~ATA{" (pause 1/2
        second before sending the answer string).

        "DIAL:" gives the dial prefix.  If your phone line does not
        support tones, then changing it to "ATDP" will use pulse
        dialing.  Putting "ATB1DT" will cause a USR Dual Standard to
        dial out with the HST protocol (instead of V.32, since "B0"
        is in the init string).

        "SEPR:" gives separation characters for the result codes.  This
        will be discussed later, under the high-speed modem section.

        "DEFL:" gives the default modem setup.  It gives, essentially,
        modem result configuration info.

        "RESL:" gives modem result code info.  There are two strings,
        then the result configuration info.  The first string is the
        actual "result code" received from the modem.  Here, verbose
        result codes are used. (All result codes are converted to
        uppercase).  The second string is the description of the result
        code, presented to the user.  The result configuration info
        gives information describing the modem result code.  The
        possible strings in this area are:

            NORM          normal state of modem
            RING          phone is ringing
            RINGING       remote phone is ringing
            ERR           error encountered
            DIS           disconnected (No connection)
            NDT           no dial tone (same as DIS)
            CON           connection established
            MS=           modem speed
            CS=           com port speed
            AS=           asymmetrical baud rates (Y/N)
            EC=           error correcting (Y/N)
            DC=           data compression (Y/N)
            FC=           flow control (Y/N)

        For 2400 or slower modems, you'll pretty much just have "MS=2400
        CS=2400 CON" (or whatever the baud rate is).  The other flags
        are used for high-speed modems.

        So, how do you modify this information?  You pretty much take it
        as-is, and modify it.  Say your modem had a result code
        indicating connection at 600 baud.  You'd then just add a line
        saying:

        RESL: "CONNECT 600"     "600"      MS=600   CS=600   CON

        And that would be it.  If you needed additional initialization
        strings sent to the modem, then you'd just add that into either
        the setup or init strings (depending on if you needed it sent
        only once, or for each caller).  Beware, though: Most modems
        only have a 40 character buffer, so if you make the strings too
        long, it might not work.

        Thus, modifying a 2400 or lower modem configuration should be
        fairly simple (if you know what you need it to do).  9600's,
        however, are much more complicated.

        If/when you need to modify a modem configuration, you should
        first take the configuration you are starting with, and copy
        it out of MODEMS.MDM into a separate file.  If, say, you need
        to tweak the H2400 configuration for your Prometheus modem,
        you'd copy the H2400 configuration (minus the FILE: "H2400")
        into a file, say, "PROMETH.MDM" in your data directory.  Then
        you'd modify the NAME: and NOTE: lines for the new modem type.
        Then, when you're done, you can easily distribute the new
        configuration (as the file PROMETH.MDM) to other people who
        might need it (and also send a copy back to WSS, so we can
        include it in future versions of the MODEMS.MDM file).

    6.3 Explanation of sample hi-speed modem in MODEMS.MDM. The
    configuration for the older USRobotics high-speed modems is:

    ########################################################
    #
    # USR HST/V.32bis/DS modems
    #
    # This really returns the optimal information.
    # Editor's note:  The SETU line in the actual MODEMS.MDM
    # a single line; it has been broken into SETU1 and SETU2
    # in this doc due to margin considerations.

    FILE: "USRC31"
    NAME: "USR Courier (With rectangular LEDs/V.32bis)"
    CONF: "ATZ{~~~~~~~AT{~~AT&&W{"
    SETU1: "ATC1E0F1H0M0Q0V1X6&&A3&&B2&&C1&&D2{~~AT&&H1&&I0&&K>
    SETU2: "&&N0&&R2&&S0S0=0S2=1{" See Editor's comment above.
    INIT: "ATB0H0M0{"
    ANSR: "ATA{"
    PICK: "ATH1{"
    HANG: "ATH0{"
    DIAL: "ATB1DT"
    SEPR: "/"
    DEFL: MS=38400 CS=38400 EC=N DC=N AS=N FC=Y
    RESL: "OK"              "Normal"        NORM
    RESL: "RING"            "Ring"          RING
    RESL: "NO CARRIER"      "No Carrier"    DIS
    RESL: "ERROR"           "Error"         ERR
    RESL: "NO DIAL TONE"    "No Dial Tone"  NDT
    RESL: "BUSY"            "Busy"          DIS
    RESL: "NO ANSWER"       "No Answer"     DIS
    RESL: "RINGING"         "Ringing"       RINGING
    RESL: "VOICE"           "Voice"         DIS
    RESL: "CONNECT"         "300"           MS=300   CS=300   CON
    RESL: "CONNECT 1200"    "1200"          MS=1200  CS=1200  CON
    RESL: "CONNECT 2400"    "2400"          MS=2400  CS=2400  CON
    RESL: "CONNECT 4800"    "4800"          MS=4800  CS=4800  CON
    RESL: "CONNECT 7200"    "7200"          MS=7200  CS=7200  CON
    RESL: "CONNECT 9600"    "9600"          MS=9600  CS=9600  CON
    RESL: "CONNECT 12000"   "12000"         MS=12000 CS=12000 CON
    RESL: "CONNECT 14400"   "14400"         MS=14400 CS=14400 CON
    RESL: "ARQ"                             EC=Y     CS=38400
    RESL: "HST"             '/HST'          AS=Y
    RESL: "V32"             '/V.32'         AS=N
    RESL: "MNP"             '/MNP'          EC=Y
    RESL: "LAPM"            '/LAPM'         EC=Y
    RESL: "MNP5"            '/MNP5'         DC=Y
    RESL: "V42BIS"          '/V.42bis'      DC=Y
    RESL: "NONE"                            EC=N
    RESL: "SYNC"

    As you can see, much of it is the same.  One of the differences
    is that the setup string is divided into two portions, to get
    around the 40 character buffer in the modem.  Another major
    difference is the "CONF:" line.  This configuration line is sent
    out from the INIT program, when the specific modem configuration
    is selected.  It is sent out at the maximum baud rate the modem
    runs at.  For the USRobotics here, it sets the baud rate in the
    NVRAM to 38400 baud.  This is important, as this stored baud rate
    is used by the modem when an error-correcting connection is made.
    Modems such as the Compucom (which does not have any NVRAM) will
    not need a CONF: line.

    A subtle, but important, change is that the SEPR: is now set to "/".
    The USRobotics result codes are sent out in strings such as
    "CONNECT 9600/ARQ/V32/LAPM/V42BIS".  The SEPR: "/" tells the BBS to
    split up that big result code into several "partial result codes",
    at the separator character.  Thus, the above result code will be
    split into "CONNECT 9600", "ARQ", "V32", "LAPM, "V42BIS", which is
    much easier for the BBS to handle.  Each one of the partial result
    codes is then processed independently, in order.  All of the partial
    result codes are processed before any connected/disconnected
    decision is made by the BBS.

    Now, the "DEFL:" line here says that, by default, the state of the
    modem is (in order) running at 38400 bps, non error correcting, no
    data compression, not asymmetrical, and flow control IS needed.
    When a result code is received, all the modem settings are assumed
    to be at the DEFL state.  The result configuration info for each
    partial result code modifies each field independently, starting from
    the DEFL state.

    Each of the "CONNECT" partial result codes simply sets both the
    modem speed (MS=) and the com port speed (CS=) to the baud rate
    specified, same as for 2400 baud modems.

    Suppose we got the result code

        "CONNECT 14400/ARQ/HST/HST/V42BIS".

    We start out at the default:

     Partial result code        modem settings after processing

    At beginning, DEFL    MS=38400 CS=38400 EC=N DC=N AS=N FC=Y
    "CONNECT 14400"       MS=14400 CS=14400 EC=N DC=N AS=N FC=Y
    "ARQ"                 MS=14400 CS=38400 EC=Y DC=N AS=N FC=Y
    "HST"                 MS=14400 CS=38400 EC=Y DC=N AS=Y FC=Y
    "HST"                 MS=14400 CS=38400 EC=Y DC=N AS=Y FC=Y
    "V42BIS"              MS=14400 CS=38400 EC=Y DC=Y AS=Y FC=Y

    Which means:

        MS=14400        The user's throughput is 14400 bps
        CS=38400        The BBS should talk to the modem at 38400
                        bps. (Due to the &&B2 setting)
        EC=Y            Error correction is active (LAPM/MNP2-4)
        DC=Y            Data compression is active (V.42bis/MNP5)
        AS=Y            Asymmetrical baud rates.  This is because,
                        with the HST connection, it is only 14400
                        bps in one direction.  The other direction
                        is only 450 bps.
        FC=Y            Flow control is still active.

    The "CON" at the end of each of the "CONNECT" lines means that the
    user is connected.  Even though the "CON" is processed in the
    first partial result code, the remaining partial result codes are
    still processed.  Note that, for the HST, V32, etc, partial result
    codes, the description of the partial result code is in single
    quotes (vs double-quotes for the CONNECT descriptions).  If the
    description is in double-quotes, then any previous descriptions is
    OVERWRITTEN.  If the description is in single-quotes, then the
    description is APPENDED to any previous partial description.  For
    the result code above, the description would end up being

    "14400/HST/HST/V.42bis" For the ARQ partial result code, there is no
    description, and so the description (so far) is unmodified by the
    "ARQ".

    How do you make your own modem configuration file?  A lot of it
    will probably be the same as other configurations (ANSR, PICK, HANG,
    DIAL, the first few RESL), however you will certainly have to
    completely re-write the SETU and INIT strings.  You will also almost
    certainly have to modify the DEFL line, and the RESL lines for the
    connecting result codes.

    There are also length limits on the strings:

    FILE: 8 chars
    NAME: 80 chars
    NOTE: 4096 chars TOTAL (for however many NOTE: lines you have)
    CONF: 160 chars
    SETU: 160 chars
    INIT: 160 chars
    ANSR: 80 chars
    PICK: 80 chars
    HANG: 80 chars
    DIAL: 80 chars
    SEPR: 9 chars
    Result code from modem: 40 chars
    Result code description: 30 chars

    Also: the sepr: string may contain multiple chars.  It is not really
    a "string" as a "list of chars".  If you know C, this string is
    passed to strtok().

    Auto-selection. WWIV maintains a database for automatic modem type
    detection in the MODEMS.MDM file.  The data comprise a sort of
    "state machine".  When trying to detect a certain type of high-speed
    modem, it starts out in state 1.  If/when it gets to state 0, then
    it has detected the modem type.  If it passes through the entire
    list without passing any of the rules, then it determines that it
    cannot determine the modem type.

    The first column is the "start" state.  The second is the "end"
    state. If the current state is equal to the "start" state, then
    the string in the fourth column is sent to the modem.  If the
    response is equal to the string in the fifth column, then the
    state transition is made, and the current state is set to the "end"
    state, and the currently detected modem type is set to the string
    in the third column.

    Note that the auto-selection data is used ONLY if the modem responds
    at 9600 baud or higher.  Also note that it is not important for you
    to put in auto-selection data to detect your modem type.  The auto-
    selection stuff is only a nicety, and you can always go into init
    section 5 and pick whichever modem data you want.

=======================================================================
7  For New Sysops
=======================================================================

    Operating a BBS can be a very satisfying (and addictive)
    experience, particularly if you have given some thought to your
    setup and the needs and desires of your target audience.  A BBS
    with an attentive and participating sysop offers a personal, "homey"
    atmosphere that the Internet cannot provide.  With the "Internet
    Explosion" still in full swing, you must target a specific group
    of users and advertise to capture a sizeable user base.

    Because a BBS can be used for such a wide variety of things,
    this chapter assumes that you know virtually nothing about a
    BBS and that you are a first-time WWIV operator. The information
    that follows is meant to help guide your thoughts and creative
    processes so that you will obtain the most enjoyment from
    the experience.

    You can determine whether your BBS is to be a general purpose BBS
    or whether it will cater to some particular interest.  A general
    purpose BBS normally will not focus on any particular topic in
    its message bases or file sections; instead, it will have something
    for everyone and will probably not try to have everything available
    on any topic or subject area.  A general purpose BBS is often the
    best approach for a beginner to take unless you have some clearly
    defined area(s) of interest that you want to pursue.  If you are
    not participating on a network, then you may wish to have message
    bases that reflect a broad spectrum of interests.  If you are on
    a network, you may wish to subscribe to subs that reflect such
    broad areas.  Your download sections may also reflect a broad area
    of interest.  It is recommended, at a minimum, that you provide
    file areas that support the needs of a general user.   That is,
    you may want to make the common archive programs, protocols, and
    terminal programs readily available to your users to make it
    easier on them to call the BBS.  You may wish to provide the
    User Documentation for download so that your users can learn how to
    use a WWIV BBS system.  Beyond those minimums, you are left to your
    own imagination and perhaps the suggestions of your users to create
    the topical download areas that will appeal to those who call your
    board.

    A special purpose BBS is generally best when it reflects your own
    interests.  If it reflects your interests, you are more likely to
    take an active interest in your BBS, to post things, and to keep
    fresh material in your download areas.  Generally, a BBS that
    reflects that the operator takes an active interest in the BBS is
    more successful than one where the operator's presence is invisible
    or totally lacking.

    Once you have determined the type of BBS that you are going to run,
    you should give some thought to the types of security levels that
    you will have on your board and the amounts of time that you will
    allow each user and/or security level.  By looking in INIT, you can
    determine the predefined or default levels for certain security
    levels.  My advice would be to (a) use no more security levels than
    you absolutely need and (b) to try to keep things as simple as
    possible.  To give you some idea of this, here is a basic overview
    of the setup at The Mountain Empire which is primarily a support
    BBS for WWIV operators.

    There are seven security levels and three access levels in use:

        Type User          SL     DSL    AR's    DAR's
                     
       Unvalidated         10       0
       Normal              20      20
       Other Sysop         30      30
       Registered Sysop    40      40   A         A
          w/ Mods Access   60      60   A M       A M
          w/ SDS Access    80      80   AKM       AKM
       Sysop              255     255   All       All

    There are two SL255 Sysops and no Co-Sysops, local or remote.
    The Advanced ASV and Guest Account features are activated so
    that users and visiting sysops who call for support will have
    immediate access to the support areas of the BBS. (sans Mods
    and SDS)

    The AR and DAR of A indicate that the user has access to the
    WWIV support message bases and file sections but does not have
    access to the modifications and/or the WWIV source code.  A
    registered visiting sysop (i.e. one that is a bonafide registered
    WWIV sysop) has access to the message bases dealing with
    modifications of the source code (indicated by AR and DAR of M)
    and the transfer areas that contain such modifications.  This status
    must be requested.  Finally, I have the sysops who are registered
    and have requested to use my board as their SDS site (source
    distribution site).  Those people must send email to WSS and provide
    the information necessary to be approved for source access.

    As you can see, the number of SLS, DSLS, ARS, and DARS used here
    is very limited, yet it suits the security purposes of my BBS.
    After you have examined your needs and thought out your own security
    arrangements, then you should use the BOARDEDIT and DIREDIT features
    to set up your board to reflect the security levels and access
    restrictions that you will need.  You may wish to also have other
    indicators (i.e. age or sex) for certain areas.  The BBS software
    supports your using all of these factors to allow or deny support
    from various sections of your board.  You should be aware that any
    user who does not have the appropriate SL and accompanying access
    restrictions will not be aware of the other parts of your BBS.  For
    example, lets say that you have a total of 10 message bases.  The
    first three have SL of 30 and no ARS; the next three have SL of 40
    and AR of A.  The last four have SL of 50 and AR of B.  A user with
    SL of 30 would see only the first 3.  A user with SL of 40 and AR
    of A would see the first 6 message bases.  In other words, if you
    have the appropriate access restrictions (ARS), you can see those
    message bases that have lower SLs than your own.   A user with SL
    of 50 are AR of B would see the first 3 message bases and the last
    4.  If that user had ARs of both A and B, then he could see all of
    your message bases.

    After you have developed your security levels and access
    restrictions, you should probably make yourself some form letters
    to send to people explaining any particular rules of your BBS and/or
    any rules associated with their particular access level.  These form
    letters are explained in  Appendix ??? of the documentation.

    You may then wish to have a few friends call so that you can learn
    the process of validating them while they are on line using the F1
    Key.  Encourage them to try out various parts of the BBS and to post
    some messages.

=======================================================================
8  WWIV on the Internet.  Telnet and PPP
=======================================================================

    With the release of v4.30, WWIV has the ability to utilize the
features of the Internet within the BBS.  Using the PPP Project by Frank
Reid, the sysop can send and receive Internet Email, import newsgroups,
and send network packets via the Internet.  With the inclusion of
internal fossil support, WWIV can now be set up for access via telnet on
both dialup and full time connections.  For detailed information and
support with the PPP Project you should subscribe to the appropriate
message bases on WWIV based networks or go to alt.bbs.wwiv and post
your support questions.

This section of the documentation will be expanded as time goes on but
there is so much information available on these two topics that it is
impossible to include here.  Here is a very brief quickstart for telnet
setup that should get you started:


    Step 1:  Go to www.tactical.com and download COM/IP.

    Step 2:  Setup COM/IP on your computer.
             When prompted to select COM ports, select any virtual
                 ports you wish to use as telnet ports.
             Select the "Enable DOS/INT14" box then OK
             When asked if you want to reboot, select NO.
             When asked to configure Virtual Modems, select NO
             When the COM/IP window comes up, select the port and then
                click Configure->DOS/INT14 Settings.
             Set Baud Rate to 57600 and check the Lock Port box
             Close COM/IP and Restart your computer

    Step 3:  Run INIT.EXE ,2 and configure Instance 2 to use the virtual
             port you just created.

    Step 4:  Manually select the COMIP modem configuration for this
             instance.

    Step 5:  Create a batch file to run the telnet instance.

        @ECHO OFF
        SET WWIV_INSTANCE=2
        c:
        cd \wwiv

        :LOAD
        bbs.exe -i2 -o -n0 -a2
        if errorlevel 2 goto END
        goto LOAD

        :END

    Step 6:  Create a shortcut to run the batch file

    Step 7:  Run the telnet instance and have a friend telnet in to
             test your setup.


    Extensive help is available for the asking on alt.bbs.wwiv and several
message bases dedicated to telnet setup.


=======================================================================

Appendix A (Forms) Registration Form


                      WWIV Software Services, LLC
                           120 Judson Drive
                         Gray, TN  37615-2512

                    Product Registration/Order Form

           SEE Section 1 regarding End-User License Agreement
                SEE Section 2.1 regarding Payment Plan.

Ŀ
Full Name                                                  
Ĵ
Address Line 1                                             
Ĵ
Address Line 2                                             
Ĵ
City, State, Zip                                           
Ĵ
Voice Phone                                                
Ĵ
BBS Name                                                   
Ĵ
BBS Phone                                                  
Ĵ
Internet Email                                             


If you are on a network or network(s) fill in the following:

Ŀ
 Network Name  Node Number  Network Name  Node Number 
Ĵ
                                                      
Ĵ
                                                      



================================================================
Complete this section ONLY if you wish to DOWNLOAD the source
code from an authorized Source Distribution System (SDS).

SDS Node Number: _______    Network: __________________

SDS BBS Name: ________________________________________

User Name/Handle on SDS Site: ________________________

User Number on SDS Site: _______
================================================================

NOTE:  You must read the End-User License Agreement prior to ordering.
Your completed registration form and fees indicate that you have read
the agreement and agree to its terms and conditions.

Ŀ
Qty             Description                  Cost   Extended 
Ĵ
     WWIV v4.xx for DOS Registration                         
     (2 Instances)                          $80.00           
Ĵ
     WWIV v4.xx for DOS Installment Plan                     
     Circle Payment #:   1   2   3   4      $25.00           
Ĵ
     Network Registration                   $25.00           
     (Included w/ BBS Reg. All platforms)                    
Ĵ
     WWIVedit Registration                  $20.00           
Ĵ
     WWIVchat Registration (Avail: MAY 00)  Future           
Ĵ
     Source Code Diskette (1.44 MB Only)     $5.00           
Ĵ
     Source Code/Mod Collection Zip-Disk    Future   N / A   
Ĵ
     CD-ROM SuperDisk  (Avail: MAY 00)      Future   N / A   
Ĵ
     Automatic delivery of next release                      
     via US Mail                            $10.00           
Ĵ
     Shipping outside North America         $10.00           
Ĵ
                                                               
                                           Subtotal:           
Ĵ
                                                               
                    TN residents add 8.5% Sales Tax:           
Ĵ
                                                               
                              Total Amount Enclosed:           



* Remit to WWIV Software Services, LLC at the address above.
* Checks and Money orders drawn on US Banks ONLY.
* Dishonored checks carry a $30 surcharge per draft.
  Checks will only be deposited once unless WSS receives written
  instructions otherwise.  Dishonored checks and surcharges may
  only be paid by money order or cashier's check.

Customer Statement:

My signature below attests that I have read, understand, agree to,
and will abide by the terms and conditions of the End-User License
Agreement(s) for the products ordered above.  I understand that
failure on my part to abide by the terms and conditions set forth
therein may result in civil or criminal liability, revocation of my
license, forfeiture of any registration fees paid, or any
combination thereof.



______________________________                  __________

       Signature                                    Date



Appendix A (Forms) Registration Upgrade Form


                      WWIV Software Services, LLC
                           120 Judson Drive
                         Gray, TN  37615-2512

                 Registration / Instance Upgrade Form

This form is for those who wish to have more than two instances, WHICH
UTILIZE THE SAME USER.LST. Sysops desiring to access different user
list files must purchase an additional full registration for each user
list used.

Ŀ
Full Name:                                                          
Ĵ
Address Line 1:                                                     
Ĵ
Address Line 2:                                                     
Ĵ
City, State, Zip:                                                   
Ĵ
Registration ##:                                                    
Ĵ
Reg. Passcode:                                                      


Registration address if different from above:

          Line 1: ________________________________________

          Line 2: ________________________________________

 City, State Zip: _________________________________________


Circle desired upgrade:

    Ŀ
    Upgrade From   <=2     4    8    16    32  
    Ĵ
    Upgrade to 4   $20                         
    Ĵ
    Upgrade to 8   $45   $25                   
    Ĵ
    Upgrade to 16  $80   $60   $35             
    Ĵ
    Upgrade to 32  $120  $100  $75   $45       
    Ĵ
    Unlimited      $220  $200  $175 $145  $100 
    

                  Amount from Above: ____________

    TN Residents add 8.5% Sales Tax: ____________

                     Total Enclosed: ____________


* Remit to WWIV Software Services, LLC at the address above.
* Checks and Money orders drawn on US Banks ONLY.
* Dishonored checks carry a $30 surcharge per draft.
  Checks will only be deposited once unless WSS receives written
  instructions otherwise.  Dishonored checks and surcharges may
  only be paid by money order.

Customer Statement:

My signature below attests that I have read, understand, agree to,
and will abide by the terms and conditions of the End-User License
Agreement(s) for the products ordered above.  I understand that
failure on my part to abide by the terms and conditions set forth
therein may result in civil or criminal liability, revocation of my
license, forfeiture of any registration fees paid, or any
combination thereof.


 _______________________                       ___________
    Signature                                      Date


Appendix A (Forms) Registration Transfer Forms (Present Owner)



                      WWIV Software Services, LLC
                           120 Judson Drive
                         Gray, TN  37615-2512

                    Present Owner Transfer Request:


I, ____________________________________, a registered
   (Printed full name of present owner)

user of WWIV under registration number ______________,
                                       (Registration number)

hereby request to transfer my registration and all

registration privileges to __________________________.
                           (Printed full name of transferee)

I agree to immediately destroy all copies of WWIV source code in my
possession and to immediately cease using WWIV software.  I realize
that any SDS access that I may have had in the past will be terminated
immediately.  I further understand that this transfer will not be
effective until the signed statements from the new owner and myself and
with a check or money order for $25.00 (US Funds) are received and
processed by WWIV Software Services.


_______________________________       _______________
Signature                                   Date

Current Mailing Address:

_____________________________________________________

_____________________________________________________

_____________________________________________________


Address at time of registration (if different):

_____________________________________________________

_____________________________________________________

_____________________________________________________



Appendix A (Forms) Registration Transfer Forms (New Owner)


                      WWIV Software Services, LLC
                           120 Judson Drive
                         Gray, TN  37615-2512

                      New Owner Transfer Request:

I, ________________________________, hereby request to
       (Print your full name)

have the WWIV BBS software currently registered to

_______________________________ under registration number
(Printed name of current owner)

_____________________ transferred to my name.
(Registration number)

I have read understand and will comply with the terms and conditions of
the license agreement contained in the shareware distribution archive.
I have enclosed my completed registration form in addition to this
letter.  I understand that this transfer will not be effective until
the signed statements from both myself and the present owner, my
completed registration form  and a check or money order for $25.00
(US Funds) are received and processed by WWIV Software Services.

My current mailing address is:

_____________________________________

_____________________________________

_____________________________________


_____________________________        _________________
          Signature                         Date


=======================================================================
Appendix B (Technical Support and Resources)
=======================================================================

WSS has established several methods of support for both registered and
non-registered users. The oldest and most used being old fashioned
email. You can email WSS on most WWIV based networks at 1@50.  Via the
Internet, there are several email addresses you'll want to keep handy:

support@wwiv.com  - For support issues, Support Boards, and  SDS issues
                    not related to sds.wwiv.com

development@wwiv.com -  For WWIV development issues

sales@wwiv.com -  For registration and general sales issues

wss@wwiv.com - For anything not covered above or general information.

sds@wwiv.com - For issues relating to sds.wwiv.com (Do not apply for
               SDS access here. Goto http://sds.wwiv.com)

wis@wwiv.com - For issues relating to wwiv.com and ftp.wwiv.com

If you need to send US Mail to WSS the address is:

WWIV Software Services, LLC
120 Judson Drive
Gray, Tennessee 37615

Email links, forms, and contact information is also on our Contact
page at http://wss.wwiv.com/Contact.htm

Message Subboards / Internet Mailing Lists
==========================================

WSS hosts several meassge bases deveoted to supporting WWIV.  All are
hosted as both WWIV based message bases and Internet Mailing Lists.


    Subtype   Host     Topic

    WSSYSOP   @50      WSS Sysop Support Forum (General)
    BETA430   @50      WWIV v4.30 Beta Testers
    WWIV4XX   @50      WWIV v4.xx Development
    WWIVDOC   @50      WWIV Documentation Project
    WWIVWIN   @50      WWIV under Windows
    WWIVOS2   @50      WWIV under OS/2
    WWIVNIX   @50      WWIV under *nix
    WWIVSEC   @50      WWIV Security Issues
    NETCON    @50      WWIV Netxx Concerns

All of these message bases are exported to Internet Mailing Lists via
the PPP Project.  You can subscribe to these lists at

  http://wss.wwiv.com/maillists.htm


Support Boards
==============
The Support Board Network (SBN) dates back to the mid 1980's.
The SBN is a network of time tested, highly skilled, knowledgeable
sysops providing regional support to the WWIV community.  It is divided
into two categories:

    Support Boards (SB): These sysops have been selected based on
    the quality as well as quantity of support they provide on a
    regular basis.  They have been full time WWIV sysops for two or
    more years and participated in WWIV-based networks for a minimum
    of one year.  They make available a vast array of WWIV and
    related software archives for download.  They are responsive and
    responsible, all of which are over 21 years old.

    Core Support Boards (CSB): These sysops have been selected by WSS
    and the active CSB sysops from the current Support Boards based
    upon need.  To be considered, the SB must have two consecutive
    years of exemplary service to the WWIV community in the SB role.

Source Distribution Sites (SDS)
===============================
Established in the early 1980's, the SDS system is a network of reliable
sysops authorized and entrusted with the responsibility of distributing
WWIV source code to registered users.  There is also an Internet SDS
located at http://sds.wwiv.com.

the most up to date listing of SB, CSB, and SDS sites is located on our
web site under the Support Link.

We are in the process of building a web site dedicated soley to
supporting WWIV sysops.  Announcements will be made on the
networks and the main web site when the site is operational.

Internet Newsgroups
===================

You can subscribe to alt.bbs.wwiv on most news servers.  This newsgroup
is monitored by WSS and a large selection of WWIV sysops.  Most any
issue you can produce can be answered by someone in this forum.

Weekly IRC Chat
===============

The WWIV Chat Channel is on any EFnet IRC server as #wwiv.  The channel
is open 24/7 and you may or may not catch someone on at any given time.
A weekly chat takes place every Sunday at 2pm EST.  WSS is usually tuned
in to the chat as well as many other WWIV sysops.


=======================================================================
Appendix C (Frequently Asked Questions) WWIV under Windows 95/98
=======================================================================

-----=============================*==================================-----

Description:     "WWIV with Win95 and Win98."  Version 1.1.

An original by:  Screaming Alarm Clock BBS, Tri-Cities ( Richland ), WA.

Copyright:       1997 - 1999 Dan Morgan / Screaming Alarm Clock BBS.

File Name:       W9XWW411.FAQ. (5 July 1999 Addendum Included)

File Date:       June 28, 1999.                Version 1.1.

Lines from top:  937.

Prior versions:  W4W95A1.TXT.   May 2, 1997.   Version 0.97.
                 W4W95A2.TXT.   Oct 15, 1998.  Version 0.98.
                 W4-W9598.TXT.  Nov 24, 1998.  Version 1.0.

-----=============================*==================================-----

Contents:  Topic.

    [ a ]  Copyright notice.

    [ b ]  Important notes about this edition.

    [ c ]  Other FAQs I have created and maintain.

    [ d ]  Introduction.

    -----

    [ A ]  Setting BBS Com Port in Control Panel / System.
    [ B ]  Setting up the Modem in Control Panel / Modem.


[ C - 1 ]  Setting up or Modifying your BBS "Shortcut".
[ C - 2 ]  What to check for Win95 A/1995, Win95 OSR 2.x, and Win98
             for the BBS Shortcut.


[ D - 1 ]  Example of my AUTOEXEC.BAT with Windows 95 with REMs.
[ D - 2 ]  Example of my AUTOEXEC.BAT with Windows 95 w/o  REMs.


[ E - 1 ]  Example of my CONFIG.SYS   with Windows 95 with REMs.
[ E - 2 ]  Example of my CONFIG.SYS   with Windows 95 w/o  REMs.


[ F - 1 ]  Example of BBS Batch file  with Windows 95 with REMs.
[ F - 2 ]  Example of BBS Batch file  with Windows 95 w/o  REMs.


[ F - 3 ]  What do the switches mean in the above BBS Batch file ?
                ( Pending for the next edition of the FAQ. )

[ F - 4 ]  Do I need those switches for the BBS Batch file to work ?
                ( Yes!  Info will be in the next edition. )

    -----

    [ G ]  Credits.                                                    

    [ H ]  Requesting this FAQ via NFT.  Where to find this FAQ on the Web.



_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


Copyright: 1997 - 1999 Dan Morgan / Screaming Alarm Clock BBS.
           Tri-Cities, WA.  All Rights Reserved - including rights
           to commercial publication / distribution.  This may not
           be bundled or sold without express, written, permission
           from the author. 
           Internet Mail: dwmorgan@pobox.com  onthefritz@pobox.com
           WWIV Username: Quixotic Quest ( OnTheFritz )
           WWIV BBS Mail: 1@1.globalnet 1@301.filenet 1@5922.taznet
                          1@14209.wwivnet 1@47102.diginet
                          1@5921.terranet/sierralink/icenet


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


********************************************
[ b ]  Important note(s) about this edition.
********************************************

* This is an interim edition for cosmetic changes for the final Beta of 
  WWIV 4.30.

* At some point I hope to also make an HTML version so readers can "point
  and click" instead of scrolling down through a long FAQ when they want 
  to reach specific items or information more quickly.

* There is some information I plan to add now that RAM is much more afford-
  able. There are more options available now to Sysops for SmartDrive for 
  increased speed --- so long as they have either: more than 16 MB of RAM
  for Win9x; or, at least 16 MB of RAM when using any of DOS, Windows 3.1x,
  or Windows for Workgroups 3.11.

  However, readers are not missing out regarding the pending information for
  Smartdrive options when you have more RAM --- coming in a later edition.
  The results from this version will do fine.  I have applied it myself with
  16, 32, 48, and 64 MB of RAM.  I plan to update this FAQ as soon as I have
  time, tho, for those who would like to tweak a more few things ( if they 
  have the above RAM requirements ).


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


**********************************************
[ c ]  Other FAQs I have created and maintain.
**********************************************

W31WW4nn.FAQ       "WWIV with Windows 3.1x and Windows for Workgroups 3.11."
                   --- where "nn" is the version number for the FAQ.


W9xWW4nn.FAQ       "WWIV with Win95 and Win98."
                   ---  where "nn" is the version number for the FAQ.
                   * For all versions of Windows 95 --- from "A" ( 1995 ),
                     through Windows 95 OSR2 ("B") and OSR2.5 ("C") ---
                     and through Windows 98 1st Edition.
                   * Information for Windows 98 2nd Edition will come as
                     soon as I have upgraded to check it out for any needed
                     changes for the FAQ.


PPP-PROJ.FAQ       "Installing and configuring the PPP Project for WWIV."
                   ( Updated version coming soon. )
                   * For info about using the PPP Project with a cable
                     modem, or ADSL, or other Ethernet setups, please 
                     join the "PPP Project Support/Development" sub on
                     many WWIV networks, or email me for the address
                     for the Internet Mailing List version.
                     You can get help there for all topics --- from
                     those the FAQs cover, to new information
                     and options that the FAQs are catching up to.
                   * For information and help on telnet and WWIV,
                     in other words making your BBS telnetable,
                     please subscribe to the WWIV/Telnet sub
                     that is on several WWIV networks.
               

WWIVHOST.LST       Supplement to MAILLIST.FAQ by "Eileen Stone".
                   For the 'PPP Project for WWIV' for hosting an
                   Internet Mailing List with your WWIV BBS.
                   * How to tell subscribers to subscribe/unsubscribe
                     via a web page, and how to post to the List once
                     they have joined.
                   * New information is coming for when your List is
                     hosted by a Server that redirects to your BBS,
                     and you want to tell your subscribers how to post 
                     to your List when you use that alternate setup.  


Other FAQs to note:  FAQs by "Eileen Stone".

                   You can find the following FAQs by "Eileen Stone"
                   for the 'PPP Project for WWIV' at the PPP Project
                   for WWIV main and mirror web sites:

                   (1) NWSGROUP.FAQ --- How to import 
                       newsgroups into your WWIV BBS.

                   (2) MAILLIST.FAQ --- How to host a Mailing List with
                       your WWIV BBS, and how to import a Mailing List
                       to a WWIV sub ( message base ).


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


*******************
[ d ] Introduction.
*******************
    
          There are various Help Files out there for setting up a BBS
            [ this one is specifically for WWIV (c) WSS/Dean Nash ]
          to run better under Windows 95 and 98 [ (c) Microsoft, Inc ].


          In my experience, suggestions in other Help Files to remove
          AUTOEXEC.BAT and CONFIG.SYS, or to remove EMM386.EXE from 
          CONFIG.SYS, created problems for some systems with Win9x.


          I've installed Win95 about a dozen times and created a plethora
          of headaches ( and gained more grey hair ) before I found a
          working combination of solutions.


          This Help File attempts to fill in the gap with examples of:
            * Batch file for WWIV ( B.BAT ).
            * AUTOEXEC.BAT.
            * CONFIG.SYS.
            * How to set the Com Port and the Modem in Control Panel.
            * "Shortcut" settings that shows how I have instructed 
              Windows 95 ( all versions ) to run WWIV.


          I have 611k free in a DOS "window" ( full-screen) --- when
          not using any hard drive compression --- with the set-up I
          describe in this FAQ.  WWIV has not had any hiccups from a
          lack of free memory yet under Win95 with the AUTOEXEC.BAT,
          CONFIG.SYS, B.BAT, and the Shortcut I use for the Screaming
          Alarm Clock BBS.


          One critical factor to mention before I get started:
          the last line of your BBS Batch file should read as
            EXIT
             or
            exit

          This can help avoid the: "Hit CTRL-C to exit your program"
          if the BBS has an error, and also when the BBS exits normally
          ( but only if you also refer to the "Shortcut" settings in
          this FAQ for the examples needed to do this ).


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


******************************************************
[ A ]  Setting BBS Com Port in Control Panel / System.
******************************************************

Follow these steps to set up your Com Port for the BBS...

Start
Settings
Control Panel

Select: System
Select: Device Manager
Select: Ports ( COM & LPT )
Select: The Com Port used by your BBS Modem


Settings:

            Bits per second:  115200 ( for internal 28.8 and 33.6 modems )

            Bits per second:  57600  ( for external 28.8 and 33.6 modems
                                       --- but you can try using 115200 )

            Bits per second:  57600  ( for 56k modems --- I get better
                                       results for WWIV, and for other
                                       software for the Internet, when
                                       I use 57600 for my 56k modem )

            Data bits:        8
            Parity:           None
            Stop Bits:        1
            Flow Control:     Hardware


Select: Advanced

Settings:

            [ x ]  Use FIFO buffers ( requires 16550 compatible UART ).

            Receive  Buffer   Low (1) x-----|-----x-----x High (14)
            Transmit Buffer   Low (1) x-----|-----x-----x High (14)

            Set each to 4 as shown with the | in the example above.


Now click on [ OK ] until you return back to the Control Panel.

Stay in Control Panel for Section B ( next section ) of this Help File.


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


*****************************************************
[ B ]  Setting up the Modem in Control Panel / Modem.
*****************************************************

In Control Panel...

Select: Modems
Select: Properties
Select: General ( Tab at the top of the dialog box )


Settings:

            Set Port to the Com Port used by your BBS Modem.
            Set Speaker Volume as desired.

            Set Maximum Speed to the same setting you used for
              the Com Port in section A.
                              115200 ( for internal 28.8 and 33.6 modems )
                              57600  ( for external 28.8 and 33.6 modems
                                       --- but you can try using 115200 )
                              57600  ( for 56k modems --- I get better
                                       results for WWIV, and for other
                                       software for the Internet, when
                                       I use 57600 for my 56k modem )
 
 
Select: Connections ( Tab at top of the dialog box )

Settings:

            Data bits:        8
            Parity:           None
            Stop bits:        1

            [ x ]  Use error control
            [ x ]  Compress data
            [ x ]  Use flow control
            [ x ]  Hardware compression

            Modulation type:  Standard


Now click on [ OK ] until you return back to the Control Panel.

Now restart Windows via the Start Button.
Exit out of all programs that are currently running.

Select: Start
Select: Shut Down
Select: Restart the Computer


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


*****************************************************
[ C-1 ]  Setting up or Modifying your BBS "Shortcut".
*****************************************************

This section has help for those who upgraded from Windows 3.1x or
Windows for Workgroups, and those who started with Windows 9x and
don't have any prior "PIFs" that were converted to "Shortcuts".


To create or modify your BBS Shortcut - follow these steps...

Start
Settings
Taskbar
Start Menu Programs
Advanced

At this point you can either find your existing BBS Shortcut or create
one.  The next paragraphs details how to create one.  Skip this indented
section if you already have a BBS Shortcut and go to the "modify" text.


      To create a BBS Shortcut:

      Select: Find the Folder you want to place the Shortcut into from
                  the List on the left side of the Explorer dialog box.

      Action: Left Mouse Click on the desired Folder to highlight it.

      Select: File from the Menu Bar
      Select: New
      Select: Shortcut

      Enter text for "Command Line"  such as:  C:\WWIV\BBS.EXE
      Enter text for "Select a Name" such as:  BBS Instance 1

      Select an Icon
      Click on Finish



Now modify the BBS Shortcut...

Select: BBS Shortcut with a Left Mouse Click to highlight it.
Action: Right Mouse Click on the BBS Shortcut to bring up a dialog box.
Select: Properties



Settings:

Select: Program

      ( Icon ):         ( Name ) BBS Instance 1
      Cmd Line:         C:\WWIV\BBS.EXE          ( if BBS is run directly )
      Cmd Line:         C:\COMMAND.COM   ( if BBS is run via a Batch file )
      Working:          C:\WWIV  ( Set this and Cmd Line to Drive you use )
      Batch File:       B.BAT ( Name of Batch file you use to run the BBS )
      Shortcut Key:     CTRL + Alt + Whatever Key You Specify
      Run:              Normal Window
      [ x ]             Close on Exit



Select: Font

      [ x ]             Both Font Types
      Font Size:        Auto



Select: Memory

      Set all to:       Auto
                                    * Except for Initial Environment ---
                                      set that to 2048 so your BBS can run
                                      Games and Utilities.
                                    * If you run more than two instances
                                      of WWIV, and you get "out of memory"
                                      errors for programs that are not
                                      part of WWIV/utils/games --- then
                                      try 1024 for the BBS Shortcut and
                                      see what happens for that software.
                                    * I have to set this to 2048 for my
                                      PC or I get occasional hiccups with
                                      external BBS utilities and games.
                                      

      [   ]             Protected
                                    * Do -not- set to Protected -unless-
                                      you run the original Win95 from 1995!
                                    * For Win95 "B" ( OSR 2.x ), Win95 "C"
                                      ( OSR 2.5 ), and Win98 1st Edition do
                                      -not- set to Protected in your BBS
                                      Shortcut!
                                    * Info on Win98 2nd Edition is still
                                      pending for a later FAQ edition.

      [ x ]             Uses HMA



Select: Screen

      [ x ]             Full Screen
      [ x ]             Display Toolbar
      [ x ]             Restore Settings on Startup
      [ x ]             Fast ROM Emulation
      [ x ]             Dynamic memory allocation
      Initial Size:     Default



Select Misc:

      [ x ]             Allow Screen Saver ( I use Blank Screen - set in
                                               Control Panel / Display )
      [ x ]             Fast Pasting
      [ x ]             All of the Windows Shortcut Keys
      Idle Sensitivity: Low ( farthest to the left )



Now Click on [ APPLY ].
Now Click on [ OK ] and exit back out to the main screen of Windows 95.


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


*******************************************************************
[ C - 2 ]  What to check for Win95 A/1995, Win95 OSR 2.x, and Win98
             1st Edition for the BBS Shortcut.
*******************************************************************


The only difference for Win95 and Win98 is in the above section where
it tells you when to set Memory to Protected, or not, in the Shortcut.

You should set it to Protected  -only-  when you run the  -original-
release of Windows 95 ( also referred to as Windows 95 "A" ) from 1995.


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


*******************************************************************
[ D - 1 ]  Example of my AUTOEXEC.BAT with Windows 95 with REMarks.
*******************************************************************

@ECHO OFF

PROMPT $d $t$_$p :                  REM  Gives a very nice command prompt.

VERIFY ON                           REM  Tells DOS to verify disk writes.

PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS;C:\WWIV\;C:\COMM;C:\ARCHIVE;
C:\SHELL;C:\SYS;C:\EDIT;C:\TEMP;C:\SYS\VIDEO;C:\ZIPTOOLS;


REM -=-=-=-= Separator Line to split sections. -==-
:SET
REM -=-=-=-= Separator Line to split sections. -==-

SET TEMP=C:\TEMP


REM -=-=-=-= Separator Line to split sections. -==-
:SOUND       REM (Some sound cards still need AUTOEXEC.BAT and CONFIG.SYS)
REM -=-=-=-= Separator Line to split sections. -==-

SET GALAXY=A220 I5 D1 K10 P530 T6
SET BLASTER=A220 I5 D1 T4
SET SOUND=C:\MMP16F


REM -=-=-=-= Separator Line to split sections. -==-
:DRIVERS
REM -=-=-=-= Separator Line to split sections. -==-

C:\SYS\16550 COM2 /f /t4   REM  Sets Com Port2 FIFO to 4 via 16550 util.
C:\SYS\16550 COM3 /f /t4   REM  Sets Com Port3 FIFO to 4 via 16550 util.

:END


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


**********************************************************************
[ D - 2 ]  Example of my AUTOEXEC.BAT with Windows 95 without REMarks.
**********************************************************************

@ECHO OFF
PROMPT $d $t$_$p :
VERIFY ON

PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS;C:\WWIV\;C:\COMM;C:\ARCHIVE;
C:\SHELL;C:\SYS;C:\EDIT;C:\TEMP;C:\SYS\VIDEO;C:\ZIPTOOLS;


REM -=-=-=-= Separator Line to split sections. -==-
:SET
REM -=-=-=-= Separator Line to split sections. -==-

SET TEMP=C:\TEMP


REM -=-=-=-= Separator Line to split sections. -==-
:SOUND
REM -=-=-=-= Separator Line to split sections. -==-

SET GALAXY=A220 I5 D1 K10 P530 T6
SET BLASTER=A220 I5 D1 T4
SET SOUND=C:\MMP16F


REM -=-=-=-= Separator Line to split sections. -==-
:DRIVERS
REM -=-=-=-= Separator Line to split sections. -==-

C:\SYS\16550 COM2 /f /t4
C:\SYS\16550 COM3 /f /t4

:END


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


****************************************************************
[ E -1 ]  Example of my CONFIG.SYS with Windows 95 with REMarks.
****************************************************************

DEVICE=C:\WINDOWS\HIMEM.SYS /SHADOWRAM:ON /TESTMEM:OFF /V

REM    ******************************************************************
REM    Note: Shadowram is specific to my PC as our CMOS is set up for it.
REM    If yours is not, or your are unsure, then use:   /SHADOWRAM:OFF
REM    as you see in the CONFIG.SYS example below that is without REMs.
REM    ******************************************************************

DEVICE=C:\WINDOWS\EMM386.EXE ON RAM H=64 D=64 /V

REM    ****************************************************************
REM    Enables EMM386.EXE. Sets File Handles to 64. DMA to 64. Verbose.
REM    ****************************************************************

FILES=50                           REM  Some suggest FILES=60 for WWIV.
                                   REM  I set to 50 or 60 even when my
                                   REM  AUTOEXEC.BAT uses SmartDrive !

DOS=UMB

FCBS=32,0

REM   *************** SOUND CARD **************************
DEVICE=C:\MMP16F\DRIVERS\EEPROM.SYS /88BC0001
REM   *****************************************************

DOS=HIGH

BREAK=ON                              REM  Enables CTRL-Break, etc.

STACKS=64,256                         REM  Max setting for com buffer.
                                      REM  Many use:   STACKS=9,256

SHELL=C:\COMMAND.COM C:\ /E:2048 /P   REM  Environment needed for BBS etc.

DEVICE=C:\DOS\FIX16550.SYS            REM  16550 fix utility for AMI BIOS.

DEVICEHIGH=C:\DOS\TANSI.SYS           REM  ANSI Driver for our video card.

DEVICEHIGH=C:\PAGERDR\CIS800N.SYS               REM  Our Document Scanner.

DEVICEHIGH=C:\DEV\HIT-IDE.SYS /D:MSCD005 /N:1 /T:3 /V     REM  Our CD Rom.


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_

********************************************************************
[ E - 2 ]  Example of my CONFIG.SYS with Windows 95 without REMarks.
********************************************************************

REM See the full FAQ for explanation of this example ( With REMs )
REM and for alternative settings for    STACKS=   and for   FILES=
REM as  STACK=9,256  saves memory  and  WWIV may demand  FILES=60 ,
REM and for more information regarding AUTOEXEC.BAT and CONFIG.SYS.


REM DEVICE=C:\WINDOWS\HIMEM.SYS /SHADOWRAM:ON /TESTMEM:OFF /V
DEVICE=C:\WINDOWS\HIMEM.SYS /SHADOWRAM:OFF /TESTMEM:OFF /V
DEVICE=C:\WINDOWS\EMM386.EXE ON RAM H=64 D=64 /V

BUFFERS=60,0
FILES=50
DOS=UMB
FCBS=32,0

DOS=HIGH
BREAK=ON
STACKS=64,256
SHELL=C:\COMMAND.COM C:\ /E:2048 /P

DEVICE=C:\DOS\FIX16550.SYS


REM -*-  =========================================  -*-
REM -*-  ===  IF I USE OLD TRIDENT VIDEO CARD  ===  -*-
REM -*-  =========================================  -*-

REM DEVICEHIGH=C:\DOS\TANSI.SYS


REM -*-  ================================  -*-
REM -*-  ===  MOST OTHER VIDEO CARDS  ===  -*-
REM -*-  ================================  -*-

DEVICEHIGH=C:\WINDOWS\COMMAND\ANSI.SYS

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


**********************************************************************
[ F - 1 ]  Example of BBS Batch file with Win95 with "exit" with REMs.
**********************************************************************

@ECHO OFF

REM  *************************************************************
REM  *  ORIGIN - SCREAMING ALARM CLOCK BBS, RICHLAND, WA - 1999. *
REM  *************************************************************
REM  *  BATCH FILE FOR INSTANCE 1 - CALLER INSTANCE.  B.BAT.     *
REM  *************************************************************
REM  *  SAVE ORIGINAL AND DELETE ALL REM(arks) FROM FILE YOU USE.*
REM  *************************************************************
REM  * Copyright   1994-1999 Dan Morgan/Screaming Alarm Clock  *
REM  *************************************************************
REM  * Quixotic Quest/OnTheFritz. Internet: onthefritz@pobox.com *
REM  *************************************************************


REM Remove all lines referring to KLOS PPP unless you use KLOS PPP drivers!


VERIFY ON                      REM Tells DOS to verify writes.
BREAK ON                       REM Enables CTRL-Break, etc.



REM -=-=-=-= Separator Line for Label for GOTO. -==-
:BBS
REM -=-=-=-= Separator Line for Label for GOTO. -==-

C:\SYS\16550 COM2 /f /t4       REM  Sets Com Port FIFO via 16550 util.

LSL /U                         REM  Force LSL to unload ( KLOS PPP ).
LH C:\WWIV\LSL                 REM  Loads LSL for BBS   ( KLOS PPP ).

C:                                        REM  Change to BBS drive.
CD\WWIV                                   REM  Change to BBS directory.

SET TZ=PST8PDT                            REM  Sets to Pacific Time Zone.
SET BBS_NAME=SCREAMING ALARM CLOCK        REM  For my Game Batch Files.
SET WWIV_INSTANCE=1                       REM  For my Game Batch Files.

FLINK                                     REM  Run FLINK for unmodded BBS.

REM  The BBS command line sets the BBS to exit after each call, which the
REM  Batch file uses to either quit ( Q or ESC-Y at WFC ) or to loop thru
REM  the Batch file to restart the BBS. The looping helps an unmodded BBS
REM  to run "LINKER" and "FLINK" utils on packets between calls. Here the
REM  BBS is told to start Instance 1 ( /I1 ) and is given exit parameters.
REM  Since I have a 28.8/33.6 modem I set my Com Port to 115200.

BBS.EXE /I1 /S115200 /N0 /A1 /O /C %1 %2 %3 %4 %5

IF ERRORLEVEL 4 GOTO EVENT
IF ERRORLEVEL 2 GOTO QUITBBS
IF ERRORLEVEL 1 GOTO PREP4BBS
IF ERRORLEVEL 0 GOTO PREP4BBS



REM -=-=-=-= Separator Line for Label for GOTO. -==-
:EVENT                        REM  From WWIV docs for BBS Batch files.
REM -=-=-=-= Separator Line for Label for GOTO. -==-

C:                            REM  Change to BBS drive.
CD\WWIV                       REM  Change to BBS directory.
GOTO PREP4BBS                 REM  After event - loop to run Net utils.



REM -=-=-=-= Separator Line for Label for GOTO. -==-
:PREP4BBS                     REM  Label for Utils prior to BBS restart.
REM -=-=-=-= Separator Line for Label for GOTO. -==-

C:                            REM  Change to BBS drive.
CD\WWIV                       REM  Change to BBS directory.

FLINK                         REM  Run FLINK for unmodded BBS.
NETWORK2.EXE                  REM  Run LINKER for unmodded BBS.

GOTO BBS                      REM  Loop back to restart the BBS.  Needed!



REM -=-=-=-= Separator Line for Label for GOTO. -==-
:QUITBBS
REM -=-=-=-= Separator Line for Label for GOTO. -==-

ECHO.
ECHO.
ECHO.
ECHO                          " QUITTING THE BBS "
ECHO.
ECHO.
ECHO.

C:                            REM  Change to BBS drive.
CD\WWIV                       REM  Change to BBS directory.

LSL /U                        REM  Unload LSL driver ( KLOS PPP ).

FLINK                         REM  Run FLINK for unmodded BBS.
NETWORK2.EXE                  REM  Run LINKER for unmodded BBS.

CD\                           REM  Habitual return to C:\ from DOS days.

EXIT                          REM  Critical for Win95 to avoid the
                              REM  horrible " Hit CTRL-C " prompt.

:END


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


*************************************************************************
[ F - 2 ]  Example of BBS Batch file with Win95 with "exit" without REMs.
*************************************************************************

@ECHO OFF

REM  *************************************************************
REM  *  ORIGIN - SCREAMING ALARM CLOCK BBS, RICHLAND, WA - 1999. *
REM  *************************************************************
REM  *  BATCH FILE FOR INSTANCE 1 - CALLER INSTANCE.  B.BAT.     *
REM  *************************************************************


REM Remove all lines referring to KLOS unless you use KLOS PPP drivers!


VERIFY ON
BREAK ON



:BBS

C:\SYS\16550 COM2 /f /t4

LSL /U                         REM  Force LSL to unload ( KLOS PPP ).
LH C:\WWIV\LSL                 REM  Loads LSL for BBS   ( KLOS PPP ).

C:
CD\WWIV

SET TZ=PST8PDT
SET BBS_NAME=SCREAMING ALARM CLOCK
SET WWIV_INSTANCE=1

FLINK

BBS.EXE /I1 /S115200 /N0 /A1 /O /C %1 %2 %3 %4 %5

IF ERRORLEVEL 4 GOTO EVENT
IF ERRORLEVEL 2 GOTO QUITBBS
IF ERRORLEVEL 1 GOTO PREP4BBS
IF ERRORLEVEL 0 GOTO PREP4BBS



:EVENT
C:
CD\WWIV
GOTO PREP4BBS



:PREP4BBS
C:
CD\WWIV
FLINK
NETWORK2.EXE
GOTO BBS



:QUITBBS
ECHO.
ECHO.
ECHO.
ECHO                          " QUITTING THE BBS "
ECHO.
ECHO.
ECHO.

C:
CD\WWIV

LSL /U                        REM  Unload LSL driver ( KLOS PPP ).

FLINK
NETWORK2.EXE

CD\

EXIT

:END


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


**************
[ G ]  Credits
**************

Much thanks for the inspiration to create a FAQ to: Bob Dunn, Sysop
of the Glass Onion BBS.  His Help File for DOS/FIDO BBSs and Win95
helped to get me started, and showed that original Help Files can go
a long way to help other Sysops avoid the messes of a new operating
system.  "How to Run Front Door Under Windows 95" (c) 1995 Bob Dunn.


MS-DOS, Windows, Windows for Workgroups, Windows 95,
        Windows 98 and "DOSKEY"...........(c) and TM Microsoft, Inc.

WWIV........( WWIV BBS Software ).........(c) and TM WSS / Dean Nash.

FLINK.......( for WWIV )..................(c) 1997 Dennis M. Meyers.

LINKER......( for WWIV )..................(c) "Hellfire".

16550.EXE...( UART/FIFO utility ).........(c) 1993 Brent C. Turner.

Note: All software mentioned in this FAQ is (c) and TM by their
      respective owners and holders.


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


***********************************************************************
[ H ]  Requesting this FAQ via NFT.  Where to find this FAQ on the Web.
***********************************************************************

On WWIV BBS's --- you can use the NFT software for FILEnet
( if your BBS is on FILEnet ) --- to request  W9XWW411.FAQ
from node 301 ( Screaming Alarm Clock ).



To download the current edition of this FAQ from
the World Wide Web go to this url:

The filename is: W9XWW411.FAQ.

Main web site - Direct ( if you have problems ):
http://users.owt.com/quixotic/ppp-wwiv

Main web site - Redirect ( url I post for downloads ):
http://pobox.com/~onthefritz/ppp-wwiv

Mirror Web site I maintain ( that I plan to convert to the Main site * ):
http://filenet.wwiv.net
( * Thanks to Frank Reid of Eagle's Dare BBS for the hard drive space! )

The main web site is often not available on Friday mornings from midnight
to 3 am ( Pacific time ).  If I ever change the Web site's location, then
just email or finger       onthefritz@pobox.com     for new information.



To download the 16550.zip ( fifo ) and the FIX16550.SYS ( for AMI bios ):

These are available for download from many WWIV boards, and
you can probably find a copy via NFT.  If they are not on
the 'PPP Project for WWIV' web site, then email me for a zip.

-*- end -*-


=======================================================================
Appendix C (Frequently Asked Questions) WWIV under Windows for Workgroups
=======================================================================

-----=============================*==================================-----

Description:     "WWIV with Win3.1x and WFWG 3.11."  Version 2.2.

An original by:  Screaming Alarm Clock BBS, Tri-Cities ( Richland ), WA.

Copyright:       1995 - 1999 Dan Morgan / Screaming Alarm Clock BBS.

File Name:       W31WW422.FAQ.

File Date:       June 29, 1999.        Version 2.2.

Lines from top:  1612.

Prior versions:

      Version 2.1 - Nov 24, 1998.
      Version 2.0 - Oct  28, 1998.     Version 1.9 - June 10, 1998.
      Version 1.8 - July 30, 1997.     Version 1.7 - Feb  1997.
      Version 1.3 to 1.6 - Feb. 1997.  Version 1.2 - Dec  18, 1996.
      Version 1.1 - Jan  28, 1996.     Version 1.0 - Aug  27, 1995.
      Version 0.9 - June 14, 1995.

-----=============================*==================================-----

Contents:  Topic.

  [ a ]    Copyright notice.

  [ b ]    Important notes about this edition.

  [ c ]    Other FAQs I have created and maintain.

  [ d ]    Introduction.

  -----

  [ 1 ]    Disclaimer.

  [ 2 ]    History / Origin / Why a FAQ is needed for Windows.


  [ 3-A ]  You can modify my BBS PIF template for use with other DOS apps.

  [ 3-B ]  Using 16550.EXE to reduce or get rid of comm overruns.


  [ 4-A ]  Example AUTOEXEC.BAT.

  [ 4-B ]  Example CONFIG.SYS.

  [ 4-C ]  Example BBS Batch File ( B.BAT ) with REMs.

  [ 4-D ]  Example BBS Batch File ( B.BAT ) w/o REMs.

  [ 4-E ]  What do the switches for BBS.EXE mean in the BBS Batch file?
           ( Pending --- this will be in the next edition of this FAQ. )

  [ 4-F ]  Do I need those switches for the BBS Batch file to work?
           ( Yes!  Information will be in the next edition. )


  [ 5-A ]  Win 3.1x  settings for WIN.INI.

  [ 5-B ]  WFW 3.11  settings for WIN.INI.


  [ 6 ]    Win 3.1x  settings for SYSTEM.INI.

  [ 7 ]    WFW 3.11  settings for SYSTEM.INI.

  [ 8 ]    Example PIF file for WWIV BBS.


  [ 9-A ]  Smartdrive.

  [ 9-B ]  Back Up your BBS now, before: setting up Smart Drive; changing
             Swap File size; and/or, before trying out 32-bit Disk Access.

  [ 9-C ]  Checking hard Drive for Errors and Optimizing/Defragging:
             PRECAUTIONS.

  [ 9-D ]  Permanent Swap File and size.


  [ 10 ]   Copyrights and Trademarks.

  [ 11 ]   Credits.

  [ 12 ]   Requesting this FAQ via NFT.
           Where to find this FAQ on the Web.


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


Copyright (c) 1995 - 1999 Dan Morgan / Screaming Alarm Clock BBS.
              Tri-Cities, WA.  All Rights Reserved - including rights
              to commercial publication / distribution.  This may not
              be bundled or sold without express, written, permission
              from the author. 


              Internet Mail: dwmorgan@pobox.com  onthefritz@pobox.com

              WWIV Username: Quixotic Quest ( OnTheFritz )

              WWIV BBS Mail: 1@1.globalnet     1@301.filenet
                             1@14209.wwivnet   1@47102.diginet
                             1@5921.terranet/sierralink/icenet
                             1@5922.taznet


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


*********************************************
[ b ]   Important note(s) about this edition.
*********************************************

* This is an interim edition for cosmetic changes for the final Beta of 
  WWIV 4.30.

* At some point I hope to also make an HTML version so readers can "point
  and click" instead of scrolling down through a long FAQ when they want 
  to reach specific items or information more quickly.


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


***********************************************
[ c ]   Other FAQs I have created and maintain.
***********************************************


W31WW4nn.FAQ       "WWIV with Windows 3.1x and Windows for Workgroups 3.11."
                   --- where "nn" is the version number for the FAQ.


W9xWW4nn.FAQ       "WWIV with Win95 and Win98."
                   ---  where "nn" is the version number for the FAQ.

                   * For all versions of Windows 95 --- from "A" ( 1995 ),
                     through Windows 95 OSR2 ("B") and OSR2.5 ("C") ---
                     and through Windows 98 1st Edition.

                   * Information for Windows 98 2nd Edition will come
                     as soon as I have upgraded to check it out for
                     any needed changes for the FAQ.


PPP-PROJ.FAQ       "Installing and configuring the PPP Project for WWIV."
                   ( Updated version coming soon. )

                   * For info about using the PPP Project with a cable
                     modem, or ADSL, or other Ethernet setups, please 
                     join the "PPP Project Support/Development" sub on
                     many WWIV networks, or email me for the address
                     for the Internet Mailing List version.
                     You can get help there for all topics --- from
                     those the FAQs cover, to new information
                     and options that the FAQs are catching up to.

                   * For information and help on telnet and WWIV,
                     in other words making your BBS telnetable,
                     please subscribe to the WWIV/Telnet sub
                     that is on several WWIV networks.
               

WWIVHOST.LST       Supplement to MAILLIST.FAQ by "Eileen Stone".
                   For the 'PPP Project for WWIV' for hosting an
                   Internet Mailing List with your WWIV BBS.

                   * How to tell subscribers to subscribe/unsubscribe
                     via a web page, and how to post to the List once
                     they have joined.

                   * New information is coming for when your List is
                     hosted by a Server that redirects to your BBS,
                     and you want to tell your subscribers how to post 
                     to your List when you use that alternate setup.  


-------------------------------------------------------------------------


Other FAQs to note:

                   FAQs by "Eileen Stone", of the MultiVersal Dreams BBS.

                   These are not written by me.  I am mentioning them as
                   they are crucial to helping you with the 'PPP Project
                   for WWIV'.

                   You can find the following FAQs by "Eileen Stone" for
                   the 'PPP Project for WWIV' at the PPP Project for
                   WWIV main and mirror web sites ( see section 12 ):

                   (1) NWSGROUP.FAQ
                       --- How to import newsgroups into your WWIV BBS.

                   (2) MAILLIST.FAQ
                       --- How to host Mailing Lists with your
                       WWIV BBS, and how to import a Mailing
                       List to a WWIV sub ( message base ).


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


*********************
[ d ]   Introduction.
*********************
    
          There are various Help Files out there for setting up a BBS
            [ this one is specifically for WWIV (c) WSS/Dean Nash ]
          to run under Win 3.1x and WFWG 3.11  [ (c) Microsoft, Inc ].


          This Help File attempts to fill in the gap with examples of:

            * Batch file for WWIV ( B.BAT ).
            * AUTOEXEC.BAT.
            * CONFIG.SYS.
            * Com Port and FIFO settings.
            * Setting up SmartDrive ( hard drive disk cache ).
            * Setting up, or re-sizing, a permanent swap file.
            * "PIF" settings that shows how I have instructed 
              Windows to run WWIV.


          I have 590k+ free ( up to about 600k ) before running WWIV
          in a DOS "window" ( full-screen) --- when not using any hard
          drive compression --- with the set-up I describe in this FAQ.


          I have heard from several Sysops about how this FAQ, and my
          Win95/98 FAQ for WWIV, have helped them to set up WWIV under
          Windows... and how the FAQs helped to speed up systems that
          already were running under Windows.

          That feedback spurs me to go on with refinements to my FAQs
          ( Thank you! ).

          So, please, if you find this to be of help, then send the
          entire FAQ to any Sysop that asks you for help with WWIV
          and Windows --- if they do not have a current copy or they
          cannot download a copy.


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%
[ 1 ]   DISCLAIMER:
%%%%%%%%%%%%%%%%%%%


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%[ DISCLAIMER ]%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

[[[  Use the information and examples in this file at your own risk!  ]]]

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%[ DISCLAIMER ]%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%
[ 2 ]   HISTORY:
%%%%%%%%%%%%%%%%


          This file has info about how to set the WIN.INI and SYSTEM.INI
          to optimize them for the BBS and for handling the comm ports.
          I began this file to help address comm overruns in Windows 3.1x
          and Windows for WorkGroups 3.11 ( aka WFWG or WFW ).

          Windows for WorkGroups 3.11 has the best handling of the 16550
          UART's FIFO.

          Windows 3.1x has the transmit and receive FIFO buffers hard
          coded ( one reason why you get more overruns with Win 3.1x ).
          So I have included info about the Shareware utility 16550.EXE
          that can help reduce comm overruns.

          I've included an example PIF file for WWIV that calls a Batch
          file.  And I've added info about drive caches ( Smartdrive and
          32-bit disk access ).  Plus examples of my AUTOEXEC.BAT,
          CONFIG.SYS, and my BBS Batch file for a Caller Instance ( with
          info on changes for a Sysop Instance Batch file ).


          *******************************
          ONE NOTE TO ADD: Screen Savers!
          *******************************

          For best results when callers are online --- use a "Blank
          Screen" for your Windows Screen Saver option ( Control Panel;
          Desktop ).

          If you use a fancy, busy, or graphics-intensive screen saver,
          especially with older 386 and 486 systems, then your BBS may
          be too slow for callers --- and it may not even be able to
          respond fast enough for some dial-up file transfers or network
          packet transfers when the screen saver starts.

          If so, then you'll see failed file transfers and failed net
          transfers that cannot be traced to other problems --- and you
          should try the Blank Screen screen saver.


          ************************************************************
          Faster PC's wanting fancy Screen Savers --- or Screen Savers
          with a Password:
          ************************************************************

          For systems that are 486-100 and faster that don't want the
          "Blank Screen" as their screen saver --- or for a BBS using
          any cpu/speed that wants to use a screen saver that has a
          password option ( the Blank Screen doesn't usually have one )
          --- then choose one with the least graphics-intensive display
          possible from the selection of screen savers that you have
          available on your system.

          You can try it with systems that are slower than a 486-100,
          but it will depend on how much RAM you have, and your video
          card, as to what results you will get and if you can get
          efficient use from something other than the "Blank Screen".


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 3-A ]   You can modify my BBS PIF template for use with other DOS apps.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


          You can use the example BBS PIF template in this FAQ
          as a guide for PIFs for other DOS programs that you
          plan to run when your BBS is up and running --- but
          only so long as you:

          [ a ] Set their foreground and background priorities to
                no more than 70.  Any less and they might be too
                slow for you.  Any more and they will slow down the
                BBS when a caller is online.  But you can experiment.

                * Slowdowns are less noticeable with faster cpu's.

                * As a result you could experiment more widely with
                  PIF settings for those.

                * I'd suggest using my PIF settings as a guideline
                  based on my own experiences to date since 1995.


          [ b ] Set the settings for WINTIMESLICE and MINTIMESLICE
                as shown in my SYSTEM.INI examples.

                * You can raise the 200 to 300 if you would like to
                  try that.  It worked well for me with an Intel
                  486DX-33 and an AMD 586-133.

                * 200 worked just fine for me for 386/486/586 cpu's.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 3-B ]   Using 16550.EXE to reduce, or get rid of, comm overruns.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


          DOS and Windows can freak the BBS with comm overruns in certain
          conditions.  This FAQ mentions a problem with Win 3.1x - and how
          WFW does better - and settings to use for SYSTEM.INI and WIN.INI
          to accommodate them.

          The final solution for me to avoid comm overruns was the
          16550.EXE shareware utility that sets the FIFO buffer.

          Setting the FIFO threshold to 4 worked best for our PC's in
          DOS and when running under Win 3.1x or WFW.

          I have 16550.EXE run every time the BBS is started - which means
          running the BBS from a Batch file - which is easy enough to do.

          16550.EXE made my overruns and retrains negligible ( or less
          common ) when connecting to all systems - except for when I
          called a local 486-SLC that botched all the connects it had.
          That was the fault of the SLC motherboard.  That Sysop tried
          everything but ended up having to replace his motherboard to
          connect well with most other local and long-distance systems.


          ***********************************************************
          Here is the command line I use in my BBS Batch file for the
          16550 utility.
          ***********************************************************

          C:\SYS\16550 COM2 /f /t4

          Key:
               C:\SYS\16550  =  DRIVE:\PATH\PROGRAM
               COM2          =  COMPORT
               /f            =  /ENABLE FIFO BUFFER
               /t4           =  /THRESHOLD AT 4


          If you need a copy of 16550.EXE it might be found on main
          WWIV distribution boards.  Or request it via Internet mail
          from me as a MIME ( Base64 ) attachment as 16550.ZIP.

               * 16550.EXE is Copyright (c) 1993 Brent C. Turner.


          For WWIV systems on the FILEnet network, you can request
          the 16550.ZIP from my BBS --- @301 --- and many other boards
          also have it for downloads and available via NFT ( Network
          File Transfer utility for the FILEnet WWIV network ).


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 4-A ]   EXAMPLE AUTOEXEC.BAT --- MS-DOS 6.22.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


REM  *************************************************************
REM  *  Origin - Screaming Alarm Clock BBS, Richland, WA - 1999. *
REM  *  My AUTOEXEC.BAT for DOS and Windows 3.1x or WFWG 3.11.   *
REM  *  REMs will not greatly slow down booting. If so - delete! *
REM  *  Save this original file so you don't lose the REM(ark)s! *
REM  *************************************************************

@ECHO OFF

PROMPT $d $t$_$p :                   REM  Day, date, time, drive.

BREAK=ON

VERIFY=ON                            REM  Sets DOS to verify writes.

PATH C:\WINDOWS;C:\;C:\DOS;C:\WWIV\;C:\COMM;C:\ARCHIVE;C:\WW4UTILS;

                                     REM  Computers that only run a
                                     REM  BBS might speed up WWIV by
                                     REM  having C:\WWIV earlier in
                                     REM  the PATH.  If you also use
                                     REM  the computer for other things
                                     REM  then my example here is fine.

                                     REM  I have my HS-Link and Zmodem
                                     REM  in C:\COMM to avoid problems.

                                     REM  I have my zip/unzip type utils
                                     REM  in C:\ARCHIVE.

                                     REM  I placed utils for chain/drop
                                     REM  files for games and doors in
                                     REM  C:\WW4UTILS --- to be able to
                                     REM  quickly find them and to have
                                     REM  an easy-to-recall dir for the
                                     REM  batch files --- for BBS games
                                     REM  that need to run utils to get
                                     REM  handle/name or speed settings.

                                     REM  I placed all games under a
                                     REM  C:\BBSGAMES dir in case I do
                                     REM  not want to back it up often.
                                     REM  This way it survives if \WWIV
                                     REM  sub-directories ever hiccup
                                     REM  from a bad network packet.
                                     REM  I don't place BBSGAMES in PATH.

                                     REM  I found that it is a good idea
                                     REM  to not have everything under
                                     REM  C:\WWIV. It can avoid -some-
                                     REM  hiccups that can arise with
                                     REM  older versions of HS-Link, etc,
                                     REM  when get a bad network packet.

SET TEMP=C:\TEMP                     REM  Location of my temp dir.

REM Mouse driver for my system       REM  Loaded high with  LH commands.

REM Shareware doskey-type util       REM  Loaded high with  LH commands.

REM CD-ROM driver for my system      REM  Loaded high with  LH commands.

LH C:\WINDOWS\SMARTDRV.EXE           REM  Smartdrive will speed up hdd.

C:\DOS\SHARE.EXE                     REM  Needed for DOS and Win 3.1x.

                                     REM  WFW 3.11 has SHARE built-in.
                                     REM  If you -always- run the BBS
                                     REM  within Windows, then you do
                                     REM  not need to load SHARE in
                                     REM  the AUTOEXEC.BAT.
                                     REM  If you ever ( plan to ) run
                                     REM  the BBS in plain DOS, then
                                     REM  you do need to load SHARE
                                     REM  in your AUTOEXEC.BAT.
                                     REM  -Never- load SHARE high with
                                     REM  LH SHARE     or you will have
                                     REM  problems and lose data!

WIN /3                               REM  Windows / WFW in Enhanced mode.

REM  *********************************************************************
REM  * Even if you enable 32-Bit disk access you will still want to use  *
REM  * Smartdrive. I don't know why - but it greatly speeds up my BBS in *
REM  * Windows - and I always use it if the BBS is running in plain DOS. *
REM  *********************************************************************

:END                                 REM  End of AUTOEXEC.BAT example.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 4-B ]   EXAMPLE CONFIG.SYS --- MS-DOS 6.22.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


REM  *************************************************************
REM  *  Origin - Screaming Alarm Clock BBS, Richland, WA - 1999. *
REM  *  My CONFIG.SYS for DOS and Win 3.1x or WFWG 3.11.         *
REM  *  NOTE: Remove REMs from actual CONFIG.SYS you boot with.  *
REM  *  Save this original file so you don't lose the REM(ark)s! *
REM  *************************************************************

DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF /V

DEVICE=C:\WINDOWS\EMM386.EXE ON RAM H=64 D=64 /V

BUFFERS=10,0                          REM  No Smartdrive? Set to 40,0 now!
                                      REM  I often set this to 40 or 50
                                      REM  even when using SmartDrive.

FILES=50                              REM  Set to 60 if needed by WWIV.

DOS=UMB                               REM  Load DOS into upper mem regions.

LASTDRIVE=Z                           REM  Set to your last drive letter.

FCBS=32,0                             REM  File control blocks.

DOS=HIGH                              REM  Load DOS into high mem.

STACKS=64,256                         REM  Greatly reduces comm overruns.
                                      REM  Some use:       STACKS=9,256

SHELL=C:\COMMAND.COM C:\ /E:2048 /P   REM  Environment space for games.

DEVICE=C:\DOS\FIX16550.SYS            REM  AMI BIOS 16550 bug fix util.

DEVICEHIGH=C:\DOS\ANSI.SYS            REM  Ansi driver.

DEVICEHIGH=C:\PATH\CDROM.SYS          REM  My CD-ROM driver loads here.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 4-C ]   EXAMPLE BBS BATCH FILE ( B.BAT ) with REMs.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


-----------------------------------------------------------------


          For a Sysop Instance ( SYSOP.BAT ) use these changes to
          make a SYSOP.BAT from the B.BAT example below:

          SET WWIV_INSTANCE=2

          BBS.EXE /I2 /N0 /A1 /O /M %1 %2 %3 %4 %5

          The /M tells the BBS to ignore any modem.  The next
          edition of this FAQ will explain all the switches in
          more detail.  You need them for this example to work!


-----------------------------------------------------------------


@ECHO OFF

REM  *************************************************************
REM  *  ORIGIN - SCREAMING ALARM CLOCK BBS, RICHLAND, WA - 1999. *
REM  *************************************************************
REM  *  BATCH FILE FOR INSTANCE 1 - CALLER INSTANCE.  B.BAT.     *
REM  *************************************************************
REM  *  SAVE ORIGINAL AND DELETE ALL REM(arks) FROM FILE YOU USE.*
REM  *************************************************************
REM  * Copyright (c) 1994-1999 Dan Morgan/Screaming Alarm Clock  *
REM  *************************************************************
REM  * Quixotic Quest/OnTheFritz. Internet: onthefritz@pobox.com *
REM  *************************************************************


REM Remove all lines referring to KLOS PPP unless you use KLOS PPP drivers!


VERIFY ON                      REM Tells DOS to verify writes.
BREAK ON                       REM Enables CTRL-Break, etc.



REM -=-=-=-= Separator Line for Label for GOTO. -==-
:BBS
REM -=-=-=-= Separator Line for Label for GOTO. -==-

C:\SYS\16550 COM2 /f /t4       REM  Sets Com Port FIFO via 16550 util.

LSL /U                         REM  Force LSL to unload ( KLOS PPP ).
LH C:\WWIV\LSL                 REM  Loads LSL for BBS   ( KLOS PPP ).

C:                                        REM  Change to BBS drive.
CD\WWIV                                   REM  Change to BBS directory.

SET TZ=PST8PDT                            REM  Sets to Pacific Time Zone.
SET BBS_NAME=SCREAMING ALARM CLOCK        REM  For my Game Batch Files.
SET WWIV_INSTANCE=1                       REM  For my Game Batch Files.

FLINK                                     REM  Run FLINK for unmodded BBS.

REM  The BBS command line sets the BBS to exit after each call, which the
REM  Batch file uses to either quit ( Q or ESC-Y at WFC ) or to loop thru
REM  the Batch file to restart the BBS. The looping helps an unmodded BBS
REM  to run "LINKER" and "FLINK" utils on packets between calls. Here the
REM  BBS is told to start Instance 1 ( /I1 ) and is given exit parameters.
REM  Since I have a 28.8/33.6 modem I set my Com Port to 115200.

BBS.EXE /I1 /S115200 /N0 /A1 /O /C %1 %2 %3 %4 %5

IF ERRORLEVEL 4 GOTO EVENT
IF ERRORLEVEL 2 GOTO QUITBBS
IF ERRORLEVEL 1 GOTO PREP4BBS
IF ERRORLEVEL 0 GOTO PREP4BBS



REM -=-=-=-= Separator Line for Label for GOTO. -==-
:EVENT                        REM  From WWIV docs for BBS Batch files.
REM -=-=-=-= Separator Line for Label for GOTO. -==-

C:                            REM  Change to BBS drive.
CD\WWIV                       REM  Change to BBS directory.
GOTO PREP4BBS                 REM  After event - loop to run Net utils.



REM -=-=-=-= Separator Line for Label for GOTO. -==-
:PREP4BBS                     REM  Label for Utils prior to BBS restart.
REM -=-=-=-= Separator Line for Label for GOTO. -==-

C:                            REM  Change to BBS drive.
CD\WWIV                       REM  Change to BBS directory.

FLINK                         REM  Run FLINK for unmodded BBS.
NETWORK2.EXE                  REM  Run LINKER for unmodded BBS.

GOTO BBS                      REM  Loop back to restart the BBS.  Needed!



REM -=-=-=-= Separator Line for Label for GOTO. -==-
:QUITBBS
REM -=-=-=-= Separator Line for Label for GOTO. -==-

ECHO.
ECHO.
ECHO.
ECHO                          " QUITTING THE BBS "
ECHO.
ECHO.
ECHO.

C:                            REM  Change to BBS drive.
CD\WWIV                       REM  Change to BBS directory.

LSL /U                        REM  Unload LSL driver ( KLOS PPP ).

FLINK                         REM  Run FLINK for unmodded BBS.
NETWORK2.EXE                  REM  Run LINKER for unmodded BBS.

CD\                           REM  Habitual return to C:\ from DOS days.

EXIT                          REM  Critical for Win95 to avoid the
                              REM  horrible " Hit CTRL-C " prompt.

:END


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 4-D ]   EXAMPLE BBS BATCH FILE ( B.BAT ) w/o REMs.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


@ECHO OFF

REM  *************************************************************
REM  *  ORIGIN - SCREAMING ALARM CLOCK BBS, RICHLAND, WA - 1999. *
REM  *************************************************************
REM  *  BATCH FILE FOR INSTANCE 1 - CALLER INSTANCE.  B.BAT.     *
REM  *************************************************************


REM Remove all lines referring to KLOS unless you use KLOS PPP drivers!


VERIFY ON
BREAK ON



:BBS

C:\SYS\16550 COM2 /f /t4

LSL /U                         REM  Force LSL to unload ( KLOS PPP ).
LH C:\WWIV\LSL                 REM  Loads LSL for BBS   ( KLOS PPP ).

C:
CD\WWIV

SET TZ=PST8PDT
SET BBS_NAME=SCREAMING ALARM CLOCK
SET WWIV_INSTANCE=1

FLINK

BBS.EXE /I1 /S115200 /N0 /A1 /O /C %1 %2 %3 %4 %5

IF ERRORLEVEL 4 GOTO EVENT
IF ERRORLEVEL 2 GOTO QUITBBS
IF ERRORLEVEL 1 GOTO PREP4BBS
IF ERRORLEVEL 0 GOTO PREP4BBS



:EVENT
C:
CD\WWIV
GOTO PREP4BBS



:PREP4BBS
C:
CD\WWIV
FLINK
NETWORK2.EXE
GOTO BBS



:QUITBBS
ECHO.
ECHO.
ECHO.
ECHO                          " QUITTING THE BBS "
ECHO.
ECHO.
ECHO.

C:
CD\WWIV

LSL /U                        REM  Unload LSL driver ( KLOS PPP ).

FLINK
NETWORK2.EXE

CD\

EXIT

:END


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 5 ]   WIN 3.1x / WFW 3.11 --- WIN.INI --- Example Settings.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


          [ a ] Edit your WIN.INI and SYSTEM.INI with Windows
                Notepad, or use a DOS Editor that saves files
                as plain ascii text.

          [ b ] Always back-up copies of all .ini files in your
                Windows directory * before * making any changes
                with the examples and info you see here.

          [ c ] Anything preceded with ; is a REMark for Windows
                and should be removed when you cut/paste and edit.

                * I use ;; to make it stand out more in this FAQ.


          -------------------------------------------------------


[ports]
COM1:=2400,e,7,1        ;; my Mouse port; 2400 baud, Com 1
                        ;; e = even parity, 7 = 7 bit, 1 = 1 stop bit.
                        ;; Example of possible settings w/mouse on Com 1.

COM2:=115200,n,8,1,p    ;; My 1st Modem port; 28.8k, Com 2 (BBS).
                        ;; n = no parity, 8 = 8 bit, 1 = 1 stop bit.
                        ;; p = hardware flow control (CTS/RTS).
                        ;;     Modem and term programs need to be
                        ;;       set to use this also (CTS/RTS).
                        ;; Example of possible settings w/modem on Com 2.

COM3:=115200,n,8,1,p    ;; My 2nd Modem port; 14.4k, Com 3 (FAX).
                        ;; n = no parity, 8 = 8 bit, 1 = 1 stop bit.
                        ;; p = hardware flow control (CTS/RTS).
                        ;;     Modem and term programs need to be
                        ;;       set to use this also (CTS/RTS).
                        ;; Example of possible settings w/modem on Com 3.


                ----------------------------------------------


          ***************************************************************
          IMPORTANT NOTES:
          COM PORT SPEED SETTINGS AND UART INFO - 14.4k modems and above.
          ***************************************************************

          [ a ] Set to 115200 as it's "2 x 57600". A setting of 57600
                should work fine, too.  You have to set this with an
                editor program.


          [ b ] However, 115200 is used here as it is twice the top
                connect speed of a 14.4 modem - and meets settings for
                28.8/33.6 - which follows suggestions I've found - ie:
                to apply this setting as a way to help reduce the com
                port bottlenecks.  With Windows 3.1x or WFW 3.11 you
                won't usually achieve connect speeds beyond 57600.


          [ c ] Win 3.1x and WFW 3.11 require NS16550AFN compatible
                16550 UARTs for 14.4k+ modems ( NS is for National
                Semiconductor ).  Without this you are prone to
                retrains and comm overruns - unless perhaps you use
                only DOS for WWIV on a dedicated PC.

                * Internal modems usually have a 16550 UART built
                  into the modem.

                * To see if your external modem's com port has a
                  16550 UART ( and not an older 16450 or 8250 UART )
                  run MSD.EXE from the DOS prompt ( not in Windows! )
                  and select Com Ports.  The last line displayed shows
                  the "UART Chip Used" by the com ports on your PC.

                * 16550 UARTs can also be found on Serial Port Cards,
                  or Combination Hard/Floppy/I/O Controller Cards.

                * If your system has com ports built into the mother-
                  board, then the com ports must have 16550 UARTs ( or
                  later/higher ) to be able to support 14.4k+ modems.

                  If not, then check your manual on how to disable
                  them ( in CMOS or via jumpers ) and purchase a
                  one or two port Serial Port Card that has 16550
                  ( or later/higher ) UARTs to support a 14.4k+
                  external modem for your BBS.


          [ d ] Can Windows for Workgroups 3.11 support a 56k modem?

                * In my experience: Yes!  So long as your settings
                  match up with what I have shown in this FAQ.

                * I achieved connects from 44000 baud to 50667
                  baud ( with connect speeds of 57600 ) with an
                  external 56k modem with 56k-Flex Fall back that
                  uses a Rockwell chipset.

                  I used a modem file I created for WWIV for 56k
                  modems that use the Rockwell chipset that have
                  56k-Flex Fall back.  Filename: R56KV9FC.MDM.
                  Version: Beta 4 ( at the time of this FAQ ).

                  I can email you a copy if I do not have it on
                  the 'PPP Project for WWIV' web sites, or if it
                  is not in my file list for NFT for the FILEnet
                  WWIV network ( my node is currently @301 ).


          [ e ] Can Windows 3.1x support a 56k modem?

                I have not tried it.  My guess is: No.

                And I would say it's a gamble --- and not to try
                it --- since Windows 3.1x does not handle the
                com port's UART FIFO as well as Windows for
                Workgroups 3.11 can ( after WFWG is tweaked ).


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 6 ]   WINDOWS 3.1x --- SYSTEM.INI --- Example Settings.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


          [ a ] Edit your WIN.INI and SYSTEM.INI with Windows
                Notepad, or use a DOS Editor that saves files
                as plain ascii text.

          [ b ] Always back-up copies of all .ini files in your
                Windows directory * before * making any changes
                with the examples and info you see here.

          [ c ] Anything preceded with ; is a REMark for Windows
                and should be removed when you cut/paste and edit.

                * I use ;; to make it stand out more in this FAQ.


          -------------------------------------------------------


[boot]
comm.drv=COMM.DRV ;; Use this! Do not use any replacement comm drivers.

[386enh]
maxcomport=4      ;; My system has 4 Com ports. Set to your maximum.

com1base=03f8     ;; Hardware Com Port 1 address. Yours may differ.
com1irq=4         ;; Standard Com 1 IRQ - my system - yours may differ.

COMnFIFO=n        ;; Remove this line when found (n is any number).
                  ;;     Tells Windows a 16550 UART is present or not.
                  ;;     Win 3.1x cannot handle this info correctly!
                  ;;     This is a correction to the manual and docs!
                  ;; A 16550 UART is req'd for Win for 14.4k+ modems,
                  ;; but don't try to tell Windows 3.1x it is present!
                  ;; Internal 14.4k+ modems usually have a 16550 UART.

                  ;; Consider the $50 (ballpark) upgrade to WFW 3.11
                  ;; if you own Windows 3.1x - for improved communi-
                  ;; cations and handling of 16550 UART's and FIFO's.
                  ;; Or, consider upgrading to Windows 95 if you have
                  ;; 16 MB of RAM or more, and a 486DX2-66 or better.

                  ;; Win 3.1x has the receive FIFO hard-coded to 14 and
                  ;; that (usually) is why you get overruns and errors.

                  ;; WFW 3.11 does not enable you to set the "transmit"
                  ;; FIFO, but you <can> set the "receive" FIFO to 4 and
                  ;; your communications could improve significantly.
                  ;; WFW 3.11 can also be set-up w/o network functions!

com2base=02f8     ;; Hardware Com Port 2 address. Yours may differ.
com2irq=3         ;; Standard Com 2 IRQ - my system - yours may differ.
com2buffer=11520  ;; Buffer for Com 2 - no more than 57600 suggested.

com3base=03e8     ;; Hardware Com Port 3 address. Yours may differ.
com3irq=7         ;; Special IRQ assignment for my system's Com Port 3.
com3buffer=11520  ;; Buffer for Com 3 - no more than 57600 suggested.

com4base=02e8     ;; Hardware Com Port 4 address. Yours may differ.
com4irq=3         ;; Standard Com 4 IRQ - my system - yours may differ.
com4buffer=11520  ;; Buffer for Com 4 - no more than 57600 suggested.

mintimeslice=20         ;; Sets minimum time slice for applications.
wintimeslice=200,50     ;; Sets foreground to 200, background to 50.
winexclusive=0          ;; Use this - enables DOS apps in background.

com1autoassign=0        ;; Prevents Com Port conflict reports & enables
com2autoassign=0        ;; DOS & Windows communications applications to
com3autoassign=0        ;; share Com Port when switching back & forth.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 7 ]   WFW 3.11 --- SYSTEM.INI --- Example Settings.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


          [ a ] Edit your WIN.INI and SYSTEM.INI with Windows
                Notepad, or use a DOS Editor that saves files
                as plain ascii text.

          [ b ] Always back-up copies of all .ini files in your
                Windows directory * before * making any changes
                with the examples and info you see here.

          [ c ] Anything preceded with ; is a REMark for Windows
                and should be removed when you cut/paste and edit.

                * I use ;; to make it stand out more in this FAQ.


          -------------------------------------------------------


[boot]
comm.drv=COMM.DRV ;; Use this! Do not use any replacement comm drivers.

[386enh]
device=serial.386 ;; Update this via Microsoft BBS or ftp.microsoft.com.
                  ;; File Name is: WG1001.EXE

maxcomport=4      ;; My system has 4 Com ports. Set to your maximum.

com1base=03f8     ;; Hardware Com Port 1 address. Yours may differ.
com1irq=4         ;; Standard Com 1 IRQ - my system - yours may differ.

com2base=02f8     ;; Hardware Com Port 2 address. Yours may differ.
com2irq=3         ;; Standard Com 2 IRQ - my system - yours may differ.

com2fifo=2        ;; Specific: Win for Work groups 3.11 for 16550 UART.
                  ;;     Tells WFW 3.11 a 16550 UART is present on Com 2.
                  ;;     16550 UART is required for Win for 14.4k+ modems.
                  ;;     This is a correction to the manual and the docs.

com2txfifo=1      ;; Enables transmit FIFO <non-configurable threshold>.
com2rxtrigger=4   ;; Sets 16-byte receive FIFO interrupt threshold to 4,
                  ;; optimized for Windows/DOS by setting the FIFO to 4.
                  ;; HS-Link FIFO threshold must also be set to 4.
                  ;; Don't use the fifo/tx/rx settings w/o a 16550 UART.

com2buffer=11520  ;; Buffer for Com 2 - no more than 57600 suggested.

com3base=03e8     ;; Hardware Com Port 3 address. Yours may differ.
com3irq=7         ;; Special IRQ assignment for my system's Com Port 3.

com3fifo=2        ;; Specific: Win for Work groups 3.11 for 16550 UART.
                  ;;     Tells WFW 3.11 a 16550 UART is present on Com 3.
                  ;;     16550 UART is required for Win for 14.4k+ modems.
                  ;;     This is a correction to the manual and the docs.

com3txfifo=1      ;; Enables transmit FIFO (non-configurable threshold).
com3rxtrigger=4   ;; Sets 16-byte receive FIFO interrupt threshold -
                  ;; optimized for Windows/DOS by setting FIFO to 4.
                  ;; HS-Link FIFO threshold must also be set to 4.
                  ;; Don't use the fifo/tx/rx settings w/o a 16550 UART.

com3buffer=11520  ;; Buffer for Com 3 - no more than 57600 suggested.

com4irq=3         ;; Standard Com 4 IRQ - my system - yours may differ.
com4base=02e8     ;; Hardware Com Port 4 address. Yours may differ.

com4buffer=11520  ;; Buffer for Com 4 - no more than 57600 suggested.

mintimeslice=20         ;; Sets minimum time slice for applications.
wintimeslice=200,50     ;; Sets foreground to 200, background to 50.
winexclusive=0          ;; Use this - enables DOS apps in background.

com1autoassign=0        ;; Prevents Com Port conflict reports & enables
com2autoassign=0        ;; DOS & Windows communications applications to
com3autoassign=0        ;; share Com Port when switching back & forth.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 8 ]   Example PIF: WWIV ( DOS ) BBS with Win 3.1x or WFW 3.11.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


---------------------------------------------------------------------------
| - |                PIF EDITOR - WWIV-N1.PIF                       |\/|/\|
---------------------------------------------------------------------------
| File  Mode  Help                                                        |
---------------------------------------------------------------------------
| PROGRAM FILENAME:      [ C:\WWIV\B.BAT                          ]       |
| WINDOW TITLE:          [ WWIV BBS - INSTANCE 1                  ]       |
| OPTIONAL PARAMETERS:   [                                             ]  |
| STARTUP DIRECTORY:     [ C:\WWIV                                     ]  |
| VIDEO MEMORY:          [x] TEXT   [ ] LOW GRAPHICS   [ ] HIGH GRAPHICS  |
| MEMORY REQUIREMENTS:   KB REQUIRED:   [ 640 ]      KB DESIRED: [ -1  ]  |
| EMS MEMORY:            KB REQUIRED: [   0   ]      KB LIMIT: [   -1  ]  |
| XMS MEMORY:            KB REQUIRED: [   0   ]      KB LIMIT: [   -1  ]  |
| DISPLAY USAGE:    [x]  FULL SCREEN           EXECUTION: [x] BACKGROUND  |
|                   [ ]  WINDOWED   ----------------      [ ] EXCLUSIVE   |
| [x] CLOSE WINDOW ON EXIT          |   ADVANCED   |                      |
|                                   ----------------                      |
| PRESS F1 FOR HELP                                                       |
---------------------------------------------------------------------------
| - |                         ADVANCED OPTIONS                            |
---------------------------------------------------------------------------
| -- MULTITASKING OPTIONS -------------------------------------  -------- |
| |                                                           |  |  OK  | |
| |  BACKGROUND PRIORITY: [ 125 ] FOREGROUND PRIORITY: [ 125 ]|  -------- |
| |                       [x] DETECT IDLE TIME                |  |CANCEL| |
| -------------------------------------------------------------  -------- |
| -- MEMORY OPTIONS ----------------------------------------------------- |
| |  [ ] EMS MEMORY LOCKED               [ ] XMS MEMORY LOCKED          | |
| |  [x] USES HIGH MEMORY AREA           [ ] LOCK APPLICATION MEMORY    | |
| ----------------------------------------------------------------------- |
| -- DISPLAY OPTIONS ---------------------------------------------------- |
| |  MONITOR PORTS:   [ ] TEXT    [ ] LOW GRAPHICS    [ ] HIGH GRAPHICS | |
| |                [x] EMULATE TEXT MODE        [ ] RETAIN VIDEO MEMORY | |
| ----------------------------------------------------------------------- |
| - OTHER OPTIONS ------------------------------------------------------- |
| | [x] ALLOW FAST PASTE               [ ] ALLOW CLOSE WHEN ACTIVE      | |
| | RESERVE SHORTCUT KEYS:  [ ] ALT+TAB    [ ] ALT+ESC    [ ] CTRL+ENTER| |
| |                         [ ] PRTSC      [ ] ALT+PRTSC  [ ] ALT+SPACE | |
| |                         [ ] ALT+ENTER                               | |
| ----------------------------------------------------------------------- |
| APPLICATION SHORTCUT KEY: [         ]                                   |
| PRESS F1 FOR HELP                                                       |
---------------------------------------------------------------------------

          * Create this via the PIF Editor.

          * Place the PIF into a Program Manager Group.

          * For example:
            Alt-File, New, Program, WWIV-N1.PIF.


          * 4 MB RAM or more is required for best results.


          * You can experiment with increasing the EMS / XMS memory
            required to give more resources to the BBS - but this
            will slow down your system and may prevent unattended
            restarts of the BBS.


          * The  -1  settings tells Windows to make memory resources
            available to the BBS when needed.


          * This example is for machines with 4MB+ of RAM running
            Instance 1 for calls and Instance 2 (not shown) for a
            local Sysop instance.


          * The "Sysop" instance PIF file should have priority
            settings around 70 and 70 to be fast enough - but still
            not interfere with the speed the caller will require.
            Experiment yourself for best results.


          * These settings have worked well for me with both an
            Intel 386DX-25 and an Intel 486DX-33 with 4 MB of RAM
            (70 ns) --- and an AMD 586-133 ( P-75 equivalent )
            with 16 MB of RAM ( 70 ns ).


          * Any DOS programs that you want to run - when the BBS is
            up - should use PIF files.


          * Priorities for PIFs for DOS programs:

              Foreground 70.

              Background 50.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%
[ 9-A ]   Smartdrive.
%%%%%%%%%%%%%%%%%%%%%


          I get best results for overall speed, and when processing
          Net packets, when I use SmartDrive ( SMARTDRV.EXE ) set in
          AUTOEXEC.BAT.  You can enable 32-bit disk access and create
          or re-size the permanent swap file in Windows 3.1x and WFW
          3.11 in the Control Panel to further speed up the PC.
          However, there are some things to check on first.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 9-B ]   Back Up your BBS now, before: setting up Smart Drive; changing
            Swap File size; and/or, before trying out 32-bit Disk Access.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


*************************************************************************
BACK-UP YOUR BBS NOW!  COMPARE/CHECK THE BACKUP TO VERIFY IT IS ACCURATE!
*************************************************************************


          * You will want to check for errors ( ScanDisk, or Norton's Disk
            Doctor ) and optimize/defrag the drive before you re-size or
            create the permanent swap file for Windows.  ( Optimize with
            MS Defrag or Norton's Speedisk. )


          * If you have never used MS-DOS hard drive utils or Norton's
            utils before - then read this section for a warning about
            being careful before using a hard disk utility to check for
            errors or to optimize/defrag the drives.


          * If you are familiar with the utils, and you agree that all
            information in this FAQ, and your application and use of
            that information, is solely at _your_ own risk, then skip
            on to the Control Panel section.  If you cannot agree,
            then do not use the information in this FAQ.


          /-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/
                                  * DISCLAIMER *
          /-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/


          * If you run the utils mentioned in this file and detect errors
            --- then it is not my fault those errors exist.

          * That may sound silly, but in today's world it's best to post
            the disclaimer before folks contact you because they didn't
            read the software manuals, or the Help files or Docs before
            using various utilities.


          * Please read the manuals and any help files to see what these
            do ( Norton's or MS-DOS ). For MS-DOS utils you can get more
            info at the DOS prompt with: HELP SCANDISK  and  HELP DEFRAG.


          * If you cannot agree that all risk in applying the information
            in this FAQ is solely _your_ own, and I am not responsible for
            hiccups / errors / lost data / any and all damages... then do
            _not_ use the information in this FAQ.


          /-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 9-C ]   Checking hard Drive for Errors and Optimizing/Defragging:
          PRECAUTIONS.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


          [ a-1 ] Make sure that:

                  * You are booted to DOS ( not running in Windows ).
                  * You do not have a Network running.


          [ a-2 ] Use the  VERIFY=ON  command before testing your
                  hard drive for errors and before optimizing/
                  defragging your hard drive!

                  * In DOS ( and before loading Windows ) use this
                    command at the prompt:

                    VERIFY=ON  [ ENTER ]


                  *******************************************************
                  * That command tells DOS to verify that info is written
                    to the hard drive correctly.
                  * That's no guarantee that DEFRAG won't still mess up,
                    but it certainly can't hurt to try to tell it to
                    verify writes.
                  * Norton's Speedisk has an option to select in the
                    pull-down menus for "Read after Write" to verify the
                    data is written correctly.  This may be redundant
                    after VERIFY=ON --- but I lost data many years ago
                    before discovering that VERIFY=ON and "Read After
                    Write" options existed!  After that I back-up
                    regularly and I make sure I use VERIFY=ON, etc.
                  
                  *******************************************************


          [ a-3 ] Turn off SmartDrive before you defrag/optimize!

                  SMARTDRIVE C- D- E- F-  [ ENTER ]

                  * Have all physical drive letters on your computer
                    in the command line and follow the above example
                    to have a minus sign after each drive letter.


          [ b ]   Run your hard disk utility to check for errors.

                  * MS-DOS Scandisk, or Norton's Disk Doctor.


          [ c ]   Optimize the hard drive.

                  *  MS-DOS Defrag, or Norton's Speedisk.

                  ****************************************************
                  NOTE: This may take several hours if you have never
                        done this before.  The goal is to unfragment
                        your drive so that later on Windows can create
                        a larger, and permanent, swap file ( 4 MB to
                        20 MB in size ).
                  ****************************************************


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 9-D ]   Permanent Swap File and size.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


          [ a ] Boot your BBS computer without a Network.


          [ b ] Run Windows 3.1x or WFW 3.11

                WIN /3   [ ENTER ]


          [ c ] Run Control Panel ( it is usually found in
                the Main Group ).


          [ d ] Select or Click on: Enhanced.


          [ e ] Select or Click on: Virtual Memory.


          [ f ] Select or Click on: Change.


          [ g ] Select or Click on:

                Use 32-Bit Disk Access    [ make an X appear ].

                * Some hard drives may not allow this ).


          [ h ] Select or Click on:

                Use 32-Bit File Access    [  make an X appear ].

                *** If you are running WFW and using 32-Bit Disk Access.


          [ i ] Select or Click on: Cache size.

                * Set to 1,024 KB

                *** If you are running WFW and using 32-Bit Disk Access.


          [ j ] Select or Click on: OK.


          [ k ] After you click on OK you will be asked if you are
                sure you want to make the changes to the Virtual
                Memory settings.  Click on "Yes".

                You will be asked if you want to restart Windows.
                Choose "Continue" to return to Windows ( instead
                of restarting Windows ).


          [ l ] Select or Click on: Virtual Memory

                * In Enhanced section of Control Panel.


          [ m ] Select or Click on: Change.


          [ n ] Select or Click on: Type

                * Set to Permanent.


          [ o ] A drive will be suggested.

                * Choose an uncompressed drive.


          [ p ] You can manually set the size.

                * You will see the following:

           SPACE AVAILABLE.    MAXIMUM SIZE.    RECOMMENDED SIZE.

           * Use the Space Available info to help determine the size
             of the permanent swap file you are now going to create
             or re-size.

           * I set my swap file to 20 MB ( 20480 ) --- that Windows
             set to 20254 when it was all done.  I had 16 MB of RAM
             and this worked well for me.

           * You should set your swap file to at least 4 MB if you
             have only 4 MB of RAM.

           * A swap file of 12 MB or more gives a speed boost in many
             cases.  The maximum size you can specify for the swap
             file depends on the amount of physical RAM your PC has.

           * Although you can kludge it to set it higher, you are
             going to be told by Windows that it will only use a
             certain amount of the swap file if you set it too high.
             

           Here's a chart for telling Windows what you want.  If it
           tells you that it will not use all of the swap file you
           create --- ignore that info --- as I have found that it
           really does tend to use more than it says it will.


           ----------------------------------------------------------
           RAM  SWAP | RAM  SWAP | RAM  SWAP | RAM  SWAP | RAM  SWAP
                FILE |      FILE |      FILE |      FILE |      FILE
                SIZE |      SIZE |      SIZE |      SIZE |      SIZE
           ----------|-----------|-----------|-----------|-----------
           MB  Set To| MB  Set To| MB  Set To| MB  Set To| MB  Set To
           ----------|-----------|-----------|-----------|-----------
            4  4816  |  5  5120  |  6  6144  |  7  7168  |  8  8192
            9  9216  | 10  10240 | 11  11264 | 12  12288 | 13  13312
           14  14336 | 15  15360 | 16  16384 | 17  17408 | 18  18432
           19  19456 | 20  20480 |           |           |
           ----------------------------------------------------------


          [ q ] After you tell Control Panel the size for the swap
                file --- you will be asked if you are sure you want
                to make changes to the Virtual Memory settings.

                * Click on: "Yes".


          [ r ] You will be asked if you want to restart Windows.

                *  Choose: "Continue"   ( to return to Windows ).


          [ s ] Now exit out of Control Panel.


          [ t ] Now exit out of Windows to DOS.


          [ u ] Restart Windows or WFW with:    WIN /3   [ ENTER ]

                * Your permanent swap file will now be created
                  or re-sized.  Windows will also now use 32-bit
                  disk access ( if both your computer and Windows
                  support it ).


          [ v ] Now exit Windows and backup your changed settings.

                * Make backups of ( from your Windows directory ):

                  WIN.INI
                  SYSTEM.INI
                  CONTROL.INI
                  PROGMAN.INI

                  and store them ( floppies for example ) in a safe place.

                  * Now backup new, and changed, files to whatever media
                    you use --- such as external drives, or tapes drives,
                    or to CDR or CD-RW, so you can restore these changes.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 10 ]   Copyrights and Trademarks.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

16550.EXE               Copyright (c) Brent C. Turner. All rights reserved.
Defrag                  Copyright (c) Microsoft.       All rights reserved.
Doskey                  Copyright (c) Microsoft.       All rights reserved.
FIX16550.SYS            Copyright Professional Software Engineering, Ltd.*
FLINK                   Copyright (c) Dennis M. Myers. All rights reserved.
HS-Link                 Copyright (c) Samuel H. Smith. All rights reserved.
LINKER                  Copyright (c) Hellfire.        All rights reserved.
MS-DOS                  Copyright (c) Microsoft.       All rights reserved.
MSD                     Copyright (c) Microsoft.       All rights reserved.
Norton's Disk Doctor    Copyright (c) Symantec.        All rights reserved.
Norton's Speedisk       Copyright (c) Symantec.        All rights reserved.
Norton's Utilities      Copyright (c) Symantec.        All rights reserved.
Scandisk                Copyright (c) Microsoft.       All rights reserved.
Windows                 Copyright (c) Microsoft.       All rights reserved.
Windows 95              Copyright (c) Microsoft.       All rights reserved.
Windows for WorkGroups  Copyright (c) Microsoft.       All rights reserved.
WWIV BBS ( and WSS )    Copyright (c) Dean Nash.       All rights reserved.

* All rights reserved.


          Copyrights and Trademarks for the hardware, software,
          utilities, and companies mentioned in this FAQ are the
          sole property of their respective owners and holders.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%
[ 11 ]   Credits.
%%%%%%%%%%%%%%%%%


          Source of the FIFO information for Windows 3.1x and
          Windows for WorkGroups 3.11:

          * "Silicon Times Report" ( Electronic Magazine );
             R.F. Mariano, Editor.


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ 12 ]   Requesting this FAQ via NFT.
         Where to find this FAQ on the Web.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


On WWIV BBS's --- you can use the NFT software for FILEnet
( if your BBS is on FILEnet ) --- to request  w31ww422.faq
from node 301 ( Screaming Alarm Clock ).



To download the current edition of this FAQ from
the World Wide Web go to this url:

The filename is: w31ww422.faq.

Main web site - Direct ( if you have problems ):
http://users.owt.com/quixotic/ppp-wwiv

Main web site - Redirect ( url I post for downloads ):
http://pobox.com/~onthefritz/ppp-wwiv

Mirror Web site I maintain ( that I plan to convert to the Main site * ):
http://filenet.wwiv.net
( * Thanks to Frank Reid of Eagle's Dare BBS for the hard drive space! )

The main web site is often not available on Friday mornings from midnight
to 3 am ( Pacific time ).  If I ever change the Web site's location, then
just email or finger       onthefritz@pobox.com     for new information.



To download the 16550.zip ( fifo ) and the FIX16550.SYS ( for AMI bios ):

These are available for download from many WWIV boards, and
you can probably find a copy via NFT.  If they are not on
the 'PPP Project for WWIV' web site, then email me for a zip.

-*- end -*-


=======================================================================
Appendix C (Frequently Asked Questions) WWIV under OS/2
=======================================================================

 NEW INSTALLATION
 SIO SETUP
 FAST SETUP
 DOS SETTINGS
 AUTOEXEC.BAT (BBS)
 INSTALLATION

 DOORS & OnLine GAME's

 HSTART
 HPFS/DOS see "Settings.os2" text file
 Transfer Protocals see "APPE.TXT" & "protos2.txt"
 LAN/PEER see "OS2PEER.TXT"
 PPP Project Considerations see "PPPDOS.FAQ"
 TELNET & Vmodem see "SIO430.DOC"


 *********************************************************

 2.1.1

 NEW INSTALLATION:

    For setup purposes, general use, and understanding
 All examples will be understood to use C:\ & C:\WWIV as
 the basic example for explination.  OS/2 equals
 "IBM's Operating System 2", and HPFS as the file system
 type.

    READ the "Entire Document" before trying to setup WWIV
 under/on an OS/2 system.  IF you are very familiar with
 OS/2 & WWIV have fun :)  All others please read on.

    Things you will need on your system before we can
 started on installing and setting up WWIV under OS/2.

 1) You will need OS/2 to be installed (duh).
 2) Copy of PKZIP/PKUNZIP (pkz204g.exe) setup & part of
    your dos path know as DPATH= in your os2 config.sys file.
    NOTE: Will NOT work with WinZip or InfoZip's unzip.exe.
 3) A copy of wwiv v4.30 installation archive.
 4) Copy of Ray Gwinn's SIO Fossil driver (SIO160D.ZIP)
 5) A modem & phone (if dial up) or some sort of connection
    to the Internet or a LAN connection.
 6) A basic working knowlage of dos commands.

 SIO SETUP:

    Setup SIO v1.60D on your system FIRST!  Shutdown your system
 and Re-Boot.  SIO should then be running.  IF you are running
 on a computer with a PS/2 Mouse.  Decide what comport you are
 setting up your modem on.  You MUST load your mouse driver
 before you load SIO in your config.sys file.

 CONFIG.SYS Changes:

DEVICEHIGH=C:\OS2\BOOT\MOUSE.SYS
DEVICEHIGH=C:\OS2\MDOS\VMOUSE.SYS
DEVICEHIGH=C:\SIO\SIO.SYS (COM2:115200,2F8,IRQ3,-)
DEVICEHIGH=C:\SIO\VSIO.SYS
DEVICEHIGH=C:\SIO\VX00.SYS

 *************** Fast Setup under OS2 Warp *********************

                 ͻ
                  FAST SETUP INFORMATION 
                 ͼ

   Setting up WWIV for the first time is very simple and
 should only take a matter of minutes (Yah right).
 Actually figure on 1 to 2 hours of "Basic" setup time.
 I have added some helpful short cuts in this document.

 2.1.2

    Before you do anything with setting up WWIV v4.30
 under OS/2 Warp.  Setup your WWIV node/instance DOS Session
 settings before you actually install wwiv.  Decide the name
 of the directory in which you wish WWIV to be installed too.
 The default directory would be C:\WWIV.  You can make a
 directory using ANY name you wish (D:\DUH, E:\SEXY, etc).
 This should be done from a command line (DOS or OS2 session).
 I suggest using a FULL SCREEN DOS session and not a window.
 Use MD or MKDIR command.  Use all upper case letters (cap-lock
 suggested) when making directories on an HPFS partition.
 mkdir WWIV <enter> as an example.

    Now this has been done we are ready to setup a batch
 file for your WWIV BBS node.  Here is an example batch file
 for running your bbs node.  Load up an "Editor" to make this
 file.  Under OS/2 I personally use "Tedit" which is a basic
 editor like dos's edit.com, but has some enhancements.
 Do this from a "OS/2 session" window or full screen doesn't
 matter.  Make the following file(s) and save them.

 rem----[ WWIV1.BAT ]--[ for remote & local use with a modem]
 @echo off
 C:
 CD \WWIV
 SET WWIV_INSTANCE=1
 :Reload
 BBS -I1 -O -N0 -A1 %1 %2
 IF ERRORLEVEL==1 GOTO End
 IF ERRORLEVEL==0 GOTO Reload
 :End
 rem-------------[ end of file ]-------------

 rem----[ WWIV2.BAT ]--[ for local use ONLY " No Modem = -M "]
 @echo off
 C:
 CD \WWIV
 SET WWIV_INSTANCE=2
 :Reload
 BBS -I2 -M -O -N0 -A1 %1 %2
 IF ERRORLEVEL==1 GOTO End
 IF ERRORLEVEL==0 GOTO Reload
 :End
 rem-------------[ end of file ]-------------

    Copy this file to your C:\WWIV directory (or where ever
 you are going to install WWIV to).  You will also want to
 copy the icon you are going to use (IF you choose) for the
 node to the same place.  You might want to name the icon
 the same as the batch file, but with ico as the extention.
 (command line:  copy wwiv*.* C:\WWIV <enter> is an example).

    Next go to OS/2 Warp's "Program" folder.  Double click
 left mouse button.  Look for an icon called "New Folder"
 place the mouse pointer on icon & hold down the right mouse
 button.  Then drag the new folder to the desktop.  Once you
 have done this.  Place the mouse on this new folder.  Hold down
 the ALT-Key, then click the left mouse button.  This will
 allow you to rename the folder.  You can name this folder WWIV
 (This is not the same as the actual directory your bbs files
 will reside in on the hard drive).  Once you have a name you
 desire.  click the left mouse button any place on the desktop
 for your new folder's name to take effect.  Now double left
 mouse on the new folder (WWIV) on your desktop and resize it
 so you can view it as well as the open "Programs" folder.

    Now its time to make and setup your first bbs node to run
 wwiv.  You will repeat the above actions - procedures, but
 instead of dragging the "New folder" icon.  You will drag
 the icon named "New Program" into the open "WWIV" folder you
 had created earlier.

    When you drag the new program icon to the wwiv folder it
 will automatically open up the "properties" window for your
 new program.  You will be presented with five different
 "Tabs" on the "New Program - Properties"  The "Program" tab
 will have 3 fields to fill in.
                                        [Find]
 Path and file name : C:\WWIV\WWIV1.BAT
 Parameters         :
 Working directory  : C:\WWIV

    Now we click on the [Find] button and locate WWIV1.BAT file.
 You will be presented with a "Find Objects"  Here we place in
 the full information to find the file(s) quickly.
 Name           : WWIV1.bat
 Start Folder   : C:\WWIV
 [x] Search all subfolders
 [Find]  mouse click on find.  When os2 has found the specificed
 file it will give you a list of found files.  Pick the first
 highlighted file.  This will usually be the one you copied
 before you started this section.  click on the [OK] button.

    On to the "Session" tab.  You will see several different
 options.  Depending on the version of OS/2 you are using
 you can pick or check the box for "DOS full screen" or
 "DOS window".  IF you are using OS/2 Warp v4.0 check and
 use "DOS full screen" and make sure "[x] Close windows on
 exit" is checked.  Then click on "DOS properties" icon.
 "DOS Settings - Categories"  * All DOS settings *  mouse
 click [OK].  Now the fun begins.

-------------------------------------------------------------
AUDIO_ADAPTER_SHARING=REQUIRED (only IF you have a sound card)
DOS_AUTOEXEC=C:\AUTOEXEC.BAT (you can use a different filename:
                             (autoexec.bbs will discuss Later)
DOS_BACKGROUND_EXECUTION=ON
DOS_BREAK=ON
DOS_DEVICE=C:\SIO\VX00.SYS
           C:\OS2\MDOS\ANSI.SYS
DOS_FCBS=50  (place between 20 & 50)
DOS_FCBS_KEEP=16
DOS_FILES=100 (change from 20 to between 60 & 100)
DOS_HIGH=ON
DOS_LASTDRIVE=Z
DOS_RMSIZE=640
DOS_SHELL=(default)
DOS_STARTUP_DRIVE=
DOS_UMB=ON
DOS_VERSION=(default)
DPMI_DOS_API=AUTO or ENABLED  (warp3 set to AUTO)
                              (warp4 set to ENABLED)
DPMI_MEMORY_LIMIT=16
DPMI_NETWORK_BUFF_SIZE=8  (change from 1 to a minimum of 8)
                 (if you are running a peer set this to 64)
EMS_FRAME_LOCATION=AUTO
EMS_HIGH_OS_MAP_REGION=0
EMS_LOW_OS_MAP_REGION=384
EMS_MEMORY_LIMIT=0  (warp3 set to 0, warp4 set to 1024)
HW_NOSOUND=ON  (set to OFF for sounds <chat calls>)
HW_ROM_TO_RAM=ON (depending on your system memory)
HW_TIMER=ON
IDLE_SECONDS=2   (set for between 2 & 16)
IDLE_SENSITIVITY=75
INT_DURING_IO=OFF
KBD_ALTHOME_BYPASS=OFF
KBD_BUFFER_EXTEND=ON
KBD_CTRL_BYPASS=NONE
KBD_RATE_LOCK=OFF
MEM_EXCLUDE_REGIONS=
MEM_INCLUDE_REGIONS=
MOUSE_EXCLUSIVE_ACCESS=OFF
PRINT_SEPERATE_OUTPUT=ON
PRINT_TIMEOUT=3600
SESSION_PRIORITY=2  (set to between 2 & 25 depending on system)
                (will discuss more in depth later in this text)
SIO_Allow_Access_COM1=OFF
SIO_Allow_Access_COM2=ON  (actual port with modem for this node)
SIO_Allow_Access_COM3=OFF
SIO_Allow_Access_COM4=OFF
SIO_Idle_Sensitivity=32   (warp4 seems to need a setting of 100)
SIO_Mode_DTR=No Change at OPEN or CLOSE
SIO_Mode_FIFO_Load_Count=16
SIO_Mode_IDSR=Ignore DSR During Recieve
SIO_Mode_OCTS=HandShake Signal, as in RTS/CTS
SIO_Mode_ODSR=Ignore DSR During Transmit
SIO_Mode_RTS=HandShake Signal, as in RTS/CTS
SIO_Mode_XON/XOFF=No XON/XOFF flow control by SIO
SIO_Screen_Sync_Kludge=OFF
SIO_Share_Access_With_OS/2=ON
SIO_Virtualize_16550A=ON
SIO_Virtualize_COM_Ports=ON
VIDEO_8514A_XGA_IOTRAP=ON
VIDEO_FASTPASTE=ON
VIDEO_MODE_RESTRICTION=CGA  (OS2 v2.1 & Warp3 set to CGA)
                            (Warp4 set to NONE)
                      (IF you enable VGA WFC set to NONE)
VIDEO_ONDEMAND_MEMORY=ON
VIDEO_RETRACE_EMULATION=ON
VIDEO_ROM_EMULATION=ON
VIDEO_SWITCH_NOTIFICATION=OFF
VIDEO_WINDOW_REFRESH=1
XMS_HANDLES=32
XMS_MEMORY_LIMIT=1024 (warp4 set first node to 1024,)
                      (any other nodes set to 2048)
XMS_MINIMUM_HMA=0

  Save settings and go on to next "Tab"

  "Association" tab.  Add the following file types in.
   "DOS Command File" & "Executable"

  "Icon" tab.  The WWIV1.ICO should already appeared here if it
  was copied over to C:\WWIV when we made your WWIV1.BAT file.
  Look for "Tital" and you will see that "New Program" is in this
  field. Place the mouse curser at the beginning of "New Program"
  and use the "Delete" key to remove the name.  Place in the name
  of "WWIV1.BAT" and you are done with the "Icon" tab area.

  "Window" tab should be already setup with the default settings
  of " * minimize window to viewer " and
  " * display exiting window "

  Save & Close out the WWIV1.BAT - Properties screen.
  The "New Program" name should be replaced with WWIV1.bat & the
  WWIV1.ICO should replace the "DOS C:\" generic icon that was
  there before.

  AUTOEXEC.BAT (BBS):

    This is an example of "How & What" changes for making a
 custom Autoexec.bat file for your WWIV v4.30 BBS to use. This
 allows you to set special DOS setting needed for WWIV v4.30 to
 work properly under OS/2 Warp.

    A simple way to make "Autoexec.bbs" is to open up an os2
 session and type from a C:\ prompt and
 type: copy autoexec.bat autoexec.bbs <enter>
 next type: tedit autoexec.bbs <enter> and add in some of the
 following changes below, but make these changes to suit
 "Your Setup" and then save the file.
 See reference in "DOS Settings" discussed above.

 ---[ autoexec.bbs ]---

@ECHO OFF
ECHO.
PROMPT $i$p$g
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;
SET WIN3DIR=C:\OS2\MDOS\WINOS2
PATH=C:\OS2;C:\OS2\MDOS;C:\;C:\OS2\MDOS\WINOS2;C:\TCPIP\DOS\BIN;
     C:\BAT;C:\MCAFEE\OS2SCAN;
LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM
SET TMP=C:\
REM LOADHIGH DOSKEY FINDFILE=DIR /A /S /B $*
REM DOSKEY EDIT=QBASIC/EDITOR $*
REM SET DIRCMD=/A
SET TEMP=C:\OS2\MDOS\WINOS2\TEMP
SET ETC=C:\TCPIP\DOS\ETC
SET TZ=PST8PDT
SET CEXYZLOG=C:\WWIV\CEXYZ.LOG
SET DSZLOG=C:\WWIV\DSZ.LOG
C:\MCAFEE\OS2SCAN\VSHIELD.EXE /NOEXPIRE

 ---[ End of autoexec.bbs ]---

    Watch for line wraps in the above example file.  The path
 should be all one line.  If you are using your os2 system for
 other things besides running the bbs you will want to set
 different path's for various programs so they do not cause
 problems with each other.  One example would be multiple
 setup's of wwiv for testing purposes.

    Any dos program or files you need to use or want to use
 should be placed in a directory that is in the DPATH statement
 of your os2 config.sys file.  If they are not in the same
 directory you have setup wwiv v4.30 they have to be set in the
 path statement.  Placing the same directory in autoexec.bbs
 will allow wwiv v4.30 to have full use of those programs.

    Look in the basic WWIV v4.30 documetation for TZ settings
 information.  This is important for systems running the PPP
 Project files & some other software.

    The log path statements for some transfer protocal programs
 are require for them to work properly (DSZ/GSZ/CEXYZ) with WWIV.
 These should be set in your "autoexec.bbs" file.

    Now that you have setup your batch file & settings for your
 first node/instance of WWIV.  Repeat this procedure for each
 additional node of wwiv.

    With WWIV v4.30 you will need a multi-instance/node code.
 You will be required to enter this code in for more than one
 node of wwiv.  This code can be requested by visiting
 http://wss.wwiv.com/  This code is "FREE" & allows a new sysop
 to setup 2 nodes of wwiv (remote & local nodes).

 INSTALLATION:

    Download WWIV v4.30 archive.  Unzip these files into a
 temp directory to prepare for installing wwiv.  Make sure
 you have pkunzip.exe in your path statement (MPATH=) for
 DOS or in the same temp directory you have unzipped
 wwiv v4.30 files.  The installation batch file for wwiv
 REQUIRE's that pkunzip.exe be used!

    Read all document files (TXT/DOC) before actually running
 the "INSTALL.BAT" file.  Note that you should run the
 install from the same drive/partition as you intend to
 install wwiv v4.30 to.

    Open a FULL SCREEN DOS SESSION.  Run install by
 typing INSTALL C:\WWIV <enter>.   INIT.EXE will be run once
 you have started the install process.  Configure WWIV for
 your first node.  Follow the directions in WWIV430.DOC file
 to configure your new setup.

    Once you have finished running the install.bat & init has
 finished.  Quit and exit the program.  You can re-run init.exe
 any time using a dos full screen session to configure wwiv.
 Refer to WWIV430.DOC file for information regarding editing
 and modifing your wwiv.ini file.  This file is very important
 that all options have been edited for use by wwiv.  Once this
 has been done you are ready to run the bbs and setup the
 first user account.  Read wwiv430.doc file for more information
 on making the account(s).

    Now go to your desktop go to the folder WWIV and
 "double left mouse click" WWIV1.BAT.  You should now have wwiv
 up and running with a wfc screen.  To logon use the spacebar
 and create your sysop account.


#################################

  4.  You will need to install SHARE.EXE or be using some
      form of "share" via your network software if you are
      on a LAN in order to have multi-instance capability.
      It is assumed that you are using OS/2 as your
      multi-tasking software you will NOT need share.
  (see comments later in this text file regarding share.exe)


 *********************************************************
 3.10.8.2  Fossil Drivers
 *********************************************************

    WWIV v4.30 does REQUIRE a FOSSIL Driver in order to run.
 Under OS/2  the "Best" fossil driver to use is written by
 Ray Gwinn.  The fossil driver is SIO.SYS, VSIO.SYS, and
 X00.SYS.  Ray gwinn has also included VMODEM.EXE for telnet
 use under OS/2.  For more information on SIO & VMODEM
 setup read SIO430.DOC.

 ***************************************************************

 3.10.8.3  Batch files in the Multi-Instance Environment

    The batch file below shows an example of having a game
 in a different directory for each "instance".  It uses
 Trade- Wars as an example.  Whether or not the setup
 shown below is necessary depends upon the chain and how
 it is written. The example is theoretical.  I have not
 checked TradeWars to determine whether or not it requires
 such a setup. Lines beginning with REM are "remark" lines
 and are meant to help you understand what is transpiring
 in the batch file.

 PROTOCALS:

    Read "protos2.txt" for information about setting up
 different protocals such as Zmodem, HS/Link, & CEXYZ.

***********************************************************

                        F.A.Q.s - I
  ķ
   Frequently Asked Questions  
  Ľ

 Q:   How do I check for INSTANCE number in a batch file?


 Q: In a batch file, how do I check for the instance
    number, for executing different command lines and so
    forth for different instances.

 A: Do a check for %WWIV_INSTANCE% in the batch file. The
    following is a simple example:

 @echo off
 if %WWIV_INSTANCE%==1 goto INST1
 if %WWIV_INSTANCE%==2 goto INST2
 if %WWIV_INSTANCE%==3 goto INST3

 :INST1
 INST 1 stuff goes here.
 goto DONE

 :INST2
 INST 2 stuff here
 goto DONE

 :INST3
 INST 3 stuff here
 goto DONE

 :DONE

 ############################################################################

 Sam's Faqs:

Q:  Do you have any advice regarding the configuration of
OS/2 to reduce problems with DSZ?

A: I have heard many people talk about OS/2 and how slow it
can be durring transfers (mainly Zmodem uploads) so I am
posting my CONFIG.SYS file that I use to run my OS/2
system.  I have a 486-66/DX2 and I use to have the same
problem with Zmodem.  Now I can have someone upload in
Zmodem on my system and it takes only 25% CPU load in
Zmodem (newest version).  You'll notice below that I have
a 2048k CACHE which is suggested by IBM for maximum
performance.  I have also included a 4096k RAMDISK of
which I have the following dirs \DLOADS \TEMP1-8 \BATCH1-8
for performance reasons they are best in the RAMDISK.  I
use to have a 16MB SWAPFILE that would increment in 4MB
intervals but now have it set to a 20MB SWAPFILE that will
increment in 2MB intervals and feel that works best. Keep
in mind that if your SWAPFILE is below 14MB you will suffer
performance wise because OS/2 itself uses 14MB (IBM told
me 16MB is suggested) but like I said the 20MB works best
for me and it is kept on the hard drive and is not RAM so
if you have the drive space USE IT.

You'll also notice below that I have broken the file down
into the 5 categories of an OS/2 CONFIG.SYS to make for
easy modifications. Be aware that I load all devices with
the DEVICEHIGH command and highly suggest it.

I am registered for 8 WWIV INSTANCES and have had them all
up and running with no problems. I use to get a memory
error, some of you may have seen the DosRaiseHigh error,
but since my modifications to the CONFIG.SYS it has
stopped and that problem is no more.

The reason for all the modifications to the CONFIG.SYS file
is due to me getting ready to move into my new house and I
will be installing multiple lines for the BBS.  As it
were, when someone would log onto my BBS and upload in
Zmodem it would register as a CPU Load of 100% which is not
good for just one session because when logging onto
another session it would not perform well at all.  Now,
with my CONFIG.SYS file modifications I am ready to add
several lines to the BBS.  When someone now is downloading
in Zmodem (in my opinion the most processor intensive
function a user can do) it registers as only using a CPU
Load of 25% and I never get transfer errors anymore. Hell,
and this is all on a dinky 486-66/DX2... if only I had a
P-100 I could run 8 sessions all downloading in Zmodem
with no system slow-down.

OS/2 WARP & WWIV both RULE!  Of course if you do not know
what you are doing I can see that you may not like OS/2
WARP and think it is slow, but as long as you read the
books that come with the software (Duh!) it is simple to
get your system to run multiple instances FAST with no
slow down.

I am very confident of the below CONFIG.SYS and feel that
it is the best you could possibly use on your OS/2 system.
Be sure to make the necessary modifcations to the CACHE
and RAMDISK to ensure you do not eat all your memory
because this CONFIG.SYS is from my system, not yours.
Note, in the configuration below, long lines have been
broken to fit this screen size.  Lines beginning with a
are continued from the preceeding line.

REM *********************************************************
REM * OS/2 SYSTEM VARIABLES - OS/2 v2.1 *********************
REM *********************************************************

PROTSHELL=C:\OS2\PMSHELL.EXE
PRIORITY_DISK_IO=NO
FILES=255
BUFFERS=100
IOPL=NO
DISKCACHE=2048,LW,32,AC:C
MAXWAIT=1
MEMMAN=SWAP,PROTECT
SWAPPATH=C:\OS2\SYSTEM 2048 20480
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS

REM IFS=C:\OS2\HPFS.IFS /CACHE:64 /CRECL:4

REM ******************************************************
REM * ENVIRONMENT VARIABLES                               *
REM *******************************************************

SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=TASKLIST,FOLDERS
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET COMSPEC=C:\OS2\CMD.EXE
LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\MMOS2\DLL;
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;
         C:\OS2\APPS;C:\MMOS2;C:\SIO;C:\WINDOWS

SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;
          C:\OS2\MDOS;C:\OS2\APPS;C:\MMOS2;C:\MMOS2\INSTALL;C:\WINDOWS

SET PROMPT=$i[$p]
SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;C:\MMOS2\HELP;
SET GLOSSARY=C:\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
SET BOOKSHELF=C:\OS2\BOOK;C:\MMOS2;
SET EPMPATH=C:\OS2\APPS;
SET KEYS=ON
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;

SET SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;C:\OS2\ETC\WPDSERV.IR
SET SOMDDIR=C:\OS2\ETC\DSOM

REM *******************************************************
REM * DOS PARAMETERS                                      *
REM *******************************************************

PROTECTONLY=NO
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS /P
FCBS=16,8
RMSIZE=640
DOS=HIGH,UMB
DEVICEHIGH=C:\OS2\MDOS\HIMEM.SYS
DEVICEHIGH=C:\OS2\MDOS\VEMM.SYS
DEVICEHIGH=C:\OS2\MDOS\VXMS.SYS /UMB
DEVICEHIGH=C:\OS2\MDOS\VDPMI.SYS
DEVICEHIGH=C:\OS2\MDOS\VDPX.SYS
DEVICEHIGH=C:\OS2\MDOS\VWIN.SYS
DEVICEHIGH=C:\OS2\MDOS\VW32S.SYS
DEVICEHIGH=C:\OS2\MDOS\VSVGA.SYS

DEVICEHIGH=C:\MMOS2\SSMDD.SYS
DEVICEHIGH=C:\MMOS2\R0STUB.SYS
SET MMBASE=C:\MMOS2;
SET DSPPATH=C:\MMOS2\DSP;
SET NCDEBUG=4000

REM *******************************************************
REM * OS/2 DEVICE DRIVERS                                 *
REM *******************************************************

BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM2FLPY.ADD
BASEDEV=XDFLOPPY.FLT
BASEDEV=OS2DASD.DMD
BASEDEV=IBMKBD.SYS
BASEDEV=OS2SCSI.DMD
BASEDEV=AHA154X.ADD
DEVICEHIGH=C:\OS2\BOOT\DOS.SYS
DEVICEHIGH=C:\OS2\BOOT\MOUSE.SYS
DEVICEHIGH=C:\OS2\BOOT\PMDD.SYS
DEVICEHIGH=C:\OS2\BOOT\POINTDD.SYS
DEVICEHIGH=C:\OS2\BOOT\TESTCFG.SYS
DEVICEHIGH=C:\OS2\BOOT\VDISK.SYS 4096
DEVICEHIGH=C:\OS2\MDOS\ANSI.SYS
DEVICEHIGH=C:\OS2\MDOS\VMOUSE.SYS
DEVICEHIGH=C:\SIO\SIO.SYS (COM1,03F8,IRQ4)
DEVICEHIGH=C:\SIO\VSIO.SYS
DEVICEHIGH=C:\SIO\VX00.SYS

REM *******************************************************
REM * VIDEO PARAMETERS                                    *
REM *******************************************************

CODEPAGE=437,850
DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
SET VIDEO_DEVICES=VIO_VGA
DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP
SET VIO_VGA=DEVICE(BVHVGA)

 ***************************************************************

                       ͻ
                        References 
                       ͼ
 ***************************************************************
 Products created by other authors have been mentioned
 throughout this documentation.  These authors or companies
 may be contacted as follows:

 PRODUCT:  DSZ, GSZ, Zmodem
 Author:   Chuck Forsberg
           Omen Technologies, Inc.
           P.O. Box 4681
           Portland, OR 97208

 PRODUCT:  HS-LINK
 Author:   Samuel H. Smith
           The Tool Shop
           P.O. Box 4808
           Panorama City, CA 91412-4808

 PRODUCT:  MpT Protocal
 Author:   Matthew Thomas
           P.O. ox 4694
           Racine, WI 53404

 PRODUCT:  ARJ Archiver
 Author:   Robert K. Jung
           2606 Village Road West
           Norwood, MA 02062

 PRODUCT:  TheDraw
 Author:   TheSoft Programming Services
           1929 Whitecliff Court
           Walnut Creek, CA 94596

 PRODUCT:  QEDIT
 Author:   SemWare
           4343 Shallowford Rd.
           Suite C-3
           Marietta, GA 50062-5003

 PRODUCT:  LIST utility
 Author:   Vernon D. Buerg
           139 White Oak Circle
           Petaluma, CA 94952

 PRODUCT:  Pkzip, Pkunzip
 Author:   PKWARE, INC.
           7545 N. Port Washington Rd.
           Glendale, WI 53217-3422

 PRODUCT:  SIO, Vmodem
 Author:   Ray GWINN, INC.
           7545 N. Port Washington Rd.
           Glendale, WI 53217-3422

***********************************************************

Comments:

DOS_BACKGROUND_EXECUTION is very important.
    It makes your BBS run while not on screen.

I turned on HW_NOSOUND because I hate the sound the chat call makes.

HW_TIMER and HW_ROM_TO_RAM apparently help speed up the BBS.  Got these from
     tips, too.

Many will say that IDLE_SECONDS and IDLE_SENSITIVITY should be used to tweak
your system.  This may be true for 4.23, but in 4.24 they actually slowed
things down, so I put them back to their defaults.

INT_DURING_IO can cause some pretty nasty problems.  I do not suggest
enabling it.

PRINT_TIMEOUT -- Don't fool with this if you have a printer.  My BBS machine
doesn't.

SESSION_PRIORITY -- By making it 2, you make the BBS a little more important
than the rest of OS/2's tasks, making it run better.



Once you get your BBS running in OS/2, you'll realize that some things just
don't work as well as they did in DOS.  For instance, if you upload using
Zmodem, it'll start slowing down your computer.  This is a fact of life.
However, using GSZ instead of DSZ sped up my machine some.

You may also notice that using WWIVedit slows down the machine, and
occasionally crashes it.  My best suggestion is to simply disable WWIVedit,
and use FEdit v2.07 (FEDIT207.ZIP)

NOTE: Try and Use (WEDIT25G.ZIP) = WWIVEDIT.EXE Modified by -Goose-

Some of your doors may not run in OS/2.  This should be a very small number.
If they don't, you may be forced to remove them.

Are your doors running too slowly over the modem?  Set them up to use fossil
drivers.  If you're using a DOS fossil driver, get rid of it and use SIO's
instead.  It's far better.

Usurper seems to have some problems in OS/2.  This, too, is a fact of life.
which will enable desqview faking.  At the end of the batch file, be VERY
sure to disable it!  WWIV does not function properly when it is faking
desqview.


=====================================================================
Frequently Asked Questions concerning Chains:
=====================================================================

    The designation of chains originated in Turbo Pascal
 versions of WWIV when the BBS literally "chained" to the
 program.  Although WWIV no longer operates in that
 fashion and is no longer written in Pascal, the CHAINEDIT
 terminology has remained.

    Not all files can be run as external programs from
 WWIV. Only those files that do all I/O through DOS calls
 can be run. This means that Wordstar, WordPerfect, the
 Norton Utilities, and most other graphics programs can
 NOT be run from WWIV.

    Games can be characterized as WWIV games if one of two
 conditions occur.  First, if the game is written to
 specifically make use of the drop file known as
 CHAIN.TXT. By drop file, is meant a file that is created
 by the BBS software either at the time of logon or when a
 door (chain) is entered.  This file typically contains
 information about the user and/or the system.  A
 commented CHAIN.TXT, written by MrBill is included later
 in this document.  Some games are written to make
 specific use of the information contained in the
 CHAIN.TXT file.  These games, although perhaps not
 specifically written for WWIV alone, are discussed in the
 category of WWIV games because they have been written to
 work with WWIV.

    The second condition that causes a game to be known as
 a WWIV game is that it makes use of the special dos color
 codes contained in the WWIV software.  These games are
 characterize by use of the DOS color commands
 (pseudo-ansi) found in WWIV.  These colors are discussed
 in the DEFAULT section of the software and are
 configurable by the user. WWIV will interpret a "heart"
 symbol as a color command when it is followed by a
 number.  Because WWIV is one of the few BBS programs that
 can use these color commands, games containing them are
 almost always written for the exclusive use of WWIV
 boards.  These games are also most often characterized as
 games where the CHAINEDIT option of USE DOS INTERRUPTS
 should be left at the default setting of Y.

     Games that may be considered as being written for
 other software are those which do not use CHAIN.TXT and
 which instead use one of the drop files of another bbs
 software.  These usually include games which use
 DORINFO1.DEF (RBBS, QBBS, REMOTE ACCESS), games which use
 PcBOARD.SYS (PcBoard versions 12 and 14), games which use
 DOOR.SYS (Wildcat 3.0, GAP, and PcBoard 14.5+), and games
 which use CALLINFO.BBS (pre-version 3.0 of Wildcat).
 These games can often be made to work with WWIV provided
 that a 'converter' is also used.  The use of converters
 and so forth will be discussed later.


 1.  Setting up WWIV games.  Most WWIV games have relatively good
 documentation and therefore setting them up and getting them to work is
 usually very straight forward.  However, if there is no documentation
 and/or the documentation seems insufficient, then there are a number of
 things that you can experiment with by trial and error to see if you
 can get the game to run.

    1.1 Placement of Game Files.  If the game does not tell you where to
    place the files, you can try each of the following setups to see if
    one of them causes the game to work:

        a. In its own directory.  i.e. C:\WWIV\MWAR

        b. In a directory called CHAINS (especially for older games)
        i.e. C:\WWIV\CHAINS

        c. In a directory off of CHAINS (also popular place for older
        WWIV games) i.e.  C:\WWIV\CHAINS\MWAR

        d.  In the main BBS directory. i.e. C:\WWIV

    1.2  Relationship to CHAIN.TXT. If you get a 'parameter file not
    found' or other type of error message from the game, then it may be
    that it is not finding CHAIN.TXT correctly.  You may try
    incorporating a batch file and copying the CHAIN.TXT to the
    directory where the game is located.

     Use  DOS commands as follows:

     copy con MWAR.BAT
     @echo off
     copy chain.txt c:\wwiv\chains\mwar
     cd chains\mwar
     mwar
     cd\wwiv

     then press CTRL Z or F6 (function key 6) to save the
     batch file.

    1.3  DOS Interrupts. Some games written especially for WWIV will let
    the BBS handle the DOS INTERRUPTS.  This is especially true of many
    games written in PASCAL for use with WWIV.  A sign that sometimes
    the DOS interrupt option is set incorrectly is when the game echos
    double characters.  If the game is viewable from local mode but not
    from the remote mode, then you may want to experiment with setting
    the DOS INTERRUPTS option differently.

    1.4  SHRINK Option. Many games do not necessitate the BBS to shrink
    out in order to run them; however, if you experience a "lock up" or
    freezing of the computer when you try to run the game, this may be
    an indication that there is insufficient memory available and that
    you should shrink the BBS. It may be helpful to set the BBS to
    shrink out if the game is large (ie the file size is big).

2.  Setting up Non-WWIV Games. Because these games are not specifically
made for WWIV, the first step is to determine what software they
support.  WWIV creates all major drop files required for most online
games.  Below is a list of BBS packages and the drop file they use.

           GAP             -> Door.Sys
           Genesis Deluxe  -> CallInfo.BBS
           GT PowerComm    -> GTUser.BBS
           Osiris#         -> ExtInfo#.QBS
           PCBoard v12xx   -> PCBoard.Sys
                              PCBoard.Dat
                                Users
           PCBoard v14xx   -> PCBoard.Sys
                              PCBoard.Dat
                                Users
           QuickBBS        -> DorInfo1.Def
           RBBS#           -> DorInfo#.Def
           WildCat         -> CallInfo.BBS
           Remote Access   -> Dorinfo1.Def
           SpitFire
           WWIV            -> Chain.Txt

3.  Fossil Drivers. WWIV now requires a fossil driver in order to run.
Some games expect a fossil to be present even though that is not
mentioned in the documentation of the game.  This is particularly true
for games written for QBBS, RBBS, and OPUS.  Games which DO NOT require
a fossil driver should work fine even though the driver is loaded.
The better known fossil drivers are X00 and BNU.  Many WWIV system
operators report excellent results from X00.

    3.1 Batchfiles in the Multi-Instance Environment. The batchfile
    below shows an example of having a game in a different directory
    for each "instance".  It uses Trade Wars as an example.  Whether or
    not the setup shown below is necessary depends upon the chain and
    how it is written. The example is theoretical.  Current versions of
    TradeWars have not been checked to determine whether or not it
    requires such a setup. Lines beginning with REM are "remark" lines
    and are meant to help you understand what is transpiring in the batch
    file.

         @Echo Off

         REM --> Check to see if instance 3
         if %WWIV_INSTANCE%==3 goto Inst3

         REM --> Check to see if instance 2
         if %WWIV_INSTANCE%==2 goto Inst2

         REM --> Example only has three instances; got here, must be
         REM --> instance 1
         goto Inst1

         REM --> Subroutine for Instance 1
         :Inst1
         Copy C:\WWIV\CHAIN.TXT C:\WWIV\DOORS\TW\1
         C:
         Cd\WWIV\DOORS\TW\1
         TW2002
         Goto Done

         REM --> Subroutine for Instance 2
         :Inst2
         Copy C:\WWIV\CHAIN.002 C:\WWIV\DOORS\TW\2\CHAIN.TXT
         C:
         Cd\WWIV\DOORS\TW\2
         TW2002
         Goto Done

         REM --> Subroutine for Instance 3
         :Inst3
         Copy C:\WWIV\CHAIN.003 C:\WWIV\DOORS\TW\3\CHAIN.TXT
         C:
         Cd\WWIV\DOORS\TW\3
         TW2002
         Goto Done

         REM --> Cleanup area, exits batch file in proper dir, or
         REM --> whatever necessary.
         :Done
         C:
         Cd\WWIV

4.  Other Comments regarding CHAINS. Some of the games written for WWIV
in Pascal are presented in uncompiled form by the authors.  This is
often done so that the pascal code may be altered or customized for your
board.  Usually these authors have made use of something called a
COMMON.PAS file which interfaces the game with WWIV.  If a particular
game has not been compiled, you must first compile it with the
appropriate version of the Turbo Pascal compiler using the appropriate
version of COMMON.PAS.  Most of the versions of COMMON.PAS are available
for downloading on the WWIV Support Boards.

    4.1  BRUNxx. Some games written in QuickBASIC have been compiled to
    utilize an intermediate program called BRUN (Basic RUN time module).
    Such games require the BRUN module specific to the compiler. Current
    versions of BRUN are BRUN20, BRUN30, BRUN40, and BRUN45.  Again,
    these programs are available on most WWIV Support Boards.  The
    BRUNxx file may be placed in your path and used by all programs that
    require it.  One advantage of the Basic RUN time compilers is that
    the resulting EXE's require significantly less space (approximately
    35k less per program).

    4.2  Commented Chain.txt.  CHAIN.TXT Definition File by MrBill

    Note:  Some of the original information about Mr. Bill and MrBill's
    Abode has been shortened to accomodate the format of these docs.

 -----------CHAIN.TXT-----------------------------------
 1                  User number
 MRBILL             User alias
 Bill               User real name
                    User callsign (HAM radio)
 21                 User age
 M                  User sex
   16097.00         User gold
 05/19/89           User last logon date
 80                 User colums
 25                 User width
 255                User security level (0-255)
 1                  1 if Co-SysOp, 0 if not
 1                  1 if SysOp, 0 if not
 1                  1 if ANSI, 0 if not
 0                  1 if at remote, 0 if local console
    2225.78         User number of seconds left till logoff
 F:\WWIV\GFILES\    System GFILES directory (gen. txt files)
 F:\WWIV\DATA\      System DATA directory
 890519.LOG         System log of the day
 2400               User baud rate
 2                  System com port
 MrBill's Abode     System name
 MrBill             System SysOp
 83680              Time user logged on/# of secs. from midn
 554                User number of seconds on system so far
 5050               User number of uploaded k
 22                 User number of uploads
 42                 User amount of downloaded k
 1                  User number of downloads
 8N1                User parity
 2400               Com port baud rate
 7400               WWIVnet node number
=====================================================================


=======================================================================
Appendix D (Common Protocol Settings)
=======================================================================

    Setting up different protocols for WWIV v4.30 file & network
transfers.  This section will help a new sysop to get up and running
using different file transfer protocol programs.  These programs are
EXTERNAL to WWIV and not part of the archieve.  These are seperate
programs used in addition to WWIV.

        NOTE:  READ ALL DOCUMENT'S BEFORE ACTUALLY SETTING UP WWIV.
               This will save some headaches and time in the long run.

    The following information is presented for information and as a
guideline for helping new sysops in running WWIV v4.30.  First item
required before you can setup WWIV v4.30 will be that a FOSSIL Driver be
setup and installed on the computer system you are setting WWIV up on.
Depending on the Operating System you are running the fossil driver(s)
required may differ.  If you are using any flavor of dos a DOS Fossil
driver will be required such as BNU or X00 to run the bbs.  IF you are
running Win9x/NT a different fossil drive(s) will be required.  IF you
are running any flavor of OS/2 SIO by Ray Gwinn will be required to run.
Second Item required will be a protocol or transfer software for upload/
download of files in a tranfers section of the bbs (IF the sysop
chooses).  There are different "flavors" of many programs.  It is
suggested that you use DSZ/GSZ from Omen, Inc. (www.omen.com).  They
have different versions available for downloads.  DSZ.COM/EXE versions
as well as a fossil version (FDSZ.EXE) available.  There are other
programs that do Zmodem transfer such as CEXYZ & PDRIVE.

   This document should answer most questions.  If it doesn't and you
have access to the internet or a local WWIV System.  You can ask there
or in alt.bbs.wwiv newsgroup for help and/or questions.  Help is always
available in the newsgroup and at http://wss.wwiv.com/

     NOTE: all of the versions & releases I have had in the last 5 years
all have worked with NON-Standard comport settings and such.  I have a
personal preferences for the *.EXE copies of DSZ & GSZ over the *.COM
releases of them. They all worked just fine under DOS for me, but under
OS/2 Warp the DSZ/GSZ.EXE versions where more reliable.  The fossil
version seems to work better with MS-Windows-9x/NT.

******************************************************************************

     OK:  Here is some added information that SHOULD be used when
setting up the protocols in INIT.EXE for use by the bbs.  I removed the
internal command lines for X-Modem, Y-Modem in INIT and replaced it with
DSZ/GSZ instead.

     Now everything is usually published in the format that you are
only using 1 modem and it is on com2 on standard settings.  The lines
will all be using the " port %2 speed " etc.  For those that are using
a non-standard modem setting, but still are only using 1 modem would use
the following.

" portx 3,3e8,5 speed " etc.

This translates to COM-3, Address 3E8, IRQ-5.  If you are using MORE
than 1 modem and one of the modems is setup on a NON-Standard comport
setting use the following:

" portx %B,%I speed " etc.

     The next thing you will run into is if you are setting up more
than one modem for use with WWIV.  You will HAVE to use the portx %B,%I
speed to enable use of your modems on each instance of the bbs.  When you
setup the protocols for your bbs.  Use the following format and pay
attention to UPPER & lower CASE letters.  Example below:

 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 sz @%3
 C:\WWIV\gsz.exe port %2 speed %1 estimate 0 %4 rz -mrr %3

     IF you have all of your protocol programs within your main BBS
directory then make sure they are in the path in init (Like above).
If you have them in say " D:\UTIL\SYSTEM\ <?>."   You will place in
INIT the following:

Zmodem w/MobyTurbo & Crash Recovery (#2)
-----------------------------------------
 D:\UTIL\SYSTEM\dsz.exe portx %B,%I speed %1 estimate 0 %4 rz -mrr %3
 D:\UTIL\SYSTEM\dsz.exe portx %B,%I speed %1 estimate 0 %4 sz %3
 D:\UTIL\SYSTEM\dsz.exe portx %B,%I speed %1 estimate 0 %4 restrict rz
 D:\UTIL\SYSTEM\dsz.exe portx %B,%I speed %1 estimate 0 %4 sz @%3
-----------------------------------------------------------------------------

     Some of the following are not shown with the full path so add the
full path to them when you do install/set them up.

X-Modem
-------
 C:\WWIV\dsz.com portx %B,%I speed %1 est 0 %4 rx %3
 C:\WWIV\dsz.com portx %B,%I speed %1 est 0 %4 sx %3

Xmodem 1-K (Option 1)
---------------------
 C:\WWIV\dsz.com portx %B,%I speed %1 estimate 0 %4 rx -k %3
 C:\WWIV\dsz.com portx %B,%I speed %1 estimate 0 %4 sx -k %3

Xmodem 1K-G (Option 1)
----------------------
 C:\WWIV\dsz.com portx %B,%I speed %1 estimate 0 %4 rx -kg %3
 C:\WWIV\dsz.com portx %B,%I speed %1 estimate 0 %4 sx -kg %3

Ymodem-g (Option 1)
-------------------
 C:\WWIV\dsz portx %B,%I speed %1 estimate 0 %4 rb -g %3
 C:\WWIV\dsz portx %B,%I speed %1 estimate 0 %4 sb %3
 C:\WWIV\dsz portx %B,%I speed %1 estimate 0 %4 restrict rb -g
 C:\WWIV\dsz portx %B,%I speed %1 estimate 0 %4 sb @%3

True Ymodem
----------------------
 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 rb %3
 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 sb %3
 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 restrict rb
 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 sb @%3

Regular Zmodem (#1)
-------------------------
 C:\WWIV\dsz.exe port %2 speed %1 est 0 %4 rz %3
 C:\WWIV\dsz.exe port %2 speed %1 est 0 %4 sz -r %3
 C:\WWIV\dsz.exe port %2 speed %1 est 0 %4 restrict rz %3
 C:\WWIV\dsz.exe port %2 speed %1 est 0 %4 sz @%3

Zmodem w/MobyTurbo & Crash Recovery (#2)
-----------------------------------------
 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 rz -mrr %3
 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 sz %3
 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 restrict rz
 C:\WWIV\dsz.exe port %2 speed %1 estimate 0 %4 sz @%3

 GSZ  (-mrr for mobyturbo and crash recovery) (#2)
 -------------------------------------------------------
 C:\WWIV\gsz.exe port %2 speed %1 estimate 0 %4 rz -mrr %3
 C:\WWIV\gsz.exe port %2 speed %1 estimate 0 %4 sz -r %3
 C:\WWIV\gsz.exe port %2 speed %1 estimate 0 %4 restrict rz -mrr %3
 C:\WWIV\gsz.exe port %2 speed %1 estimate 0 %4 sz @%3

 GSZ  (Your settings)                          (#1)
 -------------------------------------------------------
 C:\WWIV\gsz.exe port %2 speed %1 ha no est 0 %4 rz -p %3
 C:\WWIV\gsz.exe port %2 speed %1 ha no est 0 %4 sz -r %3
 C:\WWIV\gsz.exe port %2 speed %1 est 0 %4 restrict ha no rz %3
 C:\WWIV\gsz.exe port %2 speed %1 est 0 %4 ha no sz -s @%3


 3.15.1.8 SZmodem

 Description          : SZMODEM (Super Zmodem) v1.41
 (szmodem.exe)
 Receive command line : szmodem port %2 speed %1 rz %3
 Send command line    : szmodem port %2 speed %1 sz %3
 Xfer OK code         : 0

   SZMODEM (Super ZMODEM) is fully compatible with DSZ and
 other versions of ZMODEM, check this program out because
 it's very nice! This is what my SZMODEM.CFG file looks
 like:

 SZMODEM Configuration:

  1. Default Com parameters........ COM1:38400,N,8,1
  3. BBS Dorinfo processing........ OFF
  4. Input buffer size............. 6144 bytes
  5. Output buffer size............ 6144 bytes
  6. SZPath........................ (current)
  7. Delaytime..................... 2 seconds
  8. SZTurbo....................... Enabled
  9. Snow checking................. Off
 10. Ega/Vga Display............... Off
 11. SZMODEM.LOG log file.......... On
 12. Allow remote sysop page....... Yes
 13. DORINFOx.DEF path............. (current)
 14. Handshaking options........... CTS/RTS (Hard)
 15. Locked Baud Rate.............. Not Locked

 Enter number to change [A=Abort,S=Save,D=Defaults] ?

 notes:

 If you're not running a high speed modem, then it's
 obvious that you'll want to change the default com
 parameters, or if you're using com 2. If you're NOT
 running your bbs under DesqView or Windows... then you
 mightwant to turn the hi-rez EGA/VGA display on. If you
 don't want users to page you, set the allow remote sysop
 page to No. If you're not running a high speed modem, set
 the handshaking to NONE or Soft, but definitely NOT hard.
 If you're running an OLD HST (9600) or other high speed
 modems that to to get the better cps rates you have to
 lock the com port - do it. With the newer USR line you
 don't need it locked unless the user is using a form of
 compression (V.42bis/MNP/LAPM)...

***********************************************************

Super Zmodem (Option 1)
-----------------------
 C:\WWIV\szmodem.exe port %2 speed %1 /SZTurbo /HARD rz %3
 C:\WWIV\szmodem.exe port %2 speed %1 /SZTurbo /HARD sz %3

Super Zmodem 2.0 (Option 2)
---------------------------
 C:\WWIV\SZMODEM.EXE port %2 speed %1 /SZTurbo /HARD rz %3
 C:\WWIV\SZMODEM.EXE port %2 speed %1 /SZTurbo /HARD sz %3
 C:\WWIV\SZMODEM.EXE port %2 speed %1 /SZTurbo /HARD rz @%5
 C:\WWIV\SZMODEM.EXE port %2 speed %1 /SZTurbo /HARD sz @%3

Super Zmodem 2.0 (Option 3)
---------------------------
 C:\WWIV\SZMODEM.EXE portx %B,%I speed %1 /SZTurbo /HARD rz %3
 C:\WWIV\SZMODEM.EXE portx %B,%I speed %1 /SZTurbo /HARD sz %3
 C:\WWIV\SZMODEM.EXE portx %B,%I speed %1 /SZTurbo /HARD rz @%5
 C:\WWIV\SZMODEM.EXE portx %B,%I speed %1 /SZTurbo /HARD sz @%3


 3.15.1.2  HS-LINK

    HS-Link is written by Sam Smith and also works on many
 different bulletin board systems including WWIV.  HS-Link
 is capable of operating as a bi-directional protocol.
 The setup used at The Dragon's Den is:

 Description          : HSLINK Bi-Directional Protocol
 Xfer OK code         : 0
 Require MNP/LAPM     : N
 Receive command line:
 hslink -p%2 -e%4 -nu%3
 Send command line:
 hslink -p%2 -e%4 %3
 Receive batch command line:
 hslink -p%2 -e%4 -nu%3
 Send batch command line:
 hslink -p%2 -e%4 -nu@%3
 Bi-directional transfer command line:
 hslink -p%2 -e%4 -@%3

 Because HS-Link is also supported by WWIV networking
 software, you are encouraged to consult the appendices to
 WWIVNET.DOC which show the best settings for using
 HS-LINK in the WWIV networking environment.

HS/Link (Option 1)
------------------
 C:\WWIV\HSLINK.EXE -P%2 -HS -U%3 -E%4
 C:\WWIV\HSLINK.EXE -P%2 -HS -NU %3 -E%4
 C:\WWIV\HSLINK.EXE -P%2 -HS -U%5 -E%4
 C:\WWIV\HSLINK.EXE -P%2 -HS -NU -E%4 @%3
 C:\WWIV\HSLINK.EXE -P%2 -HS -U%5 -E%4 @%3

HS/Link (Option 2 - v1.13 Beta Oct.4 1992)
------------------------------------------
 HSLINK -@C:\WWIV\HSLEACH.CFG -p%2 -e%4 -u%3
 HSLINK -@C:\WWIV\HSLEACH.CFG -p%2 -e%4 -nu %3
 HSLINK -@C:\WWIV\HSLEACH.CFG -p%2 -e%4 -u%3
 HSLINK -@C:\WWIV\HSLEACH.CFG -p%2 -e%4 -nu @%3
 HSLINK -@C:\WWIV\HSLEACH.CFG -p%2 -e%4 -@ @%3



CE-XYZ (this is NOT specific to the OS/2 version)
-------------------------------------------------
 C:\WWIV\cexyz.exe /T3 /P%2 /L%1 /B%4 /Rz %3
 C:\WWIV\cexyz.exe /T3 /P%2 /L%1 /B%4 /Sz %3
 C:\WWIV\cexyz.exe /T3 /P%2 /L%1 /B%4 /Rz @%5
 C:\WWIV\cexyz.exe /T3 /P%2 /L%1 /B%4 /Sz @%3
 -------------------------------------

    Also, if you have non-standard COM ports, you should either use a
FOSSIL driver or, if you're running OS/2 with SIO, use the VX00.SYS
driver in your BBS's DOS session and use the following command lines
to use CE-XYZ in FOSSIL mode (cexyz.exe = dos version, cexyz2.exe =
OS/2 version).
 -------------------------------------
 C:\WWIV\cexyz2.exe /UFos /T3 /P%2 /L%1 /B%4 /Rz %3
 C:\WWIV\cexyz2.exe /UFos /T3 /P%2 /L%1 /B%4 /Sz %3
 C:\WWIV\cexyz2.exe /UFos /T3 /P%2 /L%1 /B%4 /Rz @%5
 C:\WWIV\cexyz2.exe /UFos /T3 /P%2 /L%1 /B%4 /Sz @%3
 -------------------------------------
 For ZedZap (8k Zmodem variant), use the same lines, but replace /Rz
 with /Rzap and /Sz with /Szap.

==============================================================================

HS/Link (Option 1)
------------------
 HSLINK -P%2 -HS -U%3 -E%4
 HSLINK -P%2 -HS -NU %3 -E%4
 HSLINK -P%2 -HS -U%5 -E%4
 HSLINK -P%2 -HS -NU -E%4 @%3
 HSLINK -P%2 -HS -U%5 -E%4 @%3

HS/Link (Option 2 - v1.13 Beta Oct.4 1992)
------------------------------------------
 HSLINK -@_:\WWIV\HSLEACH.CFG -p%2 -e%4 -u%3
 HSLINK -@_:\WWIV\HSLEACH.CFG -p%2 -e%4 -nu %3
 HSLINK -@_:\WWIV\HSLEACH.CFG -p%2 -e%4 -u%3
 HSLINK -@_:\WWIV\HSLEACH.CFG -p%2 -e%4 -nu @%3
 HSLINK -@_:\WWIV\HSLEACH.CFG -p%2 -e%4 -@ @%3

 [NOTE: Replace the "_" with the Drive/Partition letter of your BBS]
 [" HSLINK -@C:\WWIV\* " as an Example ]

HS/Link (Option 3)
------------------
 hslink -p%2 -u%3
 hslink -p%2 -u%1 sendfile %3
 hslink -p%2 -u%3
 hslink -p%2 -e%1 sendfile @%3
 hslink -p%2 -e%4 -HS @%3

HS/Link (Option 4)
------------------
 [Multi-Node, NON-Standard COMs from Random's Post. I haven't tryed
 This One].

 hslink ..........Was Not in Post.........
 hslink ..........Was Not in Post.........
 hslink -PB$%B -PI%I -I4 -e%4 -@
 hslink -PB$%B -PI%I -I4 -e%4 -@ -nu @%3
 hslink -PB$%B -PI%I -I4 -e%4 -@ @%3
------------------------------------------------------------------------------

 ***************************************************************
                       ͻ
                        References 
                       ͼ
 ***************************************************************
 Products created by other authors have been mentioned
 throughout this documentation.  These authors or companies
 may be contacted as follows:

 PRODUCT:  DSZ, GSZ, Zmodem
 Author:   Chuck Forsberg
           Omen Technologies, Inc.
           P.O. Box 4681
           Portland, OR 97208

 PRODUCT:  HS-LINK
 Author:   Samuel H. Smith
           The Tool Shop
           P.O. Box 4808
           Panorama City, CA 91412-4808

 PRODUCT:  CE-XYZ
 Author:   George Hatchew
           Cutting Edge Computing
           PO Box 90476
           Burton, MI 48509

 PRODUCT:  SZMODEM
 Author:   Scott M. Baker
           6431 Tierra Catalina #48
           Tucson, AZ 85718

 PRODUCT:  PDrive
 Author:   Larry L. Athey
           BBS Utiliteez Software

 PRODUCT:  SIO, Vmodem
 Author:   Ray GWINN, INC.
           7545 N. Port Washington Rd.
           Glendale, WI 53217-3422

***********************************************************


=======================================================================
Appendix E (Source Code)
=======================================================================

For your reference, here is a copy of the Source Code End User License
Agreement.

1. END-USER LICENSE AGREEMENT

    1.1 GENERAL.  READ CAREFULLY: This End-User License Agreement
    (EULA) is a legal and binding agreement between you and WWIV
    Software Services, LLC (WSS) and applies to all WSS products
    distributed with source code.   For the purposes of this
    document, SOFTWARE refers to and includes all software, source
    code and documentation contained in registered distribution
    archives as provided by WSS.

    IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS EULA,
    DO NOT DECOMPRESS  THE DISTRIBUTION OR  SOURCE CODE  ARCHIVE.

    WSS prosecutes violators of this license agreement to the fullest
    extent of both federal, state, civil and criminal law.

    1.2 SOFTWARE LICENSE.

        YOU ARE BOUND BY, AND INDICATE YOUR EXPLICIT ACCEPTANCE
        OF, THE TERMS AND CONDITIONS OF THIS AGREEMENT UPON
        DECOMPRESSION OF THE SOURCE CODE ARCHIVE.

        U.S. AND INTERNATIONAL COPYRIGHT LAWS AND TREATIES, TO
        INCLUDE ALL INTELLECTUAL PROPERTY LAWS AND TREATIES
        PROTECT THIS SOFTWARE.

        THIS SOFTWARE IS LICENSED, NOT SOLD.  YOU HAVE PURCHASED A
        LICENSE TO POSSESS, VIEW, AND/OR MODIFY THE SOURCE CODE.
        WSS RETAINS OWNERSHIP, COPYRIGHT, AND INTELLECTUAL
        PROPERTY RIGHTS TO THE SOFTWARE AND ANY DERIVATIVES
        PRODUCED THEREOF AND RESERVES THE RIGHT TO UNILATERALLY
        TERMINATE ALL LICENSES TO SOURCE CODE AT ANY TIME.


        a. General License Grant. WSS grants to you a personal,
        exclusive license to:

            1. Install one operational copy of the SOFTWARE that may
            operate on not more than the number of instances you are
            registered for, each accessing the same USER.LST.  Separate
            instances that access a separate USER.LST require
            additional licenses be purchased for each USER.LST.

            2. Download, view, possess, and modify WWIV source code for
            versions through v4.99 for your own personal use after
            completing verification requirements as prescribed by WSS.

            3. Have an unregistered individual modify source code for
            you ON YOUR COMPUTER for your use provided that the source
            code never leaves your computer in any form and remains
            under your direct control at all times.

            4. Have a registered user modify your source code on his or
            her system provided you notify and obtain written
            permission from WSS PRIOR to doing so.

            5. Purchase upgrades to allow the operation of the software
            on more than two and not more than 999 instances.

            6. Distribute source code modifications written by you on
            subboards designed specifically for that purpose or by
            private mailings provided the modification contains no more
            than 100 lines of the original copyrighted code.  You must
            obtain written permission from WSS PRIOR to the distribution
            of modifications containing more than 100 lines of
            copyrighted code.

            7. Provide electronic download access to modification to
            registered users of the SOFTWARE after verification by WSS
            through the use of a modification provided by WSS.

            8. Produce and distribute utilities and add-on programs
            specifically designed to operate on systems running the
            SOFTWARE that utilize ONLY the data structures of the
            SOFTWARE royalty free.  (Use of components, functions,
            or derivative code must be approved and royalty fees paid
            prior to distribution)

        b. License Exclusions.  Under your license, you:

            1. May NOT distribute any modified compilation of the
            SOFTWARE by electronic download or transfer said compilation
            to anyone by any means without PRIOR WRITTEN AUTHORIZATION
            from WSS.

            2. May NOT distribute source code or any portion thereof to
            anyone for any reason without PRIOR WRITTEN AUTHORIZATION
            from WSS. (Distribution of source code fragments authorized
            under paragraphs 1.2.a.6 and 1.2.a.7 excluded.)

            3. May NOT allow unregistered users, or users, not verified
            by WSS, but claiming to be registered, access to or
            electronic download of modifications as described in
            paragraph 1.2.a.6.

            4. May NOT produce and distribute derivative works based
            upon the SOFTWARE in whole or in part except as authorized
            under paragraph 1.2.a.8 above.  Derivatives are defined as
            software programs or components of software programs that
            duplicate the operation, function, and/or appearance of
            the SOFTWARE or contain portions of original copyrighted
            source code of the SOFTWARE.  If any code other than that
            described in paragraph 1.2.a.8 above is used, you must
            obtain written authorization to do so and may incur
            liability to pay WSS certain royalties as negotiated.

            5. May NOT "port" or rewrite the SOFTWARE to function under
            another operating system or on another platform with the
            intent to distribute the work without PRIOR WRITTEN
            AUTHORIZATION from WSS.  You may, however, "port" or
            rewrite the SOFTWARE as described above for your own
            individual use.

            6. May NOT be entitled to the source code to future
            versions of the SOFTWARE due to a decision to terminate
            this distribution method.

        c. Termination of License. WSS reserves the right to
        unilaterally terminate all licenses to source code at any time.
        In addition, WSS will terminate and permanently revoke the
        license of any registered user found in violation of the terms
        and conditions set forth in this EULA or any other EULA
        pertaining to a WSS product and will prosecute said violators
        to the fullest extent of both state and federal, civil and
        criminal laws.

        d. Documentation. This EULA grants you, as an individual, a
        personal, nonexclusive license to make, use, and make available
        for electronic download, an unlimited number of copies of the
        documentation included in the distribution archive provided
        such copies are not modified in any way and contain the original
        copyright information.

        e. Storage and Electronic Transfer of Distribution Archives. You
        may store and make available for electronic download, in
        unmodified form, an unlimited number of the original WWIV v4.30
        shareware archive as distributed by WSS.

        f. De-compilation and Reverse Engineering.  You agree not to
        make any attempt to de-compile, reverse engineer, or disassemble
        the executable portions of the SOFTWARE to avoid the requirement
        to register, modify copyright displays, or the operational
        aspects of the SOFTWARE.

    1.3 LIMITED WARRANTY.  WSS warrants that the SOFTWARE will perform
    as described in the included documentation for a period of sixty
    (60) days from the date of first installation.  Any technical
    support provided by WSS shall be as described in the included
    documentation provided to you in the distribution archive.  WSS
    will make reasonable efforts to solve any problem not covered in
    the included documentation.  To the maximum extent allowed by
    applicable law, implied warranties on the SOFTWARE, if any, are
    limited to sixty days. No other warranties are expressed or implied.
    To the maximum extent allowed by applicable law, WSS disclaims all
    other warranties and conditions, either express or implied,
    including, but not limited to, implied warranties, merchantability
    and/or fitness for a particular purpose, with regard to the SOFTWARE
    and the provision of or failure to provide support.  This limited
    warranty gives you specific legal rights. You may have others, which
    vary from state to state.  This warranty is executed under the laws
    of the Sate of Tennessee.

    1.4 CUSTOMER REMEDIES.  Your exclusive remedy shall be to notify WSS
    of a suspected failure to meet the specifications of the LIMITED
    WARANTY. The entire liability of WSS shall consist of replacement of
    the SOFTWARE with an updated version if available.


=======================================================================
Appendix F (Credits and Thanks)
=======================================================================

    There are more folks that belong on this list that can possibly be
    mentioned.  Here they are in no particular order:

    Wayne Bell (Random) - for starting it all, keeping it going for so
                many years and then seeing the way clear to pass his
                legacy on.

    Wig De Moville (Filo) - for providing a support system for Wayne
                during a time when WWIV might have faded away.

    Greg Ferrante - for introducing me to WWIV.

    Frank Reid - The one man upon whom this entire project was hinged.
                He fueled the fire and motivated me to buy WWIV in
                the first place then provided his extensive expertise
                and untiring efforts during the development process.
                Cannonization pending...

    Craig Dooley (Morgul) - for backing me up during the early years
                and his continuing support and friendship.

    Jim Wire - for writing the WFC screen and CallBack modules.
    
    Rob Clevenger (Rushfan) - for his help in every phase of development
                and documentation.

    Mike Deweese (Zu Digital) - for providing some of the most
                innovative code and features in what you see as
                WWIV v4.30.

    Mike Dunston (ATani) - for providing the base code for the FOSSIL
                implementation.  Without this code, WWIV would not be
                Internet capable out of the box.

    Tony Geisler (Goose) - for providing his consumate skill with
                communications routines and debugging the FOSSIL
                implementation and other "hard to kill" bugs

    Jeff Kronlage (Pug) - for writing and donating the code to WMChat
                for inclusion in this release.

    Glen Shere (Diamond) - for writing and donating the base code for
                STREDIT for inclusion in this release.

    Dan Morgan (Quixotic Quest) - for supplying the Windows FAQs.

    Glen Carlzen (The Animal) - for providing the OS/2 and protocol
                FAQ's.

    The WWIV Development Team (WDT) - the group of truly hard-core
                sysops that contributed their time, talents, and
                energies to develop a top quality product.

    The Beta Team - for their tireless testing of of the software and
                survival through Beta 1 and for finding a great majority
                of the bugs, some more than once.

    Mod Authors - Thanks to the authors of all the mods that were
    included and/or adapted for v4.30.

    Last but most certainly not least, the group who deserves the
    greatest appreciation, the registered users, without whom, none
    of this would be possible.


=======================================================================
Appendix G (WWIV Software Services Operational Policy)
=======================================================================

This document last revised: 27 February 2000

1. General:  WWIV Software Services (WSS) dictates policy for the
software under its control only.  Network policies are dictated
by the Network Coordinator (NC) or administrative body of the
individual networks.  WSS does however, reserve the right to interpret
our policy for the individual user and/or network administrator(s).
Any question as to applicability or interpretation of these policies
should be brought to the attention of WSS immediately and before the
registered user or network official act.  Decisions or interpretations
rendered by WSS on any issue are final.  WSS reserves the right to
revise, rescind, expand or alter the terms and conditions of this or
any other existing policy at any time and may do so without notice.
Revised policy will be grand fathered in most cases to allow no
degradation of eligibility, status, or office of the individuals it
affects.

2. Distribution, Software Registration and License: WWIV is distributed
under the shareware concept.  The user has 60 (sixty) days to evaluate
suitability of the software to his or her needs.  Not later than the
sixtieth day, the user must register the software using one of the
methods contained in paragraph 3 below, or discontinue use of the
software and remove all operational copies and archives from his or her
computer(s).  The user may download evaluation versions of the newer
revisions or releases to try the software again and the 60-day trial
period begins anew. Re-installation of the same version, for any reason,
after the initial 60-day trial DOES NOT, constitute a new trial period
and is a violation of the shareware license agreement and is illegal.
The trial period may be extended at the discretion of WSS on a cases by
case basis.  Initiation of a payment plan under the provisions of
paragraph 3b.3 below extends the trial period for 60 days. Each payment
made on time will extend the trial period for an additional 60 days not
to exceed a total of 240 days.


3. Registration:

    a.  General.  When registering, the user is purchasing a license to
        use the software in accordance with the End User License
        Agreement (EULA) associated with the product.  Registration
        does not imply nor entail ownership of the software.  WSS
        retains ownership of the software itself.

    b.  Methods: There are three methods of registration available,

        1.  Online Registration. Available JUN 00. Prices for online
            registrations are slightly higher due to increased costs.

        2.  Normal Registrations. Executed by check or money order
            via US Mail.

        3.  Payment Plan. WSS offers a payment plan for the purchase
            of BBS registrations.  See the BBS documentation for more
            information on the payment plan.

    c.  Revocation: The user's license may be revoked by WSS at any
        time should he or she violate any provision of this document or
        the terms and conditions specified in the license agreement
        contained in the distribution archives.

    d.  Upgrades: The user is entitled to upgrade to all releases of
        the product line under the major revision purchased.  For
        example, purchase of a v4.xx registration entitles the user to
        free upgrades to all releases through v4.99 for the platform.
        The user IS NOT entitled to free cross platform upgrades under
        this policy.  Cross platform upgrade fees may or may not be
        charged and will be announced  well in advance of releases.

    e.  Instance Upgrades:  The user is entitled to purchase instance
        upgrades to a previously purchased BBS registration at the price
        announced at the time of release.

    f.  Transfers: REGISTRATIONS MAY ONLY BE TRANSFERRED BY WWIV
        Software Services.  Registration transfers are only offered for
        BBS registrations.  No other registrations will be transferred.

    g.  Exemptions:  Registration exemptions are authorized to be
        granted by the Network Coordinators (NC) of :

        WWIVnet             IceNet          TerraNet
        FILEnet             GLOBALnet       WWIVLink

        The NC of these networks may grant an exemption for systems
        acting in the capacity of network servers.  NC's may place
        additional requirements on the system; however, the following
        minimum criteria must be met in order to grant the exemption:

            1.  The requesting sysop must have purchased a valid
            registration for at least one copy of WWIV and must be
            running a public BBS on the network in question using that
            registration number.

            2.  The primary purpose of the exempted system must be the
            movement of network traffic and not operate as a public
            dialup system.  User accounts on the server will be limited
            to number one accounts of connecting systems generated by
            the server operator.

            3.  The server operator will provide a dialup telephone
            number or Internet address (telnet) for the system to allow
            the NC or WSS to log on to the system.  This is to verify
            that the system is in fact a server system and maintains
            compliance with both WSS and network policy.

            4.  The exempted system must operate for the good of the
            network as a whole in the judgement of the network
            administration.

        Network Coordinators desiring authorization to grant exemptions
        should email WSS with a request.

4. Source Code.

    a.  Availability. Currently, registration of the BBS software
    entitles the user to the possess, view, and modify the source code
    to the BBS in accordance with the associated EULA.  If, at any time
    in the future, it becomes impossible or too difficult to control
    the distribution of source code, this policy may be rescinded.  FOR
    SECURITY REASONS, THE SOURCE CODE TO INIT.EXE, NETWORK SOFTWARE OR
    NETUP IS NOT AVAILABLE TO ANYONE.

    b. Obtaining the Source Code.  Current source code may be obtained:

        1. On disk by sending a completed registration form and $10.00
        (US) to WSS.

        2.  By download from an authorized Source Distribution System
        (SDS).  SDS systems are authorized by WSS to distribute WWIV
        source code without charge to registered users after
        verification of their registration information with WSS.
        In order to download the source code from a SDS, the registered
        user must logon to the SDS and establish a user account, then
        type //SDS at the main menu prompt. Following the prompts will
        send a request for access directly to WSS. Upon verification of
        your request and registration information, authorization for
        access will be sent to the SDS operator who will grant you
        access to the distribution archives.

        3.  Via the Internet SDS at http://sds.wwiv.com/.  You will be
        required to send a request similar to the one above from this
        location.  Processing of these applications is normally
        accomplished within five to seven days.

    c.  Modification Publication: Registered users may publish
        modifications on sub-boards designed for that purpose on
        individual networks.  It is the responsibility of the host of
        these subs to ensure that only registered users are permitted
        to subscribe to subs where modifications are posted.    Source
        code modifications that contain more than 100 lines of original
        copyrighted code require a release for publication from WSS.
        Email the mod in its entirety to WSS.  In most cases, unless the
        modification contains code of a sensitive or malicious nature,
        they will be approved for release.  Releases or Denial of
        Release will be issued within five business days.

    d.  Modification Access Restrictions: Registered sysops will control
        access to all BBS modifications available for download, viewing,
        reading or capture on their system.  The registration information
        for ALL individuals desiring access to modifications in any form
        must be verified with WSS before granting access.  Sysops wishing
        to distribute modifications via download will request an install a
        modification for this process from WSS.  This is the only request
        that will be accepted.

    e.  License Agreement Violations: Unauthorized distribution of WWIV
        BBS Source Code or portions thereof is a crime.  Registered
        and/or unregistered Individuals found in violation of the EULA
        contained in the source code archive will be prosecuted to the
        fullest extent of both civil and criminal laws.  All registered
        users should review of the Source Code License Agreement to
        ensure they fully understand and are in compliance with it.
        Registered users have the responsibility assigned under the EULA
        to immediately report suspected or known illegal possession,
        modification, or distribution of source code under any provisions
        contained therein.  Reporting violations protects your future
        ability to access the source code.


5.  WSS Source Distribution Systems (SDS):  WSS has several systems
specially authorized to distribute source code to registered sysops.
The number of systems is limited and only the most qualified systems
are selected for this function. Meeting all the qualifications of
the criteria listed below is no guarantee of selection.

    a.  You MUST be the sysop (#1) of your system.

    b.  You MUST have been a registered sysop for at least 2 years.

    c.  You MUST have been running your BBS continuously for the last
        2 years.

    d.  Your BBS MUST be a full time system, open to anyone who wishes to
        call.  No part-time boards, closed boards, or boards that require
        a new user password to sign on.

    e.  You MUST be 21 years of age or older and provide a photocopy of
        an official photo ID to WSS with your application.

    f.  You MUST have been a member of at least one major network for a
        minimum of one year.  (preferably WWIVnet, IceNet, TerraNet or
        FILEnet)

    g.  You MUST provide a list of at least 20 registered WWIV Sysops
        who want to be able to download the WWIV Source Code from you,
        listing their real names and registration numbers.

    h.  You must install the approved SDS Access Request Modification on
        your system.

    i.  Upon acceptance, you must be willing to sign a distribution
        agreement with WSS that outlines your legal responsibilities
        and obligations as a Source Distribution System.

6.  WSS Support Board Network:  WSS provides a network of highly
skilled, knowledgeable sysops to the BBS community.  Sysops selected
for this status are time tested and have been recognized for the amount
and quality of support they offer.  Below is a description of the types
of support offered and selection criteria for each:

    a.  The Support Coordinator and active Support Boards select new
        Support Boards (SB).  To become an official SB, the sysop, as
        a minimum, must meet the requirements of 5a through 5d above.
        In addition, the following conditions must be met:

        1.  The sysop must maintain a library of all official WSS
            releases, and a reasonably stocked library of WWIV support
            files, readily accessible to the public, without
            restrictions or ratios.

        2.  The system must offer Auto Sysop Validation (ASV) and/or
            a Guest Sysop Account (GSA)

        3.  You MUST have been a member of at least one major network
            for a minimum of one year.  (preferably WWIVnet, IceNet,
            TerraNet or FILEnet)

        4.  You must be thoroughly knowledgeable concerning BBS and
            network operations and will be required to provide prompt,
            courteous replies to requests for assistance as well as
            extensive assistance to new sysops who may request help.

    b.  WSS, The Support Coordinator,  and the active Core Sysops select
        Core Support Boards (CSB).  To be considered for Core Status,
        the sysop must have a minimum of 2 years of exemplary service as
        a Support Board.  There is no application process as with the
        SB system.  Core Support Boards are selected solely on tenure
        and merit of service.

    c.  Any form of Support Board status may be removed at any time if
        the sysop fails to meet minimum requirements or when individual
        conduct is contrary to the spirit and intent of the support
        network.

