
                    ﾚｿ ﾚﾂﾄｿ ｿ ﾚﾄﾂﾂﾄｿ ﾚﾂﾄﾄｿ ﾚｿ    ﾚﾂﾄﾄｿ ﾚﾂﾄﾄｿ
                    ﾃｴ ﾃｴ ｳ ｳ   ﾃｴ   ﾃﾅﾄ   ﾃｴ    ﾃﾅﾄ   ﾃｴ
                    ﾀﾙ ﾀﾙ ﾀﾄﾙ   ﾀﾙ   ﾀﾁﾄﾄﾙ ﾀﾁﾄﾄﾙ ﾀﾁﾄﾄﾙ ﾀﾁﾄﾄﾙ
               ﾚﾂﾄﾄｿ ﾚﾂﾄﾄｿ ﾚﾂﾄﾄｿ ﾚﾄﾂﾂﾄｿ ﾚｿ   ｿ  ﾚﾂﾄｿ  ﾚﾂﾄｿ  ﾚﾂﾄﾄｿ
               ﾀﾁﾄﾂｿ ﾃｴ  ｳ ﾃﾅﾄ     ﾃｴ   ﾃｴ ｿ ｳ ﾚﾅﾁﾄﾁｿ ﾃﾅﾄﾁｿ ﾃﾅﾄ
               ﾀﾄﾄﾁﾙ ﾀﾁﾄﾄﾙ ﾀﾙ      ﾀﾙ   ﾀﾁﾄﾁﾄﾙ ﾀﾙ   ﾙ ﾀﾙ  ﾙ ﾀﾁﾄﾄﾙ
                I  n  t  e  l  e  c       S  o  f  t  w  a  r  e 

 ﾚﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄｿ
 ｳ TwitUser                                                                   ｳ
ﾚﾁﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄｿｳ
ｳTwitUser is the easy way  to keep problem users from using specific commandsｳｳ
ｳon your BBS. It's the perfect SysOp revenge. Now granted most users are wellﾃﾙ
ｳworth their weight in gold, but problem users Do pop up from time to time...ｳ
ﾀﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾙ

If you are upgrading from version 1.0, the CNF file is no longer used and may
be deleted. You must also do the following:

1. Edit all the display files and replace the line that called the copied ppe.
   Change the line to "!d:\path\TWITUSER.PPE command" (without quotes), where
   command is the letter(s) for the command this display file is protecting.
   
2. Delete all the renamed copies of the  old twituser PPE (C.PPE, D.PPE, 
   OPEN.PPE, etc...) leaving only the TWITUSER.PPE, the display files, and 
   the .LST files. 

That's it. TwitUser checks for the command.LST file (command passed as the 
parameter. It will exit gracefully if any files are missing.
    

     ﾚﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄｿ
     ｳ Installation                                              PseudoNm ｳ
     ﾀﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾙ

    Extract the PPE/DOC files to the directory of your choice. You can extract
    the accompanying sample display and LST files as well  for  reference  but 
    they aren't needed. 

     First, you must go into PCBSetup to find the path to the command display
     files. Press B (File Locations)  and then A (System Files & Directories)
     and  the last line (Location of Command Display Files) shows the path to 
     the Command Display Files are located.

ﾉﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍｻ
ｺ                               File Locations                                ｺ
ｺ                                System Files                                 ｺ
ｺ                                                                             ｺ
ｺ  Location of Command Display Files : D:\PCB\CMDDISP\                        ｺ
ｺ                                                                             ｺ
ﾈﾍ 12:00:00 ﾍﾍﾍ 09-17-95 ﾍﾍﾍﾍﾍﾍ F1 ﾍ help ﾍﾍﾍﾍ caps: OFF  num: OFF  ins: OFF ﾍｼ

    This is the directory where you will create the display files for the 
    commands you want the TwitUser PPE to monitor. In theis directory, create
    a file for each command to be monitored. The filename must be the same as
    the command, without any extension. 

    example:

    D.      - (D)ownload Command
    DB.     - (DB) Download Batch
    OPEN.   - (OPEN) door


    add the line:

    !d:\path\TWITUSER.PPE command

    where "command" is the command to monitor. If the file exists, just insert
    the above line as the first line. It will check the twitlist for that 
    command and then the rest of the file will be displayed as usual.

  ﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍﾍ

    Next, you need to define the users that will be twitted by each command.
    This    is  accomplished by a  .LST file for each command, and these LST 
    files must reside in the PPE directory.

   (using the D)ownload command as an example)

     D.LST

     D.LST is a list of user names, one name per line of only the users  you 
     want to be "twit'd" when they use the D)ownload command.

     So if you want to have TwitUser monitor the U command you must make:
     U.         in the Command Display directory
     U.LST      in the PPE directory.

     For D an U, I recommend using DB and UB as well. 
    
     Another Quick Tip: Multi-letter commands can be used with less letters. 
     For example DOOR can be called from DOOR, DOO, or DO (unless  you  have 
     a DOO or DO, command as well, D obviously is for Download). Users  only 
     have  to give enough letters to  distinguish  the  command  from  other 
     shorter commands. But PCBoard matches the Command Display File for  the
     command entered, not what it is matched with.

     So with the Example of DOOR, you would need 3 Command Display Files:
     DO.
     DOO.
     DOOR.

     If you put !d:\path\TWITUSER.PPE DOOR in each of these, then  you  only
     need to have a DOOR.LST file in the PPE directory. All three variations
     will use the same LST file. 

     This method could be used for grouping commands too, using 1 list. <g>