Category : BBS Programs+Doors
Archive   : TB120.ZIP

Output of file : TURBOARD.DOC contained in archive : TB120.ZIP





For Version 1.0

from Software @ Work

TurBoard Version 1.0 Sysop's Reference Manual

(c) Copyright Shawn Rhoads 1991,93, All Rights Reserved

(c) Copyright Software @ Work 1991,93, All Rights Reserved

June 28, 1993

This document written by Shawn Rhoads

TurBoard is an NAPLPS, RIPscrip, ANSI and ASCII asynchronous
telecommunications program designed to provide server E-Mail,
data and information exchange for a group of users. The system
can be used in a public or private environment and over a LAN or
Modem connection.

If you wish more information about TurBoard and how to register
your copy for $75, contact:

Software @ Work

P.O. Box 566491

Atlanta, GA 31156

404/395-6525 (voice)

404/395-6326 (2400bps)

404/395-6327 (HST & V.32bis)

This document has been written to enlighten TurBoard Sysops of
the commands they can use to configure their system. If you
have any suggestions or comments on how to improve this
document, please forward your mail to the above address or you
can leave a message on the support bulletin board in the
TURBOARD support forum. Software @ Work thanks you for being
part of the best telecommunications package, TurBoard!

[1.1] Legal

You should read and understand this section before running
TurBoard. The name TurBoard refers to all the documents and
executables distributed in the TurBoard distribution archive by
Software @ Work.

End User License



You may use the software and any related documentation an a
single computer. You may maintain a single copy for backup
purposes or operation from a hard disk. You may not sell, rent
sublicense, assign or otherwise transfer this license. SOFTWARE
@ WORK retains title to and ownership of the software and to all
constituent parts at all times. If any part of this agreement
is held invalid or unenforceable, the other parts will remain
valid. You agree that the software(s) licensed herein
constitute trade secrets of Software @ Work which are covered by


This license is effective until terminated. This license will
terminate if you fail to comply with any term or condition of
this agreement. Upon termination, you agree to destroy the
software together with all copies in any form in your possession.


(Software @ Work, P.O. Box 566491, Atlanta, GA 31156 USA)



Shawn Rhoads and Software @ Work do not assume any liability for
the use or misuse of this software beyond the original price
paid by the party at stake. In no event will Shawn Rhoads or
Software @ Work be liable to you for any lost profits, lost
savings, lost programming, or other incidental or consequential
damages arising from the use of, or inability to use, this
software and it's accompanying documentation, even if Shawn
Rhoads or Software @ Work have been advised of the possibility
of such damages.

[1.2] Table Of Contents

[1.1] Legal 2

End User License 2




[1.2] Table Of Contents 3

[1.3] Requirements 7

[1.4] Registered vs. Shareware Version 8


[2.0] Installation Instructions 9



[3.0] Command Line Parameters 11

# - Node number 11

-l - Local Switch 11

-fd - Front Door Active 11

-p##### - Incoming port rate 11

-b##### - Incoming call baud rate 11

-cbios - Use BIOS for NAPLPS color graphics writes. 12

-t### - Max. Time allowed 12

-cga -ega -vga - Force CGA, EGA or VGA Graphics Mode 12

-svga# - Force TurBoard into a SVGA mode. 12

[4.0] Modem Configuration 13



[5.0] NAPLPS Graphics/RIPscrip/ANSI/ASCII 15

[6.0] Sysop Keyboard Commands 16

[7.0] User Command Overview 18

[8.0] Detailed System Configuration 20

[8.1] PC Chattanooga! Customization Menu 20




[12.0] FidoNet Support 25



[12.3] TBFIDO.EXE 26


[12.5] ECHOMAIL 26





[15.0] Mail System 32





[16.0] File System 35






[17.0] Classified Advertising System 39



[18.0] BBS List System 41

[18.1] BBS LIST MENU 41



[19.0] Door System 44



[20.0] CB Chat System 46

[20.1] CB CHAT MENU 46



[21.0] QWK Off-line Reader Support 48




[21.4] QWK SETUP MENU 49

[22.0] CD ROM Support 51




[24.0] On-Line Books System 53


[25.0] Bulletins System 55


[26.0] Questionnaire System 57






[29.0] Art Gallery System 62


[29.2] EDIT ART MENU 62


[30.0] YAK System 64

[30.1] Yak Entry Settings 64





[31.0] Customizing Your Displayed Screens 69


[32.0] DAILY.BAT (The Daily Batch Event) 71

[33.0] File Naming Conventions 72


[34.0] Color Codes 73




[35.0] YAK Codes 75

[36.0] Full Screen Editor 76

[37.0] Line Editor 76

[38.0] On-line Help System 76

[39.0] TurBoard Terminal Emulation 76

[40.0] Language File 77

[41.0] Registered TurBoard BBS's 78

[42.0] TurBoard Support Sites 78


[1.3] Requirements

With the right hardware, you might have as many as ten users on
one machine. To accomplish this, you will need a multi-port
adapter and multitasking software.

A multi-port adapter can be either intelligent or
non-intelligent. TurBoard is compatible with DigiBoard
intelligent and non-intelligent cards. Other multi-port cards
may or may not work with TurBoard, for specific information,
contact Software @ Work or your local TurBoard dealer.

To run multiple nodes on a single machine, TurBoard requires
that you run multiple sessions of DOS using a multitasker
program such as Microsoft Windows, DesqView, DesqView/X, OS/2 or
Windows NT. TurBoard is aware of all of these platforms which
means that TurBoard will run well under one of these operating

TurBoard requires that you have a PC-DOS session with at least
340 kilobytes of RAM. A serial port, modem and LAN hardware are
optional. While the serial port and modem are not required to
run this program in local mode, you must have them to run a
bulletin board system!

It is suggested that you use a asynchronous communications
FOSSIL and have DSZ loaded into your PATH. Other than this, no
other software is required.

If you intend to run a message intensive system, a 2400 baud
modem and about 5 MB of free hard disk space is all that is
required to run a small to modest message based system. If you
want to add doors, download files, FidoNet echo forums and other
features generally associated with bulletin board systems, it is
suggested that you have a 20 MB hard disk minimum. There is no
upper limit.

For local NAPLPS displays, TurBoard requires that you have a EGA
or a VGA installed in your computer. CGA mode can be used with
a device driver from the support bulletin board system, but it
is not recommended, and the poor resolution make it almost
unusable. This, however, will not hinder your callers from
using NAPLPS, you will mearly see the NAPLPS codes locally in
text mode rather than seeing the NAPLPS images.

To run a FidoNet system, a front end processor such as
BinkleyTERM or Front Door(tm) is required. Depending on the
software used, a nodelist compiler may or may not be required.
Please see the operation manuals on these packages for more
information on their requirements.

If you are planning on running a system with over 10 nodes, you
will need to network several computers together. It is a good
idea to use a file server in such instances as it will reduce
the user load across several CPUs, this will give added
performance for your users.

[1.4] Registered vs. Shareware Version

TurBoard (one node version) is distributed as Shareware
software. This means that you are able to load the software,
configure it, use it for an evaluation period and decide if you
want to continue using the software. If you decide to continue
to use the software, you are required to register the software
for $75.00.

Once you register your software, you will be able to upgrade as
new versions arrive for one (1) year from the date of
registration. If you wish to continue receiving upgrades, you
will be able to buy additional upgrade years from the support
BBS system or an authorized TurBoard dealer.

As an incentive to register the program, the shareware version
operates as one node only and displays "Unregistered Evaluation
Copy" on users log-in. Other than this, the software is fully

We are distributing our product this way in good faith. If
illegal use becomes a problem, we may discontinue shareware
distribution. Please support our continuing developmental
efforts by paying for our product.


To register your version, you will need to get your registration
serial number from Software @ Work or an authorized dealer.
Once you have the registration serial number, you must log into
your TurBoard system and enter the SE option for customize setup
(option 20). You will see two options:

11] Registered under name:

12] Registered under serial:

Change the options to reflect the name and serial number under
which your copy was registered. This is enable all the
registered features of TurBoard.

[2.0] Installation Instructions

TurBoard is distributed in a TB###.EXE file. This is a self
extracting archive that you should run in the directory you wish
TurBoard to reside in. Other utilities for NAPLPS and TurBoard
can be found in other files.


Unarchive the TB###.EXE file in the directory you wish TurBoard
to reside in.

Once you have unarchived the TB###.EXE file from your
distribution disk or from a local shareware distribution point,
you will then execute the INSTALL.BAT file.

! Save a copy of TB???.EXE, as some of the files will be removed
after they are used by the INSTALL program.

1) To configure your TurBoard system for the first time, simply


The correct subdirectories will be created and zip files will be
unzipped (make sure that your PKUNZIP program is in the current

2) Once the INSTALL program has successfully run, you will be
prompted to start TurBoard by entering the following command:


3) If this is the first time you have dealt with TurBoard,
choose the Q)uicksetup option. TurBoard will create all the
subdirectories it needs and you will only be prompted for
hardware specific information.

When configuring your modem, you should see a configuration
option similar to your modem. If not you may use the modem
configuration strings included in a later chapter to help you
configure your particular modem.

Always use TB.BAT! This is how you should always start the
TurBoard BBS system. If you do not, the system will stop
whenever someone enters a door or downloads a file.

Answer the questions. If you have a problem configuring your
modem, (you do not get the "Waiting . . ." status after you have
configured everything,) we may need to set up a special modem
definition for your specific modem. If this is the case, call
the TurBoard Support BBS system.

The following files will be unzipped in the ART, TEXT and YAK
subdirectories of the same name. They will be deleted when
INSTALL runs, but you may want to install them yourself. They
are described here for your information.

ART.EXE - Includes art for the art gallery.

TEXT.EXE - Includes Help Files, Welcome, and Logoff Screens.

YAK.EXE - Includes the menu files, news files, and the yak
data files.

(more on this later)

After this you may delete these files, you will no longer need
them all the other files are created automatically as they are


To use DSZ for downloads, you will need to install DSZ.COM into
your DOS PATH. The easiest way to accomplish this is to copy
the DSZ.COM file into your DOS directory. No modification of
your AUTOEXEC.BAT or CONFIG.SYS is required.


Follow the directions above for installing on a new system.
Once you have completed the above installation, start your
multitasking software (DesqView, Windows 3.1, OS/2 2.0, etc).
Start multiple copies of TurBoard by starting multiple DOS
sessions and entering the command TB # (where # is the node
number; ex: TB 2) from TurBoard's home directory.

TurBoard is Windows 3.1, OS/2 and DesqView aware. What this
means is that you will notice good performance when TurBoard is
running under one of these multitasking or timeslicing programs.

TurBoard will automatically create the associated files for the
different nodes. You do not need to do any special installation
for the multinode version of TurBoard. It is your
responsibility to ensure that the same node number is not used
twice. Using the same node number on two different sessions of
TurBoard will produce unpredictable results. [3.0] Command Line Parameters

"Command Line Parameters" refer to the information passed to the
program at the time the program is executed. For example, given
the DOS command "TURBOARD 1 -p2400", the command line parameters
are "1" and "-p2400" because they are both information passed to
the TURBOARD program.

Since you should never run TurBoard with the TURBOARD command,
the parameters are generally passed in from a batch file (.BAT
file) such as TB.BAT or TBFN.BAT. Certain front end programs
use the command line parameters to pass information like node
number, port and baud rate. This section will explain how you
can set your batch file to take advantage of TurBoard's command
line parameters.

These are:

# - Node number

This parameter is used when TurBoard is running over a network
or in a multitasking situation. If you plan to run more than
one executing TurBoard session on the same TurBoard software,
you will need to specify which node number you are starting so
that TurBoard will not attempt to use the same files at the same
time. In other words, if you wish to start a new session of
TurBoard, choose a node number that is not currently in use and
pass it to the program. (defaults to 1) Ex: tb 2

-l - Local Switch

This switch will bypass the call waiting screen and go directly
to local log on. For example, if you are in a networking
environment, you can use this switch at program startup, so that
the network node will begin at logon. Ex: turboard -l

-fd - Front Door Active

This switch is used when using a front door processor, such as
BinkleyTerm or Front Door. It will cause TurBoard to check for
a carrier detect, as well as to fall back to DOS after logoff.
(The call waiting screen in used in this mode.) Ex: turboard -fd

-p##### - Incoming port rate

Incoming port rate specifies the speed at which the computer is
talking with the modem. If you "lock" your port speed, this
parameter should reflect the speed at which you locked the port.
(Ex: -p19200) This switch is generally used with the -fd
switch so the front door can pass the port rate to TurBoard.
The modem to remote CONNECT rate my not be the same as the Modem
to DTE PORT rate. If this parameter is specified, TurBoard will
communicate to the modem at this rate.

-b##### - Incoming call baud rate

Incoming call baud rate specifies the speed at which the local
modem connected with the remote modem. This is generally at the
fastest rate that both modems can support. (Ex: -b2400) This
switch is generally used with the -f switch so the front door
can pass the baud rate to TurBoard. An example of the Batch
file that might be used is:

(%3 contains the baud rate parameter)

turboard -f -b%3

-cbios - Use BIOS for NAPLPS color graphics writes.

If you experience "snow" or unexpected results on you NAPLPS
displays, you may want to try this switch, it will tell TurBoard
not to use direct EGA and VGA hardware writes and to go through
the BIOS instead. On the downside, turning this switch on may
cause you to lose characters when in TurBoard Terminal Mode.

-t### - Max. Time allowed

This parameter can be used to limit a BBS visit's time limit (in
the case of an upcoming event). This parameter is usually
passed from some kind of front door processor.

%4 contains the time limit.

Ex: turboard -fd -b%3 -t%4

-cga -ega -vga - Force CGA, EGA or VGA Graphics Mode

Use this to force TurBoard into a specific graphics mode instead
of the default graphics mode. This is useful in seeing what the
system looks like for different callers. These invoke graphics
drivers for the standard CGA, EGA and VGA compatible cards.

-svga# - Force TurBoard into a SVGA mode.

Use this option to force TurBoard into a SVGA hi resolution
mode. TurBoard supports several SVGA modes that can be toggles
with replacing the # above with one of the following:

0] Standard VGA/MCGA 320x200x256

1] 256k Svga/VESA 640x400x256

2] 512k Svga/VESA 640x480x256

3] 512k Svga/VESA 800x600x256

4] 1024k Svga/VESA 1024x768x256

5] 256k Svga 640x350x256

6] 1280k+ VESA 1280x1024x256

The following graphics adapter cards are supported: Ahead, ATI,
Chips & Tech, Everex, Genoa, Paradise, Oak, Trident (both 8800
and 8900, 9000), Tseng (both 3000 and 4000 chipsets) and Video7.

Higher resolution cards have not fully been tested and may
produce unpredictable results, use only for testing purposes. [4.0] Modem Configuration

TurBoard handles the modem in a method to provide the most
efficient transfer of information from the host to the user.
TurBoard uses hardware flow control for the optimum speed in
your data communications. In addition the carrier drop is
controlled by lowering the DTR line on the modem.

Generally, you will want your modem to report to TurBoard the
actual modem connect rate (in your CONNECT ##### message), and
not the port rate. This will give your more accurate log
records as well as allow TurBoard to control the flow of
information more efficiently.

The following strings may be used to help configure TurBoard.
Use the one that most closely matches your computer. (You may
refer to your modem manual for additional information.)

TurBoard comes with a MODEMS.DAT file which includes most of
this information for you. If you did not get a list of modems
to choose from when you initially set up TurBoard, make sure
that this file is not missing. If you need to locate this file,
you may contact your local dealer or the support bulletin board.


Hayes 1200: ATS0=0M0S2=1X1H0E0

Hayes 2400: ATS0=0M0S2=1X1H0E0

Hayes 9600 V.42: AT&F&K0&C1&D2S0=0S2=255M0E0H0

Hayes ULTRA: AT&F&K0&C1&D2S0=0S2=255M0E0H0W1

USR Dual Standard: AT&F&B1&C1&D2S0=0S2=255M0E0&WH0

Boca 14.4kbps/Fax: AT&C&D2&K3S0=0M0E0W2

If you are using a modem init string not mentioned here, please
report it to us at PC Atlanta, we will include it here and
gladly give you credit for it.


When I start my system, it gets hung in a loop trying to log
itself on and off. What's wrong?

The problem lies in the modem configuration. TurBoard will jump
to the terminal emulation prompt if it thinks there is someone
on-line. Most modems can configure the Carrier Detect pin (CD)
to follow actual carrier detect or not either by switch settings
or an internal command (USR uses &C1.)

You want to set your modem up so that Carrier Detect follows
actual carrier detect. (If you do not have switch settings, add
the command to the end of your modem initialization string via
the SE command.)

When someone tries to log off the system, they just get put back
at the startup prompt again, or the BBS just sits there. What's

A high to low signal in the (Data Terminal Ready) DTR needs to
be set to cause the modem to hang up the line. Most modems use
a switch setting or AT command to control this feature. (USR
uses &D2.) If you do not have switch settings to control this
feature, add the command on the end of your modem initialization
string via the SE command.

I have an error correcting with compression 2400 bps modem,
should I lock the communications port at a high speed for
greater throughput?

This is actually personal preference, because there are benefits
to both locking and not locking your communications port. If
you lock your port, TurBoard is not as responsive to the space
bar abort function, but you will gain faster (above 2400bps)

I have a modem that will dynamically lock the port only when I
have an error correcting connection. How do I set that up?

This configuration is the best of both locking the
communications port and responsiveness. You can set a TurBoard
node up to lock the communications port only when an error
correcting or compression connection ("/ARQ") is made. Set
your modem up in it's switching mode (&B1 on the USR DS), and
set the SE Modems followbaud setting to "Locked if error
correcting connection is made." That's it!

If you have a front end processor (like BinkleyTERM) that will
do this for you, you can set that up as well. Pass the connect
rate and the port rate to TurBoard with the "-p -b"
command line parameters. (See Command Line Parameters for more

[5.0] NAPLPS Graphics/RIPscrip/ANSI/ASCII

TurBoard now supports four different graphical protocols! North
American Presentation Level Protocol Syntax (NAPLPS), Remote
Imaging Protocol Scripting (RIPscrip), VT100 (ANSI) and ASCII
(TTY) graphics.

If you have ever signed on Prodogy(tm), you have seen a form of
NAPLPS at work. The idea is to provide exciting color graphics
to the age old BBS technology. Here is a brief description of
what we are talking about:

The North American Presentation-Level Protocol Syntax (NAPLPS)
standard defines a text and graphics transmission interface with
display or recording devices with sufficient local intelligence
and memory to process the NAPLPS data stream.

In many respects, NAPLPS has reversed the normal progression
from functional description to data format or language building.
Instead, NAPLPS starts with the code extension technique
specified by ISO 2022-1982, ANSI X.41-1974, and CSA
Z243.35-1976, and fits a versatile picture-definition standard
into the constraints of the 32 character C sets and 94-character
or 96-character G sets established by those standards.

A major advantage of the code-extension technique is, of
course,that large amounts of information can be transmitted over
narrow-bandwidth transmission lines, provided the receiving
device is capable of expanding on the information.

In case you didn't understand the above, don't worry! All you
really need to understand is that NAPLPS is a way to
transmitting compressed color graphics pictures that are
hardware independent. To create these images, you will need a
NAPLPS editor (check the support BBS for current offerings).

The caller has to have a terminal emulation program capable of
decoding the NAPLPS codes. (One shareware program is
NAPCOM.ZIP.) Right now, there are not many NAPLPS terminal
emulation programs, but there are many people developing NAPLPS
technology and the current shortage will change.

Another graphical standard that has received a wide amount af
acceptance is RIPscrip graphics. TurBoard supports this
standard in the same manner that the other standards are
supported. RIPscrip graphical screens are denoted with the .RIP

TurBoard also supports ANSI and ASCII text based protocols, so
that anyone who currently calls BBS systems will be able to call
your TurBoard system as well.

TurBoard uses the file naming convention of:


*.RIP RIPscrip Frames

*.ANS ANSI Frames

*.ASC ASCII Text Files

*.TBO TurBoard Format Files

You can edit the *.TBO files with the internal TurBoard editor.
Use the command "EDIT FILENAME.TBO" to edit the files from
within the TurBoard system. You will require a NAPLPS editor
for the *.NAP, a ANSI editor for the *.ANS files (for example,
TheDraw), and a text editor for the *.ASC files. [6.0] Sysop Keyboard Commands

The following keystrokes are used to modify the operation of
TurBoard or perform a function.

Up Arrow Raise users security level.

To raise the current users security level on-line, use the up
arrow key. Their security level will raise to the next defined
security level (as set up in the SE options). Key active only
when user is online.

Down Arrow Lower users security level.

To lower the current users security level on-line, use the down
arrow key. Their security level will be lowered to the next
defined security level (as set up in the SE options). Key
active only when user is online.

Right Arrow Add five minutes to users online time.

To increase the current users time left on-line, use the right
arrow key. Their time will be increased by five minutes. Key
active only when user is online.

Left Arrow Subtract file minutes to users online time.

To lower the current users time left on-line, use the left arrow
key. Their time will be lowered by file minutes. Key active
only when user is online.

Alt-D Drop to DOS Shell

If you need to drop to DOS temporarily, use the Alt-D Drop to
DOS shell to drop to a DOS shell. If there is a user on-line,
they will be informed that the Sysop has dropped to DOS and will
be informed when you return. If you drop to DOS from the call
waiting screen, incoming calls will not be answered until you
return from the call waiting screen. If you need to busy the
line, use the Alt-X function instead.

Alt-I Information*

Gives information on registering the TurBoard BBS package.

Alt-L Local log on*

Used from the call waiting screen to log on the BBS locally.
Name and password is required for security.

Alt-O Operator available Toggle

This toggle the ability of your users to page you. Turning
sysop page on will allow the BBS users to call you for a chat
session while they are on-line.

Alt-Q Quick Logon*

This key sequence is only active from the call waiting screen.
The Quick logon will automatically log in the main (user 0)
sysop and optionally prompt the user for a password. (Set in
the SE options.)

Alt-S Snoop Mode Toggle

Snoop mode should be OFF anytime you don't wish to monitor the
BBS caller. Screen writes can slow the output data stream to
the caller, so to increase your BBS's performance, turn snoop
mode OFF at all times. This keystroke works on both the call
waiting screen and while a user is online.

Alt-T Chat mode on/ Terminal Mode

To answer a sysop page, use the Alt-T command. Also, from the
call waiting screen, Alt-T will put you in a full
ASCII/ANSI/NAPLPS terminal emulation. Alt-C also works to
invoke chat mode when actually in the system.

Alt-X Exit*

Exit the current operation. If at call waiting screen, exits

* Only available at the TurBoard call waiting screen. [7.0] User Command Overview

Following commands can be entered at the > prompt. Most of the
two letter commands require extended access.

? Help - Help with the currently executing operation.

A Art Gallery - Look at different ANSI, ASCII or NAPLPS

AA Add Art Gallery Frame - Enter new art gallery picture in the
Art Gallery List

AB Add Bulletin - Enter a new bulletin for the bulletin list.

AD Add new DOOR - This command will add a new door (be sure you
know what you're doing!)

AF Add new file directory - Will add the file forum and include
it on the forum choice list.

AL Add/Edit Language - Add/edit language file entries. (ex: AL

AL ON/OFF Turn on/off Language Codes - Use to display the
language file entry numbers.

AM Add Mail Forum - Starts a new message forum and adds all the
associated information.

AU Add New User - Utility to add user without having to log on
as new user.

B Bulletin List - Read current bulletins

B NEW New Bulletin List - List the new bulletins since you last
logged on.

BO On-line Books System - Use this command to enter the on-line
book system.

C Classified Ads - Enter/ read/ scan classified ads.

CB CB Chat - Join internodal chat system.

CD Change Directory - Change TurBoard's current file system (CD
ROM, etc)

CDO Change existing DOOR - After a door has been added, you can
change the setup with this command.

CH Chairman Utilities - Change forum defaults information.
Chairman or Sysop access. Allows the assigning (or assigning
away) of chairmanship, setting of certain forum options.

COPY Copy File - copy a file from one DOS location to another.

D Download File - Receive a file from TurBoard into your system.

DATE Date - Same as TIME command below.

DB Delete bulletin - Remove bulletin from bulletin list.

DEMO DEMO Art Gallery - Display art gallery frames in slideshow

DF Delete file directory - Remove an empty file directory from
the directory menu.

DIR DOS DIR - Give a directory of the specified DOS directory.
(ex: dir fidoin\*.*)

DO DOOR menu - Run an external program from TurBoard.

DM Delete Mail Forum - Deletes a message forum (data files
remain intact, you must physically, ie via DOS, remove the files
in that subdirectory).

E Enter Message - Send a message to another user or to the
general public.

EA Edit Art Gallery - Edit an art gallery entry.

EB Edit Bulletin - Edit bulletin setting in the bulletin list.

ED Edit Door - Edit the door information such as information
file, directory, etc.

EDIT Edit TurBoard Format File - edit specified text file (ex:
edit text\newuser.tbo)

EF Edit File Directories - Edit descriptions/sort
directories/assign security for files directories and files
within them.

F File directory List - List files available for download.

FF Find File Information - Will search all the file storage
directories for new files not included in the list and add them.

G Good-bye (log off) - Leave this TurBoard system.

H Emulation Toggle - Change to ASCII, ANSI or NAPLPS mode.

HOT Hotkey/Hotspot Frame - Edit hotspots for a particular
frame(ex:hot text\welcome)

I Inquiry (history) - Show caller history.

J Join Mail Forum - Join a message forum (usually by subject.)

K Delete message - Remove the message you just read.

L BBS List - List BBS systems on-line.

N New Files - List new files since you have last logged on.

MM Move message - Moves a message from the current forum to
another specified forum.

O Operator page - Page the operator for a "chat" session.

P Personal Mail - Read mail that has been flagged for you.

PF Pack File Descriptions - Reindex and clean up the file

PM Pack Message Forum - Deletes messages that have been
"deleted" and private mail that has been read. Removes data
files and header records.

Q Quit back to the YAK system - Tells the system to quit the
current task and return control back to the yak system.

QU Questionnaire System - Answer and edit questionnaires.

QWK QWK Off-line Mail Leader - Enter the QWK off-line reader

R Read Mail - Read messages in the current forum.

S Scan Messages in Current Forum - Show a list of message
headers in the current forum.

SE Setup Menus - Configuration menu system to configure system

T User List - List and edit the users who are active on this

TIME Show Time - Displays day, time and time remaining.

TYPE Type File - Displays the specified text file. (ex: type

U Upload File(s) - Upload files to this TurBoard system.

V Version - See the version of TurBoard this system is using.

W Who's on - See the other people signed onto this TurBoard

X eXpert toggle - Toggle the YAK system expert flag.

Y Your information - Review and change your user account

YAK YAK subsystem - Edit TurBoard's intelligent interactive

TYPE Type File - print specified text file [8.0] Detailed System Configuration

Once you are at the call waiting screen, you will probably want
to customize your system to reflect the BBS name, open or
closed, etc.

To log on for the first time, type Alt-L for local login. Give
the name and password you specified when you installed TurBoard.
When you see the ">" symbol, this is the primary TurBoard
command prompt. Any command may be entered whenever you see
this prompt.

Enter the "SE" (for setup) command to see a list of configurable

[8.1] PC Chattanooga! Customization Menu

1] Customize System 2] Customize Node

3] Customize Modem 4] Customize Network

5] Customize Security Levels 6] Customize Archive

7] Customize Forum 8] Customize Directory

9] Customize Classifieds 10] Customize BBS List

11] Customize Door 12] Customize CB Chat

13] Customize QWK 14] Customize CD ROM

15] Customize Billing 16] Customize Books

17] Customize Bulletins 18] Customize

19] Customize Users 20] Customize Setup

21] Customize Art Gallery

To customize an option, choose it's number [quit]

Following is a more in depth look at each of the customization
menus and what each of the options mean.


System Customization Menu

1] Name: TurBoard BBS

2] Password: None 3] Sysop password: None

4] Sysop available: Yes 5] Sound: On

6] Total callers: 80 7] Open system: Yes

8] Time zone: EST 9] Log records: Monthly

10] Alias names: Not allowed. 11] ASCII: Allowed.

12] ANSI: Allowed. 13] NAPLPS: Allowed.

14] RIP: Not Allowed.

To change an option, enter it's number [quit]

Name - This is the system name (ex: PC Atlanta!) that you wish
to refer to you BBS system as. Setting this option will cause
your system name to appear throughout the system menus, such as
the file directory screens.

Password - If you desire, you may require a logon password for
EVERYONE to use every time they log on. Some Sysops desire a
private board, but one you don't have to be pre-registered to
log into, this is a method to accomplish that.

Sysop Password - For added Sysop access security, this option
will require all users with Sysop access to enter this password.
This is good if your Sysops use their password on another

Sysop Avail - Toggles the message the user gets when O option is
used. Same as Alt-O at the keyboard, but allows the Sysop to
turn this option on and off remotely.

Sound - If this option is turned on, the BBS will beep (ASCII 7)
when the user does. This is defaulted to off.

Total Callers - How many people have called the BBS to date.

Open System - Normally yes, this option can disallow new users
tolog on.

Time Zone - Specifies which time zone the BBS resides.

Log Records - Specifies how the system log is kept. If None,
then no monthly files are kept of the user activity. Set this
option to 1 for monthly files.

Alias names - Does your system allow the use of alias names, if
so, allows the system to set alias names for new users, message
areas, etc.

ASCII - Allows the use of ASCII terminal emulation.

ANSI - Allows the use of ANSI terminal emulation.

NAPLPS - Allows the use of NAPLPS terminal emulation.

RIP - Allows the use of RIPscrip terminal emulation. [10.0] NODE CUSTOMIZATION MENU

Under the SE options, you can adjust the specific information
for the current node (you are logged into).

Node: 1

1] COMM. PORT: Local

2] Modem type: Local

3] Snoop: On

4] Minimum baud allowed: 300

5] Maximum baud allowed: 99999

6] Port address:

7] IRQ:

Number to change [quit]

COMM. PORT - Which hardware communications port will this node
be using. (Local means a network node.) Use 0 for local mode.
This setting is used to determine if DigiBoard, FOSSIL or
internal communciations drivers are to be used.

For example, if you choose 1 as the port, TurBoard will first
attempt to access the DigiBoard port 1, followed by FOSSIL
driver port 1 and then finally internal COM1 drivers to drive
the communications ports.

If you wish to use a combination DigiBoard/FOSSIL system (for
large multinode systems), you should start the DigiBoard port
numbers at some point HIGHER than the highest FOSSIL driver you
wish to use. For example, use port COM1 and COM2 for FOSSIL
port 1 and 2 while using DigiBoard ports 1-8 as port 3-10.

Modem Type - Which modem is attached to the communications port.
You can also use this setting to select a new modem type and
use the modem setup menu to set the individual options for that

Snoop - Toggle for turning on and off this nodes snoop mode.

Minimum baud allowed - Limits the modem callers to have a modem
capable of at least this modem speed.

Maximum baud allowed - Used to limit callers to a particular
range of connect speeds.

Port address - Used to change the default port address for the
particular port number being used. This only has an affect
external program parameters and the internal communications
driver for TurBoard.

IRQ - Used to change the in use IRQ for the port number
specified above. This has an affect on external program calls
and the internal communications driver in TurBoard. [11.0] MODEM SETTINGS MENU

In the SE setup menus, choosing Modem Settings will product the
following options:

1] Name: Modem Name

2] Init string: ATZ

3] Terminal init string: ATZ

4] Maximum modem speed: 2400

5] Modem offhook cmd: ATH1M0

6] Hang up cmd: ATH0

7] Connect response: CONNECT

8] Answer cmd: ATA

9] Lock baudrate: No

10] Ring response: RING

11] Ringing response: RINGING

12] No carrier response: NO CARRIER

13] Timeout: 34 seconds

14] Logoff wait: 2 seconds

Number to change [quit]

Name - The name of the modem installed on this node.

Init string - The modem command (initialization string) used to
reset the modem when TurBoard is initially set up. This string
should set up the modem so that it reports a true CD signal and
a high DTR to low DTR will cause the modem to drop carrier.
(See section on initialization string.)

Terminal init string- This is the modem command used to set up
the modem for use in TurBoard terminal mode. A typical setting
might be "ATM1H0E1L1".

Maximum modem speed - Specifies the maximum throughput of the
modem installed on this node. A typical setting might be "2400".

Modem offhook cmd - The command used to take the modem off hook
(busy the line). A typical AT command might be "ATH1M0". If
you do not want the modem taken off hook whenever you exit
TurBoard, set this option to a blank line.

Hang up cmd - The modem command used to hang up the modem. A
typical AT command is "ATH0M0".

Connect response - The response given by the modem whenever a
data connection is made. A typical modem will respond with

Answer cmd - The modem command used to answer the incoming call.
A typical AT command is "ATA".

Lock baudrate- This option tells TurBoard if you are locking the
baud rate or not. If you lock your port speed to the modems
maximum throughput, set this option to YES. Otherwise, set this
option to NO. For most non-error correcting modems, set this
option to NO.

Ring response - The modem response given when an incoming call
is received. A typical modem will report "RING".

Ringing response - The modem response given when an outgoing
call is being made. A typical modem will report "RINGING".
(Some modems report "RING" for this as well.)

No carrier response - The response given when there is no answer
to the call. A typical modem will report "NO CARRIER".

Timeout - The amount of time to wait while the modem is
attempting to make a connection. A good setting for this is 45
seconds, if you have an error correcting modem, you may wish to
increase this time. (Some modems are slower at detecting the
error detection than others.)

Logoff wait - The amount of time between when TurBoard is
finished displaying the LOGOFF file and carrier is actually
dropped. If you have a buffered high speed modem, you may wish
to increase this time so that the modem will be able to send all
the data before carrier is dropped.

If you wish to add a new modem type, go to the SE Node setup
menu, and change the Modem type to "New Modem Type". This will
reset all the options for your modem, and you may change them
with this menu. [12.0] FidoNet Support

FidoNet is a worldwide network of bulletin board systems which
communicate to each other through message "packets" TurBoard
v0.33 and above will interface with any other FidoNet or
compatible system through a front door. A front door is a
program which answers the incoming call, decides if the caller
is another FidoNet system or an actual user, and either receives
the FidoNet package or transfers control to the BBS system

TurBoard includes all the files necessary to configure FidoNet
with a front door processor. This includes the
"scanning/tossing" of incoming and outgoing messages. This is
performed by the TBFIDO.EXE program. This program will convert
the incoming FidoNet messages to TurBoard format and put them in
their proper message forums. It will also export messages
entered in the TurBoard forums and put them into FidoNet


The hardest part about interfacing with another external program
is configuration. TurBoard has been extensively tested with
BinkleyTerm, and I would suggest using that software. Included
is a text file called BINKLEY.CFG. This file contains an
example BinkleyTerm configuration file. There is also a .BAT
file included (TBFN.BAT) that should be used to initialize
TurBoard when running FidoNet.

It is your responsibility to ensure that the nodelists and other
data that BinkleyTerm requires is configured correctly.

When you are running FidoNet, start the TurBoard system with
TBFN.BAT rather than TB.BAT, this will run the message packer
and automatically start BinkleyTerm. I would suggest
configuring BinkleyTerm to match the ErrorLevel operations used


Actually, TurBoard is about ready to receive FidoNet message
strait out of the package. Most of your time will be spent
setting up your front door processor (which can be trick if you
are not programmer inclined.)

To set up TurBoard for FidoNet, you will need to specify your
address in the SE menu. You will also need to set up one of
your message forums as the primary FidoNet forum.

To setup the FidoNet forum (which can be any forum other than an
echoed forum), join the forum you wish to use. (If you do not
have any forums defined yet, use the AM command first and then
join that forum. But remember, the first forum you create will
be your master message forum, so you may want to name it
something like "PRIMARY" and then add a new forum for FidoNet,
which you may want to name "FIDONET".)

Once you are in the forum you wish to use for FidoNet messages,
issue the CH command and choose the option for Mail Type (it
will currently say: "Normal"). Change this setting to F for
FidoNet. At this point you are ready to go. Any messages
designated with an address in this forum will be placed in the
FIDOOUT directory for processing by the front door. It is your
responsibility to ensure that the address on the message is


This program serves three functions. First, it scanning the
incoming FidoNet directory and converts that information into
usable information by TurBoard. Secondly, it checks the
outbound FidoNet packets, if it finds ones marked .ECHO, it
combines them into "ArcMail" which are nothing more than FidoNet
compressed packets with the ARC.EXE utility.

Thirdly, if the -p command line parameter is specified, the
program will scan and pack all of the active TurBoard message
forums. This is complete and automatic. The settings for the
compression are set with the CH command in the TurBoard system

You will notice a new user added to your user log when you run
this program. It is the "MESSANGER ANGEL" alias "FIDONET
TOSSER" user. This is the user entry that TurBoard uses to keep
up with what has and hasn't been sent by FidoNet. Do not be
alarmed, this is not a back door, and it is impossible for
anyone to log in under this account.


Cost of messaging is very important to most FidoNet sysops.
Currently, TurBoard does not keep track of how much a message to
a certain system will cost, or even if the target system exists.
For this reason, it is important that you configure your front
door processor (most likely, BinkleyTerm) when it can and cannot
send messages to different systems. This is performed with
theBINKLEY.EVT file. Here you can specify the cost of a message
that is allowed to be mailed. (BinkleyTerm will check the
Nodelist for an entry and figure the cost from that list.)


TurBoard can handle echomail. To configure where outgoing (and
incoming) messages are going, as well as the name of the
EchoMail area, use the CH command for your particular forum.

For example:

Once I have set up my system for FidoNet, I perform the

Say I wanted to set up an EchoMail forum with PC Chattanooga in
Chattanooga, TN. And the name of this EchoMail "AREA:" is
TURBOARD. (This would be an answer and question echo about the
TurBoard BBS software package.)

First, I would create a new message Forum. To do this I would
issue a AM command, choose a name for the forum (say "SUPPORT")
and enter a brief description. Okay, now I want to join that
forum with the J SUPPORT command.

Once I have the SUPPORT forum as the active forum, I issue the
CH command to bring up the chairman utilities. I choose the
option named "Mail type" (it currently says "Normal"), and then
choose E for FidoNet Echo.

Now, I choose the option to give the system the name of the echo
area (it will say: SUPPORT). I want to change this to
"TURBOARD" since that is the name that FidoNet calls it (so
TBFIDO.EXE will know where to put those messages). I also want
to set up the address of the other echomail members I am
responsible for sending and getting this echo from.

You might choose the last option and add the address:

Zone: 1

Net: 133

Node: 904

Point: 0

Once I've done this, I'm ready for the echo to be sent to me!
The same procedure can be followed for ANY FidoNet echo.


1] FidoNet (1:999/999.0)

2] Add new network.

Option number [quit]

This menu is used to tell TurBoard what Fidonet-style networks
you have available and what address are you are known as in
those networks. TurBoard supports an unlimited number of
concurrent networks. Once a network has been added to the list,
you may set it with the Network Options Menu. Those options are
explained below.


1] Name: FidoNet 2] Network archive: ZIP

3] Zone: 1 4] Net: 362

5] Node: 614 6] Point: 0

7] Extension: 8] Directory:

9] Gateway zone: 0 10] Gateway net: 0

11] Gateway node: 0 12] Gateway point: 0

13] Delete this record.

Number of option [quit]

Name - The name of the network that you are setting up. Ex:
FidoNet or AlterNet, etc.

Network archive - The archiver that this network uses to create
it's network mail. (Must be set up in the system's archiver
utilities, see below)

Zone - Your ZONE address for this network. (Typical network
addresses are of the form: Zone:Net/[email protected]) If
you are joining a network, please get this information from your
local NC (network coordinator).

Net - Your NETWORK address for this network.

Node - Your NODE address for this network.

Point - Your POINT address for this network.

Extension - Your network EXTENSION for this network. An
extension is typically used on the internet and describes the
information trailing the "@" symbol. For FidoNet, the extension
is "" and that is what this option should be set to.
Typically, if you are starting a new network, your extension
should be "name" + "." + either "org" for an organization or
"com" for a company or "edu" for education or "gov" for

Directory - A directory that you wish the outbound mail to be
sent to. Leave blank unless you have different mailers for
different networks. (In other words, if you are running FidoNet
and TurNet, and want to use different phone numbers for both of
the networks, you would specify a special directory for the
FidoNet and a special directory for the TurNet. This directory
name is a subdirectory off of the outbound fidonet directory,
normally FIDOOUT. Ex: TURNET would equate to the outbound
directory FIDOOUT\TURNET.)

Gateway zone - This is an option to tell TurBoard to
automatically send all outbound mail through a gateway machine.
This option should be set to the ZONE of the gateway machine you
wish ALL your outbound mail sent to.

Gateway net - Network address of the gateway mail machine.

Gateway node - Node address of the gateway mail machine.

Gateway point - Point address of the gateway mail machine.

Delete this record - If you wish to remove this network, choose
this option.


The TurBoard security levels can be customized. You can add new
security definitions as well as change names and time limits on
currently defined levels. You can enter colors at the command
input line, but you will need some additional information, refer
to the "Colors?" section below.

Value Name Time Limit


10 New User 40

20 Full User 180

30 Special User 360

200 Co-Sysop 1440

255 Sysop 1440

1] Change security name.

2] Change security level time limit.

3] Delete security level.

4] Add new security level.

Change security name - Change the color and name of a security

Change security level time limit - Set the time limit of a
security level. The time limit refers to the total number of
minutes per day a user has online.

Delete security level - Delete a security level from the list.

Add new security level - Add a new security level to the list.


1] ARC Archive

2] ZIP Archive

3] Archive

4] Archive

5] Archive

6] Archive

7] Archive

8] Archive

Choose utility to modify [quit]

TurBoard can support up to eight different archive utilities at
once and uses this list to automatically dearchive new uploads
for virus scanning and FILE_ID.DIZ support. Following are the
prompts that need to be answered when one of the above is chosen.

Enter name for archive [ARC]:

This is the name of the archive. TurBoard comes preset with ARC
and ZIP defined for you. It is up to you to add LZH, ZOO, ARJ
and any other that you wish to use.

Enter archive program (with complete path) [C:\DOS\PKARC.COM]:

This is the path and filename for the archiving program.

Enter parameters for archiver (use "%s" for source and "%t" for
target) [a %t %s]:

These are the parameters for the archiver to use when executing
the archive. %t is replaced with the targed archive and %s is
replaced with the files that are to be archived (source).

Enter unarchive program name (with path) [C:\DOS\PKXARC.COM]:

This is the path and filename for the unarchiving program.

Enter unarchive parameters (use "%s" for source and "%t" for
target) [%s %t]:

This is the parameter list that is passed to the unarchiving
program. %s indicates the source archive file and %t indicates
the target path and name of the files that will be extracted.

Enter ASCII value of first byte in archive [26]:

This indicates the first byte value in this particular archive
type. For example, if the first byte in the archive file is an
ASCII 26, we know that the file is an ARC type archive.

Enter standard extension for this archive [ARC]:

This is the standard extension for the archive file. In the
case of the ARC archiver, the extension is "ARC".

Here are some standard archive setups for some common archive

Name of archive: ARC

Archive Program: C:\DOS\PKARC.COM

Archive Parameters: a %t %s

Unarchive Program: C:\DOS\PKXARC.COM

Unarchive Parameters: %s %t

ASCII Value: 26

Standard Extension: ARC

Name of archive: ZIP

Archive Program: C:\DOS\PKZIP.EXE

Archive Parameters: %t %s

Unarchive Program: C:\DOS\PKUNZIP.EXE

Unarchive Parameters: %s %t

ASCII Value: 80

Standard Extension: ZIP

Name of archive: LHA

Archive Program: C:\DOS\LHA.EXE

Archive Parameters: a %t %s -m

Unarchive Program: C:\DOS\LHA.EXE

Unarchive Parameters: x %s %t -m

ASCII Value: 34

Standard Extension: LZH

[15.0] Mail System

There are three types of message forums currently available in
TurBoard. They are: Topical, Network and Echo. A topical
forum is a message area that resides only on TurBoard. In other
words, the messages found in the forum will only be found on
your TurBoard system and nowhere else. A network forum is a
forum that allows you to mail messages to another bulletin board
system, typically through a network like FidoNet. For instance,
if you wanted to address a message to the TurBoard support BBS,
and you belonged to FidoNet, you could do so and it would be
delivered to the TurBoard support BBS. These messages will only
appear on your BBS and the support BBS (this is called network
mail or netmail for short).

The third type of forum is the echo forum. A forum is
considered "echoed" if 2 or more BBS systems share every
message that is entered into the forum. If someone enters a
message in that forum on another BBS, it will eventually appear
on your BBS as well, no matter who it is written to. This is a
good way to share information without having to reenter the
message multiple times to different people. TurBoard allows
unlimited message forums (limited,rather, by your available hard
disk space).

You must create the message forums with the AF command (standing
for Add Forum). The first forum you create is very important!
It is the default forum, a good name is "MAIN" or "PRIMARY".
Unless another forum is joined first or someone reads all the
messages and automatically joins the next forum, messages
entered with the E command get sent to this forum.

The primary message forum will always be displayed at the top of
the forum list. Everything below that is sorted in alphabetical

There are several commands that are available while you are
reading or scanning mail. These are:







Usually, there are no requirements placed upon the Sysop for
maintaining the message forums. And assuming you had unlimited
disk space, everything would be okay.

The PM (for pack messages) is a local forum command that removes
all messages flagged for deletion as well as all private mail
that has been read.

Another problem that Sysops run into is messages entered into a
forum that really belong somewhere else (like in the primary
forum). The MM (for move message) command will copy a message
to the specified forum and flag the original message for

Conference Chairmen have the ability to PM and MM in their
respective forum (and only in their respective forum).


It is profitable for everyone when you assign a leader or
"Chairman" to a forum. People can identify him/her with the
forum topic and have a direction to ask questions and enter
comments. The Sysop benefits by not having to police every
forum and allowing the Chairman to pack and move messages.

Chairmen have the power to read private mail, delete and
undelete any message in their forum. Chairmen also have the
power to set the security level required to read/enter messages
as well as changing the description line for the conference via
the CH command.

Chairmen can also assign away their chairmanship.

There are several things that a chairman (as well as the Sysop)
has control over. They include how many messages should remain
active at any given time, how old messages can be before they
are deleted, if people can enter private mail in this forum,
what security levels can read or enter mail in this forum, and
the description of the forum (displayed in the forum menu.)


Security is also defined by the CH command. The security level
for each message forum can be set as always with a "security
level >= X" where X is a security level set by the Sysop.

For example, if a Sysop has defined security level 35 to be
"Macintosh Users" and 40 to be "Amiga Users" and 50 to be "DOS
Users" and wishes only "Macintosh Users" and "DOS Users" to
access the "Windows GUI" forum, security can be set as follows
(via the SE command, set security level).

Security Level >= 200 (All levels >= 200 have access)

Security Level = 35 (Give Macintosh Users access)

Security Level = 50 (Give DOS Users access)

Up to four specific "exact" security levels may be defined.
This method gives greater flexibility than pervious "group"
methods, as the entire BBS is not limited to a certain number of
"groups". Access, however, may only be given to a maximum of 4
specific security levels and one greater than or equal range of
security levels.

Also, in the case of FidoNet forums: A user with security
greater than or equal to the enter security for that forum may
enter normal messages. BUT, if that user attempts to enter or
reply to a FidoNet message, their security level must exceed or
be equal to that of the security level set tin the SE option for
entering FidoNet messages. That is to say, a FidoNet (not Echo)
message can only be sent if the security of that user is

Every forum may have a initial screen displayed when you first
join it. This is useful in showcasing the forum for first time
joiners, so they will get an idea of what the forum is about.


1] Add forum security: >=200

2] Remove forum security: >=200

3] Real all mail (private, deleted, etc): >=200

4] Enter netmail security: >=100

5] Move message security: >=100

6] Allow fidomail to passthrough: No

7] Chairman utility in any forum: >=200

8] Forum information path: MAIL\

Enter number to change [quit]

Add forum security - Security level required to add a new forum
with the AM command.

Remove forum security - Security level required to delete a
message forum with the DM command.

Real all mail (private, deleted, etc) - Security level required
to read all mail everywhere and in every forum.

Enter netmail security - Security level required to enter a
netmail message (FidoNet style message with address). This is
also required to reply to a netmail message.

Move message security - Security level required to move a
message to a new forum, or to move it to the end of the current

Allow fidomail to passthrough - This option tells TurBoard
whether or not to forward netmail to it's destination. In the
case where you receive a message intended for another address,
TurBoard can forward the message to the correct address when
this option is set to YES.

Chairman utility in any forum - Security level required to use
the CH utility in *any* form. The chairman of a forum may use
the CH command in their respective forums without meeting this
security requirement.

Forum information path - The path that contains the FORUM.DAT
file and the subdirectories for each forum. The path is
typically "MAIL\".

[16.0] File System

File directories in TurBoard are used to categorize files into
different interest groups. In reality all the files
descriptions are stored in one file. A separate file contains
information on the "directories".

When a file belongs to a directory, it is specifying where it
resides on the BBS system physically. In addition it is giving
a general description of what the file does/is. Please do not
manually move files, as TurBoard


Adding a new file directory is easy. Use the AF (Add File
directory) command to specify a name for the directory, path on
the disk drive, and description. The name is of little
importance, but you should note that the directory menu sorts
the descriptions based on your directory name.

For example:

UPLOADS Recent Uploaded Files

DOSGAMES DOS Game Programs

DOSGRAPH DOS Graphics Programs

Will appear as:

1] DOS Game Programs 2] DOS Graphics Programs

3] Recent Uploaded Files

This is useful when you want to group like directories together.

Another function you should be aware of is the FF command. This
command will scan all of your disk drive directories specified
in the file descriptions for new files. If one is found, it
will prompt you for information about that file.

To list the files you currently have on-line, use the F command.
You will see the file directory menu, and at this point you may
choose a number or type in a search keyword. For example, you
may type DOS and GAME to get files that match those keywords.


The easiest and best way to add files to your directories is to
upload them while locally logged on. For example:

First, you must have an upload (UPLOADS) directory, if you are
not sure, read the section on uploads below before continuing in
this section.

While you are locally logged on (either by ALT-L or the DOS
command "turboard -l") use the U command (for upload file). You
will be prompted for a path and a filename. Give TurBoard the
path and filename of the file you wish to upload, and it will be
added to the upload directory.

Once the file is added, display it with the N command. Choose
the number of the file you just uploaded, and then choose the
option to move the file. At this point, you may place the file
in any directory you see fit.

To add a lot of files at once, copy the files (at the DOS
prompt) into the physical directory you wish to add them to.
Log back into TurBoard and use the FF function. Enter each
description of the files. Verify the files were added by using
the f command and listing your directory.

Once a file is added, ALWAYS move it with the TurBoard move
command, otherwise the File Listing will not have correct file
location information.


In version 1.00 and better, uploads can go to any file
directory, if the Sysop sets the security to upload to that
directory to a level obtainable by the uploader. In addition
the Sysop may restrict all uploads to one particular directory.

When a file is uploaded (or placed in the upload directory and
FF function used), you will be asked for a one line description
of the file. Following that, you will enter the full screen
editor where you will be tempted to write a paragraph or two on
the file. This is purely optional, you can abort the edit and
continue on.

There is a text file that is displayed whenever the U command is
issued. It is called UPLOADS.*. If you have used the default
subdirectories, use the command:

> edit text\uploads.tbo

You can include TurBoard colors and text to be displayed,
formatting is automatic.

There are additional special directory information files that
you may want to create. These files are keyed to the search
keywords or directory names. For example, you can create a
UPLOADS.FXT file in the TEXT directory to display whenever
someone lists your most recent uploads. If someone enters the
command "F ALL" TurBoard will check to see if there is an ALL.*
file in your TEXT directory, and if so, display it along with
the complete file listing. Other examples are "F GAMES" for
GAMES.* or "F 3" for the directory name for #3.


The EF (edit file directory) command will allow you to set some
options specific to a particular file directory. A typical menu
might appear as this:

Name: TEST


1] Description: This is a test directory

2] Upload security: >=0

3] Download security: >=0

4] Delete this directory.

5] Move all files to another directory.

6] Assign download security to all files.

7] Sort by: Age

8] Sort this directory.

Number to change [quit]

Description - This option allows to change the description of
the directory. This directory description will appear in your
file directory list unless you are using a test file to display
you directory list.

Upload security - This is the security that is required to
upload files to this directory (this is used when the SE file
settings allows the user to specify which directory they are
uploading the file to.)

Download security - This is the security required to download a
file in this directory. NOTE: The files download security
overrides this download security. If you move a file from
another directory into this one, the old file security will be
assigned to it. For this security to take effect, the Sysop
must choose the option to assign download security to all files.

Delete this directory - This option will remove this directory
from the file directory list. The directory must be empty
before the directory may be removed.

Move all files to another directory - This option moves all of
the files in this directory to another directory.

Assign download security to all files - Once you have decided on
a security level to use on all the files in this directory,
choosing this option will assign the download security specified
above to all the files in the directory.

Sort by - The file directories may be individually sorted by age
or name. This option will specify which you wish this directory
to be sorted by.

Sort this directory - If you do not wish to perform a full FF
command, you may choose this option and just reindex this
particular directory. This will have the same result on this
directory as performing a FF on the entire file system.


Under the SE options menu, you can further customize the
performance of the file area menus by changing the following

1] Add file directory: >=200

2] Edit file directory: >=200

3] Fix-Files utility: >=200

4] Edit list entry: >=200

5] Extended edit of list entry: >=200

6] Upload directory: User Chooses

7] Upload: >=10

8] Assign public uploads the SL of: >=10

9] Assign private uploads the SL of: >=200

10] File information directory: FILE\

11] Ask for detailed description: Off

12] Download: >=10

13] Virus Scanner Program:

Option to change [quit]

Add file directory - Security level required to add a new file
category with the AF command.

Edit file directory - Security level required to execute the EF
command and edit a specific file directory's settings.

Fix-Files utility - Security level required to execute the FF
command which packs the file directory and reindexes all of the
file directory lists.

Edit list entry - Security level required to use the edit
options on a file when it's number is entered from a file

Extended edit of list entry - Security level required to edit
the extended option on a file when it's number is entered from a
file listing.

Upload directory - The internal name given to the upload
directory you wish uploads to be placed. If this option is left
blank, the uploader chooses which directory to place his/her

Upload - The security level required to perform an upload.

Assign public uploads the SL of - The security level assigned to
new uploads. If you do not wish uploads to be available
immediately, set this security level higher than that of your
normal users.

Assign private uploads the SL of - This is the security level
assigned to those files uploaded with a description beginning
with "/".

File information directory - The directory used by TurBoard to
store the file list information. The standard default is

Ask for detailed description - This tells TurBoard weather or
not to ask the user for a detailed description when uploading

Download - The security level required to download files.

Virus Scanner Program - The .BAT file that TurBoard will execute
in the upload file directory immediately after an upload has
been performed. It is this bat file's responsibility to scan
each of the files in the directory and delete the file if a
virus is found.

[17.0] Classified Advertising System

The Classified feature of TurBoard is not a standard bulletin
board feature. It's function is to provide a place for the
buying and selling of goods through the public (not retail).

Most bulletin boards will include a "For Sale" forum to
accomplish this function. I found that this was difficult for
people to use because it didn't organize the information in a
way people could easily get at it. They are required to scan
the subject of every message and pick the one's they are
interested in.

This will work okay so long as there are only a few ads to scan
though. So I thought to myself, "What do people normally use to
buy and sell items? Classified ads!" So I decided to implement
an "electronic" version of the classified ads.

I have included a rather detailed category file that is based on
the Atlanta Journal/Constitution. Of course, you can create
your own, but it's tedious! The file that contains the
classified categories is the CATAGORY.DAT file in the classified
ads path. If you are missing your categories, make sure that
you have this file.

You may add new classified categories with the C command.
Simply choose the "Add new category" option. Other than this,
the system is completely self maintaining.


Last updated: Jan 19, 1993 (9:18 pm EST)

1] Read Classified Ads.

2] Place classified ads.

3] No ad replies.

4] Enter/edit your resume online.

5] Scan r‚sum‚'s online.

6] Add category.

7] Edit category.

Number of option [quit]

Read Classified Ads - Reads the classified ads by department and

Place classified ads - Enter a new classified ad.

No ad replies - This is the option that reads the ad replies.
If there are no replies waiting, the option will read "no ad
replies". If there are replies, the option will reflect that
there are replies waiting to be read.

Enter/edit your resume online - Everyone is allowed one resume
in the system, and must use the TurBoard editor to enter the

Scan resume's online - Scan the resumes that have been entered
on the system.

Add category - Add a new category to the classifieds system.

Edit category - Edit a category in the classifieds system.


1] Classified ads: >=10

2] Delete classified ads: >=200

3] Edit ad categories: >=200

4] Enter resume: >=10

5] Scan resumes: >=30

6] Classifieds path: ADS\

Option to change [quit]

Classified ads - Security level required to enter the classified
advertising system. (If you wish to turn off the classified ads
system, set this security to a high value).

Delete classified ads - Security level required to remove a
classified ad from the system.

Edit ad categories - Security level required to add, remove or
edit the categories used in the classified ads.

Enter resume - Security level required to enter a resume into
the resume portion of the classified ads.

Scan resumes - Security level required to scan the resumes that
others have entered.

Classifieds path - Path used by TurBoard to store all the
information related to the classified ads.

[18.0] BBS List System

This is a fairly standard BBS feature. There are some doors
that perform the same function available. The advantage to the
TurBoard BBS List command (L at the main prompt) is the ability
to comment and review each BBS entry individually.

The BBS List also does not require any maintenance on the
Sysop's part.

Once you choose the L command, you have several options. A
complete BBS list, a local BBS list, add a new BBS entry or
create the BBS text file.

The difference between the complete and local BBS list is the
"Is this BBS a local call?" flag. Only those that answered yes
are displayed in the local BBS list, thereby eliminating toll
call BBS's.

To add a new BBS entry, you can accomplish that one of two ways.
You may use the ADD command while displaying the entire BBS
list, or you may simply choose option 3. If you use the ADD
function, you will see the BBS inserted in the list as you are
listing it, so you can ensure that it was indeed added.

Option 4, create the BBS text file, is an option you can use to
publish your BBS list. It will create a text file with two
sections, a short BBS list and a detailed BBS list. Before the
first section the file "BBSLIST.TXT" will also be included from
the text file path.

If you wish to edit this file, and you have used the default
path names, use the command:

> edit text\bbslist.txt

After you have edited the file, save your changes and it will be
included in your next BBS text file creation.


Last updated: Jan 6, 1993 (5:16 pm EST)

1] Local area list.

2] Complete list.

3] Add new list

4] Create new text file.

Enter option number [quit]

Local area list - Option used to display the BBS list. The list
will be displayed one page at a time, and the user may add a new
entry in the list at any time with the ADD command while
displaying the list. This version of the list will include
those marked with the "local call" flag only.

Complete list - Option used to display the complete BBS list.
This will include local and long distance numbers.

Add new list - Used to enter a new BBS in the bbs list. (This
can also be accomplished with the ADD command during the normal
BBS list.)

Create new text file - Used to create a text file containing all
the BBS's in the list.


You may wish to exclude words like "The" and "BBS" from the name.

Enter new name [quit]?

The name of the new BBS entry.

Enter new sysop name [quit]?

The name of the Sysop of that BBS entry.

Enter new baud rate [2400]:

The maximum baud rate that the BBS supports.

The following should be a general statement as to the audience
of the BBS.

Enter new theme [quit]:

This should be a short statement about the topic of the BBS.

Please use ###-###-#### format.

Enter new data phone (###-###-####) [quit]:

The phone number of the BBS.

Is this a local call to this BBS [no]?

This is the answer that divides the local and long distance
version of the list.

Enter new maximum protocol (NAPLPS, ANSI or ASCII) [quit]:

This is the maximum protocol supported by the BBS.

Enter new supported networks [quit]:

Information on the networks supported by the BBS.

Enter new city [quit]:

Information on the city that the BBS is located in.

Enter new BBS software [quit]:

Information on the BBS software that is in use on the BBS.

Enter new computer brand [quit]:

Computer type being used.

Enter new disk size (in MB) [quit]:

Disk space available on the BBS.

Enter number of data lines [quit]:

Number of data lines available on the BBS.

Enter new modem type [quit]:

The modem type being used on the BBS

Is it okay to add this information [yes]?

Prompt asking if it is okay to add this information.

Any or all of these question may be changed with the language
file option. For more specifics on how to do this, see the
section below on the language file in TurBoard.


1] BBS List: >=10

2] Create BBS List text file: >=200

3] Delete BBS List entry: >=200

4] BBS data path: BBSLIST\

Option to change [quit]

BBS List - Security level required to enter the BBS list system.
If you wish to turn the BBS list off, set the security level to
one that is higher than your normal users.

Create BBS List text file - Security level required to create
the BBS list text file.

Delete BBS List entry - Security level required to delete an
entry from the BBS list.

BBS data path - The path used by TurBoard to store all the
information related to the BBS list.

[19.0] Door System

A "doorway" or "door" (once called a "window") is actually an
external program that the bulletin board software passes
complete control to. This is generally a game (likeTradeWars or
Solar Realms) or some useful information, like a BBS list or
Bible Trivia Game. It is TurBoards responsibility to initialize
any information files that the door requires.

TurBoard uses the AD (add door) and CD (change door) command to
maintain the door system. Doors can be entered with the DO
command. In order for doors (and up/downloads) to work
correctly, TurBoard must be started with the TB.BAT file,
otherwise, when a user enters a door, it will drop to DOS and
processing will stop.

Doors are by far one of the hardest things to install, simply
because there is no specified standard by which they work. Each
one is different and therefore a challenge, I'm afraid to say.
There are several questions you will be asked that TurBoard uses
to try to talk with a door. These are:


Name: TEST

1] Description: test door

2] Door path: DOOR\TEST

3] Bat File: TEST

4] Information file: PCBOARD.SYS

5] ASCII: Allowed.

6] ANSI: Allowed.

7] NAPLPS: Not allowed.

8] Security: >=0

9] Delete this entry.

Name - The 1-8 character name you choose to give your door.

Description - A 60 Character description of the door contents.

Door Path - The physical path of the door (this may be specified
from the root TurBoard path, i.e. DOOR/SOLAR is the name of
C:\TURBOARD\DOOR\SOLAR, if C:\TURBOARD is your root TurBoard
path;the path you are in when you start TurBoard.)

BAT File - the DOS command to start the DOOR, usually a BAT
file. This BAT file should exist in the directory you specified
in the PATH option. Also, the YAK % variables are active on
this command line so you can specify specific directories or
dynamic paths to your information file. For example, the BAT
file will be invoked by a DOS "CALL " where
is this option.

Information File: There are three information files that
TurBoard supports. They are: DOOR.SYS, DORINFOx.DEF, and
PCBOARD.SYS. See your door's documentation to see which one
your particular door requires.

ASCII - If this option is true, the user must have ASCII on
before entering the door.

ANSI - If this option is true, the user must have ANSI graphics
turned on before entering this door. This helps cut down on
ASCII users starting something they cannot finish.

NAPLPS - If this option is true, the user must have NAPLPS
graphics turned on before entering this door. This helps cut
down on ANSI below users starting a NAPLPS graphics door.

Security - The minimum required security level of the user
starting the door.

Delete this entry - option to delete this door record.


1] Door system: >=10

2] Add door: >=200

3] Edit door setup: >=200

4] Door path: DOOR\

Option to change [quit]

Door system - The security level required to enter the door
system. If you wish to turn off the door system, set this
security level to one that is higher than that of your normal

Add door - The security level required to add a new door with
the AD command.

Edit door setup - The security level required to edit a door's
settings with the ED command.

Door path - The path used by TurBoard to store all the
information dealing with DOOR programs.

[20.0] CB Chat System

Another nice feature in TurBoard is the built in CB Simulator.
To take advantage of the simulator, you need a multinode system.
As Sysop you can create a CB channel directly from the CB Chat
menu. It is suggested that you allow no more than 6 people on a
single channel, as conversation is hard to follow with more than
6. You may want to create some 2 person channels for private


Users (Max) Description

1] 3 (8) Test CB Channel

2] Add new CB Channel

3] Edit CB Channel

As a Sysop, you will see two additional options at the end of
your menu, add new CB channel and edit CB channel. To enter a
CB channel, type the number of the channel you wish to enter.
You will also be given information as to the number of users
currently active, and the maximum number of users allowed on
that CB channel.


1] Description: New CB Channel

2] Channel security level:

3] Maximum users: 7

4] Current users: 0

5] Handle allowed: No

6] Delete this channel

Option to change [quit]

Description - A brief description on the scheduled topic of the
CB channel. (Ex: Comdex)

Channel security level - The security level required to enter
the CB channel.

Maximum users - The maximum number of users allowed on the
channel at any one time.

Current users - The current number of users on the channel.

Handle allowed - If set to yes, the names that appear on the CB
channel will be the alias names rather than the person's actual
name, otherwise the user's actual name will appear.

Delete this channel - Remove the channel from the CB Chat menu


1] CB Chat: >=10

2] Add/edit CB channels: >=200

3] CB Path: CB\

Option to change [quit]

CB Chat - Security level to enter the CB chat system. If you
wish to turn off the CB chat system, set this security level to
one that is higher than that of your normal users.

Add/edit CB channels - The security level that is required to
add or edit the CB channel settings.

CB Path - The path used by TurBoard to store all the information
dealing with CB chat.

[21.0] QWK Off-line Reader Support

When trying to cut down time your users spend on-line, one of
the best ideas is to allow them to download and read their mail
at a later time, freeing their system time to do more important
things, such as use the NAPLPS system. TurBoard implements a
QWK off-line reader utility that is fully self sufficient. No
maintenance of this system is required by the Sysop. TurBoard
keeps up with what the user has and hasn't seen, provides a
method for controlling what they want to download in their QWK
packet and will even queue the file in their marked file list
for download. The internal TurBoard command to start the QWK
system is "QWK".


1] Bulletins: New 2] News: No

3] Welcome Screen: ANSI 4] Logoff Screen: ANSI

5] Archive default: ARC 6] Download Protocol: N

7] Maximum packet size: 50 8] Maximum msgs per
forum: 100

9] Forum Chooser 10] Forum Pointers

11] Make QWK file and mark it for download.

12] Make QWK file and download it now.

13] Upload replies packet.

Option to choose [quit]

Bulletins - Either set to none, all or new. This option tells
TurBoard which bulletins (from the Bulletin System, see above)
to include in the QWK packet. If set to "new", only those
bulletins that have been updated since the last login will be
included in the QWK packet.

News - Either set to yes or no. This option tells TurBoard to
include a file called "NEWS.TBO" from the YAK system directory.
If the file is not found by TurBoard, this option will do

Welcome Screen - Options include "ASCII", "ANSI" and "NAPLPS".
This tells TurBoard which version of the welcome screen to
include with the QWK packet. If NAPLPS is chosen, it is the
responsibility of the reader to display the NAPLPS frame
correctly. These screens come from the WELCOME.* files in the
TurBoard text directory.

Logoff Screen - Includes the same options as welcome screen.
TurBoard gets the information from the LOGOFF.* files in the
TurBoard text directory.

Archive default - Tells TurBoard to archive the QWK packet with
the specified archiver. The archivers must be set with the SE
archiver menu, and the QWK system can use any archiver that is
set by this menu.

Download Protocol - This is the same option that may be set by
the Y setting, given here for simplicity. This setting affects
the default protocol used by TurBoard when up and downloading.

Maximum packet size - The size, in kilobytes, that the user
wishes to limit the entire packet to. TurBoard will stop
including new messages to the QWK packet when this limit is
reached. Final packet size received from TurBoard may vary,
depending on the archiver used to compress the QWK packet.

Maximum msgs per forum - The maximum number of messages that the
user wishes to exist in any ONE forum. In the case where the
user has 700 unread messages in a particular forum, but only
wants to get the first 100 of them, this option may be set to
100 and TurBoard will stop processing that forum after the first
100 messages, and continue with the next forum.

Forum Chooser - Invokes the forum chooser menu. (see below)

Forum Pointers - Invokes the forum pointer menu. (see below)

Make QWK file and mark it for download - This option actually
begins the QWK download process in which TurBoard scans all the
forums and packs up messages accordingly. When TurBoard
finishes the QWK processing, it will mark the file for download.
The user must download the file with the D command.

Make QWK file and download it now - This option starts the QWK
processing and download process automatically.

Upload replies packet - Starts the upload process and
automatically types in the name of the upload packet for you.
The user may also upload a REP packet without this option and
TurBoard will automatically route the packet to the QWK
processor. This options is provided for convienence.



Enter forum to change [quit]

At the TurBoard prompt, you may enter as may names as you like
to toggle each forum on and off. Also, you do not have to type
the complete name to toggle a forum. For example: "> AD& BA"
will toggle both forums off. (This is the same as "SKIP"ping a
forum while reading it. TurBoard flags that forum as "off" to
the particular user that SKIPped it or turned it off with one of
the QWK menus.


AD&D] 82/82 BAD_MSGS] 19/19

Forum name to change [quit]

This menu performs roughly the same function as the forum
chooser menu, with the added functionality of being able to set
the message pointer in each forum. This is good if you want to
download an entire forum, but you have already read mail in it.
It also performs as a toggle, just as the chooser menu, to
turn on and off forums. (Same as the read "SKIP" command.)


1] QWK System: >=10

2] QWK System Name: TURBOARD

Option to change [quit]

QWK System - Security level required to enter the QWK system.
If you wish to turn off this system, set this level to one
higher than your normal users.

QWK System Name - The name that you want TurBoard to give to
your QWK packets. For example, if you set this option to
"WAFFLE", the QWK packets that TurBoard will use will be name
"WAFFLE.QWK" and the reply packets will be named "WAFFLE.REP".

[22.0] CD ROM Support


Add your CD with the SE option.

Use the cd command to make your cd active.

Add all CD directories with the AF command (and use your cd
drive and path for the directory drive and path) ex: File
directory name: 001A File directory path: D:\001A File
directory desc: Communications

Add extra directories with the ef command option 9 ex: extra
file directory: D:\001B

Examine your DIR* or FILES.BBS file and determine the column
positions for each file description and date, and length of date

Use the FF command on your CD file system.

Follow prompts.


1] Not available:

2] Not available:

3] Not available:

4] Not available:

5] Not available:

6] Not available:

7] Not available:

8] Not available:

[22.3] Which CD do you wish to alter [quit]

The CD ROM configuration menu is used to tell TurBoard of the
alternate file systems that you want to be available. It is not
required that you use this system for your CD ROM, in fact, you
could put all of the CD ROM files in your normal file system, if
you like. Since putting all of your CD ROM files on one system
might cause some confusion, you may use this system to keep your
CD ROM files separate from each other and the normal TurBoard
file system.

When adding a CD ROM by choosing one of the numbers above, you
will get questions like the ones below:

Enter new name for CD ROM []:

This is the name of your CD ROM and this will appear in the list
of available file systems.

Enter new CD drive [F]:

This is the DOS drive letter your CD ROM resides on.

Enter new CD ROM access requirements, currently: >=0

This is the security level that is required to access your CD
ROM or alternate file system.

Is this CD ROM currently available [no]?

This is a flag that either marks this CD ROM as available or
unavailable. You may use this if you have more than one CD ROM,
but only one CD ROM drive. [23.0] BILLING SETUP MENU

1] Initial download points: 1000

2] Bonus points for every 1 kilobyte uploaded: 20

3] Bonus points to uploader of file for every download: 2

4] Cost (in points) for every 1 kilobyte of download: 0

5] Limit download time to remaining time available: No

6] Upload time bonus multiplier: 0x upload time.

Option to change [quit]

Initial download points - The number of points that each user
starts out with in the point system. The value of these points
are determined by the settings below.

Bonus points for every 1 kilobyte uploaded - This is the number
of points each user gets for every 1 kilobyte of uploaded files.
For example, if this option is set to 20, and a user uploaded a
100 kilobyte file, the user would get 2000 points added to their
point bank.

Bonus points to uploader of file for every download - In
addition to the initial points for the upload, a further
incentive to upload useful files is to set this option to a high
number, and set the above option to a low number. If someone
downloads this file, the uploader will be awarded this number of

Cost (in points) for every 1 kilobyte of download - This is the
cost in points for every kilobyte downloaded. If the user
attempts to download a file of size 200 kilobytes, they would
need 200 x cost in points to download this file. If you wish to
disable the file point system, set this option to 0.

Limit download time to remaining time available - This option
tells TurBoard to limit the download time to the remaining time
available. Files that will take longer to download than the
user has left will be denied.

Upload time bonus multiplier - This option will give people who
upload files more time on the system.

[24.0] On-Line Books System

Some BBS programs refer to features similar to this one as
"continuous story" or "book writer". I had planned to include
an option for on-line databases, but due to the request of one
of the users of PC Chattanooga, I added support for a
"continuous story" as the initial implementation.

The idea here is to have entertaining, technical or whatever
kind of information available for users to access on-line (with
the option to download all or parts of the information).

In addition the users may add to the information as they feel

Options are planned for keyword searching, downloading,
uploading, etc. of the books.

To enter the book option, type the command: BO

From this point you will be able to enter/delete/add to books
and chapters of books. Each book may have an "Author"
associated with it. This is sort of like the Chairmen in the
message areas. Editors can control, add and delete the chapters
in their book.

Each book consists of multiple chapters. Each chapter is either
"open" or "locked". An open chapter allows users to append to
the end of it. For example, they may continue the current story
or add information to a technical document.

There may become a time when the Author decides that a chapter
is complete, and wishes to stop the extensions on it. The
chapter may be locked via the edit chapter option (after a
chapter is read). This will disallow further additions to the

PC Chattanooga! On-line Books

Name Description

There are no books to display.

1] Add new book.

Book number to read [quit]

Add new book - Choose this option to add a new book to the
on-line books.


1] Books: >=10

2] Add new book: >=100

3] Edit chapter: >=200

4] Add chapter: >=200

5] Path: BOOK\

Option to change [quit]

Books - The security level required to enter the book system.
If you wish to disable the book system, set this security level
to one higher than your normal users.

Add new book - Security level required to add a new book.

Edit chapter - Security level required to edit a chapter in a

Add chapter - Security level required to add a new chapter to a

Path - Path used by TurBoard to store all the information
relating to the book system.

[25.0] Bulletins System

It's a good idea to put important information for your users in
bulletins so they can refer back to the information as often as
they need to. Bulletins can be controlled solely in the
TurBoard environment. You never need to go outside the system
unless you wish to import data or text from another source.

Initially, TurBoard has no bulletins. If you wish to create
one, you will need to use the AB command. Once you issue the AB
command, you will be prompted for the description of the
Bulletin. This is the text that will appear in the main
bulletin menu.

Once you've entered the description, you will enter the editor
(either full screen or line, depending on your setup). Here is
where you will enter the actual bulletin text. If you are in
the full screen editor, you can enter colors with the Ctrl-W

After the bulletin is saved, you will be prompted for the
security level of persons with access to the bulletin, as well
as a read flag. This flag displays "No" or "Yes" depending if
the person has read the bulletin or not. (It does require some
file space, but only 1 bit per person, very small.)

For example, lets create a new bulletin via the AB command
entered at the TurBoard prompt:

> AB

Some there are some special files you can place in your bulletin
directory to add NAPLPS support that will override the normal
TurBoard displays. Using this technique, you can create a
customized bulletin display that will take full advantage of

If you wish to create your own bulletin menu in place of the
normal TurBoard created menu, create a file called BULL.NAP (for
NAPLPS), BULL.ANS (for ANSI) or BULL.ASC (for ASCII) and place
it in the DOS directory named BULL (or whatever directory was
set in the SE options; the directory is under the TurBoard root
directory). It is the System Operators responsibility that the
BULL file matches the information that TurBoard knows.

In addition, you can create specific emulation files for NAPLPS,
ANSI and ASCII. The name of the file is BUL[bulletin
number].[Emulation extension]. For example, if you wanted to
add a NAPLPS frame for bulletin number 3, the name of the file
would be BUL3.NAP.


1] Bulletins: >=0

2] Add bulletin: >=100

3] Delete bulletin: >=100

4] Edit bulletin: >=100

5] Bulletin path: BULL\

Option to change [quit]:

Bulletins - Security level required to display the bulletins.
If you wish to disable the bulletin menu, set this security
level to one that is higher than your normal users.

Add bulletin - Security level required to add a new bulletin
with the AB command.

Delete bulletin - Security level required to delete a bulletin
with the DB command.

Edit bulletin - Security level required to edit a bulletin with
the EB command.

Bulletin path - The path used by TurBoard to store all the
information dealing with the bulletins.

[26.0] Questionnaire System

This is a feature of TurBoard that allows the Sysop to question
users for just about anything. It can be used in conjunction
with YAK to set up a new user questionnaire, question someone on
their 5th call about what they do and don't like about the BBS
system, etc. You may also use the questionnaires to sell
software or just about anything. The questionnaire system
supports NAPLPS, and we will set up a demonstration in a
following example to show how YAK and the questionnaires can
work together.


First, choose the QU option to get to the questionnaire main
menu. Since we want to create a NEWUSER questionnaire, and not
a choice in the questionnaire menu, we will use the MOD command
and enter the NEWUSER name. We will now be looking at a blank
list of questionnaire entries (much like the YAK system). We
want to ADD a new question/operation to the questionnaire, so we
enter ADD and insert it as number 1. We then choose the record
type as 1, since we want it to be a question.

We are now presented with a full screen to enter our question.
Enter the first question that you want to ask your new users and
save the response. The maximum characters prompt will now
appear and we can type the maximum length that we want entered
to answer the question. The minimum length is the minimum
number of characters that the user must enter to continue past
the question.

The answer file indicator is the leading text to put in the
NEWUSER.ANS file for future readability. Continue in this
manner until all the questions have been entered.


If you are using the canned TurBoard yak file, you may wish to
back it up and erase all the files in the YAK subdirectory
before beginning this exercise.

In this section we will demonstrate how to use YAK and the
questionnaire system to create a BBS system with the specific
goal to turn a profit by providing downloadable shareware files
at a yearly or monthly fee. First, we have decided that we
wish to use the "hot" interface, as opposed to the standard
(default) TurBoard command line prompt. What this means is that
users will use "hot-keys" and "hot-spots" (with NAPLPS and a
mouse) to navigate the system, rather than entering the standard
commands at a command prompt.

The first step is to map out exactly how we want the system to
look. We do this best by getting out a pencil and paper (or
your favorite drawing program) and draw boxes. Here is a very
simple example and the one we are going to implement:

[YAK looks at its entries in order and takes the first one that
matches the set criteria.] (TurBoard always sets the MENU
variable to 0 at the beginning of each new user session.)

1] If this is the users first time on, make them fill out a
questionnaire (we'll call it NEWUSER).

2] Show them the new bulletins (only once, skip this entry
after it has been done once).

3] Give them the news (only once, like above).

4] If they are not paying customers, ask them if they would
like to register to use this system. If they answer YES, give
them the REG questionnaire, if NO, do nothing.

5] If the MENU variable is 0, display the main screen (i.e.
menu; either NAPLPS, ANSI or ASCII depending on the mode of the
user). If they choose F and they are paying registered users,
change the MENU variable to 1. If they choose G, log them off.

6] If the MENU variable is 1, display the Register User File
screen (NAPLPS, ANSI or ASCII depending on the mode of the

Now that we know how we want the system to respond, we begin
creating a YAK entry for each of our actions outlined above. We
ADD a new yak record (choosing the name to be COMMAND, since
this is a TurBoard command, and entering a description for it,
"New User Login Questionnaire", now we choose that record
(number 1) and begin changing some of the check values for that
record (options 4-7). We choose option 4 and we see the list of
Check Values and their meanings.

Since we want this to occur when it is the users first login, we
choose the check for "Number of times on is equal to checkvalue"
and we choose the Check Value to be 0, since this is the first
time the user has logged on. Now we change option 8, which is
the command to execute, to say "QU NEWUSER". This tells
TurBoard to execute the QU NEWUSER command when this is the
first login for a new user. Since we only want this to happen
once, we also change the Once flag (option 3) to TRUE. This
will tell TurBoard that once this operation has been performed,
do not perform it again.

We are done with that YAK entry, so we hit enter to go back to
the YAK list. The new bulletins command is entered in the same
way, except for the command (option 8) use "B NEW". To
display a text file, we create another YAK entry (make it number
3, since we want this to happen after the login questionnaire
and new bulletin check), but instead of choosing COMMAND as the
name of the text file, we give the YAK system the name of an
actual file to display. We choose NEWS as the name and enter,
giving the description "Login NEWS File."

Now we can choose the YAK entry we just created and modify it
further. We will choose Check 6 and check value 0 ("user has
security level greater than 0") as the conditions to do this
operation. "Once" should be true, since we only want this to
happen once. Whenever TurBoard displays a file, it uses the
simple rule that if the user is in NAPLPS mode, TurBoard will
attempt to display the filename with an "N" appended to the end
of the name. For ANSI mode, TurBoard will display the file with
a "G" appended to the end. Since we have chosen "NEWS" as the
name of the file to display, TurBoard will attempt to display
"NEWSN" if the user is in NAPLPS mode and "NEWSG" if the user is
in ANSI mode. If either of those files are not found, TurBoard
will default to the "NEWS" filename.

We need to check the check to [6: 0] and make sure "Once" is set
to TRUE, and we are done. Now, we don't have to create ANSI and
NAPLPS version of the NEWS file, but if you want complex ANSI
and NAPLPS graphics, it is recommended. We can use the TurBoard
editor to create straight text with colors. To edit the NEWS
(TurBoard Format) file, choose the Edit option in the YAK men
for the NEWS entry. Now we can use the normal TurBoard editor
to create and update the news file that will automatically be
formatted for screen size and emulation mode.


1] Questionnaire: >=10

2] Modify questionnaire: >=200

3] Questionnaire path: QUEST\

Option to change [quit]

Questionnaire - The security level required to enter the
questionnaire system. If you wish to disable the
questionnaires, set this security level to one that is higher
than that of your normal users.

Modify questionnaire - Security level required to modify the

Questionnaire path - Path used by TurBoard to store all the
information dealing with questionnaires. [27.0] USER SETUP MENU

1] EDIT file: >=200

2] TYPE file: >=200

3] View caller log: >=10

4] View detailed caller log: >=200

5] Edit users: >=200

6] New user security level: 10

7] New user keys:

8] User file path: USER\

Option to change [quit]

EDIT file - Security required to edit a file with the internal
TurBoard EDIT command.

TYPE file - Security required to display a file with the
internal TurBoard TYPE command.

View caller log - Security required to view the caller log with
the I command.

View detailed caller log - Security required to view the caller
details in the caller log with the I command.

Edit users - Security required to edit users by enter their
number for the user list.

New user security level - The security level given to new users.

New user keys - The security keys given to new users.

User file path - The path used by TurBoard to store all the
information dealing with user accounts.


1] Setup: >=200

2] YAK: >=200

3] Yak path: YAK\

4] Fido data path: FIDODATA\

5] Fido incoming path: FIDOIN\

6] Fidonet outgoing path: FIDOOUT\

7] Log path: LOG\

8] Text path: TEXT\

9] DOS shell interpreter: C:\DOS\COMMAND.COM

10] Quick-On auto password: On

11] Registered under name:

12] Registered under serial:

13] Front door processor type: .FLO file (BinkleyTerm(tm)-type)

Option to change [quit]

Setup - The security level required to enter the SE menus.

YAK - The security level required to edit YAK system (enter the
YAK command).

Yak path - The path used by TurBoard to store all the
information dealing with YAK.

Fido data path - The path used by TurBoard to store the
information about FidoNet. This is generally where the FidoNet
nodelist and nodelist compiler are kept.

Fido incoming path - The path used by TurBoard to receive new
mail from the FidoNet style networks. This is where the
incoming *.PKT and *.DD# files will be placed so that TBFIDO.EXE
will see them and unpack them.

Fidonet outgoing path - The path used by TurBoard to place
outgoing mail for FidoNet. This is where TurBoard places the
*.FLO (in the case of BinkleyTerm type outbound mail) and the
*.PKT, *.DD#, etc. and should also be used as the outgoing mail
area of the front door program. (In the case of Front Door,
TurBoard also creates *.MSG files, see option below.)

Log path - The path used by TurBoard to store all the caller log

Text path - The path used by TurBoard to store the text file
information. This includes the WELCOME.*, LOGOFF.* and *.HLP
files used by the TurBoard system.

DOS shell interpreter - This is the path and filename of the DOS
shell interpreter that TurBoard is to use when shelling to DOS
(via the Alt-D command).

Quick-On auto password - This tells TurBoard whether or not to
require a password when the Alt-Q (quick logon) key is entered
from the call waiting screen.

Registered under name - To register your copy, you will need to
get your registered name and serial from an authorized TurBoard
dealer or Software @ Work directly. This is where you place
your registered name.

Registered under serial - This is where registered users place
their serial that will activate the registered functions of

Front door processor type - TurBoard can handle both the *.FLO
type and *.MSG type of front door program. Please see your
front door manual for more information on which type your
program requires.

[29.0] Art Gallery System

Version 0.40 and above are equipped with an Art Gallery. This
is a method for displaying ANSI ASCII and NAPLPS frames as works
of art or to demonstrate a terminal emulation like NAPLPS.

In order to add a work of art, use the AA (for Add Art) command.
To edit the information used to display a work of art, use the
EA (Edit Art) command. And to display works of art use the A
(Art Gallery) command.

There is an added command called DEMO. This will rotate between
works of art with a specified period of time. The rotation will
include all the works of art regardless of current terminal


1] TEST (ANSI) test

Number to choose [quit]

The art gallery menu consists of a list of art files followed by
the type of file (NAPLPS or ANSI) followed by a description. If
the user is in the wrong mode, TurBoard will automatically
change the users mode to the correct mode just before displaying
the file.

As throughout TurBoard, the extensions for the art pictures
should adhere to the file naming conventions that TurBoard uses.
For example: the TEST entry above should be named TEST.ANS for
ANSI and TEST.NAP for NAPLPS. The files should be placed in the
Art Gallery directory specified in the SE setup. (Defaults to


Name: TEST

1] Description: test

2] ANSI: Allowed

3] NAPLPS: Not allowed

4] Security: >=0

5] Delete this entry

Description - The description of this art frame.

ANSI - Either ALLOWED or NOT ALLOWED. If this is an ANSI art
frame, this option should be set for allowed.

NAPLPS - Either ALLOWED or NOT ALLOWED. If this is a NAPLPS art
frame, this option should be set for allowed. In the case where
you have two versions of the art frame (both a ANSI and NAPLPS),
both of these options should be set to allowed.

Security - Security level required to view this art picture.

Delete this entry - If you wish to remove the entry from the
list, choose this option. (This does not delete the art file.)


1] Art Gallery: >=10

2] Edit art gallery: >=200

3] Art gallery path: ART\

Option to change [quit]

Art Gallery - Security level required to enter the art gallery.
If you wish to disable the art gallery, set this security level
to one that is higher than that of your normal users.

Edit art gallery - Security level to add, edit or delete art
gallery entries with the EA or AA command.

Art gallery path - The path used by TurBoard to store all of the
art gallery information. [30.0] YAK System

Version 1.00 of the YAK system is different from previous YAK
versions inseveral respects. This section attempts to cover
them in enough detail to enlighten TurBoard sysops on how to use
them. Your YAK system is designed to give the Sysop control
over the way the BBS performs. This includes checking for new
bulletins, displaying menus, asking questions of new users,
asking if a user wants to performs a certain function like
downloading a file, automatically invoking a questionnaire or
door program, etc.

Also, when using TurBoard NAPLPS mouse support, the YAK system
is used to create hotspot menus or hotkey menus, depending on
your personal preference. A hotkey menu refers to a menu that
accepts one-key input and will perform a sysop defined function
when that key is hit. A hotspot menu refers to a menu that
accepts mouse point and click input and will perform a sysop
defined function when type spot is selected.

A YAK entry will contain some information: should this YAK
entry execute a TurBoard command or display a file? What are
the conditions under which the command will execute or the file
be displayed? Should it happen only once or multiple times?

To start the YAK subsystem, type "YAK" at the TurBoard prompt.

To use YAK requires that you understand what you want to happen.
For instance, if the first thing the user sees is the logon
news, the NEWS information should come first in the list of YAK
items. YAK takes the list and tries to perform each from top to
bottom. If it cannot perform the first, it moves on to the

YAK supports 4 different checks at a time. These are the
criteria that must be met before a message (text file) is sent
to the user or a YAK command is executed. For example, the main
menu could be the only item in your YAK list and it might use
only 1 check value (number 9).

Whenever TurBoard is finished processing, it checks the YAK
List, it goes through each item in the list to see if that item
meets all the criteria. If so, TurBoard displays the file
associated with that entry or executes the command associated
with that entry.

Say, for example, you want the BBS to ask a user if they want to
read their mail now, if they have mail waiting. This can be
done with the YAK subsystem as follows:

Make a new YAK entry:

[30.1] Yak Entry Settings


2] Desc: Ask if user wants to read their new mail.

3] Once: True

4] Check: User has new mail. (check 1)

5] Check:

6] Check:

7] Check:

8] Enter (no action):

9] Frame type: Command Menu

10] Edit YAK\MAILNOW.TBO file (TurBoard format file).

11] Edit hotkey/command/hotspot meanings.

12] Delete this record.

Choose number to change [quit]

Use option 10 to edit the TurBoard format file. It should read:

You have new mail waiting, do you wish to read it now?

You will need to set the command for this menu so that TurBoard
will understand a Y or YES or N or NO (option 11).

PC Chattanooga! YAK\MAINMENU Hotkey/Command/Hotspot List

Hotkey Command Action H Security

Y P >=0

YES P >=0

N Q >=0

NO Q >=0

Number to change or delete, ADD to add new entry [quit]

As you can see, if the user enters a Y or YES, you want TurBoard
to convert that into a P command, where a N or NO should
translate to a Q command, or you could even leave the action
blank for those entries. We do need to include them or TurBoard
will execute a N)ew files command when the user typed N.


A command entry might have the following settings:

TurBoard BBS Yak Entry Settings

1] Fname: COMMAND <= Indicates a TurBoard Command to take

2] Desc: Check for new bulletins first when user loggs on.

3] Once: True <= Should only happen once.

4] Check: If users security level is greater than 0. <=
Conditions under which it should happen.

5] Check:

6] Check:

7] Check:

8] Command: new b <= The command that should take place

9] Delete this record.

Choose number to change [quit]

A display file YAK entry might have the following settings:

PC Chattanooga! Yak Entry Settings

1] Fname: YAK\MAINMENU <= The name of the file to be
displayed (see below)

2] Desc: Display the main menu

3] Once: False <= Can happen more than one time.

4] Check: If expert mode is off. <= Conditions under which
file should be displayed

5] Check:

6] Check:

7] Check:

8] Enter (no action):

9] Frame type: Command Menu <= Type of file menu

10] Edit YAK\MAINMENU.TBO file (TurBoard format file). <= To
edit the .TBO version (see below)

11] Edit hotkey/command/hotspot meanings. <= To set up special

12] Delete this record.

Choose number to change [quit]

Seen in their YAK list the above might look something like this:

PC Chattanooga! Yak List

File Description

1] COMMAND Show new bulletins

2] YAK\MAINMENU Display the main menu

Number to change or delete, ADD to add new entry [quit]


1 Mail>X OK if user has mail waiting.

2 Logons>X OK if user has called more than X times

3 Logons=X OK if user has called exactly X times

4 Logons
5 LastOn
6 SecLvl>X OK if security level > X

7 SecLvl=X OK if security level = X

8 SecLvl
9 expert mod OK if expert mode is turned off

10 ANSI OK if ANSI mode is on

11 NAPLPS OK if NAPLPS mode is on

12 NONE OK if not in ANSI or NAPLPS mode (ASCII Mode)

13 ANSI/ASCII OK if either ANSI or ASCII mode

14 Birthday OK if today is user's birthday

15 Random OK if CheckValue is > random number between 1
and 100.

16 MENU=X OK if MENU YAK varialbe is equal to the check value.

In case 5, the X value is an internal TurBoard (DOS, actually)
format. To use the integer for exactly the point in time you
are entering the information, use the NOW keyword. This will
insert the DOS date/time stamp for that point in time.


Now, to add multiple menus, YAK accomplishes this with a MENU
variable, which is an internal YAK variable from 0 to 35000.
TurBoard initially sets this to 0, and it can be changed at any
time with the TurBoard MENU command by typing "MENU ##" where ##
is the number. (ex: MENU 1) There is also a YAK check that
looks at the value of this variable and will return TRUE or
FALSE depending on its value (MENU = )

This MENU value is used to create the sense of "moving" through
the system while you are actually remaining at the same prompt.

For example:

Menu 0: Frame showing choice between hotkey menus and command

Menu 1: Top menu for hotkey menus.

Menu 2: Hotkey menu showing all the message functions.

Menu 3: etc...

TurBoard always initializes the MENU variable to 0 whenever a
new caller logs on. To access this, YAK has a new check (16)
that will compare the value of the menu variable to the check
value in the YAK check record and pass true if they match.

There is a new command in TurBoard called MENU that
assigns a value via the command line to the internal menu

This is how TurBoard changes hotkey menus to give the user the
appearance of different menus and menu levels. Taking the above
example we could have a YAK record for the Menu 0 frame (choice
between hotkey menus and command prompt) that looks something
like this:

Name: HOTCHOIC Check: 16 (0) <= This is a check saying that
the menu variable is zero, so Lets display
this yak file.

Menu type: Hotkey

The hotkey and hotspot settings should be set to allow input
corresponding to what your frame says. For example, you may set
up C to issue the command "MENU 35000" and M to issue the
command "MENU 1".

"C" would set the internal menu variable to the value 35000.

"M" would set the internal menu variable to the value 1, which
would then be picked up by a YAK record with check 16 checkvalue

Should you decide to perform one of the TurBoard functions with
a hotkey or hotspot simply put the normal command line command
as that command.

For example, if you have a menu with options to go to the art
gallery or door menu, as A and D respectively, set the command
for A as "A" and the command for D as "DO".

To set hotspots on a TurBoard frame, use the mouse to actually
set the spots, and where they reside. Choose the set hotspot
option from you YAK settings menu (you must have the menu type
as "Hotkey") and then choose the set hotspot option. You will
be prompted to click on the upper left then the lower right
corner of the NAPLPS "hot spot" for that command.

All your hot spots must be manually entered in this fashion, and
keep in mind that hot-spots are only for NAPLPS frames, in ANSI
or ASCII mode, mouse pointer clicks return the actual character
to the command line or hotkey menu.


Hot menus are those that accept keyboard or mouse input (in the
case of NAPLPS). You can get very creative in how you design
your menus. To change a menu from the standard command line
input to hot, choose the YAK option labeled "Type" (#11) from
"Command" to "Hot". You will notice a new option will appear,
#14, Edit hotkey meanings.

Choose that option and start ADDing keystrokes and their
appropriate action. To assign keystrokes to change menus, use
the MENU ### command to reassign the MENU variable to a new
value (###), so that YAK will display the appropriate menu.
(Use check #16 to check the MENU value.)

If you want to add NAPLPS hotspots for use with a mouse, change
your current mode to NAPLPS, get in the YAK option to set the
hotkeys, and start setting "hot-blocks" for each keystroke.
This way, a mouse can be used to click on an area of the screen
to perform an action. [31.0] Customizing Your Displayed Screens

The following files can be placed in their respective directory
and override

the TurBoard "system" display for the given function.

Special Files:

TEXT/ WELCOME.* Logon Screen

LOGOFF.* Logoff Screen

NEWUSER.* Screen new users must agree to when first logging on.

DOORMENU.* (optional) Replaces TurBoard system menu for doors.

MAILMENU.* (optional) Replaces TurBoard system menu for forums.

ADSMENU.* (optional) Replaces TurBoard system menu for
classified ads.

BOOKMENU.* (optional) Replaces TurBoard system menu for on-line

BBSMENU.* (optional) Replaces TurBoard system menu for BBS List.

FILEMENU.* (optional) Replaces TurBoard system menu for file

ARTMENU.* (optional) Replaces TurBoard system menu for art

FILE/ ALL.TBO Description shown when "F ALL" is executed.

NEW.TBO Description when when "N" is executed.

UPLOAD Shown when "U" command is executed.

DOWNLOAD Shown when "D" command is executed.

Shown when "F " is executed.

Shown when "F " is executed. area> = dir

FILE/CDx/ - Same files as above for CD directory. (x =

FILE/CDx/FILEMENU.* (optional) Replaces the TurBoard system
menu for CD file directories.


A fairly recent addition to TurBoard is the support to
completely customize your File Directory screen as well as the
Forum Directory screen. (I'm sure not everyone likes the way I
like to display the information!)

Here are the files you can alter, their format and their

(All of these files should be in your "TEXT" TurBoard
subdirectory. Also, none of these files have extensions [that
stuff after the .])

WELCOME.* - This is the initial logon screen that is displayed
just after the "Do you want to use ANSI terminal emulation? "
question. It is the initial screen that TurBoard displays and
is generally a welcome banner or system identification screen of
some sort.

LOGOFF.* - These are the logoff screens that your system will
display when the user issues the G command, just before they are
disconnected. This screen is optional, if it is not found,
TurBoard will simply put "Thank you for calling ... connection
terminating ...". You can also change that with the AL command
(see section on Language File).

NEWUSER.* - This is the information that TurBoard displays
when a user logs on for the first time. Just before the normal
questions are asked to complete the on-line information, the
user is asked, "Do you agree with the above conditions? ".
This file will outline those conditions you want to place. This
would also be a good place for a legal disclaimer, which I
highly suggest.

FILEMENU.* (or DIR.*) - These files are completely optional.
In fact they are not included in the TurBoard distribution ZIP.
These were included so that you may add your own personality to
your File Directory listing. When one of these files is placed
in the TEXT subdirectory, it overrides TurBoards internal File
Directory screen.

(A quick side note: I find it useful to create a dummy user
name that I log onto with to see what the system looks like to
the end user, I find it very helpful. Just pick a name and log
on, you may even want to enter a message to yourself.)

MAILMENU.* - This overides the TurBoard automatic forum menu.
If you wish to customize your forum menus with graphics or ANSI
text, you can use this file to accomplish that.

[32.0] DAILY.BAT (The Daily Batch Event)

Many game doors require that you run a maintenance utility once
per day. DAILY.BAT is TurBoards way of accomplishing this.
After midnight, at the first idle moment, TurBoard executes this
.BAT file. It is the Sysop's responsibility to include the
commands to run their particular application.

DAILY.BAT comes pre-configured to automatically pack all the
message forums with the TBFIDO.EXE program. (Using the -P pack
mail switch.) This takes responsibility away from the Sysop to
maintain the message forums. You may also with to run other
programs such as a bulletin generator.

Nothing besides the file itself is required to run DAILY.BAT.
(TurBoard must have been started with TB.BAT or TBFN.BAT). [33.0] File Naming Conventions

Use the following extensions for the associated files:

*.NAP - NAPLPS frame

*.RIP - RIPSCRIP frame

*.ANS - ANSI frame

*.ASC - ASCII frame

*.TBO - TurBoard format file, editable with "EDIT filename>.TBO"






























\ [34.0] Color Codes

Turboard uses single ASCII characters to indicate different
colors, you can take advantage of this in the editor and input

In NAPLPS mode, TurBoard assigns the following colors to the
internal TurBoard format for cross-compatibility.


Black 128

Blue 129

Green 130

Cyan 131

Red 132

Magneta 133

Brown 134

LightGray 135

DarkGray 136

LightBlue 137

LightGreen 138

LightCyan 139

LightRed 140

LightMagneta 141

Yellow 142

White 143


Black 144

Blue 145

Green 146

Cyan 147

Red 148

Magneta 149

Brown 150

LightGray 151


Attributes Off 152

Underscore 153

Blink On 154

Invisible 155

Clear Screen 12

Line Feed (Automatically added by TurBoard.)

End of Parag. 13

To enter these numbers in manually on a line (the file directory
description prompt, for example), use the alt key. While
holding down the ALT key, type the 3 digit number on the numeric
keypad and then release the ALT key. At that point the color of
the text you type will change. TurBoard treats this character
as a full character, so if you make a mistake, be sure to
backspace as far as you can go before trying again. [35.0] YAK Codes

%A - User's Handle

%B - User's Name

%C - User's First Name

%D - User's Last Name

%E - User's Phone Number

%F - User's Street Address

%G - User's City, ST zip

%I - User's SL Name

%K - User's last call date

%L - User's total number of calls

%M - Move cursor to the middle of the screen

%N - User's number of files downloaded.

%O - User's number of files uploaded.

%P - User's kilobytes downloaded

%Q - User's kilobytes uploaded

%R - User's number of messages entered.

%S - User's number of messages read.

%U - User's number of file points.

%V - User's time left

%W - Current message area

%0 - Current Node number

%3 - Either a line feed or clear screen depending on Y settings.

%7 - Clear Screen

%~ - System caller Number

%a - date

%b - time

%c - BBS Name

%d - Sysop Name

%h - baud rate

%i - time left in minutes

%s - Specific[1]

%n - Current node path (ex: NODE1\ )

%t - temp string

%"<>" - Special: Display file enclosed in quotes (file must
exist in the TEXT directory). ex: %"welcome"

%l - number of messages (mail)

%m - minutes on today

%o - port baud rate

%p - port number these can be used for door command lines

The above variables are active when creating the door paths, etc. [36.0] Full Screen Editor

The full screen editor work with WordStar commands. If you are
logging on remotely be sure to use doorway mode to get maximum
function from your keyboard. F1 or Ctrl-H for additional help.

Colors are stored in TurBoard format (see colors above) but in
the full screen editor do not take up a character of space.

[37.0] Line Editor

The line editor in TurBoard works as most BBS line editors.
Wordwrapping is automatic, and when you are finished editing,
hit return on a blank line.

You will be prompted to Continue, Abort, Quote or Save. If you
are replying to a message, you may quote by choosing line number
in the message you want to quote.

Colors are not supported in the Line editor. (Quoting will
still have the highlighted ">".)

[38.0] On-line Help System

TurBoard provides an easy method for the user to get online
help. The user simply needs to type ? at any prompt and
TurBoard will display text dealing with that portion of the BBS

[39.0] TurBoard Terminal Emulation

TurBoard has a built in NAPLPS terminal emulation mode, so that
busy Sysop's don't have to take their board down to call another
BBS system. From the call waiting screen, type Alt-T, this will
start TurBoard's built-in terminal emulation mode.

There are several keys you should be aware of in TurBoard's
terminal emulation mode. They are Alt-X to exit back to the
call waiting screen, Alt-C will put your terminal in ANSI mode
and clear the screen, PgUp will start a ZModem upload, PgDn will
begin a ZModem Download.

All the NAPLPS functions that are available in the normal
TurBoard BBS System are available in the terminal mode of
TurBoard. Plans for terminal emulation mode is use of the
on-line BBS list for a dialing directory. If you have any
suggestions for improving the Terminal Mode of TurBoard, please
let me know! [40.0] Language File

One of the more powerful features of TurBoard is the online
customization of the entire output of the system. With the
language file, you can change practically every message that
TurBoard sends to the user. This is useful in customizing your
text for another language or for a particular speech style.

To see the online codes use the command "AL ON". You will
notice many numbers appearing before the messages on the screen.
Use "AL OFF" to turn off these codes. These numbers are the
language file entry number that you may customize with the "AL
###" command, where ### is the language entry number you wish to

For example, if you wish to customize the main command prompt
used by TurBoard, issue the command, "AL 27". (The main command
prompt is the 27th entry in the language file.) Use the editor
to change the actual prompt. You may use any of the YAK %
control codes in the language file entries.

When you are editing the language entrys, you will be using the
full screen editor that is built into TurBoard. This gives you
the editing features of the message forums. In addition to
normal text, you may use the YAK codes to change the output
dynamically, and even use the %"" text file yak setting to
display special graphics or text files.

The TurBoard language file is TURBOARD.LNG found in the main
TurBoard directory. If you get may "Language entry ## not
defined," chances are you are missing this file. [41.0] Registered TurBoard BBS's

Due to the many additions and subtractions that occur with BBS
lists, the official TurBoard BBS list will be maintained on PC
Atlanta! BBS. A current list will be included seperately with
the registered documentation.

[42.0] TurBoard Support Sites

United States Support Site

Software @ Work

P.O. Box 566491

Atlanta, GA 31156 USA

404/395-6525 (voice Mon-Fri 9:00am-6:00pm)

404/395-6326 (2400)

404/395-6327 (14400, HST)

FidoNet: 1:133/904

Canadian Support Site

Hi-Rez BBS

Warren Zatwarniski

Yorkton, Sask., Canada

306/782-6820 (14400)

FidoNet: 1:140/111


TURBOARD Shawn Rhoads (1:133/[email protected])

Support forum for TurBoard Sysops.

NAPLPS Shawn Rhoads (1:133/[email protected])

Help with NAPLPS graphics questions and utilities.

BBS_GRAPHICS Shawn Rhoads (1:133/[email protected])

Discussion of all BBS Graphics Formats, pros/cons, etc.

(If you have an echo dedicated to TurBoard or BBS Graphics
On-line, let us know and we will list it here.)

Once you've registered TurBoard, you are entitled to free phone
support at 404/395-6525 (Mon-Fri 9:00am - 6:00pm). And
remember, if you have a suggestion or new idea, please give us a
call or leave a message because we want to make TurBoard the best