Network troubleshooting
Color 64 Network - Troubleshooting
This troubleshooting section is far from complete. The table below covers the most common problems that new Network SYSOPs have.
| Question | Answer |
|---|---|
| After I boot up and answer the "regenerate message index" question, I get a FILE NOT FOUND error and the BBS attempts to reboot. | This means that a main module is missing or cannot be found. Make sure that the two main modules, √bbs.nw1 and √bbs.nw2 are located on your PROGRAMS drive.
If your Program drive is in RAM, there are two things to watch for. One, make sure that these two modules did in fact get loaded into RAM properly. For RAMDOS users, the file called "√sys.ramove" is the means of storing these modules into RAM. Refer to "Booting the BBS with Network" for more info. The second problem may be free memory in RAM. A 1764 (with 256K ram) might be pressed for free space. The two modules may be named improperly. The first eight characters must be named √bbs.nw1 and √bbs.nw2 for the BBS to find these modules. |
| When someone sends a public or private message and I reply to it, instead of replying through the network, it tries to reply locally on the BBS. | Don't feel bad as this happens a lot. You need to brush up on the section of setting access levels for node accounts. Remember that you can have an incoming node be replyable or NON-replyable. |
| When booting up my BBS, halfway into the start of it, I get a crash with "?file data error". | What this most likely means is that either your √ntwrk.parms file or your √node list file got trashed. Review the section on using the Net Setup program.
If you determine that your file is indeed trashed, and you never made a backup, you probably won't be able to salvage the file, but you may be able to get some valuable information from it, by reading the file with the BBS DOS f: feature, and jotting down any recognizable data, then scratching the file and starting anew. √ntwrk.parms format (per line and no empty lines) is as follows:
|