Exiting And Checking Your Configuration
To exit PCBSetup you need to press E at the Main Menu. When you do, you will be asked if you wish to save your configuration. The following describes each option available to you:
| N | Do not save any changes you have made to your PCBOARD.DAT file and exit. Any changes you have made to the fields in your conference configuration are automatically saved whenever you exit the conference screen. |
| Q | Save all changes to your configuration without checking the validity of the paths and drives in your configuration. This will probably be the selection you will use most, because it is quicker then checking your entire configuration each time you exit PCBSetup. |
| Y | Saves all changes to your configuration and checks all paths and drives to make sure they exist. In addition, your CNAMES file will be updated for those utilities that use CNAMES instead of CNAMES.@@@ and CNAMES.ADD for conference information. If you have any conferences that do not have message bases, the message bases will be initialized for you. The following section describes in more detail what will occur when you select either Y (full save) or Q (quick save) when asked if you wish to save your changes. |
Full Save
PCBoard divides the checking of your system into four sections. At any section you can press E to skip over any of the following sections:
Checking Directories While Saving Files
At this junction, PCBoard is going to check the drives and paths in your configuration to make sure they are all valid. All filenames and paths listed in all setup screens will be checked to make sure they exist (including conference information)
If a path does not exist, you will be shown the path that does not exist, and then asked if you wish to create it. If a drive does not exist, you will be shown which invalid drive you had in your configuration.
If the invalid path is in one of your conferences, you will be told what conference and what question has the invalid path. With this in mind, you can quickly and easily fix your configuration to point to a proper path if you need to.
Checking BLT.LST file(s)
When you see this on your screen, PCBSetup is checking the bulletins defined in each conference's BLT.LST file. Only the paths to each bulletin are checked for validity. If the actual bulletin does not exist, nothing is printed to the screen by PCBSetup.
To help speed things up, PCBSetup is smart enough to know when it has checked a BLT.LST before and will skip it. This will save you an immense amount of time especially if you have numerous conferences using the same BLT.LST file.
Checking DIR.LST file(s)
When you see this on your screen, PCBSetup is checking the file directories defined in each conference's DIR.LST file. Only the paths to each DIR (description) file and attached subdirectory are checked for validity. If the DIR file does not exist, nothing is printed to the screen by PCBSetup.
To help speed things up, PCBSetup is smart enough to know when it has checked a DIR.LST before and will skip it. This will save you an immense amount of time especially if you have numerous conferences using the same DIR.LST file.
Checking SCRIPT.LST file(s)
When you see this on your screen, PCBSetup is checking the scripts defined in each conference's SCRIPT.LST file. Only the paths to each script are checked for validity. If the actual script file does not exist, nothing is printed to the screen by PCBSetup.
To help speed things up, PCBSetup is smart enough to know when it has checked a SCRIPT.LST before and will skip it. This will save you an immense amount of time especially if you have numerous conferences using the same SCRIPT.LST file.
Checking DLPATH.LST file(s)
When you see this on your screen, PCBSetup is checking each path listed to insure that they are valid paths on your system. If you have specified an index file in your DLPATH.LST file, it will only check to insure that the path that points to your index file is valid.
To help speed things up, PCBSetup is smart enough to know when it has checked a DLPATH.LST before and will skip it. This will save you an immense amount of time especially if you have numerous conferences using the same DLPATH.LST file.
Quick Save
A quick save is by far the quickest way to save your configuration. When you choose to save your configuration in quick mode, your configuration is not checked to make sure that all paths are valid. Instead, it simply copies the values that were in memory at the time you exited the program and writes them out to memory.