home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload
/
ShartewareOverload.cdr
/
comm
/
bbsx2.zip
/
BBSX.DOC
next >
Wrap
Text File
|
1989-01-10
|
147KB
|
4,819 lines
Rich Levin's BBSXpress (tm)
Installation and Configuration Guide
─══════════════════════════════════─
Copyright (c) 1988 Richard B. Levin
All Rights Reserved
Revised January 10, 1989
╒════════════════════════════════════╕
│ ██████████████████████████████████ │
│ ██ ███ ███ ██ ██ ██ │
│ ██ █ ███ █ ███ ██████ ██ │
┤ ██ ██ ██ ████ ████ ├
│ ██ █ ██ █ ██████ ██ ██ │
│ ██ ██ ██ ██ ██ ██ │
│ ██████████████████████████████████ │
╘════════════════════════════════════╛
The Personal BBS (tm)
═════════════════
Table of Contents
═════════════════
DEDICATION.................................................1
ACKNOWLEDGEMENTS...........................................1
PROGRAM INFO...............................................1
MINIMUM HARDWARE AND SOFTWARE REQUIREMENTS.................2
BBSX'S ARCHIVE CONTENTS....................................2
Source code (ASCII)....................................2
Batch files (ASCII)....................................2
Sample bulletins (ASCII)...............................2
Utilities (Binary).....................................3
Documents (ASCII)......................................3
Executable files (Binary)..............................3
Initialization files (ASCII)...........................3
Sample file descriptions (ASCII).......................3
Sample polls (ASCII)...................................3
COPYRIGHT NOTICE...........................................3
OWNER REGISTRATION.........................................4
CORPORATE AND GOVERNMENT USERS.........................4
PRIVATE USERS..........................................4
DISTRIBUTION POLICY....................................4
UPGRADE POLICY.........................................5
REGISTRATION FORM..........................................6
REGISTRATION FEE AND PLEDGE FOR NON-PRIVATE USERS......9
WAIVER OF REGISTRATION FEE ... FOR PRIVATE USERS......10
BBSX - THE PERSONAL BBS (tm)..............................11
INSTALLING BBSX...........................................11
CONFIGURING BBSX..........................................11
STEP 1 - Editing the BBSX.INI file....................12
BAUD_RATE=........................................13
CARRIER_DETECT_TIMER=.............................13
COM_PORT=.........................................14
DOWNLOAD_UPLOAD_RATIO=............................14
MESSAGE_LINES=....................................14
MESSAGE_SCROLL_RATE=..............................14
MODEM_INI=........................................14
MODEM_TIMER=......................................14
NEW_USER_SECURITY=................................14
NEW_USER_TIME=....................................15
SECURITY_TO_DOWNLOAD=.............................15
SECURITY_TO_READ=.................................15
SECURITY_TO_UPLOAD=...............................15
SECURITY_TO_WRITE=................................15
SYSOP=............................................15
SYSOP_DOS_PASSWORD=...............................15
UPLOAD_PATH=......................................16
General information about BBSX.INI................16
STEP 2 - Editing the GROUP.INI file...................16
GROUP_SECURITY=...................................17
GROUP_PASSWORD=...................................18
GROUP_NAME=.......................................18
GROUP_FILENAME=...................................18
END_OF_GROUPS=Y...................................19
General information about GROUP.INI...............19
Examples of GROUP.INI files.......................19
STEP 3 - Editing the FILES.INI file...................24
FILES_SECURITY=...................................25
FILES_PASSWORD=...................................26
FILES_AREA=.......................................26
FILES_PATH=.......................................26
END_OF_FILES=Y....................................26
General information about FILES.INI...............27
Examples of FILES.INI files.......................27
STEP 4 - Storing the PROTOCOL.INI file................32
General information about PROTOCOL.INI............33
STEP 5 - Editing the BBS.BAT file.....................33
BBSX's optional start-up switches.................34
General information about BBS.BAT.................36
STEP 6 - Editing the DAILY.BAT file...................36
General information about DAILY.BAT...............37
STEP 7 - Editing the DOS.BAT file.....................38
General information about DOS.BAT.................39
STEP 8 - Storing the FTX.BAT file.....................40
General information about FTX.BAT.................41
STEP 9 - Editing the MENU.BLT file....................41
Controlling .BLT file output......................42
~FORCEREAD or ~F - the "Force-Read" command.......43
~NONSTOP or ~N - the "Non-stop" command...........43
General information about MENU.BLT................44
STEP 10 - Editing the System .BLT files...............44
General information about system .BLT files.......45
STEP 11 - Editing the MENU.POL file...................46
Controlling .POL file output......................47
~FORCEREAD or ~F - the "Force-Read" command.......47
~NONSTOP or ~N - the "Non-stop" command...........48
General information about MENU.POL................48
STEP 12 - Installing yourself as a SysOp..............49
STEP 13 - Going on-line...............................50
LEARNING TO USE BBSX......................................51
REQUIRED MODEM DIP-SWITCH SETTINGS........................51
HOW TO....................................................52
USE ANOTHER DISK OR SUBDIRECTORY NAME.................52
CREATE OR CONVERT FILE DESCRIPTION FILES..............52
BBSX'S F KEY ASSIGNMENTS..................................53
TROUBLESHOOTING...........................................54
MODEM HANGS UP ON CALLERS.............................54
MODEM WON'T HANG UP...................................54
SYSTEM HANGS DURING DROPS TO DOS......................54
FILE TRANSFERS BOMB...................................55
ERROR CODES AND EXPLANATIONS..............................55
FATAL ERRORS..........................................59
APPENDIX A - FILE TRANSFER TECHNICAL REFERENCE............59
Editing the FTX.BAT file..............................59
Editing the PROTOCOL.INI file.........................63
PROTOCOL_NAME=....................................63
PROTOCOL_CODE=....................................64
END_OF_PROTOCOLS=Y................................64
APPENDIX B - TCD.COM COMMAND REFERENCE....................64
COMMAND LINE ARGUMENT SYNTAX..........................65
EXAMPLES OF COMMAND LINE ARGUMENTS....................65
1
══════════
DEDICATION
══════════
BBSX is dedicated to my wife, Carol; to the Mother Board BBS'
regular callers (you know who you are) and to BBSX SysOps
everywhere.
════════════════
ACKNOWLEDGEMENTS
════════════════
Special thanks to Scott Russell for coding TCD.COM (The
Carrier Detective) and programming guidance; to Keith Russell,
for many on-line ßeta test sessions and crazy ideas; and to John
Ellard, for giving me the kick-start on Word.
════════════
PROGRAM INFO
════════════
Program: Rich Levin's BBSXpress (tm)
Function: Multi-SIG/LIB e-mail and file transfer system
Class: PC/MS DOS-compatible bulletin board system
Price: $50.00 per node/per computer
Editor: Norton Editor v.1.3C
Trace: AddLine v.1.5
Compiler: Microsoft BASIC v.6.0
Math LIB: BC6 Alternate (/FPA)
Linker: Microsoft Segmented-Executable Linker v.5.01.20
Author: Richard B. Levin
Address: P.O. Box 14546, Phila., PA 19115
Telephone: (215) 333-8274
BBS: The Mother Board @ (215) 333-8275 (300/1200/2400)
Documentation - Author: Richard B. Levin
Proof reader: Carol Levin
Principal distribution points: The Mother Board BBS
CompuServe IBMNET
GEnie IBM and BBS RTs
BBSX is published by Richard B. Levin
9405 Bustleton Ave.
P.O. Box 14546
Phila., PA 19115
Lab: (215) 333-8274
BBS: (215) 333-8275
2
The latest version of BBSX is available for downloading on
the Mother Board BBS. Support is also available through Rich
Levin's lab. Please leave a message on our answering machine if
we are unable to answer your call personally. We return long
distance calls collect.
══════════════════════════════════════════
MINIMUM HARDWARE AND SOFTWARE REQUIREMENTS
══════════════════════════════════════════
IBM PC, XT, AT, PS/2 or true compatible
384k RAM
Monochrome display adaptor
Monochrome monitor
Hard disk drive
RS232C serial port configured as COM1 or COM2
Hayes 300, 1200, 2400 or 9600 baud modem or true compatible
PC/MS DOS v.3.0 or higher
═══════════════════════
BBSX'S ARCHIVE CONTENTS
═══════════════════════
The BBSX archive contains the following files:
Source code (ASCII)
───────────────────
BBSXSRC BAS BASIC source to BBSX file formats
Batch files (ASCII)
───────────────────
BBS BAT Loads and recycles BBSX
DAILY BAT Performs routine tasks once daily
DOS BAT Provides link between BBSX and DOS
FTX BAT Manages file transfers (down/uploads)
INSTALL BAT Installs BBSX on a hard disk
Sample bulletins (ASCII)
────────────────────────
1 BLT Bulletin # 1
2 BLT Bulletin # 2
3 BLT Bulletin # 3
DOWNLOAD BLT Displayed before downloads
GOODBYE BLT Displayed after log off
HELLO BLT Displayed after log on
MAIN BLT Displayed after entering MAIN group
MENU BLT Bulletin menu
NEWS BLT Displayed after HELLO.BLT
NEWUSER BLT Displayed to new users after NEWS.BLT
UPLOAD BLT Displayed before uploads
3
Utilities (Binary)
──────────────────
TCD COM Monitors carrier during drop-to-DOS
Documents (ASCII)
─────────────────
BBSX DOC This file
CHANGES DOC List of major system changes
README DOC May or may not be present
REGISTER DOC Owner registration form
Executable files (Binary)
─────────────────────────
BBSX EXE BBSX program
BRUN60AR EXE BBSX run-time module
Initialization files (ASCII)
────────────────────────────
BBSX INI General initialization file
FILES INI File areas initialization file
GROUP INI Message groups initialization file
PROTOCOL INI Transfer protocols initialization file
Sample file descriptions (ASCII)
────────────────────────────────
FILES LST Example of file description file format
Sample polls (ASCII)
────────────────────
1 POL Questionnaire # 1
2 POL Questionnaire # 2
3 POL Questionnaire # 3
4 POL Questionnaire # 4
5 POL Questionnaire # 5
MENU POL Questionnaire menu
════════════════
COPYRIGHT NOTICE
════════════════
The names "BBSXpress," "BBSX" and the BBSX program,
documentation, BBSX-created input and output files, visual
displays, interface, look and feel (hereinafter referred to as
"the BBSX system") are copyright (c) and trademark (tm) 1988
Richard B. Levin (hereinafter referred to as "the author"), all
rights reserved.
4
The author reserves the right to make changes to the BBSX
system at any time without prior notice. The BBSX system is
provided to the user "as is" without warranty of any kind, either
express or implied. No part of the BBSX system may be reproduced
without the written permission of the author.
The BBSX system is protected by United States Copyright Law
(Title 17 United States Code). Unauthorized modification,
reproduction, duplication, transfer or sales may result in
imprisonment of up to one year and fines of up to $10,000.00 (17
USC 506). Copyright infringers may also be subject to civil
liability. The Federal Bureau of Investigation investigates
allegations of criminal copyright infringement.
══════════════════
OWNER REGISTRATION
══════════════════
──────────────────────────────
CORPORATE AND GOVERNMENT USERS
──────────────────────────────
For-profit, non-profit and not-for-profit corporations,
governmental offices and agencies and private individuals using
BBSX within these classifications are required to register their
ownership of the BBSX system with the author. Every registration
must be accompanied by a registration fee of $50.00 for each
computer running the BBSX system.
Registered owners must submit an additional registration form
and fee whenever the BBSX system is installed on an unregistered
computer.
Site licenses and disk copies are available on request.
─────────────
PRIVATE USERS
─────────────
Private users of BBSX are required to register their
ownership of the BBSX system with the author but are not required
to remit the $50.00 registration fee. Donations are accepted.
───────────────────
DISTRIBUTION POLICY
───────────────────
Users are permitted to distribute the BBSX system free of
charge to other users when the following conditions are met:
* The BBSX system must be distributed in its entirety
as originally produced by the author.
5
* No part of the BBSX system may be altered, added to,
removed, re-archived or modified in any way
whatsoever.
FAILURE TO COMPLY WITH THE ABOVE TERMS AND CONDITIONS IS A
VIOLATION OF UNITED STATES COPYRIGHT LAW.
──────────────
UPGRADE POLICY
──────────────
The latest edition of BBSX is stored on the Mother Board BBS
(listed above) in the "Software by Rich Levin" area and can be
downloaded at any time.
Upgrades are regularly posted to the IBMNET Forum on the
CompuServe Information Service (GO IBMNET) and the IBM and BBS
RoundTables (RTs) on the General Electric Network for Information
Exchange (GEnie).
6
- - - - - - - - - - - - Tear Here - - - - - - - - - - - - -
═════════════════
REGISTRATION FORM
═════════════════
ALL USERS ARE REQUIRED BY LAW TO COMPLETE AND RETURN THIS FORM
WITH PAYMENT WITHIN TEN DAYS OF ACQUIRING THE BBSX SYSTEM
Print, complete and mail to Richard B. Levin
BBSX Registration
P.O. Box 14546
Phila., PA 19115
Please make checks payable to "Richard B. Levin."
Important: Please hand print your responses to the
registration questionnaire; do not type or
computer-print them. If necessary, use
additional sheets of paper to complete this
form.
Date of registration:
____________________________________________________________
Registered owner's name:
____________________________________________________________
____________________________________________________________
Title:
____________________________________________________________
____________________________________________________________
Department:
____________________________________________________________
____________________________________________________________
7
Company:
____________________________________________________________
____________________________________________________________
Street address:
____________________________________________________________
____________________________________________________________
P.O. Box:
____________________________________________________________
____________________________________________________________
Mail stop:
____________________________________________________________
____________________________________________________________
City:
____________________________________________________________
___________________________________________________________
State:
____________________________________________________________
____________________________________________________________
Zip:
____________________________________________________________
____________________________________________________________
Telephone: ( ) -
8
What feature(s) do you like most about BBSX?
____________________________________________________________
____________________________________________________________
What feature(s) do you like least about BBSX?
____________________________________________________________
____________________________________________________________
What feature(s) would you most like to see in BBSX that are not
there now?
____________________________________________________________
____________________________________________________________
Have you operated a BBS before?
[ ] Yes [ ] No
Please list the name(s) of the BBSes you have operated if you
answered YES to the previous question:
____________________________________________________________
____________________________________________________________
How did you hear about BBSX?
____________________________________________________________
____________________________________________________________
How did you acquire your copy(s) of BBSX?
____________________________________________________________
____________________________________________________________
Do you own or use any other software by Rich Levin?
[ ] Yes [ ] No
9
Please list the name(s) of the program(s) you own or use if you
answered YES to the previous question:
____________________________________________________________
____________________________________________________________
─────────────────────────────────────────────────
REGISTRATION FEE AND PLEDGE FOR NON-PRIVATE USERS
─────────────────────────────────────────────────
Please enclose check or money order (made payable to "Richard
B. Levin") in the amount of $50.00 for each copy of BBSX
installed on an unregistered computer.
Total number of
unregistered computers
running BBSX............[# ]
X $50.00 each =
────────────────
Amount enclosed.........[$ ]
════════════════
I agree to use BBSX in accordance with the terms and
conditions specified in this document. I pledge to do my best to
insure that registration forms (and fees, if applicable) are
submitted to the author whenever the BBSX system is installed on
unregistered computers.
Date: _____________________________________________________
Signature: ________________________________________________
Attest: ___________________________________________________
Thank you for registering!
10
───────────────────────────────────────────────────────
WAIVER OF REGISTRATION FEE AND PLEDGE FOR PRIVATE USERS
───────────────────────────────────────────────────────
I certify that I am a private user using BBSX in my home on
my personal computer(s) and that said computer(s) are not used on
behalf of any for-profit, non-profit and not-for-profit
corporations or governmental offices or agencies.
I agree to use BBSX in accordance with the terms and
conditions specified in this document. I pledge to do my best to
insure that registration forms (and fees, if applicable) are
submitted to the author whenever the BBSX system is installed on
unregistered computers.
Date: _____________________________________________________
Signature: ________________________________________________
Attest: ___________________________________________________
Site licenses and disk copies available on request.
Prices subject to change without notice. Please allow
4 to 6 weeks for registrations to be processed.
- - - - - - - - - - - - Tear Here - - - - - - - - - - - - -
11
════════════════════════════
BBSX - THE PERSONAL BBS (tm)
════════════════════════════
BBSX is a bulletin board system that remains true to the
spirit of personal computing. BBSX provides users with an
inexpensive, full-featured, user-supported alternative to
commercial BBSes. It's easy to buy, install, use and maintain,
plus 24 hour technical support is free for the asking.
In this first build, BBSX provides most, if not all, of the
popular features users demand. In addition, BBSX users are not
subject to configuration limitations, nor are they burdened with
BBS maintenance. On the contrary, BBSX imposes no limit to the
number of conferences, file areas, protocols, bulletins,
questionnaires or message sizes, and system maintenance is fully
automated.
═══════════════
INSTALLING BBSX
═══════════════
Before BBSX can be run, it must be installed and configured.
To install BBSX, do the following:
1. Copy the BBSX files to the root directory of the
hard disk (usually C:\).
2. Run the INSTALL.BAT file by entering the following
command:
INSTALL
════════════════
CONFIGURING BBSX
════════════════
BBSX can be tailored to suit your specific needs; thousands
of configurations are possible. After initial installation,
however, BBSX is pre-configured to provide the following:
* Monochrome (black and white) screen colors.
* Support for 2400 baud operation on COM1.
* Sample DOWNLOAD, HELLO, GOODBYE, NEWS, NEWUSER and
UPLOAD bulletins.
* A sample bulletin menu and three sample bulletins.
* A sample "polls" menu and six sample polls.
12
* Five public message groups: MAIN, Computer
Hardware, Computer Software, Programmer's Corner and
Word Processing.
* One sample message group bulletin for the MAIN
section.
* Messages limited to 100 lines.
* Automatic "scrolling" of message group data bases
every 300 messages (per group).
* Four public files areas: New uploads, Disk
Utilities, Printer Utilities and Telecommunication
Programs.
* Five file transfer protocols: Xmodem 128, Xmodem
1k, Ymodem 128, Ymodem 1k and Zmodem.
* Uploads immediately posted for public consumption.
* New users granted an access level of 60, providing
one hour of daily access on their first call.
* New users granted a security level of 2, allowing
reading and writing of messages in all message
groups.
* Enforced download/upload ratio of 5 to 1 (where 1
upload is required after every 5 downloads).
* Drop-to-DOS support for SysOp-level users.
You can operate BBSX as is or you can reconfigure the
installation to suit your needs.
──────────────────────────────────
STEP 1 - Editing the BBSX.INI file
──────────────────────────────────
BBSX.INI is the general initialization file. It must be
edited using an ASCII editor operating in non-document mode.
13
Load BBSX.INI into any ASCII editor. The following text will
be displayed:
~ Rich Levin's BBSXpress (tm)
~ BBSX.INI
~ Copyright (c) 1988 Richard B. Levin
~ All Rights Reserved
~
~ Revised January 10, 1989
~
~ Precede comments with a tilde.
~ Delete comments to optimize this file.
~
BAUD_RATE=2400
CARRIER_DETECT_TIMER=30
COM_PORT=1
DOWNLOAD_UPLOAD_RATIO=5
MESSAGE_LINES=100
MESSAGE_SCROLL_RATE=300
MODEM_INI=ATE0F1M0Q0V1X1S0=1
MODEM_TIMER=2
NEW_USER_SECURITY=2
NEW_USER_TIME=60
SECURITY_TO_DOWNLOAD=2
SECURITY_TO_READ=2
SECURITY_TO_UPLOAD=2
SECURITY_TO_WRITE=2
SYSOP=your name goes here
SYSOP_DOS_PASSWORD=put a unique password here
UPLOAD_PATH=\BBSX\FILES
Edit each field to reflect your configuration requirements:
1. ~ Rich Levin's BBSXpress (tm)
A comment. Text preceded by a tilde character is
ignored by BBSX.
2. BAUD_RATE=
The maximum baud rate supported by the modem. Four
characters maximum. Use 300, 1200, 2400 or 9600 to
signify 300, 1200, 2400 and 9600 bauds,
respectively.
3. CARRIER_DETECT_TIMER=
The maximum amount of time to wait for DCD (Data
Carrier Detect) on incoming calls before hanging up.
Two characters maximum. Use a whole number from 10
to 60 seconds.
This timer should match the modem's S7 register
setting.
14
4. COM_PORT=
The port number of the RS232C communications channel
to use. One character maximum. Use 1 for COM1, 2
for COM2.
5. DOWNLOAD_UPLOAD_RATIO=
The maximum number of downloads allowed before BBSX
requests one upload. Three characters maximum. Use
a whole number from 0 to 999.
6. MESSAGE_LINES=
The maximum number of lines allowed per message.
Three characters maximum. Use a whole number from
25 to 999 lines.
7. MESSAGE_SCROLL_RATE=
The maximum number of messages, per message group,
stored on disk before the oldest 25% are
automatically deleted. Four characters maximum.
Use a whole number from 25 to 9999 messages.
8. MODEM_INI=
A string of Hayes-standard AT-commands used for
modem initialization. 40 characters maximum. The
first two characters must be "AT." Do not use ATZ,
ATH or escape codes.
The MODEM_INI string featured is designed for use
with Hayes-compatible modems.
9. MODEM_TIMER=
The amount of time the modem needs to process
AT-commands. One character maximum. Use a whole
number from 1 to 9 seconds.
Some modems take longer than others to digest
AT-commands. Increase this setting if the system
behaves abnormally.
10. NEW_USER_SECURITY=
The security level granted to new users on their
first call. Three characters maximum. Use a whole
number from 0 to 994.
15
11. NEW_USER_TIME=
The amount of daily on-line time granted to new
users on their first call. Four characters maximum.
Use a whole number from 0 and 1440 minutes.
Setting this field to 0 locks out new users.
12. SECURITY_TO_DOWNLOAD=
The security level required to DOWNLOAD files.
Three characters maximum. Use a whole number from 0
to 999.
13. SECURITY_TO_READ=
The security level required to READ messages in any
group. Three characters maximum. Use a whole
number from 0 to 999.
14. SECURITY_TO_UPLOAD=
The security level required to UPLOAD files. Three
characters maximum. Use a whole number from 0 to
999.
15. SECURITY_TO_WRITE=
The security level required to WRITE messages in any
group. Three characters maximum. Use a whole
number from 0 to 999.
16. SYSOP=
The name of the board's SysOp. 50 characters
maximum. Control and high-bit ASCII characters are
accepted.
This entry must match the SysOp's USER.LOG record
exactly; it is used by BBSX to find the SysOp's
record when messages are posted "To: SysOp."
17. SYSOP_DOS_PASSWORD=
The password required to grant SysOp-level users
remote access to DOS. 25 characters maximum.
Control and high-bit ASCII characters are accepted.
This password should not be the same as the SysOp's
log-in password; it should be known only to those
persons who are granted a security level of 999 and
are allowed total access to the hard disk.
16
18. UPLOAD_PATH=
The path where uploaded files are stored. Use any
legal DOS directory pathname. 53 characters
maximum.
If a "\" character is not the last character of the
UPLOAD_PATH, BBSX will insert it. Drive letters are
optional.
If you want users to be able to download from the
new uploads directory, you must set a FILES_PATH
(see Step 3, item 4, in the "Editing the FILES.INI
file" section, below) equal to the UPLOAD_PATH.
If the UPLOAD_PATH field is BLANK, BBSX will store
uploads in the last FILES_PATH selected by the user.
General information about BBSX.INI
──────────────────────────────────
The following rules apply to BBSX.INI:
1. BBSX.INI must be stored in the BBSX
subdirectory.
2. If BBSX.INI cannot be found in the BBSX
subdirectory, BBSX will initialize using
hard-coded defaults. If these defaults are not
correct for your installation, BBSX will fail to
operate properly.
3. The data fields can appear in any order. They
have been sorted alphabetically for esthetic
purposes.
───────────────────────────────────
STEP 2 - Editing the GROUP.INI file
───────────────────────────────────
GROUP.INI is the message group configuration file. This file
is optional, used only by systems supporting a variety of message
groups.
BBSX always features one message group called "MAIN." The
MAIN group is hard-coded into the program. All other groups are
listed in GROUP.INI.
If you plan to support only the MAIN message group or if you
are in a hurry to get BBSX up and running, remove the GROUP.INI
file from the BBSX subdirectory and jump directly to
configuration Step 3, "Editing the FILES.INI file," below.
17
GROUP.INI must be edited using an ASCII editor operating in
non-document mode.
Load GROUP.INI into any ASCII editor. The following text
will be displayed:
~ Rich Levin's BBSXpress (tm)
~ GROUP.INI
~ Copyright (c) 1988 Richard B. Levin
~ All Rights Reserved
~
~ Revised January 10, 1989
~
~ Precede comments with a tilde.
~ Delete comments to optimize this file.
~
GROUP_SECURITY=2
GROUP_PASSWORD=
~
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
Edit each field to reflect your configuration requirements:
1. ~ Rich Levin's BBSXpress (tm)
A comment. Text preceded by a tilde character is
ignored by BBSX.
2. GROUP_SECURITY=
The security level required to read or write
messages in the groups defined below it. Three
characters maximum. Use a whole number from 0 to
999.
GROUP_SECURITY settings must appear before all other
fields.
Multiple GROUP_SECURITY settings can be used. Each
new setting affects the groups defined below it.
18
If multiple settings are used, a default setting
must be the first field in GROUP.INI. This prevents
the last setting encountered from looping back to
the top.
If a GROUP_SECURITY setting does not appear, the
NEW_USER_SECURITY (see Step 1, item 10, in the
"Editing the BBSX.INI file" section, above) will be
used in its place.
3. GROUP_PASSWORD=
The password required to read or write messages in
the groups defined below it. 25 characters maximum.
Control and high-bit ASCII characters are accepted.
GROUP_PASSWORDs must appear after a GROUP_SECURITY
setting.
Multiple GROUP_PASSWORDs can be used. Each new
password affects the groups defined below it.
Use a blank password to unprotect groups. Each new
blank password unprotects the groups defined below
it.
If multiple passwords are used, a default (or a
blank) password be the second field in GROUP.INI.
This prevents the last password encountered from
looping back to the top.
If a GROUP_PASSWORD does not appear, all groups will
be unprotected by passwords.
4. GROUP_NAME=
The name of a message group. 50 characters maximum.
Control, ANSI and high-bit ASCII characters are
accepted.
Every GROUP_NAME must be followed by a
GROUP_FILENAME.
5. GROUP_FILENAME=
The disk filename of a message group. 8 characters
maximum. All legal DOS filenames are accepted.
Every GROUP_FILENAME must be preceded by a
GROUP_NAME.
19
6. END_OF_GROUPS=Y
An end-of-data (EOD) flag. Must be the last entry
in GROUP.INI. BBSX stops searching for GROUP.INI
fields when this entry is encountered.
This EOD flag allows users to optionally merge
GROUP.INI into BBSX.INI, providing a central
initialization file. If GROUP.INI fields are merged
into BBSX.INI, the GROUP.INI file is not used;
however, BBSX performs better when GROUP.INI and
BBSX.INI are not merged.
General information about GROUP.INI
───────────────────────────────────
The following rules apply to GROUP.INI:
1. GROUP.INI must be stored in the BBSX
subdirectory.
2. BBSX always features one message group called
"MAIN." The MAIN group is hard-coded into the
program. All other groups are listed in
GROUP.INI.
3. If GROUP.INI fields cannot be found in the BBSX
subdirectory, BBSX will support only the MAIN
group.
4. There is no limit to the number of message
groups, group security levels and group
passwords that BBSX can support.
5. SysOps and Co-SysOps are not queried for a
password when entering protected groups.
Examples of GROUP.INI files
───────────────────────────
The following examples demonstrate how the GROUP.INI fields
provide SysOps with the flexibility to create a variety of
message groups:
20
1. This example allows users between security
levels 2 and 999 access to the Computer Hardware
and Software Forums and the Programmer's Corner.
Security levels 500 through 999 can access the
Word Processing Conference. Levels below 2 have
access to the MAIN group* only. No passwords
are used.
GROUP_SECURITY=2
GROUP_PASSWORD=
~
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_SECURITY=500
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
2. This example allows users between security
levels 2 and 999 access to the Computer Hardware
and Software Forums. Security levels 500
through 999 can access the Programmer's Corner
and Word Processing Conference. Levels below 2
have access to the MAIN group* only. No
passwords are used.
GROUP_SECURITY=2
GROUP_PASSWORD=
~
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_SECURITY=500
~
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
21
3. This example allows users between security
levels 2 through 999 access to the Computer
Hardware Forum; levels 3 through 999 have access
to the Computer Software Forum; levels 4 through
999 can access the Programmer's Corner; levels 5
through 999 may enter the Word Processing
Conference. Levels below 2 have access to the
MAIN group* only. No passwords are used.
GROUP_SECURITY=2
GROUP_PASSWORD=
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_SECURITY=3
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_SECURITY=4
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_SECURITY=5
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
4. This example allows users between security
levels 2 through 999 access to the Computer
Hardware and Software Forums and the
Programmer's Corner without requiring a
password. Access to the Word Processing
Conference is limited to users who know the
password "orbit.shelf." Levels below 2 have
access to the MAIN group* only.
GROUP_SECURITY=2
GROUP_PASSWORD=
~
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_PASSWORD=orbit.shelf
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
22
5. This example allows users between security
levels 2 and 999 access to the Computer Hardware
and Software Forums. Access to the Programmer's
Corner and the Word Processing Conference is
limited to users who know the password
"edit!compile!crash." Levels below 2 have
access to the MAIN group* only.
GROUP_SECURITY=2
GROUP_PASSWORD=
~
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_PASSWORD=edit!compile!crash
~
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
6. This example allows users between security
levels 2 and 999 access to all groups, provided
they know the passwords. Levels below 2 have
access to the MAIN group* only.
GROUP_SECURITY=2
~
GROUP_PASSWORD=mips 'n chips
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_PASSWORD=folder@rules
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_PASSWORD=diner#wheel
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_PASSWORD=road$mirror
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
23
7. This example allows users between security
levels 2 and 999 access to the Computer Hardware
and Software Forums, provided they know the
passwords; levels 500 through 999 have password
protected access to the Programmer's Corner and
Word Processing Conference. Levels below 2 have
access to the MAIN group* only.
GROUP_SECURITY=2
~
GROUP_PASSWORD=tinkerbell%squander
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_PASSWORD=verb^coil
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_SECURITY=500
~
GROUP_PASSWORD=holes&bottle
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_PASSWORD=esc*fp*down4
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
24
8. This example allows users between security
levels 2 through 999 access to the Computer
Hardware Forum; levels 3 through 999 have access
the Computer Software Forum; levels 4 through
999 can access the Programmer's Corner; levels 5
through 999 may enter the Word Processing
Conference. All groups are individually
password protected. Levels below 2 have access
to the MAIN group* only.
GROUP_SECURITY=2
GROUP_PASSWORD=bagle(shade
GROUP_NAME=Computer Hardware Forum
GROUP_FILENAME=HARDWARE
~
GROUP_SECURITY=3
GROUP_PASSWORD=virus)checkup
GROUP_NAME=Computer Software Forum
GROUP_FILENAME=SOFTWARE
~
GROUP_SECURITY=4
GROUP_PASSWORD=seat_display
GROUP_NAME=Programmer's Corner
GROUP_FILENAME=PROGRAM
~
GROUP_SECURITY=5
GROUP_PASSWORD=pulley-south
GROUP_NAME=Word Processing Conference
GROUP_FILENAME=WORDPRO
~
END_OF_GROUPS=Y
These examples demonstrate how GROUP_SECURITY and
GROUP_PASSWORD fields can be mixed and matched to create an
infinite variety of configurations.
*Note: Users will be unable to read or write messages in any
group, including MAIN, if their security level is less
than the SECURITY_TO_READ or SECURITY_TO_WRITE. (See
Step 1, items 13 and 15, in the "Editing the BBSX.INI
file" section, above.)
───────────────────────────────────
STEP 3 - Editing the FILES.INI file
───────────────────────────────────
FILES.INI is the file areas configuration file. This file is
optional, used only by systems supporting a variety of file
areas.
If you do not plan to support any file areas or if you are in
a hurry to get BBSX up and running, remove the FILES.INI file
from the BBSX subdirectory and jump directly to configuration
Step 4, "Storing the PROTOCOL.INI file," below.
25
FILES.INI must be edited using an ASCII editor operating in
non-document mode.
Load FILES.INI into any ASCII editor. The following text
will be displayed:
~ Rich Levin's BBSXpress (tm)
~ FILES.INI
~ Copyright (c) 1988 Richard B. Levin
~ All Rights Reserved
~
~ Revised January 10, 1989
~
~ Precede comments with a tilde.
~ Delete comments to optimize this file.
~
FILES_SECURITY=2
FILES_PASSWORD=
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
END_OF_FILES=Y
Edit each field to reflect your configuration requirements:
1. ~ Rich Levin's BBSXpress (tm)
A comment. Text preceded by a tilde character is
ignored by BBSX.
2. FILES_SECURITY=
The security level required to download or upload
files in the areas defined below it. Three
characters maximum. Use a whole number from 0 to
999.
FILES_SECURITY settings must appear before all other
fields.
Multiple FILES_SECURITY settings can be used. Each
new setting affects the file areas defined below it.
If multiple settings are used, a default setting
must be the first field in FILES.INI. This prevents
the last setting encountered from looping back to
the top.
26
If a FILES_SECURITY setting does not appear, the
NEW_USER_SECURITY (see Step 1, item 10, in the
"Editing the BBSX.INI file" section, above) will be
used in its place.
3. FILES_PASSWORD=
The password required to download or upload files in
the areas defined below it. 25 characters maximum.
Control and high-bit ASCII characters are accepted.
FILES_PASSWORDs must appear after a FILES_SECURITY
setting.
Multiple FILES_PASSWORDs can be used. Each new
password affects the areas defined below it.
Use a blank password to unprotect areas. Each new
blank password unprotects the areas defined below
it.
If multiple passwords are used, a default (or a
blank) password must be the second field in
FILES.INI. This prevents the last password
encountered from looping back to the top.
If a FILES_PASSWORD does not appear, all areas will
be unprotected by passwords.
4. FILES_AREA=
The name of a files area. 50 characters maximum.
Control, ANSI and high-bit ASCII characters are
accepted.
Every FILES_AREA must be followed by a FILES_PATH.
5. FILES_PATH=
The disk pathname to a files area. 8 characters
maximum. All legal DOS pathnames are accepted.
Every FILES_PATH must be preceded by a FILES_AREA.
6. END_OF_FILES=Y
An end-of-data (EOD) flag. Must be the last entry
in FILES.INI. BBSX stops searching for FILES.INI
fields when this entry is encountered.
27
This EOD flag also allows users to optionally merge
FILES.INI into BBSX.INI, providing a central
initialization file. If FILES.INI fields are merged
into BBSX.INI, the FILES.INI file is not used;
however, BBSX performs better when FILES.INI and
BBSX.INI are not merged.
General information about FILES.INI
───────────────────────────────────
The following rules apply to FILES.INI:
1. FILES.INI must be stored in the BBSX
subdirectory.
2. If FILES.INI fields cannot be found in the BBSX
subdirectory, BBSX will display the message "No
AREAS available" when requested to list them.
3. There is no limit to the number of file areas,
file security levels and file area passwords
that BBSX can support.
4. SysOps and Co-SysOps are not queried for a
password when entering protected areas.
Examples of FILES.INI files
───────────────────────────
The following examples demonstrate how the FILES.INI fields
provide SysOps with the flexibility to create a variety of file
areas:
28
1. This example allows users between security
levels 2 and 999 access to the New Uploads, Disk
Utilities and Printer Utilities areas. Security
levels 500 through 999 can access the
Telecommunication Programs area. Levels below 2
cannot access any file areas.* No passwords are
used.
FILES_SECURITY=2
FILES_PASSWORD=
~
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
~
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
~
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
~
FILES_SECURITY=500
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
~
END_OF_FILES=Y
2. This example allows users between security
levels 2 and 999 access to the New Uploads and
Disk Utilities areas. Security levels 500
through 999 can access the Printer Utilities and
Telecommunication Programs areas. Levels below
2 cannot access any file areas.* No passwords
are used.
FILES_SECURITY=2
FILES_PASSWORD=
~
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
~
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
~
FILES_SECURITY=500
~
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
~
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
~
END_OF_FILES=Y
29
3. This example allows users between security
levels 2 through 999 access to New Uploads;
levels 3 through 999 have access to Disk
Utilities; levels 4 through 999 can access
Printer Utilities; levels 5 through 999 may
enter Telecommunication Programs. Levels below
2 cannot access any file areas.* No passwords
are used.
FILES_SECURITY=2
FILES_PASSWORD=
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
~
FILES_SECURITY=3
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
~
FILES_SECURITY=4
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
~
FILES_SECURITY=5
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
~
END_OF_FILES=Y
4. This example allows users between security
levels 2 through 999 access to the New Uploads,
Disk Utilities and Printer Utilities areas
without requiring a password. Access to the
Telecommunication Programs area is limited to
users who know the password "company.refract."
Levels below 2 cannot access any file areas.*
FILES_SECURITY=2
FILES_PASSWORD=
~
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
~
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
~
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
~
FILES_PASSWORD=company.refract
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
~
END_OF_FILES=Y
30
5. This example allows users between security
levels 2 and 999 access to the New Uploads and
Disk Utilities areas. Access to the Printer
Utilities and Telecommunication Programs areas
is limited to users who know the password
"gwackle!doo." Levels below 2 cannot access any
file areas.*
FILES_SECURITY=2
FILES_PASSWORD=
~
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
~
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
~
FILES_PASSWORD=gwackle!doo
~
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
~
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
~
END_OF_FILES=Y
6. This example allows users between security
levels 2 and 999 access to all groups, provided
they know the passwords. Levels below 2 cannot
access any file areas.*
FILES_SECURITY=2
~
FILES_PASSWORD=face@wood
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
~
FILES_PASSWORD=manual#luggage
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
~
FILES_PASSWORD=spin$piece
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
~
FILES_PASSWORD=staple%post
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
~
END_OF_FILES=Y
31
7. This example allows users between security
levels 2 and 999 access to the New Uploads and
Disk Utilities areas, provided they know the
passwords; levels 500 through 999 have password
protected access to the Printer Utilities and
Telecommunication Programs areas. Levels below
2 cannot access any file areas.*
FILES_SECURITY=2
~
FILES_PASSWORD=plastic^threat
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
~
FILES_PASSWORD=os&who
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
~
FILES_SECURITY=500
~
FILES_PASSWORD=power*tree
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
~
FILES_PASSWORD=indicate(dust
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
~
END_OF_FILES=Y
32
8. This example allows users between security
levels 2 through 999 access to New Uploads;
levels 3 through 999 have access Disk Utilities;
levels 4 through 999 can access Printer
Utilities; levels 5 through 999 may enter
Telecommunication Programs. All areas are
individually password protected. Levels below 2
cannot access any file areas.*
FILES_SECURITY=2
FILES_PASSWORD=box)card
FILES_AREA=New Uploads
FILES_PATH=\BBSX\FILES
~
FILES_SECURITY=3
FILES_PASSWORD=vent_ruler
FILES_AREA=Disk Utilities
FILES_PATH=\BBSX\FILES\DISK
~
FILES_SECURITY=4
FILES_PASSWORD=bulb-date
FILES_AREA=Printer Utilities
FILES_PATH=\BBSX\FILES\PRINTER
~
FILES_SECURITY=5
FILES_PASSWORD=can+tube
FILES_AREA=Telecommunication Programs
FILES_PATH=\BBSX\FILES\TELECOM
~
END_OF_FILES=Y
These examples demonstrate how FILES_SECURITY and
FILES_PASSWORD fields can be mixed and matched to create an
infinite variety of configurations.
*Note: Users will be unable to download or upload if their
security level is less than the SECURITY_TO_DOWNLOAD or
SECURITY_TO_UPLOAD. (See Step 1, items 12 and 14, in the
"Editing the BBSX.INI file" section, above.)
──────────────────────────────────────
STEP 4 - Storing the PROTOCOL.INI file
──────────────────────────────────────
PROTOCOL.INI is a control file used by BBSX to manage file
transfer protocol selection. This file is optional, used only by
systems supporting a variety of file transfer protocols.
If you are not supporting file areas, remove the PROTOCOL.INI
file from the BBSX subdirectory and jump directly to
configuration Step 5, "Editing the BBS.BAT file," below.
33
PROTOCOL.INI should not be edited by anyone other than
experienced programmers. (A programmer's technical reference
guide to PROTOCOL.INI appears in appendix A.)
PROTOCOL.INI IS PRE-CONFIGURED FOR USE WITH "DSZ," AN
EXTERNAL FILE TRANSFER PROTOCOL DRIVER PRODUCED BY OMEN
TECHNOLOGY, INC. AND RECOMMENDED FOR USE WITH BBSX. DSZ is
available for downloading on the Mother Board BBS (215-333-8275),
Omen Technology's TeleGodzilla BBS (503-621-3746) and many public
BBSes.
General information about PROTOCOL.INI
──────────────────────────────────────
The following rules apply to PROTOCOL.INI:
1. PROTOCOL.INI must be stored in the BBSX
subdirectory.
2. If PROTOCOL.INI fields cannot be found on disk,
BBSX will display the message "No PROTOCOLS
available" when requested to list them.
3. To insure its correct operation, do not edit
PROTOCOL.INI.
─────────────────────────────────
STEP 5 - Editing the BBS.BAT file
─────────────────────────────────
BBS.BAT is a batch file used to load and recycle the BBSX
program. BBS.BAT must be edited using an ASCII editor operating
in non-document mode.
Load BBS.BAT into any ASCII editor. The following text will
be displayed:
echo off
break on
goto top
Rich Levin's BBSXpress (tm)
BBS.BAT
Copyright (c) 1988 Richard B. Levin
All Rights Reserved
Revised January 10, 1989
:top
echo Loading BBSX
c:
cd \bbsx
bbsx
goto top
34
Edit BBS.BAT to reflect your configuration requirements:
1. Change the reference to drive "c:" to the letter of
the disk drive being used.
2. Change the reference to "\bbsx" to the name of the
subdirectory being used.
BBSX's optional start-up switches
─────────────────────────────────
The following start-up switches can be added, in any order,
to BBS.BAT after the "bbsx" command:
1. /BLOCK or /BL
Causes BBSX to use a full-cell cursor on the local
screen instead of the default underline-style
cursor.
2. /CANADA or /CA
Runs BBSX in Canadian mode.
3. /COLOR or /CO
Runs BBSX in color mode.
4. /DASH or /DA
Causes BBSX to use a dash-style cursor on the local
screen instead of the default underline-style
cursor.
5. /DEBUG or /DE
Runs BBSX in DEBUG mode. DEBUG mode peppers the
NODE.LOG with information that helps track
configuration bugs. DEBUG mode decreases system
performance.
6. /DLALL or /DL
Allows users to download FILES.LST. Normally, only
SysOp and Co-SysOp level users can download
FILES.LST, because FILES.LST may contain private
information.
7. /E71 or /E7
Runs BBSX using communication parameters of E71
instead of the default N81.
35
8. /FLASH or /FL
Causes BBSX to use a continuously blinking cursor on
the local screen instead of the default
soft-blinking cursor.
9. /HALF or /HA
Causes BBSX to use a half-cell cursor on the local
screen instead of the default underline-style
cursor.
10. /IGNOREDCD or /IG
Causes BBSX to ignore the state of carrier detect.
Use when running BBSX with a null modem that does
not provide a carrier.
11. /NOLOG or /NO
Suppresses output to the NODE.LOG. Increases system
performance but eliminates activity records.
12. /NULLMODEM or /NU
Runs BBSX only at the baud rate specified in
BBSX.INI and skips modem initialization and
AT-command interaction.
13. /PRINTER or /PR
Redirects NODE.LOG output to the printer.
14. /RATIOFREE or /RA
Ignores DL/UL ratios, allowing users to continue
downloading after their DL/UL ratio goes out of
balance.
15. /SKIPATZ or /SK
Skips resetting the modem with an ATZ.
16. /SOLID or /SO
Causes BBSX to use a solid, non-blinking cursor on
the local screen instead of the default
soft-blinking cursor.
17. /THIN or /TH
Causes BBSX to use a thin, single scan line cursor
on the local screen instead of the default
underline-style cursor.
36
General information about BBS.BAT
─────────────────────────────────
The following rules apply to BBS.BAT:
1. BBS.BAT must be stored in the BBSX subdirectory or
in a subdirectory specified by the DOS PATH
environment variable.
2. If BBS.BAT cannot be found on disk, BBSX will fail
to operate properly.
3. BBSX must be run using the BBS.BAT file. Do not run
BBSX without using BBS.BAT.
4. BBS.BAT is designed to infinitely loop. Do not
alter this procedure.
5. To exit BBS.BAT, wait until the "... Press ^C ..."
prompt echos to the screen; then press ^C or
^ScrollLock. If the batch file does not "break,"
press ^C or ^ScrollLock again. Do not press ^C or
^ScrollLock while BBSX is unloading from memory;
some computers lock-up if a break key is struck
while returning to DOS.
6. Multiple switches can be specified on the command
line. For example, the following command line runs
BBSX in Canadian mode, in color:
BBSX /CANADA /COLOR
7. Start-up switches can be entered as terse,
two-letter arguments. For example, the following
command line also runs BBSX in Canadian mode, in
color:
BBSX /CA /CO
───────────────────────────────────
STEP 6 - Editing the DAILY.BAT file
───────────────────────────────────
DAILY.BAT is a batch file run by BBSX once daily. This file
is optional; it is provided so SysOps can automate maintenance
functions not supported internally by BBSX.
If you are in a hurry to get BBSX up and running, you can
delay editing DAILY.BAT (or remove it from the hard disk
altogether) and jump directly to configuration Step 7, "Editing
the DOS.BAT file," below.
37
DAILY.BAT IS PRE-CONFIGURED FOR USE WITH "ZOO," A FILE
COMPRESSION UTILITY PRODUCED BY RAHUL DHESI AND RECOMMENDED FOR
USE WITH BBSX. ZOO is available for downloading on the Mother
Board BBS (215-333-8275), GEnie's IBM RT and many public BBSes.
DAILY.BAT must be edited using an ASCII editor operating in
non-document mode.
Load DAILY.BAT into any ASCII editor. The following text
(demonstrating how DAILY.BAT can be used to back-up
system-critical files) will be displayed:
echo on
goto top
Rich Levin's BBSXpress (tm)
DAILY.BAT
Copyright (c) 1988 Richard B. Levin
All Rights Reserved
Revised January 10, 1989
:top
c:
cd \bbsx
if not exist bak\bbsx.zoo md bak
zoo a: bbsx \bin\exe\bbsx.exe
zoo a: hdr *.hdr
zoo a: ini *.ini
zoo a: log *.log
zoo a: msg *.msg
zoo a: ptr *.ptr
zoo a: rsp *.rsp
copy *.zoo bak
del *.zoo
Edit DAILY.BAT to reflect your configuration requirements:
1. Change the reference to drive "c:" to the letter of
the disk drive being used.
2. Change the reference to "\bbsx" to the name of the
subdirectory being used.
General information about DAILY.BAT
───────────────────────────────────
The following rules apply to DAILY.BAT:
1. DAILY.BAT must be stored in the BBSX subdirectory or
in a subdirectory specified by the DOS PATH
environment variable.
38
2. If DAILY.BAT cannot be found on disk, BBSX will
display the message "Bad command or file name" after
attempting to launch the child process.
3. DAILY.BAT can be programmed to perform any series of
legal DOS commands. BBSX will execute the commands
once daily.
4. To disable DAILY.BAT, delete it from disk or replace
the commands in the above example with the
following:
rem daily.bat disabled
5. Programmers developing external utilities for BBSX
should incorporate their run-time calls into
DAILY.BAT.
─────────────────────────────────
STEP 7 - Editing the DOS.BAT file
─────────────────────────────────
DOS.BAT is a batch file used to provide SysOps with remote
access to DOS. This file is optional.
If you are in a hurry to get BBSX up and running, you can
delay editing DOS.BAT (or remove it from the hard disk
altogether) and jump directly to configuration Step 8, "Storing
the FTX.BAT file," below.
DOS.BAT must be edited using an ASCII editor operating in
non-document mode.
39
Load DOS.BAT into any ASCII editor. The following text will
be displayed:
echo off
goto top
Rich Levin's BBSXpress (tm)
DOS.BAT
Copyright (c) 1988 Richard B. Levin
All Rights Reserved
Revised January 10, 1989
:top
tcd /com1 /on
ctty com1
echo Wait...
command
echo Wait...
ctty con
tcd /com1 /off
c:
cd \bbsx
Edit DOS.BAT to reflect your configuration requirements:
1. Change the reference to drive "c:" to the letter of
the disk drive being used.
2. Change the reference to "\bbsx" to the name of the
subdirectory being used.
3. Change the reference to "com1" to the port number of
the RS232C communications channel being used.
General information about DOS.BAT
─────────────────────────────────
The following rules apply to DOS.BAT:
1. DOS.BAT must be stored in the BBSX subdirectory or
in a subdirectory specified by the DOS PATH
environment variable.
2. If DOS.BAT cannot be found on disk, BBSX will
display the message "Bad command or file name" after
attempting to launch the child process and will not
provide DOS-level access to remote SysOps.
40
3. The program file TCD.COM (provided with BBSX) must
be stored in the BBSX subdirectory or in a
subdirectory specified by the DOS PATH environment
variable.
TCD.COM is a resident utility that automatically
re-boots a computer when carrier is lost. When a
SysOp working at DOS-level disconnects the telephone
(drops carrier) before returning to BBSX, TCD.COM
re-boots the system to prevent unauthorized callers
from accessing the DOS prompt. If the last command
in AUTOEXEC.BAT is "BBS," BBSX will recycle. (A
technical reference guide to TCD.COM appears in
appendix B.)
4. A copy of COMMAND.COM must be stored in the BBSX
subdirectory or in a subdirectory specified by the
DOS PATH environment variable.
5. To insure correct operation, we recommend the
COMSPEC environment variable be SET in the
AUTOEXEC.BAT file:
SET COMSPEC=[d:][path]COMMAND.COM
See your DOS manual for information on the COMSPEC
environment variable.
6. Some versions of MS DOS feature a buggy CTTY command
that causes system lock-ups during redirected
DOS-level backspacing. Users of true-blue IBM PC
DOS will not encounter this bug.
If you experience difficulty with BBSX's drop-to-DOS
function, visit the Mother Board BBS (215-333-8275)
and download GAPCTY.ARC or GATEWAY.ARC. These files
contain enhancements to the CTTY command that
resolve the MS DOS bugs.
─────────────────────────────────
STEP 8 - Storing the FTX.BAT file
─────────────────────────────────
FTX.BAT is a batch file used by BBSX to control file
downloads and uploads. FTX.BAT is an extension of BBSX's program
code and should not be edited by anyone other than experienced
programmers. (A programmer's technical reference guide to
FTX.BAT appears in appendix A.)
41
FTX.BAT IS PRE-CONFIGURED FOR USE WITH "DSZ," AN EXTERNAL
FILE TRANSFER PROTOCOL DRIVER PRODUCED BY OMEN TECHNOLOGY, INC.
AND RECOMMENDED FOR USE WITH BBSX. DSZ is available for
downloading on the Mother Board BBS (215-333-8275), Omen
Technology's TeleGodzilla BBS (503-621-3746) and many public
BBSes.
General information about FTX.BAT
─────────────────────────────────
The following rules apply to FTX.BAT:
1. FTX.BAT must be stored in the BBSX subdirectory or
in a subdirectory specified by the DOS PATH
environment variable.
2. If FTX.BAT cannot be found on disk, BBSX will
display the message "Bad command or file name" after
attempting to launch the child process and will be
unable to perform file transfers.
3. DSZ.EXE must be stored in the BBSX subdirectory or
in a subdirectory specified by the DOS PATH
environment variable.
4. If DSZ.EXE cannot be found on disk, BBSX will
display the message "Bad command or file name" after
attempting to launch the protocol driver and will be
unable to perform file transfers.
5. To insure its correct operation, do not edit
FTX.BAT.
───────────────────────────────────
STEP 9 - Editing the MENU.BLT file
───────────────────────────────────
MENU.BLT is the main bulletin menu file, displayed to users
when they request the BULLETINS menu. This file is optional; it
is provided so SysOps can offer callers a variety of bulletins.
If you do not plan to provide bulletins or if you are in a
hurry to get BBSX up and running, remove the MENU.BLT file from
the BBSX subdirectory and jump directly to configuration Step 10,
"Editing the system .BLT files," below.
MENU.BLT must be edited using an ASCII editor operating in
non-document mode.
42
Load MENU.BLT into any ASCII editor. The following text will
be displayed:
╒══════════════════════╕
│ -- BULLETINS Menu -- │
╘══════════════════════╛
1 Contact Info ... Software by Rich Levin
2 User Supported Software ... Production Staff
3 How to Get Increased Access
█═══════════════════════════════════════════════════════█
│ DOWNLOAD A download reminder │
│ GOODBYE Log-off screen │
│ HELLO Welcoming screen │
│ MENU This menu again! │
│ NEWS The daily news file │
│ NEWUSER Information for new users │
│ UPLOAD Upload requests │
█═══════════════════════════════════════════════════════█
Edit MENU.BLT to reflect your configuration requirements:
1. MENU.BLT should list available bulletins by name,
number and description.
2. Each bulletin listed must have a corresponding .BLT
file on disk. For example, bulletin #1 must appear
on disk as "1.BLT," bulletin #2 as "2.BLT," bulletin
#3 as "3.BLT," the HELLO bulletin as "HELLO.BLT" and
so on. Names, numbers, legal DOS filename
characters and combinations thereof can be used to
identify .BLT files.
3. Format MENU.BLT and .BLT files using the designs of
your choice. Control, ANSI and high-bit ASCII
characters are accepted.
Controlling .BLT file output
────────────────────────────
There are times when the output of a bulletin must be
controlled. For instance, some SysOps want to prevent new users
from cancelling a display of system rules and regulations; others
want to display ANSI-animated bulletins without pausing after
every full screen.
43
BBSX provides facilities to address these needs. The
following commands, when embedded in .BLT files, control their
output:
1. ~FORCEREAD or ~F - the "Force-Read" command
When the word FORCEREAD or the letter F is
preceded by a tilde (ASCII character 126, "~")
in a .BLT file, requests by the user to abort
the display are ignored.
There must not be any spaces between the tilde
and the force-read command. BBSX will interpret
the command as a comment if a space appears.
For best results, place the force-read command
on the first line of a .BLT file.
The force-read command can be entered in upper
or lower case.
The NEWUSER.BLT file (provided with BBSX)
contains an example of the force-read command.
2. ~NONSTOP or ~N - the "Non-stop" command
When the word NONSTOP or the letter N is
preceded by a tilde (ASCII character 126, "~")
in a .BLT file, the file is displayed to its end
without interruption. Requests by the user to
abort the display are honored unless the
force-read command has also been issued.
There must not be any spaces between the tilde
and the non-stop command. BBSX will interpret
the command as a comment if a space appears.
For best results, place the non-stop command on
the first line of a .BLT file.
The non-stop command can be entered in upper or
lower case.
The 1.BLT file (provided with BBSX) contains an
example of the non-stop command.
44
General information about MENU.BLT
──────────────────────────────────
The following rules apply to MENU.BLT:
1. MENU.BLT must be stored in the BBSX subdirectory.
2. If the MENU.BLT file cannot be found in the BBSX
subdirectory, the message "BULLETINS have not been
posted today" will be displayed when users request
the BULLETINS menu.
3. Users requesting .BLT files that BBSX cannot find in
the BBSX subdirectory will receive the message
"BULLETIN not available."
4. If a .BLT file does not appear in MENU.BLT but does
exist on disk, it can be viewed if the user knows
its name or number.
5. There is no limit to the number of bulletins (.BLT
files) BBSX can support.
───────────────────────────────────────
STEP 10 - Editing the System .BLT files
───────────────────────────────────────
There are seven .BLT files reserved for system use:
DOWNLOAD, GOODBYE, HELLO, MENU, NEWS, NEWUSER and UPLOAD. These
files, displayed automatically at specific session times, are
optional; they are provided so SysOps can customize the look and
feel of the BBS.
If you do not plan to support an exclusive BBS image or if
you are in a hurry to get BBSX up and running, remove the system
.BLT files from the BBSX subdirectory and jump directly to
configuration Step 11, "Editing the MENU.POL file," below.
System .BLT files must be edited using an ASCII editor
operating in non-document mode.
Each system .BLT file functions in a unique manner, described
below. Edit the sample .BLT files (provided with BBSX) using any
ASCII editor before putting your board on-line:
1. DOWNLOAD.BLT
An upload information screen. Displayed to users
once daily, immediately after they enter a request
to download a file.
45
2. GOODBYE.BLT
A closing "goodbye" message. Displayed to users
once daily, immediately after they log off.
3. HELLO.BLT
An opening "welcoming" screen. Displayed to users
once daily, immediately after they log in.
4. MENU.BLT
See Step 10, "Editing the MENU.BLT file," above.
5. NEWS.BLT
An opening "news" screen. Displayed to users once
daily, immediately after the HELLO.BLT file is
displayed.
6. NEWUSER.BLT
An opening "new user information" screen. Displayed
to users on their first call, immediately after the
NEWS.BLT file is displayed.
7. UPLOAD.BLT
An upload information screen. Displayed to users
once daily, immediately after they enter a request
to upload a file.
In addition, message groups can have associated bulletins.
Message group bulletins are presented to users once daily,
immediately after they enter the message group.
To link a bulletin to a message group, give the .BLT file the
same name as the GROUP_FILENAME. (See Step 2, item 5, in the
"Editing the GROUP.INI file" section, above).
For example, to present users with a greeting when they enter
the MAIN group, store a file with the name of "MAIN.BLT" in the
BBSX subdirectory. A sample MAIN.BLT is provided with BBSX.
General information about system .BLT files
───────────────────────────────────────────
The following rules apply to system .BLT files:
1. System .BLT files must be stored in the BBSX
subdirectory.
46
2. The commands for controlling .BLT file output apply
to system .BLT files. (See Step 9, the "Editing the
MENU.BLT file" section, "Controlling .BLT file
output" subsection), above.
───────────────────────────────────
STEP 11 - Editing the MENU.POL file
───────────────────────────────────
MENU.POL is the main questionnaire menu file, displayed to
users when they request the POLLS menu. This file is optional,
used only by systems supporting a variety of questionnaires.
If you do not plan to support questionnaires or if you are in
a hurry to get BBSX up and running, remove the MENU.POL file from
the BBSX subdirectory and jump directly to configuration Step 12,
"Installing yourself as SysOp," below.
MENU.POL must be edited using an ASCII editor operating in
non-document mode.
Load MENU.POL into any ASCII editor. The following text will
be displayed:
╒══════════════════════╕
│ ──── POLLS Menu ──── │
╘══════════════════════╛
1 New User Questionnaire
2 User Hardware Profile
3 User Software Profile
4 Add a BBS to our BBS list
5 BBS Users Survey
COMMENT Post a private comment to the SysOp
Edit MENU.POL to reflect your configuration requirements:
1. MENU.POL should list available polls by name, number
and description.
2. Each poll listed must have a corresponding .POL file
on disk. For example, poll #1 must appear on disk
as "1.POL," poll #2 as "2.POL," poll #3 as "3.POL,"
the COMMENT poll as "COMMENT.POL" and so on. Names,
numbers, legal DOS filename characters and
combinations thereof can be used to identify .POL
files.
3. Format MENU.POL and .POL files using the designs of
your choice. Control, ANSI and high-bit ASCII
characters are accepted.
47
Controlling .POL file output
────────────────────────────
There are times when the output of a poll must be controlled.
For instance, some SysOps want to prevent users from cancelling a
display; others want to display ANSI-animated polls without
pausing after every full screen.
BBSX provides facilities to address these needs. The
following commands, when embedded in .POL files, control their
output:
1. ~? - the "Input" command
When a question mark is preceded by a tilde
(ASCII character 126, "~") in a .POL file, BBSX
prompts the user for input.
The format of the input command is as follows:
~?#
where "#" is a number from 1 to 99, representing
the maximum number of lines to be input. For
example, the following command causes BBSX to
accept nine lines of input:
~?9
User responses are recorded in a corresponding
".RSP" file. .RSP files follow the same naming
conventions as .POL files; that is, a poll named
"1.POL" would have its responses stored in a
file named "1.RSP."
The response date, time and user name are
automatically recorded in .RSP files.
.RSP files can be viewed using any ASCII editor.
2. ~FORCEREAD or ~F - the "Force-Read" command
When the word FORCEREAD or the letter F is
preceded by a tilde (ASCII character 126, "~")
in a .POL file, requests by the user to abort
the display are ignored.
48
There must not be any spaces between the tilde
and the force-read command. BBSX will interpret
the command as a comment if a space appears.
For best results, place the force-read command
on the first line of a .POL file.
The force-read command can be entered in upper
or lower case.
3. ~NONSTOP or ~N - the "Non-stop" command
When the word NONSTOP or the letter N is
preceded by a tilde (ASCII character 126, "~")
in a .POL file, the file is displayed without
interruption. Requests by the user to abort the
display are honored unless the force-read
command has been issued.
There must not be any spaces between the tilde
and the non-stop command. BBSX will interpret
the command as a comment if a space appears.
For best results, place the non-stop command on
the first line of a .POL file.
The non-stop command can be entered in upper or
lower case.
General information about MENU.POL
──────────────────────────────────
The following rules apply to MENU.POL:
1. MENU.POL must be stored in the BBSX subdirectory.
2. If the MENU.POL file cannot be found in the BBSX
subdirectory, the message "POLLS have not been
posted today" will be displayed when users request
the POLLS menu.
3. Users requesting .POL files that BBSX cannot find in
the BBSX subdirectory will receive the message "POLL
not available."
4. If a .POL file does not appear in MENU.POL but does
exist on disk, it can be viewed if the user knows
its name or number.
5. There is no limit to the number of questionnaires
(.POL files) and response files (.RSPs) that BBSX
can support.
49
────────────────────────────────────────
STEP 12 - Installing yourself as a SysOp
────────────────────────────────────────
Every BBS requires a system operator, popularly referred to
as the "SysOp." Guess what? You're it!
BBSX SysOps are granted special privileges, among them the
ability to:
* Have unlimited on-line time
* Access the SYSTEM menu
* Change user access (time) and security levels
* "Lock-out" users
* Delete and undelete users
* View and edit the USER.LOG
* View and delete the NODE.LOG (an activity/audit log)
* Access all message and file areas
* Waive group and files password requirements
* Read "private" mail
* Delete and undelete messages regardless of who
posted
* Access DOS from a remote computer
* Watch users on-line
* Force users in CHAT mode
* Disconnect users
Assuming BBSX has been correctly installed and configured,
the next step is to let it know who's boss.
To install yourself as the SysOp:
1. Confirm that BBSX.EXE and BRUN60AR.EXE are in the
BBSX subdirectory or in a subdirectory specified by
the DOS PATH environment variable.
2. Enter the following commands:
CD \BBSX
BBSX /SYSOP
50
3. BBSX will load, display the message "WARNING: The
/SYSOP start-up switch is ACTIVE" and then prompt:
Local (CR), Quit (ESC)
Press CR or enter the letter "L."
4. BBSX will go off hook and prompt:
First name:
Enter your first name.
5. BBSX will prompt:
Last name:
Enter your last name.
6. BBSX will prompt:
Are you a NEW user (y/N)?
Enter the letter "Y."
7. BBSX will prompt:
Password:
Enter a password that YOU and ONLY YOU will know.
Control and high-bit ASCII characters are accepted.
8. After a moment, BBSX will exit to DOS, having
registered you as the board's SysOp.
Never run BBSX with the /SYSOP switch again.
───────────────────────
STEP 13 - Going on-line
───────────────────────
Assuming BBSX has been correctly installed and configured and
that the SysOp has been installed, the next step is to go
on-line.
Always run BBSX using the BBS.BAT file. To put BBSX on-line:
* If BBS.BAT is stored in the BBSX subdirectory, enter
the following commands:
CD \BBSX
BBS
51
* If BBS.BAT is stored in a subdirectory specified by
the DOS PATH environment variable, enter the
command:
BBS
BBSX will load and answer incoming calls automatically.
════════════════════
LEARNING TO USE BBSX
════════════════════
We don't provide a comprehensive "command reference" for BBSX
-- it's not necessary. We think you'll agree that BBSX's
interface is intuitive for novice and professional users alike.
Users adapt quickly to BBSX's instinctive approach to BBSing;
the less documentation there is to wade through, the faster users
get up to speed.
Jump in and start exploring the BBSXperience (tm). Feel free
to call for support (215-333-8274/voice or 215-333-8275/data)
should the need arise.
══════════════════════════════════
REQUIRED MODEM DIP-SWITCH SETTINGS
══════════════════════════════════
The following DIP-switch settings correspond to the Hayes
Smartmodem 1200 (external) and the MultiTech MultiModem 224E
(external); your modem's DIP-switches may not correspond to this
chart:
SWITCH POSITION FUNCTION
────────────────────────────────────────────────────────
1 DOWN Modem ignores status of DTR
2 UP Enables verbose (word) responses
3 DOWN Enables command responses
4 UP Enables command character echo
5 UP Enables auto-answer
6 UP DCD & DSR reflect actual status
7 UP Single line telephone jack
8 DOWN Enables command mode
The following DIP-switch settings correspond to the Hayes
Smartmodem 1200B (internal); your modem's DIP-switches may not
correspond to this chart:
SWITCH POSITION FUNCTIONS
────────────────────────────────────────────────────────
1 RIGHT Designates a COM1 device*
2 LEFT Single line telephone jack
3 RIGHT DCD reflects actual status
4 RIGHT Modem ignores status of DTR
52
(*1 LEFT Designates a COM2 device)
The modem must be set to ignore the status of DTR (generally
referred to as "forcing DTR on"). Otherwise, the modem will hang
up on callers after CONNECTing and during file transfers.
Ignoring the status of DTR should not adversely effect other
communications programs.
Notes:
1. Some modems do not have DIP-switches. Instead, AT-
and S-register commands are used for configuration.
Modems that do not use DIP-switches usually use an
"AT&D0" command to force DTR on. By adding "&D0" to
the MODEM_INI string, the modem will be configured
to ignore the status of DTR. (See Step 1, item 8,
in the "Editing the BBSX.INI file" section, above.)
Refer to the modem manufacturer's owners manual for
the appropriate commands, or call us for support.
2. DCD = Data Carrier Detect (usually referred to as
"Carrier Detect"), DTR = Data Terminal Ready.
══════
HOW TO
══════
1. USE ANOTHER DISK OR SUBDIRECTORY NAME
For reference purposes, this document calls the main
BBSX data directory "BBSX." You can name and locate
the main BBSX data directory any way you like.
Remember to change the .BAT files (see Steps 5
through 8, the "Editing the *.BAT file" sections,
above) to reflect the correct drive and directory
where the BBSX files are stored.
2. CREATE OR CONVERT FILE DESCRIPTION FILES
File descriptions are stored in ASCII text files
named FILES.LST. Each files directory must contain
a FILES.LST file; the INSTALL.BAT file created
temporary FILES.LST files during the installation
process.
FILES.LST files are formatted exactly like the
output of a DOS DIR command. The easiest way to
create or add information to a FILES.LST file is to
use the following command:
CD [files_path*]
DIR >> FILES.LST
53
(*See Step 3, item 4, in the "Editing the FILES.INI
file" section, above.)
54
Load FILES.LST into any ASCII editor and delete the
DOS-specific data:
Volume in drive C is BBSX <- Delete
Directory of C:\FILES\EXAMPLE <- Delete
<- KEEP
. <DIR> 8-09-88 6:29p <- Delete
.. <DIR> 8-09-88 6:29p <- Delete
FOO MS 1234 1-01-80 12:24a <- KEEP
BASIC60I S#1 1988 10-08-88 11:09a <- KEEP
WHATSUP DOC 808 7-30-86 9:44a <- KEEP
FILES LST 0 8-13-88 8:21a <- Delete
SHNICK ARC 128 12-12-52 12:55p <- KEEP
PLORK TXT 3476 9-30-88 1:59p <- KEEP
8 File(s) 922509568 bytes free <- Delete
||
||
Column 24
|
Column 25
Next, delete the time stamps, and enter the file
descriptions where the times used to be (2
characters after the file date). Descriptions can
be up to 47 characters long.
To convert RBBS, PCBoard, Postmaster or other ASCII
text file descriptions to BBSX's format, rename the
old files "FILES.LST." Next, confirm the date field
starts in the 24th column of the text (because
BBSX's "NEW" files search expects to find it there).
Note that months less than two digits long have a
blank space in the 24th column (see diagram, above).
════════════════════════
BBSX'S F KEY ASSIGNMENTS
════════════════════════
System keys On-line keys
────────────────────────────────────────────────────────
F1 Help F2 Who's on
F3 Speaker F4 Extended caller info
F5 Screen F6 Force chat
F7 Reserve system F8 Disconnect caller
F9 Date/time F10 Clear/cancel
55
═══════════════
TROUBLESHOOTING
═══════════════
1. MODEM HANGS UP ON CALLERS
The modem is not 100% Hayes-compatible or is not set
to ignore the status of DTR.
Confirm the modem is set to ignore the status of
DTR. (See the "REQUIRED MODEM DIP-SWITCH SETTINGS"
section, above.)
2. MODEM WON'T HANG UP
The modem is not 100% Hayes-compatible or the
MODEM_INI and MODEM_TIMER fields in BBSX.INI are not
set correctly.
Confirm the MODEM_INI and MODEM_TIMER fields in
BBSX.INI are set correctly. (See Step 1, items 8
and 9, in the "Editing the BBSX.INI file" section,
above.)
Some Practical Peripheral's (PPI) modems do not
respond to the escape code sent by BBSX at the end
of a call and, consequently, cannot hang up the
phone. Practical Peripherals acknowledged a bug in
PPI EPROM versions 1.04 and earlier is at the root
of this problem. Owners of PPI modems can call PPI
Tech Support at 1-818-706-2474 and request a free
EPROM upgrade. We thank PPI for their outstanding
support.
3. SYSTEM HANGS DURING DROPS TO DOS
The DOS.BAT file is not configured correctly (see
Step 7, the "Editing the DOS.BAT file" section,
above).
Confirm there is enough free RAM to run COMMAND.COM
after BBSX has loaded.
Do not run programs within the DOS shell unless they
support redirection. Programs supporting standard
DOS input and output (DOS commands and DOS programs,
like EDLIN) can be run through the COM ports.
56
Some MS DOS releases feature a buggy CTTY command
that causes system lock-ups during redirected
backspacing. Users of true-blue IBM PC DOS will not
encounter this bug. If you experience difficulty
with the drop-to-DOS function, visit the Mother
Board BBS and download GAPCTY.ARC or GATEWAY.ARC.
Both files contain enhancements to the CTTY command
that resolve the bugs.
4. FILE TRANSFERS BOMB
The PROTOCOL.INI and/or FTX.BAT file configurations
are incorrect. (See Step 4, the "Storing the
PROTOCOL.INI file" section and Step 8, the "Storing
the FTX.BAT file" section, above).
Confirm the FTX.BAT file and external file transfer
protocol drivers are stored in the BBSX subdirectory
or in a subdirectory specified by the DOS PATH
environment variable.
Confirm the external file transfer protocol drivers
are setting the correct ERRORLEVELs.
Confirm the FILES_PATH path names specified in
BBSX.INI or FILES.INI are considered legal by DOS
and actually exist.
Confirm the PROTOCOL_CODEs specified in BBSX.INI or
PROTOCOL.INI are correct.
If FTX.BAT has been edited, confirm the changes
conform with FTX.BAT's documented programming
conventions.
If all else fails, reinstall the original FTX.BAT
and PROTOCOL_CODEs provided with BBSX.
════════════════════════════
ERROR CODES AND EXPLANATIONS
════════════════════════════
1. Endless loop error
See the explanation of LOOP ERROR, below.
2. Bad command or file name
BBSX was unable to launch a child process (like
DAILY.BAT, DOS.BAT or FTX.BAT).
Confirm the child process files are stored in the
BBSX subdirectory or in a subdirectory specified by
the DOS PATH environment variable.
57
3. Bad FILES_PATH in BBSX.INI or FILES.INI
A FILES_PATH field in BBSX.INI or FILES.INI file
contains illegal characters or does not exist.
Double check the FILES_PATHs to confirm the path
names are considered legal by DOS and actually
exist.
4. Bad or outdated .HDR
BBSX encountered a corrupted or outdated .HDR file.
Delete the file and associated .MSG and .PTR files.
If DAILY.BAT is used, backups might be stored in the
BAK <DIR>. Restore the files from the backups.
5. Bad or outdated USER.LOG
BBSX encountered a corrupted or outdated USER.LOG
file.
Delete the file and the associated INDEX.LOG.
If DAILY.BAT is used, backups might be stored in the
BAK <DIR>. Restore the files from the backups.
6. BBSX.INI file not found
BBSX cannot find the BBSX.INI file in the BBSX
subdirectory.
The BBSX.INI file must be stored in the directory
specified by the BBS.BAT file.
7. Communication-buffer overflow
The communications receive buffer (1024 bytes)
overflowed. Usually caused by an on-line user
leaning on the keyboard.
8. Device fault
Device timeout
Device unavailable
Disk media error
Disk not ready
Indicates a hardware configuration problem (like an
open disk drive door; bad, non-existent or
incorrectly specified device) or a hardware failure.
Check disk drive doors, printer switches, cables,
connections, and related hardware.
58
9. Device I/O error
An unrecoverable I/O error occurred. Usually caused
by an on-line user repeatedly striking ^ScrollLock,
sending extended break signals or leaning on the CR
key during autobaud (baud rate adjust).
If a modem is not 100% Hayes-compatible, the escape
code sent by BBSX may not be processed correctly,
possibly causing this error.
10. Disk full
The disk is full.
Delete some non-BBSX related files and try again.
11. Out of environment space
There is not enough DOS environment space available.
Increase environment space with the DOS "SHELL"
command. See your DOS manual for information on the
SHELL command.
12. Out of memory
Out of string space
BBSX needs more RAM than is available.
Unload TSRs (memory resident utilities like
"SideKick") or buy a RAM card to increase the amount
of on-board RAM.
13. Out of paper
The printer is out of paper or the paper is jammed.
Add paper or clear the paper path.
14. Path/File access error
Path not found
BBSX was unable to access a path specified in
BBSX.INI or FILES.INI file.
Review the BBSX.INI and FILES.INI files to confirm
that the specified paths exist on the hard disk and
the path names are syntactically correct.
59
15. Permission denied
An attempt was made to write to a write-protected
disk or to a locked file in a multi-user
environment.
16. /SYSOP switch active
The /SYSOP start-up switch was used on the BBSX
command line.
Remove the /SYSOP switch from the command line.
17. Too many files
BBSX was unable to open multiple files.
Try adding the following statement to the CONFIG.SYS
file:
FILES = 25
18. Too many response lines allocated in [ *.POL ]
The allocated responses (input commands) in the .POL
file exceeds 999.
Reduce the number of allocated responses. A maximum
of 999 response lines per .POL file is allowed.
19. Loop error
See the explanation for ENDLESS LOOP ERROR, above.
60
────────────
FATAL ERRORS
────────────
The following error messages should not occur. If they do,
they indicate an internal programming problem (read: bug) within
BBSX. Contact us if any of these error messages are encountered
more than once:
RETURN without GOSUB
Out of DATA
Illegal function call
Overflow
Subscript out of range
Division by zero
String formula too complex
No RESUME
RESUME without ERROR
CASE ELSE expected
Variable required
FIELD overflow
Internal error
Bad file name or number
File not found
Bad file mode
File already open
FIELD statement active
File already exists
Bad record length
Input past end of file
Bad record number
Bad file name
Advanced feature unavailable
Rename across disks
User record alias error
Inter-module communication error
Unassigned error
Total global thermonuclear war error
══════════════════════════════════════════════
APPENDIX A - FILE TRANSFER TECHNICAL REFERENCE
══════════════════════════════════════════════
────────────────────────
Editing the FTX.BAT file
────────────────────────
The following information is provided for programmers only;
to guarantee its correct operation, non-programmers should not
edit FTX.BAT.
BBSX does not support internal file transfer protocols.
Instead, strong support for most external file transfer protocol
drivers is provided.
61
Omen Technology's DSZ program is recommended for use with
BBSX to support Xmodem (128 and 1k), Xmodem Over-thruster, Ymodem
(128 and 1k), Ymodem Over-thruster, Zmodem and Zmodem
Over-thruster, as well as mutant variations on these standard
protocols. We have been advised that Omen Technology's ZCOMM
also supports these protocols, as well as Kermit, Sealink and
others.
Any manufacturer's protocol drivers can be used, as long as
they support the standard command syntax and error reporting
conventions as Omen Technology's DSZ and ZCOMM programs.
Protocol drivers that do not generate a DOS "errorlevel"
corresponding to the success or failure of a file transfer
prevent programmers from testing conditions in FTX.BAT.
BBSX sends the following information to FTX.BAT. Programmers
can configure support for almost any protocol driver. If you are
not an experienced batch file programmer, do not attempt to
modify the parameter control code in FTX.BAT:
Parameter = Data sent by BBSX
────────────────────────────────────────────────────
%1 = com port # (1 or 2)
%2 = baud rate (300, 1200, 2400, or 9600)
%3 = s = user download, r = user upload
%4 = protocol_code* selected by user
%5 = target [d:][path][filename.ext]
(*See the "Editing the PROTOCOL.INI file" section,
below.)
The steps to add support for additional protocol drivers are:
1. Add the new PROTOCOL_NAMEs and PROTOCOL_CODEs* to
PROTOCOL.INI.
2. Add the conditional branch
if %4 == [PROTOCOL_CODEs] goto [labels]"
beneath FTX.BAT's "TOP" label.
3. Port the batch file code under the "DSZ" label to
suit the new application programs.
The "if errorlevel" portion of the code tests for failed
transfers. The logic followed is:
if errorlevel = 1 (failure) then
delete the bbsx.tmp file**
exit
else
exit
end if
62
(*See the "Editing the PROTOCOL.INI file" section,
below.)
(**Because the Microsoft Professional BASIC Compiler
[v.6.0] is unable to retrieve the errorlevel of a child
process without extensive fiddling, BBSX.TMP is created
by BBSX before file transfers; non-existence tells BBSX
that the transfer failed.)
Note that aborted uploads cause FTX.BAT to delete the
incomplete file.
FTX.BAT must be edited using an ASCII editor operating in
non-document mode.
63
Load FTX.BAT into any ASCII editor. The following text will
be displayed:
echo off
goto top
Rich Levin's BBSXpress (tm)
FTX.BAT
Copyright (c) 1988 Richard B. Levin
All Rights Reserved
Revised January 10, 1989
:top
if %4 == b goto dsz
if %4 == b-k goto dsz
if %4 == x goto dsz
if %4 == x-k goto dsz
if %4 == z goto dsz
goto s_err
:dsz
if %3 == r goto dsz_r
if %3 == s goto dsz_s
goto xit
:dsz_r
dsz port %1 speed %2 r%4 %5
if errorlevel 1 goto r_err
if not exist %5 goto r_err
goto xit
:dsz_s
dsz port %1 speed %2 s%4 %5
if errorlevel 1 goto s_err
goto xit
:r_err
rem failed receive attempts branch here
rem change del %5 to ren %5 to save aborted uploads
if exist %5 del %5
if exist bbsx.tmp del bbsx.tmp
goto xit
:s_err
rem failed send attempts branch here
if exist bbsx.tmp del bbsx.tmp
goto xit
:xit
if exist *.$$$ del *.$$$
64
─────────────────────────────
Editing the PROTOCOL.INI file
─────────────────────────────
PROTOCOL.INI must be edited using an ASCII editor operating
in "non-document" mode.
Load PROTOCOL.INI into any ASCII editor. The following text
will be displayed:
~ Rich Levin's BBSXpress (tm)
~ PROTOCOL.INI
~ Copyright (c) 1988 Richard B. Levin
~ All Rights Reserved
~
~ Revised January 10, 1989
~
~ Precede comments with a tilde.
~ Delete comments to optimize this file.
~
PROTOCOL_NAME=Xmodem 128
PROTOCOL_CODE=x
PROTOCOL_NAME=Xmodem 1k
PROTOCOL_CODE=x-k
PROTOCOL_NAME=Ymodem 128
PROTOCOL_CODE=b
PROTOCOL_NAME=Ymodem 1k
PROTOCOL_CODE=b-k
PROTOCOL_NAME=Zmodem
PROTOCOL_CODE=z
END_OF_PROTOCOLS=Y
Edit each field to reflect your configuration requirements:
1. ~ Rich Levin's BBSXpress (tm)
A comment. Text preceded by a tilde character is
ignored by BBSX.
2. PROTOCOL_NAME=
The name of a file transfer protocol. 50 characters
maximum. Control characters and high-bit ASCII are
accepted.
Every PROTOCOL_NAME must be followed by a
PROTOCOL_CODE.
65
3. PROTOCOL_CODE=
The protocol identification command parameter sent
by BBSX to FTX.BAT (see the "Editing the FTX.BAT
file" section, above). 9 characters maximum.
Every PROTOCOL_CODE must be preceded by a
PROTOCOL_NAME.
Important: Do not use spaces in the PROTOCOL_CODE
field; they prevent BBSX from supplying
drive, path, and filename data to
FTX.BAT.
4. END_OF_PROTOCOLS=Y
An end-of-data (EOD) flag. Must be the last entry
in PROTOCOL.INI. BBSX stops searching for PROTOCOL_
fields when this field is encountered.
This EOD flag also allows users to optionally merge
PROTOCOL.INI into BBSX.INI, providing a central
initialization file. If PROTOCOL_ fields are merged
into BBSX.INI, the PROTOCOL.INI file is not used;
however, BBSX performs better when PROTOCOL.INI and
BBSX.INI are not merged.
══════════════════════════════════════
APPENDIX B - TCD.COM COMMAND REFERENCE
══════════════════════════════════════
TCD ("The Carrier Detective") is a utility used to re-boot an
IBM-compatible computer when DCD (Data Carrier Detect) is lost.
TCD is used in batch files called by telecommunication hosts
before and after providing remote users access to DOS.
Once activated, TCD continuously monitors the status of DCD.
If DCD is lost, TCD re-boots the host computer. The host
completes a POST (power-on self-test) and processes CONFIG.SYS
and AUTOEXEC.BAT files. The last command in AUTOEXEC.BAT should
be one to restart the host.
If DCD is not lost, TCD is toggled off by the batch files
after users exit DOS level.
Using TCD in this manner prevents hosts from sitting idle at
DOS-level, allowing unauthorized users unrestricted access when
carrier is dropped.
TCD is often used by bulletin board system's external "doors"
programs, file transfer protocols, and "drops-to-DOS." It can
also be used by telecommunication programs providing remote DOS
access.
66
────────────────────────────
COMMAND LINE ARGUMENT SYNTAX
────────────────────────────
Launch syntax is
TCD COM[1|2|3|4] [ON|OFF] [Q] [?|H]
Where:
PARAMETER = DESCRIPTION
─────────────────────────────────────────────────────────────────
COM# Serial communications port assignment, where "#"
represents the RS232C channel number used for
remote access.
ON or OFF ON installs and activates TCD. OFF deactivates
and uninstalls TCD.
Q Quiet mode. Suppresses messages from TCD.
Ignored if an error occurs.
? or H Help command. Displays program information.
The first two parameters (COM# and ON|OFF) are required for
proper operation of TCD.
──────────────────────────────────
EXAMPLES OF COMMAND LINE ARGUMENTS
──────────────────────────────────
TCD Displays TCD syntax
TCD /COM1 /ON Loads and activates TCD monitoring of COM1
TCD /COM1 /OFF Unloads and deactivates TCD monitoring of COM1
TCD /COM2 /ON Loads and activates TCD monitoring of COM2
TCD /COM2 /OFF Unloads and deactivates TCD monitoring of COM2
TCD /COM3 /ON Loads and activates TCD monitoring of COM3
TCD /COM3 /OFF Unloads and deactivates TCD monitoring of COM3
TCD /COM4 /ON Loads and activates TCD monitoring of COM4
TCD /COM4 /OFF Unloads and deactivates TCD monitoring of COM4
TCD /H Displays TCD program information
67
This document was created using Microsoft WORD v.4.0
- End of BBSX.DOC -
