PCBoard is a registered trademark of Clark Development Company,
Inc. All other brand and product names mentioned in this manual
are trademarks or registered trademarks of their respective
companies.
































Version 14.5
Clark Development Company, Inc. 1990
All Rights Reserved

Printed in U.S.A.

Clark Development Company, Inc.
6000 S. Fashion Blvd. Suite 101
Murray, UT 84107 U.S.A.
Telephone: (801) 261-1686
Fax: (801) 261-8987
Data: (801) 261-8976




Table of Contents


Introduction
What Is A Bulletin Board System? . . . . . . . . . . . . . 6
General PCBoard Requirements . . . . . . . . . . . . . . . 6
Internal vs. External Use . . . . . . . . . . . . . . . . 6
Installation . . . . . . . . . . . . . . . . . . . . . . . 8
Manual Upgrade Procedures . . . . . . . . . . . . . . . . 9
PCBoard Structure . . . . . . . . . . . . . . . . . . . . 11
Call Waiting Screen . . . . . . . . . . . . . . . . . . . 12
Command Line Parameters . . . . . . . . . . . . . . . . . 16
PCBoard Environment Switches . . . . . . . . . . . . . . . 19

PCBSetup
General Information . . . . . . . . . . . . . . . . . . . 23
PreSetup Suggestions . . . . . . . . . . . . . . . . . . . 24
SysOp Information . . . . . . . . . . . . . . . . . . . . 25
File Locations 1 . . . . . . . . . . . . . . . . . . . . . 30
File Locations 2 . . . . . . . . . . . . . . . . . . . . . 35
MODEM Configuration . . . . . . . . . . . . . . . . . . . 38
Node/Event/Subscription . . . . . . . . . . . . . . . . . 43
Options #1 . . . . . . . . . . . . . . . . . . . . . . . . 47
Options #2 . . . . . . . . . . . . . . . . . . . . . . . . 54
Option #3 . . . . . . . . . . . . . . . . . . . . . . . . 56
User Security Level . . . . . . . . . . . . . . . . . . . 59
Main Board Configuration . . . . . . . . . . . . . . . . . 60
Conference Configuration . . . . . . . . . . . . . . . . . 66
Command Line Parameters . . . . . . . . . . . . . . . . . 74

PCBSetup - Editing Files
File Locations 1 & 2 . . . . . . . . . . . . . . . . . . . 76
Main Board Configuration and Conference . . . . . . . . . 86

PCBoard - SysOp Menu Commands
(1) View/Print/Delete Caller's Log . . . . . . . . . . . 101
(2) View/Print User's List . . . . . . . . . . . . . . . 102
(3) Pack/Renumber Messages . . . . . . . . . . . . . . . 102
(4) Recover A Killed Message . . . . . . . . . . . . . . 103
(5) List Message Headers . . . . . . . . . . . . . . . . 104
(6) View Any File On Screen . . . . . . . . . . . . . . . 105
(7) User Maintenance . . . . . . . . . . . . . . . . . . 105
(8) Pack User's File . . . . . . . . . . . . . . . . . . 106
(9) Exit To DOS (Remote) . . . . . . . . . . . . . . . . 107
(10) Perform DOS Function . . . . . . . . . . . . . . . . 107
(11) View Other Node Users . . . . . . . . . . . . . . . 108
(12) Logoff Alternate Node . . . . . . . . . . . . . . . 108
(13) View Alternate Node Caller Log . . . . . . . . . . . 108
(14) Drop Alternate Node To DOS . . . . . . . . . . . . . 109
General Information . . . . . . . . . . . . . . . . . . . 110
Boolean Text Searches . . . . . . . . . . . . . . . . . . 110

PCBoard - User Commands
User Commands . . . . . . . . . . . . . . . . . . . . . . 111
General Information . . . . . . . . . . . . . . . . . . . 138

PCBSysMgr
User File Maintenance . . . . . . . . . . . . . . . . . . 139
User Info File Maintenance . . . . . . . . . . . . . . . . 150
System Configuration Analysis . . . . . . . . . . . . . . 153




Printer Port Definition . . . . . . . . . . . . . . . . . 153
Text/Graphic Editor Definition . . . . . . . . . . . . . . 154
Color Customization . . . . . . . . . . . . . . . . . . . 154
Command Line Parameters . . . . . . . . . . . . . . . . . 155
General Information . . . . . . . . . . . . . . . . . . . 161

PCBFiler
Novice vs. Expert Modes . . . . . . . . . . . . . . . . . 161
DIR & Download Relationship . . . . . . . . . . . . . . . 162
Edit DIR Files . . . . . . . . . . . . . . . . . . . . . . 163
Sort All DIR Files . . . . . . . . . . . . . . . . . . . . 169
Create Files List . . . . . . . . . . . . . . . . . . . . 169
Scan For Duplicate/Missing Files . . . . . . . . . . . . . 169
Locate File Spec On Disk . . . . . . . . . . . . . . . . . 170
Locate File Spec In DIR Files . . . . . . . . . . . . . . 170
PCBFiler Defaults Page 1 . . . . . . . . . . . . . . . . . 171
PCBFiler Defaults Page 2 . . . . . . . . . . . . . . . . . 173
Customize DIR File Colors . . . . . . . . . . . . . . . . 175
Command Line Parameters . . . . . . . . . . . . . . . . . 175
General Information . . . . . . . . . . . . . . . . . . . 176

PCBMoni
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Command Line Parameters . . . . . . . . . . . . . . . . . 178
General Information . . . . . . . . . . . . . . . . . . . 179

PCBModem
Command Line Parameters . . . . . . . . . . . . . . . . . 181

PCBoard Utility Programs
Making 14.5 Text (Multiple Languages) . . . . . . . . . . 183
PCB145 (and BOARD.BAT) . . . . . . . . . . . . . . . . . . 185
PCBCMPRS.BAT . . . . . . . . . . . . . . . . . . . . . . . 187
PCBCopy . . . . . . . . . . . . . . . . . . . . . . . . . 187
PCBDiag . . . . . . . . . . . . . . . . . . . . . . . . . 187
PCBDisk . . . . . . . . . . . . . . . . . . . . . . . . . 188
PCBNum . . . . . . . . . . . . . . . . . . . . . . . . . . 188
PCBPack . . . . . . . . . . . . . . . . . . . . . . . . . 188
PCBSTATS . . . . . . . . . . . . . . . . . . . . . . . . . 194
PCBTEST.BAT . . . . . . . . . . . . . . . . . . . . . . . 196
PCBVIEW.BAT . . . . . . . . . . . . . . . . . . . . . . . 196
Reading a PCBTEXT file . . . . . . . . . . . . . . . . . . 197
TESTFILE . . . . . . . . . . . . . . . . . . . . . . . . . 197
ViewZip . . . . . . . . . . . . . . . . . . . . . . . . . 197

Network Operations
Hardware Requirements . . . . . . . . . . . . . . . . . . 198
Monitors . . . . . . . . . . . . . . . . . . . . . . . . . 198
Network Software . . . . . . . . . . . . . . . . . . . . . 198
Multitasking Software . . . . . . . . . . . . . . . . . . 198
SHARE.EXE and Networks . . . . . . . . . . . . . . . . . . 200
File Server Configurations . . . . . . . . . . . . . . . . 201
Node Configurations . . . . . . . . . . . . . . . . . . . 202
Setting Up a Multinode PCBoard System . . . . . . . . . . 203
Example Network Setup . . . . . . . . . . . . . . . . . . 205

Advanced Techniques
Conference Registration & Security Levels . . . . . . . . 206
Disk Caching & RAM Disks . . . . . . . . . . . . . . . . . 207
ESC Codes in Messages . . . . . . . . . . . . . . . . . . 209




Event Activities . . . . . . . . . . . . . . . . . . . . . 210
File Naming Conventions . . . . . . . . . . . . . . . . . 211
Multitasking Operations . . . . . . . . . . . . . . . . . 215
Remote Activities . . . . . . . . . . . . . . . . . . . . 217
VROOM Overlay . . . . . . . . . . . . . . . . . . . . . . 218
I. ESC CODES . . . . . . . . . . . . . . . . . . . . . . 220
II. SysOp Functions . . . . . . . . . . . . . . . . . . . 222
III. ASCII Codes . . . . . . . . . . . . . . . . . . . . . 224
IV. File Formats . . . . . . . . . . . . . . . . . . . . 226
V. Transfer Protocols . . . . . . . . . . . . . . . . . 241
VI. Packet Switch Network . . . . . . . . . . . . . . . . 246
VII. @ Variables . . . . . . . . . . . . . . . . . . . . 248
VIII. @X Color Codes . . . . . . . . . . . . . . . . . . . 250


Glossary . . . . . . . . . . . . . . . . . . . . . . . . . 251




Introduction
------------

What Is A Bulletin Board System?
--------------------------------
A Bulletin Board System or BBS gives users an opportunity to
exchange information over great distances. Certainly, this can be
easily achieved by nearly any Postal Service, but PCBoard makes it
even easier. Information is transmitted over phone lines to
anywhere in the world where another BBS exists. Originally, BBS's
transmitted few messages with little accuracy. Today, however,
BBS's are used in offices, homes, schools, and governments. They
transfer computerized files to and from any location; deliver
messages in a matter of minutes, perhaps seconds; and maintain
security for organizations that handle sensitive information. They
represent a new technology born of a new communication age.


General PCBoard Requirements
----------------------------
PCBoard 14.5 has been written in ASSEMBLY language and "C" to
expedite software functions. Following is a general list of
requirements:

DOS 3.1 (or higher) or 100% Compatible Environment
8088 Computer or Higher (286, 386 etc.)
1.5 Megabytes or Greater of Hard Disk Space
320 Kilobytes of Free Memory

PCBoard is not limited to these features, however. To extend the
line support of one computer, the SysOp may use slave cards or
multitasking software (discussed later).


Internal vs. External Use
-------------------------
Internal. PCBoard can be used within the office to share files,
send and receive messages and memorandums, build conferences for
select individuals, and maintain security specific information.
PCBoard can replace rows of filing cabinets, heaps of manilla
folders, and rolls of sticky labels. Normally, in house
communication is accomplished by physically linking computers in a
network. Common network software includes LANtastic, Novell, and
3COM. Of course, PCBoard need not use a network. Instead, it may
run in a stand alone or multitasking environment.

External. Many times, PCBoard is extended beyond the office to
permit communication between computers several hundred or thousand
miles apart. The computers become linked via MODEM. A MODEM
(MOdulator-DEModulator) converts data into computer signals that can
be sent by telephone lines to any computer with another MODEM. By
this method,PCBoard supports the same features as an in house
system.






6




When supplied with multi-tasking software or slave cards, each
computer may utilize more than one phone line. As a result, one
computer may receive two or more different callers and each caller
would operate a different session of PCBoard. There are limitations
however. Since each phone line requires its own Communication Port
and Interrupt, configuring more than two lines on one machine is
difficult (See Multitasking and Slave Card Operation).




















































7




Installation
============


General Information
-------------------
A SysOp can install PCBoard from floppy disks or a hard drive or
network. Furthermore, a conversion process has been added to
PCBoard to facilitate more expeditious upgrades from previous
versions of PCBoard.


Floppy Disk to Hard Drive Installation
--------------------------------------
A SysOp should use the following procedures to install or upgrade
PCBoard. During an upgrade, the INSTALL program will only copy
files necessary for the upgrade. All others will remain untouched.
Additionally, the following installation procedures will commence
from the PCBoard Distribution Disks to a chosen hard drive.

1. Insert the PCBoard Distribution Disk #1 in drive A:.

2. Change to the root directory of the hard drive on which
PCBoard will be installed.

3. Type A:INSTALL at the DOS prompt.

4. Follow the instructions displayed on the monitor.


Hard Disk or Network Installation
---------------------------------
A SysOp should use the following procedures to install or upgrade
PCBoard from a hard disk or network. During an upgrade, the INSTALL
program will only copy files necessary for the upgrade. All others
will remain untouched.

1. Make a subdirectory on the hard disk or network drive.

2. Copy files from the PCBoard Distribution Disks to that
subdirectory.

3. Change to the root directory of the hard drive on which
PCBoard will be installed.

4. Type INSTALL at the DOS prompt.

5. Follow the instructions displayed on the monitor.











8




Manual Upgrade Procedures


General Information
-------------------
Instead of using PCBoard's automated upgrade procedures, a SysOp may
want to upgrade previous PCBoard versions manually.


Manual Upgrade Instructions
---------------------------
The SysOp can follow the instructions below to upgrade versions
14.0, 14.1, and 14.2.



1. Run BOARD.BAT once to start PCBoard. Once inside the
PCBoard environment, immediately exit. This simple
process enables PCBSetup to determine past configurations
such as SET PCB= statements.

2. Run PCBSetup. The utility will recognize the pre-14.5
PCBOARD.DAT file and ask to convert it. Answer YES. Once
inside the PCBSetup environment, press ESC and save the
new PCBOARD.DAT file.

3. Type MKTXT145 /UPGRADE C:\PCB\GEN\PCBTEXT. This procedure
reads the existing PCBTEXT file, adds fields for 14.5, and
saves the new file. A SysOp can contact the Salt Air BBS
and download updated multilingual PCBTEXT files. Although
this is recommended, the SysOp can utilize the MKTXT145
utility to translate newly added English fields.

4. The PCBoard 14.5 executable is called PCB145.EXE instead
of PCBOARD.EXE which previous versions used. As a result,
edit the BOARD.BAT file. Replace the line that reads
pcboard with pcb145.

5. Type PCBSM /UPGRADE which reads the existing USERS file
and creates a USERS.INF file. Since the USERS file does
not change, Third Party Applications can function normally
with 14.5.

6. Copy the new HLP* files into the \PCB\HELP subdirectory.

7. Copy the new BRDM and BRDMG files into \PCB\GEN or
customize existing menu files.












9




8. Edit the PCBPROT.DAT file to include the following
internal batch settings.


Internal Batch Settings

Y,I,1024,Ymodem

G,I,1024,Ymodem/G


9. Edit the PCBRZ.BAT file to reflect batch uploads via DSZ.
Place the line SET DSZLOG=PCBDSZ.LOG inside the BOARD.BAT
file.


Sample PCBRZ.BAT File

echo off
if exist pcberr.fil del pcberr.fil
if exist pcbdsz.log del pcbdsz.log
dsz.com handshake both pB4096 z pr1 rz -p %3


10. Remove all environment switches from the BOARD.BAT with
the exception of /NMT. These environment switches are
contained in PCBSetup and new, more versatile switches
have been added.

11. Read the file called FEATURES.NEW found on the
Distribution Disk. It lists, as the name implies, all
newly added features to the PCBoard 14.5 software.


After installation is complete, the SysOp can remove the following
files used in previous versions of PCBoard.


Removable Files

CALLWAIT.SCR CNAMES.$$$ MKPCBTXT.EXE

PCBOARD.EXE ALL DIR##G Files
















10




PCBoard Structure


C:\


\WP \Lotus \PCB \dBase \HG

BOARD.BAT
EVENT.SYS
MKTXT145.EXE
PCB145.EXE
PCBCMPRS.BAT
PCBDIAG.EXE
PCBFILER.EXE
PCBMODEM.EXE
PCBMONI.EXE
PCBOARD.DAT
PCBOARD.EXE
PCBPACK.EXE
PCBPROT.DAT
PCBSETUP.EXE
PCBSM.EXE
PCBTEST.BAT
PCBVIEW.BAT
REMOTE.SYS
TESTFILE.EXE
VIEWARCH.COM
VIEWZIP.EXE

(Batch Files for
External Protocols)

\UP \MAIN \GEN \HELP \SYSOPS \DL1 \DL2

Files ANSWER# BLT(G) HLPA-HLPZPRIVATES Files Files
U/L CALLER## BLT## HLPCHAT SANSWER# AvailableAvail.
to CNAMES BRDM(G) HLPOPEN SBLT(G) For For
the DOORS.DATBRDS(G) HLPSEC SBLT## Download Down-
Main D/L.TXT CNFN(G) (Etc.) SDIR(G) Load
Board FSEC DIR(G) SDIR##
MSGS DIR## SNEWS(G)
NEWREG DOORS(G) SSCRIPT(G)
PCBNDX.# NEWASK SSCRIPT#
PWRD NEWS(G) SYSOPS
TCAN NEWUSER
USERNET.DATPCBML.DAT U/L Files
(CHAT PRIVATE
FILES) SCRIPT#
WELCOME(G)
.LST Files








11




Call Waiting Screen


General Information
-------------------
The Call Waiting Screen provides ease of access to most system
functions. Since system configurations can be modified via this
screen, only the local SysOp can see the Call Waiting Screen.


Call Waiting Screen
-------------------

Below is the Call Waiting Screen. A brief description of each
option follows:


10-01-90 PCBoard (R) v14.5/U 11:09:46

Salt Air PCBoard BBS System - Node 15

User - Busy Sysop - Busy DOS - Busy

User - Not Busy Sysop - Not Busy DOS - Not Busy

Printer is Off Page Bell is On Alarm is On

PCBSysMgr PCBFiler PCBSetup

SYSTEM Statistics PCBMoni Reset Stats


Choose between System-Wide & Node-Specific Statistics Display

COM1: System is Ready For Callers

Last Caller: None

Calls: 0 Msgs: 0 D/L's: 0 U/L's: 0

(C) Copyright Clark Development Company, Inc., 1985-1990


















12





Call Waiting Function Keys Available
------------------------------------

Function or ALT Key Description

F1 Exit to DOS - Busy

F2 Local User Logon

F3 Toggle Printer

F4 Toggle Page Bell

F7 Toggle Alarm

F8 Recycle Call Waiting
Screen

F9 Toggle Display

F10 Exit to DOS - Not Busy

ESC Exit to DOS - Not Busy

ALT S Run PCBSysMgr (System
Manager)

ALT D Run PCBFiler

ALT M Run PCBMoni




























13




User Busy
---------
When a local user enters PCBoard, other callers are unable to
remotely access the system. Instead, the caller is met with a busy
signal until the SysOp logs out of PCBoard.


User Not Busy
-------------
When a local user enters PCBoard, other callers may remotely access
the system. The caller receives normal rings. The SysOp, on the
other hand, who uses the system hears the caller rings indicating
someone is trying to access the system. The caller is not connected
until the SysOp logs out of PCBoard.


SysOp Busy
----------
When chosen, the SysOp immediately logs into the system under his or
her name and password. The SysOp local password is indicated in
PCBSetup under SysOp Information. A caller is met with a busy
signal until the SysOp logs out of PCBoard.


SysOp Not Busy
--------------
The SysOp immediately logs into the system under his or her name and
password. The caller receives normal rings. The SysOp, on the
other hand, who uses the system hears the caller rings indicating
someone is trying to access the system. The caller is not connected
until the SysOp logs out of PCBoard.


DOS Busy
--------
PCBoard is terminated and the SysOp is returned to DOS. Callers are
met with a busy signal and are unable to remotely access the system.
Only when the SysOp executes the BOARD.BAT file are callers allowed
access.


DOS Not Busy
------------
PCBoard is terminated and the SysOp is returned to DOS. The caller
receives normal rings, but the SysOp never hears the rings. Only
when the SysOp executes the BOARD.BAT file are callers allowed
access.


Printer
-------
ON = Any information that is sent to the Caller's Log
is also sent to the printer. This normally
includes all user activities, file transfers,
DOOR entries, etc.
OFF= Though all user activities are still sent to the
Caller's Log, the information is not printed.


14




Page Bell
---------
ON = When a user implements the Operator Page command, the
SysOp hears a beep for 30 seconds. He or she may then
respond or ignore the page. The SysOp may specify in
PCBSetup--Option #2 the hours he or she wishes the
bell to be active.
OFF = When a user implements the Operator Page command, he
or she is told the SysOp is unavailable for CHAT.
PCBoard, however, asks the user if he or she wants to
leave a Comment to the SysOp.


Alarm
-----
ON = The SysOp hears an alarm when an invalid function is
attempted, carrier is detected from a logon, or
automatic logoff is one minute hence (specified in
PCBSetup--Options #1).
OFF = The SysOp does not hear an alarm when invalid
functions are entered, carrier is detected, or
automatic logoff is imminent. The caller, however,
hears all alarms generated by PCBoard regardless of
the alarm status.


PCBSysMgr
---------
PCBoard enters the System Manager. See PCBSysMgr.

PCBFiler
--------
PCBoard enters its Filing Utility. See PCBFiler.

PCBSetup
--------
PCBoard enters its Setup program. See PCBSetup.

PCBMoni
-------
PCBoard enters its Monitoring routine. See PCBMoni.

Statistics
----------
LOCAL = The screen indicates the last person to log into
the system using the current node. The screen also
shows the number of calls made, messages left, and
downloads/uploads conducted.
SYSTEM= The screen indicates the last person to log into
the entire system. Like local mode, the screen
also shows the number of calls made, messages left,
and downloads/uploads conducted.

Reset Stats
-----------
When invoked, the current caller name, calls, messages, and
downloads/uploads are reset to zero.


15




Command Line Parameters

General Information
-------------------
Usually, the SysOp accesses PCBoard by typing BOARD at the DOS
prompt. This action enacts the BOARD.BAT file and the Call Waiting
Screen appears. Once the Call Waiting Screen is accessible, the
system is ready to accept callers and implement remote commands.
However, inside the BOARD.BAT file, a SysOp may include special
parameters that can restrict PCBoard to local activities, facilitate
front-end type mail programs, and user performance.

/LOCALON
--------
If PCBoard is to be used as a local program for strictly mail
operations, the SysOp can use PCB145 /LOCALON in his or her
BOARD.BAT file to bypass the Call Waiting Screen. This procedure
has some ramifications.

All normal function keys are disabled. For a list
of those function keys and their abilities, see
Appendix II.

The 10 function key definitions listed in the
Options 2 screen of PCBSetup are still available
and can be used. These definitions require a shift
to invoke.

Since the system is locally used, no MODEM
controlled uploads or downloads can be
implemented.

The SysOp may want to remove the PCBSETUP.EXE and
PCBSM.EXE files from the hard drive of each local
user to prevent unauthorized modification of the
PCBOARD.DAT file and user records respectively.
The PCBSETUP.EXE file should be kept strictly by
the SysOp for future changes to the PCBOARD.DAT
file. This modified file may then be copied to all
local hard drives.

/C:#
----
This feature permits PCBoard to employ front-end type mail programs.
To utilize this function, the SysOp must indicate the connect speed
of the caller and whether he or she has made an error corrected
connection. The # corresponds to a baud rate that follows.

Format: PCB145 /C:# /ERR










16




The /ERR indicates that an error
corrected connection has been made. # Baud Rate
If the /ERR parameter is omitted,
no full-flow protocols are available 0 300
to the caller. A full-flow protocol 2 1200
such as YMODEM/G or 1K-XMODEM/G sends 3 2400
all information to the receiving MODEM 4 4800
without acknowledging proper acceptance 5 9600
of the first 128 bytes of data. In 6 19200
non-full-flow protocols, the first 7 38400
128 bytes of data are sent and a 8 57600
response is returned by the receiving 9 115200
computer. If information was properly
sent, data transfer continues; otherwise, the connection is
terminated.

/USERSYS
--------
Sometimes, a DOOR author wants to access the USERS.SYS file even
though a caller is not online. Furthermore, he or she may want to
generate a USERS.SYS file that contains Third Party Application
information. This command offers both facilities. Its format
follows.

PCB145 /USERSYS;[First];[Last];PWRD:[Password];TPA:[Application]

Each parameter is separated by a semicolon (;) while each
sub-parameter is indicated by a colon (:). Examples follow.


PCB145 /USERSYS;John;Doe;PWRD:Test

Explanation: A USERS.SYS file is created for John Doe. He has
a password of TEST. The password is required to avoid a
security breach.



PCB145 /USERSYS;John;Doe;PWRD:Test;TPA:QMAIL

Explanation: A USERS.SYS file is created for John Doe. He has
a password of TEST and a Third Party Application record for
QMAIL.
















17




/KEY:
-----
To expedite login procedures, a SysOp can pass special characters or
the contents of an entire file to the PCBoard keyboard buffer.
While this process can automate /LOCALON logins, it also permits
DOOR applications to pass commands to PCBoard. PCBoard interprets
any information that follows the /KEY: parameter as if it were typed
at the local keyboard.


Examples

PCB145 /KEY:^M

Hard Return.

PCB145 /LOCALON /KEY:y;q^MJohn;Doe^MPassword^M

Login; Yes indicate for graphics; Quick message scan; Hard
Return; First Name; John; Last Name; Doe; Hard Return;
Password entered; Hard Return.

PCB145 /KEY:@INPUT

The contents of a file called INPUT is sent to the PCBoard
keyboard buffer.


If words are separated by spaces, the entire /KEY command must be
enclosed by quotation marks. Furthermore, since DOS strips a
percent sign from any batch file, the at-sign (@) is used to stuff
the keyboard buffer with the contents of a file. This is, however,
in accordance with other DOS programs that accept response files
using the form @FILESPEC.

/EVENT:###
----------
This command line parameter discontinues PCBoard execution and runs
a preprogrammed event. An event is merely a time at which PCBoard
unloads itself, a program (batch file) is executed, and control is
returned to PCBoard. The ### indicates the number of minutes since
the BOARD.BAT execution that an event should run. This parameter
rides any event parameters specified in the Node/ Event/Subscription
screen of PCBSetup.















18




PCBoard Environment Switches
============================


General Information
-------------------
Environment switches configure memory and other computer features to
satisfy the needs of the software and the SysOp. In previous
versions, environment switches such as /BIO, /BLAST, /NOCTS, /BAUD,
/DELAY, and /NOVIEW were needed for proper software execution. In
PCBoard 14.5, however, only /NMT and /SWAP are necessary. A
discussion of each follows.


/NMT
----
Often times, PCBoard is used in a NOVELL network environment.
Software interrupts used by certain multitaskers which PCBoard calls
directly conflict with those used by NOVELL. As a result, the SysOp
must tell PCBoard that it is not treated as a multitasking package.
The SysOp can include the following in the BOARD.BAT file: SET
PCB=/NMT.


/SWAP
-----
PCBoard, as do all programs, requires memory to function. Normally,
when a SysOp or user shells to DOS, PCBoard remains in memory which
sometimes results in insufficient memory for alternate applications.
When the SWAP function is used, however, all but approximately 10
kilobytes of PCBoard is taken from memory leaving a great deal more
for alternate programs. The SWAP function accesses one of the
following in the indicated order: Extended Memory, Expanded Memory,
or the Hard Disk. To enable the SWAP function, SET PCB=/SWAP must
be placed in the BOARD.BAT file.


Location Explanation

The SWAP function accesses Extended Memory
Extended first. In order for SWAP to use extended
Memory memory, HIMEM.SYS must be loaded;
otherwise, it will be ignored.

The SWAP function accesses Expanded Memory
Expanded after Extended Memory. If Extended Memory
Memory is absent, Expanded Memory is scanned
first. An EMS memory manager is needed
for SWAP to notice the Expanded Memory.

The SWAP function accesses the Hard Disk
Hard after Extended and Expanded Memory is
Disk or in the event both are absent.






19




PCBoard automatically tests for the presence of Extended and
Expanded Memory. If both are absent, information is sent to the
Hard Disk. Furthermore, if there is insufficient free memory to
swap, information is sent to the Hard Disk. Information is sent to
a hidden file called PCBSWAP.$$$. The Sysop may change the name and
location of this file by changing the PCB environment setting.


SET PCB=/SWAP:F:\TEMP.$$$

The SWAP function is invoked. Instead of creating the hidden
file call PCBSWAP.$$$, the hidden file called TEMP.$$$ is
created on the F drive.



/MONO
-----
This environment switch overrides DOS color modes and displays the
Call Waiting Screen, Status Line, and the File Transfer Window in
black and white. However, all subsequent screens reflect the color
scheme of the caller.


/COLOR
------
PCBoard overrides DOS color modes and displays the Call Waiting
Screen, Status Line, and File Transfer Window in color. The colors
are hard coded: blue background, red option bars, and aqua statistic
lines. All subsequent screens reflect the color scheme of the
caller.


/NOCDVERIFY
-----------
Occasionally, particularly with Packet Switch Networks, Carrier
Detect (CD) is dropped. Carrier is merely a signal sent over phone
lines which modems use to transfer data. The CD determines whether
that basic signal is present. After CD drops, PCBoard waits a
second before disconnecting the caller. This normally provides
sufficient time for a modem to overcome intermittent variations that
may have invariably stopped a signal and caused CD to drop. If the
modem does not resume activity within that second, PCBoard
disconnects the caller. When this environment switch is included,
the caller is automatically disconnected as soon as CD drops.














20




/NO16550
--------
A SysOp can use a 16550 Universal Asynchronous Receiver Transmitter
(UART) chip to sort out bottle neck clogs that result from excessive
interrupts caused by high speed modems. A 16550 chip includes a
First-In-First-Out (FIFO) buffer that allows the processor, while
multitasking, to keep pace with high speed communications. To
accommodate this hardware, PCBoard determines either a 16550 chip is
present in the computer. If present, the software utilizes the full
potential of the chip. However, some 16550 chips had errors in
their construction and caused garbled screen displays. By using
this environment switch, PCBoard disregards the 16550 chip even if
it's present.


/CONNECT
--------
This environment switch is used exclusively for packet switch
networks. Normally in such a system, the SysOp has one line
dedicated to a particular baud rate. Although the packet switch
network is capable of transferring information at higher speeds, the
calling modems are limited to a lower baud rate. To calculate file
transfer times, therefore, the lower baud rate must be specified so
callers are not given erroneous time estimates. This lower baud
rate is a sub-parameter to the /CONNECT option.

Format: /CONNECT:[Baud Rate]

Examples

Command Description

/CONNECT:2400 File transfer times are based on 2400 baud.

/CONNECT:1200 File transfer times are based on 1200 baud.



/UPCRED:#
---------
When a caller uploads a file to a system, the caller's daily time
limit is credited by the number of minutes necessary to transfer the
file. For example, if a caller with a daily time limit of 30
minutes uploads a file for 15 minutes, he or she will still have 30
minutes remaining when
the file transfer is complete. Examples
This environment switch, however,
allows a SysOp to reward callers Command Description
who upload files. Instead of
providing one minute for each /UPCRED:0 No added time.
upload minute, the SysOp can give
two, three, or any number of minutes A caller receives
for each upload minute. /UPCRED:22 minutes for
each upload min.
Format: /UPCRED:#




21




/BYTECRED:#
-----------
When a caller uploads a file to a system, the caller's daily byte
limit is credited by the number of bytes necessary to transfer the
file. For example, if a
caller with a daily byte Examples
limit of 10 kilobytes
uploads a 15 kilobyte Command Description
file, he or she can then
download up to 25 kilobytes /BYTECRED:0 No added download
when the file transfer is bytes for uploads
complete. This environment
switch, however, allows a /BYTECRED:2 Two download
SysOp to reward callers who bytes for each
upload files. Instead of byte uploaded.
providing one downloadable
byte for each uploaded byte, /BYTECRED:5 Five download
the SysOp can give two, three, bytes for each
or any number of bytes for each byte uploaded.
uploaded byte.

Format: /BYTECRED:#





































22

















PCBSetup General Information
----------------------------
PCBSetup is used by the System Operator (SysOp) to configure path
specifications and other options for system needs. To enter the
PCBSetup environment, two ways are available. First, from the Call
Waiting Screen, the SysOp can simply press ENTER at the PCBSetup
option. Second, the SysOp can type PCBSetup from within the PCB
sub-directory. By the latter method, the SysOp can also pass
parameters to PCBSetup (discussed later).

At the Main Menu of the PCBoard Setup Utility screen, there are 10
selections ranging from SysOp Information to Conferences. Use the
arrow keys to scroll the list and hit (ENTER) to make a selection.
After making a selection, you may use the Page Up and Page Down keys
to scan any of the Main Menu choices. To return to the Main Menu,
hit (ESC). Following are two special keys:

F1 Help When pressed, the system help screen is displayed.
F2 Edit When prompted, F2 allows modification of system text
files.
F3 Edit When prompted, this feature allows modification of
system ANSI graphics files.

Once setup procedures are complete, you may exit PCBSetup by
pressing the (ESC) key. You will be prompted to enter one of the
following options:

(ESC) Quit program - do NOT save changes.
(N)o Quit program - do NOT save changes.
(Q)uick Save new data without checking any paths (Quick
Save).
(Y)es Save and check all paths and files (recommended for
new system configurations).













23




PreSetup Suggestions
--------------------
Plan your system. It is prudent to plan your system configuration
with pen and paper to insure executable files are located in their
appropriate subdirectories. Otherwise, PCBoard may not execute
properly.

Specify distinct levels of security. Define different levels of
security for different users. Normally, the SysOp has the highest
security level with expert, experienced, novice, and new users
respectively following regressive levels of 10 to 20 points. This
insures certain members of your organization are privy to certain
information or system commands while others are denied.

Be aware of user needs. By listing the specific needs of users, you
can prevent future hassles and long hours of configuration
modification. Consult the users of PCBoard. Distinguish between
first time users and those who will use PCBoard's advanced options.

Learn the Software. As the SysOp of your organization, you have a
responsibility to your users to solve any problems that may arise.
By experimenting with PCBoard, reading the manual, and studying
system paths and configurations, you can more expertly address user
questions and concerns.


PCBSetup Screen
---------------
After the PCBSetup utility is invoked either from the Call Waiting
Screen or a DOS command line, the following screen appears. From
this screen, the SysOp can implement any setup option he or she
desires.


PCBoard Setup Utility
Copyright (C) 1988-1990 Clark Develop Company, Inc.

Main Menu Use w/PCBoard 14.5

A Sysop Information
B File Locations 1
C File Locations 2
D Modem Information
E Node / Event / Subscription
F Options 1
G Options 2
H Options 3
I User Levels
J Main Board Configuration
K Conferences









24




SysOp Information Screen
------------------------
The SysOp Information Screen allows the SysOp to define security
levels that generally relate to running the system (SysOp duties).
When security is set, any user with an equal or greater level has
access to that specific function. Be certain that security levels
in user files (discussed later) correspond to the levels set in this
screen. Information contained in this screen is stored in
PCBOARD.DAT. Immediately following is a detailed account of each
field. Below is a sample of the SysOp Information Screen.


Sysop Information

Sysop Name : David
Local Password :
Use Real Name : Y
Use Graphics : Y

Level Needed to Read All Comments : 110
Level Needed to Read All Mail Except Comments : 100
Sysop Level (for Sysop Menu and F1-Temp-Sysop Upgrade) : 100
Level Needed to Copy or Move Messages Between Areas : 100
Level Needed to Enter @-Variables in Message Base : 100
Level Needed to Edit Any Message in the Message Base : 100
Level Needed to Use the 'Read Only' Command : 100

(1) View/Print Callers Log: 100 (8) Pack Users File : 120
(2) View/Print Users List : 100 (9) Exit to DOS remote : 120
(3) Pack Renumber Messages: 120 (10) Shelled DOS functions: 120
(4) Recover Killed Message: 110 (11) View Other Nodes : 100
(5) List Message Headers : 100 (12) Logoff Alternate Node: 110
(6) View Any File : 110 (13) View Alt Node Callers: 100
(7) User Maintenance : 110 (14) Drop Alt Node to DOS : 110



SysOp Name
----------
The SysOp Name is displayed during program execution. When a SysOp
leaves or receives a message, this name is indicated in the message
header (unless otherwise specified under the Use Real Name field
below).


Local Password
--------------
The Local Password is requested to gain entrance as a SysOp into the
local system. To access PCBSetup, PCBFiler, or PCBSysMgr from the
Call Waiting Screen, the SysOp must indicate a password in this
field. It adds a layer of security against unauthorized SysOp
access. The password should be one word or the field may be left
blank.






25




Use Real Name
-------------
Y = If the SysOp logs into a system using the SysOp - Busy or
USER - Busy options, any messages left, comments made, or
screens displayed use information contained in record one
of the USERS file.

N = When the SysOp logs into the system, any messages left,
comments made, or screens displayed use the SysOp Name
specified above rather than information contained in record
one of the USERS file.


Use Graphics
------------
Y = Upon local entry into SysOp Into System, you will be in
Graphics Mode.

N = Upon similar entry, you will be in non-graphics mode.


Read All Comments
-----------------
Any user with this security level or above may read all comments to
and from the SysOp. Since comments often contain sensitive
information, the SysOp may want to limit access to this capability.


Read All Mail Except Comments
-----------------------------
This security level permits users to read all mail except comments.
Any user with this level or above may read all conference mail and
private messages in which he or she is registered.


Temporary SysOp Level
---------------------
This security level has two purposes. First, any user with this
security level sees the SysOp menu. Second, this is the temporary
security level given to a caller when the F1 key is pressed. The
level assigned is discontinued when the caller hangs up or the F1
key is pressed a second time.


Move or Copy Messages
---------------------
This security level is needed to move or copy messages from one
conference to another. The command is entered at the end of a
message at the "(H)elp, End of Message?" prompt. Both MOVE and COPY
are discussed in the User Menu Commands section of this manual.









26




Enter @-Variables in Message Base
---------------------------------
This security level is needed to use @-Variables in a message. An
@-Variable allows a generic representation of a name, address, or
log time of the person to whom the message was sent. A list of
@-Variables can be found in Appendix VII. For now, consider the
following examples:

@[email protected] Substitutes the actual user name i.e. John Doe.
@[email protected] Substitutes the user's first name i.e. John.
@[email protected] Substitutes this with the number of files down/loaded
by John i.e. 196.


Edit Any Message in Message Base
--------------------------------
A user with this security level can edit any message in the message
base. Since many messages contain confidential and sensitive
information, the system operator ought to keep this level high
enough to prevent arbitrary or accidental message tampering.


Use Read Only Command
---------------------
This security level is necessary to use the Read Only Command. While
reading mail, a caller with sufficient security can specify an "O"
option. In this case, a SysOp may use this option to peruse his or
her mail without setting the header flag that indicates the message
has been read and without updating the last message read pointer.


View/Print Callers Log (1)
--------------------------
This security level is required to view the caller's log or audit
trail for that node. The file contains information concerning who
logged on, when, and what functions were performed while that user
was on-line. Any security violations are also included in the file.


View/Print Users List (2)
-------------------------
This security level is needed to view the user activity list. The
list contains the name and location of all registered users included
in the USERS file. It indicates the users last logon and the
duration of the call.


Pack & Renumber Messages (3)
----------------------------
This security level is needed to compress (pack/renumber) the
message base. During repack, PCBoard duplicates the current message
base and copies the unpurged or unkilled messages back to the
message base in their new order. As a 'SysOp only' function, this
level should be exclusive to the SysOp.





27




Recover Killed Message (4)
--------------------------
This security level is required to re-activate a killed message. The
message to be recovered must exist in the current message base for
reactivation. If the message base is packed using SysOp function
(3), a killed message cannot be re-activated.


List Message Headers (5)
------------------------
This security level is needed to view message headers (killed
messages included) in a particular message base. Included in the
list are the message number, reference number, and (A) for active or
(I) for inactive. Inactive messages have been killed but not
removed from the message base by a pack.


View Any File (6)
-----------------
This security level is required to view any system file. Since this
function can display confidential or sensitive information, the
SysOp should have exclusive rights to it.


User Maintenance (7)
--------------------
This security level is needed to perform maintenance on the USERS
file. Ideally, it should be granted to the SysOp only since
password and phone number information can be exposed using this
function.


Pack Users File (8)
-------------------
This security level is required to pack the USERS file.
Additionally, PCBoard only allows the user specified in record one
of the USERS file to perform a pack since repacking creates new user
index files.


Exit to DOS Remote (9)
----------------------
This security level is needed to EXIT TO DOS from remote. This
level should normally be set for SysOp access only; otherwise, any
user can enter DOS and possibly cause system damage.


Shelled DOS Functions (10)
--------------------------
This security level is required to perform a DOS SHELL function from
inside PCBoard. This function is similar to Function (9) and should
be handled comparably.







28




The functions below are only active in versions E3, E6, E9, and U of
the PCBoard software.


View All Node Activity (11)
----------------------
This security level is needed to view current activity on all system
nodes. This functions the same as the user NODE/CHAT command.


Log off Other Node (12)
-----------------------
This security level is required to log off an alternate node. It is
used primarily by a remote SysOp to disconnect a caller from any
node. After logoff, the particular node recycles and returns on
line.


View Other Caller Logs (13)
---------------------------
This security level is needed to view a node's callers' log or audit
trail. Since this function may expose sensitive information, the
security level ought to be set for SysOp activation only.


Drop Alternate Node to DOS (14)
-------------------------------
This security level is required to drop an alternate node to DOS.
Once a node is flagged as a drop-node, it cannot be reset. This
command is normally used in local mode to flag a node to drop to DOS
when the caller is in a DOOR or performing a SHELLed protocol file
transfer.



























29




General Information
-------------------
PCBoard uses two screens to show paths of drive specifications and
filenames. Since PCBoard can run in a network environment, the
paths may vary allowing the SysOp to customize the setup to suit
specific needs. Until further confidence is developed and system
structure memorized, it is prudent to use the default configurations
listed on each screen. However, if PCBoard is installed on a drive
different than C, all default configurations must be changed to
reflect the drive upon which PCBoard was installed. If PCBoard were
installed on drive D, every C: below would be replaced with D:.

Instead of changing each field to reflect a new drive, the SysOp may
delete the PCBOARD.DAT file. When PCBoard discovers the missing
file, the system will ask for a default drive to recreate the file.

Each file listed is a text file. However, PCBoard supports graphics
file. To distinguish between a regular text file and a graphics
file, PCBoard recognizes graphics files as those with a G appendage.
Whenever a modifiable file is encountered, PCBoard prompts the SysOp
to hit F2 to edit a normal text file or F3 to edit a graphics file.
The editors are defined in PCBSysMgr.

Below is a sample of the File Locations 1 screen. Information on
this screen is stored in PCBOARD.DAT. Following is a more detailed
analysis of each parameter.


File Locations 1


Location of Help Files : C:\PCB\HELP\
Location of Login Security Files : C:\PCB\SEC\
Location of Node CHAT Files : H:\
Location of PCBTEXT Files : C:\PCB\GEN\
Location of USERS File Index Files : H:\MAIN\
Location of Temporary Work Files : F:\

Name/Loc of Users File : H:\MAIN\USERS
Name/Loc of Users Info File : H:\MAIN\USERS.INF
Name/Loc of Callers File : H:\MAIN\CALLER
Name/Loc of Conference Data : C:\PCB\MAIN\CNAMES
Name/Loc of PWRD File : C:\PCB\MAIN\PWRD
Name/Loc of FSEC File : C:\PCB\MAIN\FSEC
Name/Loc of UPSEC File : C:\PCB\MAIN\UPSEC
Name/Loc of TCAN File : C:\PCB\MAIN\TCAN
Name/Loc of WELCOME File : C:\PCB\GEN\WELCOME
Name/Loc of NEWUSER File : C:\PCB\GEN\NEWUSER
Name/Loc of CLOSED File : C:\PCB\GEN\CLOSED
Name/Loc of WARNING File : C:\PCB\GEN\WARNING
Name/Loc of EXPIRED File : C:\PCB\GEN\EXPIRED









30




Location Of Help Files
----------------------
Default = C:\PCB\HELP\ The entry defines drive and directory
location of all help files. When HELP is requested by a user,
PCBoard resorts to this path for information.


Location Of Login Security Files
--------------------------------
Default = C:\PCB\GEN\ Security messages are stored in this
directory. A message file is displayed to a caller who has a
specific security level matching the filename's security level. The
files are optional and are discussed later.


Location Of Node CHAT Files
---------------------------
Default = C:\PCB\MAIN\ This location holds Node CHAT files which
are automatically created by PCBoard when a user enters a CHAT
session. This entry is unused with /S and /D versions of PCBoard.
For /E3, /E6, /E9, and /U versions, the specified location must be
the same for all nodes.


Location Of PCBTEXT File
------------------------
Default = C:\PCB\GEN\ The PCBTEXT file is stored in this directory.
It contains all necessary strings for PCBoard's proper operation.
The default location should not be changed unless the PCBTEXT file
is respectively moved. Failure to properly define this location
will cause an error on code load. Since PCBoard supports multiple
languages (discussed later), several PCBoard text files may exist,
each with its own extension.


Location Of Users Index Files
-----------------------------
Default = C:\PCB\MAIN\ The users' quick index files are located in
this directory. In a network environment, this location must be the
same for all nodes. Further, this location should reside on a
physical drive and not in Random Access Memory (RAM).


Location Of Temp. Work Files
----------------------------
Default = C:\PCB\ This directory holds any files or messages
captured by the user. It may be set to any location and may be
different for each node.


Users File
----------
Default = C:\PCB\MAIN\USERS The USERS file holds all user records
for the system. If possible, the default should be used. In a
network environment, this entry should be identical on all nodes.




31




Users Information File
----------------------
Default = C:\PCB\MAIN\USERS.INF This file holds variable records of
parts of the USERS file mentioned above. If possible, the default
should be used. This entry should be identical on all nodes.


Caller Log
----------
Default = C:\PCB\MAIN\CALLER This file contains caller logs and
audit trails. The filename must be 6 or fewer characters and cannot
have an extension. If the SysOp wants to view the log of other
nodes, this entry must be identical on all nodes. When PCBoard
creates a new caller log in a network, it will append the node
number to the filename i.e. Caller1, Caller2.


Conference Data File
--------------------
Default = C:\PCB\MAIN\CNAMES This indispensable data file contains
all conference configurations. To reduce file server traffic, the
file may be localized to each node.


Password File
-------------
Default = C:\PCB\MAIN\PWRD This file contains the time limit, daily
download byte limit, and batch limit a caller is allotted for each
call. The file may include a group logon password. This filename
can be unique for each node to provide distinct settings for users
with different security levels. The file may be edited with the F2
key when highlighted.


FSEC File
---------
Default = C:\PCB\MAIN\FSEC This file provides security protection
for files available for downloading. The file contains drive
locations, filenames, passwords, and security levels. It may be
unique to each node or shared on the file server to allow different
download capabilities. The file may be edited with the F2 key when
highlighted.


UPSEC File
----------
Default = C:\PCB\MAIN\UPSEC This optional file provides security
protection for files available for uploading. It may also restrict
certain types of uploading. The file contains drive locations,
filenames, passwords, and security levels similar to the contents of
the FSEC file. The file may be unique to each node or shared
through the file server. The file may be edited with the F2 key
when highlighted.






32




TCAN File
---------
Default = C:\PCB\MAIN\TCAN At times, logon is attempted by users
with an alias. This file contains names of undesirable logon ID's
and will screen the inappropriate users. Entries in the file can be
a single name or two names per line. This entry can be unique to
each node or shared by the file server. The file may be edited with
the F2 key when highlighted.


WELCOME File
------------
Default = C:\PCB\GEN\WELCOME This file contains the screen
displayed as users logon to the system. A similar file with a "G"
appendage can exist to support graphics mode i.e. WELCOMEG. The
field may be left blank to disregard any logon screen. The file may
be unique to each node or shared on the file server. The file may
be edited with the F2 or F3 keys when highlighted.


NEWUSER File
------------
Default = C:\PCB\GEN\NEWUSER This file is displayed during a user's
initial logon, but ignored thereafter. A similar file with a "G"
appendage should exist to support graphics mode i.e. NEWUSERG. The
field may be left blank to disregard any initial logon screen. The
file may be unique to each node or shared on the file server. The
file may be edited with the F2 or F3 keys when highlighted.


CLOSED File
-----------
Default = C:\PCB\GEN\CLOSED This file is displayed to callers if
PCBoard is run in CLOSED mode. If the caller has a security level
defined in the PWRD file with zero minutes of on-line time, the
caller receives a CLOSED message. The field NEW REG QUESTIONNAIRE
in File Locations 2 should be left blank to show the closed board
filename. A graphics version may exist and substituted i.e.
CLOSEDG. This field is not required for normal operation and may be
unique to each node. The file may be edited with the F2 or F3 keys
when highlighted.


WARNING File
------------
Default = C:\PCB\GEN\WARNING This file is displayed to users who
access a board and have fewer than 30 days remaining in their
subscription. A graphics version may exist and substituted i.e.
WARNINGG. This field is not required for system operation and may
be unique to each node. The file may be edited with the F2 or F3
keys when highlighted.








33




EXPIRED File
------------
Default = C:\PCB\GEN\EXPIRED This file is displayed to users who
attempt to access a board and have an expired subscription. A
graphics version may exist and substituted i.e. EXPIREDG. This
field may be unique to each node or omitted. The file may be edited
with the F2 or F3 keys when highlighted.





















































34




General Information
-------------------
Like File Locations 1, this screen allows a SysOp to specify drive
specifications and filenames. Furthermore, until confidence is
developed and system structure memorized, it is prudent to use the
default configurations listed on each screen.


File Locations 2 Screen
-----------------------
Below is a sample of the File Locations 2 screen. Information on
this screen is stored in PCBOARD.DAT. Following is a more detailed
analysis of each parameter.



File Locations 2

Name/Loc of USERNET.DAT File : H:\USERNET.DAT

Name/Loc of Conference Join Menu : C:\PCB\GEN\CNFN

Name/Loc of New Reg Questionnaire :
Name/Loc of Answers to New Reg. :

Name/Loc of Protocol Data File : C:\PCB\PCBPROT.DAT

Name/Loc of Transfer Summary File :

Name/Loc of Logoff Script Quest. : C:\PCB\GEN\LOGOFF
Name/Loc of Logoff Script Answers :

Name/Loc of Multi-Lang. Data File : C:\PCB\GEN\PCBML.DAT

Name/Loc of Group Chat Topic File : C:\PCB\GEN\GROUP

Name/Loc of Color Definition File : C:\PCB\PCBFILER.DEF



USERNET.DAT FILE
-----------------
Default = C:\PCB\MAIN\USERNET.DAT This file controls all network
function displays and NODE CHAT operations. This entry must be
identical on all nodes or SysOp functions (11) and above will not
work and system failure will result.


CONFERENCE JOIN MENU
--------------------
Default = C:\PCB\GEN\CNFN This file contains the menu displayed to
users when the (J)oin Conference command is executed. A similar
file with a "G" appendage can exist to support graphics mode i.e.
CNFNG. This field should not be left blank. The file may be edited
with the F2 or F3 key when highlighted.




35




NEW REG. QUESTIONNAIRE
----------------------
Default = C:\PCB\GEN\NEWASK This is the questionnaire file accessed
if running a 'closed' board operation (one that does not allow the
caller to create a record in the USERS file, but does allow him or
her on the system). This file may be used in place or in addition
to questions PCBoard asks of new users. This file may be created
using a text editor. Instructions for creating this file are
discussed later. The file may be edited with the F2 or F3 key when
highlighted.


ANSWERS TO NEW REG.
-------------------
Default = C:\PCB\MAIN\NEWREG This file contains answers to the
questions in the NEWASK file mentioned above. Since answers may
contain sensitive information, the file is stored in the MAIN
directory. This file is automatically created by PCBoard when a
user completes the NEWASK questionnaire file.


PROTOCOL DATA FILE
------------------
Default = C:\PCB\PCBPROT.DAT This file contains data crucial to
file transfer protocols and must exist for PCBoard to function. It
holds definitions for internal protocols including XMODEM, 1K-
XMODEM, YMODEM, and ASCII. Though no external protocols are
defined, the SysOp may create his or her own by following
instructions in Appendix V. The file may be edited with the F2 key
when highlighted.


DOWNLOAD SUMMARY FILE
---------------------
Default = C:\PCB\MAIN\DOWNLOAD.TXT This optional file summarizes
system file transfer information including caller name, date and
time of file transfer, upload/download specification, number of
block errors, successful/aborted status. The file also records
whether internal or external protocol was used.


LOGOFF SCRIPT QUEST.
--------------------
Default = C:\PCB\GEN\SCRIPT0 This optional file is used to ask a
caller questions or display a message when he or she logs off the
system. A similar file with a "G" appendage should exist to support
graphics mode i.e. SCRIPT0G. If left blank, no messages or displays
will be shown at logoff. Sometimes, this file is also called
LOGOFF. The file may be edited with the F2 or F3 key when
highlighted.









36




LOGOFF SCRIPT ANSWERS
---------------------
Default = C:\PCB\MAIN\ANSWER0 This file contains answers to the
questions in the SCRIPT0 file mentioned above. Since answers may
contain sensitive information, the file is stored in the MAIN
directory. This file is automatically created by PCBoard when a
user completes the SCRIPT0 questionnaire file.


MULTI-LANG. DATA FILE
---------------------
Default = C:\PCB\GEN\PCBML.DAT This file stores the multilingual
language operation information. The F2 key in PCBSetup should be
used for editing this file. Instructions for setup of a
multilingual system are discussed later.


GROUP CHAT TOPIC FILE
---------------------
Default = C:\PCB\GEN\GROUP This optional file is displayed prior to
joining a (G)roup node CHAT session. Information may be presented
about group CHAT if the activity is regularly accessed. If left
blank, nothing will be displayed. The file may be edited with the
F2 or F3 key when highlighted.


COLOR DEFINITION FILE
---------------------
Default = C:\PCB\PCBFILER.DEF This file holds the color
specifications for the display of DIR text files chosen by the last
highlighted field of the PCBFILER program. The colors can be
specified by running the PCBFILER program discussed later in this
manual. During modification of file colors, the change is
immediately displayed.

























37




General Information
-------------------
PCBoard uses information from this screen to set parameters
indicative of your brand and type of MODEM. Before entering
information into each field, it may be wise to run PCBMODEM at the
DOS prompt of your PCBoard root directory. This program will
introduce a number of MODEMs along with their configurations.
Information needed to complete the following parameters of the MODEM
screen can normally be found in the manual purchased with the MODEM.


MODEM Configuration Screen
--------------------------
Below is a sample of the MODEM Configuration Screen. Information on
this screen is stored in PCBOARD.DAT. Following is a more detailed
analysis of each parameter.



Modem Information

Seconds to wait for carrier : 18
Comm Port (1 to 8 or 0=NONE) : 1
Opening Baud Rate (300-115200) : 19200
Lock in Opening Baud Rate : Y
Modem Initialization String : ATE0M0H0
Modem Off-Hook String : ATM0H1
Disable CTS/RTS Checking : N
Disable CTS-Drop During Write : N
Using a Hayes V-Series 9600 : N
Using a FastComm 9600 : N
Reset Modem During Recycle : N
Modem Off-Hook During Recycle : N
Packet-Switch Network : N
Leave DTR Up at Drop to DOS : N
Answer on True Ring Detect : N
Number of Rings Required : 1
Modem Delay During Recycle : 0
Allow Callers at 7,E,1 : Y
Share IRQ's on MCA Buses : N
Lowest Desired Baud : 1200 Allow Lower : Y
Start : 00:01 Stop : 23:59


Seconds for Carrier
-------------------
Default = 15 This is the time in seconds PCBoard waits after a ring
has been detected before abandoning a handshake attempt. If a
carrier is not detected during this time, PCBoard will recycle and
await the next caller. Normally, the Hayes 9600-V Series, Microcom
AX, and EVI/FastComm MODEMs all require a value of at least 20
seconds. Some V.32 and V.42 MODEMs require values even higher.







38




Comm Port Number
----------------
Default = 1 This field indicates the communication port used by the
attached MODEM. If a MODEM is not used, this field should be 0. As
a result, all MODEM control will be disabled in PCBoard. If a COM
port greater than 2 is defined, PCBSetup requests the interrupt
number and COM port address.


Opening Baud Rate
-----------------
Default = 1200 This is the speed at which data is transmitted and
received. Some high speed MODEMs may be opened at a rate that is
faster than the MODEM's carrier speed i.e. 19200 or 38400 for a 9600
bps MODEM. As a result, the MODEM is not restricted to Characters
Per Second (CPS) reflective of baud rate. Instead, it may accept
information at greater CPS.


Lock in Baud Rate
-----------------
Y = This locks in the opening baud rate (DTE link) set above. A
(Y) should only be entered if using an error correcting
MODEM i.e. MNP that permits the DTE link to remain
stationary.
N = The opening baud rate set above will not be locked into
place. This is the default and unless the MODEM used meets
specifications mentioned under (Y), it should remain as (N).


MODEM Initialization String
---------------------------
Default = ATE0Q0VX11S10=20H0 This is the MODEM command string
needed to prepare the MODEM to receive calls. This string is a
generic one and varies heavily with each MODEM. Normally,
instructions that accompany your MODEM will list details of its
specific requirements.


MODEM Off-Hook String
---------------------
Default = ATM0H1 This is the MODEM command needed to place the
MODEM 'off-hook' when in a busy mode. The default string provided
during PCBoard installation is compatible with virtually all MODEMs.


Disable CTS/RTS Checking
------------------------
Y = This disables CTS/RTS checking because the MODEM used is
incompatible with a CTS signal. The CTS/RTS checking is
used for proper flow control to ensure data integrity.
N = This enables CTS/RTS checking. Such a field entry indicates
that the MODEM is compatible with a CTS signal.






39




Disable CTS-Drop During Disk Write
----------------------------------
Y = This disables CTS turn-off during disk writes. During an
upload, PCBoard automatically disables CTS to prevent data
overflow unless otherwise specified by a (Y) in this
parameter.
N = This enables CTS turn-off during disk writes. An (N) in
this field is recommended since few systems can write to
disk quickly enough to keep pace with a 9600 bps MODEM.


Using Hayes V-Series 9600
-------------------------
Y = The MODEM to be used is a Hayes 9600 V-Series MODEM. A
distinction is made since the Hayes 9600 bps MODEM handles
the DTE link differently than other high speed MODEMs.
N = The MODEM to be used is not a Hayes 9600 V-Series MODEM.


Using EVI/FastComm 9600
-----------------------
Y = The MODEM to be used is an EVI/FastComm MODEM. A
distinction is made since it returns the words CONNECT 19200
or CONNECT 9600 in lieu of CONNECT 9600/REL for a high speed
error corrected connection.
N = The MODEM to be used is not an EVI/FastComm MODEM.


Reset MODEM During Recycle
--------------------------
Y = The MODEM will be sent an ATZ command (Soft MODEM Reset)
before the MODEM initialization string. Normally, only
extreme cases such as an EEPROM losing all settings warrant
a (Y) for this parameter.
N = The MODEM will not be sent an ATZ command before the MODEM
initialization string. This setting is recommended.


MODEM Off-Hook During Recycle
-----------------------------
Y = The MODEM will be placed off-hook (busy) during code
recycle. If hardware is sluggish, a (Y) is appropriate to
prevent a ring detect while the system is recycling. This
will increase recycle time.
N = The MODEM will not be placed off-hook (busy) during code
recycle.


Packet Switch Network
---------------------
Y = The MODEM will be used in conjunction with a Packet-Switch
Network. This instructs PCBoard to open the communication
port, but refrain from sending any command strings.
N = The MODEM will not be used in a Packet-Switch Network. This
is the usual setting.




40




Leave DTR On at DOS Drop
------------------------
Y = The DTR light on the MODEM will be left on when the user
drops to DOS. This setting is determined by MODEM type.
Some MODEMs require DTR to remain high while the telephone
is taken off-hook.
N = The DTR light on the MODEM will be turned off when the user
drops to DOS.


Answer on True Ring Detect
--------------------------
Y = PCBoard will answer the telephone with a true ring detect
signal. This is not recommended since the ATA command may
be sent to the MODEM before the MODEM is prepared to accept
it resulting in detect failure.
N = PCBoard will answer the telephone with the result code word
"RING." This is recommended since the modem is more likely
to be prepared to accept incoming calls.


Rings Required Before Answer
----------------------------
Default = 1 This represents the number of telephone rings before the
MODEM begins its handshaking routine. Some telephones connected to
MODEMs are also used for voice communication. It is therefore
appropriate to set this number according to individual needs.


MODEM Delay During Recycle
--------------------------
Default = 0 This is set to the number of seconds that the MODEM will
wait before recycling. Since some MODEMs may be lethargic, unable
to process information as rapidly as others, it is necessary to slow
the recycle process for the MODEM to keep pace. This setting is
normally chosen through a process of trial and error to determine
the appropriate delay for the individual MODEM.


Allow 7,E,1 Callers
-------------------
Y = This will allow support of 7,E,1 MODEM settings as well as
the default of 8,N,1. The distinction is necessary since
7,E,1 callers are unable to process the 8 bit high-order
characters of graphic files and any non-ASCII file
transfers.
N = This will not allow support for 7,E,1 MODEM settings. Only
the 8,N,1 MODEM setting will be permitted. Callers at 7,E,1
are informed of the 8,N,1 requirement and promptly
disconnected.









41




Share IRQ's on MCA Buses
------------------------
Y = This permits the sharing of IRQ's via an MCA bus. Normally,
IRQ's cannot be shared. With an MCA bus, however, multiple
devices may use the same IRQ. Few computers have an MCA bus
and therefore lack this capability.
N = This will not permit the sharing of IRQ's via an MCA bus.
This is the normal setting.


Lowest Desired Baud
-------------------
Default = 1200 This represents the lowest baud rate that a caller
must have to access the system.


Allow Lower Baud Rate
---------------------
Y = This allows baud rates lower than the above setting. Since
lower baud rates utilize important system time, they are
often allowed during odd hours which can be specified in the
following two fields.
N = This will not allow baud rates lower than the above setting.


Start Stop
----------
Default = 00:01 If the above parameter is set to (Y), this
represents the start time when a lower baud rate may access the
system. For instance, after 9pm (21:00), callers with 300 baud may
access the system; before this time, they are rejected. Default =
23:59 If the above parameter is set to (Y), this represents the
stop time when a lower baud rate can no longer access the system.
For instance, before 6am (06:00), callers with 300 baud may access
the system; after this time, they are rejected.
























42




Networks, Multitasking, and Slave Cards
=======================================

General Information
-------------------
PCBoard uses the following screen to specify node, event, and
subscription information. Each section is described more thoroughly
in the pages that follow.

Node/Event/Subscription Screen
------------------------------
Below is the Node/ Event/ Subscription screen. Information
contained in this screen is stored in PCBOARD.DAT. A detailed
description of each parameter follows.



Node / Event / Subscription Information

Running a Network / Multitasker System : Y
Node Number on the Network : 12
Network Timeout on Errors (20-99 secs) : 20
Node Chat Frequency (once every 5-99 secs) : 5
Include City Field in NODE Display : Y
Using Slave Cards (slows file access) : Y

Is a Timed Event Active : Y
Time to Begin Event (military time) : 16:15
Minutes Prior to Suspend All Activity : 2
Disallow Uploads Prior to an Event : N
Minutes Prior to Disallow Uploads : 0
Slide Event Time if a User is Online : N

Enable Subscription Mode : Y
Default Subscription Length in Days : 365
Default 'Expired' Security Level : 9
Warning Days Prior to Expiration : 30



General
-------
A SysOp may create a network using software such as Novell or
Lantastic allowing several computers to be physically linked. Since
each computer has at least two COMM ports and two interrupts, the
SysOp can utilize several phone lines. Normally, networks are
necessary when more than two lines are needed. However, if a SysOp
needs two lines, but does not have sufficient equipment, he or she
may employ multitasking software.

Multitasking software permits a user to partition his or her system
into two or more working environments. Common multitasking software
is DESQview, OmniView, or DoubleDOS.






43




A slave card provides an additional communication port, interrupt,
and microprocessor. Since each communication line requires its own
COMM port and interrupt, slave cards are ideal for multi-line users
with limited resources. Furthermore, the added microprocessor
insures system speed suffers little from added communication lines.


Running Network/Multitasker System
----------------------------------
Y = The user has an E3 version of PCBoard or above. If using a
network version of PCBoard and this parameter is set to (N),
the CHAT/NODE function and the SysOp 11-14 commands will be
disabled. Additionally, PCBoard versions S and D ignore
this setting.

N = The user has an S or a D version of PCBoard. The user may
also run an E3 version or greater in non-network mode.


Node Number
-----------
Default = 1 This entry specifies the node number of the machine.
Each machine should have its own node number. The number should not
be greater than the number supported by the PCBoard version in which
it runs.


Network Timeout
---------------
Default = 20 This parameter provides the number of seconds PCBoard
should attempt to resolve a network file conflict that arise from
multiple node sharing and software-hardware clash.


Node Chat Delay
---------------
Default = 5 seconds When a caller is idle at the main command
prompt, this represents the number of seconds PCBoard will wait
between NODE/CHAT requests to scan the USERNET.DAT file. To reduce
disk accesses, this number can be increased. However, this value is
access only when a caller is 'idle' (not entering commands at the
Main Command prompt).


CITY In NODE Display
--------------------
Y = During NODE/CHAT or SysOp Commands 11-14, the display will
include the callers' location and name.
N = The callers' location will not be displayed during CHAT or
SysOp operation.


Slave Card Updating
-------------------
Y = The system used has a slave card instead of a true network
environment. Since some slave cards utilize different
filing procedures, this parameter must be set to (Y).
N = The system used does not have a slave card.

44




EVENTS
======

General
-------
An event is merely a time at which PCBoard is unloaded, a
preprogrammed routine runs, and control is returned to PCBoard. A
SysOp may guard his or her system against uploads that occur prior
to an event. This feature indicates the number of minutes before
event time that caller is prevented from accessing the system.


Timed Event Active
------------------
Y = There is an active timed event that will run at a particular
time of day based on the parameters that follow. An event
is a routine procedure that performs a necessary function
such as a daily backup.
N = There is not an active timed event.


Event Start
-----------
Default = 02:00 This represents the military time when the event
will begin. The event will then run until completion. Normally,
events should not be scheduled at midnight since time and date
changes may cause complications.


Activity Suspension Before Event
--------------------------------
Default = 0 This field indicates the number of minutes before an
event time that a caller will be prevented from accessing the
system. During this time, all activity is stopped and the system
counts down to the event time.


Disallow Uploads
----------------
Y = A caller whose system time is adjusted for an event will not
be able to upload a file during his or her call. Since many
SysOp's are granted large blocks of system time, this field
may prevent a SysOp from uploading a file by remote.
N = Despite a caller's adjusted time, he or she will be able to
upload a file.


Upload Disallowed Prior To Event
--------------------------------
Default = 0 This represents the number of minutes before an event
time that a caller can upload a file. For instance, if set to 10
minutes, a caller who logs into the system at 06:00 with a 12 hour
access time will be able to upload a file any time before 17:50
assuming an event is scheduled for 18:00.





45




Slide Event Time
----------------
Y = The event can be "slid" if a caller is on line when event
time approaches. This means an event is postponed until the
caller has completed his or her file activity. If the
scheduled event is not critical for system operation, this
field may be set to (Y).
N = The event cannot be "slid." This setting may be preferable
since many events are time dependent or require
synchronization among various nodes.


SUBSCRIPTIONS
=============

General
-------
Like any subscription (magazine, newspaper, etc.), a SysOp
determines what privileges a caller is granted for paying a fee on
his or her Bulletin Board System.


Enable Subscription Mode
------------------------
Y = This enables the subscription mode. Normally, if no
limitations are placed on callers, subscription mode is
unnecessary.
N = This disables the subscription mode. With this setting, the
expired security level is ignored since each caller has
identical system abilities.


Subscription Length
-------------------
Default = 365 days This is length of time the subscription
mentioned above will be enabled. If the above parameter is set to
(N), this parameter is ignored.


Expired Security Level
----------------------
Default = 9 Upon expiration of a callers support in any BBS, his or
her security level will be reduced to whatever level is specified in
this field. To retain the higher security level, the caller will
normally have to renew his BBS support.


Warning Days Prior to Expiration
--------------------------------

Default = 30 days A file (C:\PCB\GEN\WARNING) is displayed to users
who access a board and have fewer than 30 days remaining in their
subscription. This parameter can be changed to display a message
any number of days prior to support expiration.






46




General Information
-------------------
PCBoard uses three option screens to customize the software for the
needs of the user. In the current screen, most parameters are (Y/N)
flags that are nearly self explanatory.


Options #1 Screen
-----------------
Below is the Options #1 screen. Information contained in this
screen is stored in PCBOARD.DAT. A detailed description of each
parameter follows.



Options #1

Disable Message Scan Prompt :N Display NEWS Only if Changed :Y
Disable 3-minute Screen Clear:N Display User Info at Login :N
Disable Registration Edits :Y Include 'Uploaded By' in Desc :Y
Disable High-ASCII Filter :N Verify Files Uploaded :Y
Disable NS Logon Feature :N Allow Local SHELL to DOS :Y
Disable Password Check (DOS) :Y Pre-load PCBTEXT File :Y
Multi-Lingual Operation :N Pre-load CNAMES File :Y
Disable Full Record Updating :Y Use NEWASK+Standard Questions :N
Run System as a Closed Board :N Allow One Name Users :N
Use Non-Graphics Mode Only :N Log Caller Number to Disk :N
Exit to DOS After Each Call :N Log Connect String to Disk :N
Eliminate Screen Snow in PCB :N Log Security Level to Disk :N
Allow ESC Codes in Messages :Y Read PWRD on Conference Join :N
Allow Carbon-Copy Messages :Y Confirm Caller Name / Address :N
Validate TO: Name in Messages:Y Allow Password Failure Comment:N
Enforce Daily Time Limit :Y Warning on Logoff Command :N

Keyboard Timeout (in min, 0=disable) : 3
Max Number of Lines in Scrollback : 100
Number of Upload Description Lines : 8



Disable Msg Scan Prompt
-----------------------
Y = This disables the Scan Message Base Since Last Read? at
logon prompt. Callers may only view message bases with the
Y)our Mail command.
N = This prompts the caller to Scan Message Base Since Last
Read? at logon. The caller, however, must have sufficient
security to invoke the Y)our Mail command; otherwise, the
above prompt is not displayed.


Disable 3 min Screen Clear
--------------------------
Y = The screen will remain on at all times even when a caller is
absent.
N = The screen will clear the "call waiting" screen after three
minutes. This is recommended since it helps to prevent
screen burn.

47




Disable Registration Edits
--------------------------
Y = The registration edits feature will be disabled. While
entering user information or using the W)rite User Info
command, PCBoard will not check entries to prevent erroneous
information. If using a multi-lingual system, this
parameter should be set to (Y).
N = The registration edits feature will be enabled. During
registration input, PCBoard will check phone numbers for
"-/)(" characters and names for alpha characters.


Disable High-ASCII Filter
-------------------------
Y = The High-ASCII Filter will be disabled. If using a
multi-lingual system, this parameter should be set to (Y).
N = The High-ASCII Filter will be enabled. During MODEM
operation, this setting will filter "noise" that may cause
arbitrary characters to be displayed.


Disable NS LOGON
----------------
Y = The caller is unable to use the NS command to bypass the
NEWS file displayed at logon. However, the caller may still
bypass the WELCOME screen by using a stacked Q parameter
during initial LOGON.
N = The caller may use the NS command to bypass the NEWS file.


Disable Password Check (DOS)
----------------------------
Y = The password check from a DOS return is disabled. Normally,
if a caller drops to DOS and returns to PCBoard, there is
little need to check his or her password. However, if using
an "S0=1" for MODEM ring detect, a (Y) is essential to
prevent a breech of security.
N = The password check from a DOS return is enabled. By setting
this parameter, the caller will be asked to re-enter his or
her password.


Multi-Lingual Operation
-----------------------
Y = Multiple languages are supported. PCBoard will search for a
PCBML.DAT file that holds alternate languages. If the file
is absent, this parameter will be ignored.
N = Multiple languages are not supported.











48




Disable Full Record Updating
----------------------------
Y = A user cannot change his or her entire user record via
PCBoard's (W)rite command. The user can change his or her
password and the conferences to scan.
N = A user can change his or her entire record via PCBoard's
(W)rite command. This includes name, password, conference
scan, phone numbers, and others.


Run Closed Board System
-----------------------
Y = The BBS is closed to all new callers. New callers will not
be permitted to enter a new user record. Instead, a NEWASK
file (discussed later) should contain questions asked in
lieu of normal user questions. If security to new callers
is reduced to 0, new callers will be denied access and the
CLOSED file will be displayed.
N = New callers are permitted to create a new user record on the
system.


Non-Graphics Mode Only
----------------------
Y = PCBoard will run only in non-graphics mode.
N = PCBoard will support either graphics or non-graphics mode.
This setting may be desirable if all known users need or
want graphics.


DOS After Each Call
-------------------
Y = PCBoard will drop to DOS between calls. If running an
alternate program between calls, this setting is required.
N = PCBoard will not drop to DOS between calls.


Eliminate Screen Snow
---------------------
Y = This setting eliminates any screen snow that arises as a
result of older CGA monitors. It will slow screen display
capabilities slightly.
N = Screen snow will not be eliminated (Normally, unnecessary
with Mono, EGA, and VGA monitors).


ESC Codes in Msgs.
------------------
Y = PCBoard will allow ESC codes in system messages. Normally,
ESC codes such as "[32m" are used to display color,
highlighted phrases, or flashing characters. Such a setup
can cause "messy screens" if a caller does not have ESC code
capabilities.
N = PCBoard will not allow ESC codes in system messages.





49




Allow Carbon-Copy Msgs.
-----------------------
Y = This setting allows the same message to be sent to several
users. While in expert mode and while saving a message, a
new option (SC) will be made available to save the message
with a carbon copy. Further details are discussed later.
N = A message can only be sent to one person.


Validate "To:" Name in Msgs.
----------------------------
Y = PCBoard will check the user name to whom the message is
sent. It excludes any message to "ALL" and to a SysOp.
PCBoard will also inform the sender if a user is not
registered in the particular conference. Furthermore, a
Sound-Like search can be executed to locate any users with
similar sounding names. Any message base set for echo mail
will not have a TO validation.
N = PCBoard will not check the user name to whom the message is
sent.


Enforce Daily Time Limit
------------------------
Y = Callers are restricted to daily time limits based on
security levels in the PWRD file. A caller's time limit is
reduced with each successive call during the day.
N = A caller may access the system as many times as he or she
desires with only a session time restriction. A caller's
time limit returns to the level specified in the PWRD file
each time a user calls.


Display NEWS (Changed Only)
---------------------------
Y = The NEWS file will be displayed if changed or if a caller's
last LOGON date is earlier than the date of the last NEWS
file modification. Callers with a SysOp security level will
not see the NEWS file unless requested.
N = The NEWS file will be displayed to all callers regardless of
past modification. However, it is only displayed to a
caller on his or her first call of the day.
A = The NEWS file is always displayed.


User Info. at LOGON
-------------------
Y = User information will be displayed at LOGON. This
represents the same information that a user would see if the
(V)iew Settings command were selected.
N = User information will not be displayed at LOGON.








50




Uploaded By In Description
--------------------------
Y = The upload file description will include the name of the
person who uploaded it. This can provide some incentive for
callers to upload more files.
N = The upload description will not include the source's name.
Some SysOps prefer this anonymity for security reasons.


Local Shell To DOS
------------------
Y = A local user will be able to drop to DOS using the (F5) key
while still having PCBoard in memory.
N = The user will not be able to drop to DOS while in PCBoard.


Pre-Load PCBTEXT File
---------------------
Y = The PCBTEXT file will be pre-loaded into low memory. This
insures swifter and more efficient access to text
information. This of course requires additional memory, but
also reduces wear and tear on the hard disk.
N = The PCBTEXT file will not be preloaded. Instead, it will be
accessed when needed from the hard drive. However, placing
the PCBTEXT files on a RAM disk or utilizing a disk cache
can provide more efficient performance.


Pre-Load CNAMES File
--------------------
Y = The CNAMES file will be pre-loaded. This insures swifter
and more efficient access to user name information. This of
course requires additional memory, but also reduces wear and
tear on the hard disk. If the entire CNAMES file is greater
than 64 Kilobytes or the available memory, only the last 16
conferences accessed are cached in memory.
N = The CNAMES file will not be preloaded. Instead, it will be
accessed when needed from the hard drive.


Newask+Standard Questions
-------------------------
Y = In addition to PCBoard's standard questions for new user
registration, questions contained in NEWASK can be asked to
reflect unique system needs. The format used to create the
NEWASK file is identical to a standard script questionnaire.
N = New users will be asked PCBoard's standard questions only.


Allow One Name Users
--------------------
Y = When a new caller registers, PCBoard permits him or her to
use only one word instead of a normal first and last name.
This may be advantageous for companies that use specific
serial or account numbers for each client.
N = New callers are required to register with a first and last
name.


51




Log Caller Number To Disk
-------------------------
Y = Each caller is given a successive number (1 for first, 2 for
second, 3 for third etc.). That number is recorded in the
caller's log and can only be reset by executing the file
PCBNUM.EXE.
N = Each caller is given a successive number. However, that
number is not recorded int he caller's log.


Log Connect String To Disk
--------------------------
Y = Whenever a caller connects to a system, the modem connect
string is recorded in the caller's log.
N = The caller's connect string is not recorded in the caller's
log.


Log Security Level To Disk
--------------------------
Y = The security level of the caller is recorded in the caller's
log.
N = The security level of the caller is not recorded in the
caller's log.


Read PWRD On Conf. Join
-----------------------
Y = Sometimes, when a user joins another conference, his or her
security level is augmented. By consequence of this field,
the PWRD file is scanned to provide not only changed
security, but additional time, downloadable kilobytes, and
batch limits.
N = Although a user's security level is changed after joining a
conference, he or she retains the limits previously assigned
from the initial login.


Confirm Caller's Name/Address
-----------------------------
Y = During login, PCBoard asks the caller to confirm his or her
name and address. For large systems, such a procedure is
advantageous since users with similar names may call.
N = PCBoard asks for the caller's first and last name, but does
not confirm the names or address information.














52




Allow Password Failure Comment
------------------------------
Y = When a caller logs into the system, PCBoard asks for his or
her first and last names and password. The caller has four
attempts to enter the correct password before he or she is
automatically logged off. After the fourth attempt,
however, the caller is permitted to leave a Comment to
SysOp. After the comment is entered, the caller is logged
off.
N = After the fourth attempt to enter a correct password, the
caller is automatically logged off the system without
recourse.


Warning On Logoff Command
-------------------------
Y = When a user invokes the G)oodbye command, PCBoard confirms
the user's request by displaying the question Log Off
System?. The user can bypass this question by typing BYE at
the menu command prompt.
N = When a user invokes the G)oodbye command, PCBoard logs the
user out of the system immediately.


Keyboard Timeout
----------------
Default = 5 minutes This specifies the amount of time the keyboard
remains unattended before PCBoard logs a caller off the system. If
set to 0, there is no keyboard time checking. During the last
minute, PCBoard sounds one beep every 10 seconds to inform the
caller of his or her inactivity.


MAX Lines in Scrollback
-----------------------
Default = 0 This represents the number of lines that can be
scrolled back once inside PCBoard by using the up and down arrow
keys. Placing a 0 in this field disables the function. When
enabled, it can be a number from 30 to 400, but depends on the
memory availability in the machine. This facility is available in
local mode only.


Number Of Upload Description Lines
----------------------------------
Default = 8 When a caller uploads a file, he or she is permitted to
enter a description of the file. This parameter indicates the
number of lines for each uploaded file description. Each line has
up to 45 characters. The minimum number of lines is 1.










53




General Information
-------------------
PCBoard uses three option screens to customize the software for the
needs of the user. In the Options #2 Screen, the user can program
function keys, specify compressed file information, and set other
parameters to adapt the software to the users' needs.


Options #2 Screen
-----------------
Below is the Options #2 screen. Information contained in this
screen is stored in PCBOARD.DAT. A detailed description of each
parameter follows.



Options #2

Board Name : Salt Air PCBoard BBS System

Batch file for viewing compressed files : PCBVIEW.BAT
Filename EXTENSION for compressed files : ZIP

Allow Sysop Page Start Time : 00:00
Allow Sysop Page Stop Time : 23:59

F-Key #1 :
F-Key #2 :
F-Key #3 :
F-Key #4 :
F-Key #5 :
F-Key #6 :
F-Key #7 :
F-Key #8 :
F-Key #9 :
F-Key #10 :



Board Name
----------
This is the name of the board that will be displayed upon LOGON and
at the 'call waiting' screen.


Batch File for Viewing Compressed Files
---------------------------------------
Default = PCBVIEW.BAT During a call from the (F)ile Directory of
PCBoard's main menu and a sub-command call of (V)iew file, PCBoard
will call this file (PCBVIEW.BAT) to view the file specified in the
(V)iew parameter. If left blank, the (F)ile--(V)iew command will be
disabled.







54




Compressed Filename Extension
-----------------------------
Default = ZIP This represents the extension of a filename while
using the (F)ile--(V)iew command. If the extension is omitted while
using the (F)ile-- (V)iew command, PCBoard will append the filename
with whatever extension is specified in this parameter. There can
be only one extension listed in this field.


SysOp Page Start Time
---------------------
Default = 00:00 The SysOp can be paged via PCBoard's (O)perator
Page command. If a caller needs to CHAT with the SysOp, this is the
function that allows conversation, but only beginning with the time
specified in this field.


SysOp Page Stop Time
--------------------
Default = 23:59 Like the above parameter, this field specifies the
ending time that the SysOp can be paged for a CHAT function.


(Shift+Fn) Definitions
----------------------
Default = None The ten function key fields allow definition of
frequently used strings. Whenever specified, the programmed string
can be implemented by a (Shift + Fn#). Any karat (normally Shift 6)
followed by a capital letter results in a print of a control
character. Following are special characters that can be used in the
field.


^M Carriage Return/Line Feed
%filename Imports Text File
























55




General Information
-------------------
PCBoard uses three option screens to customize the software for the
needs of the user. In the Options #3 Screen, the user provides
relevant conference information, ANSI codes, and message editing for
proper PCBoard performance.


Option #3 Screen
----------------
Below is the Options #3 screen. Information contained in this
screen is stored in PCBOARD.DAT. A detailed description of each
parameter follows.


Options #3

Number of Highest Conference Desired : 16

Maximum Lines in the Message Editor : 200
Message Capture - Maximum Messages : 1000
Message Capture - Max Per Conference : 500
Name of Capture File (blank=caller#) : SALTAIR
Stop Clock for Capture File Download : N

Default to (Q)uick on Personal Mail Scan : Y
Default to Scan ALL Conferences at Login : Y

Default Color ANSI Code : 37
Default Color Intensity : 0

Upload Buffer Size (4-64) : 8
Disable Drive Size Check : N
Parallel Port Num (1-3,0) : 1
Stop Upload's when Free Space is less than : 0 K-bytes



Highest Conference
------------------
Default = 1 This field represents the number of conferences from 1
to 65,000 that PCBoard will support. Conference information need
not be specified for all conference numbers although a listing of
active conferences is preferable.


Maximum Lines in Msg. Editor
----------------------------
Default = 99 This number indicates the number of lines in the full
screen editor of PCBoard. The field can be adjusted to reflect
system needs, but is restricted by available memory. Ideally, this
number should not exceed 150.







56




Msg. Capture--Maximum Msgs.
---------------------------
Default = 600 This is the maximum number of messages that can be
captured using the R A D, R A Z, or R A C commands of the PCBoard
command menu.


Msg. Capture--Max. Per Conf.
----------------------------
Default = 200 This is the maximum number of messages that can be
captured in each conference.


Capture File
------------
Default = None If messages are captured by a caller, this is the
file to which those messages will be downloaded. If this field is
left blank, any messages will be downloaded into a file named from
the caller's number with a CAP extension i.e. 100.CAP.


Stop Clock For Capture File Download
------------------------------------
Y = During a download of a message capture file, the caller's
allotted system time will be halted until the download is
complete. Then, the system time will resume.
N = During a download of a message capture file, the caller's
allotted system time will continue to elapse.


(Q)uick On Mail Scan
--------------------
Y = The (Y)our personal mail command will default to a (Q)uick
format search of the message base as opposed to the (L)ong
format search. The Quick Format displays the message and
reference numbers, message author and recipient, and the
subject matter. The Long Format shows the number of "msgs
for you," "msgs from you," and the "number of msgs found."
N = The (Y)our personal mail command will not default to a
(Q)uick format search of the message base.


Scan All Conf. At LOGIN
-----------------------
Y = Upon LOGIN, PCBoard will scan all conferences for comments
or messages that have been left for the caller.
N = PCBoard scans only the current conference upon LOGIN.












57




Color ANSI Code
---------------
Default = 37 This entry contains the ANSI escape code for the
default color of character input. The valid color codes follow:

31 - Red
32 - Green
33 - Yellow
34 - Blue
35 - Purple
36 - Cyan
37 - White


Color Intensity
---------------
Default = 0 This number determines whether displayed text will have
normal intensity color (0) or high intensity color (1).


Upload Buffer Size
------------------
Default = 8 This number can be between 4 and 64 and represents the
amount of space allotted to the upload buffer. This parameter
should be set to correspond with individual equipment
specifications.


Disable Drive Size Check
------------------------

Y = This setting will disable the drive size check. If the
system does not support free space checking or if
information is denied access by callers, this parameter
should be (Y).
N = This setting will enable the drive size check. Before an
upload, PCBoard will check for appropriate free space on the
hard drive.


Parallel Port Number
--------------------
Default = 1 This should represent the number of the parallel port
to which the system printer is connected: 1 for LPT1; 2 for LPT2; 3
for LPT3; 0 for none.


Stop UpLoads With Free Space
----------------------------
Default = 0 The value entered here is multiplied by 1024 to
determine the number of free bytes on the upload drive before
allowing an upload to occur. For example, if 100 were entered,
100K of free disk space would be needed for a successful upload.






58




General Information
-------------------
This screen allows entry of user security levels for all menu
options available to normal callers. A caller must have an equal or
greater security level for command access.

If 0 is set for "Users Who Refuse To Register," a new caller who
refuses to register is automatically logged off. If PCBoard will
run in a multilingual system, no minimum security level is required
for the (LANG) command.


User Security Level Screen
--------------------------
Below is the User Security Level screen. Information contained in
this screen is stored in PCBOARD.DAT. A detailed description of
each command will be discussed in the latter portion of this manual.


User Security Levels

A) Abandon Conference : 9 Q) Quick Message Scan : 9
B) Bulletin Listings : 9 R) Read Messages : 9
C) Comment to Sysop : 9 S) Script Questionnaire : 9
D) Download a File : 9 T) Transfer Protocol : 9
E) Enter a Message : 9 U) Upload a File : 9
F) File Directory : 9 V) View Settings : 9
H) Help Functions : 9 W) Write User Info. : 9
I) Initial Welcome : 9 X) Expert Mode Toggle : 9
J) Join a Conference : 9 Y) Your Personal Mail : 9
K) Kill a Message : 9 Z) Zippy DIR Scan : 9
L) Locate File Name : 9 CHAT Between NODEs : 9
M) Mode (graphics) : 9 OPEN a DOOR : 9
N) New Files Scan : 9 TEST a File : 9
O) Operator Page : 9 USER Search/Display : 9
P) Page Length : 9 WHO is On Another Node : 9

Level Required for BATCH File Transfers : 9
Level Required to EDIT Your Own Messages : 9
Level Given to Users Who Agree to Register : 9
Level Given to Users Who Refuse to Register : 0


















59




General Information
-------------------
PCBoard uses information contained in the Main Board Configuration
screen to specify file locations and unique environment
specifications. Data in this screen stored in the CNAMES file. As
previously mentioned, the CNAMES must be identical for every node to
prevent file conflicts and system corruption.

If the CNAMES file is stored on a local drive instead of the file
server, insure all nodes are updated as the CNAMES file changes.


Main Board Configuration Screen
-------------------------------
Below is the Main Board Configuration screen. A detailed
description of each parameter follows.



Main Board Configuration

Make All Uploads Private : Y
Make All Messages Private : Y

Number of Message Blocks : 8
Name/Loc of MSGS File : C:\PCB\MAIN\MSGS

Name/Loc of Users Menu : C:\PCB\GEN\BRDM
Name/Loc of Sysops Menu : C:\PCB\GEN\BRDS
Name/Loc of NEWS File : C:\PCB\GEN\NEWS

Sort Name/Loc Upload DIR File Location of Uploads
Public Upld: 0 : C:\PCB\MAIN\PUBLIC : C:\PCB\UPLOADS\
Private Upld: 0 : C:\PCB\MAIN\PRIVATE : C:\PCB\PRIVATE\

Menu Listing Path/Name List File
Doors : C:\PCB\GEN\DOORS : C:\PCB\GEN\DOORS.LST
Bulletins : C:\PCB\GEN\BLT : C:\PCB\GEN\BLT.LST
Scripts : C:\PCB\GEN\SCRIPT : C:\PCB\GEN\SCRIPT.LST
Directories : C:\PCB\GEN\DIR : C:\PCB\GEN\DIR.LST
Download Paths (listing only) : C:\PCB\GEN\DLPATH.LST



Make Uploads Private
--------------------
Y = All main board uploads become private and are therefore not
available for immediate download by other callers. Private
uploads are placed in the Private Upload Location specified
below. File descriptions are stored in the Private Upload DIR
File described below.
N = Normally, all main board uploads are considered public and are
available for immediate download by callers. As a result,
upload files are stored in the Public Upload Location specified
below and have descriptions stored in the Public Upload DIR File
also mentioned below. However, a caller may specify a file to
be private by placing a slash before its description.


60




Make Msgs. Private
------------------
Y = Upon entry, a main board message is flagged as private and can
be read by the recipient only. Once read, the SysOp may
unprotect it (available for public eyes).
N = Normally, all main board messages are available for public
viewing unless further security is attached to it (Discussed
under User Commands).


Message Blocks
--------------
Default = 4 blocks This entry specifies the number of active or
inactive messages that will be stored. Each block holds 1024
messages based on the space between the low message number and the
high message number. If, for example, 4 blocks were specified, the
message base could hold 4,096 messages. The number of messages is
calculated by subtracting the low message number from the high
message number.


MSGS File
---------
Default = C:\PCB\MAIN\MSGS This is the name and location of the
main board's message base file. The filename must have fewer than 8
characters with no extension. In a network environment, this file
must be stored on the file server to allow equal access by all
nodes.


Users Menu
----------
Default = C:\PCB\GEN\BRDM This is the file that a caller sees when
he or she logs into the system. Since some callers are granted
higher or lower security levels, user menus can be modified to
reflect differing user capabilities. File Naming Conventions are
discussed under Advanced Techniques.


SysOps Menu
-----------
Default = C:\PCB\GEN\BRDS This is the file that a SysOp sees when
he or she logs into the system. Any caller with a SysOp security
level will see this menu in lieu of the standard user menu. PCBoard
supports a graphics version of this file named BRDSG. File Naming
Conventions are discussed under Advanced Techniques.


News File
---------
Default = C:\PCB\GEN\NEWS This is the file that will be displayed
to callers as they log into the system. PCBoard supports a graphics
version of this file which should be labeled NEWSG. Further
information of the NEWS file can be found in the Options #1 portion
of PCBSetup.




61




Public Upload Sort Preference
-----------------------------
Default = 2 This entry represents the sort preference for the main
board's public upload DIR file. This information is needed by the
PCBFiler program to sort properly. The sorting preference will be
discussed later under PCBFiler capabilities. Valid entries are:

0 - No Sort 3 - File Name (Descending)
1 - File Name (Ascending) 4 - File Date (Descending)
2 - File Date (Ascending)


Public Upload DIR Filename
--------------------------
Default = C:\PCB\MAIN\UPLD This is the name and location of the
public upload DIR file mentioned above. In a network environment,
this file must be located on the file server to permit all nodes
access to new uploaded files. UPLD contains the name, size, date,
and a brief description of uploaded files. This file should only be
edited by PCBFiler.


Public Upload File Location
---------------------------
Default = C:\PCB\UPLOAD\ This represents the directory that will
contain all public uploaded files. The previous entry stores file
descriptions. This entry is the physical location of those files.
In a network environment, this path should be shared on the file
server and listed in the DLPATH.LST file to allow all callers
immediate access to uploaded files.


Private Upload Sort Preference
------------------------------
Default = 2 This entry represents the sort preference for the main
board's private upload DIR file. This information is needed by the
PCBFiler program in order to function properly. The sorting
preference will be discussed later under PCBFiler capabilities.
Valid entries are:

0 - No Sort 3 - File Name (Descending)
1 - File Name (Ascending) 4 - File Date (Descending)
2 - File Date (Ascending)


Private Upload DIR Filename
---------------------------
Default = C:\PCB\MAIN\PRIVATE This is the name and location of the
private upload DIR file. The file contains the name, size, date,
and description of any private files uploaded to the system. To
edit this file, PCBFiler should be used.








62




Private Upload File Location
----------------------------
Default = C:\PCB\PRIVUPLD\ This directory holds the actual private
uploaded files. Unlike the public upload path, this path should not
be included in the DLPATH.LST unless the SysOp permits callers
access to privately posted uploads.


Door Menu
---------
Default = C:\PCB\GEN\DOOR This file contains the menu displayed to
a caller who wishes to access a door. The file may be modified
using any text editor. PCBoard supports a graphics version of this
file named DOORG. Each DOOR may be accessed by name or by number
allowing the SysOp to design a DOOR menu appropriate for his or her
needs. If running a network and storing this file on each local
node's drive, each node should be updated when this file changes.
After specifying a text and graphics editor under PCBSysMgr, the
file can be edited by pressing F2 or F3.


Door List
---------
Default = C:\PCB\GEN\DOOR.LST This file contains a list of batch
files and optional security protection that correspond to each entry
made in the DOOR menu. To create a DOOR, consult Editing Main Board
and Conference Files.


Bulletin Menu
-------------
Default = C:\PCB\GEN\BLT This file contains the menu displayed to a
caller who wishes to access a bulletin of a particular system. The
file may be modified using any text editor (specified under
PCBSysMgr). PCBoard supports a graphics version of this file named
BLTG. Since every listing in this menu is accessed numerically,
each entry should have a corresponding number. If running a network
and storing this file on each local node's drive, each node should
be updated when this file changes. After specifying a text and
graphics editor under PCBSysMgr, the file can be edited by pressing
F2 or F3.


Bulletin List
-------------
Default = C:\PCB\GEN\BLT.LST This file contains a list of the
individual files that correspond to the numerical listings in the
BLT menu.











63




Script Questionnaire Menu
-------------------------
Default = C:\PCB\GEN\SCRIPT This file contains the menu displayed
to a caller who wishes to access a script questionnaire of a system.
The file may be modified using any text editor (specified under
PCBSysMgr). PCBoard supports a graphics version of this file named
SCRIPTG. Since every listing in this menu is accessed numerically,
each entry should have a corresponding number. If running a network
and storing this file on each local node's drive, each node should
be updated when this file changes. After specifying a text and
graphics editor under PCBSysMgr, the file can be edited by pressing
F2 or F3.


Script Questionnaire List
-------------------------
Default = C:\PCB\GEN\SCRIPT.LST This file contains a list of the
individual files that correspond to the numerical listings in the
SCRIPT menu. When F2 is pressed, a list of path specifications and

file names is displayed.


File Directory Menu
-------------------
Default = C:\PCB\GEN\DIR This file contains the menu displayed to a
caller who wishes to access a particular file directory. The file
may be modified using any text editor (see PCBSysMgr). PCBoard
supports a graphics version of this file named DIRG. Since every
listing in this menu is accessed numerically, each entry should have
a corresponding number. If running a network and storing this file
on each local node's drive, each node should be updated when this
file changes.


File Directory List
-------------------
Default = C:\PCB\GEN\DIR.LST This file contains a list of the
filenames and locations of the main board's file directories that
correspond to the numerical listings in the DIR menu. The file
directories can be edited using PCBFILER. While storing this file
on individual nodes in a network environment, each node should be
updated when this file changes.


Download Path
-------------
Default = C:\PCB\GEN\DLPATH.LST This file contains a complete
listing of all directories that contain files available for
downloading. This file is for path information only. The file may
be modified by pressing F2 or F3. This file can be located on
either a local or network drive. However, if located on a local
drive, all nodes must be updated when this file changes.







64




General Information
-------------------
PCBoard uses the following sequence of screens to maintain
individual conferences. Currently, PCBoard can support up to 65,000
conferences, but the likelihood of a system exhausting PCBoard's
conference capacity is scanty at best. For each conference
supported by a particular system, a configuration screen must be
completed.

Conference Menu Screen
----------------------
Below is the Conference Menu screen that numerically lists each
conference name. To edit a conference configuration, simply
highlight the conference name or type the conference number and
press ENTER.



Conferences Menu


1) Support 2) DOOR 3) Utility
4) Net_Mail 5) LANtasti 6) Beta
7) Develop 8) Alpha 9) Freds
10) LAN2 11) Singapore 12) ForSale
13) CentreGroup 14) ALMAC 15) Saudi Arabia
16) C.A.T.S. 17) 18)
19) 20) 21)
22) 23) 24)
25) 26) 27)
28) 29) 30)
31) 32) 33)
34) 35) 36)
37) 38) 39)
40) 41) 42)

Use arrow keys to move bar, press ENTER to select, ESC to exit






















65




Conference Configuration Screen
-------------------------------
After pressing ENTER, a configuration screen will appear. This
screen is similar to the Main Board Configuration screen and is used
to define information specific to each conference. Data entered in
this screen is stored in the CNAMES file.



Conference Name : Support Make All Uploads Private : Y
Public Conference : Y Make All Messages Private: Y
Req. Security if Public : 20 Echo Mail in Conference : N
Auto-Rejoin into this Conf : Y Additional Conf Security : 0
Allow Viewing Conf Members : N Additional Conf Time : 0
Number of Message Blocks : 32
Name/Loc of MSGS File : C:\PCB\SUPPORT\MSGS
Name/Loc of Users Menu : C:\PCB\GEN\BRDM
Name/Loc of Sysop Menu : C:\PCB\GEN\BRDS
Name/Loc of NEWS File : C:\PCB\GEN\SNEWS

Sort Name/Loc Upload DIR File Location of Uploads
Public Upld: 0 : C:\PCB\SUPPORT\PUBLIC : C:\UPLOADS\SPRT\
Private Upld: 0 : C:\PCB\SUPPORT\PRIVATE : C:\PRIVATE\SPRT\

Menu Listing Path/Name List File
Doors : C:\PCB\GEN\DOORS : C:\PCB\GEN\DOORS.LST
Bulletins : C:\PCB\GEN\BLT : C:\PCB\GEN\BLT.LST
Scripts : C:\PCB\GEN\SCRIPT : C:\PCB\GEN\SCRIPT.LST
Directories : C:\PCB\GEN\SDIR : C:\PCB\GEN\DIR.LST
Download Paths (listing only) : C:\PCB\GEN\DLPATH.LST



Auto Setup For Conferences
--------------------------
When the SysOp wants to add a conference, he or she has two
alternatives: 1) Path and file names can be created manually by
the SysOp; or, 2) Path and file names can be duplicated from the
main board and edited.

Adding the Conference. To add a conference, follow the guidelines
below:

In the Options #3 screen of PCBSetup, the SysOp must first
increase the number of conferences by one or several to enable
the conference numbers in the Conference Menu Screen. Since
PCBoard 14.5 can support in excess of 65,000 conference, there
is normally no danger in exceeding conference capacity.

Once this number is changed, return to the Conference Menu
Screen and select one of the newly added conferences.








66




Since no name is indicated for the chosen conference, PCBoard
asks the SysOp if he or she would like to use configuration
defaults. If the answer is NO, the SysOp has the
responsibility of filling each highlighted blank on the
conference configuration screen.

When the SysOp indicates YES, three events occur.

1. PCBoard requests the conference name and the SysOp must
type one.
2. PCBoard requests a directory name for the new conference
and uses the conference name as a default if none other is
indicated.
3. Configurations must be chosen for bulletins, scripts,
directories and download paths. The SysOp has three
alternatives for each of these configurations. Each
configuration option has its own respective number.

Main Board Configurations are used for the newly created
conference. Whenever configurations for this conference are
changed, the Main Board Configuration changes as well.

Main Board Configurations are copied to a conference specific
file. The newly created conference, therefore, has its own
file which can be edited without affecting the Main Board
Configuration.

An empty conference-specific file is created. The Main
Board Configuration is not affected and the SysOp must
enter all pertinent conference information.


Conference Name
---------------
Default = None This is the name of your conference. Both upper and
lower case letters can be used.


Public Conference
-----------------
Y = The conference is public. It can therefore be accessed by any
caller with a particular security level that will be defined
below.
N = The conference is not public, but private. As a result, the
caller must be registered in the conference to access it.

Security Needed If Public
-------------------------
Default = 100 This field has four optional settings:

If the Public Conference parameter is set to (N), this field
is ignored since a caller must be registered in the conference
to have access.
Security Level = 0. All new callers and previous callers are
immediately registered in the conference. The Public
Conference parameter must be set to (Y).



67




Security Level = [Positive Number]. If new users are given a
security level in excess of this field, they have access to
the conference, but are not immediately registered. That is,
if the conference security level increases and the new user
security is exceeded, the new user is denied access to the
conference. All previous callers with a security level in
excess of this field have access to the conference. The
Public Conference parameter must be set to (Y).
Security Level = -1. All new callers are immediately
registered in the conference. All previously unregistered
callers are denied. The Public Conference parameter must be
set to (Y).


Auto-Rejoin Into Conference
---------------------------
Y = Upon the next call, a caller will be placed into a conference
from which he or she left. As a result, the caller need not use
the J)oin Command to change from the main board to this
conference.
N = A caller will be placed on the main board and will have to use
the J)oin Command to access this conference.


View Conference Members
-----------------------
Y = A caller will be able to view all members of this conference.
N = A caller will not be able to view members of this conference.


Number Of Message Blocks
------------------------
Default = 4 blocks This entry specifies the number of active or
inactive messages that will be stored. Each block holds 1024
messages based on the space between the low message number and the
high message number. If, for example, 4 blocks were specified, the
message base could hold 4,096 messages. The number of messages is
calculated by subtracting the low message number from the high
message number.


All Uploads Private
-------------------
Y = All conference uploads become private and are therefore not
available for immediate download by conference callers. Private
uploads are placed in the Private Upload Location specified
below.
N = All conference uploads are public and are available for
immediate download by callers. As a result, upload files are
stored in the Public Upload Location specified below.









68




All Messages Private
--------------------
Y = Upon entry, a message in this conference is flagged as private
and can be read by the recipient only. Once read, the message
may be unprotected (available for public eyes).
N = Normally, all conference messages are available for public
viewing unless further security is attached to them (Discussed
under User Commands).


Echo Mail In Conference
-----------------------
Y = PCBoard asks the caller if the message should be echoed to
other systems.
N = PCBoard does not pose the question to have the current message
echoed to other systems.


Additional Conference Security
------------------------------
Default = 0 This security represents the amount of additional
security given a caller when the conference is accessed. For
instance, if a caller has a security level of 75 and additional
conference security is listed at 25, the caller has a net security
level of 100 with all the capabilities given a user of this level.
Normally, when the caller leaves this conference, his or her
security will drop to its original level; however, a setting in
Options 1 of PCBSetup determines whether the PWRD file is re-read
after adjusting a caller's conference security.


Additional Conference Time
--------------------------
Default = 0 This field indicates the amount of additional time
given a caller when the conference is accessed. When the caller
leaves the conference, the additional time will not be subtracted
from his or her total time. The additional time will not interfere
with a non-sliding event.


MSGS File
---------
Default = C:\PCB\\MSGS This is the name and
location of the message base file for this conference. The filename
must have fewer than 8 characters with no extension. In a network
environment, this file must be stored on the file server to allow
equal access by all nodes.


Users Menu
----------
Default = C:\PCB\GEN\BRDM This is the file that a caller sees when
he or she J)oins this conference. Since some callers are granted
higher or lower security levels, user menus can be modified to
reflect differing user capabilities (See PCBSetup - Main Board
Configuration, Users Menu). PCBoard supports a graphics version of
this file and should be labeled BRDMG.


69





SysOp Menu
----------
Default = C:\PCB\GEN\BRDS This is the file that a SysOp sees when
he or she J)oins this conference. Any caller with a security level
of 100 or above will see this menu in lieu of the standard user
menu. PCBoard supports a graphics version of this file named BRDSG.
There should be no other versions of this file.


NEWS File
---------
Default = C:\PCB\GEN\NEWS This is the file that will be displayed
to a caller as he or she J)oins this conference or uses the NEWS
command. PCBoard supports a graphics version of this file which
should be labeled NEWSG. Further information of the NEWS file can
be found in the Options #1 portion of PCBSetup. Each conference may
have its own news file.


Public Upload Sort Preference
-----------------------------
Default = 2 This entry represents the sort preference of the public
upload DIR file of this conference. This information is needed by
the PCBFiler program to function properly. The sorting preference
is discussed under PCBFiler capabilities. Valid entries are:

0 - No Sort 3 - File Name (Descending)
1 - File Name (Ascending) 4 - File Date (Descending)
2 - File Date (Ascending)


Public Upload DIR Filename
--------------------------
Default = C:\PCB\\UPLD This is the name and
location of the public upload DIR file mentioned above. In a
network environment, this file must be located on the file server to
permit all nodes access to new uploaded files. UPLD contains the
name, size, date, and a brief description of uploaded files. This
file should only be edited by PCBFiler.


Public Upload File Location
---------------------------
Default = C:\PCB\\UPLOAD\ This represents the
directory that will contain all public uploaded files. The previous
entry stores file descriptions. This entry is the physical location
of those files. In a network environment, this path should be
shared on the file server and listed in the DLPATH.LST file to allow
all callers immediate access to uploaded files.










70




Private Upload Sort Preference
------------------------------
Default = 2 This entry represents the sort preference of the
private upload DIR file of this conference. This information is
needed by the PCBFiler program to function properly. The sorting
preference is discussed under PCBFiler capabilities. Valid entries
are:

0 - No Sort 3 - File Name (Descending)
1 - File Name (Ascending) 4 - File Date (Descending)
2 - File Date (Ascending)


Private Upload DIR Filename
---------------------------
Default = C:\PCB\\PRIVATE This is the name and
location of the private upload DIR file. The file contains the
name, size, date, and description of any private files uploaded to
the system. To edit this file, PCBFiler should be used.


Private Upload File Location
----------------------------
Default = C:\PCB\\PRIVUPLD\ This directory holds
the actual private uploaded files. Unlike the public upload path,
this path should not be included in the DLPATH.LST.


Door Menu
---------
Default = C:\PCB\\DOOR This file contains the menu
displayed to a caller in this conference who wishes to access a
door. The file may be modified using any text editor. PCBoard
supports a graphics version of this file named DOORG. Each DOOR may
be accessed by name or by number allowing the SysOp to design a DOOR
menu appropriate for his or her needs. If running a network and
storing this file on each local node's drive, each node should be
updated when this file changes. After specifying a text and
graphics editor under PCBSysMgr, the file can be edited by pressing
F2 or F3.


Door List
---------
Default = C:\PCB\\DOOR.LST This file contains a
list of batch files and optional security protection that
corresponds to each entry made in the DOOR menu of this conference.
DOOR creation is discussed further in Advanced Techniques.











71




Bulletin Menu
-------------
Default = C:\PCB\\BLT This file contains the menu
displayed to a caller who wishes to access a bulletin in this
conference. The file may be modified using any text editor
specified in PCBSysMgr. PCBoard supports a graphics version of this
file named BLTG. Since every listing in this menu is accessed
numerically, each entry should have a corresponding number. If
running a network and storing this file on each local node's drive,
each node should be updated when this file changes. After
specifying a text and graphics editor under PCBSysMgr, the file can
be edited by pressing F2 or F3.


Bulletin List
-------------
Default = C:\PCB\\BLT.LST This file contains a
list of batch files and optional security protection that correspond
to each entry made in the BLT menu of this conference.


Script Menu
-----------
Default = C:\PCB\\SCRIPT This file contains the
menu displayed to a caller who wishes to access the script
questionnaire in this conference. The file may be modified using
any text editor specified in PCBSysMgr. PCBoard supports a graphics
version of this file named BLTG. Since every listing in this menu
is accessed numerically, each entry should have a corresponding
number. If running a network and storing this file on each local
node's drive, each node should be updated when this file changes.
After specifying a text and graphics editor under PCBSysMgr, the
file can be edited by pressing F2 or F3.


Script Questionnaire List
-------------------------
Default = C:\PCB\\SCRIPT.LST This file contains a
list of batch files and optional security protection that correspond
to each entry made in the SCRIPT menu of this conference.


File Directory Menu
-------------------
Default = C:\PCB\\DIR This file contains the menu
displayed to a caller who wishes to access a particular file
directory in this conference. Since every listing in this menu is
accessed numerically, each entry should have a corresponding number.
If running a network and storing this file on each local node's
drive, each node should be updated when this file changes.









72




File Directory List
-------------------
Default = C:\PCB\\DIR.LST This file contains a
list of the filenames and locations of this conference's file
directories that correspond to the numerical listings in the DIR
menu. The file directories can be edited using PCBFILER. While
storing this file on individual nodes in a network environment, each
node should be updated when this file changes.


Conference Download Paths
-------------------------
Default = C:\PCB\DLPATH.LST This file contains a
complete listing of all directories that contain files available for
downloading. This file is for path information only. The file may
be modified by pressing F2. This file can be located on either a
local or network drive. However, if located on a local drive, all
nodes must be updated when this file changes.









































73




Command Line Parameters
=======================

General Information
-------------------
A file indispensable to PCBSetup execution is PCBOARD.DAT. This
file stores all configuration information from each screen. When
PCBSetup is initiated, PCBOARD.DAT is accessed, values are read in,
the SysOp is permitted to modify the data, and information is saved.
In previous versions, when PCBSetup was invoked, the PCBOARD.DAT
file used came from the current directory, whatever that directory
may have been. Now, however, the SysOp may indicate which
PCBOARD.DAT file to use by indicating its location at the command
prompt. If no alternate PCBOARD.DAT file is indicated, PCBSetup
uses the file in the current directory.

Format: PCBSetup [Drive & Path for PCBOARD.DAT File]

Examples: PCBSETUP C:\PCB1\PCBOARD.DAT
PCBSETUP C:\PCB2\PCBOARD.DAT
PCBSETUP CONFIG1


Uses
----
Since a SysOp may have multiple nodes, each node must have a
separate configuration; hence, separate PCBOARD.DAT files. With
this command line ability, a SysOp can edit configurations for other
nodes without leaving the current directory.






























74































































75




PCBSetup - Editing Files General Information
--------------------------------------------
In the File Locations 1 & 2 screens of PCBSetup, the SysOp
stipulates the location of each system file. Though some files
cannot be manually changed, others may be modified. When a field of
a changeable file is highlighted, a bar appears at screen bottom.
When the file is a parameter file, the highlighted bar says, "Press
F2 to edit the [filename] file." If the file represents a menu,
welcome screen, or other text file, the highlighted bar says, "Press
F2 to edit the [filename] file or F3 to edit the [filename]G file."

F2. When pressed, the screen to modify appears. This
screen is either a parameter screen or a text
file with no graphics. The former is necessary
for further customization of the system. The
latter can be modified in a favorite text editor
defined in PCBSysMgr (See Define Text and
Graphics Editors).

F3. When pressed, the screen to modify appears. This
screen is a graphic reproduction of the text
file described above. It can be modified in a
favorite graphic editor defined in PCBSysMgr
(See Define Text and Graphic Editors).


F2/F3 Changeable Files
----------------------
Below is a list of parameter, text, and optional graphics files that
can be modified using the above options. When highlighted, notice
the bar at screen bottom that indicates whether it's a parameter
file or a text (graphics) file.


Parameter Files Text/Graphics Files

PWRD WELCOME NEWASK
FSEC NEWUSER NEWREG
UPSEC CLOSED SCRIPT#
TCAN WARNING ANSWER#
PCBPROT.DAT EXPIRED
PCBML.DAT CNFN



Each of these files is discussed in File Locations 1 or File
Locations 2 of PCBSetup. Following is a more elaborate description
of each file and its modification.











76




Parameter Files


Password File
============= PCBoard Setup Utility
The PWRD file provides
a list of all Pass- Base Batch
security levels used Word Sec. Time KBytes Baud Limit
by callers of the ---------------------------------------
system. The listed 0 0 0 0 0
passwords allow 10 30 9999 0 40
users with similar 20 60 9999 0 40
security levels to have 25 120 31250 0 40
different capabilities. 30 60 9999 0 40
Unless a SysOp is 35 120 31250 0 40
experienced, this field 40 60 9999 0 40
should be left 45 120 31250 0 40
untouched. To the 50 60 9999 0 40
right is the PWRD 55 120 31250 0 40
screen seen when F2
is pressed. At the bottom are ALT functions that permit insertion
and deletion f lines. Below is a further description of each
field.


Password
--------
Whenever a caller logs into the system, PCBoard scans the PWRD file
for a password that matches the caller's password. If a matching
password is found or absent, PCBoard checks the appropriate security
level and affords the indicated time, byte, and batch limits to the
current caller. Normally, however, the password field should be
left blank.


Security Level
--------------
Whenever a caller logs into the system, PCBoard scans the PWRD file
for a password and security level that matches the caller's password
and security level. Normally, the password field is blank. As a
result, a caller's limits and privileges on the system are
determined by the listed security level. When PCBoard finds a
security level in the PWRD file that matches the caller's security
level, the caller is given the time, byte, and batch limits for that
security level.


Time
----
This indicates the number of minutes per day a user has access to
the system using the respective password. By setting different
times, the SysOp may control users by maintaining a standardized
security level, but providing diverse time allotments.






77




K Bytes and Base Baud Rate
--------------------------
This indicates the number of Kilobytes that a user may download per
day. The Kilobytes are calculated as a one to one ratio with the
Base Baud Rate.

If the Kilobytes field is set to 32767, there is no
limit on the number of Kilobytes that may be downloaded.
If the Base Baud Rate is 0, the indicated number of
Kilobytes may be downloaded regardless of baud rate.

If the Base Baud Rate were 1200 with a setting of 100
Kilobytes, a caller may download 100 Kilobytes worth of
files at 1200 baud; 200 Kilobytes at 2400 baud; 400
Kilobytes at 4800 baud; and 800 Kilobytes at 9600 baud.
However, the process functions in reverse as well.

If the Base Baud Rate were 9600 with a setting of 100
Kilobytes, a caller may download 100 Kilobytes worth of
files at 9600 baud; 50 Kilobytes at 4800 baud; 25
Kilobytes at 2400 baud MODEM; and 12.5 Kilobytes at 1200
baud.


Batch Limit
-----------
The Batch Limit indicates the number of files that can be downloaded
in a batch at one time by a caller. There is no limit on the number
of batches, however.


Download Security File
======================
The FSEC file permits two Drive/ File Pass-
defenses for downloadable Path Name Sec. word
files: a necessary security -------------------------------
level and a password. In H:\ALF\ *.* 75
scanning for the file to H:\ADL\ *.* 75
download, PCBoard first H:\DEV\ U.ZIP 20 ******
searches all directories H:\LUP\ *.* 15
listed in the DLPATH.LST H:\TEMP\ *.* 9
file. The Main Board and BLT*.* 9
each conference may have a PCB.ZIP 9 ******
separate DLPATH.LST file. PC1.ZIP 9 ******
When the file is found, the
FSEC file is scanned for a match. If the file or its path does not
exist in the FSEC file, the file may be downloaded regardless of
security and with no concern for a password. However, if the file
or its path does exist in the FSEC file, the user must have at least
the indicated security level and the appropriate password to
download the file. Above is the FSEC screen. Listed fields are
Drive/Path, Filename, Security Level, and Password. Following is a
further discussion of each field.






78




Drive\Path
----------
This field indicates the path specification for the File Name
indicated in field two. It includes a drive and directory that is
scanned for downloadable files. If this field is blank, any
matching filename is used regardless of drive or path location.
However, a user may only download files if he or she has a
sufficient security level and the appropriate password.


File Name
---------
This field indicates the files that may be downloaded from the
directory in field one. Options for this field follow:

When a Drive/Path is indicated with a filename, PCBoard
scans that path specification for the indicated file. If
the file is found and no password is specified, the
caller may download the file.

The filename may be a combination of text and wildcards
i.e. BLT*.*. In this case, all files in the specified
directory that begin with BLT may be downloaded given
sufficient security and the appropriate password.

The filename may be exclusively wildcards allowing a
user to download all files in the specified directory
given sufficient security and the appropriate password
i.e. *.*.

As a general rule, filenames with their respective directories
should be listed from most specific to least specific; that is, from
USERSYS.ZIP to *.*.


Sec
---
Once the directory or file is located, PCBoard determines if the
user has sufficient security. The user must have at least the
security level indicated in this field to download the file. If a
user lacks this level, he or she is denied access regardless of
knowledge of the appropriate password.


Password
--------
Once PCBoard determines that a file exists, the password field is
scanned. If blank, the user may download the file without entering
a password. If not, the user must enter the password to complete
the download. The password may be up to 12 letters long. Special
passwords do exist.

FREE. The SysOp allows a user to download the file, but
refrains from subtracting the number of bytes from the
user's authorized Kilobytes level (See PWRD file).
Though a user's Kilobyte level is not reduced, the
user's access time is reduced by the number of minutes
needed to download the file.

79




NOTIME. Like FREE, the user may download a file without
sacrificing any part of his authorized kilobyte level.
Furthermore, time remaining is not reduced by the time
spent downloading unless not reducing his or her time
would interfere with a scheduled event. Despite this
advantage, the user must have sufficient security.

If the password in this field is identical to the user's
login password, he or she may download the file without
inputing this password.

If the caller has previously given the password to view
a file, PCBoard remembers that the caller knows the
password. As a result, when the caller tries to
download any file with the same password, PCBoard does
not request the password.


Upload Security File
==================== Edit Upload Security File
Like the FSEC file, the UPSEC
file permits two defenses for Drive/ File Pass
uploading: a necessary security Path Name Sec. Word
level and a password. In ----------------------------
scanning for the file to H:\UP\ *.ARC 60 ARC
upload, PCBoard first searches H:\UP\ *.ZIP 110 ZIP
private and public upload 0
directories. The Main Board 0
and each conference may have 0
different upload paths. The 0
UPSEC file is scanned to 0
ascertain whether the file
may be uploaded. If the file does not exist in the UPSEC file, the
file may be uploaded regardless of security and with no concern for
a password. If the path is blank, any matching filename is used
regardless of location. If the uploadable file path exists in the
UPSEC file, the user must have at least the indicated security level
and the appropriate password to upload the file. Above is the UPSEC
screen. Listed fields are Drive/Path, Filename, Security Level, and
Password. Each field of the UPSEC file functions identically to the
FSEC file. However, the FSEC file prevents unauthorized downloads
while the UPSEC file prevents unauthorized uploads.


Trash Can
=========
The TCAN file is a tool to prevent certain, often lewd, words from
becoming user names. The file is merely a list. Words (four
lettered ones included) may be entered and followed with a RETURN.
PCBoard scans this file before allowing a new user to register. If
a word match occurs, the user must change his or her entry before
proceeding.







80




Protocol File
=============
The protocols contained
in the screen at right Edit Protocol File
represent modes in which
a MODEM transfers infor- Port Lock
mation. The protocols Use Type Size MNP Open Line DESC
are used in file transfers ------------------------------------
to verify data and correct A I 128 N N N ASCII
errors that may occur. X I 128 N N N XMOD
Some protocols are faster C I 128 N N N XMCRC
while others more O I 1024 N N N 1KXM
accurately resolve errors F I 1024 Y N N 1KXMG
that arise. Each internal Y I 1024 N N N YMOD
protocol, whose letter G I 1024 Y N N YMODG
under the USE heading Z D 1024 N N Y ZMOD
cannot be changed, is N I 0 N N N NONE
discussed in Appendix V.


Use
---
Each protocol is assigned a letter or a number giving 36
possibilities. This field holds the letter that a caller uses to
initiate the indicated protocol.


Type
----
I = Internal. Each protocol has been pre-programmed into
PCBoard. There are eight internal protocols including
NONE. These are normally sufficient for file transfer.
S = Shelled. PCBoard ventures outside (externally) its for
the to transfer a file. A common external protocol is
ZMODEM. Unlike an internal protocol, the user must define
each parameter.
D = DSZLOG. Like the shelled protocol, PCBoard looks outside
(externally) its programming to transfer a file. While
downloading or uploading, however, this protocol creates a
DSZLOG file that contains information about the file
transfer i.e. filenames, characters per second, thorough
put, success or failure, etc. The filename is indicated
in the BOARD.BAT file by the following setting: SET
DSZLOG = NODE1.DSZ. To use DSZLOG, each node must have
this setting in its respective BOARD.BAT file.


Size
----
For proper error correcting, protocols are broken into blocks with
each section holding the number of bytes indicated in this field.
An XMODEM--Checksum protocol, for instance, transfers files in 128
byte blocks. A 1K-XMODEM protocol transfers files in 1,024 byte
blocks.





81




Microcom Networking Protocol (MNP)
----------------------------------
Y = Only callers who have established an MNP or V.42 error
correcting connection may use the protocol. All protocols with this
setting are omitted from the transfer protocol list when a caller
connects without MNP or V.42 capabilities. N = All callers,
regardless of their connection, may use the protocol. All protocols
are displayed in the transfer protocol list.


Port Open
---------
Y = Upon shelling to DOS, the communication port is kept open.
N = Upon shelling to DOS, the communication port is closed.
As a result of the closure, available memory increases by
6 Kilobytes. This setting is recommended.


Lock Lines
----------
Y = When the protocol is initiated, the two status lines at
the screen's bottom are moved to the screen's top and
locked into place. If file transfers cause text to
scroll, the two lines still remain in place.
N = The two status lines at the screen's bottom are moved to
the screen's top. However, if file transfers cause text
to scroll, the two lines are scrolled with the text.


Protocol Description
--------------------
This field merely provides a description of the protocol. Each
internal protocol has been described, but may be changed. The user
is responsible for naming any further external protocols.


Multi-Language Data File
========================
PCBoard can support
multiple languages. Edit Language Table File
In Options 1 of
PCBSetup, a multi- Language Extension
lingual parameter is ---------------------------------------
listed. If set to (Y), 1 - English (Default)
PCBoard displays 2 - French FRE
this screen and 3 - Spanish SPA
anticipates a number
response from the
user. The SysOp has
the responsibility to create the new text using MKTXT145 (See
MKTXT145 in Utility Programs). Above is a sample PCBML.DAT file.
Below is a brief description of the two parameters.

Language
--------
When the Multi-Language parameter in Options 1 of PCBSetup is set to
(Y), the list of languages is displayed to the user. The list may
be appended once a new language file is created with MKTXT145.

82




Extension
---------
This field represents the extension of the PCBTEXT file. After
running MKTXT145 (See Utility Programs), a PCBTEXT file is created
that reflects the new language defined. If the PCBTEXT file has no
extension, it becomes the default language. Several PCBTEXT files
may exist, each with its own extension, if multiple languages are
available to the user.


In the above screen, the files that must exist to have multiple
languages available are PCBTEXT, PCBTEXT.FRE, PCBTEXT.SPA. The
first represents English; the second, French; and the third,
Spanish.


Text/Graphics Files
===================
Each text file is strictly limited to text characters. However, to
include color, flashing characters, and advanced attributes, ESC
codes may be included. PCBoard interprets these codes and displays
text accordingly. If the user's monitor cannot support these codes,
PCBoard ignores them and displays only text.

In previous versions, a G was appended to a filename to reflect its
graphic propensities. PCBoard still seeks these files if indicated
in one of the fields described below. If the file is absent, it
defaults to a file lacking the G appendage. PCBoard, however, can
support special macros for color (@X Codes) in files that lack the G
appendage. A list of ESC codes can be found in Appendix I.
Following is a further description of each text/graphics file.

Chained Files. A SysOp can chain files together by using a
%[Filename] structure. The percent sign must begin in column one
for the file to be displayed.


WELCOME FILE
============
Whenever a caller logs into the system, the caller sees information
contained in this file. This file supports ANSI graphics (See
Appendix I) and maybe modified with the text or graphics editor
specified in System Manager.


NEWUSER FILE
============
If a caller chooses to register as a new user of PCBoard,
information contained in this file is presented. Normally, when a
caller logs into the system under a name unrecognized by the user
file, PCBoard immediately prompts the caller with this screen and
provides an opportunity to register. This file supports ANSI
graphics (See Appendix I) and may be modified with the text or
graphics editor specified in System Manager.





83




CLOSED FILE
===========
This file is displayed to a caller when the system runs as a closed
board. It supports ANSI graphics (See Appendix I) and may be
modified with the text or graphics editor specified in System
Manager.

Like all text/graphics files, the CLOSED file can use @-variables to
provide a more personalized message. A closed board either prevents
unregistered users from accessing the system or prohibits a caller
from using a particular data line. As a result, this file is
displayed under two possible conditions.

In Options 1 of PCBSetup, the SysOp may set the Run As
CLOSED Board parameter to (Y). When set in this fashion
and a NEWASK file is absent, the CLOSED file is
displayed.

A caller's time has been set to zero minutes inside the
PWRD file. This prevents a caller from accessing the
system. The CLOSED file is then displayed.


WARNING FILE
============
For SysOps who charge caller's for access on their system, a WARNING
of subscription expiration is vital. Whenever a subscription is near
expiration, this file can be displayed. In PCBSetup, the SysOp can
specify how long before a caller's expiration that this file is
displayed. This parameter is located under Node/Event/Subscription
entitled Warning Days Prior to Expiration. This file supports ANSI
graphics (See Appendix I) and maybe modified with the text or
graphics editor specified in System Manager. Furthermore, (as
indicated by the above example) @-variables can be used for user
name, exact days before expiration, and similar pertinent
information.


EXPIRED FILE
============
When a caller's subscription has expired, the EXPIRED file is
displayed. Normally, this file is preceded by the WARNING file to
permit a caller sufficient time to renew his or her subscription.
This file supports ANSI graphics (See Appendix I) and may be
modified with the text or graphics editor specified in System
Manager. Furthermore, (as indicated by the above example)
@-variables can be used for user name and other pertinent
information.


CNFN FILE
=========
When a user invokes the Join a Conference command, the CNFN is
displayed. This file supports ANSI graphics (See Appendix I) and
may be modified with the text or graphics editor specified in System
Manager. Further, @-variables can be used for user name and other
pertinent information.


84




NEWASK FILE
===========
The NEWASK file functions as a normal script questionnaire (See
Scripts under Editing Main Board and Conference Configurations) and
may be created identically. However, questions inside the NEWASK
file are posed under two circumstances.

If the parameter for Run As CLOSED Board in Options 1 of
PCBSetup is set to (Y), PCBoard asks the NEWASK
questions in lieu of standard questions.

If the parameter for Ask NEWASK+Standard Questions in
Options 1 of PCBSetup is set to (Y), PCBoard poses both
NEWASK and standard questions to a new registrar.


NEWREG FILE
===========
The NEWREG file records a new caller's responses to NEWASK
questions. Each record contains the caller's name and the date of
registration. Each record is further separated by a line of
asterisks. Though standard questions may be posed, the NEWREG file
will contain only responses to additional NEWASK questions.


SCRIPT0 FILE
============
When a caller logs off the system, a set of questions may be asked
to enlist further information from the user. These questions are
contained in the SCRIPT0 file. The SCRIPT0 file functions as a
normal script questionnaire (See Scripts under Editing Main Board
and Conference Configurations) and may be created identically. If
this field is omitted, no logoff questions are posed. If no
questions are placed in the SCRIPT0 file, the file is merely
displayed upon logoff.


ANSWER0 FILE
============
Any questions whose source is a logoff questionnaire will have
responses stored in ANSWER0. Like a normal script questionnaire,
this file contains a copy of each question posed in SCRIPT0 and the
caller's response. If this field is omitted, no logoff questions
are posed.


GCTOPIC FILE
============
When a caller decides to group CHAT, the GCTOPIC file is displayed.
Once the caller is aware of the day's topic, he or she may agree to
join the session. This file supports ANSI graphics (See Appendix I)
and may be modified with the text or graphics editor specified in
System Manager. Furthermore, @-variables can be used for user name
and other pertinent information.





85




General Information
-------------------
In the Main Board Configuration and Conference Configuration screens
of PCBSetup, the SysOp can modify LST and text or graphics files.
When a field of a changeable file is highlighted, a bar appears at
screen bottom. When the file is a LST file, the highlighted bar
says, "Press F2 to edit the [filename] file." If the file
represents a menu or other text file, the highlighted bar says,
"Press F2 to edit the [filename] file or F3 to edit the [filename]G
file."

F2. When pressed, the screen to modify appears.
This screen is either an LST screen or a text
file with no graphics. The former is necessary
for further customization of the system. The
latter can be modified in a favorite text editor
defined in PCBSysMgr (See Define Text and
Graphics Editors).

F3. When pressed, the screen to modify appears.
This screen is a graphic reproduction of the
text file described above. It can be modified
in a favorite graphic editor defined in
PCBSysMgr (See Define Text and Graphics
Editors).


F2/F3 Changeable Files
----------------------
Below is a list of LST, text, and optional graphics files that can
be modified using the above options. When highlighted, notice the
bar at screen bottom that indicates whether it's an LST or a text
(graphics) file.


MENUS Configurations

Filename Description LST File Description

BRDM User Menu. DOORS.LST Location of DOORS
BRDS SysOp Menu. Files.
NEWS News File. BLT.LST Location of Bul-
DOORS Controls DOORS letin files.
menu display. SCRIPT.LST Location of
BLT Controls PCBoard Scripts.
menu display. DIR.LST Location of system
SCRIPT Controls Script directories.
displays. DLPATH.LST Complete list of
DIR Shows available all directories
directories to that contain files
caller. for download.


Each of these files is discussed in the Main Board Configuration and
Conference Configuration screens of PCBSetup. For further
information about their function in the PCBoard setup process,
consult these sections. Following is a more elaborate description
of each file and its modification.

86




User and SysOp Commands Menu
============================
General Information
-------------------
The Users and SysOp Command Files, like any text files, may be
edited by pressing the F2 or F3 key when the field is highlighted.
The file is displayed after a user or SysOp respectively logs into
the system. When in expert mode, a User or SysOp Commands Menu is
not displayed.

Creating a BRDM/BRDS Menu. Although both files are provided, the
SysOp can change the files or simply create different ones. When
the BRDM or BRDS file field is highlighted, press F2 to modify a
regular text menu or F3 for a graphic BRDMG (BRDSG) menu. Since the
SysOp chooses which commands a user may access, the User Commands
Menu can reflect what commands are available to a user. Normally,
the SysOp is given all commands, but sometimes, when a Conference
SysOp is used, some SysOp functions can be restricted.

Security Specific BRDM/BRDS Menu. The BRDM and BRDS menus may be
security specific. As a result, when a user or SysOp logs into the
system, the user or SysOp sees a particular User or SysOp Commands
Menu depending on his or her security level. Alternate menus are
created by appending the name with the security level. For example,
a user with a security of 85 would see a User Commands Menu entitled
BRDM85 (See File Naming Conventions under Advanced Techniques).

Language Specific BRDM Menu. Several BRDM or BRDS menus may exist
depending on the caller's or SysOp's requested language. The
language extension is attached to the filename to reflect the
language of the menu. For further information, consult File Naming
Conventions under Advanced Techniques.


NEWS File
=========
General Information
-------------------
When a caller logs into the system, a NEWS file is displayed. The
file normally contains information that the SysOp wants his or her
users to know.

Creating a NEWS File. When the NEWS file is highlighted, the SysOp
may press F2 or F3 to edit the screen. Once edited, the file should
be copied to the file server to permit access by all nodes. It may
be copied to each node's local drive. If the NEWS file changes,
however, it must be changed for each node.

Security Specific & Multilingual NEWS File. The NEWS file can be
security specific, multilingual, or both. For information about the
file name structure, consult File Naming Conventions under Advanced
Techniques.







87




DOORS
=====
General Information
-------------------
A DOOR is essentially an external program that permits exit of the
current application and entry into a different application. In
PCBoard, a DOOR may be accessed via the DOOR command (see command
description). PCBoard then removes itself from memory allowing the
alternate program to run. The alternate program may be a utility,
database program, external processing module, or even a game. After
the caller or user completes use of the alternate application, he or
she may exit the program and control is returned to PCBoard.


DOORS FILE
========== DOOR # NAME Description
The DOORS menu is ---------------------------------------
displayed to a caller 1 QMAIL Allows d/l and u/l
when he or she types of messages while
the OPEN or DOOR on line.
command. For each 2 Word Word Processing
DOOR, this menu 3 Lot Spread Sheet
normally lists a 4 DB Data Base Program
number, a DOOR 5 INV Inventory Program
name, and a 6 BACK Backup program.
description. However, 7 NICHE Bit-by-bit analy-
the SysOp may sis program for
customize this screen repairs.
to indicate any sort of 8 Game Space invaders.
menu information.

Creating DOORS Menu. When the DOORS field is highlighted, the SysOp
may press F2 or F3 to edit the screen. Since this is a text or
graphics file, the SysOp may use any menu scheme he or she finds
clear and informative enough for his or her callers and users. Once
edited, the file should be copied to the file server to permit
access by all nodes. It may be copied to each node's local drive.
If the DOOR menu changes, however, it must be changed for each node.

Security Specific DOOR Menus. The DOORS menu may be security
specific. As a result, when the DOOR or OPEN command is invoked, a
caller sees a particular DOORS menu depending on his or her security
level. Alternate DOORS menus are created by appending the name with
the security level. For example, a user with a security of 85 would
see a DOORS menu entitled DOORS85. If alternate security menus are
absent, PCBoard defaults to the normal DOORS menu (See File Naming
Conventions under Advanced Techniques).












88




DOORS.LST File
============== EDIT DOORS File
The DOORS.LST
file provides a list USER. DOOR. Batch
of all system File PASS Sec Login SYS SYS Path
DOORS. The Main ------------------------------------------
Board, as well as, QMAIL4 0 N Y N C:\PCB
each conference WORD 0 N N N C:\WP
has a separate
DOORS.LST file
although they may Press F2 to edit the DOOR File.
share the same file
if no discrepancies
exist. The file ESC=Exit Alt-R=Repeat Alt-I=Ins Alt-D=Del.
consists of seven
fields: filename, password, security level, LOGIN, USER.SYS,
DOOR.SYS, and path to batch file. Above is the DOORS.LST screen
that contains these fields and below is a further discussion of
those fields.


Filename
--------
To identify the DOOR, a name is placed in this field. This
represents the file that a SysOp can call from a DOS prompt to
execute the DOOR program. However, the filename cannot be an
executable file (one with an .EXE extension). Instead, the SysOp
should create a batch file that holds the .EXE file as well as any
setup information required for the execution of the DOOR program.

Each filename is numbered. This number should correspond to the
DOOR menu discussed earlier.


Password
--------
This field contains a password that a user must enter to access a
DOOR. This field may be left blank, but if a password is present,
PCBoard will prompt a user for the password regardless of the user
security level.


Security Level
--------------
A user must have this security level or greater to access the
respective DOOR. Each DOOR has its own security level requirements.














89




Login
-----
Y = PCBoard determines the security level of the current caller. If
the user's security level matches the DOOR security level
(parameter above), the user is automatically sent through a DOOR
to the respective application after NEWS and security specific
files are displayed. This feature is beneficial for SysOps who
want new users to go through an automatic registration or
verification process or to send specific users immediately into
an application.
N = A caller enters PCBoard and does not enter a DOOR unless he or
she performs the DOOR command from the PCBoard menu.


USER.SYS
--------
Y = A USER.SYS file is created to accommodate the Third Party
Application (TPA) program. The USER.SYS passes user information
to the DOOR program. Not all TPA's need this information.
N = A USER.SYS file is not created. As a result, user information
is not passed to the DOOR program.


DOOR.SYS
--------
Y = A DOOR.SYS file is created to accommodate the Third Party
Application (TPA) program. The DOOR.SYS passes some user
information and some system information to the DOOR program.
Not all TPA's need this information. The SysOp should read
documentation to determine this.
N = A DOOR.SYS file is not created. As a result, user and system
information is not passed to the DOOR program.


Path To Batch File
------------------
In this field, the SysOp specifies the location of the batch file to
run the DOOR application. The batch file itself must be located in
this directory; however, it may branch to other locations and
utilize files in other directories.

Security Specific DOORS.LST. The DOORS.LST file may be security
specific. As a result, a caller's security can determine which
DOORS he or she may access. Alternate files are created by
appending the DOORS.LST filename with the security level. For
example, a user with a security of 85 would have access to DOORS
contained in the DOORS85.LST file. If alternate security files are
absent, PCBoard defaults to DOORS.LST (See File Naming Conventions
under Advanced Techniques).










90




Creating Remote Mode DOORS. In remote mode, a DOOR requires a COMM
port for proper execution. The DOORS are created like those in
local mode, but further manipulation is necessary. Three
alternatives exist:

The COM port routines may be written directly in the
application program. This provides greatest control, but the
most work.

Communication routines
may be directed by the watchdg1 on (Monitors Car-
DOS command CTTY prior rier in DOOR)
to initiating the DOOR echo off (No DOS echo)
application. To the ctty com1: (COM1 output)
right is a sample batch type demo1 (function)
file that uses the CTTY ctty con (Output to
command. As a result, screen)
the caller sees any echo on (DOS echo on)
output sent to his line watchdg1 off (No monitoring
from the host while the in DOOR)
host or local node board (PCBoard)
remains unchanged.

Instead of using the CTTY command, a program called DOORWAY
may be used. It too redirects screen output and keyboard
input through the COM port, but provides several additional
features that add reliability and further compatibility.

Bulletins
=========
General Information
-------------------
Bulletins hold information like an extended NEWS file. A bulletin
may contain any information that a SysOp wants his or her users to
know. Common uses of bulletins are for price information, extended
documentation, explanations of complex subjects, and a list of
users. To properly create and modify bulletin menus and files, a
SysOp must know the fundamentals of three files: BLT (Bulletin
Menu), BLT.LST (Bulletin Location), BLT# (Actual Bulletin).




















91




BLT MENU
======== Bulletin Listing
The BLT menu is
displayed to a caller Last
who invokes the B Num Update Description D/L As
command from the --------------------------------------
Main Board command 1 08-07-90 PCBoard List BLT1.ZIP
prompt. The B 2 07-19-90 Dev. Info. BLT2.ZIP
command indicates a 3 05-11-90 Order Prices BLT3.ZIP
request by a caller to 4 08-07-90 Orders BLT4.ZIP
list bulletins available 5 05-17-90 DOORS BLT5.ZIP
to him or her on the
current system. A normal menu consists of a numbered list of
available bulletins, a date of the bulletin's last modification, a
description of the bulletin, and the filename to download the
bulletin information. The screen above indicates these fields.

Creating BLT Menu. When the BLT field is highlighted, the SysOp may
press F2 or F3 to edit the screen. Since this is a text or graphics
file, the SysOp may use any menu scheme clear and informative enough
for his or her callers and users. Once edited, the file should be
copied to the file server to permit access by all nodes. It may be
copied to each node's local drive. If the bulletin menu changes,
however, it must be changed for each node.

Security Specific Menu. Unlike the DOORS and DIR menus and file
listings, the BLT menu is not security specific. As a result, every
caller and user, regardless of his or her security, sees the same
Bulletin Menu.

BLT.LST File
============
The Main Board and each
conference has a bulletin Main Board Configuration
listing file entitled BLT.LST.
In this file, the SysOp places List of BLT Path & Names
the paths and filenames for ------------------------------
each bulletin in the conference. 1) C:\PCB\GEN\BLT1
Each path and filename is 2) C:\PCB\GEN\BLT2
numbered to correspond with 3) C:\PCB\GEN\BLT3
the BLT menu discussed 4) C:\PCB\GEN\BLT4
earlier. To the right is the 5) C:\PCB\GEN\BLT5
BLT.LST screen. Notice at 6) C:\PCB\GEN\BLT6
screen bottom that a SysOp
may insert, delete, or repeat a line.

Creating BLT.LST. The BLT.LST holds path information for each
bulletin file. The BLT.LST should normally be on the file server to
allow all nodes access, but may be copied to each local drive. If
bulletins change, however, the BLT.LST must be changed for each
node.








92




Example. From the example above, the following information
can be gathered. Bulletin one is located in directory
C:\PCB\GEN. The file displayed when a caller invokes bulletin
one in the Main Board is BLT1.

Creating BLT#. The BLT# file holds an individual bulletin. The #
indicates the bulletin number to which the file corresponds in the
Bulletin Menu. For example, BLT1 refers to Bulletin 1 in the
Bulletin Menu.

Since each bulletin is merely a text or graphic file, it may
employ @X Color Codes (See Appendix VIII) and @-Variables (See
Appendix VII).


SCRIPTS
=======
General Information
-------------------
Often times, a SysOp wants specific information from his or her
users. A script questionnaire permits the SysOp to take an order
that includes (but is not limited to) name, shipping address,
pertinent sizes, credit card numbers, birthdate, and other data. To
create a Script Questionnaire, the SysOp must create or modify the
following three files: SCRIPT (Script Menu), SCRIPT.LST (System
File Information), SCRIPT# (Actual Script Text).


SCRIPT MENU
-----------
After calling into the
system, the SCRIPT Script Questionnaires Available
menu is displayed to
a caller who invokes 1) Enter Board Information into list.
the S command from 2) Order a new copy of PCBoard.
the Main Board 3) Renew support on Salt Air BBS.
command prompt. 4) Order a Plain Vanilla Modem.
The S command
indicates a request to For other orders call 1-800-356-1686
fill out a script any time between 8 am & 5 pm MST.
questionnaire created
by the SysOp of the current system. The menu displayed shows a
numerical listing of the script and a description of the script
questionnaire.

Creating SCRIPT Menu. When the SCRIPT field is highlighted, the
SysOp can press F2 or F3 to edit the menu. Once edited, the file
should be copied to the file server to permit access by all nodes.
It may be copied to each node's local drive, but must be changed for
each node if the script menu changes.

Security Specific SCRIPT Menus. Unlike the DOORS and DIR menus, the
SCRIPT menu is not security specific. As a result, every caller,
regardless of his or her security, sees the same script
questionnaire menu.




93




SCRIPT.LST File
---------------
The Main Board and
each conference has Main Board Configuration
a script listing file
entitled SCRIPT.LST. SCRIPT ? Files ANSWER Files
In this file, the SysOp ------------------------------------
places the paths and C:\PCB\GEN\SCRIPT1 H:\MAIN\ANSWER1
filenames for script C:\PCB\GEN\SCRIPT2 H:\MAIN\ANSWER2
questionnaires and C:\PCB\GEN\SCRIPT3 H:\MAIN\ANSWER3
their respective C:\PCB\GEN\SCRIPT4 H:\MAIN\ANSWER4
answer files. Each
script path is
numbered to
correspond with the SCRIPT menu discussed earlier. Above is the
SCRIPT.LST screen. Notice at screen bottom that a SysOp may insert,
delete, or repeat a line.

Creating SCRIPT.LST. The SCRIPT.LST holds the script and answer
path for the questionnaire. The script location should normally be
on the file server to allow all nodes access, but may be copied to
each local drive. If the script changes, however, it must be
changed for each node. The ANSWER# file is created automatically in
the indicated path directory when a caller requests a script
questionnaire. It must be located on the file server for proper
question/answer recording.

Example. From the example above, the following information
can be gathered. Script1 (the first script questionnaire)
is located in directory C:\PCB\GEN\SCRIPT1. Whenever a
caller invokes this questionnaire, all answers are placed in
a file named H:\MAIN\ANSWER1.

Each set of answers from individual callers is separated by a hard
page break. The ANSWER file remains until it is physically erased.

Upon its absence, the file is recreated when a caller invokes
another script questionnaire.

Creating SCRIPT#. The SCRIPT# file holds the actual questionnaire
text. Once complete, the questionnaire should be saved as SCRIPT#
where # indicates the number of the script questionnaire.

















94




The SysOp
may use any Any Title
text or Script Questionnaire Example
graphics
editor to This is an example of the Script Ques
create the list tionnaire. The first six lines are
of questions. reserved for a comment.
The length of ;
each line What is your name?
should not What is your birthdate?
exceed 70 How many brothers do you have?
characters. ;
;This is the end of the script
;questionnaire.


Each line of text must be preceded by a semicolon (;). In
this way, PCBoard can determine which lines of text are
questions and which are merely displayed for clarity,
description, or general emphasis.

Any line of text that is not preceded by a semicolon is
considered a question with the exception of the first six
lines.

Script Header. The first six lines of the questionnaire are
reserved for a title or brief description. These lines do not need
a preceding semicolon. They are displayed at the script's
initiation. The LOGOFF script questionnaire, however, does not use
the first six lines as a header, but, instead, immediately begins
script processing. If there is not ANSWER file specified for the
LOGOFF questionnaire, the LOGOFF file is displayed as a normal text
file and requires no semicolons to delineate text.


























95




Directories
===========
General Information
-------------------
Many Bulletin Board Systems are used as external mailing systems.
As a result, a SysOp can provide hundreds, sometimes thousands of
files that callers may download. These files are contained in file
directories and may be grouped by whatever similarity the SysOp
finds prudent. Common file directories might be text files, graphic
files, utility programs, DOOR programs, and recent updates.

Each group of files normally has its own directory. To create and
manipulate these directories, an understanding of three files is
necessary: DIR (Directory Menu), DIR.LST (System File Information),
DIR# (List of File Paths).


DIR Menu
--------
The DIR menu is
displayed to a caller Conference File Directory
who invokes the F
command from the 1) PCBoard Software text files.
Main Board command 2) PCBoard 14.5 Program Files.
prompt. The F 3) PCBoard Multilingual Files.
command indicates a 4) PCBoard 12.0 & Earlier DOOR Programs.
request for a File 5) PCBoard 14.x DOOR Programs.
Directory Listing. The6) PCBoard Recent DOOR Program Uploads.
Main Board and each 7) PCBoard 12.0 & Earlier Utility Progs.
conference has its 8) PCBOard 14.x Utility Programs.
own DIR listing. The 9) PCBoard Recent Utility Programs.
menu displays a
numerical listing of each directory and a description of the
contents of that directory.

Creating DIR Menu. When the DIR field is highlighted, the SysOp may
press F2 or F3 to edit the menu. Since this is a text or graphics
file, the SysOp may use any menu scheme clear and informative enough
for his or her callers and users. Once edited, the file should be
copied to the file server to permit access by all nodes. It may be
copied to each node's local drive. If the script menu changes,
however, it must be changed for each node.

Security Specific DIR Menu. The Directory Menu is not security
specific. As a result, any caller or user will see the same list of
directories regardless of his or her security level.













96




DIR.LST File
------------
The Main Board and
each conference has Main Board Configuration
a directory listing file
entitled DIR.LST. In DIR Text File Hard Disk
this file, the SysOp Name & Path Subdirectory Sort
places the path and ------------------------------------
filename for each file C:\PCB\GEN\DIR1 C:\PCB\GEN 0
in a particular
directory. The screen Sorts: 1=Filename (A) 3=Filename (D)
to the right contains 0=None 2=Filedate (A) 4=Filename (D)
four fields: DIR Text
File Name & Path, Hard Disk Subdirectory, Sort, and Directory
Description. The first three are normally displayed. Below is a
further description of each field.


DIR Text File Name & Path
-------------------------
Each DIR file contains a list of paths and filenames. In the
example above, the file DIR1 may contain several different paths and
filenames, but not the files themselves. From the DIR.LST screen,
the contents of a DIR file cannot be displayed. PCBoard utilizes a
separate utility called PCBFiler to manipulate the contents of DIR
files. This file management program is discussed in depth under
PCBFiler.


Hard Disk Subdirectory
----------------------
This represents the hard disk directory where all filenames listed
in the DIR file can be found. The directory in this field holds the
physical files whose names are held in the DIR file.


Sort
----
Inside PCBFiler, physical filenames are listed according to the
sorting preference specified in this field. No one sorting
preference has an advantage over another. Instead, each preference
is determined by SysOp needs. Below is a list of sorting
preferences.

0 = No Sort
1 = File Name (Ascending)
2 = File Date (Ascending)
3 = File Name (Descending)
4 = File Date (Descending)










97




Directory Description
---------------------
When the SysOp presses F2, the two previous fields change to a
directory description. This field is displayed to a caller or user
when he or she scans a list of directories. Furthermore, when the
directory is edited using PCBFiler, the directory name is shown.

Security Specific DIR.LST. The DIR.LST file may be security
specific. As a result, a caller's security can determine which
directories he or she may access. This technique is not recommended
(See File Naming Conventions under Advanced Techniques).

Creating DIR#. Inside the DIR.LST file is a list of DIR Text File
Names and Paths. Each of these text files contains a list of
directories that indicate the location of physical files. To
properly manipulate these files, the SysOp should use the PCBFiler
utility. It is specifically designed to handle directory and file
maintenance.


Download Paths
==============
General Information
-------------------
When accepting callers via Modem, a system normally has several
files available for callers to download. Downloading simply refers
to a process in which a caller copies a file from the host system.
The file is sent over the Modem into the caller's local system. The
SysOp places these downloadable files into Download Directories that
are controlled by the DLPATH.LST file.


DLPATH.LST File
---------------
The Main Board and
each conference has Main Board Configuration
a file that contains all
download paths. The Enter a list of download paths
file, entitled ---------------------------------------
DLPATH.LST, 1) C:\PCB\GEN\
contains only 2) C:\PCB\HELP\
directory listings. 3) H:\TEMP\
When a caller wishes
to download a file,
PCBoard searches
the listed directories for downloadable files. Above is the
DLPATH.LST screen.












98




Creating DLPATH.LST. The SysOp uses the ALT functions at screen
bottom to add or delete download paths. Although the SysOp
specifies download paths in this screen, the utility, PCBFiler, is
specifically designed to manipulate directories and files.

Security Specific DLPATH.LST. The DLPATH.LST is security specific.
As a result, a caller's security level can determine which download
paths he or she may access (See File Naming Conventions under
Advanced Techniques).


Making a File Downloadable
--------------------------
The SysOp can place a file inside one of the directories specified
in DLPATH.LST to make it available for download. Of course, this
doesn't provide a listing for the file. It merely places the file
in the directory and only callers aware of its existence can
download it. To add a file listing that includes the filename,
date, and description, the SysOp can follow the following steps.

DIR.LST. As previously discussed, the DIR.LST file holds the names
and paths of several text files. Each file represents a different
directory that contains the names of several files within that
directory. Among others, the DIR.LST file consists of DIR Text
Filename & Path and Hard Disk Subdirectory fields.

Run PCBSetup to edit the DIR.LST file.
Add definitions for the new DIR file or locate an
existing DIR file that will eventually hold the file to
download.
Make note of the Hard Disk Subdirectory and exit
PCBSetup.
At the DOS prompt, copy the file to the Hard Disk
Subdirectory listed in the DIR.LST file for the
directory in which the file will eventually be stored.


DLPATH.LST. The DLPATH.LST file, as indicated earlier, holds the
directory names that hold all files available for download. Any
file intended for download availability must reside within one of
the indicated download paths.

Insure the Hard Disk Subdirectory path (same as above)
is also an entry in the DLPATH.LST file.


PCBFiler. Although PCBFiler is discussed in a later section, the
file is most easily added to a directory listing by this utility.

Enter the PCBFiler utility by typing PCBFILER within the
PCB sub-directory, accessing it from the Call Waiting
Screen, or shelling from PCBoard with ALT D.
Choose Edit DIR Files from the main PCBFiler menu.
Select either the Main Board or Conference Directory to
edit depending on whether the intended file was placed
in the main board or the conference DIR.LST file.



99




Indicate the DIR number to which the file will be added.
When asked to Include files found on DISK that are not
listed in the DIR file?, indicate Y. (The remaining
question is optional.)
Once inside PCBFiler, locate the file name previously
copied to the Hard Disk Subdirectory in the DIR.LST
file. It should have a DSK to the left of the file
name.
Under the description heading for that file, type a
description (adding secondary lines if necessary).
Save the change upon exit. The file is now available for
download in the directory chosen earlier.















































100




General Information
-------------------
Each of the 14 SysOp functions is designed specifically for the
SysOp. The SysOp may employ a co-SysOp user, but this is not
recommended since system security may be jeopardized. Ultimately,
however, user access to the system must be determined by the
individual needs of the SysOp.


PCBoard - SysOp Menu Commands
-----------------------------
The SysOp's Main Menu includes all SysOp and user commands.
However, below is a list of SysOp commands only. Following will be
a detailed description of each.



1) List/Print Caller's Log 8) Pack the User's File
2) List/Print User's Log 9) Exit to DOS from Remote
3) Pack/Renumber Messages 10) Perform DOS Function
4) Recover a Killed Message 11) View Other Node Users
5) List Message Headers 12) Logoff Alternate Node
6) View any System File 13) View Alternate Node Caller Log
7) User Maintenance 14) Drop Alternate Node to DOS



(1) View/Print/Delete Caller's Log
-----------------------------------
SubCommands: V P S D

PostCommands: None

Whenever a caller performs a function i.e. logs in, reads a message,
joins a conference etc., the function is recorded in the Caller's
log. Using this command, the SysOp may view past activity in the
caller's log.

SubCommands:

V View. The SysOp may analyze the caller's log. It will be
displayed in a Last-in, First-out order so the most recent
activities are listed first.

P Print. The SysOp may print the caller's log. Like the
above, the caller's log will be displayed in a Last-in,
First-out order. Normally, it is advantageous to perform an
ALT- T (Top of Form) to insure the paper is correctly
positioned.

S Scan. The SysOp may search for a particular string within
the caller's log. PCBoard asks for the string and highlights
all identical strings in the caller's log. Like other text
scans, boolean operands can be used (See User Commands).

D Delete. The caller's log will be erased immediately and a
new one created. The old caller's log cannot be recovered
once deleted.

101




(2) View/Print User's List
---------------------------
SubCommands: V P
PostCommands: None

The user's list includes information about each user who is
registered on the system. For a more thorough description, please
see User Maintenance under PCBSysMgr.

SubCommands

V View. The SysOp may analyze a numerical list of registered
users. The list includes name, location, last date logged
on, last time logged on, and time spent while logged on.

P Print. The numerical list of registered users mentioned
above will be printed.


(3) Pack/Renumber Messages
---------------------------
SubCommands: None
PostCommands: None

The message base may be packed to free space on a hard disk by
eliminating old or previously read messages. The message base of
the current conference will be packed. When this SysOp function is
invoked, questions are asked (see screen at right) that correspond
to each field below. For a further discussion of each parameter
below, see PCBPack under Utility Programs.

Index Y = The index file is verified and recreated with
all active and inactive messages. No messages
are deleted.
N = A new index file is created. Messages are
deleted or saved based on information that
follows.

Fast Pack Y = PCBoard provides all appropriate prompts to pack
or renumber the message base. However, while
PCBoard creates the new index file, processing
will not be displayed.
N = PCBoard displays the processing information
after all prompts are exhausted.

DATE This field represents a date in the format of
MMDDYY. Any message with a date prior to this
field is removed. Any message created on the
specified date is not deleted.










102




Rec/Priv Y = All messages that have been received by their
intended recipient are deleted.
N = Even though a message has been read by its
intended recipient, it is not deleted from the
message base.

Renumber Y = The SysOp must input a number for the first
message in the message base. From that point,
messages will increment by 1. N = The message
base will not be renumbered upon packing. This
option is recommended since any renumbering
resets message pointers.

Keep Y = All messages that are private and have not been
read by their intended recipient are not
deleted.
N = Although a message has not been read by its
intended recipient, it is deleted if its bound
by another packing parameter such as date.

Backup Y = Normally, a message base is copied before its
packed and similarly named with a BAK extension.
Once packing is complete, this file is removed.
N = The backup message base file is not deleted.
This option is recommended in case the SysOp
needs to reinstate the former message base.

Required All nodes must be logged out of PCBoard. The
function will indicate Disk Free Space and Free
Space Required. Insure the former is greater
than the latter.


(4) Recover A Killed Message
-----------------------------
SubCommands: #
PostCommands: None

The SysOp may recover any previously killed message as long as the
message base has not been packed since the message was killed.
SysOp command (5) can be used first to insure the message exists.

SubCommands # This is the number of the message to be
reactivated.















103




(5) List Message Headers
-------------------------
SubCommands: # F Y S NS + - TS USER
PostCommands: None

Each message has a message header. It consists of the message
number, the reference number, the name of the sender, the name of
the recipient, and the subject of the message. The reference number
is a connection between the message that was formerly sent and the
current reply. This command is similar to the Quick Scan command.
Both inactive and active messages are displayed, however.

SubCommands # PCBoard provides a range of available messages.
The SysOp types the message number from which he
or she wants to begin scanning the message
headers. PCBoard will list all message headers
from the number indicated.
F The message base is scanned for all messages
left by the current user.
Y The message base is scanned for all messages
sent to the current user.
S All messages that have not already been read
will be scanned and displayed.
NS Messages will be displayed in Non-Stop Mode
(void of all More? prompts).
+ When appended to a message number, PCBoard
displays all messages in forward-numerical order
from that point.
- When appended to a message number, PCBoard
displays all messages in reverse-numerical order
from that point.
TS The header of each message is scanned for the
indicated text. This feature utilizes boolean
operands discussed in User Commands.
USER The message base is scanned for messages left to
or received from the indicated user.























104




(6) View Any File On Screen
----------------------------
SubCommands: [filename]
PostCommands: None

The SysOp may view any text file. PCBoard will position page breaks
for ease of reading. Although this SysOp feature allows any file to
be viewed, only ASCII files can actually be read.

SubCommands [filename] The text file (ASCII) may be stacked next
to the 6 or it may be entered at the
appropriate view-file prompt after the 6.
PCBoard accepts the full DOS specification
for the text file entry. If no alternate
path is indicated, PCBoard scans the
directory which contains the file
PCBOARD.EXE.


(7) User Maintenance
---------------------
SubCommands: A C D F L P Q S U #
PostCommands: None

This function permits the SysOp to add, modify, or delete a user
record. The function is identical to the System Manager's Edit
User's File option. However, it is more easily accessed and
reflects condensed user information. Any user with this ability
cannot create, change, or view a record with a greater security than
his or her own.

SubCommands A Add. The SysOp may add a user record. Like the
Edit User's File option of System Manager, the
SysOp must provide essential information to
create the record. This includes name,
password, phone numbers, and conference
registration. Any user with this ability cannot
create a record with a security level greater
than his or her own.

C Change. Once a user record is found, it can be
modified by this option. Each information field
will contain the current user information. If
ENTER is pressed, the field will remain the
same; otherwise, the SysOp may change the field
and proceed. Any user with this ability cannot
change a record to have a greater security level
than his or her own.











105




D Delete. When chosen, the delete flag of the
user record will be set to (Y). Upon user
record packing, the record is deleted from the
user file.
F Find. The SysOp enters the name of the user
whose record he or she wants to find. Once
found, the record may be modified, deleted, or
printed.
L List. PCBoard will show each record starting
with the second (or the first if the current
user holds record one of the user file). Like
the # subcommand, the SysOp can list a
particular record by typing its user record
number.
P Print. By typing P, all user records are
printed.
Q Quit. The SysOp returns to the PCBoard Command
Menu.
S Scan. The SysOp enters a text string. PCBoard
will search the user name of each user record
for the text string. If found, the record
number, user name, and password will be listed
for each user. This feature utilizes boolean
operands discussed in User Commands.
U Undelete. If the SysOp deleted a user record
and has not packed the user's file, the user
recorded may be undeleted. The delete flag will
be set to (N), but the security level for the
user will not revert to its former level. As a
result, the SysOp must change the record to
restore the appropriate security.
# A user record is listed when the SysOp types a
user record number.


(8) Pack User's File
---------------------
SubCommands: None
PostCommands: None

Like the Pack Users File option of PCBSysMgr, this function permits
the SysOp to condense the user file by eliminating previously
deleted, old, expired, or locked out records. Only the person in
record one may pack the user's file.

Locked Out Y = PCBoard will not delete users with a security
level of 0 (those who have been locked out of
the system).
N = All users with a security level of 0 (those with
a "Y" in the locked out field of their user
record) will be eliminated.

Purges This field represents a date in the format of
MMDDYY. PCBoard eliminates users who last used
the system on or before this day.





106




Security Any user with a security level of or above this
level will not be deleted despite his last logon day
or any other removal characteristic.

Fast Pack Y = PCBoard provides all appropriate prompts to pack
the user's file. However, while PCBoard creates
the new index file, processing will not be
displayed.
N = PCBoard displays the processing information
after all prompts are exhausted.

Required All nodes must be logged out of PCBoard. The
function will indicate Disk Free Space and Free
Space Required. Insure the former is greater than
the latter.


(9) Exit To DOS (Remote)
-------------------------
SubCommands: None
PostCommands: None

This function allows the SysOp to drop to DOS while at a remote
location. To expedite this remote function, the program DOORWAY
seems to be the most efficient and most compatible with PCBoard
code.


(10) Perform DOS Function
--------------------------
SubCommands: None
PostCommands: None

This function allows the SysOp to perform a DOS command while in the
PCBoard environment. The status of the DOS function will not be
displayed.

Remote While using PCBoard at a remote location, any DOS
command that requires the user to respond to a DOS
prompt cannot be used. If such a command is
invoked, the computer will freeze and PCBoard will
not recycle.

Local Locally, any DOS command may be invoked without
concern for DOS prompts.














107




(11) View Other Node Users
---------------------------
SubCommands: None
PostCommands: None

This function allows the SysOp to view the current actions of other
nodes in the network. This SysOp feature functions like the WHO
command for users (See User Commands).


(12) Logoff Alternate Node
---------------------------
SubCommands: #
PostCommands: None

The SysOp may disconnect a caller who resides on a different node.
Normally, the SysOp may implement this action if the caller is
performing dangerous or security breaching activities. If a caller
is transferring a file when the SysOp requests an automatic logoff
for him or her, the caller will not be disconnected until the
transfer is complete.

SubCommands # This indicates the node number to log off the
system.


(13) View Alternate Node Caller Log
------------------------------------
SubCommands: # A S
PostCommands: None

This function allows the SysOp to view the caller's log of any node
in the system. The node number may be stacked by the function
number i.e. 13 6. However, to insure proper execution, the CALLER
file location must be the same for all nodes on the network.

SubCommands # This indicates the node number of the log which
the SysOp wishes to view.
A Each log from every node is displayed.
S PCBoard requests text for which to scan. Like
other text scans, the SysOp may use boolean
operands (& and |) to search the caller's log.
(See User Commands).
















108




(14) Drop Alternate Node To DOS
--------------------------------
SubCommand: #
PostCommand: None

From the SysOp's current node, he or she may drop another node to
DOS. The node can be Dropped to DOS even while it sits at the Call
Waiting Screen.

SubCommands # This is the node number that the SysOp wishes to
drop to DOS.
















































109




General Information
-------------------
Like most attributes of PCBoard, the SysOp provides security levels
for each user command as defined in the User Security Levels option
of PCBSetup. A caller must have an equal or greater security level
for command access.

Since some callers are granted higher or lower security levels, user
menus can be modified to reflect differing user capabilities (See
File Naming Conventions under Advanced Techniques).

In each command description that follows, at least three listings
are provided: Command, SubCommands, and PostCommands. The Command
accesses the procedure and is usually the first one or two letters
of the menu name. Subcommands are available only before or upon
executing each command and may be stacked on the same line. Once
invoked, the Postcommands become available and the subcommands are
disabled unless otherwise indicated.


Boolean Text Searches
---------------------
PCBoard 14.5 allows boolean text searches in several of its
commands. A boolean operand is merely a test that a search must
successfully meet. Normally, this is an AND or an OR. In PCBoard,
these operands are denoted with a & and | respectively and are used
in the 1, 13, 7 S, TS, Z, USERS, and B S commands. If, for example,
a user wanted to search for messages from a particular person in a
particular company, he or she might type: TS IBM & John. PCBoard
would then flag all messages that contain IBM and John. If,
however, a user wanted to search for messages from or to a
particular company(s) or person(s), he or she might type: TS (IBM |
John) & Mary. PCBoard would then flag all messages that either
contain IBM or John and also contain Mary. Fields may be enclosed
by parenthesis. Each parameter may be enclosed by quotes if
characters such as ( ) | or & are part of the scanned text.


PCBoard - User Commands
-----------------------
Below is the Main Menu for system users. Notice that all SysOp
commands previously described are omitted. A detailed description
of each command follows. Multi-letter commands can be abbreviated
to the first two letters.















110




User Commands
=============

Abandon Conference
------------------
Command: A
SubCommands: None
PostCommands: None

When invoked, PCBoard exits the current conference and returns to
the main board. If the current conference is the main board,
nothing occurs.


Bulletin Listings
-----------------
Command: B
SubCommands: # A D N R S NS
PostCommands: None

PCBoard displays the Bulletin Menu. Bulletins available must be
defined in PCBSetup under the Conference Configuration option. In
the Menu Listing field of this screen, the menu and path/name should
be defined. To the right is a simple bulletin example.

SubCommands # This indicates the number of the bulletin to
view i.e. 1 2 3 etc.
A All bulletin listings are displayed.
D PCBoard enters download mode and prepares to
download the chosen bulletin.
N Used in conjunction with the A subcommand, only
bulletins new to the callers are displayed. The
"new" bulletin is determined by the callers last
date of logon and the creation date of the
bulletin.
R When invoked, PCBoard re-displays the bulletin
listings.
S When combined with the A subcommand or a list of
bulletins to scan, this command searches for
text in the specified bulletins. If the text is
found, the entire bulletin is displayed.
NS The bulletin chosen for viewing is displayed in
non-stop mode. At the end of each page, PCBoard
will not show the MORE? prompt.















111




CHAT Between NODEs
------------------
Command: CHAT or NODE
SubCommands: # G A U
PostCommands: Q E U H

A user may CHAT with a person on a node or group of nodes. PCBoard
displays the status of each node. In this way, the user can
determine who is available for CHAT and who is not. To the right is
a CHAT session.

SubCommands # User begins CHAT with a person indicated by this
node number.
G A user initiates group CHAT. As a result, the
user may CHAT with people from more than one
node.
A This flags the current node as available for
CHAT. Other users may initiate CHAT with your
node.
U This flags the current node as unavailable for
CHAT. Other users may not initiate CHAT with
your node.

PostCommands Q/E Quit CHAT.
U PCBoard will display the status of other nodes
in the system.
H A list and description of postcommands will be
displayed.


Comment To SysOp
----------------
Command: C
SubCommands: None
PostCommands: (See Enter a Message command)

This command allows a user to leave a message for the SysOp. When
invoked, the user may use all postcommands made available by the
Enter a Message command.


Download A File
---------------
Command: D
SubCommands: [filename] [protocol]
PostCommands: GB BYE

When a user calls another Bulletin Board, he or she may download a
file from that system. Downloading simply refers to a process in
which a file from the current system is copied via a phone line to
your system.








112




If the caller's default protocol is a batch protocol such as YMODEM,
YMODEM/G, or ZMODEM, PCBoard allows the users to request multiple
files by simply typing D and pressing ENTER followed by a list of
files to be downloaded. This is similar to typing DB to initiate a
batch transfer. Alternatively, the caller can download a single
file and avoid further prompts from the system by stacking the D
command and filename on the same command line.

SubCommands [filenames] Multiple filenames may be used on the
command line or at the prompt.
Furthermore, DOS wildcards are permitted.

[protocol] Under the Trans. Protocol option of the
user menu is a of all download protocols
available. Up to 36 protocols may be
defined in the PCBSetup.

PostCommands GB or BYE After the download is complete, the
caller is logged off the system after a
10 second countdown.


DB Download Batch
-----------------
Command: DB
SubCommands: [filename(s)] [protocol]
PostCommands: G A E GB BYE

Like the Download a File command, a user may download a file(s) from
a system that he or she calls. The difference, however, lies in the
prompts given to the caller. The DB command always prompts for a
second filename and asks if the user to edit the list batch files to
be downloaded.

Subcommands [filenames] This represents the files to download. A
prompt is given for each file, but files
may be stacked. Furthermore, DOS
wildcards are permitted.
[protocol] Up to 36 protocols may be defined in the
PROTOCOL DATA FILE field of File
Locations 2 of PCBSetup. Each protocol
has a corresponding letter.

















113




PostCommands G After the batch download has completed,
the user is logged off the system after a
10 second countdown.
A The current batch download will be
aborted.
E The batch list may be edited. From the
batch list, a user may remove a file, add
a file, or list the current files to be
downloaded.
GB or BYE After the download is complete, the
caller is logged off the system after a
10 second countdown.


Enter A Message
---------------
Command: E
SubCommands: None
PostCommands: A C D E F H I L Q S U

This permits a user to leave a message for the SysOp, another user,
or a group of users. Before entering the message, the user must
complete three fields: To, Subject, and Full-Screen Editor. An
optional field is Echo. If modem carrier is lost at any time during
message entry, PCBoard automatically saves the message.

To This prompt indicates the user to whom the message
will be sent. If ENTER is pressed, the message is
sent to all users.
Subject This is a brief description of the message whose
length is restricted by the number of spaces shown.
Full-Screen Y = Use the Full-Screen Editor.
N = Use the Line-By-Line Editor.
U = The user enters upload mode. Characters are
not echoed to the screen, but are immediately
transmitted via MODEM to the upload
destination.
Echo Y = The message is flagged for echo. Though
PCBoard does not utilize this feature, other
mail programs scan a message base and download
or upload all messages with an echo header.
This option is set in each conference
configuration screen in PCBSetup.
N = The message is not flagged for echo.


Message
Security Many Bulletin Board Systems hold sensitive
information. In fact, it is not uncommon to find
BBS's in the military, legal agencies, government
organizations, and universities. Because of the
sensitive nature of information in these
organizations, message security is often essential.






114




PCBoard provides several alternatives for keeping
messages secret and because PCBoard is
extraordinarily configurable, different classes of
security can be indicated.

Inside the Main Board Configuration and each
Conference Configuration screens of PCBSetup is a
parameter that controls whether message security is
invoked or the default is used. The parameter, Make
All Messages Private, is either Y or N. If set to
Y, all messages do not have a security level. This
setting is equivalent to an N (None) security if the
PCBSetup parameter were set to N. However, if the
Make All Messages Private parameter is set to N, the
following message securities are possible. These
security flags are indicated when entering a
message.

Security
Flag Description
-------- -----------
G Group. A user may assign a password to
a message. Only users with the
appropriate password may read the
message.
R Receiver. The message can only be read
by the sender or the recipient.
S Sender. Everyone may read this message,
but only the author (holder of the
assigned password) may kill the message.
N None. The message may be read by all
users within that conference.

Once the above parameters are satisfied, the user is taken to either
the Full-Screen Editor (Available with Ansi graphics only and
indicated above) or the Line-By-Line Editor (No Ansi capabilities
and indicated above). After the message is entered, the user may
press ESC to yield the following PostCommands:

PostCommands A Abort. The message entry will be aborted and
control will return to the user main menu.
C Continue. When invoked, PCBoard returns to a
Line-By-Line edit of the message.
D Delete. PCBoard prompts the user for the line
number in the message to delete.














115




E Edit. PCBoard first requests the line number in
the message to edit. Once entered, the user
types the old text to replace, a semicolon, and
the new text i.e. pleese;please.
F Full-Screen. When invoked, control is returned
to the Full Screen Editor. See next page for
Full-Screen-Editor PC Keyboard, Control, and ANSI
commands.
H Help. When invoked, PCBoard displays the help
file for the Enter A Message command.
I Insert. After entering the line number before
which the new text will be entered, the user may
type the additional text and PCBoard will insert
it in the appropriate place.
L List. The current message being entered will be
redisplayed in line-by-line mode.
Q Quote. (See REPLY command).
S Save. When the user has finished entering his or
her message, the message should be saved. This
relays the message to the appropriate recipient.
U UpLoad. In local mode, the upload function is
unnecessary. However, the body of a message can
be uploaded to a remote editor thereby expediting
the message entry process.

Expert Mode
------------
SC Carbon Copy. The user may send the entered
message to more than one person. When invoked,
PCBoard will request the names of users to whom
the message should be sent. Though displayed in
expert mode, this command is also available in
non-expert mode.
SN Save and Next. During message reply, this command
saves the current reply, skips the re-display of
the original message, and proceeds to the next
available message. Though displayed in expert
mode, this command is also available in
non-expert mode.
SK Save and Kill. The user saves the reply, kills
the original message, and proceeds to the next
available message. Though displayed in expert
mode, this command is also available in
non-expert mode.















116




Full Screen Editor
------------------
To effectively use PCBoard's Full Screen Editor, the user should
familiarize himself or herself with the following control keys and
ANSI codes. Though hardly necessary on most systems, some systems
may support PCBoard's specialized keyboard.

Cursor PC Control ANSI
Movements Keyboard Keys Codes
--------- -------- ------- -----
Move left a char. Left Arrow S ESC[D
Move Right a char. Right Arrow D ESC[C
Move Left to Prev. Word Ctrl-Left Arrow A
Move Right to Next Word Ctrl-Right Arrow F
Move to next TAB Stop TAB Key I
Move to Start of Line Home Key W ESC[H
Move to End of Line End Key P ESC[K
Move Up a Line Up Arrow E ESC[A
Move Down a Line Down Arrow X ESC[B
Move Up a Page PgUp Key R
Move Down a Page PgDn Key C

Edit PC Control
Function Keyboard Keys
-------- -------- -------
Toggle Insert Mode INS Key V
Reformat Paragraph N
Join a Line J
Insert a Line N
Delete a Line Y
Delete to EOL K
Delete Character DEL Key G
Delete Prev Char. Backspace H
Delete Next Word T


Special PC Control
Functions Keyboard Keys
--------- -------- -------
Exit Full Screen Editor ESC U
Re-display Screen L
Quote or List Original O
Toggle 79 Column Mode [Underline]
















117




File Directories
----------------
Command: F
SubCommands: # D G L N P R U V Z NS
PostCommands: None

The user may analyze, view, or download files on the Bulletin Board
System. Files that are new to the caller are displayed with an
asterisk to the right of the date. Normally, these files have
recently been uploaded by another party.

SubCommands # Directory. After the command is invoked, this
option represents the number of the directory
that the user wishes to use.
D Download. PCBoard prompts the user for a file to
download.
G Goodbye. The caller immediately exits the
system.
L Locate by Name. The user may search available
directories for the file indicated in the prompt.
N Locate by Date. The user may search available
directories for all files created after the date
indicated in the prompt.
P Private Upload Directories. The private upload
directory is displayed. Only the SysOp and users
with SysOp privileges may use this subcommand.
R Re-List. The menu of available directories is
displayed.
U Upload Directories. Files in the upload
directories are displayed.
V View. When invoked, PCBoard displays the
contents of a file. It displays the file by
accessing routines in PCBVIEW.BAT. See Directory
Programs for more details.
Z Zippy Search. The user may search all DIR files
for the specified text.
NS Non-Stop. A file will be displayed in non-stop
mode.





















118




FLAG For Download
-----------------
Command: FLAG
SubCommands: [filename]
PostCommands: None

A user may mark a file for future downloading. When the user is
ready to download all the files he or she has flagged, the Download
a File command may be invoked and all marked files will be
downloaded. The FLAG command may be called from the Help, More?
prompt, the main command prompt, or the file list command prompt.

SubCommands [filename] This represents the file that the user
wants to mark for download. PCBoard will
remember all files flagged for download.
Wildcards and multiple filenames may be
used.


GoodBye (Hang Up)
-----------------
Command: G
SubCommands: None
PostCommands: None

When invoked, the user exits PCBoard entirely and the software
recycles to the Call Waiting Screen to await the next caller.
Depending on system setup, a caller is prompted with a Proceed With
Logoff? question and a YES or NO must be entered. This question can
be avoided by typing BYE instead of G to logoff.


Help Functions
--------------
Command: H
SubCommands: [command name] [filename]
PostCommands: None

The user asks for further information about general support or any
command. Although the Help command is initially displayed on the
user's file, it can be invoked from any PCBoard prompt. In this
way, a user can seek help during any command process without
returning to the Main Menu. Furthermore, each PCBoard utility has
separate Help routines to aid in PCBSysMgr, PCBSetup, and PCBFiler
as well as the directory programs in the PCB directory.


SubCommands [command] This represents the command or the
abbreviation of the command for which a
user needs additional information.









119




[filename] A System Operator may have created a file
about a particular command, bulletin, door,
or other utility. If the user is aware of
the file, an eight character filename may
be used here. (This is strictly SysOp
oriented. See Advanced Techniques for more
details.)


Initial Welcome
---------------
Command: I
SubCommands: None
PostCommands: None

When invoked, PCBoard displays the original logon screen. This
screen may contain extensive graphics, regular text, and color.
Further information is found in PCBSetup under File Locations 1 or
in Editing File Locations 1 & 2 Files.



Join A Conference
-----------------
Command: J
SubCommands: # [name]
PostCommands: Q

PCBoard can support up to 65,000 conferences. Each conference may
contain different information, directories, or files. Some users
may be privy to specific conferences while others are denied. A
conference may be accessed by using the conference number or the
conference name.

SubCommands # Conference Number. This is the conference that
the user wants to join. The conference numbered
0 represents the Main Board.
[Name] Conference Name. This is the name of the
conference the user wants to join. To re-join
the Main Board from another conference, the user
can type J Main.

PostCommands Q Quick Join. After the user indicates a J to join
a conference and the conference name or number,
he or she may enter a Q. PCBoard will bypass the
news file and enter the conference immediately.














120




Kill A Message
--------------
Command: K
SubCommands: [message number]
PostCommands: None

Each message is given a number that chronologically places it in the
message base. This command may be invoked to remove a message from
the message base. The only requirements are the message number and
a sufficient security level. The message may be recovered with
SysOp Function 4 before message base packing.

Subcommands [message #] PCBoard removes the message whose number is
typed at this prompt.


Locate Files(name)
------------------
Command: L
SubCommands: [filename] # A D N U NS
PostCommands: None

If a user is unaware of a file's location or exact name, he or she
may use this command to find the file. The command accepts all DOS
wildcards.

SubCommands [filename] PCBoard seeks this file. The filename may
include all DOS wildcards. (See Dos
Wildcards in the Glossary for more details.)
If a similar pattern is found, PCBoard will
display the file.
# This is a directory number. If indicated,
PCBoard will search for the above file in
this directory only.
A If chosen, PCBoard searches for the
indicated file in all available directories
inside the current conference.
D Once a file that matches specified
parameters is located, it is flagged and
prepared for a later download. If more than
one file is found, all are flagged. The
batch may be edited prior to commencing the
download.
N The search for particular files is joined by
a date scan. Files with a later date than
the specified date are scanned for the
indicated parameters.
U If chosen, PCBoard searches for the
indicated file in all upload directories.
NS Files are displayed in Non-Stop Mode (void
of all More? prompts).








121




MENU
----
Command: MENU
SubCommands: None
PostCommands: None

The SysOp or a user can immediately access the Main Menu from any
prompt in PCBoard. When invoked, the menu screen is displayed even
while in expert mode.


Mode (Graphics)
---------------
Command: M
SubCommands: CTTY ANSI GRAPHICS
Postcommands: None

This command acts as a toggle between graphics and non-graphics
display modes. A caller without ANSI capabilities should choose
non-graphics mode.

SubCommands CTTY The system is placed into non-graphics, non-
ANSI mode.
ANSI The system is placed into non-graphics, ANSI
mode.
Graphics The system is placed into graphics, ANSI mode.


New Files (Date)
----------------
Command: N
SubCommands: [date] # A S U NS
PostCommands: None

This command will locate any files that have been uploaded to the
system since the specified date. PCBoard chronicles in the user's
record, the date of the most recent file found. As a result, when
the caller uses the N S A command, he or she is only shown files
from that date onward.

SubCommands [date] This represents the date from which PCBoard
begins a search for all "New" uploaded files.
All files posted after this date (MMDDYY
format) are displayed.
# This is a directory number. If indicated,
PCBoard will search for all post-dated files
in this directory only.
A If chosen, PCBoard searches for all post-dated
files in all available directories in the
current conference.









122




D All files are queued for download. The next
invocation of the Download a File command
downloads all files found.
S PCBoard scans for files newly added since the
date of the most recent files the caller has
been shown.
U If chosen, PCBoard searches for all post-dated
files in the upload directories.
NS Files are displayed in Non-Stop Mode (void of
all More? prompts).


NEWS File Display
-----------------
Command: NEWS
SubCommands: None
PostCommands: None

A user may employ this command to read any news that the SysOp has
placed in the current conference. Normally, the NEWS file is
displayed when a user logs on to the system or joins a conference.
This screen may contain extensive graphics, regular text, and color.
The NEWS file is edited within the Main Board Configuration screen
and each conference screen within PCBSetup. When the NEWS field is
highlighted, the SysOp can press F2 or F3 (graphics file) to invoke
the Text or Graphics Editor defined in PCBSysMgr.


NODE
----
Command: NODE
SubCommands: (See CHAT Between Nodes Command)
PostCommands: None


Operator Page
-------------
Command: O
SubCommands: None
PostCommands: None

A user may request an immediate CHAT with the SysOp. If the BELL is
turned ON (See Call Waiting Screen), the user's computer will beep
for 30 seconds. The SysOp's computer will also beep informing him
or her that a user wishes to CHAT. If the SysOp does not respond,
PCBoard will inform the user that the SysOp is unavailable for CHAT.
If the BELL is turned OFF, PCBoard asks the user if he or she would
like to leave a comment for the SysOp. The SysOp specifies the time
that he or she is available for an operator page. Above and to the
right is an operator page executed on a machine with the Bell OFF.









123




OPEN a DOOR
-----------
Command: OPEN or DOOR
SubCommands: # [name] [parameters]
PostCommands: None

This command takes the user out of PCBoard and into an alternate
application. When the command is executed, a menu, created by the
SysOp is displayed. The menu consists of a DOOR number, the name,
and a description of the program. DOORS are discussed more
thoroughly in PCBSetup and Editing Files.

SubCommands # This represents the number of the DOOR to open. It
may either be stacked with the command at the main
menu prompt or chosen after the DOOR menu is
displayed.

[Name] Instead of the DOOR number, a user may type the
actual DOOR name without the preceding OPEN or
DOOR to drop to an alternate application.

[parameter] A user may pass a parameter to the DOOR that he or
she calls. This parameter is similar to one
passed at a DOS prompt to another application.


Page Length Set
---------------
Command: P
SubCommands: #
PostCommands: None

The user may specify the number of lines PCBoard displays before it
prompts "(H)elp, More?".

SubCommands: # This number indicates the number of lines
displayed per screen.






















124




Quick Message Scan
------------------
Command: Q
SubCommands: # F Y S NS + - TS USER
PostCommands: None

The user may analyze a succinct list of all available messages.
When invoked, PCBoard will display the message number, reference
number, sender, receiver, and subject. The reference number refers
to the reply by the original recipient of that message. To the
right is an example of the Quick search.

SubCommands # This is the message number from which PCBoard will
display a brief list of current messages in the
message base.
F The message base is scanned for all messages left
by the current user.
Y The message base is scanned for all messages sent
to the current user.
S All messages that have not already been read will
be scanned and displayed.
NS Messages will be displayed in Non-Stop Mode (void
of all More? prompts).
+ When appended to a message number, PCBoard
displays all messages in forward-numerical order
from that point.
- When appended to a message number, PCBoard
displays all messages in reverse-numerical order
from that point.
TS Though only the header is displayed, PCBoard scans
the entire message and message header for the
indicated text.
USER The message base is scanned for messages left to
or received from the indicated user.

Status Flags When a user does a quick message scan, each message
number has a special symbol to its left. The symbol
may represent the type of message sent, any security
attached, or the person who read the message. The
status flags are defined below.

( ) A message that can be read by anyone.
(*) A private message unread by the official
recipient of the message.
(+) A private message that has been read by the
official recipient.
(-) A public message sent to a user who has already
read the message.











125




(~) A COMMENT to the SysOp that has not yet been read
by the SysOp. In this context, the SysOp is
indicated by the user defined in record one of
the user file.
(`) A COMMENT to the SysOp that has been read by the
SysOp. In this context, the SysOp is indicated
by the user defined in record one of the user
file.
(%) An unread message protected by a SENDER PASSWORD.
(^) A message protected by a SENDER PASSWORD that has
already been read.
(!) An unread message protected by a GROUP PASSWORD.
(#) A message protected by a GROUP PASSWORD that has
already been read.
($) A message addressed to ALL protected by a GROUP
PASSWORD.


Read Messages
-------------
Command: R
SubCommands: # F Y YA S L A TS SET USER SKIP JUMP
SELECT DESELECT NS NEXT PREV RM RM+ RM- +
- / C D Z G J EDIT
PostCommands: P U F O [move] [copy] RE RR E T T- M
[enter] K N

The Read Messages command permits the user to read a message left
for him or her. The message may be protected against foreign eyes,
moved or copied to alternate message bases, and edited for
different users. Examples of the Read Messages command are
displayed.


SubCommands

SCAN # This number indicates the number of the message that
the user wishes to read.
From The message base is scanned for all messages left by
the current user.
Your The message base is scanned for all messages sent to
the current user.
Yours/All The message base is scanned for all messages sent to
the current user or to ALL.
Since All messages that have not already been read will be
scanned and displayed.
L The current message base is read backward from the
last message to the first.
A Messages are read from all conferences that have been
selected.









126




ALL Messages are read from all conferences whether
selected or not.
TS The header of each message is scanned for the
indicated text.
SET This number sets the message pointer to the message
indicated by the input.
USER The message base is scanned for messages left to or
received from the indicated user.
SKIP If a user invokes an R S or an R A command, he or she
may use SKIP to bypass the remaining messages in the
current conference. The Message Read Pointer is
changed to the last message. In the R A case,
however, invoking SKIP moves the user to the next
available conference and permits him or her to
continue reading messages in that conference.
JUMP If a user reads all conferences (R A), he or she may
jump to the next available conference for message base
scanning. The Message Read Pointer is not changed,
however.
Select While reading a message inside the main board or a
particular conference, the user can select it for
further scanning. Like the Select command from the
Main Board, an "X" is placed in the main board or
conference field. This indicates that the user wishes
to scan that conference when a future scanning command
is invoked i.e. Your Mail.
Deselect If the main board or a particular conference is chosen
for scanning, an "X" is placed in its field. When this
subcommand is invoked, the "X" is removed and any
future scans bypass the main board or deselected
conference.

Display NS Messages are displayed in Non-Stop Mode making the
display void of More? prompts.
NEXT The next numerical message is displayed.
PREV The previous numerical message in the message base
will be displayed.
RM The last message read is re-displayed.
RM+ The last message read is re-displayed and the message
base is placed in forward mode for further reading.
RM- The last message read is re-displayed and the message
base is placed in reverse mode for further reading.
+/- When appended to a message number, PCBoard displays
all messages in forward-numerical or reverse-numerical
order respectively from that point.
/ Re-display the current message.













127




Capturing C The messages displayed by the current command are
captured, placed in a file, and prepared for download.
This function is available in remote mode only.
D The messages displayed by the current command are
captured, placed in a file, and immediately
downloaded.
Z The messages displayed by the current command are
captured, placed in a file, and immediately
downloaded. The file, however, is compressed before
its downloaded.
G GoodBye. (See the user command GoodBye for more
details.)
J The user may join another conference. (See the user
command Join a Conference for more details.)
EDIT The current message is placed in the editor for
modification.

PostCommands
Sysop P The message is protected (made private). This is a
SysOp only function.
U The message is unprotected (made public). This is a
SysOp only function.
F This SysOp only function locates the user's record and
displays it.
O In this SysOp only function, messages are read in
READ-ONLY mode. The message is not marked as read and
the Last-MSG-Read pointer is not updated.
MOVE The message is moved to an alternate conference
indicated by the trailing conference number. This is
a SysOp only function.
COPY The message is copied to an alternate conference
indicated by the trailing conference number. This is
a SysOp only function.
RE Once a message is read, the user may reply to the
sender. This option permits the user to reply to the
current message.
RR If a message is a reply, the user may immediately
access the reference message with this option.
E The user may edit the To, Subj., Reference Number,
Read Status, and Protection.
T PCBoard threads forward through all messages that have
an identical subject matter as the current message.
Normally, the user memorizes his or her current
position (by using M option) and returns after the
path is followed.
T- PCBoard threads backward through all messages that
have an identical subject matter as the current
message.











128




M When invoked, PCBoard memorizes the current message
pointer. When the user wants to return to this
message, he or she may type RM, RM+, or RM-. [enter]
The Read a Message function is continued. Subcommands
are accessible.
K If the message is to/from the current user, the user
may kill it. The message can be recovered by SysOp
Command 4 before a message base pack.
N Reading ends, but the user does not exit the function
or the system.


REPLY to Message(s)
-------------------
Command: REPLY
SubCommands: #
PostCommands: None

Once a message has been sent, the recipient may respond or reply to
it. When invoked, the user may utilize all commands found under
Enter A Message. The message number of the reply becomes the
reference number to the original message.

SubCommands # This number (between 1 and 99,999) indicates the
message to which the user wishes to respond.

Quoting Local & Remote. The user may use the Q option
(Line-By-Line Editor) or CNTRL Q (Full-Screen
Editor). This displays the original message and
asks the user "to start quoting from which line?"

It then asks the line number to end the quote.
Once complete, PCBoard returns to the REPLY
message (L.B.L. or F.S. depending on the above
invocation) with the quoted information denoted by
-->.

Local Scrollback. After reading a message, the
user may choose to immediately REPLY with the RE
option of the Read A Message command. The user
may scroll back (use arrow keys) to the original
message. When the text to quote is found, press
the space bar before the passage. Scroll to the
end of the quote and press the space bar a second
time. When ESC is hit, the information will be
transferred to the REPLY message. The information
is denoted by -->.












129




RM Re-Read Mem #
-----------------
Command: RM
SubCommands: None
PostCommands: None

After a message has been memorized (M option under reading), it may
be re-displayed using this command. An RM by itself jumps to the
memorized message number and stops displaying messages. An RM+
jumps to the memorized message number and continues to display
successive messages. An RM-jumps to the memorized message number
and continues to display preceding messages.


Script Questionnaire
--------------------
Command: S
SubCommands: None
PostCommands: None

The Script Questionnaire allows the user to answer questions for
later analysis or processing. The questionnaire has been previously
created by the SysOp of the system. When invoked, a menu appears
that shows the questionnaire number and a description of the
questions. Each question is given a field that cannot be exceeded.


SELECT Conferences For Scanning Or Reading
------------------------------------------
Command: SELECT
SubCommands: # S D Q
PostCommands: None

PCBoard lists the current conferences to which a user has access.
In the list, PCBoard includes the conference number, description,
last message read, highest message in the conference, and flags. An
"X" in the flags field indicates that the user wishes to scan that
conference when a scanning command is invoked i.e. Your Mail.

SubCommands # If the "X" appears in the flags field, it is
removed and the conference is not selected for
scanning. If the "X" does not appear in the flags
field, PCBoard asks the user to set the last
message read pointer.
S This option selects all conferences for scanning.
After invoked, each conference will have an "X" in
its flags field.
D This option deselects all conferences for
scanning. After invoked, each conference will not
have an "X" in its flags field.
Q Control is returned to the Main User Menu.








130




Transfer Protocol
-----------------
Command: T
SubCommands: A-Z, 0-9 (optional)
PostCommands: None

When invoked, a list is displayed that enables a caller to choose
among several protocols to upload or download files. The protocols
are created by the SysOp and each is denoted by a single character,
a letter or a number from 0 to 9. Transfer protocols are discussed
at length in Appendix V.



TEST a File
-----------
Command: Test
SubCommands: [Filename]
PostCommands: None

The TEST command permits the SysOp to check files for viruses and
other corruptions that might exist. When invoked, PCBoard follows
these procedures:

Download paths are scanned to ensure the existence of the
indicated file.

The filename is passed to a batch file entitled
PCBTEST.BAT. In this file, the SysOp can implement any
procedures he or she believes necessary to safeguard the
system. An example of this file is at right.

The PCBTEST.BAT file is similar to the PCBVIEW.BAT file in
recognizing ZIP or ARC files. However, PCBTEST.BAT creates
one of two files: PCBFAIL.TXT or PCBPASS.TXT. The former
is created if a file is corrupt, contains a virus, or fails
for any other reason imposed by the rudimentary logic in
PCBTEST.BAT. The latter, on the other hand, is created if
the file successfully meets all requirements in
PCBTEST.BAT. Control is returned to PCBoard.

If a PCBFAIL.TXT exists after returning to PCBoard, the
SysOp or user is told of the files failure. However, if
the PCBFAIL.TXT does not exist, even if PCBPASS.TXT is
absent, PCBoard assumes the file passed all file
requirements and a message is displayed.

SubCommands [Filename] This is the file that will be tested
according to the procedures above.










131




TS Text Search Messages
-----------------------
Command: TS
SubCommands: F Y S A ALL L C D Z NS RM+ RM- ##+ #-
USER | &
PostCommands: None

The TS command permits the user to scan messages and message headers
to locate a specified text string. PCBoard allows conditional text
searches (indicated by | and &). To the right is an example of text
searching.

SubCommands F The message base is scanned for all messages left
by the current user that contain the desired text
string.
Y The message base is scanned for all messages sent
to the current user that contain the desired text
string.
S All messages that have not already been read will
be scanned and displayed if the appropriate text
string is found.
A All selected conferences are scanned for the
designated text.
ALL All conferences, whether selected or not, are
scanned for the designated text.
L The current message base is read backward from the
last message to the first.
C The messages displayed by the current command are
captured, placed in a file, and prepared for
download. This function is available in remote
mode only.
D The messages displayed by the text search are
captured, placed in a file, and immediately
downloaded. This function is available in remote
mode only.
Z Any messages that conform to the indicated text
search are captured, placed in a file, and
immediately downloaded. Before the file is
downloaded, however, it is compressed. This
function is available in remote mode only.
NS Messages found with the specified text are
displayed in Non-Stop mode.
RM+ The last message read is re-displayed and the
message base is placed in forward mode for further
reading.
RM- The last message read is re-displayed and the
message base is placed in reverse mode for further
reading.
##+ The message base is scanned for the indicated text
from this point forward.









132




##- The message base is scanned for the indicated text
from this point backward.
USER Only messages left to or received from the
indicated user with the specified text will be
displayed.
| This is a logical OR operand. When place in a
text string search, PCBoard locates messages that
contain either the first string or the second or
both.
& This is a logical AND operand. When placed in a
text string search, PCBoard locates messages that
contains both the first string and the second
string.


Upload A File
-------------
Command: U
SubCommands: [filename] [protocol]
PostCommands: GB

Like the command Download A File, this command allows the user to
transfer files between systems. In this case, however, the user is
sending a file to another system instead of receiving one.

SubCommands

[filename] This is a DOS filename of an existing file in the
system. PCBoard will ask for the filename or it may
be included on the command line. If more than one
file is uploaded, each must be listed on the command
line.
[protocol] The transfer protocols are listed under the Trans.
Protocol command. The SysOp defines the transfer
protocols. Twenty-six are permitted.

PostCommands

GB After the file transfer is complete, the user may
indicate that he or she wishes to disconnect. This
option may be included on the command line with the
other options of this command.

















133




UB Upload Batch
---------------
Command: UB
SubCommands: [filename(s)] [protocol]
PostCommands: GB

This command functions similarly to Upload A File with one minor
exception. The UB command immediately assumes that more than one
file will be uploaded. PCBoard prompts the user for each filename.
To the right is a sample batch upload.

SubCommands

[filename(s)] This is a DOS filename of an existing file in the
system. Several files may be uploaded at once
given the appropriate protocol.
[protocol] The transfer protocols are listed under the
Trans. Protocol command. The SysOp defines the
transfer protocols in PCBSetup.

PostCommands
GB After the file transfer is complete, the user may
indicate that he or she wishes to disconnect.
This option may be included on the command line
with the other options of this command.


USERS List Users
----------------
Command: USERS
SubCommands: [text string] | &
PostCommands: None

This command allows a user to search the current user's file for a
text string. The user inputs the text string. PCBoard provides a
list of users with the text string found somewhere in their records.
In the list are user name, location, and the user's last logon date.

SubCommands

[text string] This is any piece of text. PCBoard analyzes this
input, scans the users' file, and displays all
user records with the appropriate text.
| This is a logical OR operand. When placed in a
text string search, PCBoard locates user records
that contain either the first string, the second
string, or both i.e. (John | Utah).
& This is a logical AND operand. When placed in a
text string search, PCBoard locates user records
that contain both the first string and the second
string.








134




View Settings
-------------
Command: V
SubCommands: None
PostCommands: None

This command displays the current settings of the user. Each
parameter is relatively self-explanatory. To the right is a sample
listing of a common display.

If the user has SysOp privileges, the following additional
parameters will be displayed: low message number, number of
messages defined, number of free message slots available.


WHO
---
Command: WHO
SubCommands: None
PostCommands: None

This command acts like the NODE or CHAT command, but does not permit
communication with other callers. When invoked, PCBoard displays
the status of each node.


Write User Information
----------------------
Command: W
SubCommands: None
PostCommands: None

This command allows a user with proper authorization to change his
or her own user information. If proper security level is given, the
following fields may be changed: password, caller's location,
business/data phone, home/voice phone, comment field, and desired
message bases to scan. If access is denied, the user may change his
or her own password.


Xpert Mode On/Off
-----------------
Command: X
SubCommands: None
PostCommands: None

This command acts as a toggle between expert and novice modes. If
expert mode is implemented, the main menu screen is not displayed.
During many user commands, options are often reduced to one letter
(instead of the whole word). A user in expert mode is privy to
advanced capabilities in some commands. Though a novice in non-
expert mode has access to the same options, he or she is unaware of
their existence since many are not displayed i.e. the SC, SK, and SN
commands in Enter A Message.





135




Your Personal Mail
------------------
Command: Y
SubCommands: A ALL S NS Q L C + -
PostCommands: None

This command permits a user to scan his mailbox to determine if he
or she has sent or received messages. The message base is scanned
in reverse order. Depending on subcommands used, messages are
displayed in different formats. Two examples of the most common
mail searches are displayed on this screen.

SubCommands

A PCBoard scans all selected conferences including the main
board for messages from or to the current user.
ALL PCBoard scans all conferences, whether selected or not, for
messages from or to the current user.
S The message base is scanned from the last message read. Only
messages after this point are displayed.
NS Messages found are displayed in Non-Stop mode.
Q Messages are shown in quick list mode. The message base(s)
is/are scanned, but only the number of personal messages
found is displayed and not what those message numbers are.
L This option shows messages in long list mode. The message
base(s) is/are scanned and the corresponding number of each
message found is displayed.
C Only the current message base is scanned for messages.
+ When added to a message number, PCBoard scans from that point
forward.
- When added to a message number, PCBoard scans from that point
backward.


Zippy DIR Scan
--------------
Command: Z
SubCommands: # A D N U NS | &
PostCommands: None

This command scans the directories to find a specified text string.

PCBoard prompts for the text string to scan. Like other PCBoard
searching features, the user can utilize boolean operands (OR and
AND). To the right is an example of Zippy DIR Scan.

SubCommands

# PCBoard scans for the indicated text in this directory number
only.
A PCBoard scans for the indicated text in all directories on
the system.







136




D Each file found with the specified text is flagged for
download. The system does not immediately download the
files, but waits until the command Download A File or
Download A Batch.
N A search for the indicated text string is accompanied by a
date scan. Only files created after a specified date are
scanned for the text.
U Only upload directories are scanned for the indicated text.
NS Screen output is displayed in Non-Stop mode.
| This vertical bar is a logical OR operand. When placed in a
text string search, PCBoard locates files that contain either
the first string, the second string, or both i.e. (John |
Utah).
& This is a logical AND operand. When placed in a text string
search, PCBoard locates files that contain both the first
string and the second string.











































137




General Information
-------------------
PCBoard's System Manager is designed to access all necessary setup
menus from one convenient location. From this program, the system
operator can access, change, and store user information files,
PCBFiler and PCBSetup information, system configurations, printer
definitions, text and graphics editors, and system colors. A SysOp
can enter the System Manager directly from the DOS command line
(discussed later) or directly from the Call Waiting Screen.


PCBSysMgr Screen
----------------
Below is the PCBSysMgr screen. Each option can be chosen by
scrolling the menu with the arrow keys and pressing RETURN when your
choice is highlighted. To exit, press the ESC key until the desired
screen is found. Following is a more detailed analysis of each menu
option.









































138




User File Maintenance
=====================

General Information
-------------------
The Users File Maintenance option allows the SysOp to manipulate
user files. Many menu choices affect the entire users file. As a
result, all nodes must be logged out of PCBoard for the change to be
made. The Edit Users File option, however, affects an individual
record.

If errors occur before saving, the ESC key can exit the process
leaving the file unchanged. If saved, however, the original users
file may be restored by choosing the Undo (Restore Backup File)
option. Since this option exists, there must be disk space
available for two user files: the former and the new.


User Maintenance Screen
-----------------------
Below is the User Maintenance Screen. Following is a description of
each menu option and its function.

The Edit Users File option allows the SysOp to add or
manipulate a record. The option consists of three screens:
Short Form, Long Form, and Conference Fields. Below is a
description of each screen and its function.

Short Form The Short Form allows the SysOp to add or change a
user record. Several ALT functions displayed at the right of
the screen can be used to locate, add, or delete a record.
These functions are available in each screen of the Edit
Users File option. Upon entry, the SysOp will see the first
record of the users' file (SysOp record). Above is the Short
Form screen with a brief description of each ALT function and
the individual fields.

ALT-A Add A New User. When invoked, PCBSysMgr displays the Long
Form (discussed later) and requests information about each
field.

ALT-F Find A User Name. At the prompt, type the user's full name.
PCBSysMgr will immediately retrieve the user record
(assuming it exists) allowing the SysOp to modify its
contents.

ALT-S Search For Any Text. PCBSysMgr will search each field of
each record in the users file for the ASCII text indicated.
The first record with the desired text will be displayed. To
see additional records with the desired text, press ALT- R.
Continue in this manner until the appropriate record is
found.







139




ALT-L Locate Security Level. PCBSysMgr searches the Security field
of each record in the users file for the security level
indicated at the prompt. The first record with desired
security will be displayed. To see additional records with
desired security level, press ALT-R. Continue in this manner
until the appropriate record is found.

ALT-E Locate Exp. Security Level. This ALT function is identical
to the ALT-L function, but PCBSysMgr searches the Expired Sec
field.

ALT-O Locate Deleted Users. This ALT function is identical to the
ALT-L and ALT-E functions, but PCBSysMgr scans the Delete
User field for a (Y).

ALT-R Repeat Last Search. After searching the user file via ALT
functions, ALT-R proceeds to the next user record that
contains the field sought.

ALT-J Jump To Record Number. PCBSysMgr asks the SysOp for the
record number of the user to access. The record may then be
modified if desired.

ALT-T Jump To Top Record. PCBSysMgr displays the first record
(SysOp record) in the user file.

ALT-B Jump To Bottom Record. PCBSysMgr displays the last record in
the user file.

ALT-P Print The Current Record. PCBSysMgr will print the user
record that is currently displayed.

ALT-D Delete The Current Record. PCBSysMgr will flag the current
record for deletion. The Delete User field will be set to
(Y) and the record will be removed from the file upon
packing.

Long Form
---------
The Long Form has all Short Form data, ALT function
abilities, and detailed user fields. To the right is the
Long Form screen. By closely analyzing the fields, the SysOp
can determine important features of any user including number
of downloads executed, time logged in, and messages left.
PCBoard, for example, may set the Registration Expiration
Date (Reg. Ex. Date) as one year from the date of entry.
Although this is the default, a SysOp can change the default
subscription period in PCBSetup under the
Node/Event/Subscription option. Once registration expires,
the user is given the security level listed in Expired
Security. The Delete User field indicates whether the record
should be flagged for deletion (explained in Pack Users
File).






140




Since each Long Form option is relatively
self-explanatory, any further HELP is available by pressing
F1 (Help key) while a field is highlighted.

Conference Fields
-----------------
The Conference Fields screen allows the SysOp to register a
user in any conference defined to the system. To the left is
the Conference Fields screen. The Flags listing indicates a
user's registration and capabilities in a particular
conference. The Flags field may be empty (denied access) or
have an C, L, R, S, X or a combination of flags in its field.
Upon registration of a user into conferences, PCBoard first
requests the conference number. If registration into
multiple conferences is needed, conference numbers can be
separated by a space. Second, PCBoard requests what
conference abilities a user will have. These registration
flags are described below and may be stacked on the same
line, separated by a space.


Sort Users File
---------------
The Sort Users File option provides two alternatives: Single Field
Sorts and Multiple Field Sorts. Each is discussed in detail below.


Single Field Sorts
------------------
The SysOp may sort by any alternative listed on the Sort Single
Field screen (shown at right). For alphabetic fields such as name
or password, PCBSysMgr can order them from A to Z or from Z to A.
The SysOp is asked for the alphabetizing direction. For numerical
fields such as phone numbers, PCBSysMgr gives an option to
Standardize Phone Formats which insures the uniformity of the phone
number field. In this way, phone numbers can be sorted in numerical
or reverse-numerical order.


Multiple Field Sorts
--------------------
PCBSysMgr allows the SysOp to sort by multiple fields as indicated
by the Sort Multiple Fields screen to the left. Upon choosing, the
SysOp will be asked sorting preference (standard or reverse) for
both the primary and secondary key. The primary key is the first
listing: Security Level, Num Times On, Num Files
Downloaded/Uploaded, Files Upld:Dnld Ratio, Bytes
Uploaded/Downloaded, or Bytes Upld:Dnld Ratio. The secondary key is
always the Name.










141




PCBSysMgr first sorts user records by the primary key then
alphabetically by name. By this method, the SysOp can have users
grouped by security level byte ratios, or login times. Within each
group, users will be sorted alphabetically by the user's last name.


Pack Users File
---------------
The Pack Users File option permits the SysOp to condense the user
file by eliminating previously deleted, old, expired, or locked out
records. To the right is the Pack Users File screen that lists
several options for record elimination and packing. Most fields are
specific and need little explanation. However, a brief description
of each follows:


Removal Criteria
----------------
Deleted Or 'Locked Out'. If (Y), PCBSysMgr will eliminate all users
that have a (Y) in this user field or a security level of 0.

Not Been On For XXXX Days. PCBSysMgr determines the number of days
since a user last used the system. If equal to or greater than the
number of days specified, the record is eliminated.

Not Been On Since. PCBSysMgr eliminates users who last used the
system on or before this day. If set to 00-00-00, this field is
skipped.

Reg. Exp. Date Older Than. PCBSysMgr removes records with
expiration days older than the date in this field. If set to
00-00-00, this field is skipped.


Retain Criteria
---------------
Greater Than Or Equal To. PCBSysMgr will keep all records with this
security level or higher regardless of the above settings for
removal.

Locked Out. PCBSysMgr will retain users who have a security level
of 0. This insures that a user is locked out.


Deletion Prints
---------------
Y = All records that were deleted will be printed to a defined
printer.
N = All records that were deleted will not be printed.










142




Print Users File
----------------
The Print Users Listing option permits the SysOp to print user
records in one of three formats: Short Form, Long Form, or Reg.
Expiration Form. To the left is the Print Users Listing screen.

Start/Ending. PCBSysMgr expects the first record from which to
start printing and the last record at which to stop.

Exp. Users Only. If set to (Y), only expired user records will be
printed; otherwise, all records within the start/end range will be
printed.

Print Formats (A,B,C). Each printing format is chosen by individual
taste. The first has scanty, general information for quick access.
The second includes all user information and is the most detailed.
The third indicates the date that a user's registration will expire.
Below is a sample of each format.

Format A
Format B
Format C


Make Users File Index
---------------------
Though PCBoard automatically maintains indices for user records, the
SysOp may manually recreate record indices using the Make Users File
Index. The recreation process does not destroy any user
information.


Adjust Security
---------------
PCBSysMgr allows the SysOp to modify security levels based on a
user's frequent use of the system, upld/dnld ratio, or expiration
date. To the right is the Adjust Security Levels screen. Although
examples are given about a few fields, a more thorough description
is necessary.


Adjustments By Ranges
---------------------
PCBoard has two options for adjusting security levels by range. The
first, Adjust Security by Range, permits the SysOp to change a
security level within defined limits to a new level. The second,
Adjust Security by Range (Expired), permits the SysOp to change
expired security levels.

Adjustments By File Transfer Activity
-------------------------------------
An option from C to F is used only after an option from G to J is
performed. After the appropriate table is created, the respective
adjustment can be implemented. If an Upload Table is created with
option I, the adjustment can be executed with Option E, Adjust by
Number of Uploads.



143




Ratio Tables. PCBoard utilizes a not too complex series of optional
tables to reward or penalize users who upload or download files.
Since file uploads enrich a system's appeal, many SysOps like to
increase security levels or time limits for users who upload files.
The security level normally remains in effect until the user
deviates from the download/upload ratio. When that occurs, the
SysOp can decrease the user security level or reduce the user's
daily time limit. Furthermore, since user commands are controlled
by security levels, the SysOp can create a table linked with user
commands. In this manner, a user may have access to certain
commands only if he or she performs an upload or refrains from
downloading.

Ratio. The ratio used in a table may be negative or positive
depending on the rewards or penalties a SysOp wants to implement.
General rules of thumb for ratio table creations follow:

Negative numbers mean a ratio of Downloads to Uploads.

Positive numbers mean a ratio of Uploads to Downloads.

All ratios are multiplied by 10 i.e. 100:1 downloads to
uploads equals -1000 while 5.0:1 uploads to downloads equals
50.

Ratios should be ordered from smallest to largest (negative to
positive) and should be entered from lowest to highest.

These rules, however, apply to only File and Byte Ratio Tables.
Other tables such as the general Upload/Download Tables use
solely positive numbers and award security levels based on the
number of files uploaded or downloaded.

Range. Since ratios are listed from negative to positive, the
first listing presents a starting point for a series of ranges to
follow. The range is comprised of a beginning point and an
ending point. All users within that range are given the
indicated security level. The range is determined by the range
before and after it. As a result, the first listing ranges from
infinity to one higher than the second listing i.e. Infinity to
26. The second listing, therefore, ranges from 25 to, say, 10.
The third and final listing, consequently, ranges from 9 to
Infinity. See one of the following ratio tables for further
explanation.
















144




Creating A File Ratio Table
---------------------------
PCBoard allows a SysOp to define system security levels by user
upload/download frequency within a given range. Although a File
Ratio Table acts upon a ratio between the number of uploads to
downloads, it does not account for how large an upload is compared
to a download. Consequently, a caller may upload several small
programs that contribute little to a system's appeal. At the same
time, he or she may download several large files and inevitably
acquire a security level. Consider the following excerpt:


Creating A Byte Ratio Table
---------------------------
Like the File Ratio Table, the Byte Ratio Table is constructed in a
similar fashion. However, the SysOp awards security levels based on
byte ratios between uploads and downloads. This remedies the
sometimes undesirable tendency of callers to upload useless files to
improve their upload to download ratio. Consider the following
excerpt:


Creating An Upload Table
------------------------
Unlike the File or Byte Ratio Table, the Upload Table does not use
negative numbers or a ratio of any kind. Instead, it assigns
security levels to users who have uploaded a specific number of
files. Normally, security levels increase as the number of uploads
increase. Consider the following table:


Creating A Download Table
-------------------------
Similar to the Upload Table, the Download Table assigns a security
level based on the number of a caller's downloads. Normally,
contrary to Upload Tables, security levels decline as the number of
downloads increase. Consider the following excerpt:


Change Security To Expired Level
--------------------------------
When a user's subscription expires, PCBoard changes his or her
security level to the Expired Security Level defined in the user
file. PCBoard only adjusts this level in memory and does not modify
the actual user record. To adjust user records for security level
modification, this option can be implemented. Accordingly,
PCBSysMgr will change the security level of all users with expired
subscriptions.











145




Initialize Upld/Dnld Counters
-----------------------------
PCBoard allows download/upload file and byte counters to be reset.
By this method, users can be reassigned security levels (based on
the above tables) calculated from the moment counters were reset.
Both download and upload fields can be matched based on the
respective download/upload number of files. The fields may be reset
to zero or adjusted by download/upload byte ratios.


Insert or Remove Group Conferences
----------------------------------
PCBoard permits the SysOp to insert groups of users into
conferences. The specified conferences will be added to all users
within a specified security range with the characteristics
enumerated in the Insert Group Conference screen above. Though the
insertion process is thoroughly discussed, the removal process
utilizes identical information and procedures.


Conferences To Be Inserted
--------------------------
The first parameter indicates the number of the first conference to
insert. The second parameter indicates the last conference to
insert. PCBoard will add the first, the last, and all conferences
between these parameters. Respectively, a 6 and 10 in each
parameter would add conferences 6, 7, 8, 9, and 10.


User Conference Adjustments
---------------------------
As described in Conference Fields under Edit Users File, conference
flags can be set depending on whom the SysOp wants to access a
particular conference. Setting each Adjust Conference field to (Y)
will have the following effects:


Conference Fields under Edit Users File
=======================================

Field Description
----- -----------
First A user with a non-expired subscription may access the
added conferences when the R flag is set in his or her
conference field record. If a user's subscription has
expired, access is denied.
Second A user, regardless of subscription expiration, will have
access to the added conferences when the X flag is set in
his or her conference field record.
Third A user may scan the added conferences for messages or
comments when the S flag is set in his or her conference
field record.
Fourth A user will have access to the added conferences when the
C flag is set in his or her conference field record.





146




Adjust Users With Desired Security Levels
-----------------------------------------
The above adjustments will only be made to users with a security
level equal to or between the specified limits in the Adjust
Security Levels field. As a result, a particular group of users may
be registered into a range of conferences.


Adjust Message Read Pointer
---------------------------
Y = The message read pointer for each user in each newly added
conference will be reset to 0.
N = The message read pointer will not be reset and users will retain
the current message counter.


Move Users Between Conferences
------------------------------
The Move Users Between Conferences option transports registered
users from one conference to another (normally when the conference
number changes) and allows the user's message read pointer to be
transferred so old messages needn't be re-read. The above screen
lists essential information for the process to occur much of which
is similar to the Insert/Remove information from above.


Conference Numbers
------------------
The first two parameters indicate the conference from which users
should be removed and the conference to which they should be added.


User Conference Adjustments
---------------------------
Like adjustments from conference insertion and removal, these
parameters indicate what conference flags users are allowed.
Further discussion can be found under Insert/Remove Group
Conferences.


Last Conference In Flag
-----------------------
Y = The user will be logged into the conference he or she was last
in assuming the "Auto-Rejoin" flag was previously set in
PCBSetup.
N = The user will not be logged into the conference he or she was
last in. This parameter will be by-passed.


Move Last Message Read Pointer
------------------------------
Y = The user's message pointer will be transferred with his or her
record. As a result, the user can begin reading messages where
he or she ended.
N = The user's message pointer will not be transferred and old
messages, if any, are subject to re-reading.



147




Adjust Users With Desired Security Levels
-----------------------------------------
The above adjustments will only be made to users with a security
level equal to or between the specified limits in the Adjust
Security Levels field. As a result, some users may be exempt from
adjustment outside a particular security group.


Adjust Expiration
-----------------
In subscription mode, PCBoard may assign a one year expiration date
from the moment the user record is created. Though one year is
standard, PCBSetup in the Node/Event/Sub-scription Information
screen allows the SysOp to define the default subscription length in
days. The above screen allows the SysOp to adjust the subscription
date for a group of users.


Normal/Expired Level
--------------------
N = The expiration adjustments will be conducted based on the NORMAL
security level rather than the EXPIRED security level.
E = The expiration adjustments will be conducted based on the
EXPIRED security level rather than the NORMAL security level.


Adjust Users With Desired Security Levels
-----------------------------------------
Adjustments will only be made to users with a security level equal
to or between the specified limits in the Adjust Security Levels
field. As a result, some users may be exempt from adjustment
outside a particular security group.


New Expiration Date
-------------------
The date specified in this field (format: MM-DD-YY) will be
substituted for the expiration date in the user records contained in
the above security level range.


Current Date Plus XXXX Days
---------------------------
Instead of a specific expiration date, the SysOp may place an
integer in this field. The integer will be added (positive number)
or subtracted (negative number) from the expiration date of users
within the security level range specified above.


Print Changed Records
---------------------
Y = All user records that have been modified will be printed.
N = Modified user records will not be printed.






148




Standardize Phone Formats
-------------------------
When invoked, PCBSysMgr will create a standard format for all phone
numbers in the USERS file. This process permits the Sort By Phone
Number option to function correctly. Without a standard format,
this sorting procedure is rendered useless.


Undo (Restore Backup)
---------------------
If the SysOp wishes to UNDO his or her last sort, pack, security
adjustment, or conference registration, this option may be invoked.
It recreates the index file and restores backup files.














































149




User Info File Maintenance
==========================
General Information
-------------------
The User Info File Maintenance option permits the SysOp to create
and edit the USER.INF file and manipulate third party software. The
USER.INF file contains information of each user record. The third
party software is accessed via PCBoard's DOOR capabilities.


User Info File Maintenance Screen
---------------------------------
Below is the User Info File Maintenance screen. A detailed
description of each option follows.


Change Conference Allocation
----------------------------
This option must be chosen and the end parameter executed if the
SysOp decides to use more than 40 conferences. The screen to the
right shows four important features of conference manipulation.
Each is discussed below.


Total Conference Areas
----------------------
This field represents the number of conferences currently defined in
the system. If greater than 40, this number minus 40 should equal
the extended conference number below.


EXTENDED Conferences
--------------------
PCBoard displays the number of conferences above 40 (Main Board plus
39 defined conferences). This feature is necessary since PCBoard
must include extra information to accommodate conferences in excess
of 40.


Static User Allocation
----------------------
The Static User Allocation field indicates storage space necessary
for each record. This field is normally 33, but increases if user
records hold Third Party Applications (TPAs) accessed through a
DOOR. However, this number remains the same despite an increase in
the number of conferences.


Dynamic User Allocation
-----------------------
The Dynamic User Allocation may change if the SysOp has more than 40
conferences. This number increases if Third Party Applications are
added to user records or the number of conferences increases.






150




Update USERS.INF File
---------------------
Y = Update the USERS.INF file. To institute any changes made in
user records, this option must be invoked.
N = Do not update the USERS.INF file.


List Installed TPA's
--------------------
When invoked, PCBSysMgr lists all Third Party Application programs
installed. In its explanation, it provides the TPA name, version
number, static and dynamic allocations, and keyword definition.


Add/Remove Third Party Applications
-----------------------------------
Third Party Applications (TPAs) are software written specifically
for PCBoard that can be accessed via PCBoard's DOOR facility.


TPA Name
--------
This represents the name of the TPA to add.


Version, Static, And Dynamic Allocation
---------------------------------------
Whomever is responsible for the development of the TPA will provide
the version, static allocation, and dynamic allocation. This
information is necessary for the application to be installed.
Version. The TPA author uses the version number to verify that the
data structure corresponds with the program used. Since Third Party
Applications may frequently change, the TPA author must use a
version number to identify the data structure necessary to implement
the program.

Static Allocation. The TPA author assigns a certain number of bytes
to each user record. The TPA needs these bytes to function
properly. Without these bytes, users are unable to execute the
Third Party Application.

Dynamic Allocation. Often times, a TPA author allocates a certain
number of bytes for each user record that changes whenever another
conference is added. These bytes are dynamic since they change with
the addition or removal of a conference. If, for instance, a TPA
author sets a dynamic allocation of 5 and 10 conferences currently
exist, PCBoard allots 50 bytes (plus any static allocation) to each
user record. If the SysOp adds a conference, PCBoard allots 55
bytes to each user record.


Keyword
-------
The keyword is the name that the SysOp gives to the TPA. When a
user wishes to access the TPA, he or she types this keyword to
access the program. This keyword must match the name of the DOOR
indicated in the DOORS.LST file of PCBSetup.


151




Create User Info File
---------------------
This option creates a new USERS.INF file that holds last message
read pointers beyond conference 39. If created while a USERS.INF
already exists, the previous USERS.INF file will be eliminated. If
the USERS.INF file becomes corrupted, the SysOp should use the PACK
option to fix it instead of creating an entirely new file.




















































152




System Configuration Analysis
=============================

Analyze USERS And INDEX Files
-----------------------------
The analysis of system configuration is often required to determine
the cause of a problem when one exists. The system analysis can be
directed to the printer port or to a text file. The SysOp
determines the path by typing LPT1 or LPT2, PRN, or FILENAME.TXT.


Print All Config. Files
-----------------------
Y = All configuration files will be printed. This includes all
PCBSetup information.
N = Configuration files will not be printed.


Perform Analysis Section
------------------------
Y = PCBoard will analyze download paths, file locations, and some
PCBSetup information to ascertain its existence. If omitted,
the analysis will reflect the download path, file, or
information absence.
N = PCBoard will not perform the analysis.


Analyze USERS and INDEX Files
-----------------------------
Y = The USERS and INDEX files will be analyzed to determine corrupt
or inconsistent files. The SysOp will be notified of any error.
N = The USERS and INDEX files will not be analyzed by PCBoard.


Printer Port Definition
=======================

Define Printer Port
-------------------
When chosen, PCBSM requests the path in which information will be
printed. Normally, this is a file since system analyses can be
lengthy. The following choices exist:

LPT1, LPT2, or PRN Information printed from PCBSM will be sent
to the local printer.

FILENAME.TXT Information "printed" from PCBSM will be
sent to the file specified. A full DOS file
specification may be used in this field.










153




Text/Graphic Editor Definition
==============================

Text And Graphics Editors
-------------------------
The text and graphics editors are used to edit files in PCBoard.
During PCBSetup, a field allows the SysOp to press the F2 or F3 key
to edit a respective text or graphics file. The file defined in
either parameter must be an executable file for that application.
For instance, the file that would be listed for Personal Editor
would be PE.EXE.

Common text editors are QEDIT, Personal Editor , and Word Perfect
Text Editor (WPE.EXE). Common graphics editors are THEDRAW and any
ANSI support programs.


Color Customization
===================
The Color Customization option allows the SysOp to define colors
seen while using any aspect of PCBoard. After selection, four
alternatives become available. The first three, Default Color Sets
1 & 2 and Default B&W Colors, will immediately change the screen
color to reflect the choice. The fourth, however, allows the SysOp
to define his or her own color scheme. The screen above provides
the tool. The SysOp may move the cursor by using any of the cursor
movement keys (up, right, home, end, pgup, and pgdn). When the
cursor sits on the field that the SysOp wants changed, he or she
simply hits the ENTER key. At this point a palette of colors
appears. Simply point to the color desired by using the cursor keys
then press the ENTER key to select the color. Press ESC to exit.




























154




Command Line Parameters
=======================

Structure: PCBSM /[Parameter];[Sub-Parameter];...;[Sub-Parameter]
/[Parameter]


General Information
-------------------
Normally, each PCBoard utility is accessed from the Call Waiting
Screen. However, a SysOp can usually accomplish the same task from
the DOS command line. In this fashion, utility commands can be
placed in EVENT.BAT files to, among other abilities, purge unwanted
information, upgrade current users, modify expiration dates, or
augment security levels. Below is a discussion of PCBSysMgr's
command line parameters.

After the PCBSM command, a list of parameters may be added. Each
parameter must be preceded by a forward slash (/) and separated by a
space. Any sub-parameter is attached to the mother-parameter with a
semicolon (;). Since PCBSM recognizes only the first four
characters of a parameter, abbreviations may be used. Following is
a typical example:

Example: PCBSM /SECU;LOWS:40;HIGH:50;NEWS:60

In the example above, all security levels from 40 to 50 inclusively
are changed to 60. Below is a table of command line parameters and
sub-parameters.

Parameter Sub-Parameters Description
--------- -------------- -----------
/Adjust FILERATIO Adjust security according to FILE
Upload:Download Ratio.
BYTERATIO Adjust security according to BYTE
Upload:Download Ratio.
UPLOADS Adjust security according to number of
files uploaded.
DOWNLOADS Adjust security according to number of
file downloaded.
SECURITY Adjust security according to security
level. LOWSEC:### defines the low end
of range.
HIGHSEC:### defines the high end.
NEWSEC:### defines the new security
level.
EXPSECURITY Adjusts the expired security level
field instead of the normal security
level.
PRINT Print all changed records. Unlike
other sub-parameters, PRINT can be
used with the other sub-parameters.

Example: PCBSM /Adjust;Byteratio;Print

Explanation: The security level of all records is adjusted by the
Byte Upload:Download Ratio table created and contained in PCBSetup.
Any record that is changed will be printed.

155




Example: PCBSM /Security;Lowsec:50;Highsec:10;Newsec:40

Explanation: All security levels between 10 and 50 are changed to
40.

/Copyexpired By itself, this parameter changes the
security level of all users whose
subscription period has ended. The
users' security level is changed to
the expired security level.

PRINT Print all changed records.

Example: PCBSM /Copyexpired;Print

Explanation: The security level of all users whose subscription
period has ended is changed to the expired security level.
Furthermore, all changed records are printed.


/Expire NORMALSEC Changes to the subscription expiration
date are based on the normal security
level and not the expired security
level. To use this sub-parameter, the
SysOp specifies a LOWSEC/HIGHSEC range
and a day or date adjustment.
EXPIREDSEC Changes to the subscription expiration
date are based on the expiration
security level and not the normal
security level. To use this
sub-parameter, the SysOp specifies a
LOWSEC/HIGHSEC range and a day or date
adjustment.
LOWSEC:### Security Level greater than or equal
to value (###).
HIGHSEC:### Security Level less than or equal to
value (###).
DATE:MMDDYY This indicates the new expiration
date. MM is the month (01 for
January); DD is the day (01 for the
first); YY is the year (91 for 1991).
DAYS:### The current expiration date is changed
by the number of days indicated in
this sub-parameter. If a negative
number is used, the date is reduced;
otherwise, a positive number will
extend a user's expiration date.

PRINT Print all changed records.

Example: PCBSM /Expire;Normalsec;Lowsec:50;Highsec:10;Days:-300

Explanation: The expiration subscription date is adjusted. The
expiration date of all users with a normal security level between 10
and 50 is reduced by 300 days.




156




/Group INSERT Insert a group of conferences. This
requires use of the FIRST and LAST
sub-parameters.
REMOVE Remove a group of conferences. This
requires use of the FIRST and LAST
sub-parameters.
FIRST:## This indicates the first conference
number. When used, the LAST
sub-parameter must also be present to
create a range.
LAST:## This indicates the last conference
number. When used, the FIRST
sub-parameter must also be present to
create a range.
MAIN Each user with a non-expired
subscription period becomes registered
in the added conferences. When used,
this sub-parameter places an R flag in
the conference registration. If a
user's subscription has expired,
access is denied.
EXPIRED Each user, regardless of subscription
expiration, is registered in the added
conferences. When used, this
sub-parameter places an X flag in the
conference registration.
SCAN This sub-parameter places the S flag
in each conference registration
allowing the user to scan the added
conferences for messages or comments.
LOWSEC:### Security Level greater than or equal
to value (###).
HIGHSEC:### Security Level less than or equal to
value (###).
RESET The message read pointer of every
newly registered user is set to 0.

Example: PCBSM
/Group;Insert;First:1;Last:5;Main;Scan;Lowsec:10;Highsec:10

Explanation: Conferences betwixt 1 and 5 are added. All users with
a security level of 10 are added to these conferences. Each user is
given an R flag if his or her subscription is current. Furthermore,
each user is given an X flag.


/Index New indices are created for all users.
This parameter is used without
sub-parameters.

Example: PCBSM /Index

Explanation: New indices are created for all users.






157




/Pack REMOVE Users whose Delete User parameter has
been set to Y or whose security level
is 0 (locked out) are deleted from the
user base.
DAYS:### Users who have not accessed the system
in the number of days indicated (####)
are removed from the user base.
SINCE:MM-DD-YY Users who have not accessed the system
since the indicated date are removed
from the user base. MM is the month
(01 for January); DD is the day (01
for the first); YY is the year (91 for
1991).
EXPDATE:#### Users with an expiration date older
than the indicated number of days
(####) are removed from the user base.
KEEP:### Any user with a security level greater
than or equal to the indicated level
(###) is not deleted from the user
base.
LOCKOUT Any user whose security level is 0
(locked out) is not deleted from the
user base.
PRINT Any user record deleted from the user
base is printed.

Example: PCBSM /Pack;Remove;Days:30;Keep:20;Lockout

Explanation: The user base is packed. All users whose Delete User
parameter is Y are deleted. Any user who hasn't accessed the system
within the last 30 days is deleted. However, any user with a
security level of 20 or greater is kept. All users with a security
level of 0 (locked out) are kept.


/STANDARDIZE When sorting by user phone numbers,
the SysOp should first place the
numbers in a standard format to
facilitate a proper numerical
sequence. By itself, this command
accomplishes that feat. This command
yields a phone format as follows:
###,###-####.

Example: PCBSM /Standardize

Explanation: All phone numbers become standardized in the format
mentioned above.











158




/ADDTPA All Third Party Application responses
can be given at the command line.
This includes the TPA name, TPA
Version, Static Size, Dynamic Size,
and Keyword.

Example: PCBSM /ADDTPA;QMAIL4;4;256;1;QMAIL4

Explanation: A Third Party Application is added called QMAIL4 is
added with a version 4. The static size is 256; the dynamic size is
1; and the keyword is QMAIL4.

/Sort NAME The user base is sorted by the user's
last name. For an alphabetic list of
current users, both expired and non-
expired, this field can be used.
PASSWORD The user base is sorted by the user's
password.
DATAPHONE The user base is sorted by the user's
business/data phone number.
HOMEPHONE The user base is sorted by the user's
home/voice phone number.
EXPDATE The user base is sorted by the user's
expiration date.
USERCOMMENT The user base is sorted by the user
comment field.
SYSOPCOMMENT The user base is sorted by the SysOp
comment field.
CITY The user base is sorted by the user's
city.
REVERSE When used with the above
sub-parameters, the user base is
sorted in reverse order: Z to A
rather than A to Z.
SECURITY The user base is sorted by security
level then by the user's last name.
TIMESON The user base is first sorted by the
number of times the user accessed the
system then by the user's last name.
DLFILE The user base is first sorted by the
number of downloads by the user then
by the user's last name.
UPFILE The user base is first sorted by the
number of uploads by the user then by
the user's last name.
FRATIO The user base is first sorted by the
Upload:Download file ratio then by the
user's last name.
DLBYTE The user base is first sorted by the
number of bytes downloaded then by the
user's last name.
UPBYTE The user base is first sorted by the
number of bytes uploaded then by the
user's last name.
BRATIO The user base is first sorted by the
byte ratio between uploads and
downloads then by the user's last
name.

159




PRIREVERSE The primary ordering routine i.e.
security level, times on, files
downloaded, etc., is conducted in
reverse order.
SECREVERSE The secondary ordering routine i.e.
user's last name, is conducted in
reverse order.

Example: PCBSM /Sort;Security;Prireverse
Explanation: The user base is sorted by security level in
reverse-numerical order then by the user's last name.
















































160




General Information
-------------------
PCBFiler is designed exclusively for PCBoard and works in
conjunction with PCBSysMgr and PCBSetup. Throughout the PCBFiler
menu, DIR is a text file that contains a list of other files.
Whenever a caller scans a directory, he or she sees a particular DIR
file and may choose any one or all of the listed files to download.
The list includes file size, file date, and a description of each
entry.

During file removal, PCBFiler makes a SysOp's task less arduous. By
simply pointing to the file for removal, PCBFiler will delete the
physical file and will remove its listing in the DIR file listing.
The SysOp can jump from one field to another pressing TAB (forward)
or SHIFT TAB (backward).


PCBFiler Access
---------------
DOS Command. By typing PCBFiler at the DOS prompt, the SysOp
can access the file manager. Command Line Parameters
(discussed later) exist to permit, among other things, file
manipulation by event processing.

PCBFiler Shell. While inside PCBoard, the SysOp can shell to
PCBFiler by pressing ALT D or by choosing PCBFiler from the
Call Waiting Screen.

While inside the PCBSysMgr environment, a selection is given
to permit PCBFiler access.


PCBFiler Screen
---------------
Below is the PCBFiler screen. A detailed description of each option
follows.


Novice vs. Expert Modes
-----------------------
A distinction between novice and expert mode has been newly added.
Either mode is toggled by pressing ALT X.

Novice. While in novice mode, the conference number, directory
number, and file date are not shown on the screen. To see this
information, the novice user must invoke ALT M which indicates a
file move. At that time, a window appears that lists the conference
and directory numbers, an option to copy or move the file, and an
opportunity to move the file offline.

Expert. If PCBFiler is run in expert mode, the SysOp will see the
conference number, directory number, and file date on the screen.
Since extra information is displayed, other fields are abbreviated.
Normally, therefore, a SysOp should understand all fields and
whatever information is contained in them before toggling to expert
mode.



161




DIR & Download Relationship
---------------------------
DIR files are difficult concepts. As before mentioned, a DIR file
contains merely a list of available files a caller may download.
The physical files to which this listing points are not found inside
this DIR file. Instead, those files are located wherever the
filename field points. Nevertheless, a strong relationship remains
between the file that controls downloads (DLPATH.LST) and the file
that controls directories (DIR.LST).

DLPATH.LST. The SysOp defines download paths inside the Main Board
Configuration screen and each Conference Configuration screen of
PCBSetup. Whenever a caller wants to download a file, PCBoard
analyzes this file to ascertain the files exact location. PCBoard
does not consult the DIR.LST file to determine which files may or
may not be downloaded. As a result, although a file may be listed
for download, it may not be available unless its path location is
placed in the DLPATH.LST file. Likewise, the SysOp can make a file
privately accessible by placing it within the download path without
listing it in a DIR file.

DIR.LST. Normally, the Main Board and each conference has its own
directory listing. The listing displays a File Name and Path, Hard
Disk Subdirectory, Sort Preference, and Directory Description. The
first field provides merely a location for a text file that contains
a list of downloadable files. The second field points to the
location of those listed files. Normally, the SysOp should place
the same Hard Disk Subdirectory path in the DLPATH.LST so a caller
may download the files listed whenever he or she scans a directory.
If, for example, the SysOp indicates C:\PCB\GEN\DIR1 as the File
Name and Path and C:\PCB\GEN\ as the Hard Disk Subdirectory, a
caller would be unable to download any file contained in the DIR1
list unless the DLPATH.LST file contained C:\PCB\GEN\ listing.


























162




Edit DIR Files
--------------
The Editing DIR Files option allows the SysOp to manipulate the main
board, conference, or off-line DIR listings. Below, the selections
on the screen to the right will be discussed in more detail.


Directory Selection
-------------------
After choosing the main board, conference, or off-line directory
option, the Directory Selection screen will provide or request the
following information.


DIR File To Edit
----------------
PCBoard provides the number of main board or conferences available
for edit. It then asks the SysOp to enter the DIR he or she wishes
to change. A 0 represents a private DIR while a 1- ## represents
any other DIR available. If the SysOp wants a list of DIR files
with their respective Attached Subdirectories, he or she may press
F2 and a list will appear.

F2 - View/Edit DIR.LST File. PCBoard permits the SysOp to modify
the DIR Text File Name and Path, Directory Description, Hard Disk
Subdirectory where the physical files are located, and the Sort
Preference. Sorting preferences are listed at page bottom. By
depressing F2 again, the screen will toggle between the Directory
Description and the Hard Disk Subdirectory/Sort Preference fields.
To insert or delete a particular listing, ALT I or ALT D may be
respectively used while the listing is highlighted.

Upload Directories. Since upload directories are not included in
the DIR.LST file, the SysOp must edit them from within PCBSetup.
The Main Board and each conference configuration have fields for the
name and location of upload DIR files.


Selected DIR Text File
----------------------
This file contains a list of files and their individual descriptions
that can be downloaded.


Attached Subdirectory
---------------------
When the above main board or conference is chosen, this represents
the directory that contains the physical files listed in the
Selected DIR Text File.


DIR Description
---------------
This is a SysOp defined description of the above file and directory
information.




163




Include Files On Disk
---------------------
Y = PCBoard will include files found in the Attached Subdirectory
whose names are not listed in the DIR text file. Whenever such
a file is listed, DSK is displayed to the left of the file. All
file listings with a DSK status can be moved to the DIR listing
by simply providing a description and saving the modification.
N = PCBoard will not include files found whose names are unlisted in
the DIR text file.


Verify Files
------------
Y = PCBoard checks the Attached Subdirectory to verify the existence
of the file listed in the DIR text file. If found, the updated
file is listed; otherwise, a DIR is found to its left indicating
the file was not found on disk.
N = PCBoard will not verify the contents of the "Attached
Subdirectory" and will list all filenames found the DIR text
file.
A = PCBoard checks the Attached Subdirectory and all other download
directories to verify the existence of the files listed in the
DIR text file. If found, the updated file is listed; otherwise,
a DIR will be found to its left.


Maximum Lines
-------------
This line indicates the maximum number of lines available for a DIR
file. It may be adjusted in the Defaults Page 1 screen.


Status Columns
--------------
First Column. The first column indicates the location of the file
listing. This column, however, is only used when the SysOp verifies
file existence (See Verify Files above). Depending on the above
settings, the SysOp will see DSK, DIR, or nothing.

Second Column. The second column describes the status of the file
listing. Whenever the SysOp moves, copies, selects, deletes, or
removes a file listing, an abbreviation will appear in this field.


DIR File Editor
---------------
When the above fields are satisfied, the Edit DIR File screen
appears. It contains information about conference number,
directory, filename, date, and description. PCBFiler permits file
listings, text lines, and secondary lines as indicated by the
screen to the right. A description of each field and the
text/secondary/file listing distinction follow.







164




File Listings
-------------
The file listing indicates the conference number, directory,
filename, date, and description. Above the keyboard definitions,
PCBFiler displays the size of the file. When a caller views the DIR
listing, he or she will see the filename, size, date, and
description.


Secondary Lines vs. Text Lines
------------------------------
Secondary Lines. Secondary lines combine with a file listing to
describe the contents of an individual file. When viewed by a
caller, the file will be listed with an extended file description.
When the SysOp edits a secondary line, PCBFiler automatically
indents the cursor.

Text Lines. A SysOp can place text lines in a DIR file to provide
extra in formation to the caller. Normally, this information
further describes the contents of the directory or any procedure the
caller should follow. Whenever a caller accesses this directory,
the text lines are displayed. They simply represent arbitrary text
that is not linked to an individual file. Whenever text lines are
placed between file listings, the file should not be sorted. If the
file listing is sorted, the text lines will be included in the sort
and likely be moved to the top of the list.

Inserting a Line. When the SysOp wants to add a text line or
another line of description to a file listing, he or she may press
ALT I. When invoked, the insert window appears that provides three
options.

The first option adds a blank line to the DIR file. As a
result, the SysOp may type an additional text line for
descriptive or content purposes.
The second option sets up the line for file listing information.
The third option provides a formatted secondary line to permit
the SysOp to add a description to a file. PCBFiler
automatically indents the cursor to add the new information.


Moving Files
------------
While manipulating files, the SysOp has the option to move one file
listing or several to another conference, directory, or both. A
file listing marked to be moved will have an MOV (novice) or an M
(expert) to its left.

Single File. When the file to move is highlighted, press ALT M.
Immediately, a window will appear that provides the following
options:

Conference Move. To move the file listing to another
conference, change the conference field to the new conference
number. When ESC is pressed to exit, the SysOp can save the
changes.



165




Directory Move. To move the file listing to another directory,
change the directory field to the new directory number. When
ESC is pressed to exit, the SysOp can save the changes.

Multiple Files. A SysOp may move several files in two ways. First,
each file may be moved by the method explained above. However, this
can become tedious if several files need moving. As an alternative,
while each file listing is highlighted, press ALT S to select the
listing. The moving window will not immediately appear, but SEL
will be displayed to the left of the file listing. Once all files
are selected, press ALT M. The moving window will appear and the
SysOp can move the file listing to another conference or directory.

Expert Mode. While in expert mode, the SysOp can simply place the
new conference or directory number in its respective field. Upon
saving, the file listing will be moved to the indicated conference
and directory. In this manner, the SysOp can bypass the ALT M
window.


Changing File Name, Date, Or Description
----------------------------------------
When the file listing is highlighted, use TAB to move forward or
SHIFT TAB to move backward to the appropriate field. Change the
desired field and exit PCBFiler. The DIR listing will be modified
and the physical file will be changed. PCBFiler utilizes several
function keys and ALT to accommodate the needs of a SysOp. Below is
a list of those function and ALT keys and a description of their
individual uses.

Function or
ALT Keys Description
----------- -----------
ESC Exits DIR File Editor. If changes have been made,
any one of the following may be entered to save: Y)
Save the changes and process the file; N) Do not save
the changes, resume editing; A) Abort, do not save
changes, exit DIR File Editor.
F1 General Help.
F2 Display DIR.LST file. The main board or respective
conference directories with descriptions will be
shown for quick access.
F3 Convert text to uppercase characters.
F4 Convert text to lowercase characters.
F5 Convert File Listing to a Text Line.
F6 Convert Text Line to a File Listing.
F7 Remove File. (Implement only on a File Listing
Line). PCBFiler will remove the physical file and
substitute a 0-byte file to prevent future uploading
of a similar file. While in novice mode, REM is
displayed to the left of the filename. If in expert
mode, R is displayed to the left of the filename.







166




F8 Copy Files Only. (Implement only on a File Listing
Line). Instead of moving a file listing from one
conference or directory to another, the listing will
be copied. As a result, the listing will be in two
places. While in novice mode, CPY is displayed to
the left of the filename. If in expert mode, C is
displayed to the left of the filename.
F9 Delete File Listing. (Implement only on a File
Listing Line). The file listing will be removed and
the physical file will be deleted. While in novice
mode, DEL appears to the left of the filename. In
expert mode, D appears to the left of the filename.
F10 Undo. The data in a particular field will be
restored to the data before it was changed.
ALT-A Repeat Last Command. The last search command,
(ALT-L) or (ALT-Z), will be repeated.
ALT-D Delete File Listing/Text Line. The physical file is
not removed.
ALT-F Free Space. When invoked, PCBFiler checks for the
amount of free bytes on the indicated disk. Before
checking, PCBFiler requests the drive to check.
ALT-I Insert Line. A screen appears that permits entry of
one of three options: a blank line, a line filled
with file descriptions guides, or a line containing a
vertical bar indicating a secondary line entry.
ALT-L Locate File. Like PCBoard's Locate command, the
SysOp may include wildcards to search for a file
listing. PCBFiler will locate the conference and the
directory.
ALT-M Move File. (Implement only on a File Listing Line).
When invoked, a window appears. The SysOp changes
the conference and directory fields to indicate the
location to which the file listing should be moved.
Once complete, an MOV (novice) or M (expert) appears
to the left of the file listing.
ALT-O Drop to DOS. The SysOp shells to DOS.
ALT-S Select File. (Implement only on a File Listing
Line). A file listing is selected to be moved or
copied at a later time.
ALT-T Today's Date. (Implement only on a File Listing
Line). When invoked, the date of the highlighted
file listing is changed to the current date.
ALT-V View File. (Implement only on a File Listing Line).
By pressing ALT V, PCBFiler analyzes the extension of
the currently highlighted file. It then implements
one of the viewing routines specified in Defaults
Page 2. The contents of the file is displayed on the
screen.
ALT-X Novice/Expert Mode. (See Novice vs. Expert Mode)
ALT-Z Locate Text. Like PCBoard's Zippy Search, PCBFiler
scans the contents of directories to find the
indicated text.


Processing DIR File
-------------------
Once editing of the DIR file is complete, changes must be saved or
aborted. The Process DIR File screen provides this opportunity.

167




Move/Rename/Delete Marked Files
-------------------------------
Y = All marked files will be respectively moved, renamed, or
deleted.
N = All files will be saved, but none will be moved, renamed, or
deleted.
A = If a file is absent from the attached subdirectory, it will
still be respectively moved, renamed, or deleted if found in a
different download path.


Duplicate Files
---------------
Y = All marked files will be checked for duplicates. If an
identical filename is found, the SysOp is asked which one he or
she prefers to keep.
N = Files will not be checked for duplicates.
A = Duplicates will be sought from the attached subdirectory of a
DIR listing or from any download path. If an identical filename
is found, the SysOp is asked which one he or she prefers to
keep.






































168




Sort All DIR Files
------------------
When invoked, a window appears that asks whether only upload
directories should be sorted. Of course, by answering YES, only
upload directories are sorted; otherwise, only download directories
are sorted. Inside the Directory Selection screen of PCBSetup,
individual DIR listings may be unsorted or sorted by name or date.
When the Sort All DIR Files option is chosen, PCBFiler will backup
the current DIR file listings in their current order. It will then
sort each DIR file listing according to the sorting preference.


Create Files List
-----------------
When chosen, PCBFiler will make a master list of all DIR file
listings. It will store this master list in the PCBFILES.LST file.
In this way, callers may download one file to get a complete list of
files available for download.


Scan For Duplicate/Missing Files
--------------------------------
PCBFiler can scan for duplicate or missing files to insure a SysOp
is familiar with any discrepancies that exist. The Scan For
Duplicate/Missing Files option searches for the following
deviations:

Once the scan is complete, PCBFiler will write information to the
file ANALYSIS.TXT. Any incongruities found will be so stated in
this file.






























169




Locate File Spec On Disk
------------------------
By choosing this option, the SysOp may search all download
directories for the specified file. In the search field, the SysOp
may use the full filename or conventional DOS wildcards e.g. *.txt.
If located, PCBFiler will show the download path, the location of
the file, and filename.


Locate File Spec In DIR Files
-----------------------------
Like the above option, the SysOp may search all DIR file listings
for the specified file. In the search field, the SysOp may use the
full filename or conventional DOS wildcards e.g. *.txt. If located,
PCBFiler will show the conference, directory, and filename.


Locate Text In DIR Files
------------------------
This option permits the SysOp to search all DIR file listings for a
text string. If found, PCBFiler will display the line in which the
string was found. If duplicate file listings are encountered, they
will not be scanned.




































170





PCBFiler Defaults Page 1
------------------------
Most software applications allow the user to set defaults. This
procedure expedites user-computer tasks and allows the SysOp to
customize the system. In PCBFiler, two screens permit the SysOp to
set defaults that regulate verification, duplication scanning,
updates, and many other attributes previously discussed under
editing DIR file listings and download paths. To the right is the
first of these two screens. Below is a more in depth analysis of
each of its fields.


Maximum Lines In DIR Editor
---------------------------
Default = 1000. This number determines how many lines can be
displayed in the DIR file editor. Of course, the number of lines is
normally a reflection of system memory available. Typically,
however, the SysOp should set this number to reflect the largest DIR
file on the system. If a DIR file exceeds this number, PCBFiler
writes data to a virtual memory location on disk. In this way, the
maximum number of lines can be exceeded and larger DIR files
displayed at the expense of processing speed.


Include Files On Disk/Not In DIR File
-------------------------------------
Y = The parameter to include files found in the "Attached
Subdirectory" whose names are not listed in the DIR text file
will be defaulted to (Y).
N = The parameter will be defaulted to (N).


Verify File Existence
---------------------
Y = The parameter to verify the existence of a file in the DIR
listing will be defaulted to (Y).
N = The parameter will be defaulted to (N).


Perform Move/Rename/Delete On Marked Files
------------------------------------------
Y = The parameter defaults to (Y). All marked files will be
respectively moved, renamed, or deleted.
N = The parameter defaults to (N). All files will be saved, but
none will be moved, renamed, or deleted.
A = The parameter defaults to (A). As a result, if a file is absent
from the attached subdirectory, it will still be respectively
moved, renamed, or deleted if found in a different download
path.


Duplicate File Check
--------------------
Y = The parameter defaults to (Y). All marked files will be
checked for duplicates. If an identical filename is found, the
sysOp is asked which one he or she prefers to keep.


171




N = The parameter defaults to (N). Files will not be checked for
duplicates.


DIR Processing In Non-Stop Mode
-------------------------------
Y = When files are listed during DIR editing, the files will scroll
without asking the SysOp to "Press any key" upon each full
screen.
N = The SysOp will be asked to "Press any key" upon each full
screen.


Delete Tagged Files From Disk
-----------------------------
Y = The parameter defaults to (Y). At processing end, all tagged
files will be deleted.
N = The parameter defaults to (N). At processing end, all tagged
files will not be deleted.
A = This question will never be asked. All tagged files will be
automatically deleted.


Update File Date With Disk Date
-------------------------------
Y = A file's date will come from the date of the physical file on
disk.
N = The file's date will come from the DIR file listing that is
specified by the SysOp.


Set FILE DATE To Today's Date
-----------------------------
Y = Whenever a SysOp moves or copies a file to another conference or
directory, the file's date is reset to the current date.
N = Each file moved or copied by the SysOp retains its original
date. To change the file's date, the SysOp must press ALT T.
A = This represents a combination of the former two. Whenever the
SysOp moves or copies a file, PCBFiler prompts the question,
"Set File's Date to Today's Date?" The SysOp may choose either
YES or NO and the date will either be respectively changed to
the current date or left alone.


0-Byte File When Moving Off-Line/Deleted Files
----------------------------------------------
Y = A 0-byte file will be created when a file is moved off-line or
deleted via the F7 key. This prevents callers from uploading
future files with the same name.
N = A 0-byte file will not be created when a file is moved off-line
or deleted. As a result, callers may re-upload the same file.


Expert Mode
-----------
Y = The SysOp enters the PCBFiler editor in expert mode.
N = The SysOp enters the PCBFiler editor in novice mode.


172




Vertical Bar Indentation For Secondary Lines
--------------------------------------------
Default = 32. In PCBFiler, a SysOp can add secondary lines to a
file listing by pressing ALT I and choosing Option 3. The beginning
of a secondary line is denoted a vertical bar (See Text Lines vs.
Secondary Lines). The number in this field determines how many
indentation spaces are printed before the vertical bar is printed
and the secondary line begins.


PCBFiler Defaults Page 2
------------------------
Like the first default screen, the second provides information that
can expedite SysOp functions and overall performance. However, the
second screen permits the SysOp to specify off-line and backup
directories, missing and duplication scans, file extensions, and DOS
commands. Above is the Defaults Page 2 screen. Below is a more
detailed analysis of each field.


Conferences In Files List
-------------------------
The numbers in this field represent conferences whose DIR files are
scanned for inclusion in the master files list (PCBFILES.LST).
Normally, private conferences are omitted from this field indicating
their exclusion from the master list. A range of conferences may be
separated by a dash (-) while individual conferences are separated
by a comma (,). For example, if a SysOp indicated 25-30,45,46, all
file listings within conferences 25, 26, 27, 28, 29, 30, 45, and 46
would be listed in the master files list.


Conference In Missing/Dupe Scan
-------------------------------
Like the above parameter, the numbers represent conferences whose
DIR listings are scanned for missing or duplicate files. This
expedites the scan by avoiding DIR listings whose physical files are
known to be absent. A range of conferences may be separated by a
dash (-) while individual conferences are separated by a comma (,).
When the scan is implemented, four possibilities can result: Files
listed in DIRs, but missing from disk; duplicate files found on
disk; files on disk, but missing from DIRs; duplicate files found in
DIR files.


Max. Files In Missing/Dupe Scan
-------------------------------
This parameter indicates the maximum number of files allowed in the
scan for duplicate or missing files. Like the maximum lines
parameter of Page 1, PCBFiler permits a virtual memory location on
disk to accommodate files in excess of memory limits. This number
should be large enough to encompass the sum of all lines in the DIR
file listings and the number of physical files on disk.






173




Off-Line Directory
------------------
The path specification indicates the location of the Off-Line
directory. Files moved Off-Line are stored here. Typically, this
path is a floppy drive to allow storage of files no longer used.


Backup Directory
----------------
Whenever a DIR file changes, PCBFiler creates a backup with a .BAK
extension. This parameter indicates the location where those backup
files will be stored.


Replacement Directories
-----------------------
PCBoard permits the use of a RAM disk. This is specified in
PCBSetup, but for proper directory orientation, the following
directories ought to be included:

Original. If this field is not blank, PCBFiler checks each
DIR file listing for an equivalent drive and path to the drive
and path specified in this field.

New. If a file is found with the ORIGINAL path, it will be
replaced with the drive and path specified in this field.

Once replaced, the SysOp may edit his or her files on the hard disk.
This insures that all changes made to RAM disk files are permanent.


File Viewers
------------
Inside the DIR file listing, the SysOp may use ALT-V to view an
archived file (any file or group of files that has been compressed).
Because of this opportunity, the SysOp must complete two fields
listed below:

Extension. Normally, every archived file has an extension
that tells the SysOp or caller which program compressed it.
Each Extension field should contain a different extension.
Common extensions are ZIP, ARC, and PAK. If some archived
files have no extension, an extension field should contain
???.

DOS Command. Each DOS Command field corresponds to each
extension field. When ALT-V is employed, PCBFiler examines
the extension and executes the appropriate DOS command.

For a file with an ARC or ZIP extension, PCBFiler executes INTERNAL
routines to view the file. For a file with a PAK extension,
PCBFiler executes a PAK V command from DOS. For a file without an
extension (???), PCBFiler executes the LIST command from DOS.






174




Customize DIR File Colors
-------------------------
The Customize DIR File Colors option allows the SysOp to define
colors seen while using PCBFiler. When the option is invoked, a
list of instructions is immediately displayed.

The color palette consists of several solid and flashing X's in a
wide array of foreground and background combinations. After the
instruction screen and before the palette's appearance, PCBFiler
displays a filing screen. The SysOp maneuvers the cursor on the
screen to the right, presses ENTER to a field, and chooses the
appropriate color.


Command Line Parameters
=======================
Structure: PCBFiler /[Parameter];[Sub-Parameter]
/[Parameter];[Sub-Parameter] ...

General Information
-------------------
Sometimes during event execution, a SysOp may want to sort directory
files, scan for duplicate files in directories, or create a files
list for future use by callers. PCBFiler has a few command line
parameters that permit these abilities. They are enacted at the DOS
prompt. Below is a discussion of PCBFiler's command line
parameters.

After the PCBFiler command, a list of parameters may be added. Each
parameter must be preceded by a forward slash (/) and separated by a
space. Any sub-parameter is attached to the mother parameter with a
semicolon (;). Since PCBFiler recognizes only the first four
characters of a parameter, abbreviations may be used. Following is
a typical example:

Example: PCBFiler /Sort;Uplo /Scan /List

In the example above, upload directories are sorted according to the
sorting preference of the SysOp; a scan is conducted in all download
directories to find and report duplicate or missing files; and a
list of files is created.

Parameter Sub-Parameters Descriptions
--------- -------------- ------------
/LIST [None] PCBFiler creates a file called
PCBFILES.LST that contains a list of
all files inside every DIR listing.
/SCAN [None] PCBFiler creates a file called
PCBFILER.RPT that contains a list of
duplicate or missing files.
/SORT All download directories are sorted by
whatever sorting preference is
specified by the SysOp.
UPLOAD Only upload directories are sorted.
PCBFiler uses the sorting preference
chosen by the SysOp.



175














General Information
-------------------
PCBMoni is used by a SysOp to monitor system callers. The SysOp can
initiate PCBMoni in three ways.

While inside PCBoard, the SysOp can press ALT-M. Once
complete, pressing ESC returns the SysOp to PCBoard.

The SysOp can invoke PCBMoni from the Call Waiting Screen.
Once complete, pressing ESC returns the SysOp to the Call
Waiting Screen.

PCBMoni can be invoked from the DOS prompt. When doing so,
the SysOp must pass two parameters with the command. These
command line parameters are discussed below.


PCBMoni Screen
--------------
Whatever method, the following screen should appear. It provides a
list of nodes, the activity of each node, and who is the present
caller on each node.


PCBoard Node Monitoring Utility Program

# Status User Reads:6
---------------------------------------------------------------
1 Transferring a File Mike Meyer (OK)
2 Available for CHAT Lee Anderson (WI)
3 Entering a Message Jasmine Computer (NH)
4 Transferring a File Alastair Mcintyre (Scotland)
5 No Caller This Node
6 No Caller This Node
7 (Inactive Node)
8 (Inactive Node)
9 No Caller This Node
10 No Caller This Node
11 (Inactive Node)
12 Entering a Node
13 (Inactive Node)
14 (Inactive Node)
15 (Inactive Node)






176




Usage
-----
The SysOp may scroll the list until the desired node is found. By
pressing ENTER, the SysOp can view the screen of the node caller.
In this way, the SysOp may type messages on the caller's screen as
if it were his own. To exit a caller's screen and return to the
PCBMoni screen, press the left ALT key. To return to the DOS prompt
or PCBoard (from whence PCBMoni was called), press ESC.


The Network Eye
---------------
PCBMoni functions in conjunction with The Network Eye or a
compatible package. The Network Eye uses a file called TNE.EXE to
view other nodes. Without this software package, however, the SysOp
can still view the activity of a node. However, he or she will see
only the PCBMoni screen and will be unable to type messages on the
caller's screen as if it were his own.

To initiate the
Network Eye, PCBMoni Parameters
PCBMoni executes
a batch file called Parameter Description
NODE.BAT. It
passes two %1 Node#
command line %2 #
parameters displayed
at right. The pound sign is the node number to view



Messages
--------
When PCBMoni is invoked, a screen appears that shows each node, the
activity of each node, and who is the present caller on each node.
The activity of each node is represented by one of the following
messages:


PCBMoni Node Activity Messages

Available for CHAT Unavailable for CHAT
CHATTING with Group Transferring a File
Entering a Message CHATTING with Node #
Waiting for Node # CHAT Request Sent
Auto LogOff Pending No Caller This Node
Out of code in DOOR Drop to DOS Pending












177




Command Line Parameters
-----------------------
Like most PCBoard utilities, PCBMoni can be accessed from the DOS
prompt although it's far easier to enter via the Call Waiting
Screen. To access PCBMoni, the SysOp must know the location of his
or her Usernet.dat file. This file location is shown on the File
Locations 2 screen inside PCBSetup.

Structure: PCBMoni [Location of USERNET.DAT] [# Nodes to Monitor]

For example, to monitor 10 nodes with the USERNET.DAT in the USER
subdirectory on drive D, the following is typed:

PCBMONI D:\USER\USERNET.DAT 10













































178




General Information
-------------------
PCBModem provides lists of the most commonly used modems. The first
screen displays the manufacturer's name of a particular group of
modems. When a selection is made, a second menu appears that lists
modems in the chosen category. If your modem is not shown, consult
the modem manual for any compatible variety. Normally, the Generic
modem listing utilizes an initialization string appropriate for most
no name brands. However, if the pre-programmed settings remain
unsuitable, the SysOp must manually enter the modem information from
within the Modem Information screen of PCBSetup.

While some command line parameters are discussed later, PCBModem is
immediately accessed by typing PCBMODEM at the DOS prompt.


PCBModem Screen
---------------
When invoked, the following screen appears. It lists general
manufacturers of modems. When one is selected, a second screen
appears that displays specific modems within the chosen category.


Multitasking Environment
------------------------
Example. When Hayes is chosen from the general list, the screen to
the right appears. The SysOp then selects the appropriate modem.
Once the modem is chosen, PCBModem asks the SysOp a series of
questions about multitasking, COMM port and interrupt locations, and
baud rate. Each question is discussed in more detail below.

Y = The SysOp is running PCBoard in a multitasking environment. That
is, software such as DESQview or OmniView is installed and will
be utilized during PCBoard operation (See Multitasking
Operations under Advanced Techniques).
N = The user is not running a multitasking environment.


Port Opening Speed
------------------
This option indicates the speed or baud rate of the modem. The
higher the baud rate the faster the modem. Available modem speeds
are 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, and
115200 baud. The baud setting is determined by the modem used and
while high speed modems can transfer information at lower baud
rates, low speed modems cannot use higher baud rates.













179




COM Port, Interrupt, & Base
---------------------------
A modem is physically connected to a communication port from which
information is sent and received.

COM Port. A computer uses COM1 and COM2 as its standardized
communication ports. PCBoard, however, permits the SysOp to name
COM ports 1 through 8 with proper definition of an interrupt and
base. If the SysOp chooses either COM1 or COM2, PCBModem continues
with the modem initialization. Whenever any COM port above two is
chosen, however, PCBModem immediately asks the SysOp for an
interrupt (IRQ) and BASE.

Interrupt (IRQ). To allow communication through a COM port, the
microprocessor must be interrupted and instructed to send or receive
information. As a result, each COM port has its own interrupt.
COM1 utilizes IRQ4 and COM2 utilizes IRQ3. These settings are
relatively standard throughout the computer industry. However,
interrupts used for ports beyond COM2 are not standard. For the
proper interrupt setting, consult the computer technical manual.

BASE. The base setting represents the hexidecimal (base 16) memory
address of the communication port. COM1 has a base of 03F8 while
COM2 has a base of 02F8. These settings are relatively standard
throughout the computer industry. However, the base value for
alternate COM ports is normally different for each computer system.
The SysOp should consult his or her technical manual for this memory
location.


Configuration Screen
--------------------
Once multitasking has been determined, baud rate chosen, and COM
port established, the Modem Configuration screen to the right
appears and another question is asked: Proceed with Modem
Initialization? If the SysOp indicates Y, PCBModem sends a string
to the modem to insure it's properly configured. If the SysOp
indicates N, PCBModem returns to the original screen with general
manufacturers' names. If Y, when the initialization process is
complete, PCBModem either signifies that the configuration was a
success or a failure.

Initialization Success. Once the modem is properly configured,
PCBModem displays the proper settings that should reside in the
parameters of the Modem Information screen in PCBSetup. To update
information in this screen, PCBModem creates a PCBOARD.DAT file that
holds all PCBSetup and new modem data. The old PCBOARD.DAT file is
named PCBDAT#.OLD. The pound sign indicates a sequential number
that increases whenever a successive PCBOARD.DAT is created with
PCBModem. Of course, if the SysOp chooses to disregard the new
settings, he or she may simply answer No to the question that
creates the new PCBOARD.DAT file.







180




Initialization Failure. If the modem configuration process responds
with an error, PCBModem returns to the second screen which displays
specific modems. At this point, the SysOp may choose a different
modem in the previously displayed category or may press ESC to
display the general manufacturer's screen.


Command Line Parameters


Structure: PCBModem /[Parameter]:[Subparameter] ...
/[Parameter]:[Subparameter]


General Information
-------------------
Like most PCBoard utilities, the SysOp can initialize a system modem
from the DOS command line. In this fashion, utility commands can be
placed in EVENT.BAT to reinitialize a modem during each event
execution. When modem information is displayed immediately be an
initialization, PCBModem displays the modem number selected from the
list below. Examples follow:

PCBModem /Modem:3 /Port:2 /19200

In the example above, modem 3 represents the Modem Selected
displayed on the Initialization Screen, COM2 is chosen (making IRQ
and BASE unnecessary), and the baud rate is locked at 19200.

PCBModem /Modem:15 /Port:3 /IRQ:3 /BASE:04F8

In the example above, modem 15 represents the Modem Selected
displayed on the Initialization Screen, COM3 at address 04F8 is used
with interrupt 3. Below is a further explanation of each function.


/MODEM:##
---------
This indicates the number of the modem to configure. The number
comes from the list below and is also displayed on the PCBModem
configuration screen immediately before initialization.


/PORT:#
-------
A computer uses COM1 and COM2 as its standardized communication
ports. PCBoard, however, permits the SysOp to name COM ports 1
through 8 with proper definition of an interrupt and base. If the
SysOp chooses either COM1 or COM2, the /IRQ and /BASE parameters are
unnecessary. Whenever any COM port above two is chosen, however,
the /IRQ and /BASE parameters must be included among the command
line parameters.







181




/IRQ:##
-------
To allow communication through a COM port, the microprocessor must
be interrupted and instructed to send or receive information. If
either COM1 or COM2 is used, the /IRQ parameter need not be
specified since both ports 1 and 2 are preprogrammed as interrupts 4
and 3 respectively.


/BASE:####
----------
The base setting represents the hexidecimal (base 16) memory address
of the communication port. COM1 has a base address of 03F8 while
COM2 has a base of 02F8. If a communication port beyond 2 is used,
this address must be included among the command line parameters.
The /BASE parameter is only used in conjunction with the /IRQ
parameter.


/19200
------
When included in the command list, the port speed is locked at a
baud rate of 19200. PCBoard, therefore, transfers information
between itself and the port at this speed while the caller receives
the information at whatever baud rate his or her modem operates. If
not included, PCBoard moves information between itself and the port
at the baud rate used by the caller.
































182




PCBoard Utility Programs
========================
Inside the PCB sub-directory are several programs unaccessible
through PCBoard, but offer considerable advantages to the SysOp.
Each program is accessible at the DOS prompt. Like the programs
listed below, all PCBoard utilities may be accessed from the DOS
prompt. Furthermore, parameters may be sent with the utility
command. The PCBoard command line utilities such as PCBSetup,
PCBSysMgr, PCBMODEM, PCBMONI, and PCBFiler are discussed in their
respective sections.


Making 14.5 Text (Multiple Languages)
-------------------------------------
Since PCBoard is distributed worldwide, it must support multiple
languages. With so many languages sprinkled throughout the globe,
it is unrealistic for PCBoard to accomodate every vernacular. To
create a system that uses multiple languages, the SysOp can use the
MKTXT145 to modify PCBoard text and error messages to reflect his or
her native tongue. Furthermore, a SysOp can use MKTXT145 to
customize a system's appearance. To the right is an example of the
MKTXT145 screen.

When the MKTXT145 command is implemented, PCBoard asks for a file to
edit, provides records to modify, and lists available commands.
Furthermore, PCBSetup must be modified to engage the language
changes. A description of each follows.

Filename The filename field has a default path equivalent to the
current DOS path. However, this field accepts full drive
and path specifications. To create a new text file, enter
the filename as PCBTEXT.[language extension]. The
language extension is normally the first three letters of
the language i.e. Spanish (SPA), French (FRE), etc. If
the file already exists, MKTXT145 calls the existing file.

Records MKTXT145 provides a record number, length, and
justification for each adjustable record. Each record is
displayed twice. The first indicates the current text.
The second can be modified by the SysOp to reflect his or
her language.


Commands Description
-------- -----------
ESC Save & Quit.
F2 Text Search. Searches for a record with the indicated
text.
F3 New Record number. The SysOp is prompted for an
integer. MKTXT145 jumps to that record.
F4 Restore the original text.
Up-ARW The previous record is displayed.
Dn-ARW Jump to next record.
PGUP Jump back 10 records.
PGDN Jump ahead 10 records.
CTRL-PGUP Jump to first record.
CTRL-PGDN Jump to last record.
~ Places hard spaces at the end of the record string.

183




PCBSetup
--------
If multiple languages are used on one system, the SysOp must set the
Multi-Lingual Operations field in Options #1 to (Y). Upon login,
PCBoard displays the PCBML.DAT file. If English is the default
language, leave this field as (N).

The PCBML.DAT file must be modified to reflect any new language. In
the Name/Loc Multi-Lang Data File field of File Locations #2, the
SysOp can press F2 to change the language menu. PCBSetup displays
at least English (default) under the language name heading. The new
language name and extension may be added. The language extension
must match the PCBTEXT extension specified above. If the SysOp
wants the new language to be the default, no extension should be
specified. PCBoard considers any PCBTEXT file without an extension
as the default language.

Options
-------
Sometimes, a SysOp wants to display messages that contain
information other than straight text. Options do exist and a
discussion of each follows.

Each field may contain @ Variables. In this way, a SysOp can
include the user's first name, last name, byte ratio, or any
other information. A list of @ Variables can be found in
Appendix VII.

In the modifiable text field, the SysOp can indicate a
filename. The filename should include the full file
specification and should be preceded by a percent sign (%)
i.e. %C:\PCB\GEN\NOTFOUND. In this file, the SysOp may use @
Variables.

When a file is placed in the field, the file specification may
be followed by a plus sign (+) and additional text. The
additional text is written to the Caller's Log. For example,
the field entry %C:\PCB\GEN\NOTREG + in conference @[email protected]
copies the current operation into the Caller's Log.




















184




PCB145 (and BOARD.BAT)
----------------------
This file, PCB145.EXE, is the PCBoard executable. It is executed by
the BOARD command and only within the BOARD.BAT file should it be
called. To the right is the BOARD.BAT file. An explanation of each
function is described below.

Net Clock \\n10. This line synchronizes the workstation's timer
with the timer on the file server.

Set pcb=/swap. When the SWAP environment switch is used, all but
approximately 10 kilobytes of PCBoard is taken from memory leaving a
great deal more for alternate programs. The SWAP function accesses
one of the following in the indicated order: Extended Memory,
Expanded Memory, or the Hard Disk.

Set dszlog=pcbdsz.log. During a ZMODEM file transfer, a log can be
created that contains information about the file transfer. In order
for PCBoard to create the log, this line must be included in the
BOARD.BAT file.

If/Rename. Each IF statement resets remote, event, or door
activities to prevent an accidental execution.

PCB145. PCBoard is executed.

IF/Exist. When a particular function is requested, PCBoard creates
a file with a BAT extension. For example, if a SysOp chose SysOp
Function 9, a file called REMOTE.BAT is created. As a result,
REMOTE is executed as indicated by one of these lines. After
completion, the BOARD.BAT file is recalled, files are reset, and
PCBoard is executed. These IF/Exist statements, however, may be
replaced by IF statements that correspond to specific error level.


























185




Sample BOARD.BAT File
---------------------
echo off
C:
cd \pcb

net clock \\n10
set pccb=/swap
set dszlog=pcbdsz.log

if exist remote.bat rename remote.bat remote.sys
if exist event.bat rename event.bat event.sys
if exist door.bat del door.bat

pcb145

if exist remote.bat remote
if exist door.bat door
if exist event.bat event
if exist endpcb goto end

board
:end

Error Levels and Descriptions
=============================
Error Level Description
----------- -----------
0 Normal exit at SysOp request.
1 Exit to DOS for the event.
2 Exit to DOS for a door.
3 Exit to DOS for remote DOS operation.
4 Exit to DOS to run PCBPack.
5 Exit to DOS caused by caller saying GOODBYE.
99 An error occurred which dropped it to DOS.

If error level values are tested after PCB145, they must be tested
in reverse order since DOS considers a lower number test to be true
for any higher numbered error level value.

Sample Error Level Statements
=============================
If ERRORLEVEL == 3 goto remote
If ERRORLEVEL == 2 goto door
If ERRORLEVEL == 1 goto event
If ERRORLEVEL == 0 goto exit













186




PCBCMPRS.BAT
------------
When a user executes a command sequence such as R A Z, this batch
file compresses the capture file before transferring it. Below is a
description of each parameter.

%1. This parameter represents the compressed file name.
%2. This parameter represents the uncompressed capture file
name.

After the compression is completed, the %2 filename is removed. The
location of both files is specified in File Locations 1 of PCBSetup
under Location of Temporary Work Files.


PCBCopy
-------
Structure: PCBCopy [source] [destination]

This program acts as the DOS COPY command, but is able to copy a
program that is currently in use. The source indicates the file to
copy. The source is copied to the destination path. This command
uses all wildcard characters used by DOS including the question mark
(?) and asterisk (*). For further instructions on the use of
wildcards, consult the DOS manual.


PCBDiag
-------
Structure: PCBDiag

A SysOp may encounter a problem that is beyond his or her expertise.
If this occurs, PCBDiag can be executed to implement a diagnostic
analysis of the system configuration. The program locates system
incongruities, tests COM ports, determines the amount of free space
on the hard drive, and submits other important information for a
meaningful and thorough examination of the PCBoard system. Once the
analysis is complete, information can be sent to a file or to a
printer and its evaluation respectively uploaded or sent to our
technical support staff. PCBDiag provides a prompt that requests a
filename or a printer port. The filename prompt accepts a full DOS
specification while the printer port should be indicated by LPT1 or
LPT2 depending on which parallel port the printer is connected.
















187




PCBDisk
-------
Structure: PCBDisk [Drive]

This program acts similar to the DOS CHKDSK command. However, the
SysOp can check network drives that are currently in use. Since
many storage facilities require constant monitoring to insure
adequate space, this program provides an advantageous tool.


PCBNum
------
Structure: PCBNum [Integer]

When invoked, the caller number is reset to the indicated integer.
Each caller thereafter is given a successive number. If, for
example, PCBNum 1 were entered, the next caller would be numbered 2;
the second caller, 3; the third caller, 4 and so on.


PCBPack
=======

Message Base
------------
A SysOp packs the message base for a number of reasons. Among
others, he or she can rid the base of old, duplicate, or private and
received messages. The message base may also be renumbered. Each
of these options is not independent of another. Instead, each
option is used in association with another to create a combination
that can usually satisfy the needs of any SysOp. The PCBPack
program is executed from the DOS prompt or by using SysOp Command 3
or 8. Each additional option is separated by a space and preceded
by a forward slash (/).

Example: PCBPACK /Area:4-5 /Date:042590 /Fast

The example above packs conferences four and five, deletes all
messages created before April 25, 1990, and displays minimal
information on the screen. A discussion of each option follows.


/AREA:##;##-##;...;##-##
------------------------
The Area option permits specific packing of a single conference or
a range of conferences. Each conference number or range must be
separated by a semicolon (;) or a hyphen (-). The hyphen also
designates the range for packing. For example, /AREA:1;8-10;44-86
packs the message base in conferences 1, 8, 9, 10, and from 44 to 86
inclusively. With the exception of /HELP, the /AREA option is
necessary in every PCBPack structure for messages or the command
will be aborted.







188




/CAP:[Filename].[EXT]
---------------------
During a message base pack, any message number whose message was
removed is sent to the specified file. The file can later be viewed
by the SysOp. Inside the capture file, each deleted message is
tagged with an explanation for its removal. Among other reasons, a
deleted message may have been a duplicate or created prior to a
specified date. If the indicated capture file already exists, new
information is appended to the old capture file.


/CRC:[Number of Days]
---------------------
Some systems have enormous message trafficking i.e. Echo Mail
Systems. Although packing occurs consistently, duplicates may not
always be found since they are uploaded on a different day. To
remedy this, a SysOp can indicate old messages within a number of
days that ought to be saved for future comparison. For example, if
the current date is April 25, 1990 and /CRC:2 is included in the
PCBPack command, the following occurs. Message numbers from April
23 and April 24 are stored in an alternate file. The file is the
current message base name with a CRC extension. The CRC numbers are
then compared to future messages.


/DATE:MMDDYY
------------
Using the specified format, a SysOp can indicate a date-sensitive
pack. Any message created before this date is deleted. The MM
indicates the month, 01 for January; DD indicates the day, 01 for
the first; and YY indicates the year, 90 for 1990. Any message
created on the specified date is not deleted. If the /CAP option is
attached to the PCBPack structure, any message removed is sent to a
capture file.


/DAYS:[Number of Days]
----------------------
When added to the PCBPack structure, any message older than the
number of days indicated is deleted. Consider this example. The
current date is August 23, 1990, and /DAYS:5 is added to the PCBPack
structure. All messages created on or before August 18, 1990 are
deleted.


/FAST
-----
Normally, PCBPack displays all message numbers and an explanation
for each message. However, if the /FAST option is added, only
deleted and duplicate messages are displayed (same information sent
to a /CAP file). Since less information is written to the screen,
the packing process is expedited.







189




/FORCE
------
Before a message base pack, PCBPack checks each node to insure
PCBoard is no longer running. Since some networks may run up to 99
nodes, a SysOp may have difficulty ceasing PCBoard activity on each
node despite the need to pack the message base. As a result, the
/FORCE option can be used to bypass PCBPack's check of node
activity. If a caller accesses the message base while a pack is in
progress, he or she will see the following prompt: Network
Delay-Message Base in use.


/HELP
-----
A SysOp invokes this command to view examples from PCBPack. This
option is independent of all others. Its format for use follows:

PCBPack /AREA /HELP.


/INDEX
------
For expeditious retrieval, PCBoard uses an index file to locate
messages. If, however, the index file becomes damaged, it can be
recreated with this option. A SysOp knows an index file is corrupt
when a message number does not correspond with the intended message.
During the index packing process, messages are not deleted nor does
any sort of checking occur. This option is independent of all
others. Its format for use follows: PCBPack /INDEX.


/KEEP
-----
Sometimes, a SysOp may run a date or day sensitive pack. However,
some messages, although older than a given date or a specified
number of days, may be unread by the recipient. This option keeps
all unread and private messages regardless of their creation date.
The /KEEP option, however, cannot be used with the /MAXMSGS option
(discussed later).


/KILLBAK
--------
Normally, before a pack, PCBPack duplicates the message base file
and adds a BAK extension. After packing is complete, a new message
base will have been created and the old message base stored in
[Message Base Name].BAK. However, if this option is used, PCBPack
deletes the backup message base once packing is complete. While
this opportunity risks the inability to return to a previous message
base, it is advantageous for SysOps with little storage space.

/KILLDUPS
---------
Unless indicated, PCBPack retains duplicate messages. A duplicate
message has the same message content and header information as
another message. This option causes all duplicate messages to be
deleted. If a /CAP option is indicated in the PCBPack structure,
the message number is copied to a capture file. The message number
will have a description indicating that it was a duplicate message.

190




/MAXMSGS:[Number of Messages to keep in a conference]
-----------------------------------------------------
The /MAXMSGS option limits the number of messages kept in a message
base. Normally, this feature is useful for SysOps that utilize
NetMail Systems. Such systems often import several, sometimes
hundreds of messages. Since most systems are limited by disk space,
a restriction on the number of messages is often an indispensable
necessity. If, however, the number of messages exceeds the /MAXMSGS
amount, older messages are eliminated regardless of their status.
If, for instance, a message base contained 500 messages and
/MAXMSGS:400 was used to pack, the first 100 messages would be
eliminated. This option cannot be used with the /KEEP option.


/NOCALLER
---------
Whenever a message base is packed, PCBPack sends a message to the
caller's log indicating a conference number and a successful
purification of the message base. If /NOCALLER is used, PCBPack
does not send a message to the caller's log.


/NOSIZE
-------
Normally, PCBPack checks for sufficient hard disk space before
attempting a user base pack. However, the SysOp may eliminate that
check, expedite the packing procedure, and attain identical results.
If the SysOp bypasses disk space checking, but hasn't sufficient
storage, the process is aborted.


/PURGE
------
When included in the PCBPack structure, any private and received
message is deleted. Received indicates that the person to whom the
message was sent has read the message.


/RAMDISK:[Ram Drive]
--------------------
A RAM Disk acts as a hard disk that resides in memory. A user
reads, writes, and copies information from the RAM Disk as if he or
she were using a regular hard disk. The /RAMDISK option creates
the message base in memory. As a result, its construction is more
expeditious than if it were created on a normal hard drive.
Following the /RAMDISK parameter is a letter than indicates the
location of the Ram Disk. Once the message base is created, PCBPack
copies the message base from the RAM Disk to the hard drive.

/RENUMBER:[Number From Which To Begin Increment]
------------------------------------------------
Normally, after packing, each message retains its original number.
However, a SysOp can renumber the message base using this option.
The first message is numbered as the integer following the Renumber
colon and each successive message is incremented by 1. Renumbering
is not recommended since many users memorize the number of a
particular message that contains important information. Furthermore,
message read pointers are not adjusted to new message numbers.

191




/UPCASE
-------
A user can read messages off-line with an off-line reader such as
QMail. Most off-line readers produce lowercase subject fields. The
/UPCASE parameter converts the lowercase subject fields to uppercase
letters.

Normally, a SysOp packs the users base to eliminate old or
previously "deleted" users. However, other options exist. Each
option is not necessarily independent of another. That is, a SysOp
can use these functions symbiotically and normally attain a
combination that satisfies his or her needs. The PCBPack program is
executed from the DOS prompt. Each option is separated by a space
and preceded by a forward slash (/).

EXAMPLE: PCBPACK /USERS /DATA:042582 /FAST

In the example above, the user base is packed. In the packing
process, however, all users who last logged into the system before
April 25, 1990 are removed (/DATA:042590). Furthermore, only
minimal information is displayed (/FAST). Each of these options and
several others are discussed below.


/USERS
------
To pack the Users file, this parameter must be included in the
PCBPack command; otherwise, the packing procedure will be aborted.
If the /USERS parameter is used by itself, the Users file will be
packed and all users with a Y in their Delete User field are
deleted.


/CAP:[Filename].[EXT]
---------------------
During a user base pack, any user record removed is sent to the
specified capture file. The file can later be viewed by the SysOp.

Inside the capture file, each deleted record is tagged with an
explanation for its removal. Among other reasons, a deleted user
record may have been a duplicate or created prior to a specified
date. If the indicated capture file already exists, new information
is appended to the old capture file.


/DATE:MMDDYY
------------
Using the specified format, a SysOp can indicate a date-sensitive
pack. Any user who has not logged onto the system since the
indicated date is deleted. The MM indicates the month, 01 for
January; DD indicates the day, 01 for the first; and YY indicates
the year, 90 for 1990. Any user record created on the specified
date is not deleted.






192




/DAYS:[Number of Days]
----------------------
When added to the PCBPack structure, any user who has not logged
onto the system within the indicated number of days is deleted.
Consider this example. The current date is August 23, 1990, and
/DAYS:5 is added to the PCBPack structure. All user records created
on or before August 18, 1990 are deleted.


/EXPDATE:MMDDYY
---------------
Using the specified format, a SysOp can indicate a pack sensitive to
a user's expiration date. Any user record whose expiration date is
before this date is deleted. The MM indicates the month, 01 for
January; DD indicates the day, 01 for the first; and YY indicates
the year, 82 for 1982. Any user record whose expiration date
matches the specified date is not deleted.


/FAST
-----
Normally, PCBPack displays all user numbers and an explanation for
each user deletion. However, if the /FAST option is added, only
deleted and duplicate messages are displayed. Since less
information is written to the screen, the packing process is
expedited.


/HELP
-----
A SysOp invokes this command to view examples from PCBPack. This
option is independent of all others. Its format for use follows:
PCBPack /USERS /HELP.


























193




/KILLBAK
--------
Normally, before a pack, PCBPack duplicates the user base file and
adds a BAK extension. After packing is complete, a new user base
will have been created and the old user base stored in [Message Base
Name].BAK. However, if this option is used, PCBPack deletes the
backup user base once packing is complete. While this opportunity
risks the inability to return to a previous user base, it is
advantageous for SysOps with little storage space.


/LEVEL:[Security Level]
-----------------------
Any user with a security level greater than or equal to the
indicated level will not be deleted from the user base. This
PCBPack parameter holds the greatest seniority. As a result, even
if a user meets other deletion requirements, his or her record is
retained. However, users previously flagged for deletion will be
removed.


/LOCK:DROP
----------
Any user with a security level of 0 is deleted from the system. A 0
security level indicates that the user was previously locked out of
the system. All other user records, notwithstanding other PCBPack
parameters, are not deleted.


/NOCALLER
---------
Whenever a user base is packed, PCBPack sends a message to the
caller's log indicating a successful purification of the user base.

If /NOCALLER is used, PCBPack does not send a message to the
caller's log.


PCBSTATS
--------
The PCBSTATS program updates the PCBSTATS.DAT file outside of
PCBoard. Normally, a SysOp updates system and local statistics from
the Call Waiting Screen. This utility, however, enables third party
authors to update statistics without knowing the format of the
PCBSTATS.DAT file. Below is a list of mandatory and optional
parameters for the program.

Format: PCBSTATS /FILE:[Loc. & Name of PCBSTATS.DAT file] /NODE:#
/[Optional Parameters]










194




PCBSTATS Parameters & Descriptions
==================================

Mandatory or
Parameters Optional Description
---------- ------------ -----------
/FILE:[filename] Mandatory The SysOp must indicate the full
name and location of the
PCBSTATS.DAT file.
/NODE:## Mandatory This mandatory parameter specifies
the node number. If using an S or
D version of PCBoard the node
number should be 0.
/RESETNODE Optional Resets the statistics for the
indicated node.
/RESETALL Optional Resets the statistics for all
nodes.
/MSGS:### Optional This adds the number indicated to
the number of messages currently on
the system.
/UP:### Optional This adds the number of uploads
recently completed to the number of
uploads previously conducted.
/DOWN:### Optional This adds the number of downloads
recently completed to the number of
downloads previously conducted.
/NAME:[name] Optional This parameter specifies the name
of a caller who recently
disconnected from the system. It
should only be used at logoff.
/CITY:[city] Optional This parameter specifies the city
of the caller who recently
disconnected from the system. it
should only be used at logoff.

Example: PCBSTATS /file:PCBSTATS.DAT /node:1 /name:DAVID TERRY
/city:SLC, UT

Explanation: On node 1, PCBoard indicates that DAVID TERRY from
SLC, UT logged off the system.


Example: PCBSTATS /file:PCBSTATS.DAT /node:2 /up:1 /down:2

Explanation: On node 2, PCBoard indicates that the current user has
recently had one uploaded file and two downloaded files. These
numbers are respectively added to the number of uploads and
downloads previously indicated.











195




PCBTEST.BAT
-----------
The PCBTEST.BAT file tests files to insure they pass certain file
specifications. If a SysOp wants to test uploaded files for
viruses, procedures in this batch file can be used. This batch file
is called for two reasons that follow.

Viruses. The PCBTEST.BAT file to the right has the rudimentary
logic for testing ARC and ZIP files. However, a SysOp can add
similar logic to scan for viruses. If the file does not pass the
logic test, a file called PCBFAIL.TXT is created and displayed;
otherwise, no file is created. If, however, a file called
PCBPASS.TXT exists, it will be displayed. A FAILED message is
appended to a file description if the file failed the logic test.
Furthermore, the caller who uploaded the file receives no credit for
the file.

Uploads. When a file is uploaded, the PCBTEST.BAT file is
automatically executed and two parameters are passed to it. A SysOp
can use these parameters to invoke branching inside the PCBTEST.BAT
file. For an example, consider the following:

If not "%2" == "UPLOAD" goto test

This statement determines whether PCBTEST.BAT was called as a result
of an upload. If so, a following program could strip comments from
the file or check for viruses. If an upload did not occur, the line
branches to the TEST subroutine.


PCBVIEW.BAT
-----------
The PCBVIEW.BAT file is executed whenever a user initiates a view on
a particular file i.e. F V. When such a command is invoked, PCBoard
begins a three part process.

The PCBVIEW.BAT file normally activates a TESTFILE routine
that ascertains what kind of file will be viewed. The
TESTFILE routine (discussed later in this section) analyzes
the extension of the file, branches to an appropriate part of
the program, and initiates a sequence of viewing routines.

Once the program has branched and the file has been analyzed,
a directory of its contents is placed in a second file called
PCBVIEW.TXT. Although this file will not hold the exact text
of the file, it will list the files contained in the zip, arc,
or pak file. The testing procedure, however, is not limited
to these three extensions.

PCBoard automatically displays the PCBVIEW.TXT file as a
result of the previous invocation of F V.









196




Reading a PCBTEXT file
----------------------
Structure: RDPCBTXT PCBTEXT.[language extension]

This command reads any PCBTEXT file and places its contents in
another file called PCBTEXT.LST. In this file, the SysOp will find
the record number, a color code integer, and the text from the
record. RDPCBTXT provides ease of access to all error messages and
miscellaneous text accessed by PCBoard. To the right is a sample
listing of the PCBTEXT.LST file.

The RDPCBTXT command can read all PCBTEXT files created by previous
versions of PCBoard.


TESTFILE
--------
Structure: TestFile %[filename logic number] [text] [text] [text]

This command is only used in a batch file to indicate a certain
extension. Once the filename is analyzed, TESTFILE returns an error
level that causes a branch to another part of the batch program. To
the right is an example of the TESTFILE command. If no matches are
found in the search, error level 98 is returned.


%[filename logic number]
------------------------
This number corresponds to the file that followed the command that
called this program. In our example, %1 indicates the file
TEXT.ZIP.


[Text]
------
The text represents a string for which the %1 is scanned. Depending
on what text is found determines the error level returned. In our
example, TestFile would return an error level 2 which causes a
branch to the :ZIP routine. If the indicated text were not found,
TestFile would return an error level 98. According to DOS rules,
error levels must be tested in reverse order.


ViewZip
-------
Structure: ViewZip [filename with a .ZIP extension]

Once a file has been "zipped" or compressed by the ZIP.EXE command,
its contents may be viewed with this command. The user does not
immediately see the file. Instead, ViewZip places the contents of
the file in another file called PCBVIEW.TXT. Afterwards, PCBoard
automatically displays the file tot he caller. To display the
contents, type the following at the command line:

C:\PCB>TYPE PCBVIEW.TXT




197




Network Operations
==================
Network Requirements - General Information
------------------------------------------
A network allows two or more computers to be physically connected.
Each computer is called a node and may provide further data lines
for a system. Though network configuration is not difficult, it
does require a dedicated SysOp, adequate hardware, appropriate
software, and proper file storage. Each of these is discussed
further below. A generic network configuration is provided that can
facilitate setup for first time users.


Hardware Requirements
---------------------
To run PCBoard in a network, the system must utilize an E3 version
or above. Though multiple machines are not always necessary, a
network is normally comprised of several computers. The system must
function with DOS 3.1 or above. The network software must be 100
percent NETBIOS (Network-Basic- Input-Output-System) compatible. A
file server, dedicated or undedicated, must also exist. In this
manner, a commonly accessible location exists for file trafficking.

Personal Computer. Though 286 class machines or greater are
recommended for network operations, each computer must be 100
percent DOS compatible. Furthermore, the DOS version should
be 3.1 or greater and provide the SHARE.EXE file. The file
server should normally utilize at least 2 Megabytes of memory
(more if the server is running NOVELL software). This added
memory is necessary for disk caching. A computer workstation
does not need this much memory. In fact, PCBoard can function
with as little as 200 kilobytes of memory.

Monitors. Any monitor may be used from an inexpensive
monochrome to a costly VGA system. If a system is solely
dedicated to PCBoard, no functional advantage exists in using
a color system over a monochrome system. However, if a SysOp
designs a colored menu or other colored display, a CGA monitor
is necessary to view what the caller sees.

Network Software. PCBoard functions well with several network
software packages. Among the most common are LANtastic,
Novell, IBM, 3COM, Orchid, Vianet (Starlan), and Network-OS.

Multitasking Software. If multitasking software is used
(DESQview or Windows 3.0), an 80386sx-based machine or above
should be used for adequate speed and proper memory
management.

File Server. For swift network operations, a 386 class
machine or greater is recommended. Files must be stored in a
commonly accessible location. This is often called a file
server and may be used as a separate node or dedicated solely
to file trafficking. As more files are accessed from the file
server, file trafficking increases and system speed decreases.
The file server should normally utilize at least 2 Megabytes
of memory (more if the server is running NOVELL software).
This added memory is necessary for disk caching.

198




Independent & Dependent Files
-----------------------------
Independent files may be stored on each node's hard drive while
dependent files must exist on the file server for proper execution.

Below is a list of dependent files. The list shows only files that
must be stored on the file server. However, others may be added.

USERS & PCBNDX.[Letter]. The USERS file holds all pertinent
user information. When a caller enters his or her user name
and password, this file is searched to allow or prohibit
access to the system. As a result, it must reside on the file
server to allow each node equal access. The PCBNDX.[Letter]
files provide an alphabetic index of user names. Twenty-six
index files exist and all should reside on the file server.
Their names, of course, are simply PCBNDX.A, PCBNDX.B,
PCBNDX.C, etc.

MSGS & MSGS.NDX. The MSGS file contains messages left by
callers, SysOps, and other users. Each caller may leave a
message for another person. The recipient may then retrieve
the message and read it. As a result, the MSGS file must
reside on the file server to allow each node equal access.
The index file for messages is merely the message base name
with an NDX extension. This file must also reside on the file
server.

USERNET.DAT. The USERNET.DAT file controls all network
function displays and NODE CHAT operations. To allow
communication between nodes, this file must reside on the file
server.

CNAMES. The CNAMES file contains pertinent conference
information. Since each caller has access to specific
conferences, the file must reside on the file server. This
permits access to conferences by each node regardless of
caller identification.

Callers. To view each node's caller's log, the SysOp must
place the caller's log for each node on the file server.
Whenever the SysOp function 13 is executed, the SysOp may view
the caller's log of an alternate node.

*.CHT. All CHAT files with the CHT extension must reside on
the file server. This, like the USERNET.DAT file, permits
communication between different nodes.

Conference Message Bases & Indices. Like the MSGS file, each
conference may have its own message base. These message bases
must reside on the file server for the same reasons as the
MSGS file.

Downloadable Files. Any files that a caller may download
should be located on the file server. Although duplicate files
may reside on each node's hard drive, this constitutes a waste
of hard disk space. These downloadable files are listed in the
download DIRx files.


199




Public Uploads. For a caller to access a particular upload
directory, the directory must exist on the file server. It,
however, may reside on each node's hard drive, but this is
unnecessary and a waste of hard disk space. These directories
are listed in the upload DIRx files.

Although these files must reside on the file server, the SysOp may
choose to store others as well. Some common files on a file server
are WELCOME, SCRIPT, ANSWER, BLT, and all DIR listings. These,
however, are optional.


SHARE.EXE and Networks
----------------------
SHARE.EXE is a file that comes with the DOS package. The file
permits a node to share information contained on the file server
while remaining a local node. Normally, the file should be executed
following the execution of network software. For further
information concerning SHARE.EXE, consult the DOS or network
software manual.







































200




File Server Configurations
==========================

Config.Sys File
---------------
The file server is a common
access location for many network Config.sys File
files. It must be configured and
booted before further network Device=\sys\evemm.sys
nodes can function. The (Hardware EMS Driver)
CONFIG.SYS file must exist in any
DOS environment for any program Files=150
to function. The file assigns buffer (Sufficient File
and file space and indicates Handles)
hardware configurations. To the
right (bold print) is an example of Lastdrive=Z
a typical CONFIG.SYS file for a (Network up to Z)
LANtastic environment. The file is
not limited to these parameters, however, and may hold different
information. Sometimes, a SysOp chooses to run a program that
requires extra environment space. Though unaware of this necessity,
an error message (Not enough environment space) will occur to inform
the SysOp. To correct this error, the following can be added to the
CONFIG.SYS file: Shell=c:\Command.com /E:512 /P. This command sets
the environment space to 512 bytes, four times the normal level.
Normally, this level should not exceed 1,024.


AUTOEXEC.BAT
------------
The AUTOEXEC.BAT file is an executable file containing DOS commands.
It normally initializes the system, loads appropriate software into
memory, and specifies configuration information. Below is a sample
AUTOEXEC.BAT file. The file is not limited to these parameters,
however, and may hold different information.



Echo Off
Path=C:\DOS;C:\LANTASTI
CD \LANTASTI
LANBIOS IRQ=5 ADDRESS=6
REDIR N10
SERVER
SHARE /L:64
CD \PCB
BOARD












201




Node Configurations
===================
Like the file server, each node
requires its own CONFIG.SYS file. Config.sys File
Normally, each node utilizes a
similar file, but depending on Files=20
hardware restrictions, the files may (Sufficient File
be different. To the right is a Handles)
sample CONFIG.SYS file. The only LastDrive=Z
difference between it and the file (Allows networking
server is the number of files drives up to Z)
specified. Sometimes, a SysOp
chooses to run a program that requires extra environment space.
Though unaware of this necessity, an error message (Not enough
environment space) will occur to inform the SysOp. To correct this
error, the following can be added to the CONFIG.SYS file:
Shell=c:\Command.com /E:512 /P. This command sets the environment
space to 512 bytes, four times the normal level. Normally, this
level should not exceed 1,024.

Below is a sample AUTOEXEC.BAT file. The file is not limited to
these parameters, however, and may hold different information.


ECHO OFF
PATH=C:\DOS;C:\LANTASTI

CD \LANTASTI
LANBIOS IRQ=5 ADDRESS=6
REDIR N1
SERVER
SHARE <--Share.exe loaded locally.
CD \PCB
NET LOGIN \\N10 NODE1 <--Login to file server.
NET CLOCK \\N10 <--Use file server's system clock
instead of local clock (Sync-
ronizes local clock with
server's clock).
NET USE H: \\N10\N10D <--Set hard disk to use on the
server.
BOARD <--Call PCBoard.



Each node must log into the file server. Despite the example
above, each network package has unique commands for node-file
server communication. The SysOp should consult his or her manual
for this information.











202




Setting Up a Multinode PCBoard System
=====================================

General Information
-------------------
A SysOp can follow the steps below to setup a three node PCBoard
system. Of course, these procedures can be simply modified to
configure two nodes or more than three.

1. Use the INSTALL program and the installation steps at the
beginning of this manual to configure one node for operation.

2. Create a separate directory for each node. Generally, the
INSTALL program places node one in C:\PCB. For consistency, a
SysOp should place each successive node in C:\PCB2 and
C:\PCB3.

If each node utilizes a separate hard drive, a SysOp need not
create differently named directories. Instead, each hard
drive may have a C:\PCB directory for each node.

3. After Node 1 operates, enter PCBSetup and make two changes.

Node/Event/Subscription Screen: Answer YES to Running Under
a Network.
Node/Event/Subscription Screen: Place a 1 for the Node
Number parameter.

4. Include the SHARE.EXE command in the AUTOEXEC.BAT file and
reboot the computer. Some networks have SHARE compatibility
making SHARE.EXE unnecessary.

5. After system rebooting is complete, operate node 1 to insure
it functions properly.

6. Copy the following files to each node directory.

BOARD.BAT, EVENT.SYS, PCBOARD.DAT, REMOTE.SYS, PCBERR.OLD,
PCBPROT.DAT, PCBPACK.EXE

The PCBPACK.EXE is only necessary if the user or message base
will be packed from any node besides node 1.

7. A SysOp can either copy all files into each node directory or
simply share the remaining files between nodes. If all files
are copied, skip step 8; otherwise, follow step 8 to produce
proper path configurations.

8. Path configuration can be created in two ways.

Modify the AUTOEXEC.BAT file to include \PCB in the PATH
statement. For example, PATH C:\DOS;C:\PCB.
Modify the BOARD.BAT file in each node directory to read
C:\PCB\PCB145 instead of merely PCB145.





203




9. Enter PCBSetup from the C:\PCB2 and C:\PCB3 directories
respectfully and make the following changes.

Node/Event/Subscription Screen: Place a 2 for the Node
Number parameter.
Node/Event/Subscription Screen: Place a 3 for the Node
Number parameter.

From this point, all three nodes should be functional. However, if
using a multitasking system, each node must have a different COM
port setting i.e. Node 1 uses COM1, Node 2 uses COM2.
















































204




Example Network Setup
=====================


File Server

Stores:
- Message bases
- Users file
- Files for download
- Other shared files

Hardware:
- Network card
- Tape backup unit





Network
Cable






Remote Access Remote Access Local Access
Workstation Workstation Workstation

If local storage is If local storage is If local storage is
available, it may available, it may available, it may
store: store: store:
- PCBoard program - PCBoard program - PCBoard program
- Help & Menu - Help & Menu - Help & Menu
Files Files Files
- Other files not - Other files not - Other files not
shared on shared on shared on
network network - Other locally
Hardware: Hardware: used programs
- Network card - Network card
- RS232 port - RS232 port Hardware:
- MODEM - MODEM - Network card















205




Advanced Techniques
===================

Conference Registration & Security Levels
=========================================

General Information
-------------------
A conference is either private or public. The former indicates only
registered users may join. The latter indicates that any user with
a sufficient security level may join. Furthermore, any user
officially registered in a public conference may join regardless of
security level.

Since many systems have grown enormously over the years, a SysOp has
difficulty registering each new user into particular conferences.
As a result, PCBoard provides a few added features to make
conference registration a simpler task.

Below is a table that shows conferences, security levels, and an
explanation of each unique setup.

Public Required Explanation
Security
------------------------------------------------------------------
N None 1. New Users are not registered in private
conferences.
2. Existing users must be registered to join.

Y 0 1. New users are automatically registered.
2. Existing users register themselves upon
joining.
3. Anyone not locked out by the L conference
flag may join.

Y 10 1. New users are not automatically registered.
2. Existing users with a level of 10 or above
may join.
3. Existing users do not register themselves.
4. Existing users who are officially registered
in the conference and not locked out by the L
flag may join regardless of security level.

Y -1 1. New users are officially registered
automatically.
2. Existing users not locked out by the L flag
must be registered to join.












206




Disk Caching & RAM Disks
========================

General Information
-------------------
As programs become lengthy and complex, processing speed becomes an
inevitable concern. Even if a program's length remains constant,
users have adopted a not so unusual affinity with speed. Through
recent computer history, users have moved from floppy disks to hard
disks and now to caching systems and RAM disks in a never ending
skirmish to find the fastest, most reliable means of data
processing.


Caching Systems
---------------
A Disk Cache is a temporary
RAM buffer that reads and Cache Reading Process
stores data from the hard disk. ----------------------------
When a user first reads Information is initially
information from a hard disk, read from the hard disk
it's fed into the Disk Cache. at a normal hard disk
Whenever that same speed.
information is needed, it comes Information is placed in
from the Disk Cache and not the RAM Cache.
from the hard disk. As a result, Whenever this information
the computer can access is accessed again, it is
information at a speed of 100 read from the cache at
microseconds (millionths of a normal RAM speed.
second) rather than 30
milliseconds (thousandths of a second).

While most caching systems enhance information retrieval, some
greatly improve information saving. Data is first written at very
high speeds into RAM and the application program used is freed to
the user. The data is then written from the RAM cache to the slower
disk when it would otherwise sit idle. Any information in the Disk
Cache, regardless when it's copied, is identical to information on
the hard disk.

File Servers. Certainly, caching systems do not only benefit
regular personal computers. They provide an enormous
speed-enhancing tool for file servers. Since the primary
objective of any file server, dedicated or undedicated, is
providing files to workstations, caching systems are really the
only way information can be delivered quickly enough to satisfy
user needs. When demanded, files can be taken from memory
instead of the hard disk. Not only does the system seem
unhampered by file trafficking degradation, but ultimately, the
hard disk is saved from tremendous wear and tear.









207




RAM Disks
---------
A RAM Disk is similar to a Disk Cache; however, a RAM Disk acts as a
hard disk that resides in memory. A user reads, writes, and copies
information from the RAM Disk as if he or she was using a regular
hard disk. Of course, when the computer is turned OFF, any
information on the RAM disk is lost unless it was physically copied
to an actual hard disk.


Disk Cache and RAM Disk Comparisons
===================================

Comparison Disk Cache RAM Disk
------------------------------------------------------------------
Hard Disk Storage Information sent to Information sent
hard disk and to mem- to memory only.
ory. Similar retrie- Retrievals come
vals come from RAM. from RAM

Power Down Since information is Upon power down,
saved to both hard RAM disk informa-
drive and memory, tion is lost unless
but remains on the previously saved
hard drive. to a hard disk.

Benefits to PCBoard File server informa- Executables, batch
tion can be placed in files, and the
the cache. Files re- temporary file
main on the hard disk, locations can be
however, and their placed on the RAM
placement in the disk disk. The temp-
cache merely improves orary file loc.
retrieval and saving is specified in
of messages and other File Locations 1
commonly accessed of PCBSetup.
information.

Recommended Memory 1 Megabyte (As large As much as
as possible). necessary to hold
the allotted
files.

















208




ESC Codes in Messages
=====================

General Information
-------------------
In most systems, special characters exist that cause a particular
function to be implemented. One of these special characters is
ASCII 27 (^[) which informs a system that an ESC code immediately
follows. ESC codes are used by mostly users to add color, flashing
text, or other characteristics to messages and other screen
displays. Unfortunately, however, cursor movements can be
implemented by ESC codes. As a result, whenever an ESC code is used
in a message (full-screen-editor or line-by-line), PCBoard
immediately interprets that ESC code and modifies message display
accordingly. The user never actually sees the ESC code, therefore,
and consequently the code cannot be modified. Thus, a remedy is
necessary.


Suitable Remedies
-----------------
The ESC Code sequence must be entered without PCBoard immediately
acting upon it. Two options exist:

Upload Mode. At the Use Full Screen Editor or Edit
Message prompt, a U can be entered to indicate upload
message mode. In this manner, PCBoard does not
interpret ESC codes until the message is saved.

ASCII 29.
PCBoard Examples
interprets ASCII
29 (^]) as it would Description ASCII 29
ASCII 27 (^[). As
a result, ESC Blue [34m
code sequences
can be written to Clear Screen [2J
the screen and
PCBoard will not Bold On [1m
act upon them
until the message is read by its intended recipient.
An ASCII 29 character (^]) is displayed by depressing
the ALT key and typing 29 on the 10 digit key pad. Do
not use the number keys at the top of the keyboard. The
ASCII 29 character is converted to an ASCII 27 character
when the message is saved.

PCBSetup. To allow ESC Codes in messages and other screen displays,
the SysOp must set the Allow ESC Codes parameter to YES. This
parameter is located in the Options 1 screen of PCBSetup.









209




Event Activities
================

General Information
-------------------
An event is merely a time at which PCBoard is unloaded, a
preprogrammed routine runs, and control is returned to PCBoard.
Events can conduct message or user base packs, transfer mail to
other systems, update DOOR applications, or delete the Caller's Log.


PCBSetup
--------
Event activity is controlled by the Node/Event/Subscription option
of PCBSetup. Although parameters for an event's execution times are
controlled by information in the Event screen, the EVENT.SYS file is
executed to perform the actual procedures.

EVENT.SYS. The
EVENT.SYS file @echo off
contains commands echo BACKUP HARDDISK
to implement packing, cd \tape
deleting, or other fbackup < buall.dat
procedures. To the cd \pcb
right is a sample
EVENT.SYS file. In an echo PACK MESSAGE BASES
event program, a pcbpack /area:0-5;7-9;11-13 /days:45
SysOp can use /fast
command line pcbpack /area:6 /days:180 /fast
parameters for each
of PCBoard's utilities. echo PACK USERS FILE
These command line pcbsm /pack;remove;days:30;keep:10
parameters are echo SORT USERS FILE
discussed at length pcbsm /sort;security;prireverse

Multiple Nodes. echo DELETING CALLER LOGS
Depending on del D:\main\call*.*
activities in the
EVENT.SYS file, a echo ALL DONE!
SysOp may have to c:
stop alternate nodes cd \pcb
from running while the board
event is in progress.

Node Activity Suspension. A SysOp can
discontinue node activity by providing a waitbu 45
dummy event for each node. When the board
user base is packed, for example,
PCBoard must be disabled on each node for the event to process. To
the right is a sample dummy event.









210




File Naming Conventions
=======================

General
-------
Although PCBSetup allows definition of SysOp and User menus, a SysOp
may create menus for each level of security, graphics, and
multilingual users. As a result, a user with paltry security might
see a different menu than a user with average or high security; a
user with graphics abilities might request a graphics menu; or a
multilingual user might see a menu in his or her native tongue.
Files that may be changed are BRDM, BRDS, DOORS, and NEWS, all of
which are contained under the Main Board Configuration and
Conference Configuration options of PCBSetup. Below are several
parameters that illustrate menu creation based on security level,
graphics, and multilingual abilities.


Security Specific Menus
-----------------------
A SysOp may create a menu for different levels of security. When
doing so, the following always applies: Attach the security level
to the name of the file. PCBoard scans for a user, doors, or news
file that has the user's security level attached to it. If found,
PCBoard automatically uses the file; otherwise, it defaults to the
file without the security level appendage.


Examples

Filename Description

BRDM45 A menu for users with a 45 security level.

DOORS85 A DOORS menu for users with an 85 security
level.

NEWS95 A NEWS file for users with a 95 security
level.



Graphic Menus
-------------
A SysOp may create a graphic menu used by callers with graphics
abilities. When doing so, the following always applies: Attach a G
to the name of the file. PCBoard first determines if a user has
requested graphics capabilities. If so, it scans for a file that
has a G appendage i.e. BRDMG, DOORSG, NEWSG. If found, PCBoard uses
the file; otherwise, it defaults to the file without the G appendage
(the regular text file). Security specific, graphic menus should be
constructed in this format: [Filename]##G.







211





Examples

Filename Description

BRDM45G A graphic menu for users with a 45 security
level.

DOORS85G A graphic DOORS menu for users with an 85
security level.

NEWS95G A graphic NEWS file for users with a 95 security
level.



Multilingual Files
------------------
A SysOp may create a menu for different languages. After using
MKTXT145, a PCBTEXT file is created that reflects the new language.
The SysOp attaches an extension to the file i.e. PCBTEXT.SPA,
PCBTEXT.FRE. This same extension can be attached to menu files to
reflect the language. The following format is used:
[Filename]XXG.EXT. If the Options 1 parameter in PCBSetup for
multilingual capabilities is set to (N), PCBoard ignores
multilingual menus.


Examples

Filename Description

BRDM45G.FRE A French graphics menu for users with a 45
security level.

DOORS85G.SPA A Spanish graphics DOORS menu for users with
an 85 security level.

NEWS95G.GRE A Greek graphic NEWS file for users with a 95
security level.



Login Security Files
--------------------
Files can be created that are displayed when a user logs into the
system. The files are security specific and are displayed to a user
with a corresponding security level. Each file is simply named a
numerical value i.e. 10, 20, 85, etc. and placed in a special
directory defined in PCBSetup.









212




PCBSetup. On the File Locations 1 screen, there is a parameter that
shows the location of Login Security Files. The parameter is
located second from the top and requires only a directory name.
Inside this directory, the SysOp places the Login Security Files.
If a security file does not exist for a user who logs into the
system, no file is displayed and PCBoard execution continues as
normal. Like security specific menus, Login Security Files can be
graphic and multilingual in nature. The format for such files
follows.


Login Security File Format

Format Description

A normal text file displayed at logon to any user
## with the indicated security level.

Example: 40
Explanation: The text file called 40 is displayed
to any user with a security level of 40 when he or
she logs into the system.

A graphic file displayed at logon to any user with

##G the indicated security level.

Example: 40G
Explanation: The graphic file called 40 is
displayed to any user with a security level of 40
when he or she logs into the system.

A multilingual text file displayed at logon to any
##.[EXT] user with the indicated security level. The file
chosen for display depends on the language
previously picked, the PCBTEXT file created by
MKTXT145, and the multilingual parameter set in
Options 1 of PCBSetup.

Example: 55.FRE
Explanation: PCBoard displays this file to any
user with a security level of 55 who has chosen
French as his or her desired language.

A multilingual graphics file displayed at logon to
##G.[EXT] any user with the indicated security level. The
file chosen for display depends on the language
previously picked.

Example: 85G.SPA
Explanation: PCBoard displays this file to any
user with a security level of 85 who has chosen
Spanish as his or her desired language.







213




Help Files
----------
Although PCBoard provides on-line support for commands, setup files
and locations, and other features, a SysOp may want to create
additional HELP files. Each HELP file is merely a text file stored
in the HELP sub-directory. Below are procedures for the creation of
and access to HELP files.

The SysOp creates a file using any regular text editor. Once
complete, the file must be saved without an extension and
preferably with a name that reflects the file contents.

After saved, the file must be placed in the HELP subdirectory
where other HELP files are stored.

Since users are unaware of the file's existence, the SysOp
should indicate to his or her users that such a HELP file
exists. Normally, this can be accomplished by modifying the
NEWS file or creating a bulletin that lists HELP files for
extended support.

A user can access the new HELP by executing the HELP command
at the PCBoard command line. The format for use is: H
[filename].


Examples

Command Description

H QMAIL A file called QMAIL has been created to provide
further help with a QMAIL DOOR. The file is
placed in the HELP subdirectory.

HELP A file called DATABASE has been created to provide
DATABASE further help with this DOOR for, apparently, a
database program. The file is placed in the HELP
subdirectory.

A file called NEWUSER has been created to provide
H NEWUSER further help with, perhaps, initial registration
and other new user capabilities. The file is
placed in the HELP subdirectory.
















214




Multitasking Operations
=======================


What is Multitasking Software?
------------------------------
Multitasking software like DESQview, OmniView, or DoubleDOS permits
a user to partition his or her system into two or more working
environments. The user may run a spreadsheet in one and a different
application in another. Because of this partitioning opportunity, a
SysOp may execute PCBoard in one environment, use a database in
another, calculate spreadsheet figures in a third, write a letter in
a fourth, and utilize several other environments given sufficient
memory.


PCBoard and Multitasking
------------------------
Multitasking allows a SysOp to run PCBoard in two or more
environments. Notwithstanding memory limitations, two or more data
lines can be physically connected to one computer. However, there
are restrictions. Each communication port requires a unique
interrupt and base. If either is missing, an additional line cannot
be attached and the system must be networked.

Communication Port. The COM port sends or receives data.
Standardized COM ports are COM1 and COM2 utilizing IRQ4 base
03F8 and IRQ3 base 02F8, respectively. A line is physically
connected to one or both of these ports to facilitate
communication in a network or via MODEM. When a caller
engages the system, the COM port is accessed and information
is relayed through the line.

Interrupt Request Line (IRQ). To allow communication through
a COMM port, the microprocessor must be interrupted and
instructed to send or receive information. Each COM port
therefore has its own IRQ. COM1 utilizes IRQ4 and COM2
utilizes IRQ3. If a COM port is used without a unique IRQ,
communication through PCBoard is impossible. Despite
multitasking software, therefore, one machine is often
restricted to two physical lines of communication.


Multitasking Drawbacks
----------------------
Though multitasking software seems to be a panacea for limited
facilities, drawbacks and sacrifice become more prevalent. Each COM
port can be used by only one program at a time and serial ports are
limited. Furthermore, as IRQ's are added, microprocessor efficiency
and reaction time are reduced. Unless a system utilizes alternate
controls for each IRQ and COM port, several lines on one machine is
not recommended and normally impossible.







215




Comm Port/IRQ Alternatives
--------------------------
Though networking and multitasking are two multiple line
alternatives, slave cards exist to accomplish the same task. A
slave card provides an additional COM port and IRQ. These, however,
are not controlled by the system microprocessor. Instead, the slave
card has its own CPU that controls the added COM port and IRQ. The
addition, therefore, does not suffer from slowed response time due
to excessive microprocessor interrupts. Furthermore, the computer
can support multiple lines.

















































216




Remote Activities
=================

General Information
-------------------
A System Operator can not only utilize PCBoard locally, but by using
a modem, he or she can access the same functions remotely.
Normally, this requires that a SysOp drops to DOS using SysOp
Function 9 and an alternate application like DOORWAY to redirect
screen output to the modem.


REMOTE.SYS
----------

set box=no
doorway com1 /v:d^O /m:600 /g:on /o: /k:v0 /c:dos
set box=
c:
cd \pcb
board


When a SysOp drops to DOS from a remote location, the REMOTE.SYS
file is executed. Below is a further description of each setting.

Set Box = No. Normally, all PCBoard utilities have a box that
surrounds the interior text. Furthermore, at the screen's bottom,
each PCBoard utility lists, among other information, date and time
which are constantly updated. This feature turns the box and the
extraneous information OFF (ON). In local mode, this is hardly
necessary since speed is not noticeably reduced by their existence.
In remote operations, however, both the box and the constantly
updated information are sent via modem causing some lapse in speed.

Doorway. The DOORWAY program is a third party application that
permits remote access to systems. Although a discussion of its
function is not explained here, the /V:D^O needs some clarification.

/V The /V is a video parameter. The information that follows
the parameter determines whether direct screen writes are
used.
😀 When listed after the /V parameter, remote operations are
conducted by direct screen writes instead of BIOS. To use
any PCB utilities, direct screen writes must be enacted.
^O The alternative to direct screen writes is BIOS. This
option allows the remote user to toggle between direct
screen writes and BIOS. This feature is advantageous since
many programs do not require direct screen writes and data
transfer is therefore greatly improved.









217




VROOM Overlay
=============

General Information
-------------------
Most system considerations revolve around Random Access Memory (RAM)
and computer speed. While increased memory use normally reflects
enhanced speed, a computer user must typically sacrifice portions of
one to augment the abilities of the other. Indeed, a SysOp may use
more memory which inevitably boosts system response times, but
leaves little room for other programs. This, of course, is
dependent on memory availability and microprocessor use.

PCBoard ordinarily functions in at least 250 kilobytes of memory and
remains efficient at this level. However, a SysOp may replace the
regular PCBoard with a VROOM Overlay version available from the Salt
Air BBS. The Borland Code provides some advantageous qualities.


VROOM Overlay Characteristics
-----------------------------

VROOM Overlay Characteristics

When loaded, the program utilizes 75 kilobytes less memory than
the normal PCBoard program.

The overlay runs more slowly since it swaps portions of itself
to and from the hard disk when necessary.


OVLSIZE.EXE. The VROOM Overlay permits the SysOp to create a
memory-speed relationship depending on the composition of the
SysOp's computer system. The amount of free memory can be altered
to accommodate larger DIR files. The default overlay size is 4
blocks, but the smallest is 2 blocks. The OVLSIZE.EXE program that
accompanies the VROOM Overlay can set the block size lower (save
memory) or higher (increase speed).

Format: OVLSIZE [Filename] [Size]



















218




The filename represents PCBoard or a PCBoard Utility such as
PCB145.EXE or PCBSM.EXE. The size indicates the amount of the
program that resides in memory. It is determined by the table
listed below:


OVLSIZE.EXE memory Allowances

Size Bytes Size Bytes Size Bytes Size Bytes

1 4K 9 36K 17 68K 25 100K

2 8K 10 40K 18 72K 26 104K

3 12K 11 44K 19 76K 27 108K

4 16K 12 48K 20 80K 28 112K

5 20K 13 52K 21 84K 29 116K

6 24K 14 56K 22 88K 30 120K

7 28K 15 60K 23 92K 31 124K

8 32K 16 64K 24 96K 32 128K



/SWAP
-----
In conjunction with the VROOM Overlay version, as with all versions
of PCBoard, the SysOp may employ the /SWAP environment switch to
utilize Extended Memory, Expanded Memory, or the Hard Disk. To
enable the SWAP function, SET PCB=/SWAP must be placed in the
BOARD.BAT file. See environment switches for more information about
/SWAP.























219




Appendices
==========


I. ESC CODES
--------------
ESC Codes are used inside text files to make their display more
appealing. Some SysOps incorporate ESC codes in their PCBoard files
(WELCOME, NEWUSER, CLOSED, WARNING, EXPIRED, and others) to change
black and white vanilla to color and flash. Some ESC Codes add
color; others make text flash; others highlight; still others
produce sound. Below is a list of common and not so common ESC
codes.


Cursor Positioning
------------------
ESC Code Description of ESC Code
--------------------------------------------------------------------
ESC[#;#H Cursor Position. The cursor is moved to the location
specified by two parameters. The first parameter
specifies the row number. The second parameter
specifies the column number. The default value is 1.
If no values are indicated, the cursor is moved to
the home position.
ESC[#A Cursor Up. The cursor is moved up one or more rows.
The # parameter indicates the number of rows to move
up. If absent, the # parameter defaults to 1. If
the # parameter exceeds the top line, the ESC code is
ignored.
ESC[#B Cursor Down. The cursor is moved down one or more
rows. The # parameter indicates the number of rows
to move down. If absent, the # parameter defaults to
1. If the # parameter exceeds the bottom line, the
ESC code is ignored.
ESC[#C Cursor Right. The cursor is moved to the right one
or more rows. The # parameter indicates the number
of rows to move right. If absent, the # parameter
defaults to 1. If the # parameter exceeds the
rightmost column, the ESC code is ignored.
ESC[#D Cursor Left. The cursor is moved to the left one or
more rows. The # parameter indicates the number of
rows to move left. If absent, the # parameter
defaults to 1. If the # parameter exceeds the
leftmost column, the ESC code is ignored.
ESC[#;#R Cursor Position Report. The cursor position is
reported through the standard input device. The
first parameter specifies the current line. The
second line specifies the current column.
ESC[6n Device Status Report. The console driver outputs a
cursor position report sequence on receipt of device
status report.
ESC[s Save. The current cursor position is saved. This
cursor position can be restored with the restore
cursor position sequence.
ESC[u Restore. The cursor position saved with ESC[s is
restored to the console.


220




Erasing Text
------------

ESC Code ESC Code Description
------------------------------------------------------------
ESC[2J Clear Screen.
ESC[K Clear Line. The line from the current cursor
position to the end of the line is erased.


Screen Attributes
------------------
Each screen attribute below may be invoked with the following ESC
Code:

Format: ESC[#;...;#m

Parameters may be stacked and separated with a semicolon (;).


Color Foreground Background
----- ---------- ----------
Black 30 40
Red 31 41
Green 32 42
Yellow 33 43
Blue 34 44
Magenta 35 45
Cyan 36 46
White 37 47


Special Code Description
------------ -----------
0 All attribute off (normal white on black).
1 bold On (High Intensity).
4 Underscore On.
5 Blink On.
7 Reverse Video On.
8 Canceled On (invisible).



















221




II. SysOp Functions
-------------------
Although the SysOp has at least 14 commands described under SysOp
Commands, he or she may employ the function key and ALT function
capabilities below to enhance system control. To be available,
however, the SysOp must reside at his or her local station. The
SysOp may not access these commands from a remote location.

Function Key Description
------------ -----------
F1 SysOp Privileges. A window appears that asks the
SysOp whether SysOp privileges should be given to the
present caller or not. If Y, the current caller is
given SysOp privileges; otherwise, regular system
activity resumes. When F1 is pressed a second time,
SysOp privileges are automatically taken from the
caller.
F2 Lock Out. A window appears that asks the SysOp
whether the current caller should be disconnected and
locked out of the system or not. If Y, The current
caller is disconnected from the system and his or her
security level is reduced to zero. If N, regular
activity resumes.
F3 Print. The printer is turned ON. All caller's
information printed to the caller's log is also sent
to the local printer. Pressing F3 a second time turns
the printer OFF.
F4 Bell. The system bell is turned ON. When a caller
pages the SysOp a tone sounds for 30 seconds.
Pressing F4 a second time turns the bell OFF. When a
caller pages the SysOp, no tone sounds and the caller
is permitted to enter a comment to the SysOp.
F5 Shell. The current caller is taken to DOS. While in
DOS, DOS SHELL appears before the prompt. To return
to PCBoard from DOS, the caller must type EXIT.
F6 Register. The SysOp can change a caller's security
level, expiration date, conference registration, etc.
while the caller is on-line.
F7 Alarm. The system Alarm is turned ON. Pressing F7 a
second time turns the system Alarm OFF. When ON, the
SysOp hears a beep whenever a caller connects, an
error message occurs, or other displays are shown.
F8 Hangup. A window appears that asks the SysOp whether
the caller should be disconnected or not. If Y, the
current caller is immediately disconnected;
otherwise, normal system activity resumes.
F9 Screen. The screen is turned OFF. While OFF,
information normally sent to the screen is sent to a
virtual screen. Pressing F9 a second time restores
the screen and information is displayed as if the
screen had never been turned OFF.
F10 SysOp CHAT. The current caller is forced into CHAT
mode. As a result, the SysOp can CHAT with the
caller on-line.





222




ALT Function Description
------------ -----------
B Sound Bell. When depressed, a bell sounds to g e t
the caller's attention.
D Shell to PCBFiler. The SysOp is taken to PCBFiler.

When the filer session is complete, control is
returned to the Main Board.
F File Out. A message or any screen display can be
captured to a particular file. By pressing ALT F
a second time, the file is closed.
H Toggle Status Lines. When pressed, the status lines
at screen bottom are toggled between Help, Name,
Conference, Comment, and MODEM information.
I File In. A text file can be imported. This is
normally used when text is imported into a message,
but can be used any time to automate key strokes.
M Shell to PCBMONI. The SysOp is taken to PCBMONI.
When the monitoring program is complete, control is
returned to PCBoard.
N Next. When the current caller disconnects, the SysOp
is automatically connected as the next caller.
P Printer. All information from this point of
invocation is sent both to the screen and the
printer. Pressing this function a second time turns
the printer OFF.
S Shell to PCBSysMgr. The SysOp is taken to the system
manager. When the manager is complete, control is
returned to PCBoard.
T Top of Form. A Top-Of-Form is sent to the printer.
X DOS. After a caller logs off the system, the node or
line is dropped to DOS. The node remains in D O S
until the SysOp runs the BOARD.BAT file.

ALT or
CTRL Function Description
------------- -----------
F1 Decrease Caller's Time. When pressed, the SysOp
reduces the caller's time by 5 minutes. If the
caller has less than 5 minutes available, his or her
time is reduced in one minute decrements.
F2 Increase Caller's Time. When pressed, the SysOp
increases the caller's time by 5 minutes.
F9 Decrease Caller's Security Level. The caller's
security level is decreased to the next lower level
defined in the PWRD file. When the security level is
found, PCBoard adjusts the caller's time limit and
byte limit accordingly.
F10 Increase Caller's Security Level. The caller's
security level is increased to the next higher level
defined in the PWRD file. When the security level is
found, PCBoard adjusts the caller's time limit and
byte limit accordingly.







223




III. ASCII Codes
================
A SysOp or user can utilize the codes listed when entering a message
or leaving a comment. To display a character, hold down the ALT key
and type the corresponding number on the number keypad (don't use
the number keys at the keyboard top). Once the number is keyed in,
release the ALT key and the character will be displayed. By using
the @X Color Codes listed in Appendix VIII, a SysOp or user can
place colored pictures in his or her messages.

To use all ASCII codes below, a parameter in the Options 1 screen of
PCBSetup must be modified. The Disable High ASCII Filter parameter
must be set to Y. This filter, however, is used to reduce line
noise that might corrupt a signal. The SysOp should determine which
is preferred: extended ASCII characters in messages or less risk of
greater line noise.

Number Character Number Character Number Character
------ --------- ------ --------- ------ ---------
0 Null 85 U 170
1 ^A 86 V 171
2 224 87 W 172
3 ^C 88 X 173
4 ^D 89 Y 174
5 ^E 90 Z 175
6 ^F 91 [ 176
7 ^G 92 \ 177
8 ^H 93 ] 178
9 ^I 94 ^ 179
10 ^J 95 _ 180
11 ^K 96 ` 181
12 ^L 97 a 182
13 ^M 98 b 183
14 ^N 99 c 184
15 ^O 100 d 185
16 ^P 101 e 186
17 ^Q 102 f 187
18 ^R 103 g 188
19 ^S 104 h 189
20 ^T 105 i 190
21 ^U 106 j 191
22 ^V 107 k 192
23 ^W 108 l 193
24 ^X 109 m 194
25 ^Y 110 n 195
26 ^Z 111 o 196
27 ^[ 112 p 197
28 ^\ 113 q 198
29 ^] 114 r 199
30 ^^ 115 s 200
31 ^_ 116 t 201
32 Space 117 u 202







224




33 ! 118 v 203
34 " 119 w 204
35 # 120 x 205
36 $ 121 y 206
37 % 122 z 207
38 & 123 { 208
39 ' 124 | 209
40 ( 125 } 210
41 ) 126 ~ 211
42 * 127 212
43 + 128 213
44 , 129 214
45 - 130 215
46 . 131 216
47 / 132 217
48 0 133 218
49 1 134 219
50 2 135 220
51 3 136 221
52 4 137 222
53 5 138 223
54 6 139 224
55 7 140 225
56 8 141 226
57 9 142 227
58 : 143 228
59 ; 144 229
60 < 145 230
61 = 146 231
62 > 147 232
63 ? 148 233
64 @ 149 234
65 A 150 235
66 B 151 236
67 C 152 237
68 D 153 238
69 E 154 239
70 F 155 240
71 G 156 241
72 H 157 242
73 I 158 243
74 J 159 244
75 K 160 245
76 L 161 246
77 M 162 247
78 N 163 248
79 O 164 249
80 P 165 250
81 Q 166 251
82 R 167 252
83 S 168 253
84 T 169 254
255 Backspace






225




IV. File Formats
=================


CALLERS Log
-----------
The CALLERS log is a random access text file with a record length of
64 bytes. The following layout is specified in a byte offset
format. As a result, the first field begins at offset 0. Those who
use this file format should realize that strings are not NULL
terminated and that the length for the string represents the full
number of useable and storable bytes. All strings are padded with
spaces to fill the entire field.

Offset Type Length Description
------ ---- ------ -----------
0 STR 62 The actual text written to the caller's log.
62 STR 2 Carriage Return/Line Feed Characters.

Though each record is strictly formatted to 64 bytes (hence a random
access file), the file may be displayed on the screen using the DOS
TYPE command. This is possible since each record ends in a carriage
return and line feed.

PCBoard utilizes the random accessibility of the file to display its
contents in reverse order.


Message Base
============
The following information documents the format for PCBoard's message
base and message index formats. All strings in the Message Base
format are not NULL terminated. The length for the string
represents the full number of useable and storable bytes. Below is
a description of variable types used in the table that follows.



Variable Type Definitions
-------------------------
CHAR 1 Byte Character
STR Array of 2 or more CHAR bytes
BSREAL 4 Byte Basic Single Precision Real Number

Message Base Header. The message base consists of 128 byte blocks

of data. A single 128 byte header is placed at the start of each
message base. This block indicates the number of messages in the
message base and the range of message numbers in that message base.











226




Message Base Header
-------------------

Offset Type Length Description
------ ---- ------ -----------
0 BSREAL 4 High Message Number (0 to 16,700,000)
4 BSREAL 4 Low Message Number (0 to 16,700,000)
8 BSREAL 4 Number of Active Messages (0 to 32,767)
12 BSREAL 4 Number of System Callers (Main Message Base
Only)
16 STR 6 The "Locked" field for pre-14.2 systems (See
Note 1)
22 STR 106 Reserved For Future Use.

Individual Message Header. Each message consists of a 128 byte
header describing who the message is to and from. The header also
indicates the number of 128 byte blocks that comprise the entire
message. The message base layout is specified in a byte offset
format. As a result, the first field begins at offset 0.

Individual Message Header
-------------------------

Offset Type Length Description
------ ---- ------ -----------
0 CHAR 1 Message Status Flag (Note 2)
1 BSREAL 4 Message Number (0 to 16,700,000)
5 BSREAL 4 Reference Number (0 to 16,700,000)
9 CHAR 1 Number of 128 Byte Blocks in Message (Note
3)
10 STR 8 Date of Message Entry (Format: MM-DD-YY)
18 STR 5 Time of Message Entry (Format: HH:MM)
23 STR 25 Name of User to whom message is addressed
48 BSREAL 4 Date of Reply Message (Format: YYMMDD)
52 STR 5 Time of Reply Message (Format: HH:MM)
57 CHAR 1 Letter "R" if message has a Reply
58 STR 25 Name of User who wrote Message
83 STR 25 Subject of Message
108 STR 12 Password needed to read Message (if any)
120 CHAR 1 Active Status (225 = Active, 226 = Inactive)
121 CHAR 1 Letter "E" if Message is echoed
122 STR 6 Reserved For Future Use

NOTE 1
------
When the message base is locked for message insertion, PCBoard locks
only the 6 bytes starting at offset 16 (17 through 22). In previous
versions, the first 128 bytes were locked. Since previous lock
bytes include current locked bytes albeit, a fraction of the
previous, complications do not arise, Third Party Authors need not
modify their programs, and message reading commands (READ and Your
Mail) can function while the message base is updated.

Third Party Authors can use previous techniques to update the
message base even though such methods locked the entire 128 byte
header.



227




NOTE 2
------
When a user does a quick message scan, each message number has a
special symbol to its left. The symbol may represent the type of
message sent, any security attached, or the person who read the
message. The status flags are defined below.


Status Flags
------------
Character Description
--------- -----------
[Nothing] A message that can be read by anyone.
* A private message read by someone, but not read by the
official recipient of the message.
+ A private message that has been read by the official
recipient.
- A public message sent to a user who has already read the
message.
~ A COMMENT to the SysOp that has not yet been read by the
SysOp. In this context, the SysOp is indicated by the
user defined in record one of the user file.
` A COMMENT to the SysOp that has been read by the SysOp.
In this context, the SysOp is indicated by the user
defined in record one of the user file.
% An unread message protected by a SENDER PASSWORD.
^ A message protected by a SENDER PASSWORD that has
already been read.
! An unread message protected by a GROUP PASSWORD.
# A message protected by a GROUP PASSWORD that has already
been read.
$ A message addressed to ALL protected by a GROUP
PASSWORD.


























228




NOTE 3
------
The number of message blocks indicated in the message header
includes the header block itself. If a message has a body length of
1 block, the stored number in the header would be 2 (1 - message
header; 1 - body block).

Message Base Index File. The name of the message base index file is
identical to the message base name plus an NDX extension. The file
is preformatted to a size of 4,096 times the number of message index
blocks. Each message index block consists of 1,024 entries. Each
entry is BSREAL in type resulting in 4,096 bytes in each block.

When the Message Index is calculated, the value represents an offset
within the index itself. Once found, the four byte value at this
offset is used to calculate the actual message address. The offset
contained in the index file is 0 if no entry exists for that
message; a negative number if the message has been killed; and a
positive number if the message is active. Below are formulas used
to calculate the message address as well as an example using those
formulas.

Example
-------

Message Number Wanted: 1,500 Low Message Number: 1,024

Msg.Index = [1,500 - 1,024] X 4 Beginning at Message Index 1,904,
read four bytes (1904, 1905,
1906, 1907. Combined, these
BSREAL bytes represent one
number. This number must be
converted to a long integer and
used to find the appropriate
offset in the Message Base.

Msg.Address = [Long Integer Value - 1] X 128

The Message Address is the
location of message 1,500 in the
message base. The Long Integer
Value is a result of a conversion
from the BSREAL value found
above.















229




Reading Message Finding Message
Index Message Address & Reading
--------------- -----------------
LowNum = 1024; if (MsgOffset > 0) {
MsgNum = 1500; lseek(MsgsFile, (MsgOffset-1)
lseek(IndexFile,(MsgNum - * 128, SEEK_SET);
LowNum)*4,SEEK_SET); read(MsgsFile, Header,
read(IndexFile, Offset, sizeof(Header));
sizeof(bsreal)); }


PCBOARD.DAT
===========
The PCBOARD.DAT file contains information about PCBSetup. Each line
is ASCII text followed by a carriage return/line feed. The first
150 lines have existed since PCBoard 14.0. Lines after 150 have
been added for PCBoard 14.5. Each Y/N parameter uses a "-1" for YES
and a "0" for NO. Any program written to modify this file should
first read until an End-of-File (EOF) marker is encountered.

It should then return all unchanged lines to the file. Searching
for an EOF marker insures a program's compatibility with future
PCBOARD.DAT files. Following is a brief description of each line.

Line # Description
------ -----------
1 PCBOARD.DAT version identification
2 Sysop Display Name (if answered NO to "Use RealName")
3 Sysop Password (from call waiting screen)
4 Use Real Name
5 Use Graphics (when logging in as the sysop)
6 Level Needed to Read All Comments
7 Level Needed to Read All Mail Except Comments
8 Sysop Level (for Sysop Menu and F1-Temp-Sysop Upgrade)
9 Level Needed to Copy or Move Messages Between Areas
10 Security Req'd for Sysop Function 1 (view log)
11 Security Req'd for Sysop Function 2 (view users)
12 Security Req'd for Sysop Function 3 (pack msgs)
13 Security Req'd for Sysop Function 4 (recover msgs)
14 Security Req'd for Sysop Function 5 (list msg headers)
15 Security Req'd for Sysop Function 6 (view system file)
16 Security Req'd for Sysop Function 7 (user maintenance)
17 Security Req'd for Sysop Function 8 (pack users file)
18 Security Req'd for Sysop Function 9 (remote dos)
19 Security Req'd for Sysop Function 10 (shell dos function)
20 Security Req'd for Sysop Function 11 (view other nodes)
21 Security Req'd for Sysop Function 12 (logoff alt node)
22 Security Req'd for Sysop Function 13 (view node log)
23 Security Req'd for Sysop Function 14 (drop alt node to DOS)
24 Location of Help Files
25 Location of Security Files
26 Location of Node Chat Files
27 Location of PCBTEXT Files
28 Location of User INDEX Files
29 Name/Location of USERS File
30 Name/Location of CALLERS Log



230




31 Name/Location of CNAMES File
32 Name/Location of PWRD File
33 Name/Location of FSEC File
34 Name/Location of UPSEC File
35 Name/Location of TCAN File
36 Name/Location of WELCOME File
37 Name/Location of NEWUSER File
38 Name/Location of CLOSED File
39 Name/Location of WARNING File
40 Name/Location of EXPIRED File
41 Name/Location of USERNET File
42 Name/Location of Conference Menu
43 Name/Location of NEWASK File
44 Name/Location of NEWREG File
45 Name/Location of PCBPROT.DAT File
46 Name/Location of DOWNLOAD.TXT File
47 Name/Location of LOGOFF Script
48 Name/Location of LOGOFF Answers
49 Name/Location of PCBML.DAT File
50 Name/Location of Group Chat Topic File
51 Seconds to wait for carrier
52 COMx (or NONE)
53 Initial Port Speed
54 Lock Port Speed
55 Modem Initialization String
56 Modem Off-Hook String
57 Disable CTS/RTS Checking
58 Using a Hayes V-Series
59 Using a FASTCOMM
60 Reset Modem During Recycle
61 Modem Offhook During Recycle
62 Using PAD
63 Answer on True Ring Detect
64 Allow 7,E,1 Callers
65 Allow Low Baud Rates
66 Start Time for Low Baud
67 Stop Time for Low Baud
68 Disable Message Scan
69 Disable 3-Minute Screen Clear
70 Disable Registration Edits
71 Disable High-ASCII Filter
72 Disable Quick Logon Feature
73 Disable Password Check (DOS)
74 Multi-Lingual Operation
75 Disable Full Record Updating
76 Run System as a Closed Board
77 Use Non-Graphics Mode Only
78 Exit to DOS After Each Call
79 Include City Field in NODE Display
80 Eliminate Screen Snow in PCB
81 Enable Subscription Mode
82 Allow ESC Codes in Messages
83 Allow Carbon-Copy Messages
84 Validate TO: Name in Messages (except in
85 (no longer used, was: Update Msg Ptr after Read)
86 Enforce Daily Time Limit



231




87 Display NEWS Only if Changed (-1=YES, 0=NO, 1=ALWAYS)
88 Disable CTS-Drop During Write
89 Keyboard Timeout (0=disable)
90 Running a Network / Multitasker System
91 Node Number on the Network
92 Network Timeout on Errors (20-99 secs)
93 Node Chat Frequency (once every 5-99 secs)
94 Board Name
95 Batch file for viewing compressed files
96 Filename EXTENSION for compressed files
97 Function Key SHIFT-F1
98 Function Key SHIFT-F2
99 Function Key SHIFT-F3
100 Function Key SHIFT-F4
101 Function Key SHIFT-F5
102 Function Key SHIFT-F6
103 Function Key SHIFT-F7
104 Function Key SHIFT-F8
105 Function Key SHIFT-F9
106 Function Key SHIFT-F10
107 (not used)
108 Number of Highest Conference Desired
109 Maximum Lines in the Message Editor
110 Default Color ANSI Code
111 Default Color Intensity
112 Is a Timed Event Active
113 Time to Begin Event (military time)
114 Minutes Prior to Suspend All Activity
115 Disallow Uploads Prior to an Event
116 Slide Event Time if a User is Online
117 Upload Buffer Size (4-64)
118 Disable Drive Size Check
119 Parallel Port Num (1-3,0=None)
120 Stop Upload's when Free Space is less than ### K-bytes
121 Security Level for A) Abandon Conference
122 Security Level for B) Bulletin Listings
123 Security Level for C) Comment to Sysop
124 Security Level for D) Download a File
125 Security Level for E) Enter a Message
126 Security Level for F) File Directory
127 (no longer used - was security for GOODBYE command)
128 Security Level for H) Help Functions
129 Security Level for I) Initial Welcome
130 Security Level for J) Join a Conference
131 Security Level for K) Kill a Message
132 Security Level for L) Locate File Name
133 Security Level for M) Mode (graphics)
134 Security Level for N) New Files Scan
135 Security Level for O) Operator Page
136 Security Level for P) Page Length
137 Security Level for Q) Quick Message Scan
138 Security Level for R) Read Messages
139 Security Level for S) Script Questionnaire
140 Security Level for T) Transfer Protocol
141 Security Level for U) Upload a File
142 Security Level for V) View Settings



232




143 Security Level for W) Write User Info.
144 Security Level for X) Expert Mode Toggle
145 Security Level for Y) Your Personal Mail
146 Security Level for Z) Zippy DIR Scan
147 Security Level for OPEN a DOOR
148 Security Level for CHAT Between NODEs
149 Level Given to Users Who Agree to Register
150 Level Given to Users Who Refuse to Register
151 Security Level needed for USERS command
152 Security Level needed for WHO command
153 Security Level needed for BATCH file transfers
154 Name of color definition file (usually PCBFILER.DEF)
155 Lowest allowed baud rate for callers (was/BAUD:xxxx)
156 Modem delay during recycle (was /DELAY:xx)
157 Number of Rings before answering the phone
158 IRQ number of comm port if not COM1 or COM2
159 BASE address of comm port if not COM1 or COM2
160 Leave DTR up at DOS drop; some MODEMs hangup if DTR down
161 Maximum lines in scrollback buffer (was /MAX:xxx)
162 Pre-load PCBTEXT file for faster access (uses more
163 Pre-load CNAMES file for faster access (uses more memory)
164 Security Level required for a caller to use @-variables
165 Include "Uploaded By" line in uploaded file descriptions
166 Show user settings during login (was /INFO)
167 Allow local F5 shells to DOS
168 Use Slave Card updating (v14.2 did, v14.5 is faster
169 Default subscription length for new users
170 Maximum messages in a capture file
171 Maximum messages per conference in a capture file
172 Minutes prior to an event to stop uploads
173 Security Level needed to EDIT any message
174 Security Level needed to EDIT your own message
175 Share IRQ's on micro channel buses (for comm ports)
176 Default to scan ALL conferences at login
177 Level Needed to Use the 'Read Only' Command
178 Use NEWASK questionnaire plus standard new user questions
179 Location for temporary files
180 Name and location of USERS.INF file
181 Default to 'Quick Scan' method on personal message scan
182 Number of DAYS for warning prior to subscription
183 Allow ONE-name users to log onto the system
184 Default 'Expired' Security Level
185 Security Level to use the TEST command
186 Name of the message CAPTURE file (or blank=caller
187 Perform file verification on uploads
188 Stop the clock during Message Capture download
189 Start time for sysop pages
190 Stop time for sysop pages
191 Write Caller Number to callers log
192 Write Connect String to callers log
193 Write Caller's Security Level to callers log
194 Read PWRD file upon joining a conference
195 Confirm caller name at logon time
196 Allow password failure comment
197 Warning before logoff
198 Maximum number of lines in upload description



233




PCBOARD.SYS
===========
The PCBOARD.SYS file holds information about the Call Waiting
Screen, the current user, and system allotments for that user. The
following file reflects standard information from previous versions
of PCBoard as well as new information from PCBoard 14.5. The file
may be written in one of two modes depending on the need of the
programmer.

The file may be 128 bytes in length to insure compatibility
with previous versions of PCBoard.

The file may exceed the 128 byte length of previous versions
and include information specific to PCBoard 14.5.

When this file is manipulated, the first 128 bytes should be filled
with spaces to prevent arbitrary characters in unused fields.
Typically, only the first four fields of the 128 byte block are
valid when no caller is on-line. Fields outside this 128 byte block
may contain valid data or they may be truncated to 128 bytes without
serious loss.

DOOR Authors. If a caller hangs up while inside the DOOR, the
PCBOARD.SYS file should be cleared. To clear the file, fill it from
offset 9 up to and including offset 127 with spaces leaving the
first 8 bytes and the remainder of PCBOARD.SYS untouched. This
allows PCBoard to recycle normally.

The following layout is specified in a "byte offset" with the first
field beginning at offset 0. Some fields below may have a note
attached to them. The notes follow the table.

Variable Type Definitions
-------------------------
CHAR 1 Byte Character
STR Array of 2 or more "CHAR" bytes
INT 2 Byte Integer
LONG 4 Byte Long Integer
BSREAL 4 Byte Basic Single Precision Real Number
BITMAP Array of Bytes accessed one bit at a time


Offset Type Length Description
------ ---- ------ -----------
0 STR 2 Display On/Off ("-1" = On, " 0"= Off)
2 STR 2 Printer On/Off ("-1" = On, " 0" = Off)
4 STR 2 Page Bell On/Off ("-1" = On, " 0" = Off)
6 STR 2 Caller Alarm On/Off ("-1" = On, " 0" = Off)
8 CHAR 1 Sysop Flag (" ", "N"=sysop next, "X"=exit
dos)
9 STR 2 Error Corrected ("-1" = On, " 0"= Off)
11 CHAR 1 Graphics Mode ('Y'=yes, 'N'=no, '7'=7E1)
12 CHAR 1 Node Chat Status ('A'=available,
'U'=unavailable)





234




13 STR 5 DTE Port Speed (PC to Modem speed)
18 STR 5 Connect Speed shown to caller or "Local"
23 INT 2 User's Record Number in the USERS file
25 STR 15 User's First Name (padded to 15 characters)
40 STR 12 User's Password (padded to 12 characters)
52 INT 2 Time User Logged On (in minutes since
midnight)
54 INT 2 Time used so far today (negative number of
minutes)
56 STR 5 Time User Logged On (in "HH:MM" format)
61 INT 2 Time Allowed On (from PWRD file) (see note 1
below)
63 INT 2 Allowed K-Bytes for Download (see note 2
below)
65 CHAR 1 Conference Area user was in (if <= 255)
66 BITMAP 5 Conference Areas the user has joined this
session
71 BITMAP 5 Conference Areas the user has scanned this
session
76 INT 2 Conference Add Time in minutes
78 INT 2 Upload/Sysop CHAT Credit Minutes
80 STR 4 Language Extension (see note 4 below)
84 STR 25 User's Full Name (padded to 25 characters)
109 INT 2 Calculated Minutes Remaining (see note 5
below)
111 CHAR 1 Node Number (or ' ' if no network)
112 STR 5 Scheduled Event Time (in "HH:MM" format)
117 STR 2 Is Event Active ("-1" = On, " 0" = Off)
119 STR 2 Slide Event ("-1" = On, " 0" =Off)
121 BSREAL 4 Memorized Message Number
125 CHAR 1 Comm Port Number (0=none, 1-8)
126 CHAR 1 Reserved for PCBoard
127 CHAR 1 Reserved for PCBoard
128 CHAR 1 Use ANSI (1 = Yes, 0 = No)
129 CHAR 8 Last Event Date (in "MM-DD-YY" format)
137 INT 2 Last Event Minute (in minutes since
midnight)
139 CHAR 1 Caller Exited to DOS (1 = Yes, 0 = No)
140 CHAR 1 Event Up Coming (1 = Yes, 0 = No)
141 CHAR 1 Stop Uploads (1 = Yes, 0 = No)
142 INT 2 Conference Area user was in (up to 65535)
144 BITMAP VARIES High Conference Areas the user has joined
(note 6)
VARIES BITMAP VARIES High Conference Areas the user has scanned

Note 1
------
The Time Allowed On field is not the calculated allowed time
remaining. The user's record in the USERS file is not updated with
the Last Date On or Elapsed Time On information until PCBoard exits
to DOS or runs a DOOR program. DOOR programs, therefore, should not
update the USERS file in their application if the caller is
returning to PCBoard. Only if the caller hangs up inside the DOOR
and the DOOR modifies PCBOARD.SYS should the file be changed.





235




Note 2
------
The Allowed K-Bytes for Download field specifies the number of
K-bytes the caller may download in a day according to his or her
security level and connect speed specified in the PWRD file in File
Locations 1 of PCBSetup. This is not the calculated number of
K-bytes remaining. To calculate a caller's downloadable bytes
remaining, multiply the Allowed Kilobytes for Download by 1,024 and
subtract the number of bytes the caller has downloaded for the day.
Unlike the Elapsed Time On field, the Number of Bytes Downloaded
field is updated before PCBoard exits to DOS or to a DOOR program.

If the Number of Kilobytes Remaining is set to 32,767 then PCBoard
considers this to be an unlimited number. As a result, any bytes
downloaded do not count against the caller's limit (See Editing File
Locations 1 & 2 Files).

Note 3
------
The Upload/Sysop CHAT Credit Minutes indicates the number of minutes
that should be subtracted from the current time elapsed for the
caller. This extends the caller's Remaining Number of Minutes
On-Line for the session. Before returning to PCBoard, a DOOR
program may adjust this field if time credit was added or removed
from a user's on-line status.

Note 4
------
The Language Extension is added to filenames that PCBoard displays
when the caller has chosen a language other than the default. The
default is all spaces (i.e. " "). However, a language such as
French might have an FRE extension.

Note 5
------
This field is provided only as a convenience to the DOOR programmer.
It specifies the number of minutes a user has remaining when he or
she opens a DOOR or exits to DOS. PCBoard does not accept this
value, however, when a user returns from a DOOR program.

Note 6
------
The final two conference fields are bit mapped just like the two
fields at offsets 66 and 71 respectively. However, these final
fields apply only to conferences beyond 39. Furthermore, they are
dynamically sized at the byte level. Examples follow.

The formula for dynamic size follows. Any dynamic size that is
greater than zero, but less than one is rounded to the nearest byte.










236




High Conference Extended Dynamic
Number Conferences Size
--------------- ----------- -------
<39 0 0
40 1 1
50 11 2
100 61 8


Size = [High Conference Number]-39
---------------------------
8


USERNET.DAT
===========
The following information documents the format for PCBoard's
USERNET.DAT and Node CHAT files. All strings in the Message Base
format are not NULL terminated. The length for the string
represents the full number of useable and storable bytes. Below is
a description of variable types used in the table that follows.

USERNET.DAT
-----------

Offset Type Length Description
------ ---- ------ -----------
0 STR 2 A Node Number (Node-to-Node CHAT) or a
letter indicating node status.
2 STR 2 Node Number or spaces if the node is down.
4 STR 25 Name of the caller if signed on.
29 STR 24 City/State Location for that Caller.

The status flags to the right are stored at offset 0 in the
USERNET.DAT record. When mail is sent to an online caller, the
byte at offset 1 can be set to value 255 after the Mail Waiting
flag is set in the USERS file.

Status Letters
--------------

Letter Description
------ -----------
A Available for CHAT
D Out to DOS (in a DOOR)
E Entering a message.
G Group CHAT
L Logoff Pending
O Logging into system
P Paging the SysOp
R CHAT Request Sent
T Transferring a File
U Unavailable for CHAT
X Drop to DOS Pending





237




Link Up Process for Node CHAT.
------------------------------

When Node 1 initiates CHAT with NODE 2, the number 2 is
placed in the status field of Node 1.

Node 2 scans the USERNET.DAT file. Noticing the node number
in the status field, Node 2 changes the field to R
acknowledging the CHAT Request.

Node 2 returns the status field of Node 1 to the number 2.
At the same time, the number 1 is placed in the status field
of Node 2.


Diagram of Node CHAT Link Up Process
------------------------------------

Node Status Explanation
---- ------ -----------
1 A Node 1 is available for CHAT
2 A Node 2 is available for CHAT
1 2 Node 1 initiates CHAT with Node 2.
2 A Node 2 is unaware of the request.
1 R Node 2 acknowledges request.
2 A Node 2 maintains its previous status.
1 2 Node 2 accepts the CHAT by placing its node number in
the status field of Node 1.
2 1 Node 2 places the node number of Node 1 in its o w n
status field.

Node CHAT File Format. The Node CHAT files are random access files
with a record length of 78 bytes. The following represents their
format.


Node CHAT File Format
---------------------

Offset Type Length Description
------ ---- ------ -----------
0 STR 18 Both the node number and the name.
18 STR 58 The text being transmitted from the caller.
76 STR 2 Carriage Return/ Line Feed.

Though each record is strictly formatted to 78 bytes (hence a random
access file), the file may be displayed on the screen using the DOS
TYPE command. This is possible since each record ends in a carriage
return and line feed.










238




USERS.INF
=========
The USERS.INF is merely an extension of a normal user record. It
contains several exorbitant conference and third party application
limits that allow for future expansion.

The file contents follow.

A variable number of conferences ranging from 0 to 65495.
The other 40 conferences are stored in the main USERS file.

A variable sized PCBoard record permitting future growth
despite changes in file formats.

A variable number of installable Third Party Applications (0
to 65,535) permitting KEYWORD access. Furthermore, each
Third Party Record may utilize as little or as much space as
it needs.

A Third Party Author may store his or her own program information in
the USERS.INF file. As a result, the author may use PCBoard
utilities to manipulate Third Party information added to user
records.

The USERS.INF file structures and formats are available for download
from the Salt Air BBS.

































239




USERS.SYS
=========
The USERS.SYS file is a one-stop-shopping-spot for a Third Party
Author. The file contains nearly every tidbit of information about
a current caller that a SysOp may need. The DOOR or Utility author
can update the USERS.SYS without endangering any PCBoard functions.
Any changes made to the user record, whether PCBoard's or the TPA's,
are automatically posted to the appropriate files when PCBoard
reloads. Following is a general description of the file's contents.

A header record describing what is contained in the file.
A user record of fixed size with PCBoard data fields.
Last message Read pointers for conferences.
Bit map fields for conferences (registered, expired, scanned,
etc.).
Fixed record for Third Party Applications.
Conference records for Third Party Applications.

Since the information in the USERS.SYS file is derived from a
combination of the USERS and USERS.INF files, it contains the same
flexibility for growth.

The USERS.SYS file structures and formats are available for download
from the Salt Air BBS.



































240




V. Transfer Protocols
=======================
A MODEM uses a
particular protocol to PCBoard Setup Utility
transfer a file from Edit Protocol File
one computer to
another. The Port Lock
protocols are stored Use Type Size MNP Open Lines Desc.
in the PCBPROT.DAT --- ---- ---- --- ---- ----- ----
file found in A I 128 N N N ASCII
PCBSetup under File X I 128 N N N XModem-Chsm
Locations 2. C I 128 N N N XModem-CRC
PCBoard provides O I 1024 N N N 1K-XModem
several internal F I 1024 Y N N 1K-XModem/G
protocols whose letter Y I 1024 N N N Ymodem
under the USE G I 1024 Y N N Ymodem/G
heading cannot be Z D 1024 N N Y Zmodem
changed. However, a N I 0 N N N None
user may define his or
her own protocol
such as ZMODEM.
This is called an external protocol. Below is a description of
PCBoard's seven protocols as well as ZMODEM.


Internal Protocols
==================
ASCII
-----
This is an abbreviation for American Standard Code for Information
Interchange. Although not truly a transfer protocol, it represents
the format of information conveyed from one MODEM to another. No
error correction is available.


XMODEM-Checksum
---------------
Information is transferred in 128 byte packets. The bytes are
summed (128 bytes) in each packet. After the packet is sent via
MODEM, it is rechecked by the receiver to insure an identical byte
summation exists in the packet. This, of course, provides a
somewhat primitive error check since identical bytes does not
necessarily indicate identical characters. For instance, no error
is indicated for the following transfer: SAMPLE ------> SMAPLE.


XMODEM-CRC
----------
Information is transferred in 128 byte packets. The protocol uses
the following polynomial formula: x16 + x12 + x5 + 1 to calculate
a Cyclical Redundancy Check (CRC) for the packet. As a result,
error correction is far more reliable. After the packet is sent via
MODEM, bytes are checked by the receiver against their original CRC
value. Although not infallible, this protocol leaves less room for
error.




241




1K-XMODEM
---------
Information is transferred in 1,024 byte packets. This protocol is
identical to the XMODEM-CRC with the exception of the size of the
packet that is transferred at one time. However, the protocol
continues to transfer data in 1,024 byte blocks until fewer than
1,024 bytes remain. At this time, the transfer is reduced to 128
byte packets. For instance, if a file were 2,304 bytes long, it
would be conveyed in 2, 1K byte packets; and 2, 128 byte packets.


1K-XMODEM/G
-----------
Information is transferred in 1,024 byte packets. The protocol,
however, does not correct errors. If an error occurs, the transfer
is aborted. Like a regular 1K-XMODEM, though, the protocol
continues to transfer data in 1,024 byte blocks until fewer than
1,024 bytes remain. At this time, the transfer is reduced to 128
byte packets. This protocol is used only when modems have
established an error corrected session using MNP or V.42.


YMODEM
------
This is a file transfer protocol that permits several files to be
sent at one time (batches). Data is sent in 1,024 byte packets.
Each packet is checked for accuracy using the Cyclical Redundancy
Check (CRC) method. Before sending files, however, the protocol
sends a 128 byte packet that represents a header. In the header are
listed several transfer specifications to distinguish each file in
the batch. The header contains the filename, the number of bytes in
the file, CRC bytes used, and other pertinent information.


YMODEM/G
--------
This protocol permits several files to be sent at one time
(batches). Data is sent in 1,024 byte packets, but no error
correcting occurs. If an error arises, the transfer is aborted.
Like the YMODEM protocol, YMODEM/G sends a 128 byte packet that
represents a header. This protocol is used only when modems have
established an error corrected session using MNP or V.42.

















242




External Protocols
==================
External protocols represent separate files that send and receive
information. These are in contrast to internal protocols that are
specifically programmed in PCBoard. Like internal protocols, most
external conventions can send and receive one or several files.
However, for an external protocol, a SysOp must create the files
that send and receive information. A SysOp should be aware of
procedures that indicate an aborted transfer. Those methods follow.


Transfer Abortion Indicators
----------------------------

Indicator Description
--------- -----------
PCBERR.FIL When PCBoard is implemented, a file called PCBERR.OLD
exists. Whenever a transfer aborts, a SysOp's
external protocol batch file should rename the
PCBERR.OLD as PCBERR.FIL. This file indicates that
an error has occurred.
DSZLOG Whenever an error occurs, a message is relayed to the
DSZLOG that indicates a successful or failed file
transfer. In the SysOp's external protocol batch
file, the SysOp may scan for the successful or failed
message. As a result, the PCBERR.FIL check is
unnecessary.


When a caller requests
an external protocol, External Protocol Parameters
PCBoard passes several
parameters to the Parameter Description
protocol batch file.
These parameters are %1 COM Port Number.
listed to the right.
%2 PC to Modem Speed (DTE rate)

%3 Filename to transfer.

%4 Connect Speed shown by PCBoard

%5 Carrier Speed.
















243




ZMODEM
------
This external protocol allows several files to be sent at one time.
Data is sent in 1,024 byte packets. Each packet is checked for
accuracy using the CRC method. If the transfer is aborted, the user
may resume his or her transfer from where it ended. To implement
this protocol, two files must be created: a receive file and a send
file. These files must be named according to the USE field listed
in the PCBPROT.DAT file. The receive file is PCBR + [USE
Letter].BAT i.e. PCBRZ.BAT. The send file is an PCBS + [USE
Letter].BAT i.e. PCBSZ.BAT.

Port Lock Protocol
Use Type Size MNP Open Lines Description
--- ---- ---- --- ---- ----- -----------
Z D 1024 N N N ZMODEM


PCBRZ.BAT. This file
receives information echo off
for the ZMODEM set dszlog=node1
protocol. The file if exist pcberr.fil del pcberr.fil
should be located in if exist pcbdsz.log del pcbdsz.log
the communication dsz.com handshake both pB4096 z pr1
directory along with rz -p %3
the DSZ.COM file.
Normally, ZMODEM uses a DSZ program to receive and send data. As a
result, the program above can be implemented. After a file transfer
is complete, the SysOp can review the NODE1 file that holds the
DSZLOG. For information on the DSZ command, consult your manual.


PCBSZ.BAT. This file
sends information for echo off
the ZMODEM protocol. SET DSZLOG=NODE1
The file should be if exist pcberr.fil del pcberr.fil
located in if exist pcbdsz.log del pcbdsz.log
the communication dsz.com handshake both pB4096 z sz %3
directory along with
the DSZ.COM file.
The program above can be used for sending information via ZMODEM.
After a file transfer is complete, the SysOp can review the NODE1
file that holds the DSZLOG.
















244




Kermit
======
Kermit is a licensed telecommunications program popular among
bulletin board users. The program functions similar to most
transfer conventions and therefore can be included in the
PCBPROT.DAT file as an external protocol. The following settings in
the PCBPROT.DAT file are customary:

Port Lock Protocol
Use Type Size MNP Open Lines Description
--- ---- ---- --- ---- ----- -----------
K S 1024 N N N Kermit

Because of these settings, two files must be created for Kermit's
external protocol: PCBRK.BAT and PCBSK.BAT.


PCBRK.BAT. This
file receives echo Function keys disabled w/ Kermit!
information when if exist pcberr.fil del pcberr.fil
using the Kermit kermit.exe receive %3, quit
Protocol. These files if errorlevel 1 goto bad
should be located in goto end
the Kermit directory :bad
unless otherwise copy pcberr.old pcberr.fil
accessed. To the :end
right is the receiving
batch file for Kermit.
This is a generic version that should work on most systems. For
further formation on Kermit, consult your manual.


PCBSK.BAT. This
file sends information echo Function Keys Disabled w/ Kermit!
when using the Kermit if exist pcberr.fil del pcberr.fil
Protocol. These files kermit.exe send %3,quit
should be located in if errorlevel 1 goto bad
the Kermit directory goto end
unless otherwise :bad
accessed. To the copy pcberr.old pcberr.fil
right is the sending :end
batch file for Kermit.
This is a generic
version that should work on most systems. For further information
on Kermit, consult your manual.














245




VI. Packet Switch Network
==========================
Most users associate file transfer and information relay to MODEMs
since these devices are most visible to common users. However,
information that is regularly sent over long distances can utilize a
packet switch network.

In this configuration, several subscribers telephone a central
computer using a modem. Normally this central server accepts
several callers who invariably wish to contact another system. The
server accepts the incoming signals, groups them into a packet, and
relays them to their intended destination.

Once the signal has arrived, a piece of hardware separates the
signal into original subscriber signals and converts each into
RS232. At that time, each subscriber may utilize the long distance
system. Upon utilization, information is regrouped into a signal,
returned to the central server, divided into original subscriber
lines, and conveyed to each subscriber.


RS232
-----
Normally, the MODEM server is connected to the subscriber MODEM via
a 25- Pin RS232C connection. This provides more rapid and
controlled communication compared to customary MODEM settings.
Especially over long distances, this is quite advantageous since
phone bills become too costly. The configuration for an RS232C
connection is therefore much different from regular MODEM
connections. Though an installation of a packet switch network will
not be discussed here, a SysOp should be aware of the RS232C 25-Pin
settings. Below is a brief description of each pin.



























246




Description
Pin

NC 1
Transmitted Data 2
Received Data 3
Request to Send 4
Clear to Send 5
Data Set Ready 6
Signal Ground 7
RLSig Detector 8
+Trans Cur Data 9
NC 10
-Trans Cur Data 11
NC 12 Asynchronous
External NC 13 Communications
Device NC 14 Adapter
NC 15 (RS232C)
NC 16
NC 17
+Rec Cur Data 18
NC 19
Data Term Ready 20
NC 21
Ring Indicator 22
NC 23
NC 24
-Rec Cur Return 25



Null Modem Cable
----------------
A SysOp can physically link computers in a local environment using a
Null Modem Cable that is merely an RS232 cable. However, the SysOp
must reverse a few connections between computers to facilitate
proper transmitter- receiver operations. The following table
represents differing pin configurations for two computers connected
locally with an RS232 cable. All other pin connections are
identical to the above RS232 cable.

Null Modem Pin Connections
--------------------------

Computer 1 Computer 2
---------- ----------
2 3
3 2
4 5
5 4
8 20
20 8







247




VII. @ Variables
=================
A SysOp or user may include @ Variables in a message to draw
specific information from the individual. These commands function
as a word processor's macro abilities. With an @ Variable, PCBoard
may perform a function that is otherwise impossible to execute i.e.
@[email protected] Each @ variable must be capitalized and appear in this
format for PCBoard to properly interpret it:

Format: @[email protected]

@[email protected] Description
---------- -----------
## Messages are addressed to users of the security
level specified by ##.
##-## Messages are addressed to users with a security
level between the numbers indicated by ##-##.
AUTOMORE All subsequent MORE? prompts are interpreted as
@[email protected]
BEEP Sends an audible tone (CTRL-G) to the computer
speaker. The tone is only heard if the Bell is
ON.
BOARDNAME Gives the name of the current BBS.
BPS Connect speed of caller.
BYTELIMIT Gives the daily download limit in bytes of the
individual.
BYTERATIO Gives a #:# formatted string for Dn:Up Byte
Ratio.
BYTESLEFT Gives the number of bytes left to download for
the day.
CITY Caller's city.
CLREOL Clears from the cursor to the end of the line.
CLS Clears the screen.
CONFNUM Conference number that the caller currently
occupies.
CURMSGNUM This number reflects the message that the user
is currently reading.
DATAPHONE Gives the business/data phone number.
DAYBYTES Gives the number of bytes that have been
currently downloaded for the day.
DLBYTES Gives the number of bytes that was downloaded.
DLFILES Gives the number of files that was downloaded.
EVENT Gives the time specified for the event.
EXPDATE Gives the expiration date of a particular user.
EXPDAYS Gives the number of days until subscription
expiration.
FILERATIO Gives a #:# formatted string for Dn:Up File
Ratio.
FIRST First name of the user.
HANGUP Disconnects the caller. (Can only be used in a
file, not a message. Must be placed in column
1 of a line.)







248




HIGHMSGNUM High message number of the current conference.
HOMEPHONE Gives the home/voice phone number.
INCONF Currently in conference [conference name].
KBLEFT Gives the number of kilobytes left to download.
KBLIMIT Gives the number of kilobytes that may be
downloaded.
LASTCALLERNODE Name of the last caller on this node.
LASTCALLERSYSTEM Name of the last system caller.
LASTDATEON Last date on.
LASTTIMEON Last time on.
LOWMSGNUM Low message number of the current conference.
MINLEFT Gives the number of minutes left. May be used
for file transfer calculations.
MORE A MORE? prompt is displayed.
MSGLEFT Indicates the number of messages written.
MSGREAD Indicates the number of messages read.
NODE Node number.
NUMBLT Number of bulletins.
NUMCALLS Caller number.
NUMDIR Number of directories.
NUMTIMESON Number of times on.
OFFHOURS Hours during which slow speed modems are
allowed.
OPTEXT Used inside PCBTEXT for current operation text.
PAUSE Displays a MORE? prompt with a 10 second auto
return if the caller doesn't answer if first.
POFF Disables the MORE? prompt.
PON Enables the MORE? prompt.
PRODESC User's default protocol description.
PROLTR User's default protocol letter.
QOFF Disables CTRL-X/CTRL-K checking.
QON Enables CTRL-X/CTRL-K checking.
SECURITY Security level.
SYSDATE Current date.
SYSTIME Current time.
SYSOPIN SysOp IN time as specified in PCBSetup.
SYSOPOUT SysOp OUT time as specified in PCBSetup.
TIMELEFT Time left on the system.
TIMELIMIT Time available on the system.
TIMEUSED Time used by a particular individual.
UPBYTES Gives number of bytes uploaded.
UPFILES Gives number of files uploaded.
USER Yields full name in capital letters.
WAIT Displays a PRESS ENTER TO CONTINUE prompt.
WHO Displays the status of the current node.














249




VIII. @X Color Codes
====================
To modify foreground and background screen colors, @X Color Codes
are used. Like @-Variables, these codes can be used inside PCBoard
to display more ostentatious scripts, messages, news files, welcome
screens, and other modifiable presentations. The color code is
represented by a hexadecimal two digit code. The left digit
represents the background color. The right digit represents the
foreground color. The two digit combination is preceded by @X.

Format: @X##

For example:

@X1F = Bright White on a Blue Background.
@XA6 = Yellow on a Blinking Green Background.
@X4A = Green on a Red Background.
@X8F = Bright White on a Blinking Black Background.


Background (1st Digit) Foreground (2nd Digit)
Color Normal Blinking Normal Intensity
-------------------------------------------------------------------
Black 0 8 0 8
Blue 1 9 1 9
Green 2 A 2 A
Cyan 3 B 3 B
Red 4 C 4 C
Magenta 5 D 5 D
Yellow 6 E 6 E
White 7 F 7 F



Special X Codes Description
--------------- -----------
00 Saves the current color.
FF Recalls a previously saved color.





















250




Glossary
========

@-Variables. A PCBoard feature similar to a word processor's macro
ability. The function has the following format: @[email protected]

ANSI. An acronym for American National Standard Institute, but
refers to graphic commands that provide color and other graphic
characteristics.

Archived. Describes a procedure that combines several files into
one file. This permits ease for downloading and uploading since one
file can be transferred instead of several. The procedure uses the
programs PKARC.EXE and PKXARC.EXE. All archived files have an ARC
extension.

ASCII. An acronym for American Standard Code for Information
Interchange. The code is comprised of 128 standard characters (0 to
127) and 128 symbols (128 to 255).

Asynchronous Communication. A way of transmitting information.
Each data character is preceded by a start bit and followed by a
stop bit to insure each character is recognized by the information
recipient.

Attached SubDirectory. When in the main board or a conference, this
represents the directory that contains the physical files listed in
the Selected DIR Text File.

Batch. More than one file. It's normally associated with a group
of files that are downloaded or uploaded using the appropriate
transfer protocol.

Baud Rate. Indicates the speed at which characters are transmitted
or received through a MODEM.

BBS. An abbreviation for Bulletin Board System.

Bit. The fundamental component that a computer can interpret. A
bit is either 0 or 1 (binary) indicating a status of off or on
respectively.

Bits Per Second (BPS). The speed at which data is transmitted from
a MODEM.

Boolean Operands. A test that a search must successfully meet.
Normally, this is an AND or an OR. In PCBoard, these operands are
denoted with a & and | (vertical bar) respectively and are used in
the TS, Z, USERS, 7 S, and B S commands.

Buffer. An area of memory that stores data until the computer or
MODEM can process it.







251




Byte. Eight bits of data considered a unit by a computer. It
represents the measurement of computer storage and memory
allocation.

Cache. A buffer that holds files in a temporary memory location.
When a file is retrieved from the hard disk, it is copied to the
Cache. Whenever further access to this file is necessary, access to
files as well as processing manipulation are enhanced.

Call Waiting. Refers to the initial screen that allows a SysOp to
log into the system, access a PCBoard utility, or analyze local or
network statistics. The screen further indicates the most recent
caller and the time of his or her logon.

Caller. A person who remotely accesses another BBS and given
certain privileges based on security level.

Caller's Log. Holds a record of each function a caller performs.
Whenever a caller executes a function i.e. logs in, reads a message,
joins a conference etc., the function is recorded in the caller's
log.
Capturing A File. A process that sends information to a text file
on disk while, at the same time, displays the information on the
screen.

CHAT. This is a command in PCBoard that permits callers on
different nodes to communicate with one another. A user can conduct
a one-to-one CHAT session or a group CHAT session.

Com Port. Used to send or receive data. The two most common COM
ports are COM1 and COM2. A line is physically connected to one or
both of these ports to facilitate communication in a network or via
MODEM. When a caller engages the system, the COM port is accessed
and information is relayed through the line.

Compressed File. Any file whose size has been reduced by its format
reorganization. This is usually accomplished by programs such as
PKZIP.EXE or PKXARC.EXE. Normally, a compressed file is given a
special extension i.e. ZIP, ARC.

Conference. A designated area that holds files for viewing or
download and normally has its own message base. Conferences are
often created to segregate users with specific concerns or specific
topics of discussion. They may be public or private depending on
SysOp needs. In each conference, a user is either registered or
unregistered. The former indicates the user may access conference
information while the latter means a user is denied access to
conference data.

Conference SysOp. A user who has a C registration flag. Upon
joining the conference with this flag, the user is given SysOp
privileges. When the user abandons the conference, his or her
security level is returned to normal. CTTY. A DOS command that
changes the standard input and output console to an auxiliary
console. It may restore the keyboard and screen as the standard
input and output device.



252




Cursor. A block or underscore, blinking or solid, that indicates
the position of the next character to type.

Default. A setting chosen when a field is left blank or unchanged.

Delete Flag. A parameter in each user record that determines
whether a user will be deleted from the system on the next USERS
file pack. If the parameter is set to (Y), the user will be
deleted. If set to (N), the user will remain.

DIR. Describes the contents of the hard disk. A DIR file lists the
files available for downloading. It includes the size, file date,
and a description of each entry. However, the DIR file does not
contain the physical files whose names are contained in it.

Directory. A logical grouping of files on a hard disk or other
storage unit. Normally, each directory contains files related to
one another. In a directory, several sub-directories may exist to
categorize files even further. To create a directory in DOS, the
operator can type MD [directory name].

Door. Allows a caller to temporarily exit PCBoard locally or
remotely and run another application program. The alternate program
may be a utility, game, or other program.

Doorway. A program that permits remote access to alternate
applications (See DOOR for further details).

DOS. An acronym for Disk Operating System. PCBoard requires this
system (version 3.1 or above) to function. The system provides
commands for file viewing, manipulation, and general convenience.

Download. The information received from a remote computer via
MODEM. The word can be used as a noun (the data received) or as a
verb (the act of receiving the data).

DSZLOG. A record file created by an external protocol to chronicle
file transfer information, i.e. filenames, characters per second,
through put, success or failure, etc.

EISA Bus. An acronym for Extended Industry Standard Adapter.

ESC Codes. A sequence of characters that can produce screen
characteristics. Some ESC Codes add color; others make text flash;
others highlight; still others produce sound.

Expanded Memory. A board added to a computer to increase its
memory capacity. With additional memory, larger programs can be
used and advanced features become available.

Extended Memory. Memory added to a computer's mother board or add
on memory board. The additional memory ranges from 1,024 kilobytes
and above. With additional memory, larger programs can be used and
advanced features become available.





253




External Protocol. A type of transfer procedure used to upload or
download files. To create an external protocol, the PCBPROT.DAT
file in File Locations 2 of PCBSetup must be modified. A common
external protocol is ZMODEM.

File Server. A commonly accessible location for files. It may be a
separate node or a node dedicated solely to file trafficking. As
more and more files are accessed from the file server, file
trafficking increases and system speed decreases.

Function Keys. Refers to the 10 (sometimes 12) keys located at the
top or far left of most keyboards.

Hard Disk. A bulk storage system of magnetic strips. The capacity
often ranges from 20 MegaBytes to 1,000 MegaBytes for regular
personal computers. Larger systems can exceed this range and often
do.

Indexing. A method of data manipulation and sorting. It assigns a
number to a record and sorts the numbers, not the records
themselves.

Internal Protocol. A type of transfer procedure used to upload or
download files. PCBoard's internal protocols can be found in the
PCBPROT.DAT in File Locations 2 of PCBSetup. These represent
transfer procedures that are hard coded into PCBoard.

Interrupt Request Line. Intrudes upon microprocessor activity and
instructs it to send or receive information. Each COMM port has its
own interrupt. COM1 utilizes IRQ4 and COM2 utilizes IRQ3. Each
modem connection requires a unique interrupt and COM port to
function.

ISA Bus. An acronym for Industry Standard Adapter.

LAN. Refers to a LANtastic network package. The network itself is
called a LAN.

Local. A user logs into PCBoard at his own workstation. This is
contrasted with Remote access which allows a caller to use a MODEM
to log into an alternate system.

LOGON. Refers to a procedure that a caller initiates when he or she
uses PCBoard. It normally includes typing the user's first and last
name and a unique password.

LPT1/LPT2. The first/second parallel port on the computer. Either
is normally connected to a line printer or similar device.

Mail. In PCBoard, this includes any messages or files left to a
registered user by another caller. The mail is stored in the user's
"mail box."

Main Board. Acts as a "mother" conference. All users have access
to this area if the board is not closed to outside callers.




254




MCA Bus. An acronym for Micro Channel Adapter Bus. Most computers
have this type of adapter.

Message Base. The location of all messages left by a user to
another (or all) user. The message base includes all message
headers and all respective message bodies.

Message Number. The number given to a note left by a caller. Each
message has its own number. The number is located in the message
header.

Message Header. Includes the sender of the message, recipient,
message number, and the subject. Each message has a message header.


Message Read Pointer. An indicator that points to the first message
following the last message read.

Microprocessor. An integrated circuit that communicates, controls,
and executes machine language instructions.

MKTXT145. A program that permits the SysOp to redefine system text.
The PCBTEXT file is modified allowing the SysOp to create different
language files for distinct users.

MNP. An abbreviation for Microcom Networking Protocol used as an
error correction standard in MODEMs.

MODEM. An acronym for Modulator-Demodulator. The device allows
data to be translated into computer signals that can be sent via
telephone lines to any computer with a MODEM.

Multitasking. Permits a user to partition his or her system into
two or more working environments. The user may run any number of
applications notwithstanding memory limitations.

Network. Describes how a series of computers is interconnected to
communicate. Normally, a network is achieved using special software
like NOVELL or LANtastic.

Node. An individual PCBoard session that runs locally or with an
attached MODEM. In the latter case, each incoming telephone line
represents a separate session. Non-Stop Mode. All information is
displayed without a "More, Enter=yes?" prompt.

Off-Line Directory. A directory containing files that are not
immediately available for download. If disk space becomes scanty,
files can be moved Off-Line to a different drive and directory. The
caller is informed of this relocation when he or she tries to access
a particular file.

Pack. Refers to a procedure that eliminates unneeded and unwanted
information from a file making the file more compact. The USERS
file, for instance, can be packed to eliminate old or expired users.





255




Packet-Switch Network. A data communications service that processes
data in packets. Communication between computers can be achieved by
a nationwide system of local phone numbers allowing access to
on-line services without extensive long-distance charges.

Parallel Transmission. A method of simultaneously transferring
several bits of data over multiple channels.

Parameter. A setting for a particular field. If a field posed the
question, "Using Multitasking Software", the answer to this question
(Y/N) would be the parameter.

Password. Characters that comprise a security clearance for a user.
Each user has a password to log into the system. Further passwords
may be necessary to download, upload, or enter a message.

Path Specification. A location to which the software is directed to
retrieve, send, or locate a particular file, directory, or disk
drive. Normal DOS specifications are in the following format:
[Drive]:[Dir]\[File].[Ext]

PCB145. The PCBoard executable called from within the BOARD.BAT
file. Normally, it should not be called by itself.

PCBCOPY. A command similar to the DOS COPY command. The command,
however, is able to copy a program that is currently in use. It
further provides more control over file copying between network
drives.

PCBDIAG. Diagnostic program that analyzes system paths and
configuration. The analysis is stored in a file called ANALYZE.TXT.

PCBFiler. A utility for PCBoard file maintenance. The program is
comprised of ten options. A SysOp uses this program to manipulate
directories and files, print user and directory information, and
create and sort specific user data.

PCBMODEM. The PCBoard MODEM utility. When called, a list of
commonly used MODEMs is displayed. The user may choose his or her
MODEM from the list and the program will configure and test it.

PCBMoni. This PCBoard program enables a SysOp to monitor system
callers. It can be accessed from the DOS prompt or from within
PCBoard by typing ALT-M.

PCBNum. The PCBNum program resets the number of callers to the
number indicated following the command. This ability permits
control of callers for specific number competitions.

PCBPACK. The PCBoard packing utility. The program is executed from
the DOS prompt and may condense the message base or the user's file.

PCBSetup. The PCBoard setup utility. It consists of 10 screens
that are accessed from PCBSetup's Main Menu to specify SysOp, MODEM,
security level, advanced option, and conference information.




256




PCBSysMgr. The system manager of the PCBoard program. The program
permits user file maintenance, configuration analysis, text and
graphic editors definition. From this program, eight options exist
including access to both PCBSetup and PCBFiler.

Private. Indicates that a particular BBS or conference is
restricted to select users.

Prompt. A computer's expectation for input. The user is then
responsible for inputing whatever information the computer seeks.

Public. Indicates that particular BBS or conference is open to any
user. However, further security might be imposed restricting a
users ability in the BBS or conference.

Purge. Refers to the elimination of information in a file or
directory. When instructed to purge data, PCBoard erases whatever
information satisfies the purge requirements.

RAM Disk. A temporary storage facility that emulates a hard disk.
Files can be copied to it and retrieved. Since the pseudo-disk is
located in memory, access to these files as well as processing
manipulation are enhanced.

RDPCBTXT. Reads a PCBTEXT file and places its contents in a file
called PCBTEXT.LST. In this file, the SysOp will find the record
number, a color code integer, and the text from the record. The
program can read all PCBTEXT files created by previous versions of
PCBoard.

RAM. An acronym for Random Access Memory.

Reference Number. The number of the reply a user has left to a
previous message. The reference number is located in the message
header. If a user has not replied to a message, the reference
number is absent.

Remote. A caller has logged into a system using a MODEM. The
caller uses his own system (monitor and keyboard) to use the remote
PCBoard. He or she may enter messages, CHAT with other nodes, etc.

Script. Allows a SysOp to enlist specific information about his or
her users. Questions are created, the user responds, and answers
are stored in a file.

Search. To seek or scan usually a particular piece of text,
security level, user name, or file. Several PCBoard searching
facilities utilize boolean operands.

Security. Measures taken to allow or prohibit certain users access
to the system. Common security precautions are passwords and
numeric security levels.

Serial Transmission. A method of transmitting data one bit at a
time. As a result, a single can be used to maintain communications.




257




Slave Card. An addition to a computer providing a COM port and
interrupt governed by an independent microprocessor. In this
manner, several lines can be supported on one computer.

Sort. A procedure that orders pieces of information by any number
of methods. Some information is ordered alphabetically; some
numerically; some in reverse alphabetic, etc. The SysOp is given
several opportunities throughout PCBoard utilities to sort
information.

Subscription. Normally indicates a BBS providing support or access
to its system. The SysOp determines the length of the support and
the cost of the subscription period.

Synchronous Communication. A method for sending or receiving data.
Information is transmitted in blocks and synchronization information
is either provided within the blocks for long distance transmission
or provided on a separate data line for local transmission.

SysOp. An abbreviation for System Operator. The System Operator is
responsible for system maintenance, file postings, etc. Recommended
pronunciation: SisOp.

TESTFILE. Used in a batch file to indicate a certain extension.
Once the filename is analyzed, TESTFILE returns an error level that
causes a branch to another part of the batch program.

Third Party Applications. Software written specifically for PCBoard
that can be accessed via PCBoard's DOOR facility. Normal
abbreviation: TPA.

UART. An acronym for Universal Asynchronous Receiver-Transmitter
chip. The 16550 UART chip has a First In, First Out (FIFO) buffer
to sort our bottle neck clogs that result from excessive interrupts
caused by high speed MODEMs. The buffer allows the processor, while
multi-tasking, to keep pace up to 115,200 baud.

Upload. The information sent from the local computer via MODEM to a
remote computer. The word can be used as a noun (the data sent) or
as a verb (the act of sending the data).

User Record. A register of information unique to each user. The
record contains the user's name, password, security level, and other
pertinent information.

User. A person who accesses a local system. However, a person may
access a remote system and still be considered a user as well as a
caller.

User's List. Includes information about each user who is registered
on the system. Contained in the USERS file are the user's name,
city, telephone number, security level, subscription expiration
date, and other information.






258




V.32 MODEM. A type of MODEM that uses different frequencies and
modulation to convey information. It provides simultaneous bi-
directional processing, improved interactive response times, and
compatibility with other brands of V.32 MODEMs.

V.42 MODEM. An error correction standard in MODEMs. Information is
analyzed and sent in packets to another computer. The received
packet is checked to insure an identical transmission.

VIEWZIP. Once a file has been zipped or compressed by the ZIP.EXE
command, its contents may be viewed with this command.

Wildcards. Refers to DOS text substitutions. Specifically, DOS
uses two characters to denote text: * and ?. The first represents
a string of characters of any size. The second represents only one
character. The wildcard *.* indicates any filename with any
extension. The wildcard File?.* encompasses files that begin with
File, have one trailing character in the filename, and use any
extension.

XMODEM (Checksum). A file transfer protocol that conveys
information in 128 byte packets. Bytes are summed before sending a
file and summed upon the file's receipt to insure a successful
transfer (See Appendix V).

XMODEM/G-1K. A file transfer protocol that conveys information in
1,024 byte packets. There is no error detection routines, however.
The next packet is not sent until the former has cleared (See
Appendix V).

XMODEM-1K. A file transfer protocol that conveys information in
1,024 byte packets. Each packet is checked for accuracy. If an
error is detected, the process is aborted. The next packet is not
sent until the former has cleared (See Appendix V).

XMODEM-CRC. A file transfer protocol that conveys information in
128 byte packets. It uses a polynomial formula to determine the
number of bytes and composition of a file. As a result, error
correction is more reliable (See Appendix V).

YMODEM/G. A file transfer protocol that permits several files to be
sent at one time. Data is sent in 1,024 byte packets, but no error
correcting occurs (See Appendix V).

YMODEM. A file transfer protocol that permits several files to be
sent at one time. Data is sent in 1,024 byte packets. Each packet
is checked for accuracy (See Appendix V).

Zip. Describes a procedure that combines several files into one
file. The procedure uses the programs PKZIP.EXE and PKUNZIP.EXE.
This permits ease for downloading and uploading since one file can
be transferred instead of several. All zipped files have a ZIP
extension.

ZMODEM. An external protocol that permits several files to be sent
at one time. Data is sent in 1,024 byte packets. Each packet is
checked for accuracy. If the transfer is aborted, the user may
resume his or her transfer from where it ended (See Appendix V).

259