home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Professional
/
OS2PRO194.ISO
/
os2
/
com
/
bbs
/
maxlog20
/
maxtools.doc
< prev
next >
Wrap
Text File
|
1993-03-12
|
62KB
|
1,490 lines
██████████████████████████████████████████
██ █░░░░░░░██
██ MaxTools █░░░░░░░██
██ █░░░░░░░██
██ 16 Separate Utilities █░░░░░░░██
██ For █░░░░░░░██
██ Maximus System Operators █░░░░░░░██
██ █░░░░░░░██
██ Version 1.03 █░░░Θ░░░██
██ █░░░Θ░░░██
██ (Copyright 1992-93) █░░░░░░░██
██████████████████████████████████████████
< ALL RIGHTS RESERVED >
MaxTools is a Copyright of Michael Jones
Maximus is a Copyright of Scott Dudley
4DOS is a Copyright of Rex Conn & JP Software Inc.
MaxIPC is a Copyright of Peter G. Zion
Catdisk is a Copyright of Rick Hillier
Netware Lite is a Trademark of Novell, Inc.
Lantastic is a Trademark of Artisoft, Inc.
Desqview is a Trademark of Quarterdeck Office Systems
OS/2 is a Trademark of IBM Corporation
Special thanks to:
Thomas Stubbs FidoNet: 1:133/125
Tom Lane FidoNet: 1:382/91
Graham Tippett FidoNet: 1:351/1116
John Howard FidoNet: 1:244/112
David Cole FidoNet: 1:129/179
Leon Lynch FidoNet: 1:262/3
Stephane Seguin FidoNet: 1:163/16
Evin Mulron FidoNet: 1:350/501
Table of contents
1 LEGAL NOTICE . . . . . . . . . . . . . . . . . 1
2 Preface . . . . . . . . . . . . . . . . . . . 2
2.1 System requirements . . . . . . . . . . . . . 2
2.2 Message area requirements . . . . . . . . . . . 2
3 Installation . . . . . . . . . . . . . . . . . 2
3.1 Creating the MaxTools subdirectory . . . . . . . . 2
3.2 Setting the maximus environment variable . . . . . . 3
4 MaxTools Log File . . . . . . . . . . . . . . . 3
4.1 Creating the log file . . . . . . . . . . . . 3
4.2 Log file usage . . . . . . . . . . . . . . 3
4.3 Log file format . . . . . . . . . . . . . . 4
5 Error Levels . . . . . . . . . . . . . . . . . 4
5.1 Error levels which MaxTools uses . . . . . . . . 4
6 MA & FA . . . . . . . . . . . . . . . . . . . 4
6.1 Displaying message areas . . . . . . . . . . . 4
6.2 Displaying file areas . . . . . . . . . . . . 5
7 MakFM For CD ROM SysOps . . . . . . . . . . . . . 5
7.1 Rotating out CD's. . . . . . . . . . . . . . 5
7.2 Displaying offline status . . . . . . . . . . . 5
7.3 Editing Max.Ctl . . . . . . . . . . . . . . 5
7.4 Running MakFM . . . . . . . . . . . . . . . 6
7.5 File menu output formats . . . . . . . . . . . 6
8 MakMM For Scanning Private Mail Only . . . . . . . . . 6
8.1 Editing Max.Ctl . . . . . . . . . . . . . . 6
8.2 Running MakMM . . . . . . . . . . . . . . . 7
8.3 Message menu output formats . . . . . . . . . . 7
9 FBSD For adding/deleting file sizes & dates . . . . . . . 7
9.1 CD-ROM support. . . . . . . . . . . . . . . 7
9.2 Formatting an all files list . . . . . . . . . . 7
9.3 Running FBSD . . . . . . . . . . . . . . . 8
9.4 Other considerations . . . . . . . . . . . . 8
10 MAXMENU For displaying complex ANSI screens . . . . . . . 8
10.1 ANSI Welcome screens . . . . . . . . . . . . 8
10.2 The optional more?[yn=] prompt . . . . . . . . . 8
10.3 Call back when you are there!. . . . . . . . . . 8
10.4 When a user hangs up on MaxMenu . . . . . . . . . 9
10.5 Local mode and baud rate simulation. . . . . . . . 9
10.6 Running MaxMenu Setup . . . . . . . . . . . . 9
Handshaking. . . . . . . . . . . . . . . . 9
Parity . . . . . . . . . . . . . . . . . 9
Word length. . . . . . . . . . . . . . . . 9
IRQ . . . . . . . . . . . . . . . . . . 9
10.7 Running MaxMenu . . . . . . . . . . . . . . 10
Port . . . . . . . . . . . . . . . . . . 10
Baud . . . . . . . . . . . . . . . . . . 10
Lines per page. . . . . . . . . . . . . . . 10
Abortable . . . . . . . . . . . . . . . . 10
11 MAXBUL For displaying bulletins the old fashioned way. . . . 10
11.1 General bulletins, their location, and their file names . 11
11.2 Using submenus. . . . . . . . . . . . . . . 11
11.3 Adding Quit and Exit to your menus . . . . . . . . 11
11.4 Adding security levels to bulletins and submenus . . . 12
11.5 Running doors with MaxBul . . . . . . . . . . . 12
11.6 Shelling to a door . . . . . . . . . . . . . 12
11.7 Exiting to a door . . . . . . . . . . . . . 13
11.8 Running MaxBul Setup. . . . . . . . . . . . . 13
11.9 Running MaxBul. . . . . . . . . . . . . . . 13
12 MAXLOG For trimming your Max.Log file by # of days. . . . . 14
12.1 MaxLog days defined . . . . . . . . . . . . . 14
12.2 Running MaxLog. . . . . . . . . . . . . . . 14
12.3 Max.Log and the MaxTools.Log file . . . . . . . . 14
13 MAXCAT For creating a FILES.BBS from CATDISK v4.40. . . . . 14
13.1 Running MaxCat. . . . . . . . . . . . . . . 14
13.2 CATDISK v4.40 . . . . . . . . . . . . . . . 15
14 MAXCD For creating an ALLFILES.LST . . . . . . . . . . 15
14.1 MaxCD's built in /t /b filter. . . . . . . . . . 15
14.2 Configurable word wrap and unlimited line length. . . . 15
14.3 MaxCD's custom templates . . . . . . . . . . . 15
14.4 Running MaxCD . . . . . . . . . . . . . . . 15
Sw1 - The exist switch . . . . . . . . . . . . 16
Sw2 - The format switch. . . . . . . . . . . . 16
Security levels . . . . . . . . . . . . . . 16
Locks and keys. . . . . . . . . . . . . . . 16
15 MAXMUV For moving files along with their descriptions. . . . 16
15.1 Running Maxmuv. . . . . . . . . . . . . . . 16
15.2 Additional considerations . . . . . . . . . . . 16
16 MTDOOR For updating a users profile from a door file . . . . 17
16.1 Doors not written for Maximus. . . . . . . . . . 17
16.2 Lotto doors and call back verifiers. . . . . . . . 17
16.3 Running MTDoor setup. . . . . . . . . . . . . 17
16.4 Running MTDoor. . . . . . . . . . . . . . . 18
17 MTEXIST For re-writing FILES.BBS with only files that exist. . 18
17.1 Running MTExist
18 MYMAIL For scanning & retrieving echomail addressed to you . . 19
18.1 Message formats: *.MSG and Squish . . . . . . . . 19
18.2 Setting up MyMail. . . . . . . . . . . . . . 19
18.3 Running MyMail. . . . . . . . . . . . . . . 19
19 MBBS For creating pseudo AREAS.BBS files . . . . . . . . 19
19.1 Running MBBS . . . . . . . . . . . . . . . 19
20 MAXLEV For sending canned mail messages to users . . . . . 20
20.1 MaxLev's On-Line Help system . . . . . . . . . . 20
20.2 MaxLev's 20 second setup . . . . . . . . . . . 20
20.3 Sending mail to new users . . . . . . . . . . . 20
20.4 New users and call back verifier support . . . . . . 21
An Explanation. . . . . . . . . . . . . . . 21
20.5 Sending mail to users whose access has been lowered . . 21
20.6 Sending mail to users whose access has been raised. . . 21
20.7 Message formats: *.MSG and Squish . . . . . . . . 21
20.8 MaxLev's Message template format. . . . . . . . . 22
20.9 Running MaxLev. . . . . . . . . . . . . . . 22
21 MAXRE For exiting with random error levels . . . . . . . 22
21.1 Running MaxRe . . . . . . . . . . . . . . . 22
21.2 Using MaxRe to create a fake node with MaxIPC . . . . 22
22 MaxTools Official MaxTools Distributors and availability. . . 23
Magic File Names . . . . . . . . . . . . . . . . 23
Official MaxTools Distributors . . . . . . . . . . . 23
23 The end of another chapter . . . . . . . . . . . . . 24
Page 1
LEGAL DOCUMENTATION FOR MAXTOOLS
LICENSE AGREEMENT
You may distribute the non registered version of MaxTools
freely as long as everything within the original archive is
included. You may change the archiving method as long as
everything that was in the original archive is included in
the target archive unaltered. You may charge a minimal
distribution fee of no more then $10.00 provided that the
purchaser knows that this does not cover registration.
By using any of the MaxTools, even on a trial basis which
includes curiosity, bonds our agreement that you agree to
all terms of this document.
You agree that the sole owner of all MaxTools utilities and
documentation is the property of Michael Jones. You are
granted a limited license to use MaxTools. You understand
that you may not alter any of the programs documentation or
executables. This includes reverse engineering of any kind.
Your limited license extends only for a period of 1
calendar month. After that you must register and pay a
$20.00 registration fee.
The $20.00 registration fee extends your license for using
MaxTools and grants you permission to download updates via
my BBS only for as long as I provide them. I reserve the
right to revoke anyone's registration at any time without
cause or reason without any further obligation.
Although I strongly encourage registered users to supply me
with their ideas, I am no way obligated to fulfill any
request. All decisions are up to Michael Jones, the author
of MaxTools. As a registered user you agree not to
circulate any of the registered utilities downloaded from
Michael Jones or obtained from any other source. You also
understand that although I provide updates , I am under no
obligation to do so.
MaxTools & updates come with no warrantee expressed or
implied. The only thing that I can promise is that the
utilities worked fine on my machine. I will not be held
liable for any damages, loss of wages, mental anguish or
any other loss caused directly or indirectly by MaxTools
utilities, documentation or anything else thereof. You
agree to pay any and all legal costs for Michael Jones if
you decide to take any legal action against the author for
any reason.
END OF LICENSE AGREEMENT
Page 2
2 Preface
Welcome to MaxTools, A literal toolbox for Maximus
SysOps. MaxTools is probably unlike any other software
package that you have ever seen. Rather then provide
you with a gizmo that slices and dices, I have created a
cluster of small, but powerful command line driven
utilities that can work independently or together to
help you peak out your BBS's performance.
2.1 System requirements
o 8086/88 processor or above
o Monochrome or Color Monitor
o DOS Version 3.3 or above
o Maximus BBS software
2.2 Message area requirements
o MaxLev requires only your private mail area
be *.MSG format.
o MyMail requires all of your message areas be
*.MSG format
o All other utilities do not require any special
message format for your message areas.
3 Installation
Installation of MaxTools is quite simple. I have taken
an approach that will keep your maximus subdirectory from
getting cluttered. All of the executables may be placed in
any location on your hard drive provided they are in your
path.
3.1 Creating the MaxTools Subdirectory
MaxTools keeps all of its data files within its'
own directory structure. You need to first create
a subdirectory off of your Maximus directory called
"MAXTOOLS".
Example: C:\MAX> MD MAXTOOLS
Page 3
3.2 Setting the Maximus environment variable
In order for MaxTools to find your Maximus data
files as well as its own data files, Maxtools needs
for you to create a DOS environment variable called
"MAXIMUS" and have it pointing towards your Maximus
subdirectory.
Example: C:\MAX> SET MAXIMUS=C:\MAX\
It is highly recommended that you insert this
command in your autoexec.bat file and reboot your
computer. None of the MaxTools utilities will run
without it.
4 MaxTools Log File
Most of the MaxTools utilities will append to a file
called "MaxTools.Log" within your MaxTools subdirectory
only if it exists.
4.1 Creating the log file
A quick and simple way of creating the log file
would be using DOS's copy con.
EXAMPLE: C:\MAX> COPY CON C:\MAX\MAXTOOLS\MAXTOOLS.LOG
You will then get a blank line as if your PC was hung.
Type : "START" [ENTER]
Then press : CTRL Z [ENTER]
4.2 Log file usage
MaxTools.Log will keep reports just like Maximus
does in its own log file. Whether it is a progress
report or a file create error, you can generally
find it here if the file is activated.
Page 4
4.3 Log file Format
MaxTools utilities maintain MaxTools.Log in the
same format that Maximus does with a minor
exception. MaxTools uses its own "tokens" for
messages found there.
+ = Start of a program token
: = Usually a message token
# = Usually an action token such as a file read or write
! = Error token with error message on the same line.
5 Error Levels
In many of the more intense utilities, I exit with an
error level depending on the success of the utilities
session.
5.1 Error levels which MaxTools uses
The following is a basic guideline that I follow:
0 = Normal run. No action taken
7 = Normal run. Action taken. Event was successful.
13 = Normal run. Action was needed but an error
happened causing abnormal termination.
6 MA.EXE & FA.EXE
MA & FA display your message and file areas as if you were
logged on to your BBS and chose the [A]rea change command.
The main purpose of MA and FA is to view what your areas
will look like prior to running silt.
6.1 Displaying message areas
Typing MA by itself will display the available message
areas. If you are using a different file name other then
MsgArea.CTL then, you need to specify the file name on
the command line. Example: MA Areas.Ctl
MA will work with a control file that contains both file
and message areas but will only display the message
areas.
Page 5
6.1 Displaying file areas
Typing FA by itself will display the available file
areas. If you are using a different file name other then
FileArea.CTL then, you need to specify the file name on
the command line. Example: FA Areas.Ctl
FA will work with a control file that contains both file
and message areas but will only display the file areas.
7 MAKFM.EXE For CD ROM
MakFM was designed to create an external file area menu.
The output looks just like what you would see on line
except for if an area does not exist, offline is put
where the area number choice would be.
7.1 Rotating out CD's
How many of you juggle many CD's through 1 CD player and
had to rig something up so that users would know which
file areas were on line and which ones were off?
7.2 Displaying offline status
MAKFM was designed to put that nightmare to rest. MakFM
creates an external file area menu that you can add to
Maximus in a flash. And MakFM uses the same color scheme
that Maximus uses!
Example:
1 ... General Downloads
2 ... FidoNet Related Files
3 ... G Rated GIF's
offline ... Graphics Misc
offline ... Shelter Shareware
6 ... Unchecked Uploads
7.3 Editing Max.Ctl
In order to have an external file area menu, you need to
first edit your Max.Ctl file. Pull up Max.Ctl in your
favorite editor and uncomment the following line:
% Uses FileAreas Misc\FileArea
This is the mecca file that you will need to write with
MakFM.
Page 6
7.4 Running MAKFM
The command line syntax for MAKFM is:
MAKFM <switch> <file name>
Switches are:
t = target file will be text format
a = target file will be ansi format
m = target file will be mecca format
Please note that any existing file will be over written.
7.5 File menu output formats
MAKFM will create file menus in either ANSI, MECCA, or
plain text. Note that plain text contains no color.
8 MAKMM.EXE For scanning private mail only
One of the most common requests that I have had was to
figure out a way to have my BBS scan for private mail
only. I had users sit there while Maximus scanned through
the National FOR SALE echo and many other large echos.
There is a way out but you need MakMM to do it.
8.1 Editing Max.CTL
There are 2 entries in the Max.Ctl file that need to be
edited. The first one is "Highest MsgArea".
% Highest MsgArea 1
Make sure that your private mail area is the first one
in MsgArea.Ctl and is called Area 1. Normally this would
be all that you need. When anyone scans for new mail
Maximus will only scan up to Area 1 and stop.
There is only one problem. If a user is on the BBS and
decides to change areas with the [A]rea command, Maximus
will only display up to area 1. He/she will be able to
change areas, but just no see them. Unless you have an
external Msg Area menu created by MakMM.
The second entry that you need to edit is:
% Uses MsgAreas Misc\MsgArea
This is the mecca file that you need to create with MakMM.
Page 7
8.2 Running MAKMM
The command line syntax for MAKMM is:
MAKMM <switch> <file name>
Switches are:
t = target file will be text format
a = target file will be ansi format
m = target file will be mecca format
Please note that any existing file will be over written.
8.3 Message menu output formats
MAKMM will create file menus in either ANSI, MECCA, or
plain text. Note that plain text contains no color.
9 FBSD For adding/deleting file dates & sizes
FBSD does exactly what it says and stands for Files BBS
Size and Date manipulator.
9.1 CD-ROM Support
FBSD was first created for those of you who purchase
CD-ROMS and need a quick way to remove all of the
information that Maximus supplies so that it does not
show up twice while somebody is listing files. Deleting
file dates and sizes can be done with wild cards.
9.2 Formatting an all files list
Although MaxTools comes with it's own all files list
generator FBSD may be used to add dates and file sizes
for other all files list generators. FBSD download
counter aware and formats your files.bbs to a human
readable format.
Page 8
9.3 Running FBSD
The syntax for adding file sizes and dates is:
FBSD a <files.bbs> <Path to files>
The syntax for deleting file sizes and dates is:
FBSD d <files.bbs>
Wildcards are acceptable for delete only.
9.4 Other considerations
FBSD has no way of telling what is after a file name.
FBSD removes the first 2 entries that follow the file
name separated by spaces. It is suggested that you check
your FILES.BBS before using this option. FBSD will not
filter out /t /b switches.
10 MAXMENU.EXE For displaying complex ANSI screens
MaxMenu is provided so that you can easily shove any
file to the com port that you choose, whether it is
ANSI or TEXT MaxMenu will take you where you want to go.
10.1 ANSI Welcome screens
Maximus alone cannot give you a ANSI welcome screen
prior to the login prompt. LOGO.MEC does not permit
color. But using MaxMenu you not only can have that menu
but users will not be able to tell that you are using an
external program to display that menu. MaxMenu is fast!
(For faster execution it is suggested that you execute
MaxMenu in your batch file prior to running Maximus)
10.2 The more?[yn=] prompt
The optional more prompt is displayed if a certain
number of lines per page are specified on the command
line.
10.3 Call back when you are there!
If a user sits at a more prompt more then 3 minutes,
Maxbul will send them the message "Call back when you
are there!" and hang up on the user. Once this happens,
Maxbul will immediately terminate and give control back
to your software. The message and the 3 minute limit are
hardcoded and cannot be changed.
Page 9
10.4 When a user hangs up on MaxMenu
MaxMenu continually monitors the carrier so that if a
user does hang up on MaxMenu, MaxMenu will properly
terminate and give control back to your system.
10.5 Local mode and baud rate simulation
When running MaxMenu locally you need to specify the
port as 0. When ran locally with a certain baud rate
specified on the command line, MaxMenu will attempt to
simulate what that menu might look like at that speed.
Please keep in mind that I did not use any scientific
calculations for this, and the rate is a rough estimate.
10.6 Running MaxMenu Setup
Before you can even use MaxMenu, you need to run the
setup program that is built into MaxMenu.
The syntax for running setup is: MaxMenu setup
Be prepared to answer the questions that setup asks you.
1. Handshaking (None,CTS,XON-XOFF,XON-XOFF CTS)
Usually 3 for highspeeds, 0 for 2400
2. Word length (7, 8)
Usually 8
3. Parity
Usually 0
4. IRQ for your com-port. (0 for normal IRQ)
0 uses the common default IRQ's for com ports 1-4.
I would use 0 unless you really know what you are doing.
Page 10
10.7 Running MaxMenu
MaxMenu is always in what I call simultaneous snoop mode.
This means that whatever the users sees, the SysOp will
see. If a user is at a prompt, the SysOp may hit a key to
continue from his/her end.
Syntax
The syntax for running MaxMenu is as follows:
Syntax: MaxMenu <port> <Baud> <Lines> <Abortable>
Port
If port is 0 (local) MaxMenu will try to emulate
whatever baud rate is specified. I don't claim
accuracy in the speed but it is semi close.
Baud
The only exception here is if you are locking your
port to 38400 then this should always be 38400.
Lines
Lines per page give the user More [y,n,=] at that
length. 0 = none
Abortable
Abortable is whether or not you wish to enable the
user to abort menus with either CTRL-C, CTRL-K, or
space bar. CTRL-C does not work locally. Lines
per page must be specified if this option is to be
enabled.
11 MAXBUL For displaying bulletins the old fashioned way
MaxBul was designed to give Maximus SysOps that old
fashioned bulletin capability. Once Maxbul is set up,
all that you have to do to add a bulletin is create the
bulletin, and edit the menu screen.
Page 11
11.1 General bulletins, their location, and their file names
All of the bulletins must reside in your MaxTools\Maxbul
directory. To create general bulletins, a special file
naming convention is used.
BULLET1.MNU - This is your main menu
BULLET1.001 - This is bulletin 1 off of the main menu
BULLET1.002 - This is bulletin 2 off of the main menu
BULLET1.003 - This is bulletin 3 off of the main menu
Please note that all bulletins are single digit numeric
entries.
11.2 Using submenus
There are many cases where a SysOp may want to have a
special categories for bulletins. In this case MaxBul
will allow you to have submenus.
Let us say in the above example that you wanted option
#2 off of the main menu to take the person to a submenu
that had more choices. Instead of creating BULLET1.002
you would create:
BULLET2.MNU - Choice #2 off of the main menu is a submenu
BULLET2.001 - This is bulletin 1 off of your submenu
BULLET2.002 - This is bulletin 2 off of your submenu
BULLET2.003 - This is bulletin 3 off of your submenu
11.3 Adding Quit and Exit to your menus
You are going to want to add Quit and Exit as options
to your menus.
[Q] Quit - Always exits submenus. At the main menu it
does nothing.
[X] Exit - Always exits MaxBul and returns control to
the BBS. This must be at the main menu so
that callers know how to leave. It is
optional for submenus however.
Page 12
11.4 Adding security levels to your bulletins and submenus
You may decide that some of your bulletins need to
be restricted from other users. MaxBul gives you the
option of restricting singular bulletins off of the main
menu or restricting submenus off of the main menu.
To enforce security all you have to do is create a 1
line text file with the corresponding file name and
add the lowest security level that may access it.
The security levels used are numeric not Disgrace or
Worthy. The level that MaxBul references is that which
is read from DOOR.SYS or DORINFO1.DEF.
Examples security files:
BULLET2.LEV - Security file for choice 2 off of the main
menu
BULLET3.LEV - Security file for choice 3 off of the main
menu
BULLET4.LEV - Security file for choice 4 off of the main
menu
11.5 Running doors with MaxBul
Although MaxBul was not originally designed to be a full
fledged door manager, it does have limited support to do
so. The only draw back is that MaxBul does not keep
track of the users time on-line. MaxBul will however
hang up on a user if they sit at a prompt for more then
3 minutes or detect loss of carrier and exit.
There are 2 ways to run a door from MaxBul. Keep in mind
that the bulletin MUST exist and wherever there is a
bulletin you may attach a door to it. After the
bulletin is read, the door is executed.
11.6 Shelling to a door
Shelling to a door is probably the safest way, but it
will take more memory to do so. To shell to a door you
must create a batch file that MaxBul recognizes. The
following is the formula:
BULLETx.00y - MaxBul would look for BULLETxy.BAT
MaxBul executes the batch files passing the port as
parameter #1 and the baud rate as parameter #2.
Page 13
11.7 Exiting to a door
Exiting to a door may be more preferable to some. The
same formula that applies to shelling applies to the
error level which MaxBul exits with. Keep in mind that
when MaxBul exits, it is completely gone from memory and
you are responsible for executing MaxBul again after the
door ends.
Using the formula above BULLETx.00y, upon exiting,
MaxBul would exit with an error level of xy. A few
examples:
BULLET1.002 - Exits with an error level of 12
BULLET2.003 - Exits with an error level of 23
An additional note is that if you using the exit method,
is that you cannot run MaxBul from a Mecca file
directly. You need to create a batch file that runs
MaxBul. Also Maxbul does use the common error levels
that most MaxTools use when exiting. 13=error 7=success
11.8 Running MaxBul Setup
Running MaxBul setup is identical to running setup for
MaxMenu. Please review MaxMenu setup for setup
instructions.
11.9 Running MaxBul
Running MaxBul identical to running MaxMenu except that
you need to specify a door file. Below is the syntax:
Syntax : MaxBul <Port> <Baud> <Door file> <Lines> <Abort>
Explanations for all of the options excluding "door file"
may be found under MaxMenu. The door file is the full
path and file name of a valid DORINFO1.DEF or DOOR.SYS
file that Maximus creates. Please see your Maximus
documentation on how to create one of these files.
All of the options that are in MaxMenu are contained in
MaxBul including baud rate emulation.
12 MAXLOG For trimming your Max.Log file by # of days
MaxLog is a very simple program that trims down your
Max.Log file by the last number of days of activity that
you specify on the command line.
Page 14
12.1 MaxLog Days Defined
MaxLog counts days by "days of activity" rather
then actual days. MaxLog does this so that SysOps
who do not get callers every day will still be able
to look back on the BBS's activity without having
an empty log file.
Let us suppose that you have 1 caller each month,
for a period of one year. That is 12 days of calls.
If you were to shorten your log file with MaxLog
down to the last 3 days, you would have the last 3
months of calls.
12.2 Running Max.Log
MaxLog syntax is fairly straight forward:
MaxLog <# of days> < Max.Log file >
Note that if you do not specify the log file,
"Max.Log" is assumed and is looked for where your
MAXIMUS environment variable is pointed.
12.3 MaxLog and the MaxTools.Log file
MaxLog may be ran on the MaxTools.Log file with no
special precautions needed. In fact, MaxLog is
designed to append it's progress to MaxTools.Log
while the file is being shortened.
13 MAXCAT for creating a FILES.BBS from CATDISK v4.40
Using MaxCat with Maximus and CATDISK 4.40 all you have
to do is dump your files in a file area and run MaxCat.
MaxCat will instantly create your files.bbs based on
files that exist with descriptions!
13.1 Running MaxCat
When running MaxCat you must be in the directory which
contains the files that MaxCat is creating the files.bbs
file for. MaxCat will append to a files.BBS if it
already exists.
Syntax: MaxCat < Catdisk.Dta > < files.bbs >
Page 15
13.2 CATDISK v4.40
I have looked at many versions of CATDISK which were
older and newer then 4.40. My decision to support v4.40
was based on stability, features, and the number of
menus one had to go through to catalog or view files
that were catalogued. A choice had to be made because it
looked as though the file formats had changed through
out the different versions. I will consider supporting
other versions if their is an expressed desire for it.
14 MAXCD For creating an ALLFILES.LST
MaxCD is not just another ALLFILES.LST generator. MaxCD
includes features that the other ones left behind.
14.1 MaxCd's /t /b filter (Registered version only)
MaxCD has a /t /b filter hardcoded in. You will never
see a /t, /b, /tb, /bt switch in your all files list.
14.2 Configurable Word Wrap and Unlimited line length
Whether your file descriptions are already formatted or
all on one line, MaxCD will word wrap lines of any
length over 80. MaxCD word wraps at column 21 as a
default. To change this value you need to create a
text file in your 'MaxTools\MaxCD' subdirectory called
"WORDWRAP". On the first line enter a number between
5-60 or 0 for turning word wrap off.
14.3 MAXCD's Custom Templates
Currently MaxCD supports 2 types of custom templates
that appear at the top of your ALLFILES.LST
MASTER.TPL - Appears at the top of your ALLFILES.LST
<level>.TPL - Appears 2nd if MASTER.TPL exists.
These templates must reside in your MaxTools\MaxCD
subdirectory. To enable them, all you have to do is
create them.
14.4 Running MaxCD
Running MAXCD is pretty straight forward. The syntax is
as follows:
Syntax : MaxCD <Sw1> <Sw2> <Level> <OutFile Name>
Example: MaxCD 1 0 Disgrace J:\AllFiles.Lst
Page 16
Sw1 - The exist switch
1 = See if each file exists while processing the list.
If the file does exist place a '*' in front of the
file name and a space in front if it does not.
0 = Disable file exist
Sw2 - The format switch
1 = Format the files and their descriptions into even
columns
0 = Do a straight file copy of files.bbs
Security Levels
Any security level that you specify, MaxCD will create
an ALLFILES.LST for files accessible for that level and
under. Also MaxCD will use that level for its' template
selection.
Locks and keys (Registered version only)
You may specify a security level with a forward slash
followed by which ever keys that you want your file list
to be generated on. EXAMPLE: Disgrace/ABC
15 MAXMUV For moving files along with their descriptions
You have all used Hurl. This is a command line version
of Hurl that supports wild cards. You can now move *.GIF
from your uploads area to your GIF area without a second
thought.
15.1 Running MaxMuv
MaxMuv does require that you use full path names
specified on the command line. MaxMuv also requires
that the same paths be specified in your
filearea.Ctl file. This is fool proof protection
for both of us that your correct files.bbs file
gets updated. The syntax for MaxMuv is as follows:
MaxMuv <Source> <Destination>
15.2 Additional considerations
Because MaxMuv calculates your files.bbs by what
you specify, two file areas sharing the same path
will be detected and rejected for your protection.
See MT-NEWS.LZH for information on using 4DOS to tag
files for move.
Page 17
16 MTDOOR For updating a users profile from a door file
MTDoor is a simple utility which will take SysOp
defined information from a DORINFO1.DEF or DOOR.SYS file
and update the callers profile with it.
16.1 Doors not written for Maximus
MTDoor was written for SysOps that wish to use doors
that were not written specifically for Maximus but do
update a door file.
16.2 Lotto doors and call back verifiers
Most of the programs that will require MTDOOR will be
doors such as Lotto Doors or Call back verifiers which
write the updated information to the door file.
16.3 Running MTDoor Setup
To run MTDoor setup the syntax is: MTDoor Setup
You will be brought to a screen that has security levels
and toggle options.
MTDoor setup allows you to toggle which items in your
callers profile that you want to be updated from the
door file. All 4 items may be enabled or disabled. Those
4 items are:
o Users Name
o Users City
o Users time left on line
o Users security level
Users name toggle
The users name should NEVER be toggled to on unless
you really are sure of what you are doing.
Users City
This option may be needed if for some reason the door
would update the users city. This can usually be left
off.
Page 18
Users Time left on-line
Users time may be enabled if you are using a type of
time bank or lotto door not specifically written for
Maximus.
Security Level
This option is good when using a callback verifiers.
Unlike the other options this one needs a little
thinking through. Doors that do not support Maximus
will not recognize levels such as WORTHY or DISGRACE.
The setup program will allow you to key in what your
numeric equivalents are for your door files. These may
be found in your DORINFO1.MEC or your DOORSYS.MEC.
16.4 Running MTDoor
MTDoor must be ran from a mecca file with the following
syntax: [xtern_run]@MTDoor.exe <switch> <Door file>
This syntax will force maximus to re-read in the new
data that MTDoor updated into the users profile. Please
refer to the Maximus documentation for further
information.
17 MTEXIST.EXE For re-writing FILES.BBS with only files that exist
MTExist does exactly what it says. It reads in your
FILES.BBS, filters out files which no longer exist, and
writes a new one with only the files that are there.
17.1 Running MTExist
The syntax for MTExist is as follows:
Syntax: MTexist <switch> <File Path> <Files.BBS>
Valid flags are:
Raw Rewrites stripping all info from files.BBS
This is faster the Lite and good for one line
descriptions and no headers.
Lite MTExist takes caution examining what needs to
be removed. It is suggested that you use the
Lite switch if you are not sure.
"File Path" is the path to where your files are located
and "Files.BBS" is the files.bbs which you wish to
update.
Page 19
18 MYMAIL.EXE For scanning & retrieving echomail addressed to you
MyMail will scan all of the echo areas for mail which
is addressed to you. If any is found, MyMail will then
write a copy of the message in the directory which you
specify on the command line. The echo area is inserted
before the subject so that you know the origin.
18.1 Message formats *.MSG and Squish
Currently there is only support for *.MSG. Squish may
be added in a future release.
18.2 Setting up MyMail
MyMail requires an Areas.BBS file. If you do not use
an Areas.BBS file or know what one is, you need to run
MBBS.EXE, another MaxTools utility which will create a
PSEUDO Areas.BBS that MyMail will read.
18.3 Running MyMail
The syntax for running MyMail is as follows:
Syntax: MyMail <Areas.bbs> <Mailbox dir> <Your Name>
MyMail scans all areas that are not "pass through"
If Squish messages are encountered they are ignored.
MyMail will never overwrite old messages in the
target directory specified.
19 MBBS.EXE For creating Pseudo Areas.BBS files
MBBS creates a pseudo areas.bbs file for MaxTools users
who do not use one but wish to run MyMail.
19.1 Running MBBS
Running MBBS is pretty simple. The syntax is as
follows:
Syntax: MBBS <Areas.BBS file>
Any existing areas.bbs file will be over written.
Page 20
20 MAXLEV.EXE For sending canned mail messages to users
MaxLev has got to be the most popular of all of the
MaxTools combined. MaxLev will send canned messages to
users based on the users status and security level.
Don't let MaxLev fool you. It is powerful and yet very
easy to use.
20.1 The MaxLev On-Line Help System
MaxLev is one of the few utilities that has
its' own On-Line help system. If you plan on using
this utility I STRONGLY recommend that you take a
tour of it. Help will start you from an introduction
and ease you through the simple steps that are needed
to set up and run MaxLev.
Also included in On-Line help is built reference
charts that display files that MaxLev looks for as
well as the variables that MaxLev supports.
20.2 MaxLev's 20 second setup
MaxLev may be setup and ran within 20 seconds on an
AT compatible machine!
The syntax for MaxLev setup is: MaxLev write ALL
This will create the necessary directory structure
as well as sample generic canned messages that will
be sent to users. All of the variables supported are
used in the sample message templates to give you an
idea on how to use them.
20.3 Sending mail to new users
When MaxLev detects a new user, MaxLev will look
for a file in its' home directory called
NEWUSER.TXT. This is a simple text message which
follows the format discussed later in this chapter.
As always MaxLev uses what exists and assumes that
you do not wish to use it if it does not. New user
messages may be disabled simply by deleting the
file.
Page 21
20.4 New users and callback verifier support
MaxLev fully supports call back verifiers. All new
users are sent NEWUSER.TXT. If you wish to send a
user a second message "you have been upgraded via"
the door, you need to create another text message.
The format is as follows: <level upgraded to>.NEW
EXAMPLE: WORTHY.NEW
An Explanation
MaxLev keeps a second copy of the user file for
comparing who is new and who is not, as well as
what their security access has changed to. Because
a call back verifier updates a user on-line, there
is no way to detect that he/she has been upgraded.
But if all of your new users are DISGRACE and you
upgrade a user with your door to WORTHY, then a
WORTHY.NEW would only be sent to users who passed
the door. They would also get sent NEWUSER.TXT
which is for all access levels.
20.5 Sending mail to users whose access has been lowered
MaxLev will send messages to users whose access
has been lowered to a particular access level. The
file naming is as follows. < Level >.DWN
20.6 Sending mail to users whose access has been raised
MaxLev will send messages to users whose access
has been raised to a particular access level. The
file naming is as follows. < Level >.UP
20.7 Message formats: *.MSG and Squish
MaxLev requires that your private mail area is
*.MSG format. MaxLev does not care what format your
other message areas are. I am considering adding
Squish support in one of the next releases.
Page 22
20.8 MaxLev's Message template format
To create your own messages, all that you need is
your favorite DOS text editor. The message format
is as follows:
Your Name
Subject
Start of message
.
.
End of message
For a complete listing of all of the possible file
names and their extensions, please consult the
20.9 Running MaxLev
There are 2 command line switches for running MaxLev
Go - Normal memory conserving for large user files
and SysOps with low memory overhead
fast - Uses more memory and loads users names into an
array for fast sorting and comparing.
21 MAXRE For exiting with random error levels
MaxRE is actually and older MaxTool that did not make
the boat in v1.02. One of things that make life exciting
is change. People get tired of the same ole BBS as well.
With MaxRe you can bring your BBS back to life with
random events, menus, or even a realistic fake 2nd node
which really doesn't exist!
21.1 Running MaxRe
The syntax for running MaxRe is as follows:
MaxRe <start> <stop>
If you were to specify 2 and 4 MaxRe would generate
a random error level between 2 and 4.
21.2 Using MaxRE to create a fake node with MAXIPC
A user has contributed a unique way of simulating
a second node with MAXIPC and MaxRe. Please see
MaxReIPC.DOC included in MT-NEWS.LZH.
Page 23
22 MaxTools Official Distributors and availability
MaxTools is internationally distributed via MXBBSNET
and SDSMAX. In order to keep phone costs down for all
parties involved this usually happens on the average of
once per month.
I have been known to work around the clock having my cup
of coffee at the keyboard along with dinner. Because of
this it is very possible that I may have a new revision
a week to 2 weeks after a major release.
To keep the latest and greatest release available to you
I have reliable high speed distribution points which get
the latest version netmailed to them upon completion.
MAGIC FILE NAMES
The following is the Magic File names as well as the
official distribution points:
MAXTOOLS - The latest release MaxTools for MS-DOS
MTUPDATE - The latest <changes only> to the current
DOS version
OFFICIAL MAXTOOLS DISTRIBUTORS
* Michael Jones (Author)
2400-14400 V32, V42
FidoNet 1:133/115
MXBBSNET 256:256/1408
* Thomas Stubbs (South Eastern U.S. Distributor)
2400-14400 V32, V42
FidoNet 1:133/125
End Of Eternity BBS -- Atlanta, GA
(404)892-0282
* Tom Lane (South Central U.S. Distributor)
US Robotics HST/Dual Standard 16.8 bps
No Freq's 0300-0500 Central Time.
Non-Nodelisted Systems Welcome.
FidoNet: 382/91
Flotom Enterprises -- Austin, Tax_Us
(512)282-3941
* Graham Tippett (Canadian Distributor)
2400-14400 V32, V42
"MaxTools" user is set up for updates.
FidoNet: 351/1116
The Uptown BBS -- Black Creek, BC
(604)337-2163
Page 24
23 The end of another chapter
I would like to take the time to thank everyone for
their continued support. I would also like to thank all
of the new users that have stuffed my netmail box with
the kind words and thoughtful suggestions. Clearly it
was you who helped me make MaxTools what it is and I do
appreciate it! Keep those cards and letters coming and
I will keep tapping at my keyboard!
Michael Jones
P.O. Box 769192
Roswell, Georgia 30076
FidoNet: 1:133/115
MXBBSNET: 256:256/1480
MXBBSNET: 256:256/525
ChateauNet: 100:4000/401
BBS: 404-518-1356
