Filestorage: Difference between revisions

From Color 64 BBS Wiki
← Older edit
m Protected "Filestorage" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
Now that you have all your hardware together, it is time to decide how Color 64 will be able to store all its files.
{{DISPLAYTITLE:File Storage}}
[[Introduction|Introduction]] – '''File Storage Drives'''


Once your hardware is assembled, the next step is determining how Color 64 will organize and store 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.
The BBS divides external storage into logical “drives.” In this documentation, a drive refers to any isolated storage area, regardless of hardware type. A drive may be:


* A 1541 or 1571 floppy disk drive
* A 1581 disk drive
* A CMD HD partition
* An REU configured as a RAM disk
* Any other dedicated storage area


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. 
Each drive contains one or more file groups. A file group is a collection of related files serving a common function. Every group must reside together on a designated drive area.


{| class="wikitable
For example, the Public Messages group contains all public posts made by users and should reside on a single drive. If sufficient space is available, multiple groups may share the same drive.
 
----
 
{| class="wikitable"
|-
|-
|+Drive Group with Drive Assignment  
|+ Example Drive Group Assignment
! Drive
! Drive
! Group Assignment (Example Only!)
! Group Assignment (Example Only)
|-
|-
|8 (1541)  
|8 (1541)
|Boot, Program  
|Boot, Program
|-
|-
|9 (1581)  
|9 (1581)
|System, Help, Text, Aux1, Aux3  
|System, Help, Text, Aux1, Aux3
|-
|-
|10 (1581)  
|10 (1581)
|Private & Public Messages  
|Private & Public Messages
|-
|-
|11 (1571)  
|11 (1571)
|Password, Caller Log  
|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.
----


All file groups must remain accessible while the BBS is running. Disk swapping is not supported once the system is active.


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.  
When referring to a “Program Files drive,” this means the drive on which the Program group resides. The same terminology applies to all file groups. Multiple groups may share a drive if space allows.


Below is a description of the file groups used by Color 64. Recommended minimum storage values are provided as general guidance.


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:
----


{| class="wikitable
{| class="wikitable"
|-
|-
|+Approximate Storage Space of Files
|+ Approximate Storage Space of Files
! Group
! Group
! Description
! Description
! Files
! Files
! Size
! Approximate Size
|-
|-
| Boot
|'''Boot'''
| <p>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).</p>  
|Contains startup files and utilities such as SETUP, password tools, and system loaders.<br>
Must reside on drive 0 or drive 1 (LU 0 or LU 1 on Lt. Kernal).<br>
<p>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. </p>
Must not be placed in a subdirectory.
| <ul style="list-style: none;">
|
<li>Bootmaker </li>
Bootmaker<br>
<li>√sys.loadml </li>
√sys.loadml<br>
<li>√sys.mlinit </li>
√sys.mlinit<br>
<li>√sys.mlnorm </li>  
√sys.mlnorm<br>
<li>√sys.setup </li>
√sys.setup<br>
<li>+bbs </li>
+bbs<br>
<li>addt’l “+” files</li>
Additional “+” utilities<br>
<li>----------- </li>
dir.rename<br>
<li>1:dir.rename</li>  
Directory tools<br>
<li>1:dir tools</li>
Password tools<br>
<li>1:pswd tools</li>
Menu maker
<li>1:menu maker</li> </ul>
|
|<ul style="list-style: none;">
Approx. 200 blocks<br>
<li>Approx 200 Blocks</li>
Utilities approx. 70 blocks
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>----------- </li>
<li>Approx. 70 blocks</li></ul>
|-
|-
|Program
|'''Program'''
|<p>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). </p>
|Contains main overlays, √bbs.parms, and required ML files.<br>
 
Must reside on drive 0 or drive 1.<br>
<p> Note 1:√bbs.ov2 is not currently used and could be omitted until you desire some sort of expansion in functionality.</p>
Must not be stored in subdirectories.
<p> Note 2:√sys.edit would only be required if you desire to use the stand-alone editor (+editor)</p>
|
<p> 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.</p>
√bbs.init<br>
|<ul style="list-style: none;"><li>√bbs.init</li>  
√bbs.msgs<br>
<li>√bbs.msgs</li>  
√bbs.xfer<br>
<li>√bbs.xfer</li>  
√bbs.ovl<br>
<li>√bbs.ovl</li>  
√bbs.ov3<br>
<li>√bbs.ov3</li>  
√bbs.profile<br>
<li>√bbs.profile</li>  
√bbs.ansi<br>
<li>√bbs.ansi</li>
√bbs.ascii<br>
<li>√bbs.ascii</li>
√bbs.punt<br>
<li>√bbs.punt </li>
√bbs.xmoc<br>
<li>√bbs.xmoc </li>
√bbs.parms<br>
<li>√bbs.parms</li>
<br>
<li>-----------------</li>  
Optional:<br>
<li>Optional files:</li>  
√bbs.ov2<br>
<li>1:√bbs.ov2 </li>  
√sys.edit<br>
<li>2:√sys.edit </li>  
√bbs.term<br>
<li>3:√bbs.term</li>  
√bbs.trmml
<li>3:√bbs.trmml</li></ul>
|
|<ul style="list-style: none;"><li>Approx. 450 blocks</li>
Approx. 450 blocks<br>
<li>.</li>
Optional files approx. 190 blocks
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li>---------</li>
<li>Approx. 190 blocks </li></ul>
|-
|-
|System
|'''System'''
|Contains all the non-program files that are used by the main BBS system.  This includes menu files, data files, relative files, etc. <u>The drive that the System Files are stored on must be able to support storage of relative files.</u>
|Contains menus, data files, and relative files used by the BBS.<br>
The drive storing System files must support REL files.
|
|
|Minimum 300 blocks recommended
Menu files<br>
Data files<br>
REL files
|
Minimum 300 blocks recommended
|-
|-
|Help
|'''Help'''
|Contains all the files which a caller can read to get help using the BBS system.  
|Caller-accessible help documentation.
|Sysop Determined
|
Help files (Sysop defined)
|
|
Sysop determined
|-
|-
|Text
|'''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.  
|Additional readable files such as graphics or informational documents.<br>
|Sysop Determined
May be combined with Help if desired.
|
Text files (Sysop defined)
|
|
Sysop determined
|-
|-
|Password
|'''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. <u>The drive that you put the password file on MUST be able to store relative files.</u>
|Stores user account records.<br>
|√password file
Approximately 1 block allocated per user.<br>
|Dependent on maximum # of users: ~1 block per user
The drive must support REL files.
|
√password
|
Approximately 1 block per user
|-
|-
|Private Msgs
|'''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. 
|Stores private email between callers.
|
Private message files
|
|
|Minimum 300 blocks recommended
Minimum 300 blocks recommended
|-
|-
|Public Msgs
|'''Public Msgs'''
|Contains the public messages that are posted by callers.  Public messages networked to your system are also stored here.
|Stores public posts and networked messages.
|
|
|Minimum 500 blocks recommended
Public message files
|
Minimum 500 blocks recommended
|-
|-
|Caller Log
|'''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.  
|Stores caller activity logs.<br>
|√caller log  
Must reside on drive 0 (or LU 0 on Lt. Kernal).
|Sysop Determined
|
√caller log
|
Sysop determined
|-
|-
|Aux1
|'''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.  
|User Profile area (v8.1.0a).<br>
Stores signatures and welcome banners.<br>
May be disabled in SETUP (Spare 2).
|
|
|Varies by # of users and use of the function.
User signature files<br>
User banner files<br>
√bbs.profile
|
Varies by number of users
|-
|-
|Aux3
|'''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.  
|Games area (v8.1.0a).<br>
|<ul style="list-style: none;"><li>√bbs.games </li>
May be disabled in SETUP (Spare 1).
<li>√bbs.menu</li>  
|
<li>… games</li></ul>
√bbs.games<br>
|Approx 25 blocks + games
√bbs.menu<br>
Game files
|
Approx. 25 blocks plus games
|-
|-
|Network
|'''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.  
|Not needed unless you plan to participate in a Color 64 network.<br>
|<ul style="list-style: none;"><li>Programs Drive: </li>
Includes network overlays and generated data files.
<li>√sys.net </li>
|
<li>√bbs.nw1 </li>
√sys.net<br>
<li>√bbs.nw2 </li>
√bbs.nw1<br>
<li>Generated files</li>
√bbs.nw2<br>
|Minimum 1000 blocks
Generated network files
|
Minimum 1000 blocks recommended
|}
|}
----
Next Section: [[configurations|Different Configurations]]
[[Introduction|Introduction]]

Latest revision as of 23:15, 15 February 2026

Introduction – File Storage Drives

Once your hardware is assembled, the next step is determining how Color 64 will organize and store its files.

The BBS divides external storage into logical “drives.” In this documentation, a drive refers to any isolated storage area, regardless of hardware type. A drive may be:

  • A 1541 or 1571 floppy disk drive
  • A 1581 disk drive
  • A CMD HD partition
  • An REU configured as a RAM disk
  • Any other dedicated storage area

Each drive contains one or more file groups. A file group is a collection of related files serving a common function. Every group must reside together on a designated drive area.

For example, the Public Messages group contains all public posts made by users and should reside on a single drive. If sufficient space is available, multiple groups may share the same drive.

Example Drive Group Assignment
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

All file groups must remain accessible while the BBS is running. Disk swapping is not supported once the system is active.

When referring to a “Program Files drive,” this means the drive on which the Program group resides. The same terminology applies to all file groups. Multiple groups may share a drive if space allows.

Below is a description of the file groups used by Color 64. Recommended minimum storage values are provided as general guidance.

Approximate Storage Space of Files
Group Description Files Approximate Size
Boot Contains startup files and utilities such as SETUP, password tools, and system loaders.

Must reside on drive 0 or drive 1 (LU 0 or LU 1 on Lt. Kernal).
Must not be placed in a subdirectory.

Bootmaker
√sys.loadml
√sys.mlinit
√sys.mlnorm
√sys.setup
+bbs
Additional “+” utilities
dir.rename
Directory tools
Password tools
Menu maker

Approx. 200 blocks
Utilities approx. 70 blocks

Program Contains main overlays, √bbs.parms, and required ML files.

Must reside on drive 0 or drive 1.
Must not be stored in subdirectories.

√bbs.init
√bbs.msgs
√bbs.xfer
√bbs.ovl
√bbs.ov3
√bbs.profile
√bbs.ansi
√bbs.ascii
√bbs.punt
√bbs.xmoc
√bbs.parms

Optional:
√bbs.ov2
√sys.edit
√bbs.term
√bbs.trmml

Approx. 450 blocks
Optional files approx. 190 blocks

System Contains menus, data files, and relative files used by the BBS.

The drive storing System files must support REL files.

Menu files
Data files
REL files

Minimum 300 blocks recommended

Help Caller-accessible help documentation.

Help files (Sysop defined)

Sysop determined

Text Additional readable files such as graphics or informational documents.

May be combined with Help if desired.

Text files (Sysop defined)

Sysop determined

Password Stores user account records.

Approximately 1 block allocated per user.
The drive must support REL files.

√password

Approximately 1 block per user

Private Msgs Stores private email between callers.

Private message files

Minimum 300 blocks recommended

Public Msgs Stores public posts and networked messages.

Public message files

Minimum 500 blocks recommended

Caller Log Stores caller activity logs.

Must reside on drive 0 (or LU 0 on Lt. Kernal).

√caller log

Sysop determined

Aux1 User Profile area (v8.1.0a).

Stores signatures and welcome banners.
May be disabled in SETUP (Spare 2).

User signature files
User banner files
√bbs.profile

Varies by number of users

Aux3 Games area (v8.1.0a).

May be disabled in SETUP (Spare 1).

√bbs.games
√bbs.menu
Game files

Approx. 25 blocks plus games

Network Not needed unless you plan to participate in a Color 64 network.

Includes network overlays and generated data files.

√sys.net
√bbs.nw1
√bbs.nw2
Generated network files

Minimum 1000 blocks recommended

Next Section: Different Configurations

Introduction

Retrieved from "https://www.color64wiki.itchybutt.org/index.php?title=Filestorage&oldid=731"