Network troubleshooting
Color 64 Network - Troubleshooting
This troubleshooting section is not exhaustive. The table below addresses the most common problems encountered by new Network Sysops.
| Question | Answer |
|---|---|
| After booting and answering the "regenerate message index" prompt, I receive a FILE NOT FOUND error and the BBS attempts to reboot. | This usually indicates that a required Network module is missing.
Verify that the two primary modules, √bbs.nw1 and √bbs.nw2, are located on your PROGRAMS drive. If your PROGRAMS drive is loaded into RAM:
Also confirm that the filenames are correct. The first eight characters must be exactly √bbs.nw1 and √bbs.nw2. If renamed or truncated incorrectly, the BBS will not locate them. |
| When replying to a public or private network message, the reply attempts to post locally instead of going through the network. | This is typically caused by incorrect node access level configuration.
Review the “Node Access Levels” section. Incoming nodes must be configured as replyable in order for replies to route back through the network. If the access level is set incorrectly, replies will default to local posting. |
| During BBS startup, the system crashes with "?file data error". | This usually indicates corruption of either the √ntwrk.parms file or the √node list file.
Review the Net Setup section to verify configuration. If the file is corrupted and no backup exists, recovery may not be possible. However, you may attempt to extract usable information by:
The √ntwrk.parms file format (no blank lines) is structured as follows:
|