New pages

05:52, 4 October 2025 ‎Modmenu (hist | edit) ‎[22,526 bytes] ‎Admin (talk | contribs) (Created page with "Mod Menu 2.0 Color 64 v8.10a is defaulted to not use the Mod Menu functionality that came with versions 8.0 and 8.1; instead, it uses the AUX3 area for associated Games the Sysop chooses to use. However, you are not locked into this! You can still instead use the Mod Menu 2.0, particularly if you are moving your system from an existing 8.0/8.1 system where this was already in play. Just remember that if you are using the games I supplied on the insta...")
05:24, 4 October 2025 ‎Usersettings (hist | edit) ‎[3,659 bytes] ‎Admin (talk | contribs) (Created page with "Users have the option to modify their profile both for BBS performance as well as customization of their profile. There are two areas set up for Color 64 v8.10a: * User Settings * User Profile Editor Edit User Stats – Modifying User Settings If a caller types the [!]Edit User Stats command from the main prompt, they will be asked three questions regarding the way their terminal is set up. * Page-Pauser Lines : This is the settin...")
05:18, 4 October 2025 ‎Messageheaders (hist | edit) ‎[3,846 bytes] ‎Admin (talk | contribs) (Created page with "The [R]Read Public Messages routine allows you to customize the message headers. When the caller activates the Read Messages command, the program will load one of two files into memory. If the caller is currently using 40 columns, then "√headers" is used. If the caller is currently using 80 columns, then "√headers80" is used. Here is the format of the file: : Line 1: The message header top. This may be a line that divides off the message heade...")
05:04, 4 October 2025 ‎Textediting (hist | edit) ‎[4,057 bytes] ‎Admin (talk | contribs) (Created page with "The Text Editor for Color 64 (both stand-alone and internal BBS versions) have helpful shortcuts to make your life easy in your day-to-day work with the files and mail content. The table below lists the miscellaneous features available while editing or entering text: {| class="wikitable |- |+Text Editor Command Features ! Function ! Key ! Details |- | Lowercase | CTRL-L | Places an internal code in the text forcing display to transition to lower-case |- | Uppercas...")
04:58, 4 October 2025 ‎Mcicommands (hist | edit) ‎[15,486 bytes] ‎Admin (talk | contribs) (Created page with "Color 64 supports MCI commands--MCI stands for Message Command Interpreter, a system used on many BBS types. In short, an MCI command is a set of characters that you embed in a message to control the appearance of the text or perform special functions. One command could inform the computer to wait for a key to be pressed, and another command could turn on rainbow mode. MCI commands are not performed until the lines you have typed are viewed by you or someone else (whe...")
04:23, 4 October 2025 ‎Callerlog (hist | edit) ‎[3,259 bytes] ‎Admin (talk | contribs) (Created page with "The caller log is stored on disk in sequential file format. The filename is “√caller log" and it is maintained through the parameters you defined in SETUP. The caller log must always be stored on drive 0 because of BASIC programming space limitations. This is the only type of file that has this limitation, so it should pose no threat to a BBS system. As the BBS system is running, the variable LG$ is automatically updated with log information whenever a program G...")
04:22, 4 October 2025 ‎Localconsole (hist | edit) ‎[3,405 bytes] ‎Admin (talk | contribs) (Created page with "The Sysop's keyboard is always active, even when a user is logged in and using the system. This allows you to enter a command for a new user, log a caller off, invoke chat, etc. Here are some primary features: Chat Mode (F1) Pressing F1 when the user is at a command prompt will enable CHAT mode. During the time you are in CHAT mode, the BBS call timer stops. The caller's time online and time used today will not reflect this time in CHAT mode. O...")
04:18, 4 October 2025 ‎Userapplication (hist | edit) ‎[4,356 bytes] ‎Admin (talk | contribs) (Created page with "The application routine is used to find out information about your new users. The application routine is also used to get other membership information such as a real name and phone number. Fortunately for you, this aspect of the BBS program can be fully customized. To use the application feature, you'll need to have the file called "√application" present on your System Files drive. The √application file must be formatted in a certain way, so pay attention. I sug...")
04:12, 4 October 2025 ‎Graphicsmode (hist | edit) ‎[3,938 bytes] ‎Admin (talk | contribs) (Created page with "When a caller first logs on, the system determines what type of general terminal they are using with the "Backspace/DEL" test. Commodore graphics terminals send a CHR$(20) code when the caller hits the DEL key, while ANSI and ASCII callers will send a CHR$(8) or CHR$(127) code when they hit the backspace or delete keys. If they are using ANSI or ASCII, the system then asks the caller if their terminal supports ANSI graphics. If they answer "Y", then the computer will...")
04:05, 4 October 2025 ‎Signon (hist | edit) ‎[10,099 bytes] ‎Admin (talk | contribs) (Created page with "There are a couple ways to initiate a sign-on: A user can call your system using their modem, or you can do a local sign-on by pressing F1 from the Sysop Menu. Local Sign-On This is probably the first action you take with your newly-running BBS. The Local Sign-on allows the Sysop to bypass some of the processes and be logged into the BBS locally. This will take the modem off-hook, so users will only get a busy signal until you logoff. When F1 is...")
03:51, 4 October 2025 ‎Sysopstatus (hist | edit) ‎[631 bytes] ‎Admin (talk | contribs) (Created page with "Much like the Email notification flag at the Wait-for-Caller screen, there is a Sysop: In/Out status at the bottom of the screen. This is toggled by using the left arrow key on your keyboard (←). When set to “In”, the BBS will call up the file √sysopin to display to the user your customized screen showing that you are in. Conversely, √sysopout will be called showing you are out when this flag is set. center|200px")
03:48, 4 October 2025 ‎Passwordrecords (hist | edit) ‎[3,216 bytes] ‎Admin (talk | contribs) (Created page with "As you will notice if you use the F6 Password Maintenance function, there is a lot of information stored in each member's password record. The table below lists the field descriptions contained in the record: {| class="wikitable |- |+Password Record Field Descriptions ! Field ! Description |- | Access Level |Member's access level, which can range from 1 to 9. See the "SETUP-Main Parameters" section for a discussion of the default access level settings. |- |Members...")
03:27, 4 October 2025 ‎Sysopmenu (hist | edit) ‎[10,199 bytes] ‎Admin (talk | contribs) (Created page with "While the BBS program is waiting for a caller, if you press any of the function keys, you will see a SYSOP menu. Note: When starting a new system, it is IMPORTANT that you enter at least one public message before letting any other callers log on. There are two reasons for this. First, this will force the last message read variable to be increased by one (allowing new users to read their mailboxes the next time they log on to your BBS). Second, it is critical that wh...")
03:10, 4 October 2025 ‎Loading (hist | edit) ‎[9,402 bytes] ‎Admin (talk | contribs) (Created page with "Loading the BBS At this point, you should have already created your parameters file, password file, most of your core system messages and help files. Each drive assigned in your parameters file should have a disk or disk image in it with the proper files already on it. If you want to start your system with some files in the download directory, make sure you put them in the proper drive now. There are two specific discussions pertaining to loading t...")
02:34, 4 October 2025 ‎Bbs operation (hist | edit) ‎[1,070 bytes] ‎Admin (talk | contribs) (Created page with "With your SETUP and organization of your BBS complete, you are ready to start up your BBS operation! Loading The BBS At this point, you should have already created your parameters file, password file, most of your core system messages and help files. Each drive assigned in your parameters file should have a disk or disk image in it with the proper files already on it. If you want to start your system with some files in the download directory, mak...")
21:51, 3 October 2025 ‎Preconfigured builds (hist | edit) ‎[4,016 bytes] ‎Admin (talk | contribs) (Created page with "The 8.10a SD2IEC Build The SD2IEC build of Color 64 v8.1a (color64v81a.zip) is preconfigured for use with your SD drive and a WiModem (cbmstuff.com). It can easily be modified to go beyond just the SD drive when configuring in +SETUP. However, without modification, this build unzipped and placed on a freshly formatted SD card will have what you need to start building your BBS. You will see several folders already configured for the SD drive and they ar...")
21:44, 3 October 2025 ‎Email notification (hist | edit) ‎[3,460 bytes] ‎Admin (talk | contribs) (Created page with "Requirements: Home computer running Python, Wifi Modem or TCPSER This is a fun feature I put in, but it requires the use of modern technology to get us over the hump. With the power of another computer on your home network and Python3, your BBS will generate emails of BBS events that you can define through the various overlays. I’m using a Kubuntu Linux home computer, where the script listens on a specified port to receive BBS notifications (calls) and then emails me...")
21:38, 3 October 2025 ‎Help and text (hist | edit) ‎[2,830 bytes] ‎Admin (talk | contribs) (Created page with "A full set of help files are included with your Color 64 package, but no text files. The Help Files and Text Files work the same, so use the Help Files as a guide when setting up your text files. There needs to be a file in the Help Files disk called "@help files". Notice that instead of having a check mark as the first character of the filename, it has an “@” symbol. This symbol will prevent the file from showing up in the download directory, but still allow you...")
21:35, 3 October 2025 ‎System messages (hist | edit) ‎[16,035 bytes] ‎Admin (talk | contribs) (Created page with "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 assign...")
03:21, 3 October 2025 ‎Prior to running (hist | edit) ‎[3,086 bytes] ‎Admin (talk | contribs) (Created page with "Prior to exposing your system to the world, there are some files you must address first. This checklist serves as a guide in making sure you have hit on all the files and areas of code necessary to make sure the end user has a functional UI and the system is healthy enough to take logons. For questions on individual files mentioned below, refer to "The System Messages" for explanation on their function and suggestion of use. Presets You Will Want to Address </s...")
03:08, 3 October 2025 ‎Setup parameters (hist | edit) ‎[55,186 bytes] ‎Admin (talk | contribs) (Created page with "SETUP - Main Parameters The Main Parameters section is where you get to define how some of the critical functions of your BBS will be performed. If you are not sure about how to answer some of the questions, it should be OK to accept the default value given to you. You should, however, read the description of each of the items so you can understand how the BBS will use the information. {| class="wikitable |- |+Main Parameters Descriptions ! Questio...")
01:58, 3 October 2025 ‎Boot program details (hist | edit) ‎[7,310 bytes] ‎Admin (talk | contribs) (Created page with "All boot programs are denoted with a plus-symbol (“+”) at the start of the filename. The first one you will be running is “+SETUP” to configure your BBS and you will be using it frequently as things change in your BBS. When you load and run one of these files, several things occur: * An initial reset occurs (the screen clears, and the colors go back to default). The reset is done to make sure the system is ready to load the necessary programs. * Addition...")
21:18, 2 October 2025 ‎Creating boot files (hist | edit) ‎[7,836 bytes] ‎Admin (talk | contribs) (Created page with "The next step to accomplish is to use the included "bootmaker" utility to create the boot programs that start the essential BBS operations. All the boot programs begin with a "+" (plus sign) symbol; the +bbs program you copied to the boot files is an example of this. Creating these boot programs is very important because you set some important parameters for the system, such as whether you are using the SwiftLink RS-232 cartridge. The bootmaker utility creates your...")
03:00, 2 October 2025 ‎Copying the files (hist | edit) ‎[4,258 bytes] ‎Admin (talk | contribs) (Created page with "Once you have decided how to divide up your storage, it is time to copy all the files necessary to boot the BBS system. Below are the needed files for your Program drive as well as the Boot files for the boot disk. For larger disk systems, you can combine these two into one singular drive/area. For 1541 floppy disk users, the Boot Drive files will be your Boot disk. For 1571 users, if your program files disk has 700 or more blocks available, you can include the boot fil...")
02:12, 2 October 2025 ‎Installation (hist | edit) ‎[1,177 bytes] ‎Admin (talk | contribs) (Created page with "The installation process can be divided into three parts: copying the necessary program files, running the SETUP program, and then installing the system files. A detailed explanation of the function of each of the options in SETUP will be provided, as well as a description of all the necessary system files. Never use your original Color 64 disks as anything but the source of all the stock BBS files that come with Color 64. It is advised that you make a backup of you...")
03:08, 1 October 2025 ‎Reu (hist | edit) ‎[12,353 bytes] ‎Admin (talk | contribs) (Created page with "The √sys.ramove Script Program If you want to have your program overlays run off a RAM expander, then the quickest way to transfer the programs would be to LOAD them into memory and then SAVE them to the REU RAM-disk. This is exactly what the "√sys.ramove" program does, because it is a BASIC "script" program that uses the Script-Merge utility designed by myself. A script is simply a set of instructions that are executed as if you typed them in f...")
02:40, 1 October 2025 ‎Highspeed (hist | edit) ‎[1,446 bytes] ‎Admin (talk | contribs) (Created page with "If you have a SwiftLink RS-232 cartridge or you are emulating it in VICE, you can take advantage of a high-speed modem, communicating at rates of up to 38,400 BPS. There are many different types of high-speed modems, some of which may not be compatible with others because of the diverse "standards" set down by different companies. If you plan to use a high-speed modem, you should invest in one that can handle many different communications protocols. Some of the more co...")
02:40, 1 October 2025 ‎2400baud (hist | edit) ‎[2,647 bytes] ‎Admin (talk | contribs) (Created page with "Color 64 BBS supports the Hayes Smartmodem 2400 and many good compatible modems. Without using the SwiftLink interface, you should find that your C64 and Color 64 can handle 2400 baud file transfers with very few errors. Here is how I recommend you configure your modem to set up your system for 2400 baud. Hayes Smart modems come from the factory with DTR and CARRIER DETECT forced true. The 1200 baud modems had switches while the 2400 modems don't. Instead, they h...")
02:35, 1 October 2025 ‎Avatex (hist | edit) ‎[858 bytes] ‎Admin (talk | contribs) (Created page with "If you use the Avatex 1200 modem (not the Avatex 1200 HC or the Avatex 2400) on your system, then your overlays need to be changed because the Avatex 1200 is not completely Hayes-compatible. Once your system has been modified, you will not be able to use the overlays with a true Hayes-compatible modem, so MAKE A BACKUP of all the overlays to be changed. Merge the following files into the specified overlays: <ul style="list-style: none;"><li>ava.init -> √bbs.init...")
02:34, 1 October 2025 ‎Skyles (hist | edit) ‎[642 bytes] ‎Admin (talk | contribs) (Created page with "The Color 64 system will automatically detect if you are using the Flash! interface. The system will only take advantage of the interface on device 8, however. As such, you will need to make sure the 1541 to be used with the interface is device 8. To fit all your program files on the 1541 disk, you will have to leave out a couple overlays, either the "√bbs.ov2" and "√bbs.ov3" overlays, or the "√bbs.nw1" or "√bbs.nw2" overlays.")
02:33, 1 October 2025 ‎Fastload (hist | edit) ‎[914 bytes] ‎Admin (talk | contribs) (Created page with "Some fastloader cartridges may require some special merges for the BBS program to work properly during LOAD operations. To check if you need the following merges, turn your computer on with the fastloader in place (and active), and type the following line and press RETURN: PRINTPEEK(817) If the number that is printed is 223 (two hundred twenty-three), then you need these fastloader merges, which need to be merged into the specified overlays: *fst....")
02:31, 1 October 2025 ‎Cmdram (hist | edit) ‎[1,899 bytes] ‎Admin (talk | contribs) (Created page with "Color 64 works great with this super device from Creative Micro Designs. If you also have a CMD HD, you can use the parallel cable and have your overlays load in a flash. If you have a 17XX series REU from Commodore and you do not wish to use it as extra RAM on the RamLink, you can also use it with RAMDOS. Just follow the instructions in your RamLink manual for accessing the REU "as is" (i.e. "direct" mode), then follow the regular Color 64 installation instructi...")
02:30, 1 October 2025 ‎Cmd (hist | edit) ‎[2,378 bytes] ‎Admin (talk | contribs) (Created page with "The HD series of hard drives from Creative Micro Designs is another excellent choice for running a BBS system. You can allocate your disk space in almost any configuration you can think of, dividing the storage up into partitions. The CMD HD's Native Mode partitions also support subdirectories, which allow you to dynamically allocate space to individual file directories. The only "requirement" for using the CMD HD might be this: If you plan to have your Program F...")
02:28, 1 October 2025 ‎Ict (hist | edit) ‎[4,822 bytes] ‎Admin (talk | contribs) (Created page with "Color 64 BBS fully supports the InConTrol Data Chief HFD20 hard disk drive system. All you need to do is use "hm4 11 22" as the drive command for whatever files you want stored in a chain defined as starting at partition 11 and ending at partition 22 or h10 for files you want stored in an individual partition 10. The only files that you can put in chain mode are Public Messages Help Files, Text Files, Uploads and Downloads. System Files, Private Mail, Caller Logs, Pas...")
02:25, 1 October 2025 ‎Ltkernal (hist | edit) ‎[2,965 bytes] ‎Admin (talk | contribs) (Created page with "Xetec's Lt. Kernal Hard Drive system is an excellent choice to run your BBS system on. It supports up to 9 different partitions of disk space called Logical Units, and each of these units has 15 "users" which are like subdirectories. This can mean you can have up to 135 separate file directories. Color 64 will NOT be able to use the Lt. Kernal and RAMDOS at the same time, if you have an REU in configuration with the HD. To use the Lt. Kernal HD on the 64, you must...")
02:22, 1 October 2025 ‎Techsupport (hist | edit) ‎[670 bytes] ‎Admin (talk | contribs) (Created page with "I’ll reiterate I’m not the author of Color 64, whether that be 7.37, 8.0 or 8.1. That said, I’m here to help with what I’ve learned as well as to support my modified build and/or help you get running. I’m easy to locate by jumping over to my website at www.itchybutt.org. I’m not strong suited to the 7.37 build; your best bet is OasisBBS.org for questions there, but if you are dealing with 8.1 or my 8.1.0a, please feel free to reach out to me!")
02:22, 1 October 2025 ‎81aupdates (hist | edit) ‎[2,713 bytes] ‎Admin (talk | contribs) (Created page with "I still consider myself a rookie when it comes to the 8.1 code structure…. Just enough to be dangerous. That said, I’ve been working with the code for the last two years and I am slowly gaining steam with successful modifications and several bug corrections that came with 8.0/8.1. The beauty of this product is that we have the freedom to make it truly customized to our liking. It was in this spirit that I’ve spent countless weekend nights up to the crack of d...")
02:20, 1 October 2025 ‎Configurations (hist | edit) ‎[2,218 bytes] ‎Admin (talk | contribs) (Created page with "The smallest possible system would be two 1541 disk drives, with three disks: Program disk, Boot disk, and system disk (all other file groups). The first drive would be the Program Files, and the drive from which you boot the system. The second drive would have your system disk in it and would be used for all the other file groups (System Files, Public messages, etc.). With larger amounts of space, there are a few guidelines to remember: <ul><li>You should always k...")
22:21, 30 September 2025 ‎Filestorage (hist | edit) ‎[9,382 bytes] ‎Admin (talk | contribs) (Created page with "Now that you have all your hardware together, it is time to decide how Color 64 will be able to store all 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....")
20:26, 30 September 2025 ‎Overlays (hist | edit) ‎[4,295 bytes] ‎Admin (talk | contribs) (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>")
20:25, 30 September 2025 ‎Hardware (hist | edit) ‎[8,798 bytes] ‎Admin (talk | contribs) (Created page with "Hardware Support This BBS system operates on native hardware (with almost any combination of disk drives to include SD2IEC), emulated hardware like VICE, or newer builds of the Commodore such as Commodore Ultimate Elite II with IEC capability. It operates well with 1581 disk drives (or D81 images), but they are not recommended for any sections of the BBS that require REL file creation (like the system’s PASSWORD file or games that create these types o...")
13:42, 30 September 2025 ‎Specificsystemrequirements (hist | edit) ‎[1,901 bytes] ‎Admin (talk | contribs) (Created page with "There have been many products produced for the Commodore 64 and 128 computers, many of which have special features and/or requirements that can be accounted for in Color 64. In the following sections, I will try to describe how to best set up your system with various hardware configurations. Things to remember: Some systems require that special routines be merged into the main overlays and other programs; these routines have been included as separate merges on the i...")
13:24, 30 September 2025 ‎Introduction (hist | edit) ‎[557 bytes] ‎Admin (talk | contribs) (Created page with " Introduction Color 64 BBS is a historical juggernaut in the Commodore 64 BBS world with years of development under its belt. It is a marriage of complexity and simplicity that provides powerful features for the system and at the same time, ease of customization to make your system unique. This BBS program is comprised of two parts. The first part is the set of BASIC programs, called Overlays, which are responsible for the operation of the BBS progr...")
12:52, 30 September 2025 ‎Main Page (hist | edit) ‎[11,080 bytes] ‎MediaWiki default (talk | contribs)