File Storage
Introduction - File Storage Drives
Now that you have all your hardware together, it is time to decide how Color 64 will be able to store all its files.
The BBS program divides up external storage into "drives" (short for "disk drive"). In these instructions, a drive is a generic term used to refer to any type of external storage. For example, a drive can be a 1541 floppy disk drive, a CMD HD 16-megabyte partition, a 2-megabyte REU, or any other separate and isolated area where files can be stored.
On the drives are stored "groups" of files. A files group is a collection of files that have a common function. Each group of files must be together in a designated drive area. For example, the Public Messages group is the group of all the public messages posted by the users on a BBS system and a single drive should be designated for this group. You can have several groups on one drive if space permits.
| Drive | Group Assignment (Example Only!) |
|---|---|
| 8 (1541) | Boot, Program |
| 9 (1581) | System, Help, Text, Aux1, Aux3 |
| 10 (1581) | Private & Public Messages |
| 11 (1571) | Password, Caller Log |
Note that all file groups must always be accessible to Color 64, which means that you cannot use a "disk-swapping" method of changing disks in a drive as the system is running.
If I refer to a "Program Files drive" this means the DRIVE that the Program Files are stored on. This same terminology applies to the other files groups, because it allows for the possibility that you are storing more than one group of files on a single drive. For example, the System Files drive could also be the Help Files drive, but only if both groups are stored on the same drive.
The table below denotes the groups used by Color 64. Some groups have a "recommended minimum storage space" listed, which is just a recommendation on how many free blocks you should start out with for that group, and the space used at install:
| Group | Description | Files | Size |
|---|---|---|---|
| Boot | Contains all the files necessary to start up the Color 64 program, along with all the utilities like SETUP, password tools, menu maker, etc. If you have enough room (e.g. a 1571 or 1581 partition on an HD), you should put these files with your Program Files. It is required that these files be accessed only on drive 0 or drive 1 (LU 0 or LU 1 of a Lt. Kernal) of a disk drive. Also, the files should NOT be stored in a subdirectory (as on CMD drives). Note 1:These files are tools that can assist you for specific functions, but can be stored on a separate drive, if needed. Just ensure before they are run that your program drive is inserted. |
|
|
| Program | Contains all your main overlays, your "√bbs.parms" (parameters) file, plus any extra ML files required for use with your system. Usually this means all the files that are preceded with the "√bbs" prefix. One notable exception to this is the √bbs.games overlay which goes to the AUX3 designated drive. It is also recommended, but not required, that you include the BBS Boot Files with your Program Files. If you are going to run a full system, the Program Files should have at least 1000 blocks of total space on it (a double sided 1571 disk would be the minimum floppy disk); Otherwise, you *may* be able to fit your overlays onto a 1541 floppy, but only if you do not use either the "√bbs.ov2" and "√bbs.ov3" overlays, or you do not use the Network overlays. It is required that the Program Files be stored only on drive 0 or drive 1 (LU 0 or LU 1 of a Lt. Kernal) of a disk drive. Also, the files should NOT be stored in a subdirectory (as on CMD drives). Note 1:√bbs.ov2 is not currently used and could be omitted until you desire some sort of expansion in functionality. Note 2:√sys.edit would only be required if you desire to use the stand-alone editor (+editor) Note 3:√bbs.term and √bbs.trmml would only be required if you desire to use the built-in terminal for outbound calls or easy modem communications. |
|
|
| System | Contains all the non-program files that are used by the main BBS system. This includes menu files, data files, relative files, etc. The drive that the System Files are stored on must be able to support storage of relative files. | Minimum 300 blocks recommended | |
| Help | Contains all the files which a caller can read to get help using the BBS system. | Sysop Determined | |
| Text | Like Help Files, this contains all the other files (such as Commodore Graphics files) that a caller can read for information or for recreation. If you wish, you can combine this section and the Help Files section to keep all your text files in one area, or you can even choose not to have any Text Files. | Sysop Determined | |
| Password | Contains your password file, the file that contains the information for all your BBS system callers. When the file is first created, enough space is opened to allow for the maximum number of callers that you think you will ever have. You should always have enough space in the password file to allow for new users, otherwise you can get unpredictable results. About 1 block is allocated for each caller, so if you were to set the maximum to 300, the password file will be more than 300 blocks. Thus, you may wish to put this file on its own drive. The drive that you put the password file on MUST be able to store relative files. | √password file | Dependent on maximum # of users: ~1 block per user |
| Private Msgs | Contains all the private E-mail that callers send to each other. You can also add special modules to your system which will use this area for anything that is privately assigned to a specific caller. | Minimum 300 blocks recommended | |
| Public Msgs | Contains the public messages that are posted by callers. Public messages networked to your system are also stored here. | Minimum 500 blocks recommended | |
| Caller Log | Contains the caller log, which is a text file containing the record of all activity on the system, including your own. The activity is stored in the form of the commands and text that is entered by a caller. You can decide on two ways to store the caller log. You can have the log stored separately for each day of activity, or you can have just one file with the most recent activity printed on it. Either way, you will be able to set the maximum size of the file, along with the option of trimming the file when it is too large. This file must be stored on drive 0 of a disk device. This means drive 0 of a dual drive such as the MSD-SD2, or it means LU 0 of the Lt. Kernal HD. Devices such as the 1541 or CMD HD are unaffected because the 1541 is a single drive device and the CMD HD uses 0 to refer to the current selected partition. | √caller log | Sysop Determined |
| Aux1 | New to Color 64 8.1.0a is the User Profile area of Aux 1. This will hold user-specified unique items for their profile and has the capacity to hold 2 files per user: Their signature and their welcome banner. If you are tight on space, you can remove this option in your BBS SETUP by disabling the Spare 2 command. If you decide to disable, you can also remove the √bbs.profile from the programs drive. | Varies by # of users and use of the function. | |
| Aux3 | New to Color 64 8.1.0a is the Aux3 Games area. The number of games depends on you or you can disable this area entirely by removing the option in your BBS SETUP by disabling the Spare 1 command. |
|
Approx 25 blocks + games |
| Network | If you choose to participate in a Color 64 network with other BBS systems, the needed files and generated data files will require a minimum of 1000 blocks. |
|
Minimum 1000 blocks |
Next Section: Different Configurations