System messages - Revision history

Admin at 18:31, 27 February 2026

2026-02-27T18:31:37Z

← Older revision		Revision as of 18:31, 27 February 2026
Line 258:		Line 258:
	Uses heavy Variable MCI and ML-populated modem status field. Edit carefully.		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.
	\|-		\|-
	\| style="text-align:center;" \| √mod edit menu		\| style="text-align:center;" \| √mod edit menu

Admin at 18:26, 27 February 2026

2026-02-27T18:26:41Z

← Older revision		Revision as of 18:26, 27 February 2026
Line 174:		Line 174:
	\| style="text-align:center;" \| √bbs closed		\| style="text-align:center;" \| √bbs closed
	\|		\|
	\| Create to prevent new users from registering. ~~Lower case recommended for ASCII compatibility~~.		\| 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.
	\|-		\|-
	\| style="text-align:center;" \| √membership full		\| style="text-align:center;" \| √membership full

Admin at 18:25, 27 February 2026

2026-02-27T18:25:16Z

← Older revision		Revision as of 18:25, 27 February 2026
Line 165:		Line 165:
	\| [[File:application.jpeg\|center\|200px]]		\| [[File:application.jpeg\|center\|200px]]
	\| Script-driven application file.		\| Script-driven application file.
	~~Lines~~ beginning with “#~~” trigger prompts~~.
	~~Responses~~ stored in mailbox and ~~“√questXX” files~~.		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.


	\|-		\|-

Admin at 18:22, 27 February 2026

2026-02-27T18:22:12Z

← Older revision		Revision as of 18:22, 27 February 2026
Line 128:		Line 128:
	\| style="text-align:center;" \| √sysop news		\| style="text-align:center;" \| √sysop news
	\| [[File:sysopnews.jpeg\|center\|200px]]		\| [[File:sysopnews.jpeg\|center\|200px]]
	\| Displays dated SYSOP news entries. Each user only sees unread entries. Keep concise.		\| 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.


	\|-		\|-

Admin at 18:17, 27 February 2026

2026-02-27T18:17:40Z

← Older revision		Revision as of 18:17, 27 February 2026
Line 80:		Line 80:
	\| style="text-align:center;" \| √systemstart2		\| style="text-align:center;" \| √systemstart2
	\| [[File:systemstart2.jpeg\|center\|200px]]		\| [[File:systemstart2.jpeg\|center\|200px]]
	\| Immediately follows √systemstart. ~~Prompts~~ the user to press DEL or Backspace for graphics detection. Should remain lower case and non-graphical.		\| 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.

	\|-		\|-

Admin at 17:48, 23 February 2026

2026-02-23T17:48:38Z

← Older revision		Revision as of 17:48, 23 February 2026
Line 1:		Line 1:
	[[installation\|Installation]] – <strong>The System Messages</strong>		[[installation\|Installation]] – <strong>The System Messages</strong>

			== 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.		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.
Line 7:		Line 9:
	As noted earlier, all BBS system filenames must include the check mark character (shifted @) as the first character of the filename.		As noted earlier, all BBS system filenames must include the check mark character (shifted @) as the first character of the filename.

	~~<strong>~~Creating and Editing System Messages~~</strong>~~		=== Creating and Editing System Messages ===

	There are several ways to create or modify system messages:		There are several ways to create or modify system messages:
Line 24:		Line 26:
	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.		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.

	~~<strong>~~Editing a Message File~~</strong>~~		=== Editing a Message File ===

	To edit a message on any drive:		To edit a message on any drive:
Line 49:		Line 51:
	[[File:fileeditexample.jpeg\|center\|200px]]		[[File:fileeditexample.jpeg\|center\|200px]]

	~~<strong>~~Editor Capabilities~~</strong>~~		=== Editor Capabilities ===

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

	This makes the stand-alone editor ideal for creating longer system files such as welcome screens, information files, menus, and help documentation.		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:		The table below provides the list of system message files that Color 64 uses:

Line 257:		Line 261:
	\|}		\|}

	~~<strong>~~Special Provisions for ASCII callers ~~</strong>~~		=== 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.		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.
Line 279:		Line 283:
	When an ASCII caller accesses the system, the BBS will automatically display the “+” version of the file if it exists.		When an ASCII caller accesses the system, the BBS will automatically display the “+” version of the file if it exists.

	~~<strong>~~Important Limitations~~</strong>~~		=== Important Limitations ===

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

Admin at 04:31, 16 February 2026

2026-02-16T04:31:40Z

Show changes

Admin at 04:24, 16 February 2026

2026-02-16T04:24:32Z

Show changes

Admin at 03:09, 9 October 2025

2025-10-09T03:09:56Z

← Older revision		Revision as of 03:09, 9 October 2025
Line 209:		Line 209:

	Normally when a BBS uses a lot of graphics, non-graphic callers will have a difficult time deciphering what is being displayed on their screen, however Color 64 v8.1 and above take care of this pretty well. Most screens are converted automatically. That said, for specific screens that may need a “re-write” for these callers (I find menus can be particularly troublesome), there is a provision to have alternate system files just for ASCII callers, but this is totally optional. There is a merge included in the system called "afr.ovxx" (AFR for Ascii File Read), which you can merge into all your overlays except for the Network overlays. Here is how it works: First you create all the files as normal for the system. Any file that you would like to have a corresponding ASCII file, create a file with the same name, remove the troublesome graphics and add a "+" at the end of the file name (e.g. √menu1 would be √menu1+). Any system file that is not actually “read" to the modem but instead acts like a script (like √application or √sysop news) cannot be used/converted.		Normally when a BBS uses a lot of graphics, non-graphic callers will have a difficult time deciphering what is being displayed on their screen, however Color 64 v8.1 and above take care of this pretty well. Most screens are converted automatically. That said, for specific screens that may need a “re-write” for these callers (I find menus can be particularly troublesome), there is a provision to have alternate system files just for ASCII callers, but this is totally optional. There is a merge included in the system called "afr.ovxx" (AFR for Ascii File Read), which you can merge into all your overlays except for the Network overlays. Here is how it works: First you create all the files as normal for the system. Any file that you would like to have a corresponding ASCII file, create a file with the same name, remove the troublesome graphics and add a "+" at the end of the file name (e.g. √menu1 would be √menu1+). Any system file that is not actually “read" to the modem but instead acts like a script (like √application or √sysop news) cannot be used/converted.

			Next Section: [[help and text\|Help & Text Files]]

	[[installation\|Installation]]		[[installation\|Installation]]

Admin at 14:13, 4 October 2025

2025-10-04T14:13:52Z

← Older revision		Revision as of 14:13, 4 October 2025
Line 1:		Line 1:
			[[installation\|Installation]] - <strong>The System Messages</strong>

	Now that you have defined all your parameters and all the Program Files and Boot Files are in their proper place, it is time to create your system messages. This is where you get to let your creative ideas flow. In each of these messages on the install disk, I have either placed content in them describing when the file is displayed, what it is about, or added generic content to it. Use a file copier to copy all the sample "system messages" onto the disk you have assigned to store your System Files. As explained earlier, all these filenames must always have the check mark (shifted @) in front of the filename.		Now that you have defined all your parameters and all the Program Files and Boot Files are in their proper place, it is time to create your system messages. This is where you get to let your creative ideas flow. In each of these messages on the install disk, I have either placed content in them describing when the file is displayed, what it is about, or added generic content to it. Use a file copier to copy all the sample "system messages" onto the disk you have assigned to store your System Files. As explained earlier, all these filenames must always have the check mark (shifted @) in front of the filename.

Line 207:		Line 209:

	Normally when a BBS uses a lot of graphics, non-graphic callers will have a difficult time deciphering what is being displayed on their screen, however Color 64 v8.1 and above take care of this pretty well. Most screens are converted automatically. That said, for specific screens that may need a “re-write” for these callers (I find menus can be particularly troublesome), there is a provision to have alternate system files just for ASCII callers, but this is totally optional. There is a merge included in the system called "afr.ovxx" (AFR for Ascii File Read), which you can merge into all your overlays except for the Network overlays. Here is how it works: First you create all the files as normal for the system. Any file that you would like to have a corresponding ASCII file, create a file with the same name, remove the troublesome graphics and add a "+" at the end of the file name (e.g. √menu1 would be √menu1+). Any system file that is not actually “read" to the modem but instead acts like a script (like √application or √sysop news) cannot be used/converted.		Normally when a BBS uses a lot of graphics, non-graphic callers will have a difficult time deciphering what is being displayed on their screen, however Color 64 v8.1 and above take care of this pretty well. Most screens are converted automatically. That said, for specific screens that may need a “re-write” for these callers (I find menus can be particularly troublesome), there is a provision to have alternate system files just for ASCII callers, but this is totally optional. There is a merge included in the system called "afr.ovxx" (AFR for Ascii File Read), which you can merge into all your overlays except for the Network overlays. Here is how it works: First you create all the files as normal for the system. Any file that you would like to have a corresponding ASCII file, create a file with the same name, remove the troublesome graphics and add a "+" at the end of the file name (e.g. √menu1 would be √menu1+). Any system file that is not actually “read" to the modem but instead acts like a script (like √application or √sysop news) cannot be used/converted.

			[[installation\|Installation]]