home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
s
/
status24.zip
/
STATUS.DOC
< prev
next >
Wrap
Text File
|
1992-01-07
|
16KB
|
345 lines
Network Mail Status (Postlink Software Version)
=================================================================
First off I would like to thank those users who offered
suggestions and made comments. Some functions/diplays are the
result of this imput.
This program generates a network import mail status bulletin
showing each conference, 1000 maximum, and the total number of
messages imported for current date and total to date for each
conferences, the last import date and the total messages to date
for the specified network. Also generates last import bulletin
showing imported current date as well as total to date.
It also generates a network export mail status bulletin with
the same format as the above import bulletin. Since the export
routine contains all conference names it is run first to get
those names so that conferences with zero imports are still
displayed in the import bulletin. I could not find another way to
get all conference names.
Supports multiple networks. This program uses Postlink's
export / import log(s). It does a monthly rollover of the LOG(s)
using PKZIP.EXE. There is an eighteen character limit on
conference names, names longer than that are truncated.
Starting with version 2.4 there are major changes in the way
the program runs. Command line parameters have changed once again
and options are now in a nine line configuration file. Requires
registration to remove "Unregistered BBS" from bulletins.
This archive should contain the following files:
STATUS.EXE............ Actual program
STATUS.DOC............ This file
STATUS.CFG............ Sample configuration file
STATUS2.CFG........... Sample configuration file
STATUS3.CFG........... Sample configuration file
READ.ME............... Update/changes information
STATUS.BAT............ Sample batch file
FILE_ID.DIZ........... BBS description file
SUPPORT.TXT........... Location of Support BBS
Syntax is pretty straight forward:
STATUS STATUS.CFG
"STATUS.CFG" and be the name of any configuration file with
the following format:
(1) Unregistered BBS
(2) 0000
(3) Postlink
(4) C:\POST1.LOG
(5) C:\BLT7
(6) C:\POST2.LOG
(7) C:\BLT77
(8) C:\BLT777
(9) PCB
.CFG line #1
"Unregistered BBS", system name if registered
.CFG line #2
"0000" serial number if registered.
.CFG line #3
"Postlink" should be the name of the actual network you are
using, one word and case sensitive. 18 characters max, longer
names are truncated. Say you are making two different network
mail runs with the same software, you would use those names here,
each in it's own configuration file.
.CFG line #4
"C:\POST1.LOG" is the path and name of your Postlink Export
log. Lines #4 and #6 can contain the same file name if your
Export and Import logs are in one file.
.CFG line #5
"C:\BLT7" is the path and name for your Export bulletin.
.CFG line #6
"C:\POST2.LOG" is the path and name of your Postlink Import
log. Lines #4 and #6 can contain the same file name if your
Export and Import logs are in one file.
.CFG line #7
"C:\BLT77" is the path and name for your Import bulletin.
.CFG line #8
"C:\BLT777" is the path and name for your Last Import
bulletin.
.CFG line #9
Color and characters used are as follows and are setup to
give the sysop as much control over the output as possible. Not
all users can read and handle IBM extended graphic characters
(like sight impaired users and voice hardware). Program can use
either "=/-" or IBM's extended graphic characters "═/─". Line #9
should contain one of the following options:
"PCB" use IBM extended graphic characters and PCBoard's @X0
colorizing codes.
"PCB0" use no IBM extended graphic characters and PCBoard's
@X0 colorizing codes.
"ANSI" use colorizing and no IBM extended graphic
characters.
"ANSI2" use colorizing and IBM extended graphic characters.
"ASCII" use no colorizing and no IBM extended graphic
characters.
"ASCII2" use no colorizing and IBM extended graphic
characters.
PKZIP.EXE used by the Status Program
"PKZIP.EXE" must be somewhere in your path or in the current
directory. When the month changes in the export/import.log the
program archives the current log into a file using 'ML'+ the
current date (ML010193.ZIP, etc.). It also includes the current
logs (1 or 2), all three bulletins, and writes it out to the
directory that contains the log file. The program then rewrites
the log using only the current new month's data. This way there
is only one month's log data in your Postlink log(s). The
bulletins are added to the archive so that sysops wanting to see
totals would have the last ones generated prior to the rollover
without having to do so manually.
If you do not want the previous month's log(s) simply delete
the archive from your hard drive. In your calling batch file you
can add "IF EXIST ML*.ZIP DEL ML*.ZIP" and this will auto-delete
the archive. If there are no imported/export4r messages on the
day of the rollover then a bulletin reflecting same is generated.
There must be at least one meg of free disk space for the archive
to be executed. I have no idea the possible sizes and if anyone
has problems with the archive with one meg as the minimum please
let me know and I will increase the size of the free space
needed.
It should be noted that when you start using Status if your
Postlink log(s) are not the current month's logs that they will
not roll over until the month rolls over inside the log. Say your
log(s) are dated 01-15-93 and you start using Status in 02-93, no
messages since 01-15-93, the log will still show the messages
imported up till 01-15-93. If your log contains multiple months
of logs when it rolls them over you will only end up with the
previous month's log, the others will have been over written by
the last one in the archive. Either that or you can archive the
log(s) and delete everything up to the current month before you
run Status for the first time.
If you are making two or more DIFFERENT network mail runs
the only thing you must do is make two or more different
POSTLINK.CFG files, one with the name of the LOG file for each
network so that ALL logs are not put into one file. I would have
no way of knowing what messages came from what network in order
to separate them. You would then just have a TEMP1.CFG, TEMP2.CFG
and when you call postlink you just copy TEMP1.CFG POSTLINK.CFG,
then on next run you might copy TEMP2.CFG POSTLINK.CFG, etc.
A simple batch file might look like one of these:
CD \POSTLINK
COPY TEMP1.CFG POSTLINK.CFG
POSTLINK CALLER.CFG
STATUS STATUS.CFG
CD \POSTLINK
Copy TEMP2.CFG POSTLINK.CFG
POSTLINK CALLER2.CFG
STATUS STATUS2.CFG
Perhaps you want to make a bulletin with the PCBoard @X0
codes and one using straight ASCII codes and yet another using
ANSI codes. The .CFG files would contain the bulletin names and
the form setting (#9):
STATUS STATUS.CFG
(.CFG with PCB, uses ANSI codes and IBM extended graphic
characters)
STATUS STATUS2.CFG
(.CFG with ASCII, ASCII and no IBM extended graphic
characters)
STATUS STATUS3.CFG
(.CFG with ANSI, ANSI colors and no IBM extended graphic
characters)
You just call STATUS as many times as needed, with as many
.CFG files as needed, to generate whatever formats you want. On
my 386/33 it takes less than twenty seconds to run the program on
a 6,500 line test log (from three BBS systems).
If you don't like the program please write to me and explain
why. Send me any suggestions you might have. If they enhance the
overall program I will try to incorporate part, some, all, in the
next release.
Current versions (01-04-93) of James Huckabey door/Postlink
programs. The doors are Door Patch 3.8 doors and now support the
following BBS drop files: DOOR.SYS, PCBOARD.SYS, SFDOORS.DAT,
CALLINFO.BBS, DORINFO1.DEF, DORINFO2.DEF and CHAIN.TXT. Converter
needed for other BBS software. Current releases also reflect a
reduction in registration fees. Send me a diskette covering one
meg, with return postage, and I will return it with all my doors
and Postlink software on it/them and as any of my other software
programs that might fit in any free space.
BBS Doors:
BK14-400 ZIP Book Review door
BR14-300 ZIP BBS Review door
CS14-500 ZIP Community Service door
DR14-300 ZIP BBS Door Review door
GO14-400 ZIP Gotcha game door (enhanced)
GTPL-400 ZIP GT Power List door for GT Power BBS
MR14-300 ZIP Music Review door
MV14-300 ZIP Movie View door
PCOVE501 ZIP Pirate's Cove game door (all new release)
RR14-400 ZIP Restaurant Review door
TRLD-901 ZIP The Rime List Door (name change from PCRL)
SW14-600 ZIP Software Review door
WR14-300 ZIP Wine Review door
Postlink:
LT100392 ZIP Lasttime, Generates bulletin when successful
Postlink mail transfer. Supports ASCII, ANSI and
PCBoard codes. Freeware! (not a door). Filename is
compile date.
STATUS24 ZIP Generates Postlink bulletin showing total messages
to date for each conference, total conferences,
total messages, and monthly rollover. Optional last
import mail transfer bulletin. Supports straight
ASCII, ANSI and PCBoard colorizing. Registration
If you find this program useful please send BBS information
and one of the following in U.S. funds only:
Registration only.................................. $10
(outside U.S. please add $2)
Registration and latest version.................... $12
(outside U.S. please add $3) Include diskette size.
I had expected support without having to resort to a
registration system, but of course I was wrong. I just put too
much time and effort into this program to release it as freeware
like I did my Lasttime program. The program package represents
many long hours of programming, testing, updating and more
testing, as well as LD telephone calls to get it tested or
distribute the beta and release copies. Please support my efforts
and register your copy.
FROM:
Name:
---------------------------------------------------
Address:
---------------------------------------------------
City:
---------------------------------------------------
State & Zip:
---------------------------------------------------
HUB ID: NODE ID:
---------------------- --------------------
Phone(voice): (data)
--------------------- ---------------------
Diskette type if registration includes current version
(360, 1.2, 720, 1.44) ---------
Version number you have if registration includes current version.
If you have current version your version request fee will be
returned.
---------
Please supply name of BBS to be added to program. It may
include other data up to sixty characters. Anything longer than
that will be truncated, no exceptions. This is to be on one line
of code and must be legible since the serial number is based on
exact syntax. I cannot be responsible for unreadable data. Please
print. Case sensitive!
Example: "Jim's Graphic BBS". In Status it comes out as the
following in all bulletins generated (example is no IBM extended
graphic characters):
==================:Jim's Graphic BBS:==================
---------------------------------------------------------------- Your registration number, and diskette if requesting current
version, are be sent by return mail.
James Huckabey
3621-A Fraser Street
Bellingham, Washington 98226 U.S.A.
(206) 671-2868 (voice) I do have a USR 14.4 DS!
You can also contact me at:
Corporate Headquarters BBS
Sysop: Bob Neal
RelayNet (tm): CHQBBS (#1255)
(815) 886-3233 / (815) 886-9381 (14400 V32bis)