INSTALLPCPN - The Personal NetworkINSTALLPCPN - The Personal NetworkWelcome to PCPN

Welcome to the world of PCPN - The Personal Network, one of the most complete, personal,
user-friendly, multi-featured Bulletin Board Systems ("BBS"es) available today!

Running PCPN allows you, the System Operator or "SYSOP", to grant "remote users" controlled
access to your personal computer. PCPN allows users to:

        keep informed about news, events, information (bulletins)
        send and receive electronic mail
        participate in public debates
        exchange programs and/or data

Registering your PCPN further enhances your BBS's capabilities when you become a member
"node" of "PunterNet" (named after its author, Steve Punter). As a Node, you become a
member of a North American electronic communications network allowing your PCPN to
communicate with other PCPNs with both Electronic Mail and Echo Conferences, allowing your
users to:

        exchange messages, both private and public, with users on other PCPN nodes
        participate in public discussion forums or "Echo Conferences" which are usually based
         on a single topic, not necessarily computer-related (for example, "Star Trek")
        share views and opinions with other users from across the continent: Conferences
         contain (almost) exactly the same messages on each and every PCPN that supports
         them!

With PCPN "add-ons", or "Program Links" (purchased from outside vendors), PCPN can do
pretty well anything you wish. For example, users may:

        send messages out as FAX calls to real FAX machines (with a FAX modem)
        play games
        take quizzes you make up
        access a database

The new Graphics-like User Interface ("GUI") will enable even the most inexperienced BBS user
to efficiently and effectively handle all of PCPN's features with ease. Using a combination of
pull-down menus, pop-up windows, presented in full ANSI colour, this menuing system allows
a user to select PCPN commands with a single keystroke. Even in non-ANSI mode, PCPN can
still function in this manner. Help, should it be required, is available online for every single
command and prompt.

PCPN will also run as a "multi-user" system (more than one person online at a time) under a
"multi-tasking" operating system, or on a local area network (LAN) such as Novell or Lantastic.


Evaluation Copies

PCPN can be run as either an "Evaluation" copy, or as a "Registered" copy. If you received an
evaluation copy from a friend, or downloaded one from a BBS, you are free to operate it for a
period of two or three weeks. Evaluation copies contain all PCPN features except for PunterNet
network access and thus do not support Conferences, which are a major part of PCPN. Please
do "try before you buy"! If, after running an evaluation copy for two to three weeks, you find
that PCPN really doesn't meet your needs, you are under no obligation to purchase the
program, nor do you need to pay for the time period you were using it. Just shut the system
down and remove it from your hard drive (the specifics of removal will be detailed later).
Hardware Requirements

Listed below is the recommended, and the minimum, hardware you will require to operate
PCPN:




Item
Recommended Setup
Minimum Required Setup


CPU
386 or better
(PS/2 not recommended)
IBM PC or compatible


Conventional
Memory
519K free
519K free


Extended, Expanded
Memory
(not required, though multitasking
environments may require some to
load DOS, Devices, TSRs, etc., high to
allow 519K Conventional Memory
free)
(not required)


Hard Drive(s)
100 Meg and up
(any valid combination of MFM, RLL,
IDE, SCSI, ESDI)
30 Meg
(any type)




Note: Installation alone requires 13 Megabytes free


Monitor
CGA Colour (80x25) or better
Any monochrome text
(80x25)


Serial Port
Standard serial port, or RS232
Adapter with an Intel 16550AN UART
chip (for fast modems)
Standard serial port


Modem
USR Courier HST Dual Standard, or
any V.32 14.4K bps modem
Any direct connect (non-
acoustic) 300 baud modem


Modem Cable
25 pin shielded RS-232 cable
25 pin shielded RS-232
cable


MS-DOS O/S
MS-DOS 5 or higher
(MS-DOS 6 "DoubleSpace" disk
compression does seem compatible)
MS-DOS 3.3


Backup System
Any Tape Drive
Backup to floppy software
(ie; FastBack, QuikSave)


Printer
Optional. Any will do (dot matrix,
daisy wheel, or laser, preferably with
IBM character set)
(not required)


Phone Line
A voice grade telephone line without
"Call Waiting". Do not use a Party
Line.
A voice grade telephone line


Network (LAN)
Optional. Any network, that once
loaded, leaves at least 519K free.
(not required)


CD-ROM
Optional (for download files). Any that
can run leaving at least 519K free.
(not required)


Multi-Line
Requirements
-    DesqView with QEMM
-    2 or more serial ports with modems
     on each
          and/or
     LAN File Server with one or more
     workstations
(use as single line only)

PCPN Registration and Support

To register your PCPN, send $99.95 cheque or money order (CDN funds in Canada, US funds
elsewhere) to:

 PCPN Support                            Make cheques payable to: Steve Punter.
 4342 Forest Fire Lane
 Mississauga, Ontario
 Canada  L4W 3P4

Please also state what size and density floppy diskettes you require (360K 5.25", 1.2M 5.25",
720K 3.5", or 1.4M 3.5"). It would be appreciated if you would also supply your BBS's phone
number, and a voice number where you may be contacted should there be any network
problems.

In return, you will receive the latest version on floppy diskettes, a printed manual, and most
importantly, your PunterNet network access code, Node number, and Security Codes which will
enable to you to complete your PCPN installation.

We would like to be informed of any difficulties you do encounter, no matter how small, as well
as any suggestions for improvements, or even compliments, that you may wish to pass on to
the author. Please note that we can not guarantee a response by mail (land mail, such as
Canada Post, the U.S. Postal Service, or a courier); once your PCPN is fully operational, please
use PunterNet messages or the Conferences for correspondence. Your continued support will
help us make PCPN a better program for all to enjoy for many years to come.


PCPN Manual Conventions & Symbols

PCPN documentation is divided into three sections:

 Installation Guide
 User's Manual
 SYSOP's Manual

We hope to present information in a logical order, discussing simple concepts before introducing
more complex ideas. As PCPN SYSOP, you should read through all documentation to familiarize
yourself with PCPN's features.

Feel free to copy and distribute the User's Manual to your users. It covers all the concepts and
commands they will need to utilize PCPN to its fullest potential.

The following table shows the print styles used throughout the manuals:




Sample
Meaning


Phrase
Something you type on the keyboard


<ENTER>
A key on the keyboard that you press


<CTRL>-A
A combination of keys that you press together (like "CONTROL" and "A",
here)

The Supplied Diskettes

PCPN is supplied on either 5.25, or 3.5 inch diskettes. With the exception of the installation
program, INSTALL.EXE, and PKUNZIP.EXE, all files are compressed. Installation cannot be
accomplished by merely copying files to your hard drive. If you have ordered your copy of
PCPN directly, then you may have been assigned a Node Number. If this is the case, your
network codes will also appear on the supplied diskettes.












Creating a New System

The following section covers first time PCPN installation. Note that multi-user versions require
only one installation of PCPN.

Installation Methods

You may install PCPN directly from the floppy diskettes, or by copying the floppies onto your
hard drive first. Installing from your hard drive is about 1.5 times faster than installing from
floppies. The following chart gives approximate installation times:




Installation Type
Time using a 386 (33 MHz)
Time using an XT


Floppy Direct
11 minutes 36 seconds
40 minutes
37 minutes 35 seconds


Copy Floppies, then from
Hard Drive
7 minutes 39 seconds



With either method, you must first note the path to your PKUNZIP.EXE, as you will need this
to specify its exact location during the installation process. If you do not have PKUNZIP.EXE,
you will find it on the PCPN diskette labelled "Install". Copy it onto your hard drive (anywhere
you wish, but remember to note the path).

If you choose to install from your hard drive, copy all the PCPN diskettes into a directory (any
name) on your hard drive now. DOS's XCOPY can be used to copy all the files on each
diskette:

 md c:\pcpnzips    Make the directory (or pick an existing one)
 cd c:\pcpnzips    Change into it
 xcopy a: /v  Copy Disk in a: (repeat for all PCPN disks)
Running INSTALL.EXE

You may choose to install your PCPN onto any hard drive, in any directory you wish. This
allows PCPN to run over a network, as it may be located on a remote server. The only
requirements PCPN has of C: drive are the modifications it needs to make to the
AUTOEXEC.BAT and CONFIG.SYS files so your device drivers and DOS environment settings
are correct.

If installing directly from floppies, insert the PCPN diskette labelled "Install" into drive A: and
type a:install (INSTALL.EXE can not be run from B:). If installing from a hard drive, either
have INSTALL.EXE in your DOS path, or prefix it with its own path.

INSTALL.EXE acts according to the start up parameters you specify:




To have PCPN Install to:
Type the Following:


C:\BBS
(the usual set up most SYSOPs choose)
c:
install
  or
install c:\bbs


[drive:]\BBS
[drive:]
install


[drive:]\[path]
[drive:]
install [path]
  or
install [drive:\path]


Note: The default path of "\BBS" on the current drive, or the path you specified as a parameter,
must NOT already exist! If it does, you will get "[drive\path] already EXISTS!". This is to
prevent SYSOPs already running PCPN from writing over their existing BBS, should they
attempt to create a new PCPN system by mistake. Either delete this path or restart
INSTALL.EXE with a path that doesn't exist.

The installation program will present the following menu:


















Note that on your screen, above the option list, is the path you have chosen for your BBS.
Make sure this is what you expected... or choose option D. Return to MS-DOS and restart
INSTALL.EXE.

If you have decided the path is correct, choose 1. Create New System. You'll now be asked
to give the location of PKUNZIP.EXE on your hard drive. This allows the installation program
to properly uncompress the files which came on your PCPN diskettes. For example, if your copy
of PKUNZIP.EXE was located on drive "D:" in a path called "COMPRESS", then you would enter
the following at this prompt:

 d:\compress

Next, you'll be asked to supply the location of your BBS ZIP files. These will either be located
on the floppies you were shipped, or you will have already copied them to your hard drive as
described earlier. If the files are to be installed directly from floppies, merely press <ENTER>
at this next prompt. However, if you wish to install the system from your hard drive, then you
must enter the path of the ZIP files as you did in the prompt above for the PKUNZIP.EXE
program. For example, if you have copied the ZIP files to drive "C:" in a path called
"PCPN\ZIPS", then you would enter:

 c:\pcpn\zips

The installation program will now use PKUNZIP.EXE to extract the stored PCPN version number.
This information will be used to verify that you are using the correct version of the
INSTALL.EXE program.

System Variables

When installing a brand new system, certain important "System Variables", as defined in the
following pages, must be assigned before the BBS can even be added to your hard drive. All
of these variables may be changed after you have run INSTALL.EXE (except for "Size of Main
Msg Base", which doesn't matter, as this size may grow dynamically at a later time). You may
do this even after your PCPN has been up and running, so if you haven't made a final decision
on these choices, just use something temporary for now. The following table shows what
characters make up the various "groups" which may be input as System Variables:




Lower Case
a b c d ... z


Upper Case
A B C D ... Z


Numbers
0 1 2 3 ... 9


Symbols
! @ # $ % ^ & * ( ) , etc. (keyboard keys other than letters and
numbers)


High ASCII
ASCII 160 to ASCII 254
Not recommended, but valid anywhere symbols may be used.
These characters are guaranteed visible only on IBM & clones
thereof; they may appear as a completely different character on
another type of computer. Also, certain printers may have adverse
reactions when trying to print them. If desperately needed, you can
enter them by holding down the ALT key while typing the
corresponding number on the numeric keypad


In-Text Commands
"PCPN ANSI": The way PCPN allows you to enter ANSI codes
(such as colour) into your text. Not important right now, you can
add these later if you fancy.

The following tables list each of the System Variables that you be will asked for, define their
purpose, outline what groups of characters may be entered, and state how many characters
you will be allowed to enter (or what numeric range is valid):




Variable
System Name


Purpose
Your PCPN BBS' Name


Input Type
Upper/Lower Case, Numbers and Symbols


Max Length
38


Comments:

The title of your system, usually its name. This text is used to create a default opening screen
for callers. You may change this screen to any five lines of text you like from a command within
the BBS.





Variable
Board Tag


Purpose
Tags messages with a unique system identifier


Input Type
Upper/Lower Case, Numbers, Symbols, In-Text Commands


Max Length
8


Comments:

These 8 characters are tagged to any PunterNet mail originating from your system. Your "Board
Tag" appears in the header of all non-Conference messages and is also appended to the
"Posted" line of all private PunterNet mail, so that printed copies of the messages may be
identified as having come from your system.





Variable
SYSOP's Name


Purpose
Used to identify the real name of the System Operator


Input Type
Upper/Lower Case (Numbers and Symbols allowed though not
recommended)


Max Length
38


Comments:

Capitalized: Any lower case you enter will be translated to upper case. Do not use High ASCII or
people may not be able to send any messages to you!

The letters "SYSOP" are often translated into the full name of the System Operator where
confusion may exist as to who the real SYSOP is (as in Conference messages). In addition, any
non-Conference mail addressed to the SYSOP by your full name will be translated as "To:
SYSOP".




Variable
SYSOP's Password


Purpose
Assigns the access password for the System Operator


Input Type
Upper/Lower Case, Numbers, and Symbols


Max Length
6


Comments:

Capitalized: Any lower case you enter will be translated to upper case.

During installation, the user "SYSOP" is added to the user list, and given the password you
designate here. This password will allow you to gain remote access, while preventing
unauthorized persons from doing so.





Variable
Location of Node


Purpose
To identify the location of your system


Input Type
Upper/Lower case, Numbers, and Symbols


Max Length
38


Comments:

Capitalized: Any lower case you enter will be translated to upper case.

This location is added to user name "SYSOP" as your designated location.





Variable
X00 Port


Purpose
Specifies the serial port to which the modem is attached


Input Type
Numbers


Range
0 to 7


Comments:

This refers to the X00 FOSSIL driver port number, which is always one less than the DOS COM
port number, ie:

 DOS             X00
 COM 1           Port 0
 COM 2           Port 1
 COM 3           Port 2
 COM 4           Port 3
   -             Port 4
   -             Port 5
   -             Port 6
   -             Port 7

Enter the X00 port number that your modem is connected to. To assign modems to X00 ports 5
through 8, please read the documentation which comes with this device driver.




Variable
System Type


Purpose
Defines the type of system (open/semi-closed/closed)


Input Type
Numbers


Range
0, 1, or 2


Comments:

PCPN allows you to set up three different types of systems. Each type handles new users in a
different manner, as described below:

0    Open: Immediate access at Security Level 1. Most flexible, as Security Level 1 can be
     defined with hardly any access allowing only a brief look-see, right up to full access to
     everything, at your discretion. New users at Level 1 can later be "validated" to a higher level
     with more access if you so desire.

1    Semi-Closed: New users are allowed to register (enter the User List), then they are signed
     off without gaining any access to your BBS. You have to validate them to a Security Level
     that grants access before they will be allowed into the BBS. This type of system is normally
     used by those running pay BBSes.

2    Closed: No access at all to new users. Any user names not recognized as already in the user
     list are shown a message (you may write one) and disconnected. You must manually add all
     new users who you wish to give any access to. This system type is normally used by those
     running completely private BBSes.





Variable
Password Required


Purpose
Determines if all callers must enter a system password


Input Type
Numbers


Range
0 or 1


Comments:

This refers to a password granting initial access to your BBS, not to any users' individual
passwords. Only users who know this password will be able to sign on to your BBS, while
those that don't know it will be shown a message (you may write one) and disconnected.

A BBS, or System, password is usually used where you only want a certain group of people to
sign on your BBS as either new, or established, users. For example, a computer club may put a
password on their BBS and publish it only in their newsletter, thus cutting down on the number
of non-club members who can sign on.

An entry of "0" means you do not wish to implement password protection on your system,
while an entry of "1" means you do.




Variable
Password #1 and Password #2


Purpose
If passwords are required, defines what the passwords are


Input Type
Upper/Lower case, Numbers


Max Length
20


Comments:

Capitalized: Any lower case you enter will be translated to upper case.

If you chose to have the System Password active in the previous question, you'll be required to
supply two passwords. As it's certain that the password will eventually be leaked, there are
actually two System passwords in effect at any time. This lets you change passwords every so
often without locking out your users who haven't received the newest password yet. With a bit
of thought, you can see that making both these passwords the same one week after issuing the
new one allows one week for all your current users to obtain the new password.





Variables
Tries at System or User Password


Purpose
Limits how many times a caller may fail to enter a correct password


Input Type
Numbers


Range
1 to 99


Comments:

The number of times a user may incorrectly enter the System password, or their personal
password. After this number of times, the BBS will disconnect, thus preventing unauthorized
users from tying up the BBS phone line playing "guess the password" games, or attempting to
sign on as somebody else.





Variable
Standby Messages


Purpose
Display (or not) a Standby message while loading a Link


Input Type
Numbers


Range
0 or 1


Comments:

On slower computers, usually only XTs, you may wish to have the BBS notify your users to
"Standby" while it loads Links (so they don't think your computer has crashed on them). 386s
and faster are generally fast enough that there is hardly any perceptible delay during these
loads.

"0" = No Standby Messages, "1" = Show Standby Messages




Variable
Pieces of Extra Data


Purpose
Defines the number extra items a user must enter to register


Input Type
Numbers


Range
0 to 3


Comments:

You may have the BBS store up to three extra items of data about each user. When a user first
signs on, they will be asked to supply these items, which will then be written to their user
profile which you, or they, may edit later. You may use this feature to find out more about the
user, such as their phone number, birthday, computer type, etc. Select 0 for no extra data, or
from 1 to 3 for up to three items.





Variable
Extra Data Prompt #1 to #3


Purpose
Defines the prompt for each extra data item


Input Type
Upper/Lower case, Numbers, and Symbols


Max Length
38


Comments:

If you choose to have any Extra Data, you will be prompted to enter the questions you would
like to ask of your users. Don't end with a question mark; one will be generated automatically
for you.

Note: A useful trick to know is that if you blank or clear out one of your user's Extra Data
Fields, they will be asked to fill it in again next time they sign on.





Variable
Size of Main Message Base


Purpose
Defines the initial size of the non-Conference ("MAIN") message base


Input Type
Numbers


Range
100 to 3000


Comments:

Sets the maximum number of messages in your main message area (all messages not including
PunterNet Conferences).

This size is used while creating the random access file that contains your main messages (to be
exact, their headers). Though initially empty, it is created at its full size so that it occupies
sequential disk clusters on your hard drive, which speeds up access. You will not, therefore, be
limited to the size specified here. However, remember that if the size is dynamically increased
later, as more messages are entered, the file may become fragmented. This will result in
decreased performance when reading messages beyond the initial limit.

Unless you're pressed for disk space, choose the maximum number of messages (choosing
3000 uses about 600K, while 100 uses about 20K).




Variable
Drive Letter of EXE Files


Purpose
Defines the physical drive upon which executable files are found


Input Type
Upper Case


Range
C to Z


Comments:

Enter the hard drive letter where you wish the BBS .EXE files to be placed. Any existing hard
drive (or RAM drive) is valid, from C: to Z: You should have at least 6.5 Mb free on the drive
you choose. Never choose a floppy, tape, or CD ROM drive.

The .EXE files will be placed on this drive, in a \BBS directory (or the directory you specified as
a parameter to INSTALL.EXE).



What Next?

Once you have answered all the questions, the installation program will extract all the required
files from your PCPN ZIPs, placing them in appropriate directories on your hard drive(s). Note
that the main BBS directory, containing especially your message bases and bulletin files, along
with various system files (but not the .EXE files if another drive was specified for them), will
be placed in C:\BBS (or the BBS directory drive and path you specified as a parameter to the
Install program).

When installation is complete, you will be returned to the Installation Main Menu, however,
we're not quite ready to run just yet. If you are installing an Evaluation copy, the very next
section on PunterNet Network Installation does not apply to you, though you may wish to read
through it anyway. The following sections will guide you through the rest of the installation.PunterNet Network Installation

PCPN can be run without the network for evaluation purposes, or even as a registered copy for
those who don't wish to join the network (although typically most SYSOPs do). Registering
your PCPN opens up a whole new world. This stage of the installation may be performed at any
time, either before or after you have had your system up and running.

When you registered your PCPN software, you received your own, unique, PunterNet node
number, and your network "Security Codes". The codes are unique to your specific node
number, so no other PunterNet node can pass itself off as you (and vice-versa). Usually you
would receive these codes on a diskette sent by mail, though they may have been uploaded to
your BBS if it was already operational. In any case, now that you have your codes, let's begin.

Run the INSTALL.EXE program as you did initially, then select option 2 from the Install Menu.
After an explanation, you'll be given three choices:









Select the choice that corresponds to where your network codes can be found. For a first time
network upgrade, this will commonly be from a floppy so you should press <ENTER>.
Otherwise you may enter the hard drive directory the codes are located in, either as a PCPN
Folder name, or as a DOS directory name.

Once the installation program locates the codes, it will need to ask you for a bit more
information:

First off, you must input your area code, so that dialling prefixes for all calls may be correctly
calculated. Next, it will need to know how to handle all types of local and long distance dialling
situations. As there is no standard throughout North America for handling how calls are dialled,
PCPN has been designed to account for all contingencies. The "Dialling Type" variable is
actually composed of a group of options which are chosen by adding together their
corresponding values.

NOTE: Changes in the Area Code System may result in the "splitting" of area codes in some
regions. PCPN has been programmed to take this into account.

Add 1           If you want to include the area code in all local calls. Normally, the area code is only
                included if the party being called is in a different area than your own. Many phone
                systems do not care if an area code is dialled, if it is the same as the one in which you
                are calling from. For that reason, it is generally safe to choose this option, though you
                should check with you telephone company first, or test your equipment by hand dialling
                a friend in your same area code, but with the area code included.

    The following table demonstrates how two sample numbers will be dialled were you
    calling from the 905 area code. Note the first dialled number is also in 905, while the
    second is in 416.




Local Calls:



Option Not Selected
Option Selected


896-1446
905-896-1446


416-967-1111
416-967-1111


Add 2           If you want the area code included in all long distance calls. Normally, the area code is
                included only if the party being called is in a different area than your own. Most
                telephone systems now require this, but it is still wise to check with you local telephone
                utility, or make some manual tests with your telephone.

    The following table demonstrates how two sample long distance numbers will be dialled
    from the 905 area code. Note the first dialled number is also in 905, while the second
    is in 416.




Long Distance Calls:



Option Not Selected
Option Selected


1-762-1233
1-905-762-1233


1-416-776-2556
1-416-776-2556


Add 4           If you wish to have a "1" added to the phone number if the area codes differ (even
                though they are local calls). Some telephone utilities require the dialling of a "1" in front
                of any phone number located in a different area code, even if there will be no charge
                for the call. Normally, the BBS only adds a "1" to the number if the Node being called
                is designated as long distance.

    The following table demonstrates how two sample local numbers will be dialled from
    the 905 area code. Note the first dialled number is also in 905, while the second is in
    416.




Local Calls:



Option Not Selected
Option Selected


896-1446
896-1446


416-967-1111
1-416-967-1111


Add 8           if you want a "1" to be added to all calls, regardless of whether they are local or long
                distance. This is a rare situation, but should your phone company require this, the
                option is available.

A typical scenario would require option "+2" only, so the value entered for "Dialling Type"
would be simply 2. However, you may also require the "+1" option, in which case the value
entered would be 3.

Next you'll be asked for a wait factor in dialling. Generally speaking, you can enter a value of
zero here and have no problems. However, some telephone systems are a little slow, and
require that the phone be "placed on the hook" for longer periods of time in order to get a dial
tone. If you find that you must hang up the phone for longer than a second before picking it
up again and getting a new dial tone, then you may want to consider making this value higher.
Enter the number of seconds you wish to have the system wait before "picking up the phone
and dialling".

Next, the installation program will ask at what rate you wish to charge users for sending long
distance PunterNet mail. The charge is based on the transmission of 100 characters of text at
2400 baud. The actual cost charged to a user is scaled to correspond with the baud rate of the
Node to which the message is being sent (or your baud rate, whichever is lower). This does not
refer to Conferences, but to messages sent in private to another specific system. A screenful
of text contains 2000 characters (if packed absolutely full), which would be about 20 "packets"
of 100 characters. A charge of 0.5 cents would net 10 cents for our sample 2000 characters,
which is probably more than enough (check your long distance rates to be sure). If you have
a higher speed modem, charges are "scaled" to match the actual baud rate compared to 2400.
For example, 9600 baud connections would be 4x less expesive.
The minimum charge is fixed for all baud rates, and represents the lowest possible fee that a
user will be charged for sending a private PunterNet message. This feature is supplied to
accommodate the minimum charge levied by most telephone companies on long distance calls.

Local PunterNet messages are usually free, but should you wish to charge for them, you may
do so. They will be charged for at the rate of a long distance PunterNet message, multiplied by
this Local Charge Factor. For example:




Charge
Factor
Amount Charged for a Local PunterNet Message


0
Local Messages are Free


0.5
Local Messages are half the cost of Long Distance


1
Local Messages are the same price as Long Distance


2
Local Messages are twice the price of Long Distance


You may wish to make your local PunterNet messages free, but to discourage users from
sending tons of messages (for example, "For Sale") to every local node and not getting charged
anything, you can set a separate charge rate for use of the LOC/ALL and LOC/SYSOP feature.
This factor works the same way as the Local Charge Factor, above, as a percentage of the long
distance message charge.

PunterNet supports the idea of "Pathway" nodes. What this means is that PunterNet messages
may be sent via another node, without that node actually acting upon them. This is allowed for
three reasons:

Firstly, say node A wants to send a message to node C, but node C is a long distance call.
However, there exists a node B which is a local call for both A and C. When A wants to send
to C, it instead sends to B, which then simply passes the message along to C. That way,
nobody pays long distance rates for any calls. C can also send its messages to A, via B. Users
on any of A, B, or C, can send their messages as local directly to any user on any of the three
nodes; PunterNet takes care of the pathway process invisibly and automatically.

Secondly, "gateways" can be built. When an area has a lot of nodes that are local to each
other, one node decides to provide a pathway to all the others. When a long distance node
wishes to send to any number of these nodes, it simply sends everything to the gateway,
which then distributes the messages to their appropriate nodes. This lets the long distance node
make only one long distance call, rather than having to call each of those nodes in turn.

Finally, some nodes operate on phone lines that charge a certain amount per call, even if it's
a local call. These nodes can collect all their outgoing messages, and send them to another
node, which can call out for free. The second node then distributes all the messages to their
appropriate destinations.

You can decide whether your Node may be used as a pathway by selection either a "0" or a
"1" when prompted for "Pathway Flag?". Note that even if you do allow your Node to be used
as a pathway in the above manner, you are never forced to pass along a message which would
incur long distance charges.

This completes the conversion of your PCPN to a PunterNet node, though you are not yet
"active". Once we have your BBS up and running, exactly how you become an active node will
be detailed.
Local Mode Boot

You have now successfully completed the installation of the files necessary to run the BBS.
However, we aren't done just yet, since there are a number of important details which must
be seen to first.

During installation of all the files, a batch file called "BBS.BAT" was created in your main BBS
sub-directory. Copy this BAT file over to the sub-directory you commonly use to store batches,
or move it to a sub-directory that exists within your "PATH". It isn't necessary to path the BBS,
as it does not rely on default paths to function. Once you have moved BBS.BAT file, you may
start execution of the board at any time by merely entering BBS and <ENTER>. Do so now
to boot the system.

You should immediately see a box appear at the top of your screen. This box is known as the
"Status Line", and is used to show you what's going on. Within a few seconds, the words "No
Modem Profile Selected ... Board Will Run in Local Mode Only" will appear on the screen
beneath the Status Line. Don't worry about this, as our first task now that we have the BBS
has loaded will be to change this so that a modem is recognized.

Defining Your Modem Profile

All modems are different, and each requires a unique approach to handling commands and
result codes. This means that the BBS cannot be written in a generic form that will work with
everything. Instead, we use modem drivers, which are referred to as "Modem Profiles". Before
we can select a Modem Profile however, we must log into the system. The screen will clear,
and the name of your board will appear, along with the present time, and a prompt to enter
your name. As the System Operator, your name is actually SYSOP. Enter this now. Since this
is local mode, no password will be asked for, and you will gain immediate access to the system.
By default, the SYSOP's user profile has been created with the Menu Shell active. To help you
become you accustomed to its nature, we will use the Menu Shell exclusively to lead you
through the rest of this installation guide.

We must first move to a new "Link" called the FIXLINK. Much of PCPN is broken down into
smaller program chunks called links. You'll move between them quite often. To move to the
required link, press the "L" key, and a box of selections will appear on the screen. Select the
Fix Link by scrolling down to that entry using the cursor up and down keys, then pressing
<ENTER>; or simply press the "F" key. The new link will be loaded, and a brand new menu
will appear on the screen. Choose option "E", and a further list of options will appear on the
screen. Choose "M" to edit Modem Profiles. A third list of options will appear. Choose option
"D" to Set Default Profile.

A new type of box will now appear on the screen which allows the entry of a string of
characters. As you have no idea what to enter, do as the instructions in the box suggest, and
type "L" (followed by <ENTER>) to see a list of available Modem Profiles. The screen will
clear, and a list of profile names will appear. While limited to only 8 characters, the profile
names should be descriptive enough to identify one which suits your modem. The dialog box
prompting for the name of the Modem Profile will have reappeared on the screen, so type in
the name of the desired profile now, and press <ENTER>.

However, what if none of the available profiles seem to fit your specific brand of modem? The
first thing that can be done is to try various profiles that seem as though they might work. You
can't damage anything trying, and you might end up saving yourself a lot of trouble if you can
locate an existing profile that will work. If you're going to follow this route, select a profile
now, and continue with the installation process.

If, however, you can't find a profile that is even remotely close, then you will need to contact
Customer Service for more details. The phone number is located at the end of this section.
They will give you some advice about writing your own profile, or modifying an existing one.
That's all there is to it, we have now installed the necessary modem driver, though it will not
take effect until the system is next booted. Let's exit the system now so that we may reboot
and test that the modem responds as it should. Press "Q" to indicate that we wish to quit, then
press <ENTER> to verify our decision. You will now be logged you out, and the board will
return to the initial login screen. In response to the "Your Full Name?" prompt, type MSDOS
and press <ENTER>. Once the DOS prompt reappears, start the system once again, and
observe what happens.

If the modem fails to respond, one of a number of things may be wrong. However at this stage,
you just want to get control of your computer back. As the system has probably locked up as
result of the modem's failure to respond, it is best to reset your machine by pressing <ALT>,
<CTRL>, and <DEL> simultaneously. If that doesn't work, then press the "Reset" button,
or power down the computer. Once you have regained control and are back at the DOS prompt,
we must take steps to remove the selected modem profile so that we may successfully boot
the BBS once again.

Change to the main BBS sub-directory, C:\BBS, or the path you created when you ran
INSTALL.EXE. Once in that sub-directory, type the following DOS command:

 del modem.1

This removes the previously selected default Modem Profile, so we may boot the system as we
initially did. Reboot the system, and log back on as SYSOP. You might have chosen the wrong
Modem Profile, in which case you may repeat the above procedure for another profile name,
and try again. You may have selected the wrong X00 port when installing the system. Don't
worry though, this doesn't mean you'll have to erase everything and start again.

Press the "L" key to get a list of links, then press "E" to choose the Edit Link. A new menu will
appear on your screen. Select option "E" to Edit System Files, and a new list of options will
appear. Choose "V" for Edit Variables. The screen will clear, and a list of variables, and their
present contents, will appear. Check field "C", and make sure the selected X00 port is correct.
Remember, X00 numbers its ports from zero, while physical ports are numbered from one. If
your modem is attached to physical port 1 of your computer, then the X00 port designation
should be 0. If your modem is attached to physical port 2, then the X00 port designation should
be 1.

If the X00 port is wrong, you may edit it now by typing "C" followed by <ENTER>. This will
move the cursor up to the line containing the present port number designation. Press <BACK
SPACE> to delete that number, then type in the correct port, and press <ENTER>. Exit the
editor by typing "X", followed by <ENTER>, the press "Y" to verify that you wish to save the
changes. With the port correctly assigned, return to the FIXLINK and reselect a default Modem
Profile.

Reaching Customer Service

If you still can't get your system to boot with the modem after checking these things, please
call our Customer Service Line. Unlike larger corporate software vendors, we cannot afford to
maintain a bank of service representatives who are paid to nothing but. We do, however, have
some volunteers who can answer your questions, so long as you don't need to use up huge
amounts of their time. Our Customer Service (such as it is) can be reached at:

 (416) 635-2908 during business hours

Note that this is Eastern time, so calculate your calling hours accordingly.
Setting Up Security

Access to various sections of PCPN is controlled through a fairly elaborate security system.
Your first line of defense is the "Security Bits" which may be set or cleared at your discretion
for each of 15 available Security Levels. Levels are numbered 0 through 14, though you may
find you don't need them all. Three of them, however, do have predefined purposes. Level 14
is reserved for high end users such as you, the SYSOP, and should always be left will all
available bits set. Level 0 is relegated to sub-entry level access, and is used primarily for putting
a user on "temporary hold". Access to level zero would either be excessively limited, or used
to lock out users assigned to it. First time callers automatically get Level 1, so this Security
Level should be assigned with the kind of access you want for first time callers. Validation of
a caller is done by changing his Security Level to 2, or higher.

Logon your system as SYSOP, then press "L" and "E" to go to the Edit Link. From this link's
Main Menu, choose option "S" for Security Systems, then choose option "S" again for Edit
Security Levels. The screen will clear, and an array of asterisks will appear beside a list of
attributes. There are 30 attributes in total, only 15 of which are presently shown on the screen.
Your cursor should currently be located on the space designated for the first attribute, under
"0", meaning Security Level 0. Using the standard cursor movement keys, you may position
the cursor to any of the available locations on the screen. Pressing the period key will set a
specific Security Bit, while pressing <SPACE> will clear it. To move to the next group of 15
attributes, press the "N" key.

The following table outlines the purpose of each Security Bit. Note that each bit is completely
independent of the others (except for the "Fwd Flags"). The bits designated with an pointing
hand are generally reserved for SYSOPs, and should not be granted to regular users. If you
really aren't sure at this time what a bit does, then it is best to leave it clear until you are sure
that it will be of value to your callers.




Bit
Description
Purpose


0
 Read All
Allows reading of messages addressed to "ALL".


1
 Read Spec User
Allows reading of public messages addressed specifically to any
user.


2
         Read Private
Allows reading of all private mail.


3
 Send All
Caller may post messages in the main base to "ALL".


4
 Send Spec User
Caller may post public messages to any other specific user.


5
 Send Private
Caller may post private messages to any other specific user.


6
 Receive Public
Allows other users to address public messages to the caller.


7
 Receive Private
Allows other users to address private messages to the caller.


8
 Fwd Flag Bit 0
These three bits, taken together, form a binary number which
defines the manner in which one user may forward messages to
another. See the notes which follow this table for details on setting
these bits, or leave all three clear.


9
 Fwd Flag Bit 1



10
 Fwd Flag Bit 2



11
 All Bulls
Grants access to all bulletin section sub-directories, not just the
"MAIN" directory.


12
         Use PNET
Allows the caller to use the PNET command in the SET link.


13
         Use PVT
Allows the caller to use the PVT command in the SET link.


14
         No Idle Timer
With this bit set, the caller is under no obligation to do something
within a preset time. They will not, therefore be "idled off" the
system due to inactivity.


15
         General Edit
Gives the caller access to many of the editing commands.


16
         NET Commands
Gives the caller access to many of the network control commands.


17
         FIX Commands
Gives the caller access to many of the fix commands.


18
         Edit TO Them
Allows a caller to edit messages which are addressed TO them,
rather than only ones that they have composed.


19
 Local Pnet
Even though you may have defined local PunterNet messages to be
free, users are still required to have an account balance before
they may send any. By setting this bit, you grant the user the right
to send free local PunterNet messages without having an account.
Does not apply if local PunterNet is not free.


20
         Access GROUP
Gives the user access to the GROUP command in the XCON link.


21
         Access USER
Gives the user access to the USER command in the XCON link.


22
         Create
Extended
Gives the user permission to create a Folder with an extended
path. Applies on to user with SYSOP access to the Parent Folder.


23
         Use COMP
Gives the user access to the COMP command in the EDIT link.


24
         Use DR
Gives the user access to the mass deletion of messages via the DR
command in the Main Message Area.


25
         Send to Bull
Allows the user to create or edit system bulletins via the EB
command of the Main Message Area.


26
         Send HELP
Allows the user to create or edit online help files via the EB
command of the Main Message Area.


27
         Bull Dirs
Allows the user to create or destroy Bulletin Section sub-
directories.


28
 Not Used
(For future expansion)


29
 Free LOC/ Msgs
Allows the user to circumvent the charges normally imposed for a
LOC/ALL or LOC/SYSOP message.


The following table outlines the 6 possible settings for the "Fwd Flag Bits", and describes the
effect they will have on the message forwarding process. By the way, "forwarding a message"
refers to the act of taking a message addressed to one person, and making a second copy
addressed to another person.



Bit 0
Bit 1
Bit 2
Messages Which May Be Forwarded


Clear
Clear
Clear
Public mail to yourself.


Set
Clear
Clear
Any mail to yourself. Private messages will remain private.


Clear
Set
Clear
Any mail to yourself. Private messages can be made public.


Set
Set
Clear
Any public message.


Clear
Clear
Set
Any message. Private messages will remain private.


Set
Clear
Set
Any message. Private messages can be made public.


To exit the Security editor, press the "X" key, then <ENTER>. Verify that you wish to save
the changes by pressing the "Y" key.

Your second line of defense concerns time limits placed upon a caller. Again, each Security
Level is assigned its own group of time limits. To edit the assigned time limits, press "L",
followed by "F" to move over to the Fix Link. From this link's Main Menu, press the "E" key
to Edit, then the "T" key to select Maximum Times. Your screen will clear, and a table of
maximum times will appear for each of the 15 available Security Levels. Note that the maximum
times have been defaulted for Level 14, of which SYSOP is a member.

There are five different time limits specified in the table. Each has a unique function:




Time Limit
Description


Day Max
Defines the total number of minutes that a user may spend on your system in
a 24 hour period. After exceeding this maximum, the user will be logged off,
and any subsequent attempts to log back in prior to midnight will display an
explanation message.


Call Max
Defines the total number of minutes that a user may spend on your system
during a single call. This limit is not strictly imposed, so if a user is composing
a message, or transferring a file, when the limit is exceeded, the user will not
be immediately thrown off.


D/L Max
Defines the total number of minutes that a user may spend downloading files.
Once the limit is exceeded, the user will be unable to download any further
files until after midnight. This has no effect on uploading, which may take
place so long as the user is allowed online.


Warning
Defines the number of minutes prior to an automatic logoff (as specified by
Day Max or Call Max) that a user starts to receive reminder messages. Setting
this to zero stops reminder messages from appearing.


Idle
Defines the number of seconds a user is allowed to remain idle before the
system will automatically log them off. This limit may be circumvented by
Security Bit 14.


To edit any Security Level's time limits, type the letter appearing next to the level in question,
then enter new values for each of the five limits on that line of the screen. Press <ENTER>
after each entry. To keep an old entry, just press <ENTER> to move on to the next. Press "X",
followed by <ENTER>, to exit the command.

Quick Tour of the Full Screen Editor

In the next section, you are going to be required to create or edit some system bulletins. These
will be used for various purposes, from opening bulletins, to controlling link access to the
system. In order to do that, you must have at least a basic understanding of one of the
system's two available editors. Because it is the most powerful, the Full Screen Editor will be
discussed at this time, though you aren't restricted to using it if you don't want to.

As its name implies, the Full Screen Editor allows direct manipulation of the on-screen text in
the same manner as a word processor. Enter text by merely typing it, but don't press
<ENTER> unless you wish to leave a blank line, terminate a paragraph, or terminate a single
line of "stand alone" text. As with word processing programs, <ENTER> actually inserts a
"hard return" into text, and uses this when deciding upon the format of a line. Unlike other
Bulletin Board Systems, PCPN actually formats text to match the screen width chosen by the
user. Text is saved to disk in "raw" form, so the "hard returns" are important delineation points
within the text.

To edit text, use any of the four standard cursor movement keys to position the cursor to the
area where you wish to make alterations. The text will automatically scroll as you go off the
top or bottom of the editor screen. Normally, newly typed characters will "overstrike" those
already on the screen. To cause the new characters to automatically insert themselves, press
the <INS> key to put the editor into "Insert Mode". You may turn off this mode by pressing
<INS> a second time. Either <DEL> or <BACKSPACE> delete characters. The difference
is that <DEL> deletes from under the cursor, while <BACKSPACE> drags both the cursor,
and the text, over the character immediately to the left (a standard DOS practice).

Once a bulletin has been composed, you may save it by pressing <ESC>, followed by the "S"
key. To verify that you wish to commit to this action, type "Y", followed by <ENTER>. You
may abort a bulletin by pressing <ESC>, followed by "A". To verify this action, type "A" once
again, followed by <ENTER>. This isn't the extent of the editor, of course, but it's as much
as you need to get on with the task at hand. Feel free to play around with the editor and learn
some things about it on your own.

Entering and Editing Bulletins

Bulletins are different from messages, in that they are not part of any "Message Base" or
"Conference". They are merely text files which may be read by the system for the purposes of
informing a caller of certain conditions, features, or limitations. There is also a "Bulletin
Section", in which large numbers of bulletins may be grouped together to form a kind of
electronic magazine for your users. It isn't necessary that we set up the Bulletin Section at this
time, so that part will be ignored for the purposes of expediency.

Bulletins, like messages, may also include a plethora of special in-text commands, which allow
the setting of colors, the drawing of boxes, and centering of text (among other things). Those
commands, however, are well beyond the scope of this installation guide, and will not be
covered here. For the time being, we will write strictly uncoloured bulletins with no boxes,
centering, or special characters of any kind.

To edit or enter a bulletin, first make sure you are in the Main Message Area. Check the heading
at the top of the Menu to determine where you are. If you aren't presently in the Main Message
Area, press "L", followed by "B", and it will be loaded into memory. Now press "O" for SYSOP
Only Options. From the list which appears, select "B" for Maintain Bulletins. Now press "E" for
Enter Bulletins. A dialog box will appear prompting you to enter the name of the desired
bulletin. All bulletin names (with a few notable exceptions) are made up of two parts: a sub-
directory name; and a bulletin name. These two components are separated by a period.
When the BBS is first installed, only one sub-directory exists, "MAIN". All system bulletins
(except those notable exceptions) go there. The first system bulletin we will cover is the
"Opening Bulletin". This piece of text is shown to each caller as they log into your system.
Customarily, you would use this bulletin to make any announcements you wanted everyone to
be aware of. There are, in fact, two different Opening Bulletins, one which appears immediately
after the caller has finished logging in, and another which appears just before that caller to
moved to the Main Message Area. The second Opening Bulletin (or "OB" for short) would
generally be used to show reminder messages, or to display a "slogan of the day". Both
bulletins are optional, and may be deleted, or left blank if not required.

The name of the first opening bulletin would be "MAIN.OB". Type this string in when prompted
to enter the name of the bulletin. You should have that dialog box on your screen right this
minute, if you've been following along. After you enter the name and press <ENTER>, a
prompt will ask if you wish to use the Full Screen Editor. As we haven't covered the use of the
Line Editor, you should press "Y" at this time. During file installation, a stock OB was created
on your hard drive. The contents of that stock OB will appear in the editor's work space. You
can delete this stock text by backspacing over it, or by typing on top of it. Go ahead and
compose an appropriate Opening Bulletin, then press <ESC>, "S", "Y", and <ENTER> to
send it. A box will now appear on the screen, giving you the option of returning to the BBS, or
editing another bulletin. Press <ENTER> to work on another bulletin, and use the name
"MAIN.OB2" this time. Create a second OB for your callers.

System Bulletins

The following table outlines the various system bulletins which need to be created in exactly
the same manner as you did with the OBs:




Bulletin Name
Purpose of Bulletin


MAIN.LOGOFF
This bulletin is displayed when a user logs off the system. Use to display
any closing comments you like, such as "Thank You, Please Call Again".


MAIN.NEWUSER
When a new user logs onto the system, and you have allowed new users
to access the system via the setting of System Type 0 or 1, this bulletin
is displayed once they have entered and verified their user profile
information. Use it to explain system rules, or to welcome the new user
aboard.


MAIN.NEWUSER1
This bulletin is used only on systems of type 1, in which a new user may
not gain access to the system until you have raised their Security Level
from 1 to something higher. Use to this bulletin to explain to the caller
that you have not yet had a chance to validate them, but will do so in the
not-too-distant future.


MAIN.TMAX
If a user attempts to log on after exceeding their daily connection
allowance, this bulletin is read prior to disconnecting them. Use it to
explain to the user that they must call back after midnight, when their
daily usage is reset.


MAIN.PASSWOR
D
If your board has been implemented with a system password, this bulletin
is read anytime a caller fails to correctly enter that password within the
set number of tries. Use it to explain to the caller that they have failed to
enter the correct password, and tell them what to do to obtain it, or why
they shouldn't have it.


MAIN.USERCODE
This bulletin is similar to the one above, but is displayed to a caller if they
fail to correctly enter their personal password in the specified number of
tries. Use to explain to the user what they should do to log back on the
system (ie; call you, voice).


Link Access Control Bulletins

You previously learned how to use Security Bits to control what a user can and cannot do
online. These bits do many things, but are not used to limit access to various links on the
system (both standard PCPN links, and external links which you may buy from outside
vendors). When the system is created, users with Security Levels 1 through 13 are granted
access only to the Main Message Area, the SETTINGS link, the CONF link, and XFER link. This
access is handled through a series of bulletins called "GO" through "GO14". Note that unlike
standard system bulletins, they do not include a sub-directory name. These are some of the
notable exceptions that were mentioned earlier.

Each line of these special bulletins contain three fields of data. The first is the name of the
actual command (not the menu option) which will be used to access the link. The second
(separated from the first by a semi-colon) defines the name of that link as it exists on the hard
drive (less the .EXE extension). The third field (separated from the second by a colon) describes
the link. This description is included in a listing of available links, which a user may display. If
this field is left blank (nothing after the colon), the item will not appear on the list, though it is
still a valid command. For example, the following line defines a link, called ATTACH.EXE on the
hard drive, but accessed via the command "ATT":

 att;attach:The Attach Link

Lines containing comments may be used to punctuate or delimit the list. Any line starting with
an asterisk will be taken as a comment only. For example, the following three comment lines
can be used to separate two sections of the list:

 *
 *External Links
 *

Access to any link may be restricted by Security Level using two different methods. Both
methods involve modifying the "GO" bulletin for the Level in question. To make a link
completely invisible, with no indication anywhere of its existence, just don't list the link at all.
To show the link exists, yet not allow users to enter it, replace the hard drive name of the link
with the string "&NOACC". Any attempt by users of this Level to gain access to the link will
be denied; the user will then be shown a special pre-defined system bulletin which explains that
they have been denied access on the basis of their Security Level. If you'd like to edit this pre-
defined bulletin, it is called "HELPM.M-NOACC".

For example, the following line in "GO2" would list the existence of the Attach Link, but deny
access to users of Security Level 2:

 att;&noacc:Attach Link (Needs Higher Security)

Make sure you repeat this process for each GO Bulletin that represents a Security Level in use.
There is no need to maintain an associated GO Bulletin for unused Security Levels, just don't
forget to modify the corresponding GO Bulletin if you ever do start using those levels.
The Filter File

The Filter File, "FILTER", is actually a list of "banned" sub-strings which new users may not
include as part of their names. The term sub-string refers to an occurrence of a specific
sequence of characters within a longer word. For example, "USER" is a sub-string of the word
"HOUSER". Care should be taken when composing this list, as sub-strings which appear safe
("USER"), are actually part of very common names ("Doogie Houser"). Additionally, such
obvious computer words such as HACKER, are actually legitimate last names. Safer Filter words
would be SYSOP, MODEM, ATDT, and various swear words. Remember, the Filter File applies
only to new users, and not to those who are already in the user list. This means that is possible
to manually add user names which would otherwise be rejected by the Filter File.

A sample Filter File was installed for you. You may use it, add to it, or delete it and start your
own.


Adding Users Manually

When operating a Closed System, or whenever you wish to add a user to your list, this can be
easily accomplished in the Edit Link. To get there, press "L" and "E", then choose option "U"
from the main menu. When the next list of options pops up on your screen, press the "A" key
to Add Users. Enter the user's name, city, user code, and Security Level, as prompted. If you
wish to enter their "Extra Data" at this time, do so, or else you can leave that up to them when
they first log on. After you have entered their basic profile information, an edit screen will
appear. Ignore this for the time being, and press "X", followed by <ENTER>, to exit to the
main menu once again. Repeat this process for all the users you wish to add at this time.

Network Activation

If you have registered your copy, and have now installed the network codes, your next step is
to inform the Network Administrator on Node 1. To do this, log onto your system and go to the
Main Message Area. Press "E" for Enter a Message, then choose Keyboard entry by pressing
<ENTER>. Address your message to:

 1/NET ADMIN

The subject of the message is irrelevant, but should at least give some indication of the
message's content. When asked if the message should be private or public, indicate that you
wish it to be private. Tell the Network Administrator that you have put your system online,
would like your Node's status changed to "Active". If you haven't yet supplied the network
administrator with your board's phone number, do so now. Within approximately 24 hours,
your Node's existence will begin to spread around PunterNet, and other Nodes will be able to
call you. When you save the message, you'll be further asked if this is to be "Regular" or "Fast"
delivery. Choose fast, by pressing the "F" key.

How does this message get to the Network Administrator? It is transmitted there, over
PunterNet, by your Node. Before that can happen, you must first make sure that Node 1 can
be dialled accurately. By default, Node 1 is set up on your system as a long distance call. If
Mississauga, Ontario is within your local calling area, you must change Node 1 to Local status
before a successful call may be placed from your system. Should you need to change Node 1
to local, go to the NET LINK by pressing "L", then "N". From the main menu there, choose
option "N", followed by option "L". When prompted, enter the number 1, and press <ENTER>.
Change the local/long distance status of Node 1 by pressing the <SPACE> bar, then exit the
command by pressing "X".
Your node will automatically call Node 1, sometime between midnight and 7AM the next
morning. No further action is required on your part. The network administrator will send a
message back to your over PunterNet to inform you that activation has taken place. If you don't
receive this reply within approximately 48 to 72 hours, you should look into the possibility that
the message has not yet been sent. Did you correctly set Node 1 as local or long distance?
Remember, the message is being sent to Mississauga, Ontario (which is near Toronto). Did you
remember to ask for Fast Delivery when the message was sent? If not, the message will be sent
in four days, rather than one. If you still don't get a reply, contact our customer service line
during business hours.

New Nodes and Conferences

When your system was first set up, it knew nothing of any Nodes on PunterNet (other than
Node 1), or of any available Conferences. When your Node contacted Node 1 to send your
activation message to the Network Administrator, a "Nodes Update" file containing all that
information was transmitted to you. Each change you receive is noted in a special bulletin
which is displayed automatically every time you log on (as SYSOP). If your message has been
sent successfully, you'll know it, since a long list of Nodes and Conferences will appear to you
when you next login as the SYSOP. This massive lists occurs only this once, since under
normal use, only changes to the Nodes or Conferences will be displayed.

Setting Local & Long Distance Nodes

Now that you have received a list of PunterNet Nodes, it is necessary to look through them and
determine if any are local to you. By default, all new Nodes are added to your system as Long
Distance. Failure to change any that are local may well result in the inability of your system to
successfully call them. To see a list of Nodes, first move to the Net Link by pressing "L",
followed by "N". From this Link's main menu, choose the "I" option, followed by "N" for List
Nodes by Name. Press <ENTER> to see them all. Look down the list of cities, and make a note
of all Nodes which are within your local calling area. If you aren't sure what's in your local
calling area, consult your phone directory, or contact an operator.

To change Nodes to Local, choose option "N" from the main Net Link menu, then choose option
"L". When prompted, enter the number of the first Node from your list. Press the <SPACE>
bar to toggle the Local/Long Distance status to Local. Exit the function by pressing the "X" key.
Repeat this process for each Node in your local area.

Joining Conferences

Now that you have a list of available Conferences, you may join some so that your users may
begin to enjoy the advantages of cross-country messaging. To join a Conference, move first to
the Conference Maintenance Link by pressing "L", "C", and "M". To list the available
Conferences, press "C", followed by "A" and <ENTER>. Take note of any Conferences which
either you, or your users, may be interested in. Try not to join more than 5 or 6 Conferences
in a single day, since the sheer amount of data you will have to download to get a Conference
online can really bog your computer down. To join a Conference, press "J" twice, then enter
the desired Conference number when prompted. Verify with "Y".

First, the BBS will prompt for the physical drive upon which you wish to install the Conference
files. Choose an appropriate drive letter, then press <ENTER>. The system will next display
the number of bytes free on the selected drive, and ask that you verify this to be acceptable.
You should have at least 1 or 2 Mb (minimum) free before joining a Conference on that drive.
If all is well, the system will next ask if the Conference is to have public access. If you answer
yes, then all callers who have the right to enter the Conference link will be able to read this
Conference. If you answer no, then only users that you personally grant access to will be able
to read this Conference. As we are not going to get into the details surrounding Conference
access at this time, choose "Y" for yes.
You'll now be asked to give a size limit for the Conference. As each message stored on your
hard drive uses precious space, you might have to limit the size of the Conference to conserve
space. Trimming is handled automatically whenever the number of messages in the Conference
exceeds the amount you specify. No Conference may be larger than 900 messages, so this is
the largest possible size limit that you may give. A 900 message Conference would typically
use between one half and one full megabyte of space.

Next, you'll be asked if you wish to redirect the Conference through a Node other than its
Server. The Server is defined as the Node at which the Conference technically originates. As
we will not be covering network gateways in this section, answer no so that you call the server
directly. If the server is not local to you, you'll finally be asked for a call increment. Bearing in
mind that it costs money to make a long distance call, and that one large transfer always costs
less than a bunch of little ones, choose the number of days between each call your system will
make to the served to maintain this Conference. An increment of 3 to 4 days is generally quite
acceptable. Anything more than this will greatly delay answers to messages, since not only
must they be sent out, the replies must also be pulled in. A four day increment would therefore
result in a minimum turn around of 8 days.

Finally, you'll be asked if you wish to have the Conference entered from a diskette. As the files
you need to download to put a Conference online can exceed one half, to one full, megabyte
each, it may prove to be much cheaper to have someone mail you a copy of their Conferences.
This is beyond the scope of this Installation Guide, so choose "No" when asked this question.

At this time, 0.5 Mb of space will set aside on your hard drive, and the Conference flagged as
"unreceived". Until such time as you Node can make contact with the server, thus downloading
the contents of the Conference, no users (including the SYSOP) may actually enter the
Conference for the purpose of posting mail. No matter what you entered for a call increment,
your Node will make the initial call the same night as you joined the Conference. If you join a
second Conference served by the same Node, the system will not ask for the call increment a
second time.

Technical Support & Suggestions

One of the most important Conferences to join, from your standpoint as the System Operator,
is number 1, "PCPN Technical Support". You may use this Conference to read about upcoming
changes, to ask questions about the software. Address your mail to "TECHNICAL SUPPORT",
or any other users in the Conference you feel may know the answer to a technical question
concerning PCPN. This Conference should not be used for chit-chat with other SYSOPs, or to
make derogatory comments about either the software, or its authors and/or marketers. If you
feel you must speak your mind on an issue, consider joining Conference 54, "Speakers Corner".
Within sane limits, any subject matter not better suited elsewhere may be discussed. This
includes any good or bad comments you wish to make about the software, manual, or
marketing efforts. To request Server Status for a new Conference, address messages to "NET
ADMIN" in Conference 67.

Please, remember the old marketing adage; "If you like the product, tell your friends. If you
don't like the product, tell us". However, please do so in a polite manner, as our support people
are only human too, and don't like being spoken to as though they were dirt. You are quite
welcome to make suggestions for future versions, but please do not expect what you say to
be accepted automatically. All suggestions are given equal consideration, though we cannot
guarantee that any one suggestion will be implemented. Failure to implement a suggestion does
mean your idea lacks merit, only that it was impossible to do for a number of compelling
reasons. For example, two suggestions which are at odds with one another cannot both be
implemented; one, or both, must be rejected. Also, a suggestion may be deemed too complex
to attempt, though a modified version of it may be adopted.
It has been our observation that many SYSOPs feel slighted, or even ignored, if suggestions
they make are not used, while those of other SYSOPs are. We don't wish to create any feelings
of alienation, so it is strongly recommended that suggestions not be posted in public
Conferences. Instead, make your suggestions in private PunterNet mail, addressed to
"1/TECHNICAL SUPPORT". Our technical support people may comment upon your idea, if they
wish to obtain further details. Generally speaking though, your suggestion will be
acknowledged, and thanks given for your active participation.

PunterNet is a very small network, and as such, the coming and going of even one member
system is either a great triumph, or a terrible blow. Harmony among System Operators is
always difficult to maintain, since we are all very different people, with very different ideas.
Please try and uphold the rights of others to have those differences, and don't bicker amongst
yourselves as many past SYSOPs have done. Not only does it create a bad feeling between the
participants, it also makes it difficult for others. PunterNet is supposed to be fun, and it doesn't
take all that many bad apples to spoil the bunch.

Inevitably, there will be individuals on the network who are both annoying and persistent.
Through years of experience, it has been found that the best way to deal with such individuals
is to ignore them. If you insist on taking their bait, you'll only encourage them to do even more.
Try, therefore, to resist the urge to belittle some of the PCPN fools, and treat them for what
they really are, just a small fish in a much larger ocean. Do your part to maintain harmony and
goodwill, and we'll all benefit for it.













Booting the BBS

Now that you have set up all the basic operating requirements for your particular installation
of PCPN, you are ready to tell the BBS to wait for your first call. If you are still signed on, quit
from the system now with "Q", then <ENTER> to verify. The screen will clear and "Waiting
For Call" will show on the Status Line. While waiting for a call, PCPN may be switched into
local mode by pressing the <F6> key on the local keyboard. While prompting for a logon name
in local mode, the program may be returned to remote mode by entering REMOTE, then
<ENTER>. Remote mode refers to the state in which the BBS accepts calls from outsiders via
the modem. Local mode refers to the use of the BBS from its own keyboard and monitor (no
modem).

When booted from the DOS command line, you may force PCPN directly into remote mode by
placing a lone "R" after "BBS" command, like so:

 BBS R
Cancelling an Evaluation Copy

If you decide that PCPN really doesn't suit your needs, just shut the system down and remove
it from your hard drive. For those of you who are not using MS-DOS 6 ("DELTREE"), removing
the entire BBS and all its sub-directories can be accomplished with KILLDIRS.EXE, a freeware
utility supplied with PCPN. You are free to keep and use this utility whether you register PCPN
or not; it's completely free of charge, and may be freely distributed. Move KILLDIRS.EXE into
your DOS sub-directory, or any other directory in your DOS path, and it will be available to you
at any time. 

KILLDIRS.EXE is simple to use, just type killdirs, followed by the full path you wish to remove.
All sub-directories in this specified path and those contained within it, will be removed. For
example, to delete the BBS (assuming you used the standard setup) you would type the
following command at the DOS prompt:

 KILLDIRS C:\BBS

The two to three week evaluation period during which you test ran PCPN is granted to you
without any financial obligation. We would appreciate it very much if you would drop us a note
stating why you decided against using PCPN, so we may improve it to appeal to a wider
audience.

Updating to a New Version or Release

As INSTALL.EXE is also used during the update processes, a brief mention of those procedures
should be made here. The update process is actually pretty straightforward.

First, it is recommended that you back up your existing BBS files (entire BBS directory, message
section, and the files section if converting from a pre-3.1A version), just in case you run into
any problems. It is not essential to backup any Conferences you carry as they may be
recovered by modem, but if you do have backups you would be able to recover them directly
from diskette (though it is unlikely that an update would damage any Conferences). If you have
changed any help files or menus, back them up as well as they may be overwritten by newer
versions.

Upon receiving your new version of PCPN, run INSTALL.EXE just as you would if you were
starting a brand new board. Be sure to include the path of your system if you originally choose
something other than the default of "C:\BBS". Instead of choosing option "1" this time, choose
option "3". As before, you will be asked for the path of both PKUNZIP.EXE, and your newly
acquired PCPN ZIP files. After that, just follow the instructions as they present themselves.
You'll then only need to insert diskettes as required. Except in a rare circumstance, you will not
be required to enter any System Variables. Once the process is complete, you may reboot your
system.

PCPN updates replace only files that have changed (have an older date than the update
version). If you have made changes to your PCPN files, dating them LATER than the new
program files are dated, the update will NOT update your PCPN. Please contact Technical
Support for assistance.
