MFLAG.DOC     12-15-94

                            
                            
                            MFLAG.PPE v1.0
                            
        As a SysOp I fell in love with FLAG.PPE by David Terry, however, 
        as time went by, I observed a problem with new users that were 
        using a non-batch protocol as their default protocol.
        
        FLAG.PPE would let this user flag all the files they wish to 
        flag, but when it came time to download the files, PCBoard would 
        present the user with a list of BATCH-MODE protocols to choose 
        from, because they had more than one file flagged for downloading! 
        
        And of course, now what? If they don't have a batch-mode 
        protocol to choose from in their communications program, they 
        are stuck (Otherwords, in trouble!). Let them figure their way 
        out of this one. They probably won't, so here comes ALT-H!
        
        Believe it or not, there are many new and unsophisticated 
        callers NEW to the BBSing world using hand-me-down computers and 
        communications software. Either their software lacks batch-mode 
        protocols (Procomm Plus v1.0), or they do not know the difference,
        and have selected to use a non-batch protocol. In any event, this
        raises havoc on your BBS when FLAG.PPE is used.
        
        So, the object of MFLAG.PPE is to keep them out of this trap and 
        to force them into immediate download when they have flagged a 
        file to download. A screen file will be displayed to them 
        explaining why the download needs to take place now, and they 
        are offered the opportunity to either download the file now, 
        (C)ancel the download and the flagged file is UNflagged, press
        (H)elp for a help file telling them what the differences are
        between the available protocols on your BBS.
        
        If a caller has a batch-mode protocol selected as default on 
        your BBS, then normal multiple file flagging will be done just 
        like the original FLAG.PPE...
        
        Also, If the caller did not select ANY default protocol to use 
        on the BBS when completing the new user process, (I do get some 
        new callers doing just that!), any attempt to flag a file will 
        immediately CALL FLAGPROT.PPE to offer the user the opportunity 
        to select a protocol of choice NOW! If none is selected, they 
        are returned to MFLAG.PPE and the screen they were viewing at 
        the time. Nothing is flagged! They cannot flag a file UNTIL they
        have selected a default protocol to use on your BBS.
        
        However, if they DID select a protocol to use as their default 
        on the BBS, MFLAG.PPE will behave accordingly. Multiple flagging 
        for batch-mode protocols, immediate downloading for non-batch 
        protocols. This way both parties are happy; the user, and the 
        SysOp!
        
                            MFLAG.DOC                     Page 2
        **********************************************************
        Now lets look at the list of files included in the archive.
        
        README.1ST    I hope you have read the file BEFORE this one!
        MFLAG.PPE     The main program
        FLAGPROT.PPE  The protocol setting PPE called by MFLAG.PPE
        DLNOW         Display file explaining immediate download need
        DLHELP        Display file explaining available protocols. ADD
                      additional protocols you may be offering.
        PNONE         Display file explaining a need to select a protocol.
                      Note: if you have MORE than 11 protocol choices to
                      offer, Add a @PAUSE@ macro to the end of this file.
        FLAGNEW       Standard FLAG prompt, enhanced with additional info.
                      A Ctrl-Z display file! (see README.1ST)
        FLAGOLD       Non-ANSI prompt for TTY callers
        FLAGBAR       RIPscrip "Use MOUSE to flag files" (untested by me)
        FLAGBARR      RIPscrip prompt  (Functionality untested by me)
        
        The above files are the required files for normal use. The
        following files are optional, select to use as you wish.
        
        FLAGNEW.OP1   Optional FLAGNEW prompt, displays DIR number the
                      user is viewing. A Ctrl-Z file! Rename to FLAGNEW.
                      
        FLAGNEW.OP2   Optional FLAGNEW prompt. Displays CONF & DIR number
                      user is viewing. A Ctrl-Z file! Rename to FLAGNEW.
                      Great for CD-ROM conferences in addition to Main
                      Board.
                              
        I personally like using FLAGNEW.OP2 prompt so I can observe
        where the user is: What conference, directory, etc.
        
        INSTALLATION:
        
        My assumption here is that you are ALREADY using FLAG.PPE, so I'm
        not going to explain how to install MFLAG.PPE as such. 
        Temporarily backup your current FLAG directory, DELETE the old files,
        than copy the new MFLAG files to that directory. If you are lazy,
        then just rename MFLAG.PPE to FLAG.PPE and everything will operate
        just as before, without needing to modify the PCBTEXT file!
        
        USING A RAMDISK:
        
        I certainly hope you have been running FLAG.PPE and it's 
        required files from a ramdisk... It's really necessary for fast 
        usage and display of the prompt line! I use a batch file called 
        START.BAT that is called from my autoexec.bat to "copy" all the 
        required files to the ramdisk, and PCBTEXT reflects this path to 
        run the PPE. (don't forget to copy FLAGPROT.PPE there also).
        
        I hope you enjoy using this revised PPE as much as I have...
        
        Don Bearor, SysOp
        The Home Office On-Line
        BBS: 310-422-0401