DOCUMENTATION FOR QMUP
                   FILE TO MESSAGE FILE TRANSFER PROGRAM
                             FOR QBBS SYSTEMS
                                    BY
                              LAWRENCE DAVIS


    Documentation for QMUP 1.01 (10/25/86)
 
    ** For use with QRUN389C or later **

    QMUP, a file to message file program, is designed to facilitate posting
    of messages to the message base.  With QMUP one can create a message
    offline and transfer it via an error checking program such as KMD or
    XMODEM.  This virtually eliminates difficulties in uploading a file
    while in the BBS.


    QMUP SETUP:

    QMUP.COM should be placed on Drive A, User 0 and named QMUP.COM.  It
    should be tagged as a $SYS file using STAT QMUP.COM $SYS.  The Sysop
    should run QBBS using the BYE E command and then use the Q command to
    load QMUP.  The first time QMUP is run it will prompt for the
    Drive/User where private files are uploaded.  This Drive/User area is
    the same as the RP (Receive Private) area in KMD or XMODEM.  It will
    then prompt for the maximum number of lines a user may upload to a
    message base.  The maximum number is 100 lines.  QMUP will create a
    file called QUP-DAT and place it in the drive/user area with the rest
    of the QBBS data files.  If you need to change the above values just
    erase QUP-DAT and re-run QMUP.


    QMUP AUTOMATION:

    The file to message file transfer procedure can be automated to a great
    extent.  This automation is fully optimized with systems that have a
    multi-command line buffer enabled in CP/M.  These systems include
    ZCPR2, ZCPR3,and ZCMD2x.  The first thing to do is to create an alias
    file to hold your multi-command.  If using ZCPR2 or ZCMD2x, the AKA
    program should be used.  If using ZCPR3 the ALIAS program should be
    used.  The multi-command should be structured similar to the following
    (comments are in parentheses):

    KMD RP QUP  (Load KMD to receive file QUP to private area)
    A0:QMUP     (Evoke QMUP.COM to transfer QUP text file to message base)

    Name the above multi-command as QUP.COM and place it on A0.

    Note that the uploaded file will always be named QUP so that QMUP.COM
    can find it without prompting for a filename.

    To review:  QUP.COM on A0 is an alias that loads KMD to receive the
    text file QUP.  It then loads QMUP.COM which will transfer the file to
    the QBBS message base.

    If your CP/M does not support a multi-command line then the user will
    have to go through two steps:

    1.  They will have to enter KMD RP QUP.

    2.  After the transfer they will have to enter QMUP.


    QMUP SYSOP USAGE:

    The Sysop has a few extra privileges when using QMUP.  The Sysop may
    transfer a full 100 line message regardless of the line length
    limitation for callers.   The Sysop may continue to transfer files
    after the first one (the caller exits to CP/M after each transfer).

    QMUP.COM normally erases the uploaded file after it transfers it to the
    message base.  The sysop may place various files in the 'RP' area and
    they will not be erased after transfer (1.01).  The Sysop should take
    care not to name a file QUP as this would prevent future callers from
    uploading files via the KMD automation procedure.


    FILE PREPARATION:

    The file to be transfered to the message base should be formatted with
    the following restrictions in mind:

    1.  The file should not exceed the number of lines designated by
        the Sysop during the QMUP installation.

    2.  The line length should not exceed 63 charcters of text.  A
        line longer than 63 characters will be truncated.

    3.  It is recommended that a non-document type editor be used to
        create the message file (VDE is probably the best choice as it
        allows a right margin to be set and will word-wrap automatically).
        Wordstar/NewWord in non-document mode are also acceptable.

    4.  No end of file marker is necessary as QMUP can detect the end
        of the file.


    ADDITIONAL NOTES:

    1.   Since QMUP.COM is looking for the text file QMUP (to automate
         things) it must erase it after transfer so that there is
         space for the next upload.

    2.  If the file exceeds the number of lines set by the Sysop the
        program will abort and not save any text.  

    3.  The user (or SYSOP) may abort QMUP by entering a RETURN alone at the
        'Subject?' prompt.  A RETURN alone at the 'Enter the Filename to
        Transfer' prompt will also abort the program.