ÛÛ» ÛÛ» ÛÛ» ÛÛ» ÛÛ» ÛÛ» ÛÛ»
ÛÛº ÛÛº ÛÛº ÛÛº ÛÛº ÛÛº ÛÛº
ÛÛº Û» ÛÛº ÛÛº Û» ÛÛº ÛÛº ÛÛº ÛÛº
ÛÛºÛÛÛ»ÛÛº ÛÛºÛÛÛ»ÛÛº ÛÛº ÈÛÛ» ÛÛÉ¼
ÈÛÛÛÉÛÛÛÉ¼ ÈÛÛÛÉÛÛÛÉ¼ ÛÛº ÈÛÛÛÛÉ¼
ÈÍÍ¼ÈÍÍ¼ ÈÍÍ¼ÈÍÍ¼ ÈÍ¼ ÈÍÍÍ¼

BBS Documentation
v4.30 Public Beta 1
For the Sysop

Comments and suggestions should be sent to WWIV Software Services.
Your comments and suggestions are welcome. We hope that you find these
documents useful as you use WWIV BBS software.

Table of Contents

Section Title Page
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
1 End-User License Agreement (EULA) ............. 1-1

2 Introduction .................................. 2-1

2.1 Registration Procedures ...................
2.2 Upgrade Information .......................
2.3 Registration Transfers ....................
2.4 Documentation .............................
2.5 Accessories ...............................
2.6 WWIV Software Services ....................
2.7 Historical Developments ...................

3 Quick Start ................................... 3-1

3.1 Quick BBS Setup ...........................
3.1 Quick Multi-Instance Setup ................
3.2 Updating a Current Installation ...........

4 Full Installation ............................. 4-1

4.1 Initialization using INIT.EXE .............

4.1.1 System Information .................
4.1.2 Paths ..............................
4.1.3 Com Port Settings ..................
4.1.4 Auto-Detect Modem ..................
4.1.5 Modem Selection ....................
4.1.6 External Protocols .................
4.1.7 External Editors ...................
4.1.8 Security Levels ....................
4.1.9 Auto-Validation Settings ...........
4.1.10 Archiver Configuration .............
4.1.11 Configuring Networks ...............
4.1.12 Changing Max Subs and Directories ..
4.1.13 Languages Configuration ............
4.1.14 Registration Entry .................
4.1.15 WWIV.INI ...........................

4.2 Directories and Standard Files ............
4.3 Menu System Setup .........................
4.4 Multi-Instance Setup ......................

5 Operating the BBS ............................. 5-1

5.1 Starting the BBS ..........................

5.1.1 Startup Batch File ..................
5.1.2 Command Line Arguments ..............

5.2 Waiting for Caller (WFC) Screen ..........
5.3 Logging On ...............................
5.4 User Online Keys .........................
5.5 Top Screen Information ...................
5.6 Message System ...........................
5.7 Email System .............................
5.8 Transfer System ..........................
5.9 Chains (Door) Setup ......................
5.10 General Files (GFILES) Setup .............
5.11 Menu System ..............................
5.12 Events Management ........................
5.13 Instance Management ......................
5.14 Chatroom Setup ...........................

6 Modem Information and Setup ................... 6-1

7 For New Sysops ................................ 7-1

8 WWIV on the Internet Telnet and PPP ........... 8-1

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

Appendicies

A References .................................... A-1
B Forms ......................................... B-1
C Technical Support and Resources ............... C-1
D Frequently Asked Questions (FAQ) .............. D-1
E Common Protocol Settings ...................... E-1
F Source Code ................................... F-1
G Credits and Thanks ............................ G-1
H Closing Comments .............................. H-1
I Index ......................................... I-1
J WWIV Software Services Operational Policy...... J-1

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

******************************************************
THIS IS A FINAL DOCUMENT AND IS COMPLETE
******************************************************

1. END-USER LICENSE AGREEMENT FOR WWIV SOFTWARE

WWIV v4.30 is distributed as SHAREWARE.

Definition of SHAREWARE: Shareware is a software distribution method that
allows the end user to install, use and conduct a thorough evaluation of
the software for a specified period of time to determine if the software
meets the needs of the user and its fitness for continued use.

1.1 GENERAL. READ CAREFULLY: This End-User License Agreement
(EULA) is a binding legal agreement between you and WWIV Software
Services, LLC (WSS) and applies to WWIV v4.30 which includes all
software and documentation contained in the distribution archives
as provided by WSS (SOFTWARE). WSS prosecutes violators of this
license agreement to the fullest extent of both federal and state
civil and criminal laws and statutes.

1.2 SOFTWARE LICENSE.

IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS EULA, DO
NOT INSTALL OR USE THIS SOFTWARE! YOU ARE BOUND BY, AND INDICATE
YOUR EXPLICIT ACCEPTANCE OF, THE TERMS AND CONDITIONS OF THIS
AGREEMENT UPON FIRST EXECUTION OF INIT.EXE FILE.

THIS SOFTWARE IS PROTECTED BY US COPYRIGHT LAWS AND INTERNATIONAL
COPYRIGHT TREATIES, AS WELL AS INTELLECTUAL PROPERTY LAWS AND
TREATIES.

THIS SOFTWARE IS LICENSED, NOT SOLD.

a. General License Grant. WSS grants to you a personal, non
exclusive license to install one operational copy of the
SOFTWARE. This installation is for the sole purposes of
evaluating the capabilities and features of the SOFTWARE for a
trial period not to exceed sixty (60) days.

b. Termination of License. Your license to use the SOFTWARE
terminates on the sixtieth day following the date of first
installation of the SOFTWARE unless sooner registered. Upon
such termination, you must remove all operational copies of the
SOFTWARE you installed and discontinue all use of the SOFTWARE.

c. Documentation. This EULA grants you, as an individual, a
personal, nonexclusive license to make, use, and make available
for electronic download, an unlimited number of copies of the
documentation included in the distribution archive provided such
copies are not modified in any way and contain the original
copyright information.

d. Storage and Electronic Transfer of Distribution Archives. You
may store and make available for electronic download, in
unmodified form, a copy of the WWIV v4.30 archive as
distributed by WSS containing the original PKZip(r)
Authenticity Verification codes.

e. De-compilation and Reverse Engineering. You agree not to make
any attempts to de-compile, reverse engineer, or disassemble
the executable portions of the SOFTWARE to avoid the
requirement to register, modify copyright displays, or the
operational aspects of the SOFTWARE.

1-1

1.3 LIMITED WARRANTY.

a. WSS warrants that the SOFTWARE will perform as described in the
included documentation for a period of sixty (60) days from the
date of first installation. Any technical support provided by
WSS shall be as described in the included documentation
provided to you in the distribution archive. WSS will make
reasonable efforts to solve any problem not covered in the
included documentation. To the maximum extent allowed by
applicable law, implied warranties on the SOFTWARE, if any, are
limited to sixty (60) days.

b. No other warranties are expressed or implied. To the maximum
extent allowed by applicable law, WSS disclaims all other
warranties and conditions, either express or implied, including
but not limited to, implied warranties, merchantability and/or
fitness for a particular purpose, with regard to the SOFTWARE
and the provision of or failure to provide support. This
limited warranty gives you specific legal rights. You may have
other rights, which vary from jurisdiction to jurisdiction.

1.4 CUSTOMER REMEDIES. Your exclusive remedy shall be to notify WSS
of a suspected failure to meet the specifications of the
LIMITED WARANTY. WSS's entire liability will be replacement of
the SOFTWARE with an updated version if available.

1-2

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

2. Introduction. - Wayne Bell originally wrote WWIV BBS software and
developed it until 1997. In 1998, WWIV was purchased by WWIV Software
Services, LLC (WSS) and is now supported, developed and distributed by
WSS and authorized Source Distribution Sites (SDS). It is the BBS
system of choice for thousands of sysops world-wide who appreciate
having a rock-solid BBS system to rely upon and who like the fact that
it is dynamic and evolving software.

WWIV is available in two basic forms. One version is shareware, which
permits the user to use a fully functional copy of WWIV for a trial
period of 60 days. If the user likes the software, he must register
or terminate its use within the 60-day trial. The other version is
the registered version which includes access to the source code and
license to modify the BBS to suit user needs within the limits of the
Source Code EULA (App. ???) This is a feature not found in any other
BBS and is what makes WWIV so unique.

Beginning with v4.23 it has been possible to "upgrade" the capacity of
the BBS to handle more than two "instances." Multi-instance refers to
the ability of the software to have several instances in use
simultaneously using the same BBS.EXE and accessing the same data
files. This multi-instance ability permits systems to be both
multi-node and multi-line. The software offers many features commonly
found in BBS software selling for many times as much. It also retains
the ability to be easy for a sysop to install and operate. Thus the
combined features of versatility, power, and ease of use make WWIV one
of the most prominent, dynamic, and fastest-growing BBS programs
available.

2.1 Registration Procedures - As stated in the EULA, when registering,
the user is purchasing a license to use WWIV BBS software and to
use the network software indefinitely. WSS retains ownership of
the software itself. Also included with registration is the
(separately licensed) source code to the BBS and selected support-
ing programs. Registration entitles the user to free upgrades to
all releases under the major revision registered. For example, if
a user registered version 4.10, s/he is entitled to free upgrades
to all 4.xx releases. Upgrade fees for major revisions may be
charged and if applicable, will be published well in advance of
major releases. There are three methods of registration are
available:

a. Online Registration: $90.00 (US) for the DOS platform of
the BBS Software. Pricing for other platforms will be
published as they are released.
/////////////////////////////////////////////////////////
Online registration WILL BE
available at http://wss.wwiv.com/register.htm.
/////////////////////////////////////////////////////////
Registration numbers and passcodes are issued at the time
of purchase.

b. Normal Mail-In Registration: $80.00 (US) for the DOS
platform of the BBS Software. Pricing for other platforms
will be published as they are released.

c. Registration Payment Plan: WSS offers a payment plan for
the purchase of DOS platform BBS registrations. The
payment plan consists of three payments of $20.00 (US),
with a final payment of $30.00 (US). Each payment extends
the users trial period by sixty days. ALL PAYMENTS ARE
NON REFUNDABLE. If a user fails to make scheduled payments
on time or to complete the payment plan within 240 days (8
months), the account will be in default, the payment plan
will be terminated and no refund will be issued. The
registration number and passcode are not issued nor is the
user registered until all payments have been made. WSS
will notify network administrators of payments received
and extensions of the trial period at the request of the
user.

2-1

WSS processes Mail-In registrations and accessory product orders
once a week, normally on Saturdays. Disk mailers with the
products ordered, registration papers, and letters are normally
mailed the following Monday. Thus, if you send in an order, allow
a few days for the post office to do its work and then assess the
schedule above to determine when you should get a response. If you
have not gotten a response by one week after that date, please
contact us and ask about the status of your order. When inquiring
about the status of an order, please give your real name and
address at the time of registration as our files are indexed and
verified using this information.

2.2 Upgrade Information - The unregistered shareware version allows the
user to run a single instance of the BBS software and registered
versions allow two instances. At the time of registration or at a
later date, upgrades may be purchased to allow the operation of
more instances. The upgrade order form is in App. ??? and a text
version is in the distribution archive. Upgrade pricing is as
follows:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÒÄÄÄÄÄÄÂÄÄÄÄÄÄÂÄÄÄÄÄÄÂÄÄÄÄÄÄÂÄÄÄÄÄÄ¿
³ Upgrade From º 1/2 ³ 4 ³ 8 ³ 16 ³ 32 ³
ÆÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÎÍÍÍÍÍÍØÍÍÍÍÍÍØÍÍÍÍÍÍØÍÍÍÍÍÍØÍÍÍÍÍÍµ
³ Upgrade to 4 º $20 ³ ³ ³ ³ ³
³ Upgrade to 8 º $45 ³ $25 ³ ³ ³ ³
³ Upgrade to 16 º $80 ³ $60 ³ $35 ³ ³ ³
³ Upgrade to 32 º $120 ³ $100 ³ $75 ³ $45 ³ ³
³ Unlimited º $220 ³ $200 ³ $175 ³ $145 ³ $100 ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÐÄÄÄÄÄÄÁÄÄÄÄÄÄÁÄÄÄÄÄÄÁÄÄÄÄÄÄÁÄÄÄÄÄÄÙ

2.3 Registration Transfers - Some registered users may, at some point,
decide to terminate their use of WWIV and desire to transfer their
registration to someone else. There is a specific process to be
followed to legally transfer the registration number.
REGISTRATIONS MAY ONLY BE TRANSFERRED BY WWIV Software Services.
Transfer requests must include Old Owner and New Owner Transfer
forms; a new registration form completed by the new owner and a
check or money order for $25.00 (US). It is up to the parties
involved as to who pays the transfer fee. Any sales price beyond
the transfer fee are the concern of the parties involved and are
not the responsibility or concern of WSS. The necessary forms for
transfers are contained in App. ??? Transfers will not be
processed until all completed forms and fees are received. All
entitlements to source code and SDS Access for the Old Owner are
terminated upon the proper execution of the transfer.

2-2

2.4 Documentation - The documentation for WWIV is available in several
categories and formats. All are available on ftp.wwiv.com/wwiv/docs
and will be included with the CDROM distribution of WWIV when
available. It is separated into the following functional areas by
format:

430SYSTX.ZIP- v4.30 Sysop Docs in ASCII text
430SYSAR.ZIP- v4.30 Sysop Docs in Adobe Acrobat Reader format
430SYSMS.ZIP- v4.30 Sysop Docs in MS-Word format
430SYSHT.ZIP- v4.30 Sysop Docs in HTML format

430USRTX.ZIP- v4.30 User Docs in ASCII text
430USRAR.ZIP- v4.30 User Docs in Adobe Acrobat Reader format
430USRMS.ZIP- v4.30 User Docs in MS-Word format
430USRHT.ZIP- v4.30 User Docs in HTML format

2.6 Accessories - At present, WSS develops and distributes the following
add-on accessories:

NET37 (Proprietary Networking Package)
COST: Free with WWIV v4.30 registration
$25 (US) for stand-alone use
DISTRIBUTION: Pre-compiled only.
DESCRIPTION: Proprietary networking software for WWIV-based
networks. Provides password secured two-way
transmission of email, messages, and files.
Dean Nash, Lead Programmer

NetUp (Network Updater)
COST: $100
DISTRIBUTION: Restricted
DESCRIPTION: NetUp sends and receives RSA encrypted data file
updates to all systems in the network and designated
network officials. Operates only on the network for
which it is purchased only.
Dean Nash, Lead Programmer.

NGTrans (Internet Newsgroup Import / Export)
COST: $50.00
1YR LEASE: $15.00
DISTRIBUTION: Purchase or Lease, pre-compiled only
DESCRIPTION: NGTrans is an Internet newsgroup import / export
utility. Written in C, NGTrans was originally
developed by Wayne Bell.
Chuck Bensinger, Lead Programmer.

WWIVedit (Full-Screen Editor for WWIV)
COST: $20.00
DISTRIBUTION: Shareware, pre-compiled only
DESCRIPTION: WWIVedit is a full-featured full-screen editor for
WWIV. It is written in PASCAL and was originally
developed by Adam Caldwell. WWIVedit is now owned,
developed, and distributed by WSS.
Authur Johnston, Lead Programmer.
(All previous registrations honored)

//////////////// NOT CURRENTLY AVAILABLE////////////////////
// WWIVchat (WWIV ChatRoom)
// COST: $25.00
// DISTRIBUTION: Shareware, pre-compiled only
// DESCRIPTION: WWIVchat is a full-featured chat room for WWIV.
// Fully configurable with CB style chat or windowed
// rooms. Specificly designed for multi-node systems.
// Original author: Joe Barbara,
// Dean Nash, Lead Programmer.

2-3

2.6 WWIV Software Services, LLC - In 1998, WWIV Software Services, LLC
was formed as a corporate entity to continue development, support
and distribution of WWIV and associated software. We established
a set of core beliefs upon which we conduct business:

The sole reason for our existence is the registered user.

An open, responsive line of communication with users is essential.

Registered sysops deserve fast, efficient service.

Trial users deserve the highest level of support during their trial
period.

Development requires end user input; listen to it.

Our mission to support registered users never ends.

You can reach WWIV Software Services, LLC via the following methods:

* Send E-mail to 1@50 on most major WWIV-based networks.
* Send E-mail to wss@wwiv.com via the Internet
* Point your web browser to http://wss.wwiv.com
* Call "The Mountain Empire BBS" Home of WWIV at (423) 477-4015
* Send regular US Mail to:

WWIV Software Services, LLC
P.O. Box 4468
Johnson City, Tennessee 37602

2.8 Historical Data - WWIV was originally written by Wayne Bell. Wayne
began work on WWIV when he was a teenager. It was first written
in BASIC on a TRS-80. Wayne soon recognized the limitations of the
BASIC language for BBS operations and he re-wrote the program in
PASCAL. At that time, the BBS program could be registered by
donations of $25. The last PASCAL version was v3.21d. Many modern
day PASCAL BBS systems are based wholly or in part upon this early
version of WWIV. All v4.xx releases of WWIV have been written in C.
With this language, WWIV has developed into a multi-featured BBS
system supporting one of the most trouble-free hobbyist networks
in the world. WWIVnet, the network founded by Wayne, began as a
local based network in Los Angeles, California with 25 charter
members. In the early 1990's, the network grew to over 1,500
members located around the world. Because many sysops wanted to
run their own networks for various reasons, Wayne added a feature
which allowed the BBS system to participate in multiple WWIV-based
networks and developed the networking software to support such
multiple network usage. At the peak, there were some 100 WWIV-
based networks offering a range of topics and supporting a
multitude of various interests.
In January of 1998, Dean Nash purchased WWIV and WWIV Software
Services from Wayne Bell. WSS was reformed as a Tennessee Limited
Liability Company with a full corporate posture. Craig Dooley was
appointed Support Coordinator and supervises the Support Board
System and Source Distribution Sites.
The documentation for WWIV has also developed overtime. It began
as a short 3-page document written by Wayne. Later, with v4.10,
William Daystrom wrote a complete set of documentation for use with
WWIV. Beginning with v4.20, Filo added additional comments to some
of the documentation files written by Will and completely rewrote
others. The documentation was again completely rewritten by Filo
for v4.23 and updated for the v4.24a release.
With the release of v4.30, the documentation was updated to reflect
all code changes and was converted to several different formats for
your convenience.

2-4
******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

3. Quick Start:

3.1 Setting up WWIV for the first time is very simple and should
take only a matter of minutes. (NOTE: In order for INIT to
function properly and install all files, PKUNZIP.EXE must be in
the default directory or somewhere in your PATH.) The first
thing to do is to create a directory for the BBS. This should
be a directory created off of the root directory of any drive.
To create such a directory, you can use the DOS MD(make
directory) command. Most people name their main bbs directory
as either WWIV or BBS.

Step 1: Make the BBS Directory

cd\ (change directory) slash gets you to the root
directory of the drive.
md wwiv creates the WWIV directory.

Step 2: Unzip the Archive. The next step is to unzip the bbs files
into the WWIV directory that you just created. Assuming
that your WWIVxxx.ZIP file is on drive "A", the
appropriate steps would be

cd\WWIV (change directory) to WWIV
pkunzip a:\wwiv4xx.zip this will unzip the archive
into the current directory
(ie the WWIV directory)

You must have PkZip (tm) somewhere in your path in order
to use the PkZip commands. All files distributed by WSS
are compressed using PKzip and contain PKware's Authenticity
Verification. If you do not see a -AV by each file as they
are decompressed, or the lines:

Authenticity Verified:
WWIV Software Services ????????

the archive is not authentic or has been modified in some
way. DO NOT USE THESE FILES! Obtain a fresh archive from
ftp.wwiv.com/wss or an authorized Support Board.

Files included: You should check the FILES.LST contained
with the archive to determine the complete files list
shipped with the current version. If any files are missing,
your BBS may not run properly or perhaps not run at all.
To view the FILES.LST, you can use the DOS type command:

type files.lst

Step 3: Run the initialization routine. If all files are present,
your next step is to run the INSTALL.BAT file.
The batch file will type out a couple of messages
and then run the INIT program. The first screen you will
see is:

[ insert INIT screen shot ]

You should answer Y. INIT will then proceed to install the
necessary files and directories for WWIV to run. You should
note that all directories will be made as sub-directories
of the current working directory, so be SURE that your
current directory is the one you want to use as your main
WWIV directory, when you first run INIT.

3-1

INIT.EXE will automatically create some directories for you on the
hard drive and put certain files in some of these directories.
Although each version of WWIV may have slightly different files,
you should expect to see something like this as the directory tree
that is created:

A number of files will be placed in DATA when you finish the
INIT program, and a number of *.msg files will be created in
or moved to the GFILES directory. These files may be edited
to suit your preferences. Editing those files is discussed
later in the documentation(App. ???).

Step 4: Configure the modem. The first time that you run INIT, the
program will attempt to detect your modem type and configure it
for use with the BBS. If the modem type that is selected does not
work well, you can select the SELECT MODEM TYPE from the menu and
choose the one that most closely represents your own modem. More
details about modem selection and modem use is in the section of
the documentation dealing with modems. (App. ???)

Step 5: Configure the system. After your modem has been configured
there are certain items of information requested by INIT that you
will definitely want to fill in immediately; other items may be
left at the default values until you are more familiar with WWIV.

You will be told that your system password has defaulted to SYSOP.
The system password is a password that should only be known by the
primary system operator. The system password is required whenever
you see the "SY:" prompt. You will need to enter the system
password when you run INIT, or run more sensitive sysop functions
from the BBS. After you are told what the system password is, you
will be given the "SY:" prompt, and you will need to enter the
system password, SYSOP.

After correctly entering the system password, you will be in the
Initialization/Configuration program. You will presented with
menu options that are described later in order. If you don't fully
understand some of the options, just leave them as they are, and
their use will probably become clear after playing with the
system a bit, or reading the WWIV sysop manual.

For a fast setup, change the following items in Option 1 to fit
your system:

System PW (Should be changed IMMEDIATELY)
System Name (the name you want for your BBS)
Sysop Name (what you want to be called on the BBS)

The rest of the settings can be altered later after you learn more
about how WWIV operates.

Step 6: You must now edit create a batch file with which to run
the BBS. WWIVBAT.SAM is an example which contains several
command lines for FOSSIL Drivers and the proper sequence for
loading the BBS. It must be renamed with an extention of .BAT
to function. You must install a FOSSIL driver (i.e. X00,
ADF, WinFossil) for v4.30 to work properly. More information on
FOSSIL Dirvers is contained in App. ???.

Step 7: Establishing your user account. You must now load the
BBS using the batch file you just created and log on as NEW to
establish your user account. Once the Waiting for Caller (WFC)
screen comes up, hit the space bar. You will be presenting with
the Logon? prompt. Hit Y. Answer the following questions as they
are posed to you. When you have finished logging on, you should
hit the F1 key to edit your user account while online. Since you
want all powers and features, enter 255 as your SL and DSL. For
ARS and DARS, enter the letters A through P or just hold the space
bar down. If restrictions are shown remove them by pressing the
letter of the restriction. For exemptions, enter 31. When you
exit the online user edit function, you should see your time
increase dramatically. You are now a sysop with an operating BBS.
Have a friend call from his computer to test it out.

Summary: There is much more to learn, but you are better off
learning through experimenting with the BBS reading further.
Thoroughly reading the documentation is recommended within the
first 60 days of operation to ensure you can make an informed
choice as to whether you wish to continue using WWIV as your BBS
software.

3.2 Multi-Instance Quick Start: Beginning with v4.23 it is possible to
run more than one instance of WWIV. This may be done in situations
where you are using multitasking software and/or a LAN. This
permits more than one user to be using an "instance" of the BBS
at the same time. In order to utilize more than one instance, you
must do the following for EACH instance (other than the first).

Step 1: Run INIT.EXE for the instance. Run INIT using the following
command:

INIT ,2

which enables you to create the "second instance". If the second
instance is only for local keyboard use (ie no modem attached),
there are no changes required in INIT. INIT will automaticlly
create the subdirectory TEMP2 off the main BBS directory and
set that as the instance temporary and batch direcotry. You may
wish to check to ensure the com port for the instance is set to
0 for local instances under option 3.

If the second instance is attached to a modem, then it will be
necessary to define the COM port for that modem and select a
modem type for it.

Step 2: Configure instance batch file

For a local logon, you need a batchfile that can be used to logon
to the second instance. This will be invoked by your multi-
tasking software in a multi-tasking environment or may be used
over a LAN. The batchfile should look something like this:

REM --- BBS Batch file for instance 2
@echo off
REM --- Goto BBS drive and directory
c:
cd\WWIV
REM --- Set the instance environment variable
SET WWIV_INSTANCE=2
REM --- Run the BBS:
REM --- -m = ignore modem
REM --- -i2 = designates instance to run on
bbs -m -i2

If the second instance is attached to a modem and you wish to use
the modem on that instance, you should make a copy of WWIVBAT.SAM
and edit the file as described previously for this instance. The
-m parameter used above is only for local logons. The i2 is
necessary to tell the BBS that it is instance 2 that is being run.

You will need to install SHARE.EXE or be using some form of "share"
via your network software if you are on a LAN in order to have
multi-instance capability. If you are using Windows 95/8 or OS/2
as your multi-tasking software you will NOT need share. Additional
information for multi-tasking may be found in App. ???.

3.3 Updating a Current Installation. If you are upgrading from a
previous version of WWIV, the process has been greatly simplified
for you using an included batch file named UPGRADE.ME. You may be
required to edit the file if you have a non-standard setup.

It is highly recommended that you make a backup of your current
setup since nothing is infallible. We have tested the upgrade
process, however, it is possible that individual configurations
could fail.

The batch file renames WWIV.INI to WWIVINI.OLD and MODEMS.MDM to
MDMSMDM.OLD as you may require entries contained in those files.
As the final step in the process, INIT is run to upgrade and
convert some data files to the current format.

You may choose to print the file out and then enter the commands
manually. The file is well commented so this should be a
rather simple task.

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

4 FULL INSTALLATION

4.1 Initialization using INIT.EXE. Once INIT is run, and after you
have correctly entered the system password, you will be presented
with a menu listing fifteen options as shown here:

[insert INIT screen shot ]

This section describes each of above options and how to edit and
modify the configuration of your BBS.

4.1.1 System Information

4.1.1a System password. The system password defaults to SYSOP,
but you should be sure to change it to something else, hopefully
something that other people will have a difficult time guessing.
Selecting your own personalized system password prevents other
people from gaining unauthorized access to your BBS. When you
type the password it will show on screen as XXXXX.

Note that with the release of v4.24, an added security measure
has been added that allows you to enter a system password on the
command line when you start up your bbs. See the setup section
for details.

4.1.1b System name. This should be set to the name of your BBS,
but if it isn't set correctly, nothing bad will happen. You
should give considerable thought to selecting a name for your BBS.
To avoid duplication of other names that might be in use on other
BBSes, you are encouraged to check the network listings for the
various WWIV based systems and perhaps FidoNet systems as well.

4.1.1c System phone. This should be set to the phone number of
your BBS. This isn't critical information UNLESS your board is a
member of a WWIV network.

4.1.1d Closed System. If your system will not be allowing users
to dial up and establish accounts on your system, set this to Yes.
If someone does dial up a closed system, they will be presented
with a short message telling them it is a closed system and does
not accept new users.

4.1.1e Newuser PW. This is the password users will have to enter
in order to log on as new users. If there is no newuser password,
anyone may log on as a new user. This should only be used if you
wish to operate a "private" system where you only allow people you
know to log on.

4.1.1f Newuser restrict. This sets the restrictions that all new
users are given. This should probably be left as-is until you fully
understand what the restrictions are used for. See "Restrictions"
for more details. The default restriction of M means that any
messages that the user posts, will not be seen by anyone else until
you have validated the messages.

4.1.1g Newuser SL. This sets the security level that all new
users are given. The default is 10. This should also be left alone
until you understand what the different security levels do, and
even then, most sysops will probably want to leave this set to 10.

4.1.1h Newuser DSL. This sets the download security level that
all new users are given. The default is zero. New users are
severely limited in what they can do on the BBS until you have
'validated' them which usually involves an increase in their SL
and DSL as well as possibly the assignment of some Access
Restrictions (AR's) and Download Access Restrictions (DAR's).

4.1.1i Newuser gold. WWIV keeps track of an amount of "gold" for
use in online games, if needed. This sets the default amount new
users are given. The regular distribution version of WWIV does not
use gold for anything. If you have registered your BBS and obtained
the source code, modifications are available which can allow you to
use gold, for example, to regulate downloads or game use by
requiring that the caller "earn" a certain amount of gold by
posting.

4.1.1j Sysop name. At a few points in the BBS, the system will
need to print out the name of the system operator. This is where
you can set what that name will be. You may use your real name,
but many sysops use "handles" or aliases instead. This is totally
up to you.

4.1.1k Sysop low time. The sysop low time and sysop high time
set the time limits that the sysop is available to be chatted with.
If, for example, you don't want people to be able to request a chat
between 11pm and 7am, then your chat hours would be 7am to 11pm.
The low time (when chat hours begin) would then be 7am, and the
high time (when chat hours end) would be 11pm. You enter the time
in the standard 24-hour format, where 7am is 07:00 and 11pm is
23:00.

Normally, the scroll lock key determines when the sysop is
available for chat. If sysop hours are defined, the system ignores
the status of scroll lock during the hours the sysop is supposed to
be unavailable. In other words, if you followed the above example
and chose available hours to be from 7am to 11pm, callers will not
be able to request chats with you from 11pm to 7am, regardless of
the scroll lock setting.

During the sysop hours (7am to 11pm), scroll lock IS monitored,
and will determine whether or not the sysop is available for chat.
If the scroll lock is on, callers will be told you are available,
and if they request a chat, a chat alarm will be sounded (unless
you have turned the beep off. (See page ??? for details).

4.1.1l Up/Download ratio. Many sysops want to have up/download
ratio requirements. This allows you to set them. A caller's ratio
is defined to be the number of kilobytes (k) (1024 bytes) of files
uploaded divided by the number of k of files downloaded. So, if you
want a caller to be able to download 5k for every 1k uploaded, the
required ratio would then be 1/5=0.2, so you would set the ratio
required to be 0.200. This way, when a caller has violated the
ratio (downloaded over five times what he/she uploaded), the caller
would not be allowed to download again until the caller uploaded
enough data to clear the ratio.

4.1.1m Post/Call ratio. Similar to the Up/Download ratio, this
restricts users from downloading if they do not meet the minimum
ratio established.

4.1.1n Max waiting. Each caller may have a number of pieces of
mail waiting. This allows you to set the maximum number of pieces
of mail a caller can have waiting. NOTE: The sysop (SL=255) can
have 5 times this number of mail waiting. So, if, for normal
callers, 20 is the maximum, then 100 would be the maximum for
the sysop. If the sysop has more than 254 pieces of email waiting,
only the first 254 will show up at the mail prompt, but the rest
will not be deleted. After the sysop reads some email, the
software will make more of the waiting email available, but will
still only show the first 254 pieces at the mail prompt.

4.1.1o Max users. The BBS requires you set the maximum number of
users that can be on the system. This defaults to 500, but you may
increase or decrease it. The absolute maximum is 32,767, but 2,000
is probably about the limit for performance reasons (ie, the
system slows down the more users you have).

4.1.1p Caller number. If you have converted to WWIV v4 from
another BBS (possibly an earlier version of WWIV), you may set the
current caller number with this option. This counter is increased
by one each time the system receives a non-network call unless the
remote caller is the sysop.

4.1.1q Days Active. Again, if you converted from another BBS,
you can set the number of days your BBS has been active here.
2.3.3 Option 3. Paths (messages, gfiles, data, etc)

4.1.2 Paths. If you have more than one hard disk, you may wish to
split up the BBS files among your hard disks, in order to
better use the space. Using this option, you may change
the directories that the BBS looks to for certain things.
Please note that changing any of the options here will
only change where the BBS looks for the data; IT WILL NOT
ACTUALLY MOVE ANY FILES OR DIRECTORIES. The following
rules should be observed when assigning or changing
directories:

1. Never use the root directory of any drive to store
BBS files; the root directory can only hold a
fixed number of files, while any sub-directories
may hold an unlimited number of files in them.

2. Always have a backslash on the end of the
path/directory name. The software will normally
add this backslash for you.

3. The directory may be specified relative to the
main BBS directory, or as a full pathname. In
other words, "msgs\" is recognized as a
sub-directory of the main BBS dir. In most
instances, however, you won't need to change the
default directories. If you choose to have
directories located on another drive, remember to
include a drive letter in the pathname.

4.1.2a Messages Directory. Information regarding all e-mail
and posts is stored here.

4.1.2b GFILES Directory. The Directory where the BBS text
files are stored. These files can be read by users while they
are on line. If you have any GFILE sections (described later),
the BBS will create sub-directories of the GFILES directory,
ie "gfiles\section1\". See[????] for information on G-Files.

4.1.2c Data Directory. Data files used by the BBS are
stored here.

4.1.2d Dloads Directory. This directory is used to set the
default directory for new file sections.

4.1.2e Temp Directory. This area is used to temporarily
store files for the BBS. Because this area is "cleared" each
time that a user logs off, you should not store anything in
this directory. In a multi-instance setup you will need a
separate temporary directory for each instance that you have.
The INIT program will create a temporary directory for
each instance the first time it is run for that
instance. The default directory name is TEMP<inst num>.
You may change this, but remember to create the
directory as INIT will not automatically do this for
you.
Please note also that any files found in the temporary
directory when the BBS is run will be DELETED. If you
point the temporary directory to your root directory, or
the BBS directory, ALL THE FILES IN THAT DIRECTORY WILL
BE ERASED. Therefore, have the temporary directory be one
that doesn't contain any files you care about.

4.1.2f Batch Directory. This directory is used to
temporarily store files that are batch uploaded (defaults
to the defined Temporary directory) Make sure this
directory has adequate disk space for files being batch
uploaded; at least 5 megs recommended). After batch
uploads are completed, the BBS will automatically move
the files into the appropriate drive and directory and
delete the original files.

You may freely change DLOADS, TEMP and BATCH to whatever you
want without hurting anything. HOWEVER, the TEMP and BATCH
directories MUST exist. You may choose to have the temporary
directory exist as a ramdisk. If the TEMP directory is a
sub-directory of a ramdisk, MAKE SURE that the directory is
created BEFORE the BBS is run. In other words, run the BBS in
a batch file that first creates the temp directory.

The others (messages, gfiles, data), however, will have files
in them that the BBS needs to find in the appropriate directories.
If you change the Messages, GFILES, or DATA directories,
you must:

1. Go to DOS and create the new directory.
2. Move all files from the old to the new directory.
3. You should then probably erase the old files and old
directory, to ensure you aren't confused by multiple
copies later on.
4. You will then need to create subdirectories, of the
new directories, with THE SAME NAME, and copy all files from
the old subdirectories to the new ones.

4.1.3 Com port info (port, IRQ, base address, etc

4.1.3a Com Port. This sets the com port number that your modem
is connected to. If this is set to zero, the result is that the
BBS will not use a modem at all (same as /m parameter). Initially,
the com port is identified and set with the auto-detect features
of the INIT program.

4.1.3b Interrupt. This allows you to manually change the interrupt used
by the BBS. You will probably not need to modify this.

4.1.3c Base address. This sets the com base address used by the
BBS, and is dependent upon the com port number. It is set automatically
when you change the com port option, and you will not normally need
to change this setting.

4.1.3d Slow UART. The INIT program automatically detects the
presence of the 16550 buffered UART chip for the com port listed.
"Y" indicates INIT has detected a 'slower' UART chip and
the "Unbuffered UART on COMx" message will be displayed.

4.1.4 Auto-Detect Modem. INIT will scan the available com
ports and select the proper configuration for some more prevelent
modem types on first run. This may or may not work with your
modem. If your modem type is not detected, a generic
definition may be selected. If you are not satisfied with the
auto detect choice, select a definition manually.

4.1.5 Select modem type. This option allows the manual selection of
the modem type to be used by the BBS. Modem definitions are listed in
alphabetical order. Use the UP/DOWN arrows, and PgUp/PgDn keys to
scroll to the modem type that most closely describes your modem;
press enter, and a new MODEM.DAT file will be compiled and placed in
the DATA directory. It is this file that contains all modem
information the BBS needs. MODEM.DAT is a data type file that
cannot be altered or changed. The source for the MODEM.DAT file is
a configurable text file called MODEMS.MDM. MODEMS.MDM is a
compilation of known, working modem setups that is located in
the DATA subdirectory following installation. It is very unlikely
that you ever need to change the data stored in MODEM.DAT, but if it
ever became necessary(changing a result code or such), the place to
do so is in MODEMS.MDM, then re-select that modem type and a new
MODEM.DAT file will be compiled. For more information on modems and
modem setup, consult Chapter 5.

4.1.6 External Protocols. Using this option, you will be able to
insert, delete, and modify external protocols for the BBS to use.
A full range of protocol settings are contained in Chapter 8.
Note that these settings are for up/downloads on the BBS
itself, NOT the network software.

4.1.7 External Editors. A full screen editor (FSED) allows you and
your callers (with ANSI) to write email and posts using an editor that
is not restricted to the line-by-line approach used by WWIV's built
in text editor. Some editors allow the use of function and arrow
keys to move the cursor about the screen, in much the same manner
as a regular word processor. Full screen editors tend to be awkward
for callers to use, however, as while the sysop might use the arrow
keys to move the cursor, the caller must almost always use control-
key combinations to achieve the same thing. Still, there are some
great advantages to using a full screen editor, especially from
the sysop's point of view, and so provision is made in WWIV for their
use. The full screen editor must do all I/O through DOS calls.

WWIVedit, another WSS product, is probably the most preferred
FSED and is written specifically for use on WWIV BBS systems.
WWIVedit is self installing and requires very little
intervention during installation. WWIVedit is available on all
Support Boards and on the Internet FTP site.

The following are Command lines for other full screen editors.
You should read the documentation that is distributed with the
editor in depth and adjust these commands to your liking:

Description : FSED
Filename to run remotely
fsed +dosansi.cfg +wordstar.cfg -w%2 -h%3 -l%4 %1
Filename to run locally
fsed +console.cfg %1

Description : FEdit 1.1
Filename to run remotely
FEDIT %1 %2 %3 %4
Filename to run locally
FEDIT %1 %2 %3 %4 %5

4.1.8 Security Levels. For each security level (SL) there is a
set of data that determine what a caller with this SL may do.
These levels are numbered 0 through 255. You may change the
default settings to suit your particular situation but most find
the default setup satisfactory. If you should desire to change the
settings, use {,},[,], to scan through until you find an SL you want
to change. Then, hit enter to edit the data. You can then alter:

4.1.8a Security level. Changing this field moves you to the
entered security level. The other data on the screen is
appropriately changed. Any data changed for the previous SL
is saved.

4.1.8b Time per day. This gives the time, in minutes, that a
caller with that SL is able to be logged on the system per day,
regardless of the number of calls.

4.1.8c Time per logon. This gives the time, in minutes, that
a caller with that SL is able to be logged on to the system per
call. Normally, the time per day is 2.5 times the time per logon.
Normally, the time allowed on is limited by the time per logon,
but after the second call that day, the time per day may cut down
the total amount of time on. Of course, the time allowed on may
be affected by uploads, chat time, and extra time allowed by the
sysop.

4.1.8d Messages read. This sets the number of messages that
can be read (per call) by a caller with that SL.

4.1.8e Emails per day. This sets the maximum number of pieces
of mail that a caller with that SL can send, per day.

NOTE: Email excludes feedback. All callers are allowed to send up
to five pieces of feedback per day.

4.1.8f Posts per day. This sets the maximum number of posts a
caller with that SL can post per day.

4.1.8g Post anony. If set, this means that a caller can post a
message anonymously on any message base.

4.1.8h Email anony. If set, this means that a caller can send
anonymous e-mail on the system. No network emails may be sent
anonymously.

4.1.8i Read anony posts. If set, a caller with this SL can
read the names on anonymous posts.

4.1.8j Read anony email. If set, a caller with this SL can
read the names on anonymous e-mail.

4.1.8k Limited co-sysop. If set, a caller with this SL can
validate and delete messages from any caller. Normally, callers
can only delete messages they themselves have written.

4.1.8l Co-sysop. If set, a caller with this SL has access to
all co-sysop functions.

4.1.9 Auto-Validation Configuration. The sysop can set the Alt-F
keys (Alt-F1 through Alt-F10) to set certain data for a caller.
This function allows you to change that data. You may set the SL,
Download Security Level (DSL), Access Restriction (AR),
Download Access Restriction(DAR), and System Restrictions. Then,
when a caller is on-line, you may press any ALT-function key
combination to immediately change that caller's access levels and
restrictions. This may be useful for validating a user that is
online. You can, for example, just hit Alt-F1, and if you have
that configured to give the caller standard access, the caller
will immediately receive the configured access. It all happens
very quickly, and there is no immediate indication on the caller's
side that anything has happened, save perhaps a dramatic increase
in the time-left display. The Alt-F10 key combination is used if
you have configured the optional Simple Auto-Sysop Validation ASV.
The first four (Alt+F1-F4) settings are used in the optional
Advanced ASV system. See Section 4.1.15 for more information on ASV.

CAUTION: If you are logged-on locally, and hit an Alt-key combination,
your stats will be altered as well. This would do no permanent damage,
but it will cause an annoyance as you have to reset your own access
levels again.

4.1.10 Archiver Configuration. You may configure up to 15
supporting archiver formats. ZIP, ARJ, PAK, LHA, and RAR are
pre-configured on first installation. The first archiver
record is the default archive on the system. The first four
are also copied into the pre 4.30 archiver structure for
backward compatability with other supporting programs. For
most users, you will not need to adjust these settings.
The standard DOS replaceable parameters %1 and %2 are used for
source and destination filenames. To navigate through the archiver
records, use the bracket keys [ and ]. To edit a record, hit enter.

CAUTION: It is *HIGHLY* recommended that you edit the command
lines of all archivers and specify a complete path and
filename to the program to run (i.e. c:\bat\pkzip.exe -a %1 %2).
It is possible, though very unlikely, that a mischievious or
malicious user could upload a batch file or compiled
executable with an archiver name that may do harm to your
system if run.

4.1.10a Archiver Name. This is a recognizeable name you
can assign to the archive type.

4.1.10b Archive Extension. This is the three letter
extension applied to files of this particular type. This
setting is how the BBS identifies archives.

4.1.10c Archive List. This command lists the archive to
the screen without actually extracting the files.

4.1.10d Archive Extract. This command extracts the
archive to the temporary directory for the current
instance.

4.1.10e Archive Add. This command adds a file to an
archive.

4.1.10f Archive Delete. This command deletes a specified
file or list of files from the current archive.

4.1.10g Archive Comment. This command applies a BBS
comment to the selected archive. %K substitutes
GFILES\COMMENT.TXT for commenting.

4.1.10h Archive Test. This command tests the selected
archive for validity and integrity.

4.1.11 Network Configuration. If you have installed the
NETxx.ZIP archive in the BBS directory, this option will allow
configuration of networks. The prompts are self explanatory.
For details on network configuration, see NETxx.DOC in the
distribution archive.

The only setting that effect the BBS itself is the Network
Type. This setting tells the BBS and the network software how
to handle the particular network. There are currently three network
types: WWIV, Fido, and Internet.

4.1.11a WWIV network types. This type is processed
normally and entirely by the NETxx package.

4.1.11b Fido and Internet network types. These types implement
internal hooks for pre-processors and tossers such as WWIVtoss
and the PPP Project to convert native type messages and email to
WWIV format and vice versa.

4.1.12 Change Max Subboards/Directories. This is a system tuning
parameter. These items require runtime memory thus the higher
they are set, the less memory is available when shelling to
DOS or running external programs. You should NOT select more than
you think that you will actually need, for more memory is required
as the number is increased. This setting may be modified
later if you require more subs or directories.

4.1.13 Language Configuration. WWIV has the ability to offer
users multiple languages through the use of string files. To
configure languages, all that is required is to define the
directory where the language string and menu files are
located. See Chapter 9 for more information.

4.1.14 Registration Information. When you register WWIV,
this is where you will enter your registration number,
passcode, name and address information. A registration
passcode is required for v4.30 for the BBS to operate beyond
the 60 day trial period. Previously registered sysops will be
issued a passcode at no charge at http://wss.wwiv.com/passcode.htm.

The name field is required. Enter the same name you used to
register the software. The address fields are optional and are for
your information only. You may be required to provide the
address information at the time you registered at some point
in the future.

4.2 WWIV.INI. The INI or Initialization file is probably the
most enigmatic part of WWIV. It provides quick access to the core
of configurable options and allows a quite diverse array of system
tuning parameters. The file is well commented and should be fairly
easy to adjust to your particular situation. The default file is
setup for a generic BBS and should be sufficient for most
applications.

4.3 Directories and Standard Files. INIT creates the
following directory tree on first run:

A general description of each directory and the files contained therein
is covered here:

4.3.1 DATA. This directory contains the core data files
for the BBS. User records, subboard and transfer
directory data, archiver, color, and menu configurations, are
all stored here.

NOTE: If you don't backup your data regularly, you should start
now with this directory. Disk or data errors here will devastate
your BBS and you will find yourself starting over from scratch.

The subdirectories REGIONS and ZIP_CITY contain area code
and zip code information for deriving locational
information. Regular updates to these files are on the
WSS web site and Support Boards.

4.3.2 DLOADS. This is the base directory for files that
you will make available to your users. You may choose to
store a majority of your files on other drives or
partitions. It is recommended that you *DO NOT* move the
SYSOP subdirectory. This is the directory where files
that only you have access to are stored. You may also
have set options that force all uploaded files into this
directory.

4.3.3 GFILES. This is the "General Files" directory.
Basic menu and text files are stored here. Subdirectories
are created here when GFILE sections are added. You will
need to move the text files you want your users to have
access to via the GFILES section there.

New to v4.30 are configurable menu sets. The subdirectory
MENUS contains subdirectories consisting of complete Menu
Sets and a single file named DESCRIPT.ION. This should be the
only file in MENUS and is NOT editable. The subdirectory
MENUS\WWIV contains the default WWIV Menu Set. See
Section 4.7 for information on Menu Sets.

4.3.4 MSGS. This is where all messages and email is
stored. As with your DATA directory, these files should be
backed up regularly.

4.3.5 TEMP<inst>. As described earlier, the TEMP
directories are used to store runtime and working files.
These directories are purged at logoff.

4.4 Menu System Setup. [???]

4.5 Multi-Instance Setup. Many have wondered why WWIV is
called "multi-instance" instead of multi-line or multi-node.
The reason is simple; it is both multi-line and multi-node
and we wanted a way to convey this. WWIV uses a single USER.LST
that can be accessed simultaneously by instances that may be on a
Local Area Network, a single machine that is multi-tasking, or
from remote locations via modems over multiple phone lines.
Because WWIV literature has always referred to BBSes on WWIV-based
networks as nodes, we wanted to avoid the confusion that could
result from use of that term and we wanted to convey that it was
much more than merely multi-line.

4.5.1 Multi-Instance Requirements. WWIV is distributed as a
two-instance BBS. The registered sysop is entitled to use
these two instances as two remote lines, two local instances
(no telephone line) or a combination of the two. The
unregistered sysop is expected to use it with no more than one
telephone line connected to it although it may be used with a
local access and a telephone line. Persons wanting to have
more than two lines and who are registered sysops are referred
to the Upgrade information contained in Section [???]. The
costs of upgrading to more instances is contained there along
with information regarding how to make this upgrade.

4.5.1a Registration Requirement. To have more than one
phone line connected to your BBS OR have more than two local
instances (assuming no remote lines), you are required to
register the software. With registration and an upgrade, you
can increase the number of instances up to a theoretical
maximum of 999 instances. This is referred to as a
theoretical maximum because, to our knowledge, no one has
tested the software on more than 38 instances.

4.5.1b Hardware Requirements. The hardware required to run
multiple instances is largely a function of the type of
setup that you have and the type of additional software
that you may be using. For example, to run WWIV using
OS/2(tm) or Windows (tm) as your multi-tasking or operating
system, you will need more memory available than if you were
to run the BBS on multiple computers connected on a LAN.
After all other software is loaded, you need a minimum of
580k of free lower memory to successfully run most operations.
Other sections of this documentation provide advice from
sysops who have operated WWIV in various environments.

Deskvue (tm) - See Section [???]
Windows (tm) - See Section [???]
Windows for Workgroups - See Section [???]
OS/2 - See Section [???]
OS/2 Warp - See Section [???]
Novell Netware - See Section [???]
Lantastic - See Section [???]

4.5.1c Software Setup. INIT must be run for each instance
that you wish to use. You are able to identify which instance
you are working with by the following command to INIT:

INIT.EXE ,x

where x represents the number of the instance you wish.
If the instance has a modem attached to it, you should
define the comport and select the modem type. If there
is no modem attached, you may ignore the comport and
other modem options.

The path to the TEMP directory is set by default to
TEMP<instance> and the directory is created for you.
If you want to use another directory or name, you will
have to rename the directory both in INIT and in DOS.
If batch downloads are permitted for this instance, you
must define a batch directory. To avoid confusion, use
the same directory defined as your TEMP directory.

INIT.EXE will permit you to run it with any number
following it; however, it will only create a viable setup
for you if you have upgraded your software (See UPGRADE.FRM),
to have that number of instances enabled.

4.5.1d Instance Batch files.

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

5 Operating the BBS. This chapter covers basic operation of the BBS
and system editors. With v4.30, the BBS uses FOSSIL based
communication with the com ports. Prior to starting the BBS, you
must install a Revision 5 compliant FOSSIL driver. Known working
drivers include X00, ADF and WinFossil. See the driver doumentation
for setup.

5.1 Starting the BBS. Once the FOSSIL driver is installed, you
are ready to start the BBS. The use of a batch file is recommended
since there are various settings and commands that must be issued
prior to the BBS actaully running.

5.1.1 Startup Batch File. A normal batch file may look
as follows:

@ECHO OFF
REM ***** Sample batch file for running the BBS on Instance 1:
REM ***** First, set the environment variable for the instance:
SET WWIV_INSTANCE=1
REM ***** Change drive and directory to the location of the BBS
d:
cd \bbs
REM ***** Looping the BBS to include a reload of the fossil
REM ***** driver is recommended after every user.
:LOOP
REM ***** Load the fossil driver in the begining of the loop.
REM ***** X00 or BNU work fine in DOS or a DOS box.
REM ***** WinFossil or ADF will work well for Windows.
REM ***** X00 commandlines are used for an example. You will
REM ***** have to adjust these for your system.
REM ***** Setting of TX/RX buffers is NOT recommended for any
REM ***** fossil driver. Allow the fossil to set them.
REM
REM X00.EXE E B,1,115200
REM ³ ³ ³ ³ ³
REM ³ ³ ³ ³ ÀÄÄÄ rate of your com port
REM ³ ³ ³ ÀÄÄÄÄÄÄÄ com port -1 COM1=0 COM2=1 ect...
REM ³ ³ ÀÄÄÄÄÄÄÄÄÄ baud settings
REM ³ ÀÄÄÄÄÄÄÄÄÄÄÄ Eliminates the X00 info splash
REM ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ X00. Must be in the BBS dir or path
REM
REM Next call XU.EXE, the runtime interface for X00. It has
REM to be called twice, once to turn the port on, again to
REM lock the port.
REM
REM XU.EXE PORT:<x>:<ON | OFF>
REM ³ ³ ³ ³
REM ³ ³ ³ ÀÄÄÄÄÄ turns port ON or OFF
REM ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄ com port -1 COM1=0 COM2=1 etc.
REM ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ addresses command to the port
REM ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ interface while X00 is active
REM ³ ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ locks baud rate of port
REM ³ ³ ÚÄÄÄÄÄÄÄÄÄÄÄÄ com port-1 COM1=0 COM2=1 etc.
REM ³ ³ ³ ÚÄÄÄÄÄÄÄ baud rate to lock port at
REM ³ ³ ³ ³ ÚÄ sets parity on port
REM ³ ³ ³ ³ ³
REM XU.EXE LOCK:<x>:<baud>:8N1
X00.EXE E B,1,115200
XU.EXE PORT:1:ON
XU.EXE LOCK:1:115200:8N1
REM ***** Load the BBS -o = Exit after one user
REM ***** -n0 = Error level 0 on normal exit
REM ***** -a2 = Error level 2 on abnormal exit
REM ***** %x = Allows passing of other parameters
REM ***** on the commandline (i.e. WWIV -m)
bbs.exe -o -n0 -a3 %1 %2 %3
REM ***** If the BBS exits abnormally goto the specified label.
if errorlevel 3 goto ABNORMALEND
REM ***** Errorlevel 2 is a normal quit or escape from the BBS
if errorlevel 2 goto END

REM ***** Otherwise, turn of and unload the fossil driver
XU PORT:1:OFF
X00.EXE
REM ***** And go back to the top of the loop to reload.
goto LOOP

REM ***** Actions to be performed if the BBS exits abnormally
:ABNORMALEND

REM ***** Nothing goes below this label
:END

5.1.2 Commandline Arguments. The BBS accepts 14 different
commandline options:

/B - someone already logged on at rate (modem speed)
/S - used only with /B, indicates com port speed
/N - normal exit level
/A - abnormal exit level
/R - specify max # minutes until event
/O - quit WWIV after one user done
/H - don't hang up on user when he logs off
/M - don't access modem at all
/F - pass full result code (CONNECT 9600/ARQ/HST/HST/V.42BIS)
/C - enable CTS/RTS flow control
/P - Set System Password to <password>
/V - pass usernumber online
/E - load for beginday event only;
/? - display command line options

5.2 Waiting for Caller (WFC) Screen. New to v4.30 is an optional
full screen WFC that provides information to the sysop whenever the
BBS is idle. The screen looks as follows:

[ insert screen shot ]

Also included is a defineable screen saver. See WWIV.INI for
enabling and disabling these features.

5.3 Logging on. From the keyboard, local logons are initiated from
the WFC using the SpaceBar. You will see the "Logon?" prompt. If
this is your first logon, hit Y and follow the prompts to establish
your account. If you have already established your account, hit
F for a "fast" logon or Y to logon normally. SL255 users numbered
1 through 10 may use a fast logon by hitting the SpaceBar and their
user number.

Note: This feature only works for SL255 users.

Once this logon process is complete, the last few callers and
user information screens will be presented and you will be
located at the Main Message Base prompt.

5.4 User Online keys. User online keys are used to perform
certain actions on the system or the user while he or she is
online.

5.4.1 F1 - QuickEdit User Account. Pressing the F1
key while a user is online will produce a pop
up box containing the current users access levels,
restrictions and other pertinent information. You
can tab through the fields an edit this information
as needed. Pressing F1 again closes the pop up.
A [WAIT] prompt is displayed to the user while
editing and all caller input is ignored. This is
the first User online key you will use. After
logging on and establishing your sysop account, hit
this key and give yourself maximum values as displayed
below

[ insert screen shot ]

Shift+F1.
Ctrl+F1.

5.4.2 F2 - Toggle Top Screen information. There are
three toggles of the Top Screen with F2;
System Status, Caller Status, and none.
SL255 users locally logged on default to
no Top Screen. If you want to turn it on,
hit the F2 key.

Shift+F2 -
Ctrl+F2 -

5.4.3 F3 -
5.4.3a Shift + F3.
5.4.3b Ctrl + F3.
5.4.4 F4 -
5.4.4a Shift + F4.
5.4.4b Ctrl + F4
5.4.5 F5 -
5.4.5a Shift + F5.
5.4.5b Ctrl + F5.
5.4.6 F6 -
5.4.6a Shift + F6.
5.4.6b Ctrl + F6.
5.4.7 F7 -
5.4.7a Shift + F7.
5.4.7b Ctrl + F7.
5.4.8 F8 -
5.4.8a Shift + F8.
5.4.8b Ctrl + F8.
5.4.9 F9 -
5.4.9a Shift + F9.
5.4.9b Ctrl + F9.

5.4.10 F10 - Enter Chat Mode. This key activates the
selected chat mode. You may select "split screen" chat by
setting the 2WAY_CHAT INI option to Y.

5.4.10a Shift + F10.
5.4.10b Ctrl + F10.

5.4.11 Alt-F Keys. Hitting any Alt-F key combination
while a user is online will apply the validation template
assigned in INIT to the users account.

***CAUTION An Alt-F key combination while you are online
will apply the template to your account. No permanent
damage will be done, but you will have to reset all access
levels for your self.

5.5 Top Screen Information. The local sysop's screen can show two
screens of information, which may be toggled with the F2 key. The
first screen is System Status. The second screen is User
Status of the current user online.

5.5.1 System Status Top Screen. The system status topscreen
information shows the following data about the status of the
system.

[ insert screen shot ]

The first line contains the BBS name and today's date. The
second line indicates the total number of users, total calls to
date, calls today, and number of posts today. The third line
displays the current user's name (alias) and number, time the
system has been active today, percent of time today the system
has been used, and amount of e-mail sent today. The latter
statistic as well as the number of posts today includes both
local and network information, if the board happens to be
participating in the network. The fourth line shows the current
user's security level, download security level, time left,
feedback waiting for the sysop, files uploaded today, and
feedback sent today.

5.5.2 User Status Top Screen. This top screen shows
various information concerning the current user online.

[ insert screen shot ]

The first line contains the user's name (alias) and number, mail
waiting for user, uploaded files and kilobytes, security level,
total logons, and posts. The second line contains the user's
real name, phone number, callsign, downloaded files and
kilobytes, download security level, total time on, and e-mail
sent. The third line contains the user's AR and DAR,
restrictions, exemption, logons today, and feedback sent. The
fourth line shows the user's note, sex, age, computer, time
left, and feedback waiting for the sysop. A fifth line may
appear after a caller requests a chat. This line would give
the reason the caller entered for wanting to chat. The border
line at the bottom of the topscreen information may also show
the following flags to alert the sysop of the current status of
the user and system:

5.5.2a Temp Sysop flag. This flag appears when the sysop
has toggled temporary sysop status with F9.

5.5.2b Capture flag. This flag appears when the sysop
has toggled the global capture with Shift-F1.

5.5.2c Alert Flag. This flag appears when the sysop has
pressed F6 to be informed when the caller hangs up. When
Alert has been toggled on, the computer will beep after the
current user logs off, and will not return to WFC so that
the sysop can log on locally.

5.5.2d Comm Disabled flag. This flag appears when the
sysop has pressed F3 to prevent the caller from typing.

5.5.2e Available flag. This flag is displayed when the
sysop has toggled the sysop available for chat option
with scroll-lock key.

5.5.3 Abbreviations used in the TopScreen Information.

W - Mail waiting for caller SL - Security Level
R - User restrictions DL - Download Security Level
AR - User AR/DAR PO - Total # of posts
LO - Total number of logons ES - Total e-mails sent
TO - Total minutes on FW - Feedback waiting for sysop
FS - Total feedback sent EX - User exemptions
UL - Kilobytes uploaded DL - Kilobytes downloaded

5.6 Messaging System. Message bases are sometimes referred to as
"subs." These are areas on the bbs where messages related to
particular subject areas may be kept. Any topic you can imagine
may be used for a sub. Common examples include politics, science
fiction, entertainment, sports, trivia, etc. WWIV based networks
have subs on every imaginable topic. You may want to join such a
network to offer a more diverse array of topics in your message
bases.

The very first sub on your BBS should be one where you alone can
post messages. This is your place to make announcements concerning
your system etc. You can force users to read this sub any time
there are new messages using the USE_FORCE_SCAN and
FORCE_SCAN_SUBNUM INI settings. See WWIV.INI for more information
on these settings. Users who have the appropriate SL and ARs can
read the message bases and post on them. These messages are not
private and may be read by anyone else who has the appropriate SL
and ARs.

*** NOTE: Because the more message bases and directories that you
create, the more memory is required for pointers and so forth, it
is advisable to set the number of message bases to the next highest
multiple of 32 over the number that you actually intend to use.
This will help conserve memory.

Message bases are setup by using the BOARDEDIT feature. This
feature may be accessed in the following ways:

[1] From WFC, enter B and then enter the system
password when prompted for it.

[2] From the main menu, enter //BOARDEDIT and then
enter the system password when prompted for it.

[3] From the main menu, enter //BE (short form for
BOARDEDIT and the system password when prompted
for it.

5.6.1 BoardEdit. Using Boardedit, you can delete, insert, and
modify subs. The default installation sets up one sub-board
named General.

You will see a screen that looks like the following after you
have chosen to add or modify your listing. A description of
each setting is included below:

[ insert screen shot ]

A. Name. Each sub-board needs a name, describing what type of
messages are expected on that sub-board. If your BBS is a
member of a WWIV network, the software will insert either <Net>
or [Net] preceeding the sub-board name when the sub listing is
obtained. The difference between these two uses of NET is
discussed below under the Network Validation Option.

B. Filename. Each sub-board also needs a UNIQUE filename. If
two subs have the same filename, BOTH SUBS WILL REFER TO THE
SAME MESSAGES. The filename can be whatever you want (up to 8
letters in length), but it must not contain an extension. For
example, WSSYSOP would be a legal name to enter, but
WSSYSOP.SUB would be illegal because it uses an extension. It
is recommended that you develop a naming convention for your
networked message bases to identify the file that belongs to a
particular sub. Using the sub above, if you subscribed via
WWIVnet, you may want to name the file WWSSYSOP. The prepended
W identifies the file as subtype WSSYSOP on WWIVnet.

C. Key. Normally, all sub-boards are assigned a number (in
ascending order, starting at one for your first sub-board)
which callers can press to immediately access them. If you
would prefer that a sub-board be referred to by a key (such
as %,&,#, etc) instead of a number, setting the key to that
character will do so. This option will not normally be used.

D. Read SL. This setting determines the minimum SL required to
allow a caller to read messages on the sub-board. If the read
SL for a sub is 40, and a caller's SL is 39, that caller will
never know that the sub-board exists.

E. Post SL. This setting determines the minimum SL required
for a caller to post on the sub. The post SL should be greater
or equal to the read SL. Having the post SL greater than the
read SL would allow callers to read messages on the sub, but
not post any. This type of setting is often useful on some
network subs where anyone may be permitted to read the sub, but
posting may be only by certain persons (perhaps the sysop
and/or the co-sysops.)

F. Anony. Setting the anony (no, yes, forced, dear abby)
determines whether or not messages posted on that sub can be
anonymous. No means no anonymous (unless the caller has a
security level which permits it); yes means the caller has the
option of posting anonymously, regardless of security level;
forced means the post is always anonymous; dear abby means that
the caller will be presented a choice of "signatures" for
his/her post: their name (alias), Abby, or Problemed Person.
In effect, the "dear abby" option does the same thing as
setting anony to yes, but it gives the caller two options on
which name will represent the author of the post. This option
is ignored on all networked message bases.

G. Min age. This will allow you to specify the minimum age of
callers on that sub. If, for example, you set the minimum age
to 18 (years), anyone under 18 would not know the sub existed.
This setting is normally used for adult-oriented subjects.

H. Max msgs. This sets the maximum number of messages that
can be on the sub at one time. This is usually set to 50 or
100, but can be up to 999. When the maximum number is reached,
the oldest post in the sub is rotated off (deleted) as each new
post is entered, unless a post has been given permanent status.
A post with permanent status means that it will not be erased.
This is useful if you have posted the sub rules or something as
the first message on the sub. To give permanent status to a
post, you hit N after reading the post. You will see the
message, "This post will NOT be auto-purged.

I. AR. This allows you to specify the AR for that sub. AR is
used to allow specific people to access specific subs when
other sub limitations (age, post SL, etc) are not sufficient
for your needs. As an example, suppose you have a group of
Amiga callers on your BBS. You want to give them their own area
to talk about Amigas. Age and SL restrictions would be
cumbersome and inefficient. That is where AR comes into play.
There are 16 different AR flags that can be used, A through P.
To give the Amiga callers their own sub, you would use this
setting to assign an AR to the sub. You can use any letter
(A-P) you wish, as long as it isn't in conflict with another
sub which doesn't concern the Amiga people (you can use the
same AR on different subs, but realize that anybody with the
same AR flag set would be able to access all subs with the
identical AR). For this example, you could set the AR flag to
A. Then you would go into UEDIT and activate each Amiga
caller's A flag. Now, all Amiga callers would be able to
access the Amiga sub (as long as SL and age requirements, if
any, were met) and nobody else would know the sub exists.

J. Net info. Used with WWIV network software on network subs
to properly allocate messages. If the sub you are editing is not
a WWIV network sub, leave this blank. If you select this
option, you will get a sub-menu asking for information
regarding Network, Type, Host, and Flags. As you enter the
information, you will receive helpful prompts. The Networks
that are recognized are those that you have setup in the INIT
program.

NOTE: When setting up a networked message base, this is the
first setting you should enter. Some of the fields will be
filled out for you if you have a current SUBS.LST file for
the specified network.

TYPE refers to the SubType. Under WWIV v4.21a and NET31 or
earlier, these subtypes had to be integer values; under NET32
and WWIV v4.22, you may use 7 letter character names for the
subtype. This option is referred to in WWIV literature as
"sub-by-name".

HOST refers to the network host of the sub; if you host it,
the information will display HERE; otherwise, the host's
network node number will be shown.

SUBS refers to the number of subscribers on the sub and is
diplayed only when you are the sub host.

FLAGS refers to whether the sub is auto-requestable and whether
or not the information about the sub should be reported in the
SUBS.LST distributed on each network. For more information on
this, refer to the WWIVnet Documentation that accompanies the
Network Software.

There will also be an appended category on subs you host. If
this is chosen, a list of available categories (distributed
by the NC for the network) will be given. The purpose of this
is to allow the sysop to select the most appropriate category
(for that sub information) for listing in the Subs List that
is distributed by each network.

K. Storage type. There are 2 main ways messages can be
stored, either with each message in its own file, or with all
messages in that message base in one large file. 0 means each
message will be in its own (text) file, 2 means all messages
in that sub will be in one large (non-text) file.

L. Val Network. This option may be toggled on or off. If
toggled on, sub-board that are network subs, will have the
network name enclosed in brackets (i.e. [WWIVnet]) in front of
the name and the sysop will need to validate the messages
received there before the messages will be sent over the
network. If the option is toggled off, the sub will have
the network name enclosed in v-brackets (i.e. <WWIVnet> in
front of the Sub-Board name. Because many network subs have
various restrictions (such as no ansi posts, or posts from #1
on the BBS only, etc), network validation is a means of
insuring that posts originating from this BBS are in compliance
with the sub-host's rules.

M. Req. ANSI. The sysop can require that the user have ansi
enabled in order to view this sub. This option is particularly
useful if the sub is one of ansi pictures drawn with THEDRAW or
some other ansi editor. An example of an all ansi sub is the
WWIVnet Sub known as The Ansi Art Gallery.

N. Disable Tag. This option, if toggled on, will disable
taglines in the messages. This may be useful if a network sub
host does not permit posts which have taglines added to them.

O. Description. This option permits you to supply a
description of a sub that you host. This description will
be used in the SUBS.LST file maintained by the network. The
entry in this field makes it possible for subs you host to
be included in the SUBS.LST without your intervention; the
only requirement is that the auto-info option in FLAGS be set
when the sub is set up.

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

6 Modem Information and Setup

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

7 For New Sysops

Operating a BBS can be a very satisfying
(and addictive) experience, particularly if you have given
some thought to your setup and the needs and desires of your
target audience. A BBS with an attentve and participating
sysop offers a personal, "homey" atmosphere that the Internet
cannot provide. With the "Internet Explosion" still in full
swing, you must target a specific group of users and advertise
to capture a sizeable user base.

Because a BBS can be used for such a wide variety of things,
this chapter assumes that you know virtually nothing about a
BBS and that you are a first-time WWIV operator. The information
that follows is meant to help guide your thoughts and creative
processes so that you will obtain the most enjoyment from
the experience.

You can determine whether your BBS is to be a general purpose BBS
or whether it will cater to some particular interest. A general
purpose BBS normally will not focus on any particular topic in
its message bases or file sections; instead, it will have something
for everyone and will probably not try to have everything available
on any topic or subject area. A general purpose BBS is often the
best approach for a beginner to take unless you have some clearly
defined area(s) of interest that you want to pursue. If you are
not participating on a network, then you may wish to have message
bases that reflect a broad spectrum of interests. If you are on
a network, you may wish to subscribe to subs that reflect such
broad areas. Your download sections may also reflect a broad area
of interest. It is recommended, at a minimum, that you provide
file areas that support the needs of a general user. That is,
you may want to make the common archive programs, protocols, and
terminal programs readily available to your users to make it
easier on them to call the BBS. You may wish to provide the
User Documentation for download so that your users can learn how to
use a WWIV BBS system. Beyond those minimums, you are left to your
own imagination and perhaps the suggestions of your users to create
the topical download areas that will appeal to those who call your
board.

A special purpose BBS is generally best when it reflects your own
interests. If it reflects your interests, you are more likely to
take an active interest in your BBS, to post things, and to keep
fresh material in your download areas. Generally, a BBS that
reflects that the operator takes an active interest in the BBS is
more successful than one where the operator's presence is invisible
or totally lacking.

Once you have determined the type of BBS that you are going to run,
you should give some thought to the types of security levels that
you will have on your board and the amounts of time that you will
allow each user and/or security level. By looking in INIT, you can
determine the predefined or default levels for certain security
levels. My advice would be to (a) use no more security levels than
you absolutely need and (b) to try to keep things as simple as
possible. To give you some idea of this, here is a basic overview
of the setup at The Mountain Empire which is primarily a support
BBS for WWIV operators.

There are seven security levels and three access levels in use:

Type User SL DSL AR's DAR's
ÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ ÄÄÄÄÄ ÄÄÄÄÄÄ ÄÄÄÄÄÄÄ
Unvalidated 10 0
Normal 20 20
Other Sysop 30 30
Registered Sysop 40 40 A A
w/ Mods Access 60 60 A M A M
w/ SDS Access 80 80 AKM AKM
Sysop 255 255 All All

There are two SL255 Sysops and no Co-Sysops, local or remote.
The Advanced ASV and Guest Account features are activated so
that users and visiting sysops who call for support will have
immediate access to the support areas of the BBS. (sans Mods
and SDS)

The AR and DAR of A indicate that the user has
access to the WWIV support message bases and file sections
but does not have access to the modifications and/or the
WWIV source code. A registered visiting sysop (i.e. one
that is a bonafide registered WWIV sysop) has access to
the message bases dealing with modifications of the source
code (indicated by AR and DAR of B) and the transfer areas
that contain such modifications. This status must be
requested. Finally, I have the sysops who are registered
and have requested to use my board as their SDS site
(source distribution site). Those people must send a
letter to Wayne Bell and provide the information necessary
to be approved for source access.

As you can see, the number of SLS, DSLS, ARS, and DARS
used here is very limited, yet it suits the security pur-
poses of my BBS. After you have examined your needs and
thought out your own security arrangements, then you
should use the BOARDEDIT and DIREDIT features to set up
your board to reflect the security levels and access
restrictions that you will need. You may wish to also
have other indicators (i.e. age or sex) for certain areas.
The BBS software supports your using all of these factors
to allow or deny support from various sections of your
board. You should be aware that any user who does not
have the appropriate SL and accompanying access rest-
rictions will not be aware of the other parts of your BBS.
For example, lets say that you have a total of 10 message
bases. The first three have SL of 30 and no ARS; the
next three have SL of 40 and AR of A. The last four have
SL of 50 and AR of B. A user with SL of 30 would see
only the first 3. A user with SL of 40 and AR of A would
see the first 6 message bases. In other words, if you
have the appropriate access restrictions (ARS), you can
see those message bases that have lower SLs than your own.
A user with SL of 50 are AR of B would see the first 3
message bases and the last 4. If that user had ARs of
both A and B, then he could see all of your message bases.

After you have developed your security levels and
access restrictions, you should probably make yourself
some form letters to send to people explaining any
particular rules of your BBS and/or any rules associated
with their particular access level. These form letters
are explained in Chapter 42 of the documentation.

You may then wish to have a few friends call so that
you can learn the process of validating them while they
are on line (see section ). Encourage them to try out
various parts of the BBS and to post some messages.

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

8 WWIV on the Internet. Telnet and PPP

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

Appendix A (References)

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

Appendix B (Forms) Registration Form
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
WWIV Software Services, LLC
PO Box 4468
Johnson City, TN 37602-4468

Product Registration/Order Form

SEE Section 1 regarding End-User License Agreement
SEE Section 2.1 regarding Payment Plan.

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³Full
Name ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³Address
Line 1 ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³Address
Line 2 ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³City,
State, Zip³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³Voice
Phone ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³BBS
Name ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³BBS
Phone ³ ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

If you are on a network or network(s) fill in the following:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÒÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Network
Name ³ Node Number º Network Name ³ Node Number ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄ×ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ ³ º ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄ×ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ ³ º ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄ×ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ ³ º ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄ×ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ ³ º ³ ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÐÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

Installment Plan (Y/N)________ Payment Number: 1 2 3 4
(Circle One)

================================================================

Complete this section ONLY if you wish to DOWNLOAD the source code from
an authorized Source Distribution System (SDS).

SDS Node Number: _______ Network: __________________

SDS BBS Name: ________________________________________

User Name/Handle on SDS Site: ________________________

User Number on SDS Site: _______

================================================================

NOTE: You must read the End-User License Agreement prior to ordering.
Your completed registration form and fees indicate that you have read the
agreement and agree to its terms and conditions.

ÚÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄ¿ ³Qty
³ Description ³ Cost ³ Extended ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
WWIV v4.xx for DOS Registration ³ ³ ³ ³ ³ (2
Instances) ³ $80.00 ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
WWIV v4.xx for DOS Installment Plan ³ ³ ³ ³ ³ $20 /
$20 / $20 / $25 ³ ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
Network Registration ³ ³ ³ ³ ³
(Included w/ BBS Reg. All platforms) ³ ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
WWIVedit Registration ³ $20.00 ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
WWIVchat Registration ³ $25.00 ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
Source Code on 1.44 MB Diskettes ³ N / C ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
Source Code/Mod Collection Zip-Disk ³ $15.00 ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
CD-ROM SuperDisk (Available AUG 99) ³ Future ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
Automatic delivery of next release ³ ³ ³ ³ ³ via US
Mail ³ $10.00 ³ ³
ÃÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ ³
Shipping outside North America ³ $10.00 ³ ³
ÃÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´
³ ³ ³
³ Subtotal: ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´
³ ³ ³
³ TN residents add 8.5% Sales Tax: ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´
³ ³ ³
³ Total Amount Enclosed: ³ ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÙ

* Remit to WWIV Software Services, LLC at the address above.
* Checks and Money orders drawn on US Banks ONLY.
* Dishonored checks carry a $30 surcharge per draft.
Checks will only be deposited once unless WSS receives written
instructions otherwise. Dishonored checks and surcharges may
only be paid by money order or cashier's check.

Customer Statement:

My signature below attests that I have read, understand, agree to, and
will abide by the terms and conditions of the End-User License
Agreement(s) for the products ordered above. I understand that failure
on my part to abide by the terms and conditions set forth therein may
result in civil or criminal liability, revocation of my license,
forfeiture of any registration fees paid, or any combination thereof.

______________________________ __________

Signature Date

Appendix B (Forms) Registration Upgrade Form
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

WWIV Software Services, LLC
PO Box 4468
Johnson City, TN 37602-4468

Registration / Instance Upgrade Form

This form is for those who wish to have more than two instances, WHICH
UTILIZE THE SAME USER.LST. Sysops desiring to access different user list
files must purchase an additional full registration for each user list
used.

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³Full Name: ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³Address Line 1: ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³Address Line 2: ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³City, State, Zip:³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³Registration ##: ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³Reg. Passcode: ³ ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

Registration address if different from above:

Line 1: ________________________________________

Line 2: ________________________________________

City, State Zip: _________________________________________

Circle desired upgrade:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÂÄÄÄÄÄÄÂÄÄÄÄÄÄÂÄÄÄÄÄÂÄÄÄÄÄÄ¿
³Upgrade From ³ <=2 ³ 4 ³ 8 ³ 16 ³ 32 ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÅÄÄÄÄÄÄ´
³Upgrade to 4 ³ $20 ³ ³ ³ ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÅÄÄÄÄÄÄ´
³Upgrade to 8 ³ $45 ³ $25 ³ ³ ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÅÄÄÄÄÄÄ´
³Upgrade to 16 ³ $80 ³ $60 ³ $35 ³ ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÅÄÄÄÄÄÄ´
³Upgrade to 32 ³ $120 ³ $100 ³ $75 ³ $45 ³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÄÅÄÄÄÄÄÅÄÄÄÄÄÄ´
³Unlimited ³ $220 ³ $200 ³ $175 ³$145 ³ $100 ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÁÄÄÄÄÄÄÁÄÄÄÄÄÄÁÄÄÄÄÄÁÄÄÄÄÄÄÙ

Amount from Above: ____________

TN Residents add 8.5% Sales Tax: ____________

Total Enclosed: ____________

_______________________ ___________
Signature Date

Appendix B (Forms) Registration Transfer Forms (Present Owner)
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

WWIV Software Services, LLC
PO Box 4468
Johnson City, TN 37602-4468

Present Owner Transfer Request:

I, ____________________________________, a registered
(Printed full name of present owner)

user of WWIV under registration number ______________,
(Registration number)

hereby request to transfer my registration and all

registration privileges to __________________________.
(Printed full name of transferee)

I agree to immediately destroy all copies of WWIV source code in my
possession and to immediately cease using WWIV software. I realize that
any SDS access that I may have had in the past will be terminated
immediately. I further understand that this transfer will not be
effective until the signed statements from the new owner and myself and
with a check or money order for $25.00 (US Funds) are received and
processed by WWIV Software Services.

_______________________________ _______________
Signature Date

Current Mailing Address:

_____________________________________________________

Address at time of registration (if different):

_____________________________________________________

Appendix B (Forms) Registration Transfer Forms (New Owner)
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

WWIV Software Services, LLC
PO Box 4468
Johnson City, TN 37602-4468

New Owner Transfer Request:

I, ________________________________, hereby request to
(Print your full name)

have the WWIV BBS software currently registered to

_______________________________ under registration number
(Printed name of current owner)

_____________________ transferred to my name.
(Registration number)

I have read understand and will comply with the terms and conditions of
the license agreement contained in the shareware distribution archive. I
have enclosed my completed registration form in addition to this letter.
I understand that this transfer will not be effective until the signed
statements from both myself and the present owner, my completed
registration form and a check or money order for $25.00 (US Funds) are
received and processed by WWIV Software Services.

My current mailing address is:

_____________________________________

_____________________________ _________________
Signature Date

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

Appendix C (References) Technical Support and Resources

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

Appendix D (Frequently Asked Questions)
******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************
Appendix E ( Common Protocol Settings )
******************************************************
THIS IS A FINAL DOCUMENT AND IS COMPLETE
******************************************************
Appendix F ( Source Code )

For your reference, here is a copy of the Source Code End User License
Agreement.

1. END-USER LICENSE AGREEMENT

1.1 GENERAL. READ CAREFULLY: This End-User License Agreement
(EULA) is a legal and binding agreement between you and WWIV
Software Services, LLC (WSS) and applies to all WSS products
distributed with source code. For the purposes of this
document, SOFTWARE refers to and includes all software, source
code and documentation contained in registered distribution
archives as provided by WSS.

IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS
EULA, DO NOT DECOMPRESS THE DISTRIBUTION OR SOURCE CODE
ARCHIVE.

WSS prosecutes violators of this license agreement to the fullest
extent of both federal and state civil and criminal laws and statutes.

1.2 SOFTWARE LICENSE.

YOU ARE BOUND BY, AND INDICATE YOUR EXPLICIT ACCEPTANCE
OF, THE TERMS AND CONDITIONS OF THIS AGREEMENT UPON
DECOMPRESSION OF THE SOURCE CODE ARCHIVE.

U.S. AND INTERNATIONAL COPYRIGHT LAWS AND TREATIES, TO
INCLUDE ALL INTELLECTUAL PROPERTY LAWS AND TREATIES
PROTECT THIS SOFTWARE.

THIS SOFTWARE IS LICENSED, NOT SOLD. YOU HAVE PURCHASED A
LICENSE TO POSSESS, VIEW, AND/OR MODIFY THE SOURCE CODE.
WSS RETAINS OWNERSHIP, COPYRIGHT, AND INTELLECTUAL
PROPERTY RIGHTS TO THE SOFTWARE AND ANY DERIVATIVES
PRODUCED THEREOF AND RESERVES THE RIGHT TO UNILATERALLY
TERMINATE ALL LICENSES TO SOURCE CODE AT ANY TIME.

a. General License Grant. WSS grants to you a personal, exclusive
license to:

1. Install one operational copy of the SOFTWARE that may
operate on not more than the number of instances you are
registered for, each accessing the same USER.LST. Separate
instances that access a separate USER.LST require additional
licenses be purchased for each USER.LST.

2. Download, view, possess, and modify WWIV source code for
versions through v4.99 for your own personal use after
completing verification requirements as prescribed by WSS.

3. Have an unregistered individual modify source code for you
ON YOUR COMPUTER for your use provided that the source code
never leaves your computer in any form and remains under your
direct control at all times.

4. Have a registered user modify your source code on his or
her system provided you notify and obtain written permission
from WSS PRIOR to doing so.

5. Purchase upgrades to allow the operation of the software
on more than two and not more than 999 instances.

6. Distribute source code modifications written by you on
subboards designed specifically for that purpose or by private
mailings provided the modification contains no more than 100
lines of the original copyrighted code. You must obtain written
permission from WSS PRIOR to the distribution of modifications
containing more than 100 line of copyrighted code.

7. Provide electronic download access to modification to
registered users of the SOFTWARE as verified by WSS through the
use of a modification provided by WSS.

8. Produce and distribute utilities and add-on programs
specifically designed to operate on systems running the SOFTWARE
that utilize ONLY the data structures of the SOFTWARE royalty free.
(Use of components, functions, or derivative code must be
approved and royalty fees paid prior to distribution)

b. License Exclusions. Under your license, you:

1. May NOT distribute any modified compilation of the SOFTWARE
by electronic download or transfer said compilation to anyone
by any means without PRIOR WRITTEN AUTHORIZATION from WSS.

2. May NOT distribute source code or any portion thereof to
anyone for any reason without PRIOR WRITTEN AUTHORIZATION from
WSS. (Distribution of source code fragments authorized under
paragraphs 1.2.a.6 and 1.2.a.7 excluded.)

3. May NOT allow unregistered users, or users, not verified
by WSS, but claiming to be registered, access to or electronic
download of modifications as described in paragraph 1.2.a.6.

4. May NOT produce and distribute derivative works based upon
the SOFTWARE in whole or in part except as authorized under
paragraph 1.2.a.8 above. Derivatives are defined as software
programs or components of software programs that duplicate
the operation, function, and/or appearance of the SOFTWARE.
If any code other than that described in paragraph 1.2.a.8
above is used, you must obtain written authorization to do
so and may incur liability to pay WSS certain royalties as
negotiated.

5. May NOT "port" or rewrite the SOFTWARE to function under
another operating system or on another platform with the
intent to distribute the work without PRIOR WRITTEN
AUTHORIZATION from WSS. You may, however, "port" or rewrite
the SOFTWARE as described above for your own individual use.

6. May NOT be entitled to the source code to future versions
of the SOFTWARE due to a decision to terminate this
distribution method.

c. Termination of License. WSS reserves the right to unilaterally
terminate all licenses to source code at any time. In addition,
WSS will terminate and permanently revoke the license of any
registered user found in violation of the terms and conditions set
forth in this EULA and will prosecute said violators to the fullest
extent of both state and federal, civil and criminal laws.

d. Documentation. This EULA grants you, as an individual, a
personal, nonexclusive license to make, use, and make available
for electronic download, an unlimited number of copies of the
documentation included in the distribution archive provided such
copies are not modified in any way and contain the original
copyright information.

e. Storage and Electronic Transfer of Distribution Archives. You
may store and make available for electronic download, in
unmodified form, a copy of the original WWIV v4.30 shareware
archive as distributed by WSS.

f. De-compilation and Reverse Engineering. You agree not to make
any attempts to de-compile, reverse engineer, or disassemble the
executable portions of the SOFTWARE to avoid the requirement to
register, modify copyright displays, or the operational aspects
of the SOFTWARE.

1.3 LIMITED WARRANTY. WSS warrants that the SOFTWARE will perform as
described in the included documentation for a period of sixty days
from the date of first installation. Any technical support provided
by WSS shall be as described in the included documentation provided
to you in the distribution archive. WSS will make reasonable efforts
to solve any problem not covered in the included documentation. To the
maximum extent allowed by applicable law, implied warranties on the
SOFTWARE, if any, are limited to sixty days. No other warranties are
expressed or implied. To the maximum extent allowed by applicable law,
WSS disclaims all other warranties and conditions, either express or
implied, including, but not limited to, implied warranties,
merchantability and/or fitness for a particular purpose, with regard
to theSOFTWARE and the provision of or failure to provide support.
This limited warranty gives you specific legal rights. You may have
others, which vary from state to state. This warranty is executed
under the laws of the Sate of Tennessee.

1.4 CUSTOMER REMEDIES. Your exclusive remedy shall be to notify WSS
of a suspected failure to meet the specifications of the LIMITED
WARANTY. The entire liability of WSS shall consist of replacement of
the SOFTWARE with an updated version if available.

J-1

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************
Appendix G ( Credits and Thanks )

There are more folks that belong on this list that can possibly be
mentioned. Here they are in no particular order:

Wayne Bell - for starting it all, keeping it going for so many
years and then seeing the way clear to pass his
legacy on.

Wig De Moville (Filo) - for providing a support system for Wayne
during a time when WWIV might have faded away.

Greg Ferrante - for introducing me to WWIV in the first place.

Frank Reid - The one man upon whom this entire project was hinged.
He fueled the fire and motivated me to buy WWIV in
the first place then provided his extensive expertise
and effort during the development process.
Cannonization pending....

Craig Dooley (Morgul) - for backing me up during the early years
and his continuing support and friendship.

Rob Clevenger - for his help in every phase of development and
documentation.

Mike Deweese (Zu Digital) - for providing some of the most
inovative code and features in what you see as
WWIV v4.30.

The WWIV Development Team (WDT) - the group of truly hard-core
sysops that contributed their time, talents, and
energies to develop a top quality product.

The Beta Team - for their tireless testing of of the software and
survival through Beta 1 and for finding a great majority
of the bugs, some more than once.

Last but most certainly not least, the group who deserves the
greatest appreciation, the registered users, without whom, none
of this would be possible.

******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

Appendix H ( Closing Comments )
******************************************************
THIS IS A WORKING DOCUMENT AND IS NOT COMPLETE
******************************************************

Appendix I ( Index )
******************************************************
THIS IS A FINAL DOCUMENT AND IS COMPLETE
******************************************************

Appendix J ( WWIV Software Services Operational Policy )

This document last revised: 01 July 1999

1. General: WWIV Software Services (WSS) dictates policy for the
software under its control only and does not attempt to influence the
operation of any network in any manner. Network policies are dictated by
the Network Coordinator (NC) or administrative body of the individual
networks. WSS does however, reserve the right to interpret our policy
for the individual user and/or network administrator(s). Any question as
to applicability or interpretation of these policies should be brought to
the attention of WSS immediately and before the registered user or
network official act. Decisions or interpretations rendered by WSS on
any issue are final. WSS reserves the right to revise, rescind, expand
or alter the terms and conditions of this or any other existing policy at
any time and may do so without notice. Revised policy will be grand
fathered in most cases to allow no degradation of eligibility, status, or
office of the individuals it affects.

2. Distribution, Software Registration and License: WWIV is distributed
under the shareware concept. The user has 60 (sixty) days to evaluate
suitability of the software to his or her needs. Not later than the
sixtieth day, the user must register the software using one of the
methods contained in paragraph 3 below, or discontinue use of the
software and remove all operational copies and archives from his or her
computer(s). The user may download evaluation versions of the newer
revisions or releases to try the software again and the 60-day trial
period begins anew. Re-installation of the same version, for any reason,
after the initial 60-day trial DOES NOT, constitute a new trial period
and is a violation of the shareware license agreement and is illegal. The
trial period may be extended at the discretion of WSS on a cases by case
basis. Initiation of a payment plan under the provisions of paragraph
3b.3 below extends the trial period for 60 days. Each payment made on
time will extend the trial period for an additional 60 days not to exceed
a total of 240 days.

3. Registration:

a. General. When registering, the user is purchasing a license to
use the software in accordance with the End User License
Agreement (EULA) associated with the product. Registration
does not imply nor entail ownership of the software. WSS
retains ownership of the software itself.

b. Methods: There are three methods of registration available,

1. Online Registration. Available AUG 99. Prices for online
registrations are slightly higher due to increased costs.

2. Normal Registrations. Executed by check or money order
via US Mail.

3. Payment Plan. WSS offers a payment plan for the purchase
of BBS registrations. See the BBS documentation for more
information on the payment plan.

c. Revocation: The user's license may be revoked by WSS at any
time should he or she violate any provision of this document or
the terms and conditions specified in the license agreement
contained in the distribution archives.

d. Upgrades: The user is entitled to upgrade to all releases of
the product line under the major revision purchased. For
example, purchase of a v4.xx registration entitles the user to
free upgrades to all releases through v4.99 for the platform.
The user IS NOT entitled to free cross platform upgrades under
this policy. Cross platform upgrade fees may or may not be
charged and will be announced well in advance of releases.

e. Instance Upgrades: The user is entitled to purchase instance
upgrades to a previously purchased BBS registration at the price
announced at the time of release.

f. Transfers: REGISTRATIONS MAY ONLY BE TRANSFERRED BY WWIV
Software Services. Registration transfers are only offered for
BBS registrations. No other registrations will be transferred.

g. Exemptions: Registration exemptions are authorized to be
granted by the Network Coordinators (NC) of :

WWIVnet IceNet TerraNet FILEnet
GLOBALnet DigiNet WWIVLink SierraLink

The NC of these networks may grant an exemption for systems
acting in the capacity of network servers. NC's may place
additional requirements on the system; however, the following
minimum criteria must be met in order to grant the exemption:

1. The requesting sysop must have purchased a valid
registration for at least one copy of WWIV and must be
running a public BBS on the network in question using that
registration number.

2. The primary purpose of the system must be the movement
of network traffic and not operate as a public dialup system.
User accounts on the server will be limited to number one
accounts of connecting systems generated by the server
operator.

3. The server operator will provide a dialup telephone
number or Internet address (telnet) for the system to allow
the NC or WSS to log on to the system. This is to verify
that the system is in fact a server system and maintains
compliance with both WSS and network policy.

4. The requesting system must operate for the good of the
network as a whole in the judgement of the network
administration.

Network Coordinators desiring authorization to grant exemptions
should email WSS with a request.

4. Source Code.

a. Availability. Currently, registration of the BBS software
entitles the user to the possess, view, and modify the source code
to the BBS. If, at any time in the future, it becomes impossible
or too difficult to control the distribution of source code, this
policy may be rescinded. FOR SECURITY REASONS, THE SOURCE CODE TO
INIT.EXE, NETWORK SOFTWARE OR NETUP IS NOT AVAILABLE TO ANYONE.

b. Obtaining the Source Code. Current source code may be obtained:

1. On disk by sending a completed registration form and $10.00
(US) to WSS.

2. By download from an authorized Source Distribution System
(SDS). SDS systems are authorized by WSS to distribute WWIV
source code without charge to registered users after
verification of their registration information with WSS.
In order to download the source code from a SDS, the registered
user must logon to the SDS and establish a user account, then
type //SDS at the main menu prompt. Following the prompts will
send a request for access directly to WSS. Upon verification of
your request and registration information, authorization for
access will be sent to the SDS operator who will grant you
access to the distribution archives.

3. Via the Internet SDS at http://sds.wwiv.com/. You will be
required to send a request similar to the one above from this
location. Processing of these applications is normally
accomplished within five to seven days.

c. Modification Publication: Registered users may publish
modifications on sub-boards designed for that purpose on
individual networks. It is the responsibility of the host of
these subs to ensure that only registered users are permitted
to subscribe to subs where modifications are posted. Source
code modifications that contain more than 100 lines of original
copyrighted code require a release for publication from WSS.
Email the mod in its entirety to WSS. In most cases, unless the
modification contains code of a sensitive or malicious nature,
they will be approved for release. Releases or Denial of
Release will be issued within five business days.

d. Modification Access Restrictions: Registered sysops will control
access to all BBS modifications available for download, viewing,
reading or capture on their system. The registration information
for ALL individuals desiring access to modifications in any form
must be verified with WSS before granting access. Sysops wishing
to distribute modifications via download will request an install a
modification for this process from WSS. This is the only request
that will be accepted.

e. License Agreement Violations: Unauthorized distribution of WWIV
BBS Source Code or portions thereof is a crime. Registered
and/or unregistered Individuals found in violation of the EULA
contained in the source code archive will be prosecuted to the
fullest extent of both civil and criminal laws. All registered
users should review of the Source Code License Agreement to
ensure they fully understand and are in compliance with it.
Registered users have the responsibility assigned under the EULA
to immediately report suspected or known illegal possession,
modification, or distribution of source code under any provisions
contained therein. Reporting violations protects your future
ability to access the source code.

5. WSS Source Distribution Systems (SDS): WSS has several systems
specially authorized to distribute source code to registered sysops. The
number of systems is limited and only the most qualified systems are
selected for this function. Meeting all the qualifications of the
criteria listed below is no guarantee of selection.

a. You MUST be the sysop (#1) of your system.

b. You MUST have been a registered sysop for at least 2 years.

c. You MUST have been running your BBS continuously for the last
2 years.

d. Your BBS MUST be a full time system, open to anyone who wishes to
call. No part-time boards, closed boards, or boards that require
a new user password to sign on.

e. You MUST be 21 years of age or older and provide a photocopy of
an official photo ID to WSS with your application.

f. You MUST have been a member of at least one major network for a
minimum of one year. (preferably WWIVnet, IceNet, TerraNet or
FILEnet)

g. You MUST provide a list of at least 20 registered WWIV Sysops
who want to be able to download the WWIV Source Code from you,
listing their real names and registration numbers.

h. You must install the approved SDS Access Request Modification on
your system.

i. Upon acceptance, you must be willing to sign a distribution
agreement with WSS that outlines your legal responsibilities
and obligations as a Source Distribution System.

6. WSS Support Board Network: WSS provides a network of highly skilled,
knowledgeable sysops to the BBS community. Sysops selected for this
status are time tested and have been recognized for the amount and
quality of support they offer. Below is a description of the types of
support offered and selection criteria for each:

a. The Support Coordinator and active Support Boards select new
Support Boards (SB). To become an official SB, the sysop, as
a minimum, must meet the requirements of 5a through 5d above.
In addition, the following conditions must be met:

1. The sysop must maintain a library of all official WSS
releases, and a reasonably stocked library of WWIV support
files, readily accessible to the public, without
restrictions or ratios.

2. The system must offer Auto Sysop Validation (ASV) and/or
a Guest Sysop Account (GSA)

3. You MUST have been a member of at least one major network
for a minimum of one year. (preferably WWIVnet, IceNet,
TerraNet or FILEnet)

4. You must be thoroughly knowledgeable concerning BBS and
network operations and will be required to provide prompt,
courteous replies to requests for assistance as well as
extensive assistance to new sysops who may request help.

b. WSS, The Support Coordinator, and the active Core Sysops select
Core Support Boards (CSB). To be considered for Core Status,
the sysop must have a minimum of 2 years of exemplary service as
a Support Board. There is no application process as with the
SB system. Core Support Boards are selected solely on tenure
and merit of service.

c. Any form of Support Board status may be removed at any time if
the sysop fails to meet minimum requirements or when individual
conduct is contrary to the spirit and intent of the support
network.