S L I C K B U L L E T I N B O A R D
by Simple Software Company
P.O.B. 8184
N. O., La., 70182
(504) 288-6550
03/10/1990 SBBS V.4.5 New Release, More Features
ACKNOWLEDGEMENTS:
Terry Tekippe, Ph.D., Notre Dame Seminary, my assembler instructor,
Svengali, and overall guiding light.
VARIOUS UN-NAMED SYSOPS whose support, suggestions, ideas and
contributions cumulatively helped mold the
final product.
The Guys at SemWare for creating a programmer's editor that
home of "Q"edit almost writes the code for you.
REGISTRATION POLICY:
The only files not provided (until registration) are the source code files
themselves. SBBS is available without the source code for half price. The
fully registered version, with source code, is $59.00. Without source code
it's 29.00. If registered without source code we will provide you with the
latest version, customized with your BBS's name. With the source code
registration you will be licensed to alter at will with NO restrictions
relative to your private non-commercial use. In either case, you will
have full telephone support (your toll expense), and any further upgrades
when they are available for never more than 25% of the current Retail
prices. Bug fixes will always be NO CHARGE.
If you wish to see this BBS in action, CALL 504-283-9785. Unfortunately
the phone lines are extremly noisy and of poor quality, so although SBBS
supports 2400 baud, you will likely do better with 1200. In any case,
our Support BBS, Host Line, running V 4.4 of SBBS, is on 24 hours a day
seven days a week at 300/1200/2400 8N1.
FORWORD:
My intention in writing a bulletin board was not to re-invent the wheel, but
rather to provide a flexible product that provides the following advantages.
#1. A basic BBS kernel that on its own provides most of the services that
are popular with most users of on-line systems. #2. A high level language
that is MORE likely to be understood by most computer aficianados.
#3. Providing *** ALL *** source code with NO hold backs, which is fully
commented so even the novice purchaser can understand what's going on.
#4. Using a language that will allow the user to purchase a compiler for
under $50. #5. Provide the basis for a new or experienced Sysop to once
and for all have total control over over his operation with the ability
to customize or change at will.
Because it is next to impossible to actually re-invent the wheel, you
will no doubt find a great deal of similiarity to the operational style
of SBBS in comparison to many other good BBS products. And you should,
because I took the best features of them all in designing the style,
feel and elegance of SBBS.
Turbo Basic was picked for this unique and rather ambitious
project. Sure, Turbo Basic is no longer under continuing development
by Borland and Quick Basic by Micro Soft still is, but Turbo Basic as
it stands does everything that needs to be done as you will soon see.
There are a number of operations that are unquestionably best done in
machine specific code. These portions therefore are included in TB $INLINE
and CALL INTERRUPT format. There ARE NO mysterious OBJ files that are
required to be linked, but come with NO SOURCE code. You will have everything
you need to COMPLETELY rewrite the entire BBS if you desire to.
FEATURES:
SBBS supports only COM1 and COM2 from 300 to 2400 baud at 8N1. Although
restrictive in some cases, I have found this to take care of 95% of most
users' hardware needs. The Shareware Version comes hard-coded for COM1 at
2400 baud. Registered versions without source code will be shipped to
your specifications within the above limits. Those requesting source code
registration will of course be able to alter ANY parameters at will.
See the end of this document for some modem hints and suggestions.
SBBS allows any number of message conferences, security levels, bulletins,
and users. Both private and public messages are supported. SBBS provides
for both a master and/or master and assistant sysop. Uploading and Downloading
of Files is supported by using the famous DSZ protocol engine provided by
OMEN Tech. also available from the BBS where you obtained SBBS. This engine
provides for the three most common file transfer protocols. Xmodem (in
all its variant forms), Ymodem Batch and the highly recommended Zmodem
with its fancy error checking, crash recovery, and packet resizing ability.
Various Door Utilities can be supported such as ZIP viewers and text file
readers. The code as written supports just one door but can easily be modified
to accomodate as many as you want. Doors are Batch operated and care should
be taken to insure that any utility you desire to run monitors the Modem
MSR byte for carrier detect at bit position 7. Most well-designed Doors do it.
The Sysop Menu allows the Master Sysop to Drop to DOS from a remote
terminal. SBBS incorporates its own Hot Boot code in such a way that if the
system is idle at 2 minutes 45 seconds past MidNight it will initiate a
System re-boot to reset your DOS time from your internal battery clock. If
someone happens to be on line at that time, the re-boot is delayed until
after they logoff. SBBS will also reset immediately if for any reason
carrier is lost during a logon. SBBS also monitors idle time at the remote
keyboard. If no activity is detected within 3 minutes, again SBBS will
Logoff and reset. A warning is displayed after 2 minutes. Any keystroke
automatically resets the counter.
This archive should contain the following files, and/or they will be
created by the configure engine, SLICKCFG.EXE. Those marked with a
star (*) are generated by the SLICKCFG. Files marked by a pound
symbol (#) are created and/or updated by the runtime file, SLICKBBS.EXE.
SLICKBBS EXE The Main BBS Program complied with Turbo Basic Ver 1.1
SLICKBUL DAT# The bulletin database reference. Ascii Sequential File
SLICKCFG DAT* MAIN BBS configuration file created by SLICKCFG.EXE*
SLICKCON DAT* The conference database. Ascii Sequential File
SLICKLOG DAT* Record of daily logons, updated by BBS, deleted nightly.
SLICKMSG DAT* Message database containing text of mail
SLICKMSG HDR* Message pointer database. Random access file
SLICKUSR HDR* User Database. Random access file
SLICKUSR REF# User Name/Number Ascii file (pointer to SLICKUSR.HDR)
SLICKMOD CFG* New Modem Configure file (simple ascii)
NEWUSER LOG# Ascii text record of all new logons.
ACTIVITY LOG# Accii text record of all activity of BBS
SIGNON TXT Text File you may customize with your own Logon Message
WELCOME TXT@ Text File can be anything you want, Notices, Alerts, etc.
NEWUSER TXT@ Text File displayed to New Users ONLY. You customize
TODAY TXT Text File displayed (if found) to every logon
BBSLIST TXT@ Text File of whatever BBS's you wish to promote (called/Main)
SYSINFO TXT@ Text File describing your BBS operation called from Main Menu
MENU TXT@ Text File of Main Menu
FILEMENU TXT@ Text File of File Menu
FILESDIR TXT Text File of files available for DownLoad on your system.
JOKES TXT Text File collection of witty sayings to be shone randomly
SIGNOFF TXT@ Text File of your logoff message (again, anything you want)
SYSMENU TXT@ Text File of Sysop Menu
(samples of all Text Displays are Included)
The files with the @ to the right all have their ANSI COLOR Graphic counter-
parts located in a separate archive called ANSI.ZIP. They must be located
in a separate directory by themselves, pointed to via the SLICKCFG.DAT file.
If a logon selects Color, SBBS will then automatically point to the correct
directory and the ANSI Color files will be displayed. NOTE: We highly
recommend an ANSI Editor called TheDraw (available on almost all good BBS's)
to edit these files. The samples included were created on TheDraw.
PLEASE NOTE: The ANSI display files HAVE THE SAME FILE NAMES as their plain
Ascii counterparts. DO NOT unzip the archive ANSI.ZIP in the same directory
as the mono versions as there is a chance you may overwrite them even though
pkunzip will warn you ! Its best to move this file to the directory where
it will reside and upzip it there !
GETTING STARTED:
It is highly recommended that you load SBBS via your autoexec.bat file.
In this way, when SBBS does a warm boot at midnight your board will
automatically return on line.
You will need to do a little planning ahead and prepare to answer the
following questions. How many users do you expect to support? (this can
always change later). How much time are you going to allow your users to
logon on a per logon basis? What will be the size of your message support
system? What will be the security level of new logons? How many conferences
and at what security levels do you wish to operate?
Before anything else is said, a very important element is the FIRST Logon.
This MUST be YOU if your intentions are to be the SYStem OPerator (Sysop).
The FIRST Logon (either locally at the console or via a remote) is, by
default, given the highest access (level 6000/Master Sysop). Everyone from
then on is assigned the level put into the configuration file (SLICKCFG.DAT).
Then it is up to either the assistant sysops (if the Master creates any at
level 5000) or the Master himself to upgrade ANY user higher than the Logon
default of 1000. It might also be noted that the user reference file called
SLICKUSR.REF is created automatically on first logon and updated from then
on as new users logon. ALL files created by SLICKCFG.EXE must also be
in the runtime (SD) slick directory, otherwise SBBS will fail to load and
run.
Let's begin by understanding a few numbers based on experience. I suggest
you begin with a database for 200 users and 200 messages (again, this
can always change). Most video boards support 25 lines of screen text and
most users generally leave messages under 100 words. So, my suggestion is
to set the number of message lines to 20. Since each line is 80 characters
long this will produce a file of 320K (80X20X200) that will nicely backup
on a standard floppy if you wish to save it (and if you run a BBS, you
should backup everything). One of the big problems with any BBS is the
pile up of old traffic (messages) in the database. To help with this
problem, SBBS automatically marks any personal traffic that has been
read by the receiver for deletion. Then, depending on need, it's only
necessary to enter the Sysop menu and hit "D" to remove them. A detailed expla-
nation of ALL Main menu and Sysop menu keys will follow. But, REMEMBER, with
the source code you have total control of any of this. Also, a 20-line
message eliminates the need to have an elaborate scrolling method (which
few BBS have anyway) as the sender can always view his entire message on
just one screen length. I have incorporated some miminimal editing capability
into the code so corrections can be made before saving. You can go ape
with security levels but I suggest a simple system. 1000 for new logons,
2000 for regular users, 3000/4000 for SIGS, 5000 for assistant sysops,
and 6000 for you the master Sysop. Unless you register for the source
code, you won't have any control over these defaults anyway; but the numbers
work out nicely. By default, 2000 is required for File access through
the Main Menu. A simple registration policy is best without any begging
or threats of banishment if users dont upload. SBBS asks by default for
the user's real name and phone number. It's my personal policy to verify
the phone number and then give them regular access. Thirty percent will
leave you a thank you note, the rest expect access as if it were a
right but you will soon learn that Sysoping is a one-way giving experience
only. SBBS will generate a NEWUSER.LOG and record all new users and
their phone numbers to make upgrading relatively easy. The Sysop has
easy access to this file via his Menu.
Again, obeying the KISS formula, I suggest keeping the number
of Conference Areas to just a few. Five or six seems to work well,
with Titles like Public Forum (1000) (NOTE: Private Mail is covered by
default as Conference zero (0), and mail addressed to Sysop is
defaulted to the name of the first logon (the Sysop). Then something
like: Swap Shop (1000), Buy & Sell (1000) all accessible to New Logons
on first call. Then perhaps a regular user conference like Local
Happenings: (2000), and or Hints & Tips: (2000). If you wish, you can
support SIG's (special interest groups) like Programmer's Corner:
(3000) and/or non-computer interest like Citizens Against Drugs:
(3000) etc.
When you run SLICKCFG.EXE, a number of questions will be asked. First,
What com port are you using, COM1: or COM2:, (enter it that way). What
is the max baud of your modem, 300, 1200, or 2400. What pariety, What
Databits, What stopbit, What modem init string to use? After these
questions are correctly answered it will then proceed to the next questions.
How many conferences do you wish to support? Remember, you can always
add on more, so start small. Second question, how many lines per question?
20 is suggested. How many messages? I suggest 200 to start. In what directory
will your downloads (those received from your users) be stored ? I suggest
setting up a directory off the root called C:\BBS, then create C:\BBS\DOWN for
this location. Next question wants the same information for the directory
in which you intend to store files you are making available to your users. This
can be C:\BBS\UPLOAD. Next, where will the main files be located? Of
course this will be C:\BBS. (NOTE: The mono text graphic files will
reside here as well, i.e. Menus,Bulletin and display files.) Then, where
will you keep the COLOR ANSI files? I suggest using C:\BBS\ANSI. Also
you will need a directory called C:\BBS\TEMP if you use the utility
AVIEWCOM. The identical display Ansi files should be placed here. The
next question is, what security level will be assigned new users? I
suggest using 1000. How many users? I suggest 200 to start. Finally, and
this like everything else is a judgment call, how many minutes will
you allow each logon ? I suggest between 60 and 120 minutes. REMEMBER,
any of these items can be altered later on. A sample of the file created
by this utility is included down below along with all other data files
used by SBBS.
This Utility will also generate several other files SBBS looks for at
runtime. One is SLICKLOG.DAT and the other is SLICKBUL.DAT. The first
must be found at runtime. The second can be dynamically created via the
Sysops utilities later on; but, to illustrate a good idea, one is made
for you which incorporates a master bulletin of all other bulletins
as bulletin #1. The Title "Master Bulletin" and file name MAST.BUL with
a security level of 1000 is suggested. The first "sample menu" below is
that of MAST.BULL containing a descriptive list of 20 other bulletins.
LOGON:
Once you have created all the necessary directories, placed the proper
files therein, and customized whatever display files you need, the first
test will be to boot SLICKBBS.EXE. For now, just move to SBBS's parent
directory and type the name at the C> prompt. If all necessary files are
in place, SBBS will come into action with a message appearing in the upper
left corner of the screen. SBBS will say it is Waiting for a Call.....
You will also note the two keys necessary to either LogOn Locally at the
console or terminate the program. The Esc key will allow a local log and
the "+" key will terminate the program. NOTE: A local logon, for simple
security reasons, will not automatically give Sysop access. In fact, to
assist in learning what the user sees, a Local logon will run you through
the same exact sequence of events as if it were a remote logon. REMEMBER,
the FIRST LOGON controls WHO will be MASTER SYSOP. If SBBS fails to reach
the runtime mode, more than likely the reason is due to its inability to
locate one or more of its necessary support files. An error code of 52,53
or 63 or 64 will indicate this. Since there are only a handful of support
files, I saw no reason to include code (it takes up more space and runtime)
that would point to the specific missing file, although this could easily
be added if you wanted it.
Once you have succeded in doing the first logon, you may wish to leave the
first piece of mail to ALL, welcoming everyone to enjoy your new BBS. You
can also run through all the Main Menu options, testing every feature to
insure all other display files are working, etc. Unfortunately, when a
User selects color, the local console will not react to the ANSI escape
codes to trigger the video card into color. The Remote user will, however,
receive correctly. Again, to keep speed to a max, I avoided the DOS
function Int 21, direct write to console function. As an observer, you
have little use for seeing ANSI color anyway when a remote logon occurs.
Again, if anyone wants this feature, and doesn't mind the slowdown, I
will be happy to show them how to do it.
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ͵ Host Line Bulletin Menu ÆÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º º
º # 1 - This Menu of ALL Bulletins # 12 - Universal BBS Rules º
º # 2 - How to USE SBBS facilities # 13 - Mensa Mind Benders º
º # 3 - Location of Area SIG Meetings # 14 - Learn to Fly º
º # 4 - Advertisement from SSC # 15 - List of N.O. BBS's º
º # 5 - News on Slick Terminal # 16 - How to setup for ANSI Colorº
º # 6 - Area GrapeVine (Gossip) # 17 - Defeat Call Waiting º
º # 7 - ZIP info ! # 18 - SBBS Protocols º
º # 8 - Bargain Shoppers Memo # 19 - From the Mind of a SYSOP º
º # 9 - Sysop's File Reviews # 20 - Reserved º
º # 10 - SSC Shareware Products NOTE: Some Bulletins require access º
º # 11 - New Users Read this FIRST over 1000; ie REG,SIG,RSWU etc. º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
Mono Ansi
²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²
²² ²²
²² ** M A I N M E N U ** ²²
²² ²²
²² X = Expert Menu Mode B = Bulletin Section ²²
²² ? = ReDisplay Menu F = Files Menu (Reg Only) ²²
²² E = Enter Message U = User List of SBBS ²²
²² R = Read Messages W = Welcome message ²²
²² D = Delete Message I = Information on SBBS ²²
²² Y = User Status M = Message Statistics ²²
²² P = Page the Sysop A = Alter Password/Phone ²²
²² N = New Messages G = Goodbye, LogOff ²²
²² L = Show Today's Log S = Scan Message Titles ²²
²² O = Other AREA BBS's C = Toggle ANSI Color ²²
²² + = Sysop's Utilities * = Reserved ²²
²² ²²
²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²
Most of these selections are rather obvious but some not so. The
Menu comes in two forms, the full file menu (as shone above, which
can be edited easily with any text editor) and the abbreviated
menu which always appears after each regular text menu. Even the
abbreviated menu can be changed via the source code. The (X)pert
mode simply disables the text menu display and saves a few seconds
of toll time for the experienced user. Even in the (X)pert mode,
a simple question mark (?) will redisplay the correct menu. The
user has two options for reading his new mail, at logon or later
from the main menu via the (N)ew key. The (L)og key shows all
users who have been on since midnight. The (O)ther key displays
a simple ASCII text file you can create and modify at will to
promote your buddies BBS's as well. The (+) key allows access
to the Sysop Menu (providing the user has a level of 5000 or
greater). The code is written to make a record of any non-
authorized uses of that key in the activity log. I am not sure
what it suggests when a non-authorized user attempts to gain
access to the Sysops utilities, but it's fun to notice who does
and who doesn't. The (F)iles selection is only functional to
users with level 2000 or above. The Sysop must approve and set
this additional level of access from his utilities. The (U)ser
list will display ALL or some or one user that you may be
interested in. The (W)elcome key simply repeats a few of the
messages from original Logon. The (I)nfo key again displays a
basic text file you can create to explain all about the purpose
and goals of your BBS. The (M)essage Stats key gives just that,
information on the messages presently in the message base.
The (A)lter key allows users to change their passwords or
phone numbers. The (S)can key gives a quick run down of the
flavor of messages in the system. The (C)olor key simply toggles
the directories that hold either the Mono or ANSI Color Text &
Menu Files. The (G)oodby key is for signing off.
Mono Version
ÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜ
Û Û
Û *** S Y S O P' S M E N U *** Û
Û Û
Û R = Return to BBS A = Re-Alphabetize User List Û
Û D = Remove Deleted Messages K = Kill a Bulletin Û
Û L = Delete Daily Log C = Edit Conferences Û
Û M = Edit Message Header O = Slash OLD users Û
Û ? = This Menu E = Edit Bulletin Headers Û
Û U = Edit User F = Toggle Linefeeds Û
Û B = Add a New Bulletin T = Trash Old Messages Û
Û $ = Edit File Dir: S = Shell to DOS Û
Û X = Toggle Auto Timer V = View DIR (Lcl Cons only) Û
Û N = New User Log Z = Zap New User Log Û
Û * = Read Activity Log # = Kill Activity Log Û
Û Û
Û * <F1 = Sysop at Console> * <F2 = Chat with User > Û
Û * <F3 = Toggle Linefeeds> * <F7 = End Chat > Û
Û * <F9 = Shut BBS Down: > * <F10= Log Off Violator> Û
Û * <F4 = Forced Chat > [* From Local Console Only ] Û
ÛÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÛ
The (R)eturn key brings you back to the Main menu. The (D)elete key
removes any messages marked for deletion by virtue of either having
been read by the receiver or deleted by the originator. The (L)og
key allows you to dump the Daily Logon record and reset it manually.
This is done automatically every night after midnight. The (M)essage
edit key allows editing of the content of the SLICKMSG.HDR file.
The (U)ser edit key is the most active as it is from here you will
upgrade your users from the default logon level of 1000 to that of
regular user level 2000. The (B)ulletin key allows you to add new
bulletins to your available list. All bulletin files should be
standard Ascii text files with the suggested extension of .BUL
The (E)dit bulletin key is also usful for altering some items.
You may also set the required security level for each bulletin as
well as enter a Title. The dollar sign key ($) allows line editing
of the FILESDIR.TXT so you may change as required with new additions
or deletions. The (X) key disables the auto timer annunciator.
The (N)ew key displays any new users since last reset, and the
(Z)ap key kills and restarts the log again. The (A)lpha key is a
seldom used bubble-sort utility for re-alphabetizing the user ref
file, SLICKUSR.REF, in case it ever gets disorganized. The (K)ill
key allows you to remove old bulletins. The (C)onference key is
for editing the SLICKCON.DAT conference data file. The (O)ld
user key is for setting a cutoff point for users that have not
logged on within so many days, months, etc., and for removing them.
The (F)orce linefeeds toggles the LF on or off. Most systems
require each line to be terminated with a Carriage Return followed
by a Line Feed (CHR$(13) & CHR$(10)) and this is the default. But,
if you need to eliminate the LF, this toggle will do it.
The (T)rash old messages key is useful for marking ALL messages for
deletion ON or BEFORE a certain date. Messages tend to build up
quickly and few are ever worth keeping for reference. The (S)hell
key allows the Master Sysop (only) to access DOS directly from a
remote. The (V)iew key allows the Master Sysop to basically get
a directory display of the default when in local mode. The "*"
key will dump the activity log to screen and the "#" key will
delete it from disk.
When at the local console, the F2 and F7 are used to start and
end Chat mode with a user. F10 can be used to start an immediate
LogOff of an undesirable user. (The kind who like to attempt
crashes of your system). F4 now provides a "Bust in" forced Chat
in case the logon is in the middle of code the F2 key cant penetrate.
Mono Version
²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²
²² ²²
²² L = List Files Directory ²²
²² D = DownLoad File(s) ²²
²² U = UpLoad File ²²
²² R = Read a .TXT File (ascii) ²²
²² Q = Quit to Main Menu ²²
²² V = View ZIP content (if avail) ²²
²² G = Good-Bye/LogOff ²²
²² ? = Re-Show this Menu ²²
²² ²²
²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²
The (L)ist key displays the FILESDIR.TXT file which is where you
will be keeping a record of your available files. I guess if there
is any section that has a lot of room for expansion it is here.
Services here are admittedly bare bones. There is no elaborate
file database for catogorizing files. Everything is in one basic
directory seen via the filesdir.txt. The novelty here is that
you can use any utility like PCTOOLS to re-sort your directory
(by date, decending....recommended) then do a "DIR > FILESDIR.TXT"
command at DOS to create your updated file. It's that simple for
now. Users are getting more sophisticated every day and the good
ones will usually download your list first to get a record of
your goodies, then simply download when they need to.
The (D)ownload feature supports batch Zmodem and allows the user
to grab up to nine files at one time. Also, Xmodem/Ymodem and
Ymodem/Batch are also available. The (U)pload feature allows
only SINGLE file transmission to facilitate giving a text
description of each contribution. SBBS will mark all NEW
Uploads with a (*) to clue the other users its not yet available
for download. This requires the Sysop to move the file
physically from one directory to another and remove the "*".
It's also a good idea for the Sysop to check the files he
receives before making them available to his users.
The (V)iew utility (AVIEWCOM highly suggested) is a very clever
utility for allowing three MAJOR operations. One: The viewing or
reading of any documentation file within an archive. Two: The
viewing of the contents of the archive itself, and Three: The
Downloading of any particular file within an archive. There are
many of these utilities around, but I suggest you register this
one in particular with the author.
A new feature has been added with the release of Version 4.5. Now
you can include ascii text files in your directory that the logon
can read (send to console) without having to download. This is a
feature that seems to be very popular lately, sort of a lazy mans
message and bulletin mode. I think the reason is obvious, all logons
immediately jump to the files department -- always passing up the
regular mail and bulletin sections. Therefor, to help get information
quickly to the users, Sysops are condoning this practice more
often than not.
****************************************************************************
SAMPLE of New Modem Configure File
SLICKMOD.CFG
COM1:
1200
N
8
1
CS2000
DS2000
ATH0M1V0&C1&D2S0=1S2=128
****************************************************************************
DROPDOS BAT Batch File to allow Sysop Drop to DOS.
CTTY COM1: {Three line content of dropdos.bat; note: Command.Com must
COMMAND.COM be in either the path or default directory}
CTTY CON
****************************************************************************
This information valid for version AVIEW34.ZIP Only!
DOOR1 BAT Sample Batch for running a DOOR. In this case, it is called
via the Files menu for manipulating the content of archives.
AVIEWCOM {content-just one line in this case} NOTE: We highly
recommend this shareware utility called AVIEWCOM.COM
for ZIP content viewing, text & doc displaying and
downloading. Since this and a large number of other
door utilities reset various com registers, SBBS
will automatically reset the modem back to the original
references (before door activation) after completion.
Another reason for buying AVIEWCOM is it also uses the
Omen DSZ engine for file transfers.
*AVIEWCOM CNF configuration file {comes with their package}
AVIEWCOM EXE utility itself ""
AVIEWCOM LOG dynamically created by runtime program.
*Sample content of AVIEWCOM.CNF for proper operation with SBBS
===============================
#SEARCH
#PATHS
C:\BBS ;main directory of SBBS and location of AVIEWCOM
#PORT
COM1 ;port, assummed to be COM1
;#VIDEO
;ANSI
#TEMPORARY
C:\BBS\TEMP ;temp directory for pkunzip to do its thing
#EXTRACTOR
PKUNZIP ;archive engine
===============================
This information valid for version AVIEW37.ZIP Only!
CONTENT of AVIEWCOM.CFN
#search
#paths
c:\modem\upload
CONTENT OF DOOR1.BAT
AVIEWCOM * COM1 -a2 -c -e4 -l -pC:\MODEM\TEMP -t30
****************************************************************************
Sample Bulletin names and possible content descriptions.
BULLMENU BUL Description of All Bulletins
ANSI BUL How to install ANSI NOBBS BUL List of Local BBS's
ANSIDEMO BUL ANSI Demo File PROTOCOL BUL Explanation of Protocols
BBSRULES BUL Rules of your BBS Etc. Etc.
BEST BUL Shareware Reviews
CALLWAIT BUL Disable Call Wait
GRAPE BUL Area GrapVine Gossip
MINDGAME BUL Word Games
NEWUSER BUL Help stuff for new users
*****************************************************************************
CONTENT of SLICKCFG.DAT, generated by SLICKCFG.EXE (sample)
Content Description Variable
_____________________________________________________________________________
5 Number of Conferences you decided on [NC]
20 Maximum Number of Lines per message [MAXLINE]
200 Maximum Number of Messages desired [MAXMESS]
1000 Sign On Security Level (1000 is suggested) [SEC]
200 Total Number of Users you will configure for [MAXUSER]
120 Total Number of Minutes allowed on per Logon [MAXTIME]
C:\BBS\DOWN DownLoad Directory (recv from user ) [DL$]
C:\BBS\UPLOAD UpLoad Directory (avail to users ) [UL$]
C:\BBS DIR of General Files (Slick Directory) [SD$]
C:\BBS\ANSI DIR of ANSI Files (Slick ANSI Menu) [CD$]
1 Total Messages Handled ( starts with 1 ) [REF]
1 Total Logons todate ( starts with 1 ) [CNUM]
{ $ denotes String variable, numeric type without }
*****************************************************************************
SLICKCON.DAT
Sample Content Array used Description
_________________________________________________________________________
Public Comments: -------> CONF$() Conference Title
1000 ------------------> CONF() Security Required
Hackers'Conference:
2000
Buy/Sell/Swap:
2000
Request Line:
1000
Bay Area SIG:
3000
CONF$(0) always = "Private Mail"
C(NC) conf.pointer
*****************************************************************************
SLICKUSR.HDR 76 byte records, 8 Fields
FIELD Description Variable Field size
____________________________________________________________________________
User Password UP1$,UP$ 10 bytes (characters)
User Name (full) UN1$,UN$ 30 bytes
User Phone Home UPH1$,UPH$ 12 bytes
Mail Reference ULR$ 2 bytes (integer) [total msg on sys]
Last Date of Logon UDL1$,UDL$ 10 bytes
Time of Last Logon UTL1$ 8 bytes
User Security Level USL$ 2 bytes (integer)
Mail Waiting UNW$ 2 bytes (integer)
*****************************************************************************
SLICKMSG.HDR 114 byte records
FIELD Description Variable Size Notes:
__________________________________________________________________________
Message From MF1$ 30 bytes
Message To MT1$ 30 bytes
Message Date MD1$ 10 bytes
Message Time MTI1$ 8 bytes
Message Conference # MC$ 2 bytes private, deleted, read
Message Subject MS1$ 30 bytes
Message REF Number MR$ 2 bytes
Message Security Level MSEC$ 2 bytes
*****************************************************************************
SLICKMSG.DAT 80 byte records
__________________________________________________________________________
Data of message D$ 80 bytes
*****************************************************************************
SLICKLOG.DAT
Sample Content Variable Description
WAITING FIRSTCALL ----->A1$ --------->Users Full Name
00:02:45 ----->A2$ --------->Logon Time
00:02:45 ----->A3$ --------->LogOff Time
GARY RAYMOND
15:30:17
15:31:36
JOHN DOE
15:31:43
15:35:30
*****************************************************************************
SLICKBUL.DAT
__________________________________________________________________________
MENU of All BULLETINS
BULLMENU.BUL
11-07-89
1000
HOW to USE SBBS
USESBBS.BUL
11-07-89
1000
BAY AREA SIG MEETINGS
SIG.BUL
10-18-1989
1000
*****************************************************************************
JOKES.TXT Ascii Text File containing about 150 witty quotes you
add or delete from at will.
BO$(BO) Array variable used by SBBS to Load Jokes.
*****************************************************************************
YOUR MODEM:
More than 90% of the calls we receive requesting help turn out to be Modem
configuration problems. SBBS sends the following string to your modem at
runtime. "ATH0M1V0&C1&D2S0=1S2=128" The explanation is as follows, and as
most modern modems respond to these commands, you should have no problems.
But, if you happen to have an oddball piece of hardware, this explanation
might help solve your setup problems.
AT Hayes modem ATTENTION command....more is comming
HO Put the line ON-HooK and prepare to receive calls
M1 Leave the speaker ON until Data begins to move
* V0 Give NUMERIC result codes instead of Verbal (verrry important)
* &C1 Make Carrier Detect go high in presence of Carrier (verrry impt too)
* $D2 Make Modem assume Command state when DTR goes low (verry impt too)
* S0=1 Answer on FIRST ring
S2=128 Set ESCAPE CODE character out of reach by disabling
NOTE: The items with the star must be set one way or another to insure
proper BBS operation. If your modem cannot be set either by dip
switches or by AT commands to these values, the sucessful outcome
of your BBS is in serious doubt.
If your modem does not support numeric results codes, the source
code of SBBS could be easily modified to accept verbal responses.
It's just not as accurate.
DISCLAIMER
THIS PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. THE AUTHOR WILL NOT BE LIABLE TO USERS
OF THIS PROGRAM FOR ANY DAMAGES, INCLUDING LOST PROFITS OR
LOST SAVINGS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES,
ARISING OUT OF USE OF THIS PROGRAM.
HISTORY
12/20/1989 SBBS V.4.2 Maintenance Release
A number of reports about eratic operation on older PC XT's running
at 4.77 were isolated to timing problems in the serial port coding.
Also a bug was reported in the message section (that has also been
swatted) that caused a lockup ocasionally when replying to private
mail.
01/10/1990 SBBS V.4.4 Maintenance Release
Several cosmetic changes in the various mini menus. Corrected several
prompts working only on uppercase responses.
03/10/1990 SBBS V.4.5 New Release New Features
Many new features (all covered in the text above) have been added
to the system. Several cosmetic changes to the Bulletin Department,
the addition of a new optional text file (TODAY.TXT) sent (if present)
to the logon, a new Read Text utility in the Files Department for
viewing text files on screen from the file directory. BUT, the most
important new feature, based on the spirit of shareware, is a MODEM
configuration file to enable any baud rate, com1 or com2 port,
pariety, databits, stopbits and modem init. string. Many potential
users either had the wrong baud modem or unavailable comm port or
both. This will give those budding sysops the ability to evaluate
the BBS on their own computer.
THE END