4DVC: 4DOS Version Control


    Thanks for looking into 4DVC. To get started, make sure that all 4DVC files
are either in your current directory or in a directory defined in your PATH
Environment Variable. Then simply enter "4DVC" from the 4DOS Command-Line.
Select option "I" for information about 4DVC and its uses/requirements.

    Minimum Requirements:
    1) 4DOS 3.02
    2) PK(UN)ZIP 1.1
    3) At least 128 bytes of free Environment Space
    4) KEYSTACK.SYS loaded as a Device Driver in your CONFIG.SYS file.

================================================================================
Release Notes:

 2.11 - First Public Domain Release

 2.20 - Added logic to scan the PATH for 4DVCREAD.ME so that the file does not
        have to reside in your current directory.

 2.21 - Added instructions at front-end of 4DVC to ensure that all files used by
        4DVC are accessible via the PATH. Also added a check to ensure that
        enough Environment Space is available before allowing 4DVC to run.

 2.22 - Moved edit-checks to a separate .BTM file (4DVCCHK.BTM). Edits now
        include checks to make sure that PK(UN)ZIP is addressable via the PATH,
        a CONFIG.SYS file is defined, KEYSTACK is loaded as a device driver.
        There are also checks to make sure that the versions of PK(UN)ZIP are
        1.1 or higher, although these checks are commented-out. They tend to
        slow-down the start-up process to an unaccetable point, but if you wish
        to include them, just uncomment the lines.

 2.30 - ALLRIGHT ALREADY! Geez! C'mon folks, I'm glad you are finding good
        uses for 4DVC, but as I said, THIS IS NOT MENT TO COMPETE WITH OTHER
        COMMERCIAL PACKAGES! This release will be the last for a while (unless
        someone finds "real" bugs). Your comments and suggestions are welcome,
        and I will attempt to include them in future releases, but you will have
        to make attempts to "fix" problems yourself on an immediate basis. For
        those of you who called long-distance to ask questions and/or goad me
        into applying "fixes", I must say that I am overwhelmed with your
        interest, but isn't there ANYONE in your area than knows PC's and can
        work with you to modify 4DVC? Since I posted the first Public Domain
        version of 4DVC on 10/22/90, this makes the 5th release in as many days!
        From now on, you can expect enhancements once every 3 or 4 months at
        best - no sooner, and I will no longer support callers, even if you are
        calling long distance. This is just 4DOS BTM files, guys. I know they
        are a little complex, but an hour or two of study will clarify all!

        These are the changes made in release 2.30 (note that you might need a
        STACKS= in your CONFIG.SYS because of the now large nested levels of
        processing):

      - Added a change to the EXTRACT and DELETE functions so that they won't
        hiccough on comments that contain unusual or wierd characters. These
        processes "worked" before, they just didn't pull the comments from
        the ZIP file.

      - Added logic into 4DVC.BTM to test the command line for processing
        options and automatically execute them if found (if not found, user
        input is prompted for just like 4DVC used to always run).
        Rules for the command line parameters are:
        1) Format: 4DVC c 1 2 3 ... n
           where   c    = A (add), X (extract), E (erase), or I (Information)
                   1-n  = filespecs for the A, X, and E commands (ignored for I)
        2) Only 1 command can be processed per run of 4DVC; all other parms on
           the command line are taken to mean "filespecs" options for the
           primary command entered.
        3) After execution of the command, 4DVC exits to the 4DOS prompt.
        4) If 1-n are not provided, user input is prompted for.
        5) If the command is invalid, 4DVC runs as if no command line parameters
           were provided (user input is prompted for).