This utility will encrypt your user file to prevent any unauthorized persons who get hold of your user file from obtaining useful information from it.
PCBoard and System Manager will automatically unencrypt the file when they open the file. The following fields are encrypted:

• password
• city
• data/business phone number
• home/voice phone number
• comment1
• comment2

To encrypt the user file, you must first encrypt your user file using the ENCRYPT program using the following syntax:

ENCRYPT [location of user file]

If your user file is stored in C:\PCB\MAIN\USERS, you would enter the following:

ENCRYPT C:\PCB\MAIN\USERS

Once the user file has been encrypted, you must inform PCBoard that the user file is encrypted. If you skip this step, these fields will appear to be filled with garbage and you can damage your user file. To update PCBoard, answer Y to the Encrypt Users File question in PCBSetup > Configuration Options > System Control.

The USERS.SYS and DOOR.SYS files that are created by PCBoard will have decrypted values so that doors which read these files will continue to operate properly. Any third-party programs which read the user file directory most likely will not work with the encrypted file and may end up damaging your user file.

WARNING: You must enable encryption on all nodes that will be accessing an encrypted user file. If you do not, you may damage your user file.

If you would like to decrypt the user file, use the ENCRYPT program with this syntax:

ENCRYPT /D [location of user file]

For example, if your user file is stored in H:\PCB\MAIN\USERS, you would enter the following:

ENCRYPT /D H:\PCB\MAIN\USERS

Encrypting the user file is most useful when you operate in a large network environment where users may be able to directly access the user file. By encrypting the user file, you can protect the accounts on the system because they cannot be viewed using a file viewing program.

The main PCBoard executable file is overlaid. This means that only a portion of the executable is in memory at any given time. How much of the executable can be held in memory depends on two factors: 1) How much of it is resident (not in the overlay) and 2) How big the overlay buffer is. You can determine how big of an overlay buffer you want to set for each executable using this utility.

A setting of 16 sets up a 64K overlay buffer. This setting allows PCBoard to swap pieces of the executable file in and out of memory keeping up to 64K of it in the overlay buffer.

  OVLSIZE [filename] [buffer size]

The following chart in this section will show you the valid buffer sizes that you may select:

A higher value allows more of the executable file to be held in memory. The highest possible value, of course, would simply load the entire executable file into memory and would never access the hard disk. An overlay buffer of this size would be wasteful of memory.

Lower values may hurt performance by causing PCBoard to continually swap code in from disk - creating more disk activity than would otherwise be necessary.

You may want to use a smaller value such as 16. This lets PCBoard pull in the code that is running, when it is needed, and leave the rest of the code on disk until it is needed.

Allowing you to pick the buffer size allows you to tune your system to meet your memory and performance needs. If you need more memory, go for a lower overlay buffer size. If you need more performance, go for a higher buffer size.

NOTE: The minimum value that you should select is 14 for PCBoard to operate properly. If you plan to execute any PPE files, the minimum value you should select is 16.