System messages

Installation – The System Messages

The System Messages

With your parameters defined and your Program and Boot files properly installed, it is time to create and customize your System Messages. This is where your BBS begins to take on its personality.

The install disk includes sample system message files. Many contain placeholder content explaining when the file is displayed or what it is used for. Use a file copier to transfer all desired sample "system messages" onto the drive assigned for your System Files.

As noted earlier, all BBS system filenames must include the check mark character (shifted @) as the first character of the filename.

Creating and Editing System Messages

There are several ways to create or modify system messages:

• A word processor that saves SEQ text files (such as Easy Script)
• The stand-alone BBS message editor
• The built-in message editor within the BBS DOS section
• Kaleidoscope (recommended for menu-style screens)

To use the stand-alone message editor, load and RUN the program "+editor" from your Boot disk (for floppy-based systems).

After loading, you will see a menu similar to this:

The “Read Newsletter” option is a legacy item from the original 8.0 release when a Color 64 newsletter was planned. It remains as an artifact of that era.

Editing a Message File

To edit a message on any drive:

• Press F1.
• Enter the device number of the drive that contains (or will contain) the message file.

If the number shown in brackets is correct, press RETURN.

• Enter the drive number (0 or 1). Again, press RETURN to accept the default.
• Enter any drive initialization command if required.

Normally, you will press RETURN for the init command. However, special configurations may require commands such as:

• `u0>h1` for the back side of a 1571
• `u0>m1` to place a 1571 into 1571 mode
• Hard drive partition commands as needed

Finally, enter the filename — remembering to include the required prefix character:

• “√” for protected system files
• “@” when appropriate for hidden description files

If the file exists, it will load into memory for editing. If it does not exist, it will be created when saved.

Example screen:

Editor Capabilities

The stand-alone editor functions the same way as the online message editor used for public and private messages.

Key differences:

• The stand-alone editor allows messages up to approximately 500 lines.
• It supports full color control codes.
• The online editor is limited to the “Maximum lines per message” value defined in the “√bbs.parms” file.

This makes the stand-alone editor ideal for creating longer system files such as welcome screens, information files, menus, and help documentation.

System Messages Definition List

The table below provides the list of system message files that Color 64 uses:

System Message Files

File	Example	Description
√systemstart		The very first file displayed when a user connects. Keep this in lower case and graphics-free in case the caller is using ASCII (it will appear upper case to them). Common uses include BBS name, date, time, or an initial greeting.
√systemstart2		Immediately follows √systemstart. Edit it and include verbiage to the user to press DEL or Backspace for graphics detection. Should remain lower case and non-graphical.
√banner √abanner		Displayed after graphics detection. √banner = Commodore (PETSCII) terminals √abanner = ANSI terminals Graphics are fully permitted here.
√welcome1		Main greeting screen shown after graphics check and before credential entry.
√welcome2		Optional. Displayed after successful login. Can be graphical or minimal.
√logon stats √logon stats80		Shows current BBS and account status. √logon stats = 40 column √logon stats80 = 80 column Uses extensive Variable MCI commands. Edit cautiously.
√sysopin √sysopout		Displayed depending on whether the SYSOP flag is set to “In” or “Out.” Graphics permitted.
√level # msg		Level-specific message displayed after login. Create files such as “√level 3 msg” or “√level 7 msg.” If added or removed while running, press F4 at WFC to reset flags.
√wall		Optional user wall / guestbook. Remove command “W” from BBS Commands if deleting.
√sysop news		Displays dated SYSOP news entries. Each user only sees unread entries. Keep concise. New entries should have a date immediately following the last line of previous entry. Keep in mind that you don’t want this file to get too long. New users will see every single news entry when they go through their logon process. This file is optional.
√menu#		Main menu screen per access level (e.g., √menu4). Can be graphical. Multi-page menus are possible but may slow navigation.
√chat enter		Displayed when chat session begins.
√chat exit		Displayed when chat session ends.
√new user msg1		Displayed after new user account assignment. Keep short and avoid screen clears.
√new user msg2		Displayed after application completion. Include instructions for validation if needed.
√application		Script-driven application file. This is displayed to the user, but the display will be different than what you see here as it is being run as a script. The application is a combination of a regular text and special "prompt lines" that will cause the BBS to stop and wait for the caller's response to the application question. Any line beginning with a "#" (number sign) will not be printed but instead will cause the application routine to stop and wait for the caller to type something. The text after the "#" symbol will then be part of the application information that is put in your mailbox. Then the next bit of text will be printed until the next prompt, where the BBS will wait for another response, and this repeats until the last line of the file is used. Then it prints everything back to the caller and asks if this is correct. If they answer "N", then the application routine will begin again. Otherwise, the answers are stored in your mailbox and in a file called “√questXX" where XX is the number of the month (e.g. √quest07 for July). The "√questXX" file is stored in the Private Files section. You will be able to print your mailbox for a hard copy while all your remote SYSOPs will be able to see the same answers in the "√questXX" file.
√bbs closed		Create this file to prevent new users from registering. If this file exists, the BBS will not allow new user registration. Lower case recommended for ASCII compatibility.
√membership full		Displayed when maximum user limit has been reached.
√member list msg		Displayed before membership list.
√membership list		Automatically generated user list.
√information		System information file describing hardware, configuration, or other details.
√no mail		Displayed when no private mail is waiting. Optional.
√sysop not here		Displayed when chat request receives no response.
√still not here		Displayed on subsequent unanswered chat requests.
√sayings#		Random sayings displayed before first command prompt. Example: √sayings1 through √sayings6. Optional.
√games menu		Required if running games from AUX3. Disable spare command “1” if using Mod Menu instead.
√logoff		Displayed prior to disconnect. Optional.
√upload msg		Displayed before upload begins.
√upload held		Displayed after upload when below auto-release level.
Other Notable Screens
√doshelp		Displayed at DOS Wedge when “?” is entered.
√msg menu		Message menu help display.
√wfc		Waiting For Call screen (SYSOP console). Uses heavy Variable MCI and ML-populated modem status field. Edit carefully. Also note the “BBS Name” just below “Last Caller” in this screenshot is only populated if you have Network 1.26a running.
√mod edit menu		Help screen for Mod Menu.
√mod sub menu		Sub-menu help for Mod Menu.

Special Provisions for ASCII callers

Normally when a BBS uses a large amount of PETSCII graphics, non-graphic (ASCII) callers can have difficulty understanding what is displayed on their screen. Fortunately, Color 64 v8.1 and above handle most screen conversions automatically, making the system usable for both PETSCII and ASCII users.

That said, certain screens — particularly menus with heavy graphics — may not translate cleanly. For these situations, Color 64 provides an optional method for creating alternate system files specifically for ASCII callers.

Included with the system is a merge file called afr.ovxx (AFR = ASCII File Read). This merge can be applied to all overlays except for the Network overlays.

How the ASCII Alternate File System Works

• Create your standard system file as usual.
• If you want an ASCII-friendly version, create a second file:
  • Use the same filename.
  • Remove or simplify any troublesome PETSCII graphics.
  • Add a plus sign (+) to the end of the filename.

Example:

• √menu1 (standard PETSCII version)
• √menu1+ (ASCII alternate version)

When an ASCII caller accesses the system, the BBS will automatically display the “+” version of the file if it exists.

Important Limitations

System files that function as scripts rather than simple display files cannot use this method. Examples include:

• √application
• √sysop news

These files are executed as part of program flow rather than being read directly to the modem, and therefore cannot be converted using the AFR method.

Next Section: Help & Text Files

Installation