If PCBoard is unable to safely load, you will receive an error message in the upper left portion of your screen. This error message gives you information about why PCBoard could not load. The following lists each possible error that can occur as PCBoard loads and an explanation of how to fix the problem.

In order for you to see this message, then you must have set the Float Node Number option in PCBSetup > Node Configuration to Y.

A user has attempted to log into the system but there is not a free node on the system for them to log into. Remember that PCBoard will only begin scanning for free nodes from the node number that is specified in PCBSetup > Node Configuration up to your software license limit. In order to check if a node is free, the USERNET.XXX file is scanned.

The only cure for this problem is to free up a node for new users to login or to upgrade your software license limit.

If you check your system and you see that PCBoard thinks people are logged in locally when in reality you know that they are not (because they rebooted their system from the local connection or otherwise improperly exited PCBoard), you need to manually clear out their entries using PCBMONI.EXE.

Load PCBMONI and cursor down to the node number. Next, press the M bar to access the Edit User Net Status screen. In the status field, enter Z for Node is offline. This will clear the entry for that node. The node will then be free for other users to log in to the system.

PCBoard attempted to open the caller log. The log file could not be opened, so an attempt was made to create the file. However, the file could not be created. Since there is no way for to keep track of the calls to the system, the system is not brought online.

The following are all valid reasons as to why the caller log could not be opened/created:

The path specified in PCBSetup > File Locations > System Files does not exist. Since the path does not exist, PCBoard cannot create the caller log file.

If your system is on a network, you may have lost your connection to the server which contains the caller log files. This would mean that the path where your files are normally stored would not exist and consequently the log could not be created.

You do not have enough file handles to open up the caller log. Make sure that you have at least 25 files defined in your CONFIG.SYS (FILES=25) for each node that the machine runs. In addition, also make sure that your server (if you are running on a network) has at least 25 file handles for each node that you are running.

PCBoard attempted to open the default PCBTEXT file defined in PCBSetup > File Locations > System Files but could not open the file. This may mean that you have an invalid path specified in the PCBTEXT field or the path is correct, but there is no PCBTEXT file in the directory. It could also mean that you do not have enough file handles available. Make sure that each node on the computer has at least 25 file handles available via CONFIG.SYS and that your server also has at least 25 file handles for each node that you are running.

You should only see this message if you are using the /M version of PCBoard. It means that the communications port specified in PCBSetup > Modem Information > Modem Setup could not be opened via COMMDRV. A number will be displayed after the error message. To get more information why the port could not be opened, call technical support and give the technician the error message and error number.

Only the /M version of PCBoard will report this error and only if you have configured PCBoard to communicate through the FOSSIL driver (PCBSetup > Modem Information > Modem Setup). PCBoard has attempted to communicate via a FOSSIL driver. However, the information that was returned from the FOSSIL driver was invalid. Make sure that your FOSSIL driver is installed properly.

Anytime that you increase the Number of Highest Conference Desired in PCBSetup > Configuration Options > Messages, you need to update your conference allocations. To do this, you need to load System Manager, select User Info File Maintenance, and finally select Change Conference Allocation.

You will be shown some information about your USERS.INF file. If you do need to upgrade the file to accommodate the increased number of conferences you are told that the file needs to be updated and then are asked if you wish to update the file. By updating the USERS.INF file,. the size of the file on disk will be increased so that information about the new conferences can be stored.

PCBoard uses the language that is defined without a filename extension (usually the default language) to determine the text that should be written to the caller log files. If a language is defined without an extension, PCBoard cannot determine the text that should be written to the log files.

If you receive this error, you need to modify your PCBML.DAT file (PCBSetup > File Locations > Configuration Files) to include a language that has a blank extension. You may have to change the definition of one of the currently defined languages or you may have to install a brand new language to meet this requirement. Until the requirement is met, PCBoard will not load.

If you have answered Y to the Running a Network / Multitasker System in PCBSetup > Node Configuration PCBoard checks to make sure that SHARE is loaded and functioning properly before accepting calls.

If you receive this error message, SHARE.EXE is either not loaded or is not functioning properly. Without SHARE, file access cannot be relegated properly leading to potential corruption of files. Rather than risk data corruption, PCBoard will display this error message and return to the DOS prompt.

Check your configuration to make sure that SHARE.EXE is being loaded in AUTOEXEC.BAT.

In order for PCBoard to be able to operate properly in a multinode configuration it must be able to read and write to the USERNET.XXX file. If you get this error, the location of this file is blank in PCBSetup > File Locations > System Files. Specify a valid path and filename and the error should not reoccur.

The USERS.INF file has been damaged or corrupted in some manner. This may signify a possible file corruption problem on your system (e.g., faulty disk cache, etc.) or a utility may that accesses the USERS.INF file may have damaged the file in some fashion.

About the only thing that you can do (as an immediate fix) is to recreate the USERS.INF file by selecting Create User Info File from System Manager > User Info File Maintenance.

PCBoard determined that you did not have enough memory to create the buffers that it uses for communication buffers. You need to increase the amount of conventional memory that is available before you load PCBoard.

You do not have enough conventional memory available for PCBoard to store the conference strings. You need to increase the amount of conventional memory that is available before you load PCBoard.

There is not enough conventional memory for PCBoard to store the conference flags. Before PCBoard can be loaded, you need to increase the amount of conventional memory that is available before you load PCBoard.

PCBoard determined that you did not have enough conventional memory available to store the message pointers. Before you can load PCBoard, you must increase the amount of conventional memory that is available.

PCBoard attempted to open the communications port specified in PCBSetup > Modem Information > Modem Setup but determined that you do not have COMMTSR loaded. In order for the /M version of PCBoard to run properly, you must have COMMTSR loaded as per the installation instructions in the Multiple Nodes chapter of this manual..

Along with the error message, you will be given an error number. When you call for technical support, please have the error number handy so that the technician will be able to help you solve your problem faster.

You have specified that PCBoard should communicate via the FOSSIL driver that you have installed. However, the FOSSIL driver could not be identified. Make sure that your driver is installed properly.

The COM port that you have specified in PCBSetup > Modem Information > Modem Setup does not exist, or the UART for the COM port is malfunctioning. Check the hardware for your COM port to make sure that it is functioning properly and replace it if necessary.

You have used the /C: command line switch with PCBOARD.EXE but you have not specified a valid port/connect speed for the option. Make sure that your use a valid port speed such as /C:19200, /C:14400, etc.

This error only occurs when using the /M version of PCBoard. In the DAT file that is used to load COMMTSR, there is a setting for the output buffer size. PCBoard determined that the size of the output buffer was less than 2K. Re-run DRVSETUP.EXE to make sure that the settings are correct and save a new DAT file.

You have attempted to load PCBoard, but is already loaded. This is usually caused when you press 5 to shell out to DOS and then execute BOARD.BAT while you are in the shell. To return to PCBoard, type EXIT at the DOS prompt.

PCBoard attempted to open the PCBTEXT file but determined that it could not be opened. This could be due to any of the following reasons:

The path you specified in PCBSetup > File Locations > System Files is invalid or does not exist. Therefore, the PCBTEXT file(s) could not exist in that directory let alone be opened for access.

If you are running in a network configuration, you may have lost your connection to the server thereby making the files on the server unavailable for access. Reconnect to the server (if your PCBTEXT file(s) are stored on the server) and the problem will be corrected.

You may not have enough file handles available to open another file. Make sure that you have allocated enough file handles in your CONFIG.SYS statement. For one node on the machine you should have FILES=25. If you are running 3 nodes on the one machine then you need to have at least FILES=75. If you are in a network configuration, make sure that you have allocated at least 25 file handles for each node.

The default PCBTEXT file that PCBoard loads at startup was determined to be the wrong version. To fix the file, load MKPCBTXT.EXE. When prompted for the filename to edit, specify the full path and filename of your PCBTEXT file. You will then be guided on the steps necessary to fix the file.

Your default PCBTEXT file is an older version which was not designed to run with the version of PCBOARD.EXE that you are running. If you run MKPCBTXT.EXE and specify the filename of your default PCBTEXT file, it will be upgraded.

PCBoard attempted to open the PCBPROT.DAT file but could not locate it, or it could not be opened. The following are some reasons why the file could not be opened:

• The file you specified in PCBSetup > File Locations > Configuration Files is invalid or does not exist.
• If you are running in a network configuration, you may have lost your connection to the server thereby making the files on the server unavailable for access. Reconnect to the server (if your PCBPROT.DAT file is stored on the server) and the problem will be corrected.
• You may not have enough file handles available to open another file. Make sure that you have allocated enough file handles in your CONFIG.SYS statement. For one node on the machine you should have FILES=25. If you are running 3 nodes on the one machine then you need to have at least FILES=75. If you are in a network configuration, make sure that you have allocated at least 25 file handles for each node.

  
  

  UNABLE TO OPEN USERS FILE - RUN PCBSM TO CREATE IT

  PCBoard attempted to load the USER file but could not do so. The file may not exist or the location specified in PCBSetup > File Locations > System Files is incorrect. Other possibilities include not having enough file handles specified in CONFIG.SYS to open the file or having lost your connection to the server (if running a network) where the USERS file exists.

If you do not have a USERS file and need to create it then you should use System Manager to create a new USERS file. If you have a USERS.INF file but no USERS file, then delete the USERS.INF file that remains behind.

Next, load System Manager, and select Users File Maintenance and then select Edit Users File. You will be informed of an error and that you need to create the User Info File this is to be expected. Next, return to the Main Menu and select Users Info File Maintenance and select Create User Info File. You will be asked if you wish to create the file. Answer Y to the question and a new USERS.INF file will be created. You should now have one record in the USERS file which is the SysOp record.

The USERS.INF file could not be opened. If you know that you have a USERS.INF file then this error could be caused by any of the following reasons:

The location of the USERS.INF file specified in PCBSetup > File Locations > System Files is incorrect or invalid. Specify the correct location of the USERS.INF file or make sure that the entry is valid.

If you are using a network then make sure that you have not lost your connection to the server. If you have lost your connection then of course you will not be able to access the USERS.INF file that is stored there.

Make sure that you have enough file handles available. You should allocate at least 25 file handles for each node on the computer and on your server you should allocate 25 handles for each node on your system. This can be done using the FILES= statement in your CONFIG.SYS.

If you need to create a new USERS.INF file then you may do so by loading System Manager, selecting User Info File Maintenance, followed by Create User Info File.

PCBoard attempted to create the USERNET.XXX file used to maintain what each user is doing on the system but was unable to. The file location in PCBSetup > File Locations > System Files may point to an invalid subdirectory or if you are running under a network you may have lost your connection to the server.

Another possibility is that you may not have enough file handles available to open the file. Make sure that each session on your computer has 20 file handles available and that your server has 20 file handles allocated for each node in the system.

PCBoard has determined that the format of the USERNET.XXX file is invalid. It could be that you are using an older version of the USERNET.XXX or it has been corrupted excessively. If you delete the file, PCBoard will recreate the file using the proper format.

When PCBoard attempted to load the USERNET.XXX file into memory there was not enough conventional memory to do so. You need to increase the amount of conventional memory that is available before you load PCBoard.

The USERNET.XXX file could not be opened. It could be that the path to your USERNET.XXX file is incorrect (PCBSetup > File Locations > System Files). Another possibility is that you have lost connection to the server or you may have insufficient file handles available to open the file.

When PCBoard attempted to read the USERNET.XXX file it could not do so or encountered an error of some sort. If you have had disk access problems in the past it may cause this type of error. You could delete the USERNET.XXX file since PCBoard will recreate it and see if that clears anything up. However, it may turn out that this is a symptom of hardware failure on your system.

Nothing can be more frustrating than setting up your system and then realizing that it is not accepting any calls. This sections details some reasons why your system may not be properly answering phone calls.

Normally when a call comes in, PCBoard will display Ring Detected followed by a number which counts down. When you see this message you know that a call was detected and that the two modems are attempting to establish a connection. What if you do not see this message but you know a phone call is coming in? There are two common reasons why this may occur:

Your modem is not properly configured to send RING whenever a call is detected by the modem. Without the modem returning that response code, PCBoard does not know if the phone is ringing or not. Make sure you used PCBModem to configure you modem. It will setup both your hardware and your software to work as PCBoard expects it to work.

You have purchased the /M version of PCBoard but you are running the regular version of PCBoard. The /M version stores the configuration in PCBOARD.DAT as PORTx whereas the normal software stores it as COMx. Because the normal version of PCBoard does not know how to handle the PORTx, it will report No Modem Selected as the communications port. Of course, since no communications port is selected, PCBoard cannot answer the phone.

When a call is detected, PCBoard counts down from the value you entered in Seconds to wait for carrier located in PCBSetup > Modem Information > Modem Setup. As soon as you see the Ring Detected message, PCBoard sends an ATA to the modem signaling that it should answer the call. At this point, it is up to your modem to answer the call properly.

If your countdown goes to 0 for every phone call without getting a connection established then it could be caused by the following reasons:

You have not given the modem enough time to answer the phone. Increase the Seconds to wait for carrier so that your modem has enough time to answer the call.

If your RS-232 cable is not wired correctly then the PCBoard may never realize that the connection has been established. In order for a connection to be realized as valid, PCBoard waits for the CONNECT message from the modem and also checks the CD (carrier detect) line to make sure that connection really exists. If your CD line is not wired properly (or not wired at all) in your RS-232 cable then the connection may never be considered valid. The easiest solution to this problem is to make sure that your cable has all 25 pins wired straight through.

Anytime PCBoard cannot send the initialization string at the call-waiting screen you will receive a Modem Reset Error which is signified by a low-tone beep and a message. Before ever sending the initialization string though, an AT is sent to the modem. PCBoard then expects an OK to be returned from the modem. If that OK is not received within approximately 25 seconds then PCBoard will report that there was a modem reset error.

If the error occurs when you load PCBoard for the first time, this usually signifies that your hardware and software are not configured properly. First, make sure the right communications port is being opened. If that all checks out, then it may mean that you have an IRQ conflict in your system which will prohibit communications with the devices that are using the same IRQ.

Another possibility is that your initialization string contains a command which is not recognized by your modem. Check your initialization string in PCBSetup to make sure that all commands in your initialization string are valid.

If you get modem reset errors after users have logged into your system, it could be caused by any of the following reasons:

You have loaded another application which access the same COM port as the node that is giving you the errors. You may have also accessed a port which uses the same IRQ. That would mean the other application stole away the IRQ – meaning PCBoard would not be able to communicate with the modem.

Your modem may be malfunctioning. It is not uncommon for modems to malfunction. One solution may be to turn your modem off and back on again to see if that has any effect on the situation. Aside from that, there is not much you can do but to have your modem checked.

A common question among SysOps is why did my date not change at midnight the night before? You may be inclined to blame PCBoard for not changing the date, but in reality PCBoard has nothing to do with changing the date at midnight.

The responsibility of changing the system date lies with the the software that reads the BIOS clock ticks. PCBoard does not read the BIOS clock ticks, therefore it is not responsible for changing the date. It is quite common for some TSRs to monitor time in this fashion and to not properly update the date. Therefore, you may want to begin by systematically removing the TSRs on your system to see if any of them may be the cause of the problem.

Because something else is reading the BIOS clock ticks the CPU may be too busy to change the system date. That is the real reason your system date is not changing at midnight.