IntroductionFile 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