Overlays - Revision history

Admin at 15:56, 27 February 2026

2026-02-27T15:56:18Z

← Older revision		Revision as of 15:56, 27 February 2026
Line 66:		Line 66:

	<strong>Disk Speed Enhancers </strong>		<strong>Disk Speed Enhancers </strong>

	~~Here is a professionally rewritten version of that section, polished for clarity and flow while keeping the technical detail intact:~~

	~~---~~

	The program overlays average approximately 90 blocks each. On an unmodified disk drive, load times can be excessive, making the use of a disk speed enhancement system strongly recommended. JiffyDOS is highly recommended, though many other fastloader systems compatible with Color 64 may also be used. The Xetec Lt. Kernal hard drive with its Host Adapter is another supported option; when using Lt. Kernal, ensure the NMI trap is set to OFF (00) in the Lt. Kernal configuration. As a general guideline, if load times exceed 15 seconds, callers are likely to notice and may become dissatisfied.		The program overlays average approximately 90 blocks each. On an unmodified disk drive, load times can be excessive, making the use of a disk speed enhancement system strongly recommended. JiffyDOS is highly recommended, though many other fastloader systems compatible with Color 64 may also be used. The Xetec Lt. Kernal hard drive with its Host Adapter is another supported option; when using Lt. Kernal, ensure the NMI trap is set to OFF (00) in the Lt. Kernal configuration. As a general guideline, if load times exceed 15 seconds, callers are likely to notice and may become dissatisfied.

Admin at 23:07, 15 February 2026

2026-02-15T23:07:08Z

← Older revision		Revision as of 23:07, 15 February 2026
Line 67:		Line 67:
	<strong>Disk Speed Enhancers </strong>		<strong>Disk Speed Enhancers </strong>

	~~The average size of these overlays~~ is ~~about 90 blocks each and would require~~ a ~~long time to load on an unmodified disk drive, so it is required~~ that ~~you use a speed enhancer. JiffyDos is highly recommended~~, ~~although there are many other types of fastloader systems that are compatible with Color 64. You can also use the Xetec Lt. Kernal hard drive with its own Host Adapter (make sure you set~~ the ~~NMI trap off - 00 - in the Lt. Kernal setup). If any load time takes more than 15 seconds, you will probably get complaints from your callers.~~		Here is a professionally rewritten version of that section, polished for clarity and flow while keeping the technical detail intact:

	~~Another solution~~ to the slow disk access is ~~to add~~ a ~~C1764~~, ~~C1750~~, or compatible ~~Ram~~ Expansion Unit (REU) expanded to at least 256K. These ~~units add 256K or 512K (or more if expanded) of internal~~ RAM ~~to your 64~~, eliminating ~~program loading~~ delays ~~in the~~ BBS. Color 64 ~~will support~~ up to ~~2 megabytes~~ of external RAM. ~~Separate~~ boot programs are ~~used that will~~ install RAMDOS and ~~then load~~ a BASIC "script~~" which will copy all the necessary~~ files ~~onto your~~ REU. Even if you ~~plan~~ to ~~use~~ REU ~~for your system~~, ~~I suggest that you~~ first install ~~it without the REU~~ and run ~~it off~~ a disk device. ~~Then once~~ you are ~~comfortable~~ with the ~~operation of Color~~ 64, ~~you can easily switch~~ to ~~REU use~~.		---

			The program overlays average approximately 90 blocks each. On an unmodified disk drive, load times can be excessive, making the use of a disk speed enhancement system strongly recommended. JiffyDOS is highly recommended, though many other fastloader systems compatible with Color 64 may also be used. The Xetec Lt. Kernal hard drive with its Host Adapter is another supported option; when using Lt. Kernal, ensure the NMI trap is set to OFF (00) in the Lt. Kernal configuration. As a general guideline, if load times exceed 15 seconds, callers are likely to notice and may become dissatisfied.

			An effective alternative to slow disk access is the addition of a Commodore 1764, 1750, or compatible RAM Expansion Unit (REU) expanded to at least 256K. These devices provide additional RAM, eliminating most overlay load delays during BBS operation. Color 64 supports up to 2MB of external RAM.

			Dedicated boot programs are included to install RAMDOS and execute a BASIC script that copies required system files into REU memory. Even if you intend to operate primarily from an REU, it is advisable to first install and run the system using a standard disk device. Once you are familiar with system operation, transitioning to REU-based operation is straightforward.

			You may notice that each program overlay filename begins with the “√” character. On a Commodore 64 or 128, this character is entered by holding either SHIFT key and pressing the @ key. The prefix is used to conceal system files from normal directory listings, preventing callers from viewing or downloading them.

	As you may have noticed, each of the program overlay filenames begins with a “√“. To type this character on Commodore 64 & 128, you must press and hold either shift key, then press the @ key. This special character is used to hide all the system files from being seen or downloaded by your callers.

	Next Section: [[filestorage\|File Storage / Drives]]		Next Section: [[filestorage\|File Storage / Drives]]

	[[Introduction\|Introduction]]		[[Introduction\|Introduction]]

Admin at 03:02, 9 October 2025

2025-10-09T03:02:51Z

← Older revision		Revision as of 03:02, 9 October 2025
Line 72:		Line 72:

	As you may have noticed, each of the program overlay filenames begins with a “√“. To type this character on Commodore 64 & 128, you must press and hold either shift key, then press the @ key. This special character is used to hide all the system files from being seen or downloaded by your callers.		As you may have noticed, each of the program overlay filenames begins with a “√“. To type this character on Commodore 64 & 128, you must press and hold either shift key, then press the @ key. This special character is used to hide all the system files from being seen or downloaded by your callers.

			Next Section: [[filestorage\|File Storage / Drives]]

	[[Introduction\|Introduction]]		[[Introduction\|Introduction]]

Admin at 14:27, 4 October 2025

2025-10-04T14:27:56Z

← Older revision		Revision as of 14:27, 4 October 2025
Line 1:		Line 1:
			[[Introduction\|Introduction]] - <strong>The Program Overlays</strong>

	To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example:		To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example:
Line 44:		Line 45:
	\|User Profile customization area, permits users to create a customized signature for messages as well as a greeting banner to display to other users when they are messaging that person.		\|User Profile customization area, permits users to create a customized signature for messages as well as a greeting banner to display to other users when they are messaging that person.
	\|}		\|}


	If you are going to use Network, then there are two other overlays that Color 64 will use.		If you are going to use Network, then there are two other overlays that Color 64 will use.
Line 63:		Line 63:
	\|Note: File prscrn52750 is also required as part of this.		\|Note: File prscrn52750 is also required as part of this.
	\|}		\|}


	<strong>Disk Speed Enhancers </strong>		<strong>Disk Speed Enhancers </strong>

	The average size of these overlays is about 90 blocks each and would require a long time to load on an unmodified disk drive, so it is required that you use a speed enhancer. JiffyDos is highly recommended, although there are many other types of fastloader systems that are compatible with Color 64. You can also use the Xetec Lt. Kernal hard drive with its own Host Adapter (make sure you set the NMI trap off - 00 - in the Lt. Kernal setup). If any load time takes more than 15 seconds, you will probably get complaints from your callers.		The average size of these overlays is about 90 blocks each and would require a long time to load on an unmodified disk drive, so it is required that you use a speed enhancer. JiffyDos is highly recommended, although there are many other types of fastloader systems that are compatible with Color 64. You can also use the Xetec Lt. Kernal hard drive with its own Host Adapter (make sure you set the NMI trap off - 00 - in the Lt. Kernal setup). If any load time takes more than 15 seconds, you will probably get complaints from your callers.


	Another solution to the slow disk access is to add a C1764, C1750, or compatible Ram Expansion Unit (REU) expanded to at least 256K. These units add 256K or 512K (or more if expanded) of internal RAM to your 64, eliminating program loading delays in the BBS. Color 64 will support up to 2 megabytes of external RAM. Separate boot programs are used that will install RAMDOS and then load a BASIC "script" which will copy all the necessary files onto your REU. Even if you plan to use REU for your system, I suggest that you first install it without the REU and run it off a disk device. Then once you are comfortable with the operation of Color 64, you can easily switch to REU use.		Another solution to the slow disk access is to add a C1764, C1750, or compatible Ram Expansion Unit (REU) expanded to at least 256K. These units add 256K or 512K (or more if expanded) of internal RAM to your 64, eliminating program loading delays in the BBS. Color 64 will support up to 2 megabytes of external RAM. Separate boot programs are used that will install RAMDOS and then load a BASIC "script" which will copy all the necessary files onto your REU. Even if you plan to use REU for your system, I suggest that you first install it without the REU and run it off a disk device. Then once you are comfortable with the operation of Color 64, you can easily switch to REU use.

			As you may have noticed, each of the program overlay filenames begins with a “√“. To type this character on Commodore 64 & 128, you must press and hold either shift key, then press the @ key. This special character is used to hide all the system files from being seen or downloaded by your callers.

	As you may have noticed, each of the program overlay filenames begins with a “√“. To type this character on Commodore 64 & 128, you must press and hold either shift key, then press the @ key. This special character is used to hide all the system files from being seen or downloaded by your callers.		[[Introduction\|Introduction]]

Admin: Protected "Overlays" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2025-10-03T21:53:04Z

Protected "Overlays" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 21:53, 3 October 2025
(No difference)

Admin at 22:48, 30 September 2025

2025-09-30T22:48:45Z

← Older revision		Revision as of 22:48, 30 September 2025
Line 1:		Line 1:

	To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example:		To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example:

Line 10:		Line 11:
	For the purposes of this manual, suffixes will not be referred to when discussing specific overlays, but note that version 8.1.0a does have some unchanged files from previous iterations of 8.0/8.1, so not all files will be shown with suffix “810a”.		For the purposes of this manual, suffixes will not be referred to when discussing specific overlays, but note that version 8.1.0a does have some unchanged files from previous iterations of 8.0/8.1, so not all files will be shown with suffix “810a”.

	~~<p style~~="~~text~~-~~align: center;"><strong>~~Color 64 v8.1.0a Overlays ~~</strong></p>~~		{\| class="wikitable
	~~<table>~~		\|-
	~~<tr><th>Overlay</th><th>~~General Description~~</th></tr>~~		\|+Color 64 v8.1.0a Overlays
	~~<tr>~~		! Overlay
	~~<td><strong>~~√bbs.init~~</strong></td><td>~~Responsible for initial variable setup, caller logon, and password maintenance. ~~prscrn52750 * if using BBS network </td></tr>~~		! General Description
	~~<tr><td><strong>~~√bbs.msgs ~~</strong></td><td>~~Responsible for all public and private messages.~~</td></tr>~~		\|-
	~~<td><strong>~~√bbs.xfer~~</strong></td><td>~~Responsible for single and multi-file uploads/downloads, and directory maintenance.~~</td></tr>~~		\|√bbs.init
	~~<tr><td><strong>~~√bbs.ovl~~</strong></td><td>~~Responsible for multi-uploads, help and text files.~~</td></tr>~~		\| Responsible for initial variable setup, caller logon, and password maintenance.
	~~<tr><td><strong>~~√bbs.ov2~~</strong></td><td>~~This handles loading your online games and modules. Use of the module loader in "√bbs.ov2" is optional to the Sysop. Version 8.1.0a now includes an alternate games module, √bbs.games.~~</td></tr>~~		\|-
	~~<tr><td><strong>~~√bbs.ov3~~</strong></td><td>~~This is used for a system guestbook / “wall” and should be included as part of your system.~~</td></tr>~~		\|√bbs.msgs
	~~<tr><td><strong>~~√bbs.term ~~</strong></td><td>~~A full-featured terminal program. Optional for ~~the Sysop~~.~~</td></tr>~~		\|Responsible for all public and private messages, composing and reading.
	~~<tr><td><strong>~~√bbs.games~~</strong></td><td>~~A new game module as an alternative to √bbs.ov2. This module is set to use the AUX3 designated drive and the √bbs.games file itself should be resident there. It is the only overlay placed outside of the designated “programs” drive. ~~</td></tr>~~		\|-
	~~<tr><td><strong>~~√bbs.profile~~</strong></td><td>~~User Profile customization area, permits users to create a customized signature for messages as well as a greeting banner to display to other users when they are messaging that person. ~~</td></tr>~~		\|√bbs.xfer
	~~</table>~~		\|Responsible for single and multi-file uploads/downloads, and directory maintenance.
			\|-
			\|√bbs.ovl
			\|Responsible for multi-uploads, help and text files.
			\|-
			\|√bbs.ov2
			\|This handles loading your online games and modules. Use of the module loader in "√bbs.ov2" is optional to the Sysop. Version 8.1.0a now includes an alternate games module, √bbs.games.
			\|-
			\|√bbs.ov3
			\|This is used for a system guestbook / “wall” and should be included as part of your system.
			\|-
			\|√bbs.term
			\|A full-featured terminal program. Optional for install.
			\|-
			\|√bbs.games
			\|A new game module as an alternative to √bbs.ov2. This module is set to use the AUX3 designated drive and the √bbs.games file itself should be resident there. It is the only overlay placed outside of the designated “programs” drive.
			\|-
			\|√bbs.profile
			\|User Profile customization area, permits users to create a customized signature for messages as well as a greeting banner to display to other users when they are messaging that person.
			\|}


	If you are going to use Network, then there are two other overlays that Color 64 will use.		If you are going to use Network, then there are two other overlays that Color 64 will use.

	~~<table>~~		{\| class="wikitable
	~~<tr><th>~~Overlay~~</th><th>~~General Description~~</th></tr>~~		\|-
	~~<tr><td><strong>~~√bbs.nw1 ~~</strong></td><td>~~This contains the Network message editor, and handles calling and receiving calls. ~~</td></tr>~~		\|+Network Related Overlays
	~~<tr><td><strong>~~√bbs.nw2~~</strong></td><td>~~This handles the Network maintenance and the distribution of messages. If you do not wish to run Network, then these files are not required. ~~</td></tr>~~		! Overlay
	~~</table>~~		! General Description
			\|-
			\|√bbs.nw1
			\|This contains the Network message editor, and handles calling and receiving calls.
			\|-
			\|√bbs.nw2
			\|This handles the Network maintenance and the distribution of messages. If you do not wish to run Network, then these files are not required.
			\|-
			\|
			\|Note: File prscrn52750 is also required as part of this.
			\|}

	<strong>Disk Speed Enhancers </strong>		<strong>Disk Speed Enhancers </strong>

Admin at 22:24, 30 September 2025

2025-09-30T22:24:32Z

← Older revision		Revision as of 22:24, 30 September 2025
Line 10:		Line 10:
	For the purposes of this manual, suffixes will not be referred to when discussing specific overlays, but note that version 8.1.0a does have some unchanged files from previous iterations of 8.0/8.1, so not all files will be shown with suffix “810a”.		For the purposes of this manual, suffixes will not be referred to when discussing specific overlays, but note that version 8.1.0a does have some unchanged files from previous iterations of 8.0/8.1, so not all files will be shown with suffix “810a”.

	<strong>Color 64 v8.1.0a Overlays </strong>		<p style="text-align: center;"><strong>Color 64 v8.1.0a Overlays </strong></p>
	<table>		<table>
	<tr><th>Overlay</th><th>General Description</th></tr>		<tr><th>Overlay</th><th>General Description</th></tr>

Admin at 20:40, 30 September 2025

2025-09-30T20:40:23Z

← Older revision		Revision as of 20:40, 30 September 2025
Line 9:		Line 9:

	For the purposes of this manual, suffixes will not be referred to when discussing specific overlays, but note that version 8.1.0a does have some unchanged files from previous iterations of 8.0/8.1, so not all files will be shown with suffix “810a”.		For the purposes of this manual, suffixes will not be referred to when discussing specific overlays, but note that version 8.1.0a does have some unchanged files from previous iterations of 8.0/8.1, so not all files will be shown with suffix “810a”.

			<strong>Color 64 v8.1.0a Overlays </strong>
			<table>
			<tr><th>Overlay</th><th>General Description</th></tr>
			<tr>
			<td><strong>√bbs.init</strong></td><td>Responsible for initial variable setup, caller logon, and password maintenance. prscrn52750 * if using BBS network </td></tr>
			<tr><td><strong>√bbs.msgs </strong></td><td>Responsible for all public and private messages.</td></tr>
			<td><strong>√bbs.xfer</strong></td><td>Responsible for single and multi-file uploads/downloads, and directory maintenance.</td></tr>
			<tr><td><strong>√bbs.ovl</strong></td><td>Responsible for multi-uploads, help and text files.</td></tr>
			<tr><td><strong>√bbs.ov2</strong></td><td>This handles loading your online games and modules. Use of the module loader in "√bbs.ov2" is optional to the Sysop. Version 8.1.0a now includes an alternate games module, √bbs.games.</td></tr>
			<tr><td><strong>√bbs.ov3</strong></td><td>This is used for a system guestbook / “wall” and should be included as part of your system.</td></tr>
			<tr><td><strong>√bbs.term </strong></td><td>A full-featured terminal program. Optional for the Sysop.</td></tr>
			<tr><td><strong>√bbs.games</strong></td><td>A new game module as an alternative to √bbs.ov2. This module is set to use the AUX3 designated drive and the √bbs.games file itself should be resident there. It is the only overlay placed outside of the designated “programs” drive. </td></tr>
			<tr><td><strong>√bbs.profile</strong></td><td>User Profile customization area, permits users to create a customized signature for messages as well as a greeting banner to display to other users when they are messaging that person. </td></tr>
			</table>

			If you are going to use Network, then there are two other overlays that Color 64 will use.

			<table>
			<tr><th>Overlay</th><th>General Description</th></tr>
			<tr><td><strong>√bbs.nw1 </strong></td><td>This contains the Network message editor, and handles calling and receiving calls. </td></tr>
			<tr><td><strong>√bbs.nw2</strong></td><td>This handles the Network maintenance and the distribution of messages. If you do not wish to run Network, then these files are not required. </td></tr>
			</table>

			<strong>Disk Speed Enhancers </strong>

			The average size of these overlays is about 90 blocks each and would require a long time to load on an unmodified disk drive, so it is required that you use a speed enhancer. JiffyDos is highly recommended, although there are many other types of fastloader systems that are compatible with Color 64. You can also use the Xetec Lt. Kernal hard drive with its own Host Adapter (make sure you set the NMI trap off - 00 - in the Lt. Kernal setup). If any load time takes more than 15 seconds, you will probably get complaints from your callers.


			Another solution to the slow disk access is to add a C1764, C1750, or compatible Ram Expansion Unit (REU) expanded to at least 256K. These units add 256K or 512K (or more if expanded) of internal RAM to your 64, eliminating program loading delays in the BBS. Color 64 will support up to 2 megabytes of external RAM. Separate boot programs are used that will install RAMDOS and then load a BASIC "script" which will copy all the necessary files onto your REU. Even if you plan to use REU for your system, I suggest that you first install it without the REU and run it off a disk device. Then once you are comfortable with the operation of Color 64, you can easily switch to REU use.


			As you may have noticed, each of the program overlay filenames begins with a “√“. To type this character on Commodore 64 & 128, you must press and hold either shift key, then press the @ key. This special character is used to hide all the system files from being seen or downloaded by your callers.

Admin at 20:28, 30 September 2025

2025-09-30T20:28:35Z

← Older revision		Revision as of 20:28, 30 September 2025
Line 1:		Line 1:
	To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example:		To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example:

	<ul>		<ul style="list-style: none;">
			<li>√bbs.ovl 8000 = Main Overlay, Version 8.0</li>
			<li>√bbs.ovl 8001 = Main Overlay, Version 8.0 revision 1</li>
			<li>√bbs.ovl 8100 = Main Overlay, Version 8.1</li>
			<li>√bbs.ovl 810a = Main Overlay, Version 8.1.0a</li>
			</ul>

	</~~ul>~~		For the purposes of this manual, suffixes will not be referred to when discussing specific overlays, but note that version 8.1.0a does have some unchanged files from previous iterations of 8.0/8.1, so not all files will be shown with suffix “810a”.

Admin: Created page with "To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example:

"

2025-09-30T20:26:17Z

Created page with "To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example: <ul> </ul>"

New page

To get the most out of the Commodore 64's limited amount of memory, the BBS program has been divided into several program overlays. All the overlay file names begin with "√bbs." and have a suffix in the form of an alphanumeric. For example:

<ul>

</ul>