Network installation

Color 64 Network - Installation

Network Installation Overview

Summary of Files

The table below provides a summary of the required and optional network-related files included with your Color 64 system.

Summary of Required Files for Network Operations

File	Description
√bbs.nw1, √bbs.nw2	These are the two main network program modules and should be located in the Program Files.
√sys.net	This is the NET SETUP program, similar to BBS SETUP. It allows you to define drives and configure individual node information.
prscrn52750	This file must be located on the Boot Files drive with Net Setup. It allows screen dumps to the printer while inside the program. (**)
√rlog, √slog	These are the receive and send logs for Network file transfers. (*)
bck to bill	Stand-alone program used to create a new billing file from a backup. It should be located with your Boot Files.
bbu.nw2	Optional merge file that installs an automatic billing backup feature into the midnight routine.
√node app	Sequential file that you edit. It is used the first time you call a new node to introduce your system. The name of your BBS is automatically inserted at the beginning of this message when it applies to a new node. (*)
√conditions	Sequential file that you create. It is used when a node calls you for the first time and describes your validation requirements for new nodes. (*)
√temp xref	Optional file used to assign nodes new ID numbers without requiring them to change their existing IDs. It is created and edited manually. (*)
* Must ALWAYS remain on your NETWORK drive. ** Must ALWAYS remain on the Boot Files drive.
** Other Files ** These files may be self-generated and appear on your drive as they are needed
√node x users	Membership list of users on your BBS who have access to Network. Created nightly (midnight) and provided to remote nodes as your system membership list.
√node [#] users	[#] = Node Number. Membership list for an individual node. This file is received when you send data and request a new listing.
√+node [#]	Packet of public and private messages posted to the node specified by [#].
√+file [#]	File containing information about file transfers to be sent to the node specified by [#].
√node ledger	Shows node account transactions. Remains on the drive until moved or scratched. Present but not used in this version.
√public storage	Holds messages you have released from received Node public messages.
√node list	List provided when sending to a node. Created by the Net Setup program.
√ntwrk.parms	Contains setup details for how Network is to run, including data for each node. Created by the Net Setup program.
√node accounts	Relative file containing name, password, level, and last date called for each incoming node.
√node billing	Relative file containing dollar amounts for each user on the system. Present but not used in this version.

Installation

The following steps prepare your system to run Network:

1) Boot the normal BBS SETUP program.

2) Select Main Parameters (option 1) to edit.

3) Near the end of the parameter list, answer "Y" to the question asking if you want to run Network.

4) Go to Disk Drive Assignments (option 2) and verify the correct drive is selected for the Network Files.

5) Go to BBS Commands (option 7) and verify Network-specific command levels are set as desired:

* Post Network Message: Used by you or users to create network messages. Typically safe for most users except new users.

* Net Maint Menu: Network maintenance submenu for online/offline maintenance. Includes options related to node status and selecting files to transmit. This should be restricted to top staff.

* Release Publics: Allows public messages received from the network to be released. This is well-suited to a co-sysop role and is covered in detail later.

* Restrict Posts: Not a command. Defines a per-call limit on the number of network posts a user can make. The first value is a level exemption (users at or above this level are not limited). The second value is the maximum number of posts per call for users below the exemption. This should be accessible only by the Sysop.

Network Setup

Locate the file called "+net setup" in your Boot Files. Ensure the file "prscrn52750" is located on the same drive. The "+net setup" loader works like other boot files, except it loads the "√sys.net" (NET SETUP) program.

Once the program loads, you may be prompted to insert your Program disk.

You will then be asked a series of questions:

1) Number of Nodes

You should already have at least one system in mind. The minimum is "1", and you can add more later. You will need information about each node in a later step, so if you do not have the required information, abort setup and return when ready.

You may define 1 to 99 nodes, but higher values require additional memory.

2) Public Message Category

Network supports both private E-Mail and public messages. This setting determines how incoming public messages are handled.

You have two choices:

* Automatically place public messages directly into the message base by entering the destination category letter.

* Hold public messages in a special holding file for manual release by entering 0 (zero).

You may type "?" at this prompt to display a list of categories.

3) Open and Close Times

Defines the time window when network calls and message transfers are allowed. This feature originated to avoid higher phone-rate windows, but may still be useful.

Restrictions:

* The open time cannot be later than the close time.

* The open/close window cannot span midnight (for example, 23:00 to 03:00 is not allowed). You may open at 00:00, but you cannot remain open through midnight.

Times are entered in 24-hour (military) format. These values can be adjusted later.

4) Days Request Membership List

Each night at midnight, your BBS creates a network membership list (√node x users). When you call other nodes, they may request a fresh copy of this list.

This value determines how many days to wait before requesting a new membership list from a node you call. Lower values increase request frequency.

5) Your BBS Name

Enter your BBS name as it should appear in outgoing network message headers. Maximum length is 25 characters.

6) Does Modem Support BUSY and NO DIALTONE?

If your modem returns BUSY or NO DIALTONE response codes, you may choose to answer "Y". Check your modem documentation for the ATX command details.

This setting affects how the network lockout mechanism interprets failed call attempts.

If enabled, a node may be locked when the modem returns NO CARRIER (indicating repeated ringing with no answer). With BUSY/NO DIALTONE support, NO CARRIER is more likely to indicate the remote system is down, not picking up, or otherwise unavailable.

If you answer "N", the system will not lock nodes based on NO CARRIER/BUSY/NO DIALTONE responses.

If your modem does not support BUSY and NO DIALTONE, you must answer "N".

7) File Release Directory

Determines where files received through the network are placed. You may choose a U/D directory or the Network drive.

If a U/D directory is selected, the directory is automatically updated as files are received (similar to multi-upload).

8) Hold Files for Release?

Determines whether received files are held for manual release or made available immediately, similar to standard file transfers and the auto-release level setting in SETUP.

If you have already chosen to place received files on the Network drive, this option has no effect.

Net Setup - The Node Editor

After completing the main Network questions, you will be placed at the node editor prompt:

At this prompt, you can edit any node. The value in double brackets [ ] indicates the last node number you edited. Entering "?" displays a list of node names and their status, which helps locate open slots or specific entries.

Before editing nodes, keep these definitions in mind:

• Node Number: Assigned by you in +NET SETUP. Used for selecting a destination when users post a network message. The remote system does not see or use this number. (Outgoing calls)
• Node ID Number: Assigned by you (or automatically assigned during electronic application) and displayed in the NETWORK MAINTENANCE menu. This is effectively the remote node's "user id" when it calls your system. (Incoming calls)

INCOMING and OUTGOING are separate. NET SETUP configures OUTGOING calls. The Node Editor in NETWORK MAINTENANCE configures INCOMING node access.

To edit the first node, enter 1 (Node Number One) and press RETURN. You will see a screen similar to the following:

Summary of Required Fields for Network 64

Field	Description
1. Node Name	Name of the remote node (maximum 25 characters). This name is displayed to users when selecting a destination for network posts. If you want to replace this node with another system, enter a new node name. Example display during a network post:
2. Node Membership ID Number	Membership ID assigned to you by the remote node. This is your "User ID" on that system and is not generated by your BBS. There are two ways to obtain it: Request an ID and password from the remote Sysop. Enter "1" to initiate a node application process. When the remote node receives this number on an incoming call, it treats your system as a new node applying for access and assigns a membership ID automatically (see section 4.9.1). If you know your ID number, enter it now. Otherwise, enter 1.
3. City and State	City and State of the remote node. Use a slash to separate the city and state. Do not use commas.
4. Telnet/Phone	Telnet address or phone number used to call the remote node. You may include special dialing prefixes if needed (for example, "t" to force tone dialing). Telnet format: domain:port Example: westwoodbbs.org:64738
5. Password	Password for your account on the remote node. If you were assigned a password, enter it here. If you entered "1" for the membership ID to apply as a new node, enter the password you wish to request. Requirements: 3–9 characters Avoid special characters Lowercase will be converted to uppercase The remote Sysop may accept your requested password or assign a different one.
6. Baud Rate	Baud rate for the remote node. If unknown, enter the highest rate supported by your system. The modem will detect the remote rate and automatically adjust. Billing questions from 8.0/8.1 were removed from setup. To re-enable billing, modify the √sys.net file accordingly.

After saving your entry, one of two things may occur:

• If you entered a Node Membership ID of 1, the system copies your √node app file into √+node x (where x is the node number). Your BBS name is automatically inserted at the beginning because the first line of the node application is used as your system name on the remote node.
  • To override this and present a different name, place the desired name at the beginning of √node app preceded by two CTRL/N characters.

• If you replaced an existing node name with a different one, you may be asked to confirm that you are replacing one node with another. If confirmed, the old node's files are scratched.

When all nodes have been entered, press RETURN at the select node prompt. The required files will be created as needed:

• √ntwrk.parms
• √node list
• √node accounts
• √node billing

Note that the last two files are created only if they do not already exist.

You may alter node information later, but use care. If you change drive assignments, remember to move existing network files from the old drive to the new one. You must shut down the BBS to make changes, so it is recommended to plan changes and apply them together.

One important caution: Do not edit √ntwrk.parms or √node.list with a message editor. These files are not designed to be modified with standard text editing tools and doing so can cause network instability and system errors.

Next Section: Booting Network

Color 64 Network