home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
DOOR
/
CLASAD20.ZIP
/
CLASSAD.DOC
< prev
next >
Wrap
Text File
|
1994-11-02
|
9KB
|
226 lines
CLASSAD v2.0
(C)1994 Heavenware Software
WARRANTY:
---------
CLASSAD is distributed without warranty. In no event will Heavenware
Software be liable to you for damages, including any loss of profits,
lost savings, or other incidental or consequential damages arising out
of your use of or inability to use this program, even if Heavenware
Software, or an authorized representative have been advised of the
possibility of such damages. Heavenware Software will not be liable
for any such claim by any other party. Every possible means has been
used to ensure the integrity of this program.
SHAREWARE CONCEPT:
------------------
CLASSAD is distributed as shareware, and may be used up to 30 days
as a trial period, after which, you must either register this program
by sending $10.00 U.S. dollars to:
Heavenware Software
P.O. Box 9824
Dyess AFB, Tx # 79607-9824
or stop using it.
REG BENEFITS:
------------
With the key in place, your users will have access to all the categories
you have defined in the CAT.CTL file.
The 5 sec delay at the end of the program will be bypassed.
The maintenance utility will be operational.
And you'll have the pleasure of knowing that you have helped support one
of the upcoming leaders in the shareware programming world.
REMEMBER, once registered, always registered, but to obtain any new
releases or updates you must call one of our boards.
Seventh Heaven @ 1-915-698-9514 / Fido 1:392/20
Rapid Output @ 1-915-695-6488 / Fido 1:392/27
We have always tried to support our products as much as is humanly
possible, and will continue to do so, so please... if you need help,
contact us, even if you are not registered!
COPYRIGHTS:
-----------
CLASSAD is (c)1994 Heavenware Software and was written in Turbo Pascal
7.0, Copyright (c)1992 Borland International, using RMdoor (c)1991-1994
By Mark Goodwin and Randy Hunt.
INSTALLATION:
-------------
1. Unzip the archive into any dir.
2. Then edit CLASSAD.cfg file to suit your board.
Line 1: Door data file type
Line 2: Path to the door data file(s)
Line 3: BBS Name
Line 4: Sysop's Name
Line 5: Locked Baud Rate
As illustrated above, the door's data file type is specified in line 1
and can be PCB for PCBoard, GAP for GAP (DOOR.SYS), SF for Spitfire,
RBBS for RBBS, WC for Wildcat!, TRIBBS for TriBBS, or WWIV for WWIV.
NOTE: RoboBOARD Sysops, use GAP.
The Locked baud rate is specified in line 5. If the sysop doesn't
lock his serial port, he must specify 0 for the locked baud rate
NOTE: Although many door formats do pass the locked baud rate in the
door data files, some older formats such as RBBS do not. For
conformity, CLASSAD requires that you specify the locked baud rate
in line 5 and ignores any value passed in the door data files.
The following is a sample door configuration file:
GAP
C:\ROBOFX\TEMP_#
Seventh Heaven
Heavenware Software
57600
CLASSAD can be run locally without a door data file by specifying
/L after the configuration file parameter in the DOS command line.
Example:
Clasad20 Classad.cfg /l
Non standard IRQs can be used with CLASSAD by specifying the IRQ number
after the "config" parameter in the command line used to run the door.
Example:
CLASSAD CLASSAD.CFG IRQ
SPECIAL KEYS:
-------------
While the door is running, the sysop can press certain special keys to
perform a variety of functions. The following is a list of the
functions that these keys perform:
Key(s) Function
HOME Toggles between the user status window and a help
display that lists the special keys.
F6 Takes 5 minutes away from the caller.
NOTE: This will NOT be returned to BBS.
F7 Gives 5 minutes to the caller.
NOTE: This will NOT be returned to the BBS.
F9 Quit the door and return the caller to the BBS.
F10 Enter chat mode. Pressing the ESC key exits the
chat mode.
Alt+D Drop to DOS.
3. Edit or create the CAT.CTL file. This file must exist for CLASSAD to
run properly. You may change it in anyway you wish with the following
exceptions.
a.) The unregistered version will only use the first category listed,
so you may not want to waste your time creating more than one until
you register.
b.) The MAXIMUM number of categories is 20. If you have more they just
won't be read into CLASSAD.
c.) Each description may not be longer than 20 characters long.
The .CTL file is a straight ASCII text file, so you may edit it with
almost any text editor. Just make sure you do a CR after each item is
entered.
4. Create the appropiate batch files that will run CLASSAD.
5. Edit your BBS structure to put CLASSAD on the menu(s).
MULTI-NODE SETUP:
-----------------
Although CLASSAD was not specifically written as a multi-node door, it
can be run on a multi-node BBS. The basics of "HOW TO" are this:
a.) You'll need to create separate batch files for each node.
and within each batch file have it look for a empty file that will
be created when a user enters the door.
If the file exists then redirect the user to a utility door that
will inform them that the door they wanted to enter was being used
by another node. One such utility exists. We wrote one a while back,
and it is available for download or FREQ. Filename: TRISCR.ZIP.
TRISCR is just another door but all it does is looks for a screen
that you have specified and displays it. TRISCR supports RIP, ANSI,
& ASCII style screens. And the best part is it's FREE.
Here's a sample of one of my batch files for Node 1:
@echo off
d:
CD\ROBOFX\DOORS\DOORX
if exist busy2.flg goto inuse <-- Checks for any other .flg
echo > busy1.flg <-- Creates the flag for node 1
CLASAD20 CLASSAD1.CFG <-- Runs door using node 1 .cfg
del busy1.flg <-- Deletes the flag after use
goto done <-- redirects batch file
:inuse <-- If door is already being used
cd\robofx
busy1 <-- Batch file that runs TRISCR.
:done
cls
b.) You will also need to create seperate .cfg files unless all the paths
and locked baud rates are the same for all nodes.
This may all sound difficult, but it really isn't that hard.
Depending on your setup and the BBS software you are running, all
of this may or may not be necessary.
If you are asking why we didn't write all this into the program, I
have the answer. Because if the user drops carrier while inside the
door, and the door was supposed to delete the busy.flg, the .flg
file will not get deleted and the next user who calls and tries to
enter the door will not be able to. So although it is a little harder
this way, you win in the end.
If there are any other questions concearning Multi-Node setup,
don't hesitate to ask. We may not beable to help, but we'll sure try.
UPGRADE INFO:
-------------
If you are upgrading from v1.2, you will need to do a complete fresh
install with the exception of the classad.cfg file.
IMPORTANT NOTES:
----------------
Upon a caller placing an Ad, CLASSAD will create the appropiate .dat
file for that category,
Do NOT attempt to edit these yourself through a text editor. You could
corrupt the file making them completely useless to CLASSAD.
Instead use the CAMAINT.EXE utility that came with this archive.
If after installing CLASSAD, you wish to edit the CAT.CTL file, you will
need to delete ALL of the .dat files that exist in that directory.
If you do not, possible .dat file corruption could result. So the best
thing to do is to make sure you have all the categories you want listed
in the CAT.CTL before allowing user access to CLASSAD.
- END OF FILE -