Network maintenance: Difference between revisions

From Color 64 BBS Wiki
Created page with "Color 64 Network - <strong>Network Maintenance</strong> This is your Network Maintenance menu and below that are the options and their descriptions.  center|250px {| class="wikitable |- |+Network Maintenance Functions & Descriptions ! Menu Command ! Screenshot ! Command Description |- | 1: Node Status Report | center|200px | Displays status and allows you to LOCK or UNLOCK a node. When lo..."
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Network64|Color 64 Network]] - <strong>Network Maintenance</strong>
[[Network64|Color 64 Network]] - <strong>Network Maintenance</strong>


This is your Network Maintenance menu and below that are the options and their descriptions. 
This is the Network Maintenance menu. The available options and their descriptions are shown below.


[[File:networkmaintmenu.png|center|250px]]
[[File:networkmaintmenu.png|center|250px]]


{| class="wikitable
{| class="wikitable"
|-
|-
|+Network Maintenance Functions & Descriptions  
|+ Network Maintenance Functions & Descriptions
! Menu Command
! Menu Command
! Screenshot
! Screenshot
! Command Description
! Command Description
|-
|-
| 1: Node Status Report  
| 1: Node Status Report
| [[File:nodestatusreport.png|center|200px]]
| [[File:nodestatusreport.png|center|200px]]
| Displays status and allows you to LOCK or UNLOCK a node.
| Displays the current status of all nodes and allows you to LOCK or UNLOCK individual nodes.


When locking a node, if there are any messages, they will not go out under any circumstances. Additionally, you will not be allowed to post a message to that node. You will first be shown all the nodes with their stats, and after the listing if you hit RETURN, you'll go back to the menu.  If you enter a node number, you'll be given a chance to Lock or Unlock one or more nodes.  
If a node is locked:
* No outgoing messages will be sent to that node.
* You will not be allowed to post new messages to it.


There are two other ways a node can become locked: ACCESS and CARRIER, which are done automatically. 
Upon entering this option, all nodes and their statistics are displayed. Press RETURN to go back to the menu. Enter a node number to toggle the lock status of one or more nodes.
* ACCESS means that the node was called, and you were denied access for some reason.  
 
* CARRIER is when you have selected the special response code setting in Net Setup. This means that you called a node, and your modem returned a NO CARRIER (indicating that the node did not pick up, or no answer, or voice).
Nodes may also become locked automatically under the following conditions:
* '''ACCESS''' – The system attempted to call the node but was denied access.
* '''CARRIER''' – Enabled through Net Setup special response handling. This occurs when a call attempt results in a NO CARRIER response (no answer or modem did not connect).
|-
|-
| 2: Node Account File Edit  
| 2: Node Account File Edit
| [[File:nodeaccountfileedit.jpeg|center|200px]]
| [[File:nodeaccountfileedit.jpeg|center|200px]]
| This is where you go to edit your incoming node accounts. Everything here is straight forward. See section 4.10, Incoming Node Accounts, for more information on exactly what you'll need to do at this editor.  
| Used to edit incoming node account records. This section manages the credentials and access information for remote systems calling your BBS.
 
Refer to section, ''Incoming Node Accounts'', for detailed information about the fields and procedures used in this editor.
|-
|-
| 3: Attach a File to Send  
| 3: Attach a File to Send
| [[File:netfilesend.jpeg|center|200px]]
| [[File:netfilesend.jpeg|center|200px]]
| This option allows you to send a PRG or SEQ file to another node. The node must be running Network 1.26 or 1.26a for this to work. If you try to send a file to a Network 1.24 node, your BBS will discover this fact and hang up.  
| Allows you to send a PRG or SEQ file to another node. The receiving node must be running Network 1.26 or 1.26a. If a remote system is running Network 1.24, the transfer will be aborted.
 
Steps:
 
* Enter the device number where the file resides. You may enter the ">" character instead to access a Mini-DOS. The Mini-DOS allows drive switching, directory viewing, and reading SEQ files. Press RETURN to exit Mini-DOS.
* Enter the drive number, drive command, and file name exactly as it appears on disk.
* Enter the destination node number, or enter "?" to list nodes. You may also enter "x" to use the default file send feature.
 
You will be asked whether the file should be deleted after transmission.
 
Next, enter the filename to be used on the receiving node. Press RETURN to use the same name as on your disk.


Steps to utilize this option are as follows:
If a file description exists, you will be prompted to include it.
* Enter the device number of the file you want to send.  From here, you may choose to enter the '>' character instead, taking you to a Mini-DOS.  This Mini-DOS only lets you switch drives, read directories, and view SEQ files.  Enter RETURN to exit. 
* Enter the drive number, drive command, and file name as it appears on your disk. 
* Enter the node number you wish to send the file to.  Enter the number or enter '?' for a list of nodes.  You may also choose to enter 'x' for a default file send.  


The BBS will query if you would like the file to be deleted after it is sent.
A file named "√+file x" (where x is the node number) is created on your Network drive. This file stores the transmission information.


You are then prompted for the file name for the receiving node.  If you press only RETURN, it will use the same name as the file is on your disk. 
Transfer guidelines:


If a file description is found for the file you are sending, you will be asked if you would like to have it sent also.  
* Do not exceed 20 files per call.
* Network v1.26 nodes enforce an 18-minute transfer limit.
* At 2400 baud, approximately 450 blocks can be transferred in 18 minutes.
* At 1200 baud, limit file size to approximately 250 blocks.
* If both systems are running v1.26a (Color 64 v8 includes v1.26a), there is no enforced file size limit. However, practical limits of 1000 blocks or less are recommended.


A file named "√+file x", where 'x' is the node number, will appear on your Network drive.  This file contains all the information that you just entered.  The BBS does not limit the number of files that you may send; however, you should not exceed 20 files at a time.  For v1.26 nodes, there is an 18-minute limit on transfer time.  At 2400 baud, about 450 blocks can be transferred in 18 minutes.  A v1.26 node will not be able to receive files larger than 450 blocks.  If you or the v1.26 node only runs 1200 baud, limit the file size to about 250 blocks.  If both you and the remote node are running v1.26a (Color 64 version 8 includes v1.26a), then there is no limit placed on the size of the files, although you should limit file sizes to 1000 blocks or less for practical reasons.  It is not required that you send a message with the file, but on the other hand, you may send one. Messages and files will be sent during the same call.  
You are not required to send a message with a file, but you may do so. Messages and files are transmitted during the same call.
|-
|-
| 4/5: Read Receive and Send Logs  
| 4/5: Read Receive and Send Logs
| [[File:netlogs.jpeg|center|200px]]
| [[File:netlogs.jpeg|center|200px]]
| These options will display the "√slog" and "√rlog" files. These files provide a more detailed description of file transfers. After viewing one of these logs, you will be asked if you want to clear it. It's best to clear these files after you read them or they will just continue to grow.  
| Displays the contents of the "√slog" (send log) and "√rlog" (receive log) files. These logs provide detailed information about network transfers.
 
After viewing a log, you will be prompted to clear it. It is recommended to clear these logs periodically to prevent them from growing excessively.
|}
|}
Next Section: [[node accounts|Node Accounts]]
Next Section: [[node accounts|Node Accounts]]


[[Network64|Color 64 Network]]
[[Network64|Color 64 Network]]

Latest revision as of 22:22, 27 February 2026

Color 64 Network - Network Maintenance

This is the Network Maintenance menu. The available options and their descriptions are shown below.

Network Maintenance Functions & Descriptions
Menu Command Screenshot Command Description
1: Node Status Report
Displays the current status of all nodes and allows you to LOCK or UNLOCK individual nodes.

If a node is locked:

  • No outgoing messages will be sent to that node.
  • You will not be allowed to post new messages to it.

Upon entering this option, all nodes and their statistics are displayed. Press RETURN to go back to the menu. Enter a node number to toggle the lock status of one or more nodes.

Nodes may also become locked automatically under the following conditions:

  • ACCESS – The system attempted to call the node but was denied access.
  • CARRIER – Enabled through Net Setup special response handling. This occurs when a call attempt results in a NO CARRIER response (no answer or modem did not connect).
2: Node Account File Edit
Used to edit incoming node account records. This section manages the credentials and access information for remote systems calling your BBS.

Refer to section, Incoming Node Accounts, for detailed information about the fields and procedures used in this editor.

3: Attach a File to Send
Allows you to send a PRG or SEQ file to another node. The receiving node must be running Network 1.26 or 1.26a. If a remote system is running Network 1.24, the transfer will be aborted.

Steps:

  • Enter the device number where the file resides. You may enter the ">" character instead to access a Mini-DOS. The Mini-DOS allows drive switching, directory viewing, and reading SEQ files. Press RETURN to exit Mini-DOS.
  • Enter the drive number, drive command, and file name exactly as it appears on disk.
  • Enter the destination node number, or enter "?" to list nodes. You may also enter "x" to use the default file send feature.

You will be asked whether the file should be deleted after transmission.

Next, enter the filename to be used on the receiving node. Press RETURN to use the same name as on your disk.

If a file description exists, you will be prompted to include it.

A file named "√+file x" (where x is the node number) is created on your Network drive. This file stores the transmission information.

Transfer guidelines:

  • Do not exceed 20 files per call.
  • Network v1.26 nodes enforce an 18-minute transfer limit.
  • At 2400 baud, approximately 450 blocks can be transferred in 18 minutes.
  • At 1200 baud, limit file size to approximately 250 blocks.
  • If both systems are running v1.26a (Color 64 v8 includes v1.26a), there is no enforced file size limit. However, practical limits of 1000 blocks or less are recommended.

You are not required to send a message with a file, but you may do so. Messages and files are transmitted during the same call.

4/5: Read Receive and Send Logs
Displays the contents of the "√slog" (send log) and "√rlog" (receive log) files. These logs provide detailed information about network transfers.

After viewing a log, you will be prompted to clear it. It is recommended to clear these logs periodically to prevent them from growing excessively.

Next Section: Node Accounts

Color 64 Network

Retrieved from "https://www.color64wiki.itchybutt.org/index.php?title=Network_maintenance&oldid=902"