home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR3
/
KPROT191.ZIP
/
KPROTECT.DOC
< prev
next >
Wrap
Text File
|
1993-10-10
|
13KB
|
240 lines
┌─────────────────────────────┐
│ Kill Protect 1.91 │
└─────────────────────────────┘
!!!! WARNING !!!!
!! This Program Is Designed for GT 16.00+ Specifically !!
!! Use on previous versions could prove hazardous to your system !!
──────────────────────────────────────────────────────────────
History
──────────────────────────────────────────────────────────────
01-11-92 Ver 1.0 Initial Release
01-12-92 Ver 1.1 Introduction of /F: Parameter (see below)
02-08-92 Ver 1.2 Fixed a small bug in reading of GTMDIR.BBS
Multiple message variables were not under-
stood in ver 1.0 and 1.1. For example....
if you had #^E:\GTMAIL\SYSOP, KPROTECT would
error out when opening MESSAGE.CTL.
12-06-92 Ver 1.3 Now compatible with the new QWK version of
GTMDIR.BBS. Added /REGISTER command line
parameter.
2-02-93 Ver 1.4 Bug Fix, corrected problem reading GTMDIR.BBS
2-21-93 Ver 1.5 Kprotect now understands a '#' flag in the
GTMDIR.BBS file.
7-21-93 Ver 1.6 Kprotect now provides loggins support, as
requested by Jim Knight. Along with the log
support comes two new command line parameters
/L /NL. /L tell Kprotect to turn on the
logging feature and create a
<GTPATH>\HOTWARE\KPROTECT.LOG. /NL also turns
on the logging feature but will create a NEW
LOG thus overwriting any information that may
be contained from a previous log.
7-24-93 Ver 1.7 Bug Fix in the Msg Couting logic. KPROTECT
was counting the SYS CTL entry in the
MESSAGE.CTL as a valid message.
8-15-93 Ver 1.8 Added logic to make sure messages in a public
message area are all public. Likewise to make
sure that a private message area has all
private messages. These messages will be
converted if they are incorrect. If a message
has a pesky little Re: starting the subject,
like so many readers like to apply, it will be
removed. Both of these new options are
optional and can be turned off with new command
line switches. /NFC or "No Flag Convert" will
tell the program NOT to convert messages from
public <> private. /NSC or "No Subject Change"
will tell the program to leave the Subject
intact.
9-14-93 Ver 1.9 Kprotect now creates a work copy of the
GTMDIR.BBS prior to execution. This allows
KPROTECT to work in Multitasking Environments
where multiple programs are accessing the
GTMDIR.BBS. The work file will be placed in
the <GTPATH>\HOTWARE directory and
automatically removed after execution
completes.
10-10-93 Ver 1.91 Corrects a small problem with the REGISTER
feature. The SYSOP.BBS file, which is where
the name is found for the FROM: field of the
registration message, will now be searched for
in 1. The GTPATH, 2. The DOS PATH, and finally
3. The BBSCBS path as found in the GT.CNF.
──────────────────────────────────────────────────────────────
What is It?
──────────────────────────────────────────────────────────────
A simple little program that will go to each message area
listed in your GTMDIR.BBS file and "Kill Protect" each message
that is not currently either "Private" or "Kill Protect".
This program will also convert any Public messages in a Private
only message area to Private. It will also convert any Private
messages in a Public only message area to Public.
At the end of each execution you will be given a report on,
1. The total number of messages available on your system, 2.
The total number of "Kill Protected" messages on your system,
3. Total number of "Private" messages on your system, 4. Total
number of message areas found in your GTMDIR.BBS file, 5. Total
number of message areas that were successfully processed, 6.
The total number of unsuccessfully processed message areas, 7.
Total number of messages converted Public <> Private, 8. Total
number of messages that were converted to "Kill Protect"
status on this execution of KPROTECT.
──────────────────────────────────────────────────────────────
Why Is It?
──────────────────────────────────────────────────────────────
You may be asking about now, Why would you want to do this?
It's simple. On my system, all "Public" messages default
to "Kill Protect" when they are entered. Unfortunately not
all systems in the GT Network are not this way. Therefore
messages arriving in echos that are not marked "Kill Protect"
are often deleted by users as they read the echos. By marking
all NON-Private messages as "Kill Protect" the messages will
remain in the echo areas for others to read. Besides, my
nightly maintenance is very efficient at removing out of date
messages for me automatically.
──────────────────────────────────────────────────────────────
Registration
──────────────────────────────────────────────────────────────
I am not requesting any money for this program, but I would
not turn any down either <g>. If you want to slip $5.00 into
and envelope I'll accept it. Although I don't require a
registration fee I would appreciate knowing that you are using
the program on a normal basis. Therefore I have provided a
simple and easy way for you to register this program. From
the DOS prompt type:
KPROTECT /REGISTER
Kill Protect will the proceed to send me a netmail message informing
me that you are using the program. Please use this feature ONCE.
──────────────────────────────────────────────────────────────
Execution..
──────────────────────────────────────────────────────────────
Running the program is very easy. The only things that are
required are 1. A valid GTPATH statement, and a valid GTMDIR.BBS
file in the directory pointed to by GTPATH. KPROTECT takes care
of the rest of it. It reads each line of the GTMDIR.BBS file
and takes appropriate action on each message area. The program
is intended to run daily either during your nightly maintenance
or after any mail run. I personally run the utility after each
run of MDIST, just to pick up any stray "Un Kill Protected"
messages that should arrive. If you would rather specify a
filename other than GTMDIR.BBS you may use a /F: parameter on
the command line of KPROTECT. For example....
KPROTECT /F:C:\TESTING\ALTERNATE.BBS
This would read information from a file named ALTERNATE.BBS
located in C:\TESTING. This file MUST be in the same format
as the GTMDIR.BBS file.
If you would like Kill Protect to keep a log file for you, you may
use one of two parameters /L or /NL. /L will simply turn on the
logging feature and APPEND to any existing log information. /NL
or NEW LOG will erase any old log files and start a fresh new one.
The LOG file will be placed in <GTPATH>\HOTWARE\KPROTECT.LOG.
Here is an example of what you will find in the log.
Kill Protect Started: 7-21-1993 21:44
Message Area Totl Msgs Start Msg # End Msg # Totl Chng
-------------------------- ----------- ------------- ------------ -----------
General Public Messages... 1 0 0 0
Private E-Mail............ 1 0 0 0
Private Sysop Mail........ 33 1 47 0
Netmail Message Area 73 1 170 0
HOTware Support and Sugges 18 50 71 0
*----------------- Kill Protect Execution Statistics -----------------*
Messages Inspected Kill Proof Messages Private Messages
551 436 115
Total Message Areas Sucessful Areas Aborted Areas
5 5 0
Total Messages Kill Protected This Run
0
*-----------------------------------------------------------------------*
If you do NOT want Kill Protect to convert Public messages to Private
in a message area marked Private Only, or if you do not want it to
convert Private messages to Public in a Public only message area then
you can place a /NFC on the command line as follows:
KPROTECT /NFC
The Kill Protect default is to convert these messages as needed.
If you do NOT want Kill Protect to remove those pesky little Re:
additions to the Subjects of messages then you can use a /NSC on the
command line as follows:
KPROTECT /NSC
The Kill Protect default is to remove this little additions that so
many offline readers like to apply.
──────────────────────────────────────────────────────────────
Errorlevels
──────────────────────────────────────────────────────────────
Here are the possible errorlevel exits the program will give.
ERRORLEVEL 0 No Problems, Good Run.....
ERRORLEVEL 1 GTPATH Environment not Set.
ERRORLEVEL 2 Cannot Find GTMDIR.BBS in GTPATH.
ERRORLEVEL 3 CTRL-BREAK Pressed
──────────────────────────────────────────────────────────────
Who Is Responsible for This?
──────────────────────────────────────────────────────────────
Rob Roesch
The HOTware BBS
GT Power Net-Node 064/003
Rt 7 Box 566
Mocksville, NC 27028
704-492-2081 (USR 16.8 DS)
If you start using this utility, and get a chance, let me know
what you think of it. If you don't have any use for it, delete
it for your total refund of all the disk space that it was
occupying. This program comes with no warranty, no guarantee,
and no promises. If it works GREAT, if not let me know and I
will gladly take a look at it in my spare time. If you really
really really like the program and want to make any donations,
feel free, but it is not a requirement.....
──────────────────────────────────────────────────────────────
Alternate Distribution Sites
──────────────────────────────────────────────────────────────
The HOTware Utilities now have alternate Distribution
Centers for your convenience. The following BBS always
have the latest and greatest HOTware utilities online and
available for download.
BBS Name BBS Phone Location GT Net/Node Hours
┌──────────────────┬───────────────┬────────────────────┬───────┬──────────┐
│ Laboratory 386 │ 618-549-2322 │ Carbondale IL │064/400│ 10pm-8am │
└──────────────────┴───────────────┴────────────────────┴───────┴──────────┘
EOF