BBSXpress (tm)
BBSXUSER.DOC
Copyright (c) 1988 Richard B. Levin
All Rights Reserved
Revised October 23, 1988
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
THIS IS *NOT* FREE SOFTWARE!
THIS PROGRAM IS DISTRIBUTED AS SHAREWARE. IF YOU USE IT, PLEASE PAY FOR IT.
Projects of this kind take time and money to develop. Please support the BBSX
project and the shareware concept by sending in your paid registration.
>>>-> BBSX PRICE: $50.00 PER COPY (Cheap) <-<<<
See the "REGISTRATION FORM" section, or REGISTER.DOC, for remittance address
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
========================
DOCUMENT FORMATTING NOTE
========================
This document, and all BBSX .DOC files, are formatted for 80 columns,
no margins, no page breaks, with tabs set every 8 characters.
============
PROGRAM INFO
============
Program: BBSXpress (tm)
Function: Multi-node, multi-SIG, multi-LIB, e-mail and file transfer system
Class: PC/MS DOS compatible bulletin board system (BBS)
Price: $50.00 per node/per PC
Editor: Norton Editor v.1.3C
Compiler: Microsoft BASIC v.6.0
Math LIB: BC6 Alternate (/FPA)
Linker: Microsoft Segmented-Executable LInker v.5.01.20
Trace: AddLine v.1.5
Author: Richard B. Levin
Contact: BBSoft, P.O. Box 14546, Phila., PA 19115
Voice: (215) 333-8274
BBS: The Mother Board @ (215) 333-8275 (300/1200/2400)
Documentation written by: Richard B. Levin
Documentation edited by: Carol Levin
Katherine Margolis
Principal distribution points: The BBSoft Support BBS (see above)
CompuServe Information Service IBMNET
GEnie IBM and BBS RoundTables
BBSXpress is published by:
BBSoft
9405 Bustleton Ave. Lab: (215) 333-8274 We Give
P.O. Box 14546 BBS: (215) 333-8275 Free Support!
Phila., PA 19115
The latest version of BBSXpress is available for downloading on the
BBSoft Support BBS. Support is also available through the BBSoft Lab. Please
leave a message on our answering machine if we are unable to answer your call
personally. We return long distance calls collect.
================
COPYRIGHT NOTICE
================
The names "BBSoft," "BBSXpress," "BBSX," and the BBSXpress program,
documentation, BBSXpress-created input and output files, file formats, visual
displays, interface, look, and feel (hereinafter referred to as "the BBSX
system") are copyright (c) and trade mark (tm) 1988 Richard B. Levin
(hereinafter referred to as the author), all rights reserved.
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 end user
"as is" without warranty of any kind, either express or implied. No part of
the BBSX system may be reproduced without the express written permission of
the author.
The BBSX system is protected by United States Copyright Law (Title 17
United States Code). Unauthorized reproduction, duplication, transfer, and/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.
==============
UPGRADE POLICY
==============
The latest copy of BBSX is stored on the BBSoft Support BBS (listed
above), in the BBSoft Product Carousel, and may be downloaded at any time.
Upgrades are regularly posted to DL0 in the IBMCOM Forum of IBMNET on
the CompuServe Information Service (GO IBMCOM) and in the IBM and BBS
RoundTables on the General Electric Network for Information Exchange (GEnie).
=================
REGISTRATION FORM
=================
ALL USERS ARE REQUIRED BY LAW TO COMPLETE AND RETURN THIS FORM WITHIN
TEN DAYS OF THE ACQUISITION OF THE BBSX SYSTEM.
- - - - - - - - - - - - - - - - - Tear Here - - - - - - - - - - - - - - - - - -
Print, complete, and mail to: Rich Levin's BBSoft Co.
BBSXpress Registration
P.O. Box 14546
Phila., PA 19115
IMPORTANT: MAKE CHECKS PAYABLE TO "RICHARD B. LEVIN"
Do NOT make checks payable to BBSoft or BBSX
Please HAND PRINT your responses to the registration questionnaire.
Please do NOT type or computer-print your responses.
If necessary, use additional sheets of paper to complete questionnaire.
Registered Owner Name: _______________________________________________________
_______________________________________________________________________________
Title: _______________________________________________________________________
_______________________________________________________________________________
Department: __________________________________________________________________
_______________________________________________________________________________
Company: _____________________________________________________________________
_______________________________________________________________________________
Address: _____________________________________________________________________
_______________________________________________________________________________
P.O. Box: ____________________________________________________________________
_______________________________________________________________________________
Mail stop: ___________________________________________________________________
_______________________________________________________________________________
City: ________________________________________________________________________
State: _______________________________________________________________________
Zip: _________________________________________________________________________
Phone: ( ) -
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 which are NOT supported now?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Have you ever run a BBS before? [ ] Yes [ ] No
Please list the name(s) of the BBS software you have used 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 BBSoft products? [ ] Yes [ ] No
Please list the name(s) of the BBSoft product(s) you own or use if you
answered YES to the previous question:
_______________________________________________________________________________
Please CHECK ONE: I am [ ] REGISTERING the SHAREWARE version of BBSX
I am [ ] PURCHASING the DISK version of BBSX *
* Purchasers of the disk version receive BBSX on a
5.25" floppy disk. 3.5" disks are NOT available.
Total number of SHAREWARE copies being registered: [ ]
@ $50.00 per copy: $ ____________
Total number of DISK copies being purchased: [ ]
@ $75.00 per copy: $ ____________
Shipping & handling (DISK copies only) @ $ 5.00 per copy: $ ____________
Total amount enclosed: $
============
- - - - - - - - - - - - - - - - - Tear Here - - - - - - - - - - - - - - - - - -
============================
BBSX: THE PERSONAL BBS (tm)
============================
BBSX, the personal BBS, remains true to the spirit of shareware and
personal computing. BBSX provides users with an inexpensive, full-featured,
user supported alternative to commercial systems. It's easy to buy, easy to
install, easy to use, and easy to maintain. Plus, 24 hour voice and data
support is free for the asking.
In this, it's first build, BBSX provides most, if not all, of the
popular features demanded by callers and SysOps. Additionally, BBSX users are
not burdened with configuration limitations, nor are they subject to the
drudgery of BBS maintainance. On the contrary, BBSX imposes no limit to the
number of conferences, files areas, protocols, bulletins, questionnaires, or
message sizes, and system maintainance is fully automated.
============
INTRODUCTION
============
You and I have something in common. You probably hate reading
software documentation, and I certainly hate writing it. On the other hand,
you're interested in running a new BBS software program, and I'm interested in
having you run mine.
BBSXpress ("BBSX") was designed to require little supporting
documentation. Configuring the program consists of editing the
self-documenting .BAT files and BBSX.INI file, running the program with the
"/SYSOP" switch to install yourself as a "SysOp," (optionally) creating the
bulletins, bulletin menu, polls, polls menu, and (optionally) making upload
and download directories.
Even if you have never run a BBS before, you will probably have BBSX
up and running in 90 minutes or less. Take a look at the "A Step By Step
Guide To Getting Started" section, and you're off.
If you have any problems or questions, feel free to call BBSoft
Support (215 333 8274) or the BBSoft Support BBS (215 333 8275) anytime.
================
BEFORE YOU BEGIN
================
BBSX does not have unusual hardware or software requirements, and will
run on any IBM PC, XT, AT, PS/2, or true compatible, using a Hayes or Hayes
compatible modem. BBSX also provides support for null modems, no-modem
connections, non-Hayes compatible modems, and other unusual configurations.
No changes have to be made to your AUTOEXEC.BAT or CONFIG.SYS files,
nor do any settings have to be placed within your DOS environment. Further,
BBSX co-exists well with most DOS reassignment commands (such as SUBST and
JOIN), RAM disks (such as VDISK.SYS), disk caches (such as PC-SuperKwik and
PolyBoost II), console enhancement utilities (such as QuicKeys and Cruise
Control), most TSR's (such as SideKick), DOS shells (such as the Norton
Commander, DesqView, and DoubleDOS), and most EMS/EEMS software.
Note that your system will perform better with BBSX, and other
programs, if you use 33, or more, DOS disk buffers. If you are using a
write-through disk cache, DOS disk buffers will still significantly increase
system performance when set in multiples of 8 per cached disk, where 8 = 4224
buffer bytes per disk, or 2 disk clusters. If your system uses larger of
smaller cluster sizes, adjust this calculation accordingly.
To set disk buffers, add the following line to your CONFIG.SYS file:
BUFFERS = 33
(or whatever number of buffers you wish to set)
==========================================
MINIMUM HARDWARE AND SOFTWARE REQUIREMENTS
==========================================
IBM PC, XT, AT, PS/2, or true compatible
384k RAM
Monochrome monitor
Hard disk
Hayes 300, 1200, 2400, or 9600 baud modem or true compatible
PC/MS DOS v.3.0 or higher
===============================
NOTE TO ADVANCED COMPUTER USERS
===============================
See the FASTART.DOC file if you want to get BBSX up and running right
away, and you are an experienced computer user.
If you are not an advanced computer user, follow the step-by-step
installation instructions which follow.
=======================================
A STEP BY STEP GUIDE TO GETTING STARTED
=======================================
Follow these steps to configure, install, and run your new BBSXpress
software. If you have any problems or questions, feel free to call BBSoft
Support (215 333 8274) or the BBSoft Support BBS (215 333 8275) anytime.
* COPY ALL OF THE BBSX FILES INTO THE BBSX DIRECTORY
Make a directory on the root of your hard disk named "BBSX". Next,
copy all of the BBSX files into the BBSX subdirectory.
(Note: If you did not download your BBSX files from CompuServe,
GEnie, or the BBSoft Support BBS, you should do so as soon as possible. Many
times, the BBSX files found on your neighborhood BBS are incomplete or out of
date. If BBSX is missing any of it's system files, it will not run properly.)
* EDIT THE BBSX.INI FILE
Run your ASCII text editor and load "BBSX.INI." Read and follow the
instructions contained in the BBSX.INI file as you edit.
* EDIT THE BBSX .BAT FILES
Run your ASCII text editor and load, one at a time, each of the BBSX
.BAT files. Read and follow the instructions contained in each .BAT file as
you edit.
* EDIT THE MENU.BLT FILE
Run your ASCII text editor and load "MENU.BLT." Read and follow the
instructions contained in the MENU.BLT file as you edit.
* CREATE YOUR SYSTEM BULLETINS
The MENU.BLT file explained how to create your system bulletins.
Sample system bulletins are provided under the filenames "1.BLT," "2.BLT," and
"3.BLT."
* EDIT THE MENU.POL FILE
Run your ASCII text editor and load "MENU.POL." Read and follow the
instructions contained in the MENU.POL file as you edit.
* CREATE YOUR SYSTEM POLLS
The MENU.POL file explained how to create your system polls. Sample
system polls are provided under the filenames "1.POL," "2.POL," "3.POL,"
"4.POL.," and "5.POL."
* DOUBLE CHECK EVERYTHING!
You were guided through the BBSX configuration process as you edited
BBSX.INI, and the .BAT, .BLT, and .POL files, by the instructions contained in
each of those files.
Before you run BBSX for the first time, review this launch checklist:
[ ] Make sure that you have a BBSX subdirectory off the root of your
hard drive.
[ ] Make sure that ALL of your BBSX data files are stored in the BBSX
directory.
[ ] Make sure that ALL of your BBSX .BAT files are stored in a
subdirectory included in your DOS PATH.
[ ] Make sure that ALL of your BBSX .BAT files have been edited to
reflect the correct drive and directory where your BBSX files are stored.
[ ] Make sure that you have added the correct start-up switches, if
any, to the BBS.BAT file as documented in BBS.BAT.
[ ] Make sure that BBSX.EXE is stored in your BBSX subdirectory, or in
a subdirectory included in your DOS PATH.
[ ] Make sure that the BBSX run-time module, BRUN60AR.EXE is stored in
your BBSX subdirectory, or in a subdirectory included in your DOS PATH.
[ ] Make sure that TCD.COM (The Carrier Detective) is stored in your
BBSX subdirectory, or in a subdirectory included in your DOS PATH.
[ ] Make sure that COMMAND.COM is stored in a subdirectory included in
your DOS PATH *AND* that your COMSPEC environment variable is SET to point to
COMMAND.COM (see your DOS manual for more info on the COMSPEC).
[ ] Make sure that your external file transfer protocol drivers (such
as DSZ.EXE) are stored in your BBSX subdirectory, or in a subdirectory
included in your DOS PATH, as documented in the FTX.BAT file.
[ ] Review your BBSX.INI file (and alternate .INI files, if you are
using them) and make sure they're properly configured.
[ ] If you are using files areas, make sure that the paths to your
files subdirectories correspond to those specified in BBSX.INI (or FILES.INI,
if you are using alternate .INI files).
[ ] If you are using files areas, make sure that each files
subdirectory containing files available for downloading also contains a
FILES.LST file (see the section on HOW TO CREATE OR CONVERT FILE DESCRIPTION
FILES, later in this document, for more information regarding the creation of
FILES.LST files).
[ ] Make sure that ALL of the .BLT files, if you are using them, have
been edited to your satisfaction.
[ ] Make sure that ALL of the .POL files, if you are using them, have
been edited to your satisfaction.
[ ] Make sure that your modem is ON and is hooked up properly.
[ ] Make sure that your modem DIP switches are set to FORCE DTR TRUE.
[ ] Make sure that you have enough free RAM to run BBSX. BBSX
requires at least 384k of free RAM.
[ ] Make sure that you are running DOS 3.0 or higher.
* RUN BBSX AND INSTALL YOURSELF AS SYSOP
The FIRST TIME (and ONLY the first time) you run BBSX, start it up
WITHOUT using the BBS.BAT file, but USING the "/SYSOP" start-up switch, as
follows:
BBSX /SYSOP
*************************************************
BBSX will prompt: You will:
*************************************************
Local (CR), Quit (ESC) Press CR (a/k/a the ENTER key)
First name: Enter your first name
Last name: Enter your last name
Password: Enter your password
Are you a NEW user (y/N)? Enter the letter Y
Calling from (City and State): Enter your city and state
BBSX will automatically log your SysOp information to disk, and then
display the MAIN menu. After BBSX displays the MAIN menu, press ESC *TWICE*
to Quit to DOS.
Do NOT run BBSX with the /SYSOP switch again unless you are
reinstalling your BBSX system from scratch.
-------------------------------------------------------------------------------
NOTES:
1. Use a password that YOU and ONLY YOU will know. Do NOT use the
same passwords that you use on other boards.
2. You will NEVER have to use the /SYSOP start-up switch again,
UNLESS your USER.LOG file is damaged or accidentally deleted, and you are
reinstalling your system from scratch.
-------------------------------------------------------------------------------
* RUN BBSX USING THE BBS.BAT FILE
Enter the following command to run BBSX using the BBS.BAT file:
BBS
*************************************************
BBSX will prompt: You will:
*************************************************
Local (CR), Quit (ESC) Press CR (a/k/a the ENTER key)
First name: Enter your first name
Last name: Enter your last name
Password: Enter your password
BBSX will log you in and present you with the MAIN menu.
Now you can begin your BBSX user education. Charge right ahead and
explore the many menus and their commands. Post a message or two to your
users. Try and figure out where we've hidden the SysOp's menu (don't worry -
you'll find it). Don't be afraid to experiment or try an unusual command.
BBSX will guide you through each step of every command process.
After you log-off, leave BBSX running, and your callers will be
managed automatically by your new BBSXpress BBS. Welcome aboard, SysOp!
===============
WHAT TO DO IF'S
===============
>>>-> REMEMBER: WE GIVE FREE SUPPORT! CALL THE BBSOFT HOTLINE (215 333 8274)
OR THE BBSOFT SUPPORT BBS (215 333 8275) ANYTIME FOR FREE TECHNICAL SUPPORT.
* IF YOUR MODEM HANGS UP ON CALLERS
Make SURE that you have DTR FORCED ON. See the explanation of the
MODEM_INI field in BBSX.INI for more information.
* IF YOUR MODEM WON'T HANG UP AFTER A CALL
Make sure that the MODEM_INI and MODEM_TIMER fields in BBSX.INI are
set correctly.
Note that some Practical Peripheral's (PPI) modems do not respond to
the escape code sent by BBSX at the end of a call and, consequently, BBSX
cannot command the modem to hang up the phone. Instead, BBSX waits for the
user to drop carrier.
Practical Peripherals has acknowledged that a bug in PPI EPROM
versions 1.04 and earlier is at the root of this problem. Owners of PPI
modems should call PPI Tech Support at 1-818-706-2474 and request a *FREE*
EPROM upgrade.
* IF YOUR SYSTEM HANGS DURING DROPS TO DOS
Double check DOS.BAT for proper configuration. Also, make sure you
have enough free RAM to run COMMAND.COM after BBSX is loaded. Finally, do NOT
run any programs within the drop to DOS shell unless you are CERTAIN they are
able to be run via the COM port. ONLY programs which support standard DOS
input and output (such as all DOS commands and DOS programs, like EDLIN) may
be run via the COM port.
IMPORTANT NOTE: Most versions of MS DOS feature a buggy CTTY command
which can cause a system to lock-up during redirected DOS-level backspacing.
Users of true blue IBM PC DOS probably will not encounter this bug. However,
if you experience difficulty with BBSX's, or any program's, drop to DOS
function, visit the BBSoft Support BBS (215 333 8275) and download GAPCTY.ARC
and/or GATEWAY.ARC. Both files contain enhancements to the CTTY command which
should resolve the MS DOS bugs and other potential problems.
* IF YOUR FILE TRANSFERS BOMB
Your FTX.BAT file configuration is probably wrong.
Double check that the FTX.BAT file and your external file transfer
protocol drivers are stored in a subdirectory specified in your DOS PATH.
Make sure that your external file transfer protocol drivers are
setting the correct ERRORLEVEL after each file transfer attempt.
Make sure that the FILES_PATHs specified in BBSX.INI (or FILES.INI, if
you are using alternate .INI files) correspond to the file paths on your hard
disk.
Make sure that the PROTOCOL_CODEs specified in BBSX.INI (or
PROTOCOL.INI, if you are using alternate .INI files) are correct.
If you have edited FTX.BAT, make sure that the changes you made
conform with the FTX.BAT file's stated programming conventions.
If all else fails, reinstall the original FTX.BAT and PROTOCOL_CODEs
provided in the BBSX archive.
* IF USERS COMPLAIN THAT THEIR "MAIL WAITING" MESSAGES ARE OUTDATED
Tell them that they probably have been logging off using the ^C
command, or by dropping carrier. When a user logs off with ^C, or by dropping
carrier, their mail waiting are preserved.
To delete mail waiting messages, users must log off normally.
* IF USERS COMPLAIN THAT THEIR MESSAGE POINTERS ARE INCORRECT
Tell them that they probably have been logging off using the ^C
command, or by dropping carrier, before they exited a group. When a user logs
off with ^C, or by dropping carrier, their pointers in the LAST GROUP THEY
VISITED WITHOUT EXITING are NOT updated.
Note, however, that if users exit the group and THEN log off using ^C
or by dropping carrier, their message pointers ARE updated.
* IF USERS COMPLAIN THAT BBSX DOES NOT ADJUST TO NON-STANDARD COMM PARAMETERS
Tell them that BBSX operates using the industry standard communication
parameters of N81. BBSX makes NO attempt to adjust it's communication
parameters to incoming calls beyond the required adjustments for baud rate.
SysOps can use the /E71 start-up switch to force BBSX to use E71 as
it's default communication parameters. Note, however, that most file transfer
protocols will not operate correctly unless they are run at N81.
* IF YOUR MATE THREATENS TO DIVORCE YOU BECAUSE YOU DO TOO MUCH BBSING
Buy him or her their own computer for their birthday, Christmas, or
Hannukka. Then you can have those nice, long, heart-to-hearts through the
board.
========
HOW TO'S
========
>>>-> REMEMBER: WE GIVE FREE SUPPORT! CALL THE BBSOFT HOTLINE (215 333 8274)
OR THE BBSOFT SUPPORT BBS (215 333 8275) ANYTIME FOR FREE TECHNICAL SUPPORT.
* HOW TO USE ANOTHER DISK OR SUBDIRECTORY NAME
BBSX does not care what the name of it's main data directory is, or
where the main data directory is located. For reference purposes, this
document calls the main BBSX data directory "BBSX."
You may name and locate the main BBSX data directory any way you like.
Make sure, however, that you change *ALL* of the BBSX .BAT files to reflect
the correct drive and directory where your BBSX files are stored.
* HOW TO VIEW THE FUNCTION KEY ASSIGNMENTS
Press the F1 key at any time for a list of F key assignments.
* HOW TO CREATE OR CONVERT FILE DESCRIPTION FILES
BBSX stores file descriptions in an ASCII text file called FILES.LST.
Each files directory features its own FILES.LST.
FILES.LST is formatted *EXACTLY* like the DOS DIR command. The
easiest way to create, or add information to, a FILES.LST file is to use the
following DOS command:
DIR >> FILES.LST
Then load FILES.LST into your ASCII editor, and delete all of the DOS
DIR-specific data:
Volume in drive D is MotherBoard <- Delete
Directory of D:\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 ALL of the file TIME stamps. Finally, type in your file
descriptions where the file times used to be (2 characters after the file
date). Descriptions can be up to 47 characters.
To CONVERT an RBBS, PCBoard, Postmaster, or other ASCII text based
file description file over to BBSX, simply rename the old file "FILES.LST."
Next, make sure that the DATE field starts in the 24th column of text, because
BBSX's "NEW" files search expects to find it there. Note that months which
are less than two digits long have a BLANK SPACE in the 24th column (see
diagram, above).
* HOW TO UPLOAD PRIVATE FILES
At the UPLOAD prompt, enter the letter P to make the upload private.
Private uploads do not appear on the files area directory LIST, but can be
downloaded by any user who knows the exact name of the file.
This feature allows users to upload files that are "SysOp-only," and
to exchange personal files while preventing other users from accessing them.
Because the FILES.LST file may contain private file information, BBSX will not
allow any user to download it.
* HOW TO VIEW THE NODE.LOG
The NODE.LOG may be viewed, but NOT edited, using any ASCII file-view
utility or editor. Additionally, BBSX's SYSTEM menu allows SysOps and
Co-SysOps to review the NODE.LOG.
* HOW TO LOCK-OUT USERS
Use the USERS editor to set their ACCESS LEVEL to 0. Whenever the
user logs in, they will be immediately disconnected.
* HOW TO RESTRICT USERS FROM EXECUTING CERTAIN COMMANDS
Access to the following commands can be controlled by the SysOp:
READ
WRITE
UPLOAD
DOWNLOAD
BBSX.INI provides a SECURITY field for each of the above commands. If
the user's security level is LESS than the SECURITY level set in BBSX.INI, the
user will be denied access to the respective command.
See the BBSX.INI file for more information.
Use the USERS editor to set a user's SECURITY LEVEL.
* HOW TO RUN A PRIVATE BOARD
If you do not want the general public to be able to access your BBS,
set NEW_USER_TIME=0 in BBSX.INI. All new users will be disconnected
immediately after logging in. Later, you can upgrade those users who are
entitled to access by using the USERS editor.
* HOW TO ACCESS THE USERS EDITOR
What is it? Where can you find it? How do you use it? These
questions, and more, will be answered as you explore BBSX during your first
session. Tantalizing, isn't it?
* HOW TO KEEP SHAREWARE ALIVE
Send in your paid BBSX registration today!
======================
BBSX 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
================================
BBSX FILE NAMES AND DESCRIPTIONS
================================
The ONLY files which may be, and SHOULD BE, stored in subdirectories
included in your DOS PATH are the .BAT files, BBSX.EXE, the BRUN60AR.EXE
run-time module, TCD.COM, COMMAND.COM, and any external file transfer protocol
drivers you are using (such as DSZ.EXE).
Note that *ALL* .BLT, .POL, FILES.INI, GROUP.INI, and PROTOCOL.INI
files are *OPTIONAL*.
INDEX BAK Backup of INDEX.LOG (ASCII)
USER BAK Backup of the USER.LOG (Binary)
GOODBYE BLT Bulletin displayed after log off (ASCII)
HELLO BLT Bulletin displayed after log on (ASCII)
DOWNLOAD BLT Bulletin displayed before download (ASCII)
NEWS BLT Bulletin displayed after HELLO.BLT (ASCII)
NEWUSER BLT Bulletin displayed to new users after NEWS.BLT (ASCII)
PROTOCOL BLT Bulletin displayed before protocol selection (ASCII)
UPLOAD BLT Bulletin displayed before upload (ASCII)
MENU BLT Bulletin menu (ASCII)
1 BLT Sample bulletin # 1 (ASCII)
2 BLT Sample bulletin # 2 (ASCII)
3 BLT Sample bulletin # 3 (ASCII)
TCD COM The Carrier Detective, a TSR Drop to DOS utility (Binary)
WAITING <DIR> "Mail waiting" messages stored here (auto-maintained - ASCII)
BAK <DIR> Subdirectory created by DAILY.BAT to store critical files backup
BBSXUSER DOC This file (ASCII)
CHANGES DOC Text file describing latest changes to the BBSX system (ASCII)
README DOC Text file describing FaStart (ASCII)
REGISTER DOC BBSoft/BBSXpress Owner Registration Form (ASCII)
TCD DOC Supplemental text file describing TCD options (ASCII)
BBSX EXE BBSX (Binary)
BRUN60AR EXE BBSX run-time module (ASCII)
MAIN HDR Message headers for the MAIN group (Binary)
???????? HDR Message headers for other groups (Binary)
BBSX INI BBSX initialization file (ASCII)
FILES INI List of available files areas (Optional/See BBSX.INI) (ASCII)
GROUP INI List of available message groups (Optional/See BBSX.INI) (ASCII)
PROTOCOL INI List of available protocols (Optional/See BBSX.INI) (ASCII)
INDEX LOG Index to the USER.LOG (ASCII)
DSZ LOG Log file created by DSZ (ASCII)
USER LOG Log file of all user information (Binary)
OPTIMIZE LOG Log file of last date system auto-optimized (ASCII)
SCREEN LOG Log file of screen ON/OFF status (ASCII)
SPEAKER LOG Log file of speaker ON/OFF status (ASCII)
NODE LOG Log of all system activity (Binary but ASCII readable)
CALL LOG Total # of calls received (ASCII)
FASTART DOC BBSX FaStart instructions (ASCII)
FILES LST DOS DIR-style file descriptions of files directories (ASCII)
MAIN MSG Message text for the MAIN group (Binary)
???????? MSG Message text files for other groups (Binary)
MENU POL Questionnaire menu (ASCII)
1 POL Sample questionnaire # 1 (ASCII)
2 POL Sample questionnaire # 2 (ASCII)
3 POL Sample questionnaire # 3 (ASCII)
4 POL Sample questionnaire # 4 (ASCII)
5 POL Sample questionnaire # 5 (ASCII)
MAIN PTR Message pointers for the MAIN group (Binary)
???????? PTR Message pointers for other groups (Binary)
???????? RSP Responses to questionnaires (ASCII)
=====================================
WHY BBSX REQUIRES DTR TO BE FORCED ON
=====================================
Due to a "feature" of the Microsoft BASIC compiler (v.6.0), DTR is
DROPPED, and the caller HUNG UP, whenever BASIC attempts to launch a child
process, such as BBSX's external file transfer protocol drivers. To prevent
this from happening, you MUST set your modem to FORCE DTR ON.
Microsoft is aware of this problem, but sometimes they do not act on
bug/feature reports until quite a few people have screamed at them. If
forcing DTR on bothers you (as it does us), let Microsoft know about it! Tell
them that you want BC6 updated so that the status of DTR is NOT changed during
a SHELL to DOS.
Write to:
Thomas L. Button
Program Manager
Languages Group
Microsoft Corporation
16011 NE 36th Way
Box 97017
Redmond, WA 98073-9717
Tell Tom that Rich Levin, Chief Lunatic at BBSoft, and Director of the
Philadelphia Area Computer Society BASIG, referred you.
============================
ERROR CODES AND EXPLANATIONS
============================
* Endless loop error
See the explanation on LOOP ERROR, below.
* Out of memory
* Out of string space
BBSX needs more RAM than is available.
Try unloading some, or all, TSR's, or buy a RAM card to increase the
amount of on-board RAM in your system.
BBSX requires a minimum of 384k free RAM.
* Device fault
* Device timeout
* Device unavailable
* Disk media error
* Disk not ready
These errors indicate a hardware configuration problem (such as an
open disk drive door, bad, non-existant, or incorrectly specified device) or a
hardware failure.
Check all cables, connections, and related hardware. If the problem
persists, call BBSoft Support for assistance.
* Out of paper
Your printer is out of paper, or the paper is jammed.
* BBSX.INI file not found
BBSX cannot find the BBSX.INI file in the current directory.
Make sure that the BBSX.INI file is stored in the directory specified
in the BBS.BAT file.
* Device I/O error
An unrecoverable I/O error occurred.
This is a non-fatal error. 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) operations.
If your modem is not 100% Hayes compatible, the converted escape code
sent by BBSX may not be processed correctly. This would cause your modem to
fail to hang-up the line after a completed session. Callers will hang-up
manually, which could cause a device I/O error.
* Disk full
Your disk is full.
* Communication-buffer overflow
The communications receive buffer (1024 bytes) overflowed.
Usually caused by an on-line user leaning on the keyboard.
* Permission denied
An attempt was made to write to a write-protected disk, or to access a
locked file in a multi-user environment.
* Path/File access error
* Path not found
BBSX was unable to access a path specified in either the BBSX.INI or
FILES.INI file.
Review the BBSX.INI and/or FILES.INI files and confirm that all of the
specified paths exist on your hard disk, and that the path names are
syntactically correct.
* Too many files
BBSX was unable to open multiple files.
Try adding the following statement to your CONFIG.SYS file:
FILES = 25
* Bad FILES_PATH in BBSX.INI or FILES.INI
BBSX encountered a FILES_PATH field in either the BBSX.INI or
FILES.INI file where the path specified contains illegal characters or does
not exist.
Double check all of your FILES_PATH statements and make sure that the
DOS path names are considered legal by DOS, and that the paths specified
actually exist on your hard disk.
* Bad or outdated *.HDR file
BBSX encountered a corrupted or outdated .HDR file.
Delete the file and it's sister .MSG and .PTR files. If your BBSX
system uses DAILY.BAT, you will find backups of the files stored in the BAK
<DIR>. Restore the files from the backups.
* Bad or outdated USER.LOG file
BBSX encountered a corrupted or outdated USER.LOG file.
Delete both the USER.LOG and the INDEX.LOG files. If your BBSX system
uses DAILY.BAT, you will find backups of both files stored in the BAK <DIR>.
Restore the files from the backups.
* Too many response lines allocated in [ filename.POL ]
The number of responses allocated in the specified .POL file exceeds
999. BBSX allows a maximum of 999 response lines per .POL file.
Reduce the number of allocated responses.
* Out of environment space
There is not enough DOS environment space available.
Delete the "SET DSZLOG=" statement from FTX.BAT, or increase the
environment space with the "SHELL" command. See your DOS manual for more
information on the SHELL command.
* Loop error
See the explanation of ENDLESS LOOP ERROR, above.
============
FATAL ERRORS
============
The following error messages should NOT occur. If they do, they may
indicate an internal programming problem within your version of BBSX. Contact
BBSoft if you encounter any of these error messages 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
Unassigned error
Total global thermonuclear war error
*-----------------------------------------------------------------------------*
Rich Levin's BBSoft Co. Since 1982 SharewarEverywhere
*-----------------------------------------------------------------------------*
- End of BBSX.DOC -