MODKIT, version 4.0
A Procomm+ script can be built by combining standard modules, each of
which accomplishes a pre-determined task.
This modular approach permits the writing of complex scripts with
MODKIT is designed to automate operations on your favourite BBS.
Version 4 supports PCBoard and WildCat. Support for other BBS software
can be added by any user familiar with the ASPECT language.
A timer, included with MODKIT, will let you initiate communications
sessions automatically, at a chosen time, during the night for example.
It is possible to contact various BBS'es successively, without operator
intervention, and to execute in each case a series of tasks, for example
The following instructions assume that you are familiar with Procomm+,
and also with PCBoard and/or WildCat in manual mode. A general
knowledge of Procomm's ASPECT language will facilitate understanding.
CONTENTS OF MODKIT.ARC
Here is a list of the files contained in MODKIT.ARC:
uload.mod ³ The sandardized communications modules
dload.mod ³ (described in next section).
lis.bat ³ Batch files to facilitate use of modules.
change.com ³ Public domain utilities,
waituntl.com ³ used by the batch files.
procomm.set ³ Example of a Procomm+ setup
modkit.doc ³ This file
The modules are designed for PCBoard version 14.1, and WildCat version
(NOTE: All module names end with the .MOD extension. This extension is
omitted in the following, to simplify text)
EASY ³These are header modules, each corresponding to a
ALLEY ³particular BBS, and containing information specific to that
RELAIS ³BBS and to yourself.
LOGON ³This module establishes contact with the BBS, using the info
³contained in the header module.
GETMAIL ³This procedure will get new mail, and also the list of new
DLOAD ³Downloads a file.
ULOAD ³Uploads a file.
ANSWER ³Answer a message.
ENTER ³Enter a new message (not an answer).
BUL ³Get a bulletin.
JOIN35 ³Join conference 35. This module can be modified easily to
³join other conferences.
ABAN ³Abandon a conference, that is, return to Main Board.
BYE ³End communications session. Reset everything to normal
³and hang up.
All modules contained in the archive must be copied to the same
directory that contains Procomm+ (except MODKIT.DOC and PROCOMM.SET,
which can be placed elsewhere).
The file DSZ.COM (not included here) must also be present in the
Procomm+ directory for the DLOAD and ULOAD modules to work. DSZ.COM is
an external protocol supporting XMODEM, YMODEM and ZMODEM. ULOAD and
DLOAD use the XMODEM implementation. The modules call this program
directly, without your intervention, as long as it is present in the
Procomm+ directory. The use of DSZ is made necessary by a bug in
Procomm+'s ASPECT interpreter. Following a file transfer, the WAITFOR
instruction misbehaves. This problem exists for all protocols except
KERMIT and ASCII. Datastorm Technologies does not have a patch for
this bug at this time.
Provided with the kit are the header modules for ALLEYCAT, EASY
ACCESS, and LE RELAIS. Each header module is specific to a BBS and
must contain the corresponding number(s) of your Procomm+ dialing
directory. Each header must also contain you first and last names,
your password, and the name for the LOG file assigned to that BBS.
With a text editor or word processor, you must customize each header
module by writing in the necessary information. The modules must then
be saved in pure ASCII, that is, un-formatted.
The other modules do not need to be customized and can be used in their
PCBOARD: If you wish to join conferences other than number 35, you must
create these modules from the JOIN35 module. Copy that file while
renaming it. Then, with your text editor, change the conference number
variable at the beginning of the module. You must also specify if the
conference belongs to "Echo Mail". "Echo Mail" is a network where
messages are repeated to other BBS's across North America. Most
conferences are not "Echo Mail". Ask your SYSOP if he is a member of
Your Procomm+ setup must also be adequate. This concerns particularly
your ASCII TRANSFER OPTIONS and your GENERAL OPTIONS. Included with the
kit is the file PROCOMM.SET, containing my personal setup. The scripts
work fine with it.
There are also requirements concerning your personal setup on PCBoard.
Your default protocol must be XMODEM CRC, otherwise you will have to
modifiy the GETFILE and SENDFILE commands in the ULOAD and DLOAD
modules. Secondly, you must be in EXPERT mode on PCBOARD, otherwise,
some prompts will be different, and you will have to modify the modules.
On WildCat also, your default protocol must be XMODEM CRC.
Finally, you will notice that in the LOGON and BYE modules, the commands
ATM0 and ATM1 are sent to the modem. These commands are valid for a
Hayes or compatible modem. If your modem is different, you may have to
This completes the installation procedure.
TOOLS AND EXAMPLES
At the beginning of each module, there is a section for the
parameters. These parameters are numbers and strings which vary
according to use. For a given user, some parameters are almost fixed,
for example your name, password, phone number, or the default
directories for ULOAD, DLOAD, ENTER and ANSWER. With an ASCII text
editor, you can write in those parameters once and for all, and save
the modified modules permanently. Other parameters will change each
time you use the kit. For example the name of the file to upload or
download, or the name of the file containing the text of a message. In
the latter case, the parameters are not written into the basic
modules, but rather into the script MADE.ASP, which is generated as
Batch files are supplied to combine the modules.
The first batch is MAKE.BAT, which "glues" together up to nine basic
modules to generate the script MADE.ASP. This script will be executed