------------------------------------------------------------------------------ ßÛß ÛÜÝÞßÛ NukePPE Version 2.0 PPE Concept/Codeing/Testing by BayBeVet for the TUNWarez Programming Team PPE Testing/Q.A. by The Chairman for the TUNWarez Programming Team TUNSTALL Coding/Testing by BayBeVet for the TUNWarez Programming Team PPE Concept/Code/Rights Reserved 1994-95 by The TUNWarez Programing Team Support BBS: The Underground Network (516)281-8139 28.8 V.34 Node 1 (516)281-6938 28.8 V.34 Node 2 (516)281-8321 28.8 V.Fast Node 3 (516)281-8358 28.8 V.Fast Node 4 Beta & Distro. Sites: --------------------- TraVesTy Of LiFe White Eagle (516)475-7532 28.8K Node 1 (516)475-2489 28.8K Node 2 ------------------------------------------------------------------------------ HISTORY: -------- This PPE grew from a need at our board. Nearly ALL PCBoard SysOps use PFED, and Boomer included his good, but lacking, PFEDNUKE PPE but The problem with PFEDNUKE is: 1) Boards incorrectly setup the message base so users never read their mail 2) Users just Don't read their Email 3) Users Dont Delete their Email, thus your Message Databases become HUGE rock on your drive ! 4) Pfed's Limit of a 35 character line notice. Some cases, too small to get a complete thought across to the user 5) More damn work for the SysOp, After he gets done in PFed, He needs to Logon to his board, and then run PFEDNUKE to send out the notices. We admit it, we are too damn lazy, more so with all the work of a multi-node BBS. This PPE = Less Work for you ! 6) No Master Log so you can go back and review what you have deleted from a user in the past. Good for spoting those troublesome users. So, The result was the birth of this PPE to offer a better choice than all the presently available PFed Related PPE's Out There. FEATURES -------- -> Unlike many other popular PPE's in use out there, this one has no damn "Backdoors" in it ! We are just too old to deal with that stuff. The TUNPPE you downloaded from our board is the same damn one, code for code, that we use on our board, so think about it :) -> Completely Automated. No sending Email, No Packing The Message Bases. The PPE checks the PFEDNUKE.LOG when a user logs on, displaying any notices to them, and removing the notice entry from the PFEDNUKE.LOG and placing it into a MASTER.LOG so you have a record of the action and to confirm the user got the notice(s). -> Works for NUKE, BONUS, and WARNING notices of PFED. -> Allows for SysOp Made Form Letters matching PFED Macro Number to display to the user in greater detail the reason for the nuking, or otherwise. This allows you to display to the user your rules or otherwise concerning the subject in addition to the 35 character long reason used by PFED. -> Nearly All Display Screens and Prompts are 100% SysOp Configurable using in most cases standard ANSI/Text screens ( PCB @Color Codes are valid ), to create that custom look ( no more of that damn name of the PPE author on each and every screen and part of the PPE hard coded in! ). Furthermore, some prompts may even be replaced with future TUNNukePPE Enhancement Modules or 3rd party PPE's ( for lightbar Prompts for example,either your own or other compatible available PPE's ). This allows your board to be unique instead of looking like everyone else's board ( Like SysOp's that use SLogon/Provote for example, all their boards look nearly the same during the logon process ). -> TUN'EM ( TUN "Engine/Module" ) program design allows for future compatiablity with other TUNPPE's as well as the possiblility of enhancement modules which may be used to customize/change certain parts of the PPE should they become available in the future. ( For example, a lightbar enhancement modules may be used to change the default DOS matrix to a light bar driven prompted one ) ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ INSTALLATION ------------ TUNLogon.PPE Users Installation -------------------------------- 1) Unzip this file into a directory 2) Run TUNSTALL 2) Edit the TUNNUKE.CFG file as warranted 3) Copy the file MACROS in your PFED installed directory into the directory you have installed this PPE ( Or copy the MACRO file provided by us to your PFED installed directory and use them instead) 4) In the file TUNBUL.TXT ( created by TUNSTALL for TUNLogon.PPE ) or whatever file you make your call to TUNLogonPPE, add the following line right after the line that calls TUNLogonPPE !drive:\path\TUNNUKE.PPE for Manual Installations ------------------------ 1) Unzip this file into a directory 2) Run TUNSTALL 2) Edit the TUNNUKE.CFG file as warranted 3) Copy the file MACROS in your PFED installed directory into the directory you have installed this PPE ( Or copy the MACRO file provided by us to your PFED installed directory and use them instead) 4) Somewhere during your logon process, add a call to this PPE like !drive:\path\TUNNUKE.PPE ============================================================================== ------------------------------------------------------------------------------ Setup Detail Docs ---------------------- Filename(s): PROMPT.PMT Path: \DISPLAY This is a standard ANSi/ASCii Text File Used As the Prompt for the user online to hit any key to continue. As a added bonus, we have thrown in one of our enhancement module PPE's and made a call to it with this file creating the flying ReaD THiS prompt. Filename(s): CHECKLOG.BBS Path: \DISPLAY This standard ANSi/ASCii File is displayed to the user online when the PPE first starts and scans the PFEDNUKE.LOG for any notices for that user Filename(s): TUNNUKE.FRM Path: \DISPLAY This standard ANSI/ASCii File is displayed to the user when a notice(s) is found. It is displayed to the user for each notice he/she has waiting. It is used in conjunction with all the *.BBS files listed below to create an entire effect Filename(s): FILENAME.BBS Path: \DISPLAY This standard ANSi/ASCii Text File is displayed to the user After the display file TUNNUKE.FRM. Right after displaying this file, TUNNUke.PPE will display the filename found in the PFEDNUKE.LOG notice for the user. *Note: In The DEFAULT screens provided in TUNNUKE.PPE, We made used of ANSi screen position codes to reposition the cursor to make it match where in the TUNNUKE.FRM file the information is displayed. If you were to use just a plain ASCii text file for this prompt like FILENAME -> TUNNuke.PPE would display the following to the user for a file called DELETED.ZIP which it found in the PFEDNUKE.LOG for that user notice FILENAME -> DELETED.ZIP Since the default *.BBS display files provided contain noting but ANSi cursor positioning codes, the PPE simply positions the cursor on the TUNNUKE.FRM screen displayed before them & displays just the filename Filename(s): BYTES.BBS Path: \DISPLAY This standard ANSi/ASCii Text File is used to display the BYTES information provided in the PFEDNUKE.LOG on the file listed in the user notice. Filename(s): USERNAME..BBS Path: \DISPLAY This standard ANSi/ASCii Text File is used to display the USERNAME information provided in the PFEDNUKE.LOG on the file listed in the user notice. Filename(s): ACTION.BBS Path: \DISPLAY This standard ANSi/ASCii Text File is used to display the ACTION TAKEN information provided in the PFEDNUKE.LOG on the file listed in the user notice. Filename(s): NOTE.BBS Path: \DISPLAY This standard ANSi/ASCii Text File is used to display the NOTE information provided in the PFEDNUKE.LOG on the file listed in the user notice. This would contain the pre-defined Macro string or input entered by the SysOp in Pfed for REASON GIVEN. Note, this string is also used by the PPE to decide if a form letter is available and should be displayed. Further details on FORM LETTER is available later in these docs. Filename(s): PFEDVER.BBS Path: \DISPLAY This standard ANSi/ASCii Text File is used to display the PFED Version information provided in the PFEDNUKE.LOG on the file listed in the user notice. Filename(s): DATE.BBS Path: \DISPLAY This standard ANSi/ASCii Text File is used to display the DATE information provided in the PFEDNUKE.LOG on the file listed in the user notice. FORM LETTERS ------------ A powerful feature of this PPE is its ability to display an addition SysOp definable FORM LETTER to expand on the reason a file was nuked, bonus given, or warning sent. It will work ONLY for the PRE-DEFINED macros you have setup for your PFED. For this reason, you MUST place a copy of the MACROS file found in your PFED directory into the installed directory of TUNNUKE.PPE TUNNUkePPE will search the MACRO file for a match on the reason a notice was sent, and if it is found, it will display a file based on the MACRO NUMBER as shown in PFED ( or the MACRO FILE ). So, For Example, your MACRO file may contain the following predefined macros ----------- [-NUKE-] 1)OLD GAME,-1 NO GAMES > 6 Months Of Age ! 2)ANCIENT,-1 NO FILES > 1 Year Old ! [-BONUS-] 1)REQUEST,-1 REQUESTED UPLOAD - THANKS! [-WARNINGS-] 1)FINISH,-1 PLEASE FINISH THIS UPLOAD A.S.A.P [-END-] ------------- If while you were in PFED, you nuked a file uplaoded by a user for nuke macro number 2 "NO FILES > 1 Year Old !", TUNNukePPE will look in the NOTE entry of the PFEDNUKE.LOG for the notice the user is geting, match it to nuke macro #2, and will display a standard ANSi/ASCii file found in the \NUKE directory called simply "2" ( no extension ). So, lets say, you nuked it for reason #1, "NO GAMES > 6 Months Of Age !", TUNNukePPE would match the STRING "NO GAMES > 6 Months Of Age !" in the users notice to the entry in the MACRO file, figure out it was macro 1, and display filename "1" found in the \NUKE directory. As with PFED, no more then 16 letters for each NUKE, BONUS, and WARNINGS may be used. All 16 macros DO NOT need to be defined, TUNNukePPE just will not display any additional information to the user since none exists. For this reason, if while in PFED, you manually type in a reason for NUKING a file ( or bonus, warning, whatever ), TUNNukePPE will not match it to any strings it finds in the MACRO file, thus, no form letter will be displayed. Filename(s): *. ( NO EXTENSION!) Path: \NUKE This standard ANSi/ASCii file displayed to the user when a match is made between the NOTE entry in the notice sent to the user and the Pfed MACRO file you copied to the PPE installed directory. Valid filenames are 1 - 16 matching of course, the macro number it is to represent. Use these files to redisplay rules on age limits of uploads, how to PKUNZIP -t, or otherwise as you see fit. Filename(s): *. ( No Extension ) Path: \BONUS This standard ANSi/ASCii file displayed to the user when a match is made between the NOTE entry in the notice sent to the user and the Pfed MACRO file you copied to the PPE installed directory. Valid filenames are 1 - 16 matching of course, the macro number it is to represent. Use these files to redisplay rules on age limits of uploads, how to PKUNZIP -t, or otherwise as you see fit. Filename(s): Path: \WARNINGS This standard ANSi/ASCii file displayed to the user when a match is made between the NOTE entry in the notice sent to the user and the Pfed MACRO file you copied to the PPE installed directory. Valid filenames are 1 - 16 matching of course, the macro number it is to represent. Use these files to redisplay rules on age limits of uploads, how to PKUNZIP -t, or otherwise as you see fit. ============================================================================== ------------------------------------------------------------------------------ REGISTRATION --------------- This PPE is NOT freeware. You are welcome to use it and pass it along to any/all your friends and boards you visit. To register this PPE, insure future updates, and removal the unregistered announcement send check or money order for $5 made to and addressed as listed below. *Please make sure to include the following information in order to get your serial number and activation code -The EXACT SysOps name as entered in PCBSETUP and the EXACT name of the board as entered in the PCBSETUP ( Note, Case Sensitive ! ) ( These are lines 94 and 2 respectedly in your PCBOARD.DAT file ) - Name Of The PPE you are registering - Your Board Telephone Number ( if required for below ) You may include a self-addressed stamped envelope for us to return your serial number and activation code to your if you wish a member of the TUNWarez Team to call and drop it off then 1) Create a user on your board called TUNWAREZ TEAM 2) Give that user any password you want. Include the password you create above, as well as any NUP or system password used by your system should we require it with your $5.00 Make Checks Payable To: Eric Lapham Address: TUNWarez Programming Team C/O 104 Johns Neck Road Shirley, N.Y. 11967 U.S.A. Your registration is limited to TUNNukePPE, TUNNukePPE Enhancement series Paks, TUNNukePPE Enhancement modules and TUNNukePPE Reg'ed User Enhancement modules. This offer is not good for other quality TUN_PPE's -------------------------------------------------------------------------------