旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � � � 靈컴컴컴왜커 靈왜컴컴컴왜컴컴컴왜컴컴커靈컴컴커 靈커 � � � 米 米 낳 � � 낳 旼캠 넛� 旼� 낳 旼컴暮 旼캠 � 獺 � � � � 낳 낳 낳 � � 낳 읕캭 � � � � 낳 읕� � 읕캭 � � � � � � 낳 낳 낳 � � 낳 旼� 粕 � � � 낳 旼� � 旼� 粕 � � � � � 낳 낳 낳 읕� 낳 � � 읏笭 읕� 낳 읕컴옌 � � 읏 笭 읏 � � 聃夢켸聃夢컴컴켸聃� 聃켸聃컴컴켸聃컴컴夢켸 聃켸 聃컴� � � model c � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 a utility for pcboard and netmail doors [ this version supports qmail4 and kmail doors ] [ other mail door support coming soon ] 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 Steve Leigh - the Tower Club - Tampa, Florida - 813-971-2934 HST/DS 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 These docs will help you get a quick start with Murder1. There's almost nothing to using Murder1, other than calling it from your $$LOGOFF batchfile. Please pay particular attention to all references to the CALLER file. �袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴敲 � A special thank you to Cam DeBuck, author of PCBPack. � � Without PCBPack, we wouldn't stand a chance against duplicate messages. � 훤袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴� Murder1 is ShareWare �袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴敲 � Try Murder1.... if it does what you need and it works for you, then you � � should register it. Many hours went into this program. It's been � � enhanced to the point where you can just "set it and forget it". It � � will take care of your dupe messages without any intervention, and, if � � you should change your conferences message areas, Murder1 will adjust. � � Registration -completely- disables the shareware screen and delay. � � � � Please send $15 registration to: � � � � Steve Leigh � � 15124 North 18th Street Thank You! � � Lutz, Florida 33549 � � Voice support for registered users: 813-971-5334 � 훤袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴� What the Murder1 process does: ------------------------------ * Read in from your CALLERx file, and determine if messages were uploaded via your mail door. * If so, determine which conferences messages were uploaded in. * Write a batchfile instructing PCBPACK to pack ONLY those message bases which were uploaded to, and kill any duplicate messages, with optional logging. * Run the created batchfile to kill duplicate messages. * Append the CALLERx file to a master caller log. * Delete the CALLERx file, ready for the next caller. * Recycle the board. A few basic ground rules apply here, so please become familiar with them. � Both MURDER.EXE and PCBPACK.EXE -MUST- be in your system path. However, it is not necessary that either be in your \PCB subdirectory. � You should have only -ONE- $$LOGOFF.BAT file. More are not necessary, and could create a problem. However, the $$LOGOFF batchfile must be in your system path. � You must define a "secondary" caller log if you intend to keep a log of your callers. Murder1 expects to find a SINGLE caller entry in your caller log. The reason for this is to reduce the board's cycle time, as well as the amount of code. It's actually transparent, so no need to get upset! Read this part carefully to understand how to implement this: Let's say you have defined your caller log in PCBSM as C:\PCB\MAIN\CALLER In your $$LOGOFF.BAT file, at the -very end- you would add these 2 lines: 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � TYPE C:\PCB\MAIN\CALLER >> C:\PCB\MAIN\CALLER.LOG � � DEL C:\PCB\MAIN\CALLER � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� That's all there is to it. In this way, your -real- caller log is now named CALLER.LOG instead of CALLER, and the actual CALLER file is deleted after each caller, so the next caller begins with a fresh log. As you can see, as soon as the caller logs off, his caller log will be added to your CALLER.LOG, then erased. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � **Note: If you have a multi node system, just use these lines instead of � � those above: � � � � TYPE C:\PCB\MAIN\CALLER%PCBNODE% >> C:\PCB\MAIN\CALLER%PCBNODE%.LOG � � DEL C:\PCB\MAIN\CALLER%PCBNODE% � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � Suggestion: If you have any utilities which look for your CALLER logfile, you could change a line in PCBSM and create a different temporary file, rather than change the utilities. For example, change PCBSM to C:\PCB\MAIN\CALL, then at the end of your $$LOGOFF batchfile just append CALL to CALLER. In this way, you will retain the filename (CALLER) for your utilities, since the temporary file is only on disk for the duration of a single call anyway. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 Here is a working sample of a $$LOGOFF batchfile for a single node system: 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � @echo off � � if exist MURDER.BAT del MURDER.BAT � � MURDER � � � � call MURDER.BAT < note the "CALL" for a "batch within a batch" � � � � type c:\pcb\main\CALLER >> c:\pcb\main\CALLER.LOG � � del c:\pcb\main\CALLER � � del MURDER.BAT � � %PCBDRIVE% � � cd %PCBDIR% � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 Here is a working sample of a $$LOGOFF batchfile for a multi node system: 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � @echo off � � if exist MURDER%PCBNODE%.BAT del MURDER%PCBNODE%.BAT � � � � MURDER � � � � :PROCESS_MURDER � � if exist c:\pcb\USERS.SYS goto LOOPER < test for user in mail door � � if exist i:\pcb\USERS.SYS goto LOOPER < test for user in mail door � � if exist j:\pcb\USERS.SYS goto LOOPER < test for user in mail door � � if exist k:\pcb\USERS.SYS goto LOOPER < test for user in mail door � � � � call MURDER%PCBNODE%.BAT < note the "CALL" for a "batch within a batch" � � goto end � � � � :LOOPER � � timechek /PAUSEFOR=00:00:15 < 15s delay to exit mail door on other nodes � � goto PROCESS_MURDER � � � � :END � � type c:\pcb\main\CALLER%PCBNODE% >> c:\pcb\main\CALLER%PCBNODE%.LOG � � del c:\pcb\main\CALLER%PCBNODE% � � del MURDER%PCBNODE%.BAT � � %PCBDRIVE% � � cd %PCBDIR% � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 Important Points about the Environment: Murder1 has been tested with PCBoard 14.5/D, 14.5/E3 and 14.5/E6. It adapts itself to either type configuration; ie: when PCBNODE is present, it is used, or, in the case of a single node system, 14.5/D, the PCBNODE variable is ignored. Murder1 looks to the environment to locate the data files it must read. These environment variables are initialized by PCBoard as it loads a door. Please note: Murder1 cannot run -until- the PCB environment variables have been set. All the environment variables may not be set until a door program is actually loaded. Try this: load PCBoard, then load a door, then exit to DOS, issue the SET command, and you should see something like this: PCBDRIVE=C: PCBDIR=\PCB PCBDAT=C:\PCB\PCBOARD.DAT PCBNODE=1 Since PCBoard sets these variables when loading a door, you can go ahead and add them to your BOARD.BAT file or your AUTOEXEC.BAT file. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� Checklist for installing Murder1: � - adjust your $$LOGOFF batchfile to run MURDER.EXE and then to call MURDERx.BAT (remember the call statement) � - type (append) secondary caller file, then delete it at the end of $$LOGOFF batchfile � - MURDER.EXE and PCBPACK.EXE must be in your system path As you can see, all the setup work is done in your $$LOGOFF batchfile. Murder needs -no- configuration files, or setup programs. Additionally, (multinode sysops), if you choose to, you can delete the LOOPER label shown above which tests for a user on another node. I have tested the process without the LOOPER delay, and PCBPack will, at worst, simply skip a conference during the pack process. Which leads to that basic axiom: �袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴� � "If the washin' don't getcha, the rinsin' will!" � 훤袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴暠 ..and the skipped conference will be packed NEXT time a caller uploads to it. That should wrap it up .... I hope Murder1 is a useful program for you! Steve Leigh 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴�