Tricarb Monitor system settings

In order to change these settings, you must run Tricarb Monitor with the /SYSOP command line switch to get in the SYSOP mode. Either use the File|Run command of your Program Manager, or use the DOS box. In both cases, enter the following command:

      C:\>\tricarb\tricarb /SYSOP
    

Tricarb will now let you access the System menu. Please perform the customizations described in the following sections, using the commands of the System menu.

Output directory

Please enter the path to your data directory. This is the directory that you created in the step Installation-Prepare Directory Structure and will most probably be C:\TRICARB\DATA. All measured data will be placed in subdirectories of the data directory.

COM Settings

Use this dialog box to define the COM port parameters for the communication between the computer running Tricarb Monitor and the Tricarb counter. The following default values are preset and must not be changed except the Baud Rate:

The first setting usually needs not be changed unless you experience any communication failures. The last setting must match the hardware connection. E.g. use COM2 if your mouse is already connected to COM1.

Log options

Tricarb Monitor writes a log file with the time and date of all important events that happen while it is online. The log file is located in the data directory. Use this dialog box to choose what you want to be logged. The following events may be selected or deselected by the corresponding checkboxes:

Another checkbox allows you to limit the size of your log file. If the option is checked, the list will be trimmed to the last n entries, where n is the number in the corresponding edit field. If you e.g. limit the size to 100 entries, the log file will always show the most recent 100 entries with the oldest entries being deleted as new ones are added. If the option is deselected, the log file will grow to its maximum size of 64K. Then the file will be copied to a backup file, and the log file starts again with zero entries. If this happens again, the backup will be overwritten, so it is the sysops task to backup the backup in time if this should be necessary.