JAMPACK.EXE - JAM Message Base packer for T.A.G. 2.7c
(c) Copyright 1994,1995 by Mark McKay,
The Skeleton Closet BBS (Mark & Debbi McKay sysops),
1:275/138,139,140 (804-671-8547,804-499-5150,804-473-2217)
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Disclaimer/Legal Stuff ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
Although this program has been tested, this software has no warranty,
either expressed or implied. The use of this software is at the user's own
risk. Mark McKay shall in no way be responsible for any special, incidental,
consequential or other damages resulting from the use and/or misuse of this
software. Every effort has been made to test this software and its
documentation for possible errors, but no guarantee to that effect is made.
This program must be distributed AS IS in it's original archive. This
program may not be distributed as part of any other software package without
the expressed written consent of the author, Mark McKay. It may not be
altered or reverse engineered in any way, shape or manner.
The usual I don't promise it will do anything and if it messes up/you mess
it up, you own the pieces. If you use it, you alone are liable for the
results.
THERE WILL BE NO FURTHER UPDATES TO THIS PROGRAM. IF IT WORKS FOR YOU GREAT!
IF NOT, OH WELL. SUPPORTING THIS PROGRAM ISN'T WORTH THE HASSLE. IF YOU
CAN DO BETTER OR FIND BETTER, GO FOR IT.
I apologize to the 2 people who registered it previously.
JAM(mbp) - Copyright 1993 Joaquim Homrighausen, Andrew Milner,
Mats Birch, Mats Wallin.
ALL RIGHTS RESERVED.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Why even have JAMPACK? ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
Because as of February 4, 1995 there are STILL no real working JAM message
base packers for any BBS that I can find. MBButil and RemoteAccess's RAMSG
programs claim to work, but don't do as advertised on my system anyway.
Also you only have to run JAMPACK once, not with a PURGE then PACK
parameter.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Quick Notes ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
1. JAMPACK has no prompts and is intended to be run from a batch file
unattended. I made it colorful because I can't stand plain dull
grey and subconsciously you think the program runs better if it
looks slicker.
2. JAMPACK creates JAMPACK.LOG to tell you what it did. Keep an eye on
the size of this file. It gets big quickly.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Setup ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
These docs are really short, but hopefully not that complex. This program
is intended to be simple to setup. All you do is the following:
1. Unzip JAMPACK9.ZIP into your DATAFILES DIRECTORY, the directory where
your MBOARDS.DAT is located.
2. Copy MBOARDS.DAT to MBOARDS.BAK. (If you don't JAMPACK will for you).
3. Run MBEDIT.EXE or MBEDIT1.EXE (MBEDIT1 is faster because it doesn't show
how many messages are in each area) and edit the following for each area:
1. number of days worth of messages to keep per area
2. Maximum number of messages to keep in each area.
3. Whether to pack that area by number of days or number of messages
4. Run JAMPACK
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ What does this thing do? ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
JAMPACK is a JAM message base packer written exclusively for T.A.G. BBS
sysops. It does the following:
1. Looks for your MBOARDS.BAK in the same directory as JAMPACK.EXE.
2. It opens MBOARDS.BAK and reads it area by area.
3. If the area is a JAM style base it does the following.
a. Checks the temporary directory it will make and kills any preexisting
JAM files. (we don't want to add to an existing one, it defeats the
whole purpose of JAMPACK).
b. It checks for enough free space to make a new base (the size of
the current area JAM files + 20K).
c. If there is enough space free, JAMPACK creates a temporary directory
off of the jam directory for the current area named JAMPCK. If there
is not enough disk space for THAT area or there are no JAM files
JAMPACK skips the area. If you are short on diskspace larger areas
may be skipped but the smaller ones may get packed.
d. If the area is set for "Number of Messages" JAMPACK does the
following:
If "Number of Messages" in MBEDIT is 0 then the area is skipped.
JAMPACK counts the number of active messages in the JAM base. If
this number is greater than the MaxMsgs for the area in MBOARDS.BAK
then the starting point is calculated as the high message number
minus the MaxMsgs in the MBOARDS.BAK. If this number is less than
one or one then the area will be skipped. Then JAMPACK reads the JAM
messages one by one, (from the start point calculated above) and if
the message isn't marked as deleted then it is rewritten to the JAM
Base in the new directory. Lastread pointers are updated as
necessary.
If you have messages marked as deleted, you will end up with less
than the maximum number.
e. If you the area is set for "Number of days" then JAMPACK does the
following:
If "Number of Days" in MBEDIT is 0 then the area is skipped.
JAMPACK reads the JAM messages one by one. If the message date is
newer or equal to (the date the message was received) the number of
days specified in the MBOARDS.BAK and not marked as deleted then it
is rewritten to the JAM Base in the new directory. Lastread pointers
are updated as necessary.
f. Once the area is done the original JAM files are deleted and the
new JAM files are renamed to the same as the old. (It's faster
than copying then deleting them and they're on the same drive
anyway.)
4. The process is continued until the end of your MBOARDS.BAK is
reached.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Command Line Parameters ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
There are none as of JAMPACK 8.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Registration ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
JAMPACK is now free for use, but the author retains all copyrights.
Due to the flack I took for JAMPACK because of a bug in TAG 2.7C, this
is THE LAST VERSION you will ever see. It's not worth the BS.
Bugs or not, this is THE LAST VERSION.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ History ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
1.00 - September 4, 1994 - Initial release
1.01 - September 5, 1994 - Cosmetic changes
Added updating lastread pointers (oops)
1.10 - September 7, 1994 - Wrote MBEDIT (never released)
1.20 - September 9, 1994 - Rewrote MBEDIT and JAMPACK to use MBOARDS.BAK
instead of MBOARDS.DAT.
JAMPACK now reads MBOARDS.BAK for number of days
in each area and can keep seperate numbers of
days messages in each area.
Now reads areas one by one and closes the MBOARDS
file instead of leaving it open the entire time.
2.00 - November 19, 1994 - Added packing by number of messages.
Changed JAMPACK to use -D mode or -M mode.
2.02 - November 30, 1994 - Fixed bug in v2.00 that only gave you usage
screen no matter what you did.
Updated MBEDIT to show days and number of msgs
on main list
2.03 - December 2, 1994 - Minor changes, never released.
2.04 - December 4, 1994 - Major rewrite of JAMPACK, "should" fix any
problems with previous versions.
2.05 - December 20, 1994 - No major changes, just cosmetic stuff.
Added MBEDIT1 because MBEDIT takes forever to load
2.06 - January 7, 1995 - Made minor changes to Lastread pointer checking
increase speed.
Spent hours looking for "missing subjects", can't
see anything wrong with JAMPACK.
2.07 - January 12, 1995 - Rewrote MBEdit to use one of MBoards.Dat (Bak's)
boolean types for number of days mode/number of
messages mode. JAMPACK modified to no longer
need to use commandline parameters, each area is
configurable.
3.00 - January 14, 1995 - Made a few display, logging additions.
Slightly changed the look of JAMPACK.
Spent MANY, MANY, MANY, MANY, MANY, MANY, MANY
hours looking for the dreaded "missing subjects"
that appeared magically with T.A.G. 2.7C, still
can't see anything wrong with JAMPACK. It
just reads the old one and writes the new one.
3.01 - February 4, 1995 - Added FJAMPACK.EXE, a faster, no-frills version
of JAMPACK.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Alledged Problems ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
1. JAMPACK puts weird numbers for user number in the lastread file.
It's not JAMPACK, JAMPACK only reads it from the old Lastread file and
updates the new file with the new lastread message number.
The lastread field of the .JLR file is supposed to be a "longint", other
programs (I suspect TAG) may be using "word" or "integer" types which may
be causing the problem.
2. JAMPACK is erasing the Subject in Echomail areas.
JAMPACK only reads the old one and rewrites the new one.
The subjects are still there, the problem is in TAG 2.7C.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘