Ú¿ ÚÂÄ¿ ¿ ÚÄÂÂÄ¿ ÚÂÄÄ¿ Ú¿ ÚÂÄÄ¿ ÚÂÄÄ¿ ô ô ³ ³ ô ÃÅÄ Ã´ ÃÅÄ Ã´ ÀÙ ÀÙ ÀÄÙ ÀÙ ÀÁÄÄÙ ÀÁÄÄÙ ÀÁÄÄÙ ÀÁÄÄÙ ÚÂÄÄ¿ ÚÂÄÄ¿ ÚÂÄÄ¿ ÚÄÂÂÄ¿ Ú¿ ¿ ÚÂÄ¿ ÚÂÄ¿ ÚÂÄÄ¿ ÀÁÄ¿ ô ³ ÃÅÄ Ã´ ô ¿ ³ ÚÅÁÄÁ¿ ÃÅÄÁ¿ ÃÅÄ ÀÄÄÁÙ ÀÁÄÄÙ ÀÙ ÀÙ ÀÁÄÁÄÙ ÀÙ Ù ÀÙ Ù ÀÁÄÄÙ I n t e l e c S o f t w a r e ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ WelcoMat ³ ÚÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³ ³WelcoMat PCBoard PPE utility will perform two functions for new users after ³³ ³they have filled out their registration information. First it gives you a ³³ ³method to automatically upgrade specific persons that you know will be ³³ ³calling, without having to set up their user record. They logon, register, ³³ ³and then welcomemat auto-upgrades them to whatever security level you have ³³ ³set for their entry and optionally registers them in specified conferences. ³³ ³ The second function is to provide other new users with a list of files ³³ ³to download such as Registration Information, Rules, etc.... allowing them ³³ ³to flag and download them, or instead send an automated message requesting ³³ ³that Registration Information be sent to them. After processing, the PPE can³³ ³also Log the user off. Upgraded users aren't displayed the files, and aren'tÃÙ ³affected by the Logoff. Either option of WelcomeMat can be disabled as well!³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Installation WelcoMat ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Installation of WelcoMat is fairly straight-forward. Hopefully you are already familiar with PPEs so I don't have to get overly verbose here. Here's how I recommend it be done. In a Security Logon file for your new user security level (i.e. new user security of 10 would have a filename of 10. see PCBoard Docs if you're unsure about this) place the following line: !E:\PPE\WELCOMAT\WELCOMAT.PPE If you are using the second function (displaying a list of files to download): - Create the file(s) you want to have available for downloading to the new user. - place the file(s) in your DLPATH.LST - create an entry in the FSEC file making the file(s) a FREEFILE Now Edit the Config, List, and display Files to suit your system If you have registered, place a copy of the WELCOMAT.KEY (or POWERPAK.KEY) in the same directory as the PPE. The Welcomat config file MUST be called WELCOMAT.CNF and all files must be located in the same directory as WELCOMAT.PPE. This is very important! ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Y ³ Y/N Activate WelcomeMat for Known Callers ³ Y ³ Y/N Activate Reg. Request for Unknown Callers ³ REGREQ.LST ³ File List for Reg. Request ³ WELCOMAT.LST ³ List of names that you want to upgrade. ³ DISP ³ Filename displayed to upgraded callers ³ 5 ³ Minimum security level to run this PPE. ³ 10 ³ Maximum security level to run this PPE. ³ RRINTRO ³ File Displayed to Unknown Callers ³ Y ³ Y/N Logoff Unknown Callers after Processing ³ SYSOP ³ Information Request Message TO: field. ³ 0 ³ Information Request Message Conf. # ³ R ³ N/R Information Request Message Security ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Line 1 - Indicates whether you want to check new users for automated upgrading in the WELCOMAT.LST file. Line 2 - Indicates whether you want new users to be displayed the file list indicated in REGREQ.LST and prompted to download them (User selects what they want to download) Line 3 - List Filename for Downloadable files (see REGREQ.LST) Line 4 - Known Users list File (See WELCOMAT.LST) Line 5 - Display if Known User is found and Upgraded Line 6 - Minimum Security to Run PPE. Useful if you run the PPE from the LOGON script or from a bulletin. Line 7 - Maximum Security to Run PPE. Same. Line 8 - Intro file for Unknown users. Displayed before the file list is displayed. Allows you to give a brief explanation before-hand. Line 9 - Y/N Logoff Unknown users after processing. For users not upgraded (not in the Welcomat.lst file) the PPE can automatically log the user off after they have downloaded their selected files (or sent the req. message). Handy for closed BBS's. Line 10- Information Request Message TO: field If User doesn't DL any of the files, they can send an automated message (they don't actually enter the text). This is who it should go to (usually the sysop) Line 11- Information Request Message Conf. # The Conference number that the message should go to. Line 12- N/R Information Request Message Security Whether the message should be public or private. The DISP can contain @X codes and is displayed when upgraded. The RRINTRO can contain @X codes and is displayed when the new user isn't found in the welcomat.lst file. Then the screen is cleared and the file list is displayed. They are also capable of security, Language, and Graphic specific Displays. WELCOMAT.LST ============= The WELCOMAT.LST is an ascii list of user names with a specific format. A sample is shown below: JOHN DOE 5 1;2;3;4;5;6;7;8;9;10;11;12;13;14;15;16;17;18;19;20;21;22;23;24;25 JANE DOE 10 1;2;3 Each entry into this list file must use 3 lines. The first line is the user name that you want upgraded. The second is the security level to upgrade this user to. The third line contains all the conferences you want this user registered in as soon as they log in. You must separate each conference number with either a space or semi-colon. We've taken this approach so that you can have different upgrade options for each of several different users who may be calling you. If you don't wish to register particular users in any conferences then leave that user's "third line" blank. REGREQ.LST =========== The REGREQ.LST file lists all the files (and the descriptions) that you want new users to be able to download and has the following format: 2 New User Registration Request file REGREQ.ZIP PK-Zip Archiver (Self-Extracting) PKZ204G.EXE Line 1 - The number of files available in the list line 2 - Description of file. Displayed to the User line 3 - Actual file name that is flagged. Repeat lines 2 and 3 for the number of entries listed in line 1 Attempt to keep the description lines to 60 characters or less Filename lines cannot include paths; the files must be found in a directory in the DLPATH.LST, and should be accessible to the security level with an entry in the FSEC file.