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.
== SETUP Parameters ==
SETUP is where you define how Color 64 will operate on your system: message limits, credit rules, modem behavior, disk assignments, directories, time limits, categories, and command permissions. If you are unsure about a specific prompt, it is usually safe to accept the default value shown in brackets and fine-tune later. The notes below explain how each option affects day-to-day operation.
{| class="wikitable
----
=== Main Parameters ===
The Main Parameters section controls core BBS behavior such as message limits, upload/download rules, credit handling, access levels, and modem settings.
{| class="wikitable"
|-
|-
|+Main Parameters Descriptions
! Question
! Question
! Description & Settings
! Description & Settings
|-
|-
|Maximum lines per message
| Maximum lines per message
|The maximum number of lines to limit each message.
| Limits the number of lines permitted in a single message.<br />
Default:100 Allowable range: 20-200
Default: 100<br />
Range: 20–200
|-
|-
|Maximum columns per line
| Maximum columns per line
|The default word wrap length you would like when you use local-mode features like the text editor.
| Sets the default word-wrap width used by local-mode tools (such as the editor).<br />
Default: 38 Suggested: 38 for 40-column use, 78 for 80-column.
Default: 38<br />
Suggested: 38 for 40-column systems; 78 for 80-column output.
|-
|-
|Maximum # of messages
| Maximum # of messages
|The maximum number of public messages the system will keep online at any one time. Once the maximum threshold is reached, older messages will be removed as new messages are generated.
| Maximum number of public messages retained online. When the limit is reached, older messages are deleted as new ones are posted.<br />
Default: 50 Allowable range: 25-232
Default: 50<br />
Range: 25–232<br /><br />
Considerations: 1541 disks only permit 144 files to be stored on one disk. SFD 1001 permits 224. Hard disks can have an unlimited number, but 232 is the maximum of the system.
Considerations: 1541 disks allow only 144 directory entries per disk. SFD-1001 allows 224. Hard drive style systems may allow far more, but the BBS itself tops out at 232.
|-
|-
|Maximum password number
| Maximum password number
|Sets the maximum number of passwords you want to set the system up for.
| Sets the maximum number of member records in the √password file.<br />
Default: 100 Allowable Range: 25-9999
Default: 100<br />
Range: 25–9999<br /><br />
Considerations: 1541 limit is 720 records. If limit is exceeded, new incoming users will see the "√membership full” file when trying to apply. Approximately 1 disk block is used for each user record. Changing this value over time is permitted but may cause fragmentation of your file – slowing the read time of the file. See hint below this table on rectifying this condition.
Considerations: 1541 limit is roughly 720 records. If exceeded, new callers will receive the “√membership full” message when attempting to apply. Roughly 1 disk block is used per user record.<br /><br />
This value can be increased later, but expanding repeatedly over time may fragment the file and slow access. See “Password File Fragmentation” hints below for a clean rebuild method.
|-
|-
|Minimum blocks-cycle msgs
| Minimum blocks-cycle msgs
|Sets the minimum number of blocks free allowed on the Public Messages drive before the messages start cycling. You do not want to let this disk completely fill up, especially if it will also be storing private messages on it. Default: 50 Recommended Range: 25 to 75
| Minimum free blocks required on the Public Messages drive before messages begin cycling.<br />
Default: 50<br />
If blocks free on this disk ever fall below this variable, every time any new message is posted, the oldest public message will be deleted even if the maximum number of messages is not exceeded.
Recommended: 25–75<br /><br />
If free blocks drop below this value, each new public post will delete the oldest public message even if the maximum message count has not been reached.
|-
|-
|Minimum blocks-allow uploads
| Minimum blocks-allow uploads
|Sets the minimum number of blocks free to allow uploads.
| Minimum free blocks required to permit uploads.<br />
Default: 75<br />
Default: 75 Recommended range: 10 to 75
Recommended: 10–75<br /><br />
If private messages share this same disk, do not set below 25. The BBS will not allow private mail to be sent if free blocks fall below 25.<br /><br />
If you are going to be storing private messages on the same disk, then you will not want to set this value less than 25. The BBS will not allow private messages to be sent if the directory falls below 25 blocks free. You will never want to set the value below 10. This is to allow space for the “√directory" file to be processed after an upload. Note that the free space message given at the end of the directory list and before an upload will automatically be decremented by this value (i.e. free upload space is the total free minus the minimum blocks free). Also, the caller log routines use this value in determining when the caller log should be trimmed if it is taking up too much space.
Never set below 10. Space is required for directory processing and temporary files after uploads. The “free upload space” shown to callers is automatically reduced by this value.
|-
|-
|Maximum downloads per call
| Maximum downloads per call
|Sets the maximum number of downloads you will allow per call.
| Maximum number of downloads allowed per caller session. Enter 99 for a practical “no limit.” Callers who reach the limit must log off and back on to continue downloading. Exemptions can be granted via “No DL file limit level.”
If you enter "99", then for all practical purposes there will not be a limit to the number of downloads per call. When a caller reaches their maximum downloads per call, they must logoff and logon again before they can download more. You can set the level at which callers are exempt from this function when you enter the level for "No DL file limit level" asked later in this section.
|-
|-
|Download credits per call
| Download credits per call
|Sets the number of blocks of download credit you will give per block uploaded.
| Sets how many download-credit blocks a caller earns per block uploaded.
|-
|-
|New mbr download credits
| New mbr download credits
|Sets how many free credit blocks for each new caller. After these free credits are used up, your callers will have to upload to earn more download credits.
| Free download credits granted to each new caller. Once used, callers must upload to earn additional credits (unless exempt).
|-
|-
|Credit system exempt level
| Credit system exempt level
|Sets the access level at which your callers become exempt from the credit system. If you do not plan to use this credit system, just set this variable to 1 (making all your callers exempt).
| Access level at which callers become exempt from the credit system. If you are not using credits, set to 1 so all callers are exempt.
|-
|-
|Max files on public msgs drive
| Max files on public msgs drive
|Sets the maximum number of files that you want to be on the public messages drive. The system will count the files after each user logoff.
| Maximum directory entry count permitted on the Public Messages drive. The system checks after each user logoff.<br /><br />
Recommendations:<br />
Recommendations:
1541: ~135 messages<br />
1541 drive: 135 messages SFD 1001: 210
SFD-1001: ~210<br />
SD2IEC / LTK: 200-250 or enter “0” to avoid message count
SD2IEC / LTK: ~200–250, or enter 0 to avoid file counting<br /><br />
Higher limits increase message indexing time at boot and may reduce available memory.
Note that higher capacities will extend message indexing time at boot-up and may result in less memory available.
|-
|-
|Number of days to hold mail
| Number of days to hold mail
|Sets the maximum number of days that you want the BBS to hold private mail before deleting it.
| Maximum days private mail is retained before automatic deletion.<br /><br />
When mail is purged, an entry is written to the caller log at midnight indicating the member number affected. A safety buffer prevents mass deletion if the system clock is accidentally wrong: if calculated mail age exceeds the purge value by more than 7 days, that mail will not be deleted.
A significant amount of mail may be resident for users that have been dormant. If a caller does not read their mail within 30 days or so, it is likely unimportant at that point.
When mail is deleted, an entry is made in the caller log at midnight indicating the member's number who had their mail deleted. This could be useful in determining if this value is set too low and deleting too much mail. There is a safety check built in to prevent everyone's mail from being deleted if you accidentally type in the wrong year or month when loading the BBS. When the system calculates how many days a piece of mail has been online, if that number exceeds the purge mail variable by 7 days, that mail will not be deleted. Remember this if in the future you decide to change this purge mail variable.
|-
|-
|New User Access Level
| New User Access Level
|This sets the access level for new users logging on. Some SYSOPs desire level 1 until validated. Others provide full access to their systems.
| Sets the access level assigned to new callers. Some sysops prefer Level 1 until validation; others start users higher. Default level meanings are summarized below.<br /><br />
'''Typical use of levels (defaults):'''<br />
Access levels by their default are as follows:
;1: Recommended for unverified new users
:1
:* Read System Messages
::Recommended for all new users until verified by admin
:* Create Profile/Signature
::* Read System Messages
:* Very limited system time
::* Create Profile/Signature
;2: “Browse” level
::* Very limited in allowable time on system
:* Includes Level 1
:2
:* Adds read access to public messages and text files
::This access level allows new users to look around. This can be an alternative place to start new users.
;3: Standard contributor level
::* Includes Level 1 privileges
:* Includes Level 2
::* Adds Read Access to public messages and text files
:* Adds posting, uploads, and downloads
:3
;4–5: Full normal access
::Good level to give callers if you are trying to get voluntary contributions. You could also set the credit system exemption level to 4, so that level 3 callers have something to gain by sending in a financial contribution
:* Same abilities; use categories, time limits, and directory levels to differentiate
::* Includes Level 2 privileges
:* Common network approach: Level 4 non-network; Level 5 network-approved
::* Adds ability to post Public Messages and perform Uploads and Downloads
;6: Privileged callers
:4-5
:* Exempt from per-call time limit
::* Full use of system
:* No download limit per call
::Since both levels have the same abilities, you will be able to set up the different message categories, download directories, time limits, etc and maybe give some of your most contributing callers more access.
:* No time-between-calls restriction
::One recommendation if you plan to have a Networked BBS is have level 4 non-network access and maintain approved users for the network at level 5.
;7: Helper sysops/moderators
:6
:* Scratch public messages or downloads
::This would be for your more privileged users that aren’t worried about abusing the system time unnecessarily as it removes many limitations of normal users:
:* Edit download descriptions
::* Adds exemption for “per call” time limit
:* Release uploads
::* Removes maximum download limit per call
;8: High-level sysop (co-sysop)
::* Removes time between calls limitation
:* Set clock/date
:7
:* Change user access levels (cannot elevate to sysop)
::Access for regular sysops. They can be of help in maintaining the download directories and by removing offensive or no-longer-needed public messages. In addition to level 6 permissions, this level provides:
:* Read caller log
::* Scratch any public message or download
:* Warning: Level 8 can view other users’ passwords
::* Edit download descriptions
;9: Full sysop
::* Release uploads for public access
:* Password maintenance
:8
:* Full DOS functions
::High-level (Co)Sysop. Includes all features of Level 7 with addition of:
:* Should be limited to you (and possibly one trusted backup)
::* Set Clock & Date
::* Change another user's Access Level (cannot make a user SYSOP or change a SYSOP’s level)
::* Read Caller Log
::This level gives enough access to allow someone to run the BBS for a weekend or so while you may be away. YOU DO NEED TO BE CAREFUL WHO YOU GIVE THIS ACCESS LEVEL. Since level 8 users will be able to see anyone else's passwords, you owe it to your callers to make sure the people you select for level 8 are trustworthy!
:9
::Includes all the below level privileges and:
::* Password Maintenance
::* Full DOS functionality
::This access level should only be given to yourself and possibly one other caller if you are going to be gone for a long while. There really is not much you cannot do with this access level, so you should be very cautious about who you give level 9 access.
|-
|-
|Mbrs expired access level
| Mbrs expired access level
|Sets the access level you want the BBS to assign to a caller when their membership has expired. In each caller's password record, there is a field that can contain a membership expiration date. You would use the Password Maintenance or the (V)alidate option to enter/edit this date. At midnight, a compare of this date to the current date will be made and if there is a match, that caller's access level will automatically be changed to the level you define here. This allows us to give a caller a certain number of days on the system and not have to try to remember to lower that caller's access level on any certain day. One use of this feature would be to give callers a 30-day trial membership, for example. And since the system automatically lowers your caller's access level, there may be less hard feelings towards you afterwards.
| Level assigned automatically when a caller’s membership expiration date is reached. The expiration date is stored per user record and is checked at midnight. Useful for trial memberships or time-limited access.
|-
|-
|Upload auto-release level
| Upload auto-release level
|When a caller uploads a file to the system, do you want that file to automatically be released as a public download, or would you prefer it to be held for a SYSOP to review before it is released? You can assign higher level callers you trust to have their files immediately released for the masses.
| Determines what access level is required for an upload to be automatically released as a public download. Lower-level uploads can be held for sysop review.
|-
|-
|System Baud Rate
| System Baud Rate
|This should be set to the maximum possible rate of your modem. The system will automatically step-down the baud rate when someone with a lower baud value calls in.
| Sets the maximum communications rate between the computer and modem/interface. The system can step down based on the caller’s capabilities (and modem requirements).<br /><br />
If you are not using SwiftLink, the practical maximum is 2400. With SwiftLink, 38,400 BPS is supported in many configurations, including TCPSER, where the computer-to-modem rate can remain high even if the modem-to-modem connection is lower, depending on the “Adjust BPS to connect rate” setting.
If you are not using the SwiftLink RS232 interface, then the highest BPS rate for your system is 2400 BPS. For SwiftLink users, the use of high-speed modems becomes a little complex. Most high-speed modems that support MNP and rates above 2400 BPS allow the computer to communicate with the modem at rates much greater than even the maximum connect rate of the modem. Previous experimentation with the Supra Fax 14.4K BPS modem, we have found you can set the rate at 38,400 BPS with no problems at all. This allows the computer to send data to the modem at the fastest possible speed and allows the modem to take care of the necessary data buffering. The computer and modem will be communicating with each other at a rate of 38,400 BPS even if the host modem and the remote modem are communicating at only 1200 BPS, but only if the computer doesn’t have to adjust its BPS rate to the connection rate (as some modems require). Thus, this setting should be used in conjunction with the "Adjust BPS to connect rate" question asked later in this section.
|-
|-
|DD$ MCI on
| DD$ MCI on
|This question deals with the built in MCI (Message Command Interpreter) commands, which allow you to print messages and do special formatting inside of text files. One of the messages that the MCI commands can print is the current contents of the variable DD$ (see section 3.8, on MCI commands, for more information). DD$ is one of the items that is stored in each caller's password record, and it is up to the SYSOP on how this item is used. It is limited to 8 characters, so this field can hold a short 8-character note about the caller that will be printed on the Password Maintenance report. It can be used to note callers that have been given free access; you can enter SYSOP for callers who are SYSOPs of other systems, or GUEST for members on your system as a guest, or REMOTE for remote SYSOPs. If you want to keep this information private (i.e. the MCI commands won't print this information), then answer "N" to this question.
| Controls whether MCI commands may print the DD$ field from a caller’s password record. DD$ is an 8-character sysop-defined note field (for example SYSOP, GUEST, REMOTE). Answer N to keep DD$ private from MCI output.
|-
|-
|Using Upload Descriptions
| Using Upload Descriptions
|Enables or disables the "upload descriptions" feature of Color 64 BBS. Most will want to answer "Y" to this question. The only time you may want to say "N" is if you do not have enough disk space and all the extra file descriptions will fill up the directory or disk. The popular SFD 1001 disk drive has a limitation of only 224 files in its directory. This sounds like a lot until you realize that each download requires a second file for the description. So, if you are using an SFD 1001 and you want to use upload descriptions, you will be limited to 111 files in the downloads (allowing for the. directory and √dir.tmp files). This gets even worse if you are also putting system files, messages, help files, and/or text files on the same SFD. If you answer "n" to download descriptions, it is possible for you or your SYSOPs to manually enter a download description on any specific file. Just use the [E]dit Dnld Desc command to create the description file. All download descriptions will be stored on the disk as "@dnldname". Example, the description file for "ccgms termz4.0+" is "@ccgms termz4.0+". Before starting an upload, a check is always made to make sure a download under that name and a description under that name does not exist. If you ever see a "file exists" error and cannot figure out why, remember about the download descriptions (even if you are not using them).
| Enables download description files (stored as @filename). Most sysops should answer Y. If directory-entry limits are a concern (notably on SFD-1001), descriptions reduce the maximum number of downloads because each file consumes an additional directory entry. Manual description creation remains possible via the Edit Download Description command.
|-
|-
|Mutiple dirs. per drive
| Mutiple dirs. per drive
|This question is asking if you will have multiple file categories on one disk drive. This option is mainly for large disk drives (like 5, 10 or 20-meg hard disk drives) and will allow you to divide that large area of disk space up into more manageable, smaller areas. You could use this option on any disk drive, but it may not be worth the effort unless you have a lot of files on one disk drive. If you do answer Y to this question, every file uploaded to the system will automatically have a letter (A-Z) added to the beginning of its filename. The callers do not see this letter, it is just used by the BBS to group the files into different directories. If you manually copy a file onto your download disk, you will need to rename the file, so the proper capital letter is the first character of the filename. There is a utility included in this package to help you rename your current downloads called "dir rename". When you use it, the delete key deletes the first character of the filename, any other key pressed becomes the first character of the filename. Remember, if you answer N to this multiple directory question, you will not need to rename any files. They will be displayed to your callers exactly as they are on the disk, with all the files on one drive in the same directory.
| Enables multiple logical directories on the same physical drive. When enabled, the BBS prefixes uploaded filenames internally with a letter (A–Z) for grouping. Callers do not see the prefix. If you manually add files, you must rename them with the correct leading letter. If you answer N, no renaming is required and everything resides in a single directory.
|-
|-
|Daily Log Backup
| Daily Log Backup
|Enables / Disables the daily backup of your caller log during the midnight reset routine. If you answer "N", then the caller log file will just contain a running list of the most recent calls. If you answer "Y", then each night the caller log will be backed up and dated, and the caller log will be cleared. In either case, the size of the current caller log is limited by several factors. First, the minimum space on the caller log drive is determined by the "Minimum blocks-allow uploads" question. Also, two later questions in this section, “Caller log max size blocks" and "Caller log trim blocks", determine the maximum size of the caller log and the number of blocks that will be trimmed from the caller log if the maximum size is exceeded, or the minimum space is available. See the section in this documentation on the Caller Log System for more information on how the caller log is maintained.
| Enables nightly caller log backup and rotation at midnight. If N, the caller log remains a running recent-history file. If Y, the log is dated and archived daily, then cleared. Log size trimming is governed by “Caller log max size blocks” and “Caller log trim blocks,” as well as the “Minimum blocks-allow uploads” threshold.
|-
|-
|Rerun on Errors
| Rerun on Errors
|Enables / disables program restart on BASIC errors. If a caller does find a way to crash the BBS causing a BASIC error or if you have made a change to the BASIC coding and accidentally left an error in the program, the system will automatically rerun itself. Normally you DO want this option to be enabled. The only time you may want to disable this option is if you are making modifications to the BBS programs and are still testing the changes. Note that when rerun is enabled, the STOP key will be disabled. Once the STOP key is disabled, then only by pressing a combination of the SHIFT, COMMODORE, and CONTROL keys will the program "break". See the section titled "Additional Commands Console Mode Only" for more information on this feature.
| Restarts the BBS automatically after BASIC errors. Normally this should be enabled. Disable only while actively modifying/testing overlays. When enabled, STOP is disabled; breaking requires SHIFT+COMMODORE+CTRL.
|-
|-
|Screen Blanking
| Screen Blanking
|Enables / disables screen blanking on SYSOP side when a caller is reading or writing a private message. There are some that feel that a private message should be totally private, not even read by the SYSOP. Others feel the SYSOP is totally responsible for everything on the BBS, even the private messages. This option allows you to set up your system the way you feel is best. If you do answer "Y" to this question, the screen will be blanked when a caller is reading their mail or sending mail to anyone else on the system. The screen will NOT be blanked when a caller is sending feedback or private mail to your mailbox or when you are accessing the system from the console.
| If enabled, blanks the local sysop screen when callers read or write private mail (excluding feedback to sysop and console-local use). Use this based on your privacy philosophy and moderation needs.
|-
|-
|Does your modem support DTR
| Does your modem support DTR
|Identifies if your modem and interface both support DTR (Data Terminal Ready) and if you have all switches or settings set so the phone/telnet line will disconnect if DTR is false. Most Hayes-compatible modems and TCPSER support DTR, The Volksmodem 12 when used with cable J does not support DTR, nor does the 1670 (the 1670 does support DTR but seems to work better if we disable this feature). If you are unsure, answer N to this question.
| Indicates whether your modem/interface supports DTR drop for disconnect. Most Hayes-compatible modems and TCPSER support DTR. Some hardware behaves better with DTR disabled (notably certain 1670 setups). If unsure, answer N.
|-
|-
|Adjust BPS to connect rate
| Adjust BPS to connect rate
|This question is for those SYSOPs who will be using high speed modems (2400 MNP and higher BPS rates). Once a caller connects to the system, most 1200 and 2400 modems will automatically step down the BPS rate to the connection rate and expect the computer to do so. If you are using a 1200 BPS modem or a 2400 BPS modem, then most of the time you should answer yes to this question. Otherwise, you may need to do some experimentation to find out if your high-speed modem requires the computer to also step down its BPS rate. From our own experience we know that TCPSER users can achieve 38,400 BPS. The Supra Fax 14.4K BPS modem will let the computer communicate with the modem at a rate up to 38,400 BPS even if the modem-to-modem rate is only 1200 BPS. Thus, for the Supra Fax, you would answer "N" to this question.
| Controls whether the computer should step down its BPS rate to match the modem connect rate. Many 1200/2400 modems expect this; some high-speed setups (including many TCPSER configurations) can run 38,400 computer-to-modem regardless of connect rate. This may require experimentation depending on your modem.
|-
|-
|Run Network v1.26a
| Run Network v1.26a
|Color 64 Network provides the ability for two or more BBS systems to share messages and files between them. It utilizes one message and file category that you select for your BBS and permits users with access to post public and private messages to the participating systems.
| Enables Color 64 Network features (sharing messages/files between participating systems). New sysops should normally answer N until the system is stable and coordination with another network sysop is complete. If enabled, you must run +net setup afterward.
If you are a new SYSOP just starting your BBS, you should answer “N” to this question. However, once you are familiar with your system, it is stable in operation, and a remote BBS (or more) are desiring to participate with you in a network, then you can answer “Y” at this prompt whenever you are ready. This takes coordination with the remote BBS SYSOP(s) and they must be running the Network option as well. Once you have answered “Y” to this prompt, after saving these changes, run “+NET SETUP and follow that section in establishing your Network.
|-
|-
|Modem Init Command
| Modem Init Command
|This defines the initialization command to be sent to your modem before accepting a caller. You will need to know a little about your modem before you can answer this question. Refer to your modem documentation on what settings you should or desire to use. Some pointers:
| Initialization command sent to the modem before accepting a caller. Must start with lowercase “at”. Recommended strings vary by modem type. Verbose mode (v1) is essential. If the BBS shows OK at init, the string is accepted; if it shows ERROR, remove unsupported parts and test again in a terminal.<br /><br />
Examples commonly used:<br />
* The init string must begin with “at" (lower case). This stands for “attention” and needs to be entered only once even though many commands are in this one string.
WiModem: ate0x1s0=0s10=30v1<br />
* If your modem will accept it, consider following the “attention” with a reset (“z”). This reset is required for many types of modems to keep them from getting locked up. Conversely, the Hayes Smartmodem 1200 and both Commodore 1670 modems will ignore the remainder of the init command after a “z” is encountered; don’t use the "z" reset with these modems. In summary, use “ate1x1s0=0s10=30f1q0v1m0" for the Hayes Smartmodem 1200 and most compatibles. If you are using a Volksmodem 12 or some other Hayes-compatible that does not clear the command buffer when it executes an "atz”, your modem may work better if you add a "z" just after the "at" and just before the "e1". Change the modem init command to “ate1x1s0=1s10=30f1q0v1m0" for the new (4 switch) version 1670 or “ate1x1s0=2f1q0v1m0" for the original 1670 (the version with only 3 switches). If you have the 17XX ram expansion module with an old 1670, it is safe to change the "s0=2" above to "s0=1".
TCPSER: ate0v1h0x1m0b1
* Many wifi modems have eliminated some of the commands; of these, they will still accept the command but will not act on it. A good example of this would be the “speaker volume” command (“l”). For the WiModem, we used init string of “ate0x1s0=0s10=30v1”
* For TCPSER, the init string “ate0v1h0x1m0b1” works well.
* A critical setting for BBS operation is Verbose mode ON (“v1”)
* If your modem does not support any of the commands in the above init strings (such as the s10=30), just take that part of the command out.
* If you are having a problem finding which part of the init string is causing you a problem, you can load up a terminal program and try typing in the command.
* If you get an "ok" when the BBS initializes, then you are all set. If it says "error", you need to find which part of the command is not supported. Also, if after loading the BBS the waiting for caller screen is printed, but the time and date are not printed, then there is something in this modem init string that is not set correctly.
|-
|-
|Network Modem Init Command
| Network Modem Init Command
|This is just like the previous parameter, except that the Network modem init command is sent to the modem before each outgoing Network call. SYSOPs with high-speed modems can set this command so that MNP or other error correction is turned off during Network calls (error correction can interfere with Network calls).
| Sent before each outgoing network call. Some sysops disable error correction for network calls if their modem’s MNP interferes. Default (ate0) has worked well for many v8.1a network setups.
The default value for this (ate0) has been successful with our recent network operations for v8.1a.
|-
|-
|Scratch any msg level
| Scratch any msg level
|Sets the access level to scratch any public message. Normally, callers are allowed to scratch only their own messages they have authored. Anyone who has the level for this option will be able to scratch any public message on the system, even if it is not their own. This should be reserved for remote SYSOPs and/or assigned moderators. Default: Level 7
| Level required to delete any public message (not just the caller’s own). Default: 7
|-
|-
|Category/Link level
| Category/Link level
|Sets the access level to change the category or the threading link of messages. Someone with access to this option will be allowed to move a message into another category or link a message to another message so that it will be part of the same message “thread". This should be reserved for remote SYSOPs and/or assigned moderators. Default: Level 7
| Level required to change message category or thread link. Default: 7
|-
|-
|Merge seq file level
| Merge seq file level
|Sets the access level to merge a sequential file into a message. When someone is editing a message and they have access to this option, then they are allowed to use the "*" command from the editor prompt to merge in a sequential file of their choice. This should be reserved for remote SYSOPs and/or assigned moderators. Default: Level 7
| Level required to merge a SEQ file into a message via the editor “*” command. Default: 7
|-
|-
|Caller log delete level
| Caller log delete level
|Sets the access level to delete the caller log. This is for remote SYSOP use. Default: Level 8
| Level required to delete the caller log. Default: 8
|-
|-
|Message MCI level
| Message MCI level
|Sets the access level needed to use the special Message MCI commands anywhere on the system. You may wish to limit the use of the Message MCI commands to higher-level individuals. The Message MCIs were mainly provided as a shortcut to print certain information such as the time or date, although many people find it entertaining and will put them to fun uses.
| Level required to use Message MCI commands. Default: 2
Default: Level 2
|-
|-
|Variable MCI level
| Variable MCI level
|Sets the access level to use the Variable MCI command. Normally the use of this advanced MCI should be restricted to the highest-level SYSOPs as any errors in the use of this may result in a system crash. Make sure that whoever has access to use the Variable MCI command is VERY familiar with the way BASIC and the Variable MCI commands work. Default: Level 9
| Level required to use Variable MCI commands. This should be restricted to trusted sysops due to crash potential from misuse. Default: 9
|-
|-
|No DL file limit level
| No DL file limit level
|Sets the access level at which a caller is exempt from the "Maximum downloads per call" setting. Default: Level 6
| Level exempt from “Maximum downloads per call.” Default: 6
|-
|-
|Min msg memory bytes
| Min msg memory bytes
|Sets the minimum number of free characters of memory when in the text editor. When you edit a text file, the computer has only so much free memory in which to store the message, and as you type each line the amount of free memory decreases. This value determines the minimum amount of memory that can be available before the computer will not let you add any more lines. If you set it to a high value (like 700), then you will avoid lengthy "garbage collection" delays while the computer tries to compensate for low memory. If you set it to a lower number (like 300), you will have more memory available for editing the message.
| Minimum free memory permitted while editing before the system stops accepting new lines. Higher values reduce garbage-collection pauses; lower values allow larger messages. Typical values: 300–700.
|-
|-
|Caller log max size blocks
| Caller log max size blocks
|Sets the maximum size (in blocks) of the caller log file. The caller log is constantly being added to, so it is necessary to put a limit on the size of the file to avoid excessively large files. If the maximum size is exceeded, then the caller log will be trimmed, using the value set by “Caller log trim blocks". Default: 50 Allowable Range: 8 – 200 blocks
| Maximum size of the caller log file (blocks). If exceeded, the log is trimmed using “Caller log trim blocks.”<br />
Default: 50<br />
Range: 8–200
|-
|-
|Caller log trim blocks
| Caller log trim blocks
|Sets the number of blocks that will be trimmed off the caller log when the maximum size is exceeded, or when the minimum upload blocks is reached. It should also never exceed half the maximum size of the caller log. Default: 8 Allowable Range: 4 – 100 blocks
| Blocks removed when trimming is triggered (by size or low disk space). Should not exceed half of “Caller log max size blocks.”<br />
Default: 8<br />
Range: 4–100
|-
|-
|Validate via email level
| Validate via email level
|Sets the access level to validate another caller through e-mail. If you have a remote SYSOP who does validations, they can validate a caller by (A)uto-replying to the caller's mail, then typing (V)alidate at the editor command prompt. If they have access to this command, they will be able to set the caller's level to validate them. Default: Level 8
| Level required to validate a caller through e-mail workflows. Default: 8
|-
|-
|Edit any message level
| Edit any message level
|Sets the access level to be able to edit any public message. Normally callers may only edit their own authored messages, but a caller who has access to this option will be able to edit any message on the system using the [E]Edit message command. Only that caller's messages will be displayed, but he/she can type any message number at the prompt. This should be reserved for remote SYSOPs and/or assigned moderators. Default: Level 9
| Level required to edit any public message (not only the caller’s own). Default: 9
|-
|-
|Max chars/40 column header
| Max chars/40 column header
|Sets the maximum width of the header information as printed in the customizable header routine (see section 3.13, on the customizable message headers), when the system is currently set to 40 columns output. If you wish to use the included custom header file, then this parameter must be set to 30 (the default). Default: 30
| Maximum header width when output is set to 40 columns. Default: 30
|-
|-
|Max Chars/80 column header
| Max chars/80 column header
|Same as above except this is for when the system is set for 80 columns output. The default is 70, which will work with the included customized header files.
| Maximum header width when output is set to 80 columns. Default: 70
|-
|-
|No time restriction level
| No time restriction level
|Sets the access level when a caller will not be restricted by the daily time limit as set in the caller's Time Limits section. Default: Level 6
| Level exempt from per-day time restrictions set in Time Limits. Default: 6
|-
|-
|Edit DL Description
| Edit DL Description
|Sets the access level for callers who can edit download descriptions, after using the [Z]View DL Description command to view the description first. Default: Level 7
| Level required to edit download descriptions after viewing them. Default: 7
|-
|-
|Use fast garbage collect
| Use fast garbage collect
|This is up to you on having this set or not and should depend on how your system is behaving when in operation. Default: N
| Optional performance behavior. Leave at default unless you are tuning for stability/speed on your system.<br />
Default: N
|}
|}
----
=== Additional Hints ===
Additional hints:
;Password File Fragmentation
If you expand the password database repeatedly and suspect fragmentation (slow reads), you can rebuild cleanly:
* Password File Fragmentation:
# Use pswd tools to back up the √password file.
# Create a new blank disk/partition.
# Rerun SETUP to create a new password file at the new desired maximum size.
# Use pswd tools to restore password records.
# Copy remaining files from the old disk to the new disk.
:If you later decide to increase the password database size and suspect the password file is get fragmented (slow response time during read), you could use “pswd tools" program to make a backup of your password file. Then on a new blank disk, rerun SETUP to make a new larger password file and use "pswd tools" to restore all your passwords into the new password file. Then use a file copier to copy all other files from the old disk onto the new one. This will make all files contiguous again, greatly speeding up disk access time. In the Disk Drive Assignments, you will be deciding which drive to put your password file on.
This restores contiguity and can significantly improve performance.
* Credit Exemptions
;Credit Exemptions
If a caller uploads files you do not want to count toward credits, adjust their “blocks uploaded” total in Password Maintenance to remove the undesired credit.
:If one of your callers uploads a program that you do not want to count as a credit, you will need to use Password Maintenance function to change their number of blocks uploaded variable to less than what is currently in that field (depending on the number of blocks uploaded). Say for example they already had 100 blocks uploaded and they uploaded another 50 that you do not want them to get credit for. Go into Password Maintenance and change the blocks uploaded from 150 to 100. If they had already downloaded blocks based on that upload credit, then when they call next time, they will have to upload many more blocks before they can download again.
A utility program (pswd tools) can reset upload/download counters for all callers or a single caller if you want to restart the credit system.
:Included with this package is a program called "pswd tools" that can be used to reset all or your caller's upload and download counters, or optionally just one caller's counters. This would be useful if you decided to start the credit system over after your BBS has been in operation for a while.
Credits are calculated as:<br />
(free credits) + ((uploads) × (credits per upload)) – downloads
:Credits are calculated by a formula based on the caller's number of blocks uploaded and downloaded. The formula used to calculate download credits is: (free credits) + ((uploads)x(credits per upload)) – downloads
If credits become ≤ 0, the caller must upload more before downloading again.
:This formula can calculate a negative credit if you implement this credit system on an operational BBS without first clearing the upload and download counters, or if you remove any upload credits from a caller who had already downloaded blocks based on that upload's credit, or if later you change the number of credits per upload or number of free credits variables. If the number is less than or equal to 0, then that caller will not be able to download until they upload enough blocks to make their credit status positive again.
----
<strong>SETUP - Disk Drive Assignments </strong>
=== SETUP – Disk Drive Assignments ===
This section will be used to assign which groups of files will be stored on which disk drives. It is here that you will be able to balance the load between your drives to make the most efficient use of your hardware. If at first you are not sure where to put which files, don't worry too much. Once the system starts running and if you see one drive has too many files, you can rerun SETUP, change the appropriate variables, then move the affected files.
This section assigns each file group to a drive. It is where you balance storage across devices for performance and capacity. If you later change your mind, you can rerun SETUP, adjust assignments, and move the affected files.
[[File:diskdriveassignments.png|center|200px]]
[[File:diskdriveassignments.png|center|200px]]
Each of these questions asks for four parameters.
Each assignment prompt requests four values (device, drive, and init):
The first question asks for the device number of the desired drive and can range from 8 to 30 and will default to 8 on the first run of SETUP. The second question is the drive number, typically 0 or 1, and the init string required. The picture above shows an init string for the Lt. Kernal drive, selecting LU 0 User 0 (“!l800”) with an initialization command included (“!i0”). These two commands will be sent to the command channel whenever this group of files are requested. Refer to the section "Drive Initialization Commands" for information on which init commands should be used for your system.
The device number range is 8–30. The drive number is typically 0 or 1. The init string defines how the system selects the correct partition/LU/subdirectory for that file group. The example above shows an Lt. Kernal selection of LU 0/User 0 (“!l800”) plus initialization (“!i0”). These commands are sent to the command channel whenever the associated group is accessed. See “Drive Initialization Commands” for system-specific guidance.
For each question, you can either press RETURN to accept the current value listed in brackets or you can edit the value.
{| class="wikitable
{| class="wikitable"
|-
|-
|+Disk Drive Assignment Descriptions
! Question
! Question
! Description & Settings
! Description & Settings
|-
|-
|Password File
| Password File
|Sets the device, drive number, and disk initialization command for the disk drive where the "√password file" will be stored. You can "point" this to any drive you want, but if you point it to a drive other than a 1541, make sure the drive is capable of handling relative files. For example, the SFD 1001 does a fine job with relative files, but you cannot store relative files in a chain of ICT HD partitions. 1581 and SD2IEC drives will work with REL files, but typically require the REL file to be created on a 1541 or 1571 disk or disk image first – then copied over with a REL file copier.
| Location of the √password file. The assigned drive must support REL files. SFD-1001 supports REL well; ICT chained partitions do not. 1581 and SD2IEC may require REL creation on a 1541/1571 first, then copying with a REL-aware copier.
|-
|-
|System Files
| System Files
|Stored on this drive are the welcome messages, logoff message, menus, information file, membership list, membership full message, or any message that does not fall into one of the other categories. The System Files drive should be able to store relative files.
| Welcome/logoff messages, menus, membership list, membership-full file, and other system text/data. Drive should support REL files.
|-
|-
|Help Files
| Help Files
|Stored on this drive are all the Help Files that your callers can access. See the section on the Help Files for more information on this subject.
| All caller-readable help content.
|-
|-
|Public Messages
| Public Messages
|Stored on this drive are all the public messages which your callers will post. Many of the questions in the Main Parameters (2.5.2) section relate to the Public Messages drive.
| Public message base and supporting files.
|-
|-
|Private Messages
| Private Messages
|Stored on this drive are all the private e-mail that callers can send to one another. Also stored on this drive will be the "√questxx" files for the new member applications. See the section on the new member Application routine for more information.
| Private mail plus √questxx new-user application files.
|-
|-
|Text Files
| Text Files
|Stored on this drive are all the Text Files your callers can access. See the section on Text Files for more information on this subject.
| Caller-readable text files outside the help system.
|-
|-
|Caller Log
| Caller Log
|Stored on this drive is the current caller log, a log of the most recent call, and any dated backups of the caller log.
| Current caller log, “most recent call,” and optionally daily backups.
|-
|-
|Program Files
| Program Files
|Stored on this drive are all the BASIC BBS overlays, plus any ML files which will be loaded during BBS operation. If you are using a REU, then you must enter the device number of the REU you chose when setting up your RAM DOS.
| All BBS overlays plus required ML files. If using REU, this must match the REU device number defined by RAMDOS.
|-
|-
|Network Files
| Network Files
|This will be the drive to hold all files related to Color 64 Network operations if you chose to run Network 1.26a in your Main Parameters. This drive must be able to store relative files.
| Network data and files (if Network enabled). Must support REL files.
|-
|-
|AUX 1 Files, AUX 2 Files, AUX 3 Files
| AUX 1 Files / AUX 2 Files / AUX 3 Files
|This version of Color 64 utilizes both AUX 1 and AUX3 file areas.
| AUX 1: User Profile area (signatures and banners).<br />
:AUX 1 = User Profile area for user signatures and banners
AUX 3: Games area (if used).<br />
:AUX 3 = Game area if you intend to have games on your system.
AUX 2: Reserved (unused) for future expansion.
:AUX 2 is not used and is available for expansion.
See the Programming section for information on using the Auxiliary drives.
|}
|}
As you can see, the Drive Assignments section allows you to move your files around any way you need to best balance the load between your available drives.
IMPORTANT NOTE: If you are using the Epyx Fastload cartridge, you must use “ui” as the drive command for Program Files or you may experience intermittent lockups.
IMPORTANT NOTE: If you are using the Epyx Fastload cartridge you MUST always use "ui" as the drive command for Program Files or you will experience intermittent system lockups.
After completing the assignments, SETUP will ask “Is this correct?” Answer N to revise, or Y to continue to Upload/Download Directories.
Again, you will be asked "Is this correct?" If you need to change any of the previous answers, answer "N" and you will be taken through all the questions again. If you are sure everything is correct, just enter “Y" and press RETURN. Then you will be taken to the Upload/Download Directories section.
In this section of setup, you will go through a series of questions defining each of your upload and download directories. You can set up to 26 different directories on any number of drives. Each directory will be assigned a description, download status, upload status, access level, device number, drive number and a drive command.
This section defines your upload/download directories (A–Z). Each directory has a name, upload/download status, access level, and its own device/drive/init settings.
You will want to give each UD Directory a unique name since your callers will reference this name when selecting drives. The first drive that has a “Y" in the download status field will be the system's default download drive and the first drive with a "Y" in the upload status field will be the system’s default upload drive. This can be the same drive (simply by entering "Y" in both download and upload status fields) or totally separate drives. You need to make sure the access level assigned to these drives is for the lowest level callers. You would not want the system to default to one of your restricted download directories!
You must create at least one upload and one download directory, even if you intend to restrict access. To effectively disable transfers for callers, set their access level to 9 (sysop) or 10.
The first thing you need to do is enter the number of directories you would like to have on your system. You can have up to 26 directories, and each directory is referenced by a letter from A to Z. While you are entering the directory information, you should also keep track of the directories and their ID letter on paper. After you enter the number of directories, if you didn't change the number of directories (if previously set up), then you will be asked which directory you wish to edit. Enter the letter assigned to a directory to edit its information.
[[File:numberofdirectories.jpeg|center|200px]]
[[File:numberofdirectories.jpeg|center|200px]]
You will be asked to enter the following information described in the table below for each directory:
{| class="wikitable"
{| class="wikitable
|-
|-
|+Directory Information Query Fields
! Question
! Question
! Details
! Details
|-
|-
|Description
| Description
|The description is the name of the directory as you want it to appear in the list of UD directories. It should not be more than 30 characters in length, and you will not be allowed to include quotation marks in the description.
| Display name for the directory (up to 30 characters). Quotes are not permitted.
|-
|-
|Allow Downloads
| Allow Downloads
|If you want to allow downloads from this directory, then answer "Y" to this question. If this directory is the first directory that has "Y" selected here, it will be the default download directory for all callers, regardless of their access level. This means that if a caller were to use the [D]Download command without first using the [#] Change Directory command, then they will be accessing the default download directory.
| Enables downloads from this directory. The first directory marked Y becomes the default download directory.
|-
|-
|Allow Uploads
| Allow Uploads
|If you want to allow uploads to this directory, then answer "Y" to this question. If this directory is the first directory that has "Y" selected here, it will be the default upload directory for all callers, regardless of their access level. This means that if a caller were to use the [U] Upload command without first using the [#] Change Directory command, then they would be accessing the default upload directory.
| Enables uploads to this directory. The first directory marked Y becomes the default upload directory.
|-
|-
|Access Level
| Access Level
|This is the access level that will apply to all callers attempting to access the directory unless the directory happens to be the default upload or download directory. You can set the level to 10 to effectively "turn off” the directory.
| Minimum level required to use the directory (unless it is the default upload/download directory). Use 10 to effectively disable.
|-
|-
|Device, Drive, Init
| Device, Drive, Init
|This is just like the questions in the Disk Drive Assignments section above.
| Same structure as Disk Drive Assignments.
|}
|}
Once you enter the information for all the directories, you will return to the question asking which directory you wish to edit. If you do not wish to change any more information, then you can just press RETURN. Otherwise, you can enter the letter of the directory to edit, or you can press "-" to go back to the question asking for the number of directories.
When finished entering directories, you will return to the edit prompt. Press RETURN to continue. If SETUP loops back instead of continuing, you likely did not mark at least one upload and one download directory as enabled.
Whether or not you decide to have file transfers available, you must have at least one upload and one download directory created. To prohibit users from utilizing the transfer area, set your level access for these to SYSOP (level 9) or level 10.
If you decide not to edit any other directories, you will be asked "Is this correct?" If you need to change any of the previous answers, answer "N" and you will be taken through all the questions again. If you are sure everything is correct, just press "Y". Then you will be taken to the next section of the SETUP program. If after answering "Y", the program still jumps back to the beginning of the Uploads/Downloads section instead of going on to the next screen, you probably have not assigned at least one download and one upload directory.
<strong>SETUP - User's Time Limits </strong>
These questions will be used to set the time limits for the different access levels. First you will be asked to set the maximum time allowed "per call” for levels 1-5 during AM hours and again during PM hours. This is different than the maximum allowed per day in that a caller may get 60 minutes per day but might only be allowed 30 minutes per call during PM hours, forcing them to not tie up the BBS for a continuous amount of time during what is normally the busier hours. In the default system setup, this variable applies to all callers with access levels 1 through 5, and access levels 6 and above are exempt. This can be changed through the "No time restriction level" in Main Parameters (section 2.6). You might give your close friends level 6, so they will not be disconnected prematurely. Any value from 1 to 999 is ok. Note that if you do not want a "per call" time limit, then set either/both values to 999.
The next question is asking for the time required to pass before a level 1-5 caller can get back onto the system. You would use this value to prevent one caller from staying online for the maximum "per call" time limit, then immediately calling back for another session. Any value from 0 to 30 is ok. If you do not care to use this "between calls" feature, just put a 0 in this location. Again, access level 6 callers and above are exempt from this variable, unless you change the "No time restriction level" in Main Parameters.
----
The remaining questions in this section are about the daily time limits for access levels 1 through 9. Any value from 1 to 999 is ok; set them any way you see fit.
=== SETUP – User’s Time Limits ===
The system will not disconnect a caller if they are in the middle of a download or entering a message and their time expires, but the system will "borrow" the extra time used from the next day. So, if a caller has a 20 minute per daytime limit and spends 60 minutes typing feedback, the system will enter -40 minutes in that caller's membership record. Then every night at midnight, this time will be increased by 20 minutes. This caller would not be allowed back onto the system until their daily time limit goes positive again (3 days in this example). Note that all callers are subject to these limits, regardless of the setting of “No time restriction level" in Main Parameters.
Time limits apply by access level:
At the end of this section, once again you will be asked "Is this correct?" If you need to change any of the previous answers, answer "N" and you will be taken through all the questions again. If you are sure everything is correct, just enter “Y" and press RETURN.
* Per-call limits for Levels 1–5 (AM and PM), with higher levels exempt by default (controlled by “No time restriction level”).
* Time-between-calls delay for Levels 1–5.
* Daily time limits for Levels 1–9.
If a caller exceeds their time while downloading or composing a message, the system will not disconnect them mid-action. Instead, it “borrows” the extra time from the next day by storing a negative balance and restoring time nightly at midnight.
<strong>SETUP - Caller Purge </strong>
At the end, SETUP will ask “Is this correct?” Answer N to revise, or Y to continue.
The next section is where you will assign the number of days that must pass before the BBS's purge routine will automatically delete a member that has not called in a while. When the BBS deletes a member, they are completely deleted; there is no way to bring them back unless you have a "√backup password" file you can use to restore their record. An example might be to set the system to automatically delete any level 1 not calling in 15 days, level 2 not calling in 31 days, or level 3 not calling in 62 days. And set all other levels to 999 days so the system will not automatically delete them (you can use the membership expiration feature to lower their access level to a 2 after a set number of days or when their fees run out).
----
The way this routine works is every night at midnight, each password record is evaluated and if that caller has not called in the defined number of days, they are deleted. An entry is made into the caller log (their record number followed by an asterisk to differentiate from a membership expired status). As a safety check, when the system calculates the number of days since the last call and compares it to the current date, if the calculation exceeds the purge variable by more than 7 days, the system will not delete that caller. Without this safety check, if you accidentally entered the wrong year while loading the BBS and the system processed its "end of day” routines, ALL your members would have been deleted! I strongly urge you to use the caller purge feature, it will make the long-term maintenance of the BBS a lot easier.
=== SETUP – Caller Purge ===
At the end of this section, once again you will be asked "Is this correct?" If you need to change any of the previous answers, answer "N" and you will be taken through all the questions again. If you are sure everything is correct, just enter “Y" and press RETURN.
Caller purge automatically removes inactive accounts based on access-level thresholds you define. Deleted accounts are permanently removed unless you restore from a √backup password file.
The purge runs nightly at midnight. A safety check prevents mass deletion if the system clock is incorrect: if the calculated inactivity exceeds your purge value by more than 7 days, the record is not deleted.
<strong>SETUP - Message Categories </strong>
At the end, SETUP will ask “Is this correct?” Answer N to revise, or Y to continue.
This screen will be used to enter the message base categories. You can have anywhere from 2 to 18 categories. When a message is posted, the caller will be asked to select from one of these categories for their message. When a caller reads the messages, they will be given the option to read just the messages in one category or the messages in all the categories that they have access to.
----
Each category will have an access level assigned to it. Any callers with a level lower than the category’s level will not see any messages in that category. It is recommended that you assign your category levels in order with the lowest levels at the top of the screen and the highest at the bottom so lower-level users will see a consecutive list of choices.
=== SETUP – Message Categories ===
You will not be able to use quotation marks in your message category titles, because quotes in the name could cause errors when the BBS is reading in the "√bbs.parms" file.
Defines message categories (2–18). Each category has a required access level. Callers below that level will not see or access the category.
Again, you will be asked "Is this correct?" If you need to change one of the previous categories, answer "N" and you will be taken through all the questions again. If you are sure everything is correct, just enter a "Y” and press RETURN.
Avoid quotation marks in category names; quotes can cause issues when reading √bbs.parms.
At the end, SETUP will ask “Is this correct?” Answer N to revise, or Y to continue.
<strong>SETUP - BBS Commands </strong>
----
The next section is where you can really start to customize your system. Every command that your caller’s type from the main command prompt and the level required to execute that command are SYSOP defined. For example, if you do not like "O" for logoff, you can change it to "G" (goodbye). But then you need to remember to assign something different for the graphics command. And if you like level 1 callers to be able to read all messages, you will be able to adjust that here too. The commands marked "spare 1” through "spare 9" are for future expansion, although the system comes with Mod Menu pre-installed in spare 4. For now, setting the access level for the unused spare commands to 10 will eliminate them from the system. Currently, if anyone selects an unused spare command (and has a high enough access level), the BBS will load in the appropriate module and then just return to the command prompt. These have been left like this so you will be able to easily add your own modules to Color 64 BBS using these commands. The spare commands are something you can make use of later, after you are more familiar with Color 64 BBS.
=== SETUP – BBS Commands ===
The table below provides a summary of all the commands built into Color 64, with their default character assignments and levels:
This section lets you define each command key and the minimum access level required. You can change command letters to match your style, reserve features for higher levels, and disable unused “spare” commands by setting them to level 10.
{| class="wikitable
{| class="wikitable"
|-
|-
|+Default System Command Settings
! Key
! Key
! Name
! Name
Line 390:
Line 373:
! Description
! Description
|-
|-
|R
| R
|Read Messages
| Read Messages
|2
| 2
|Read public messages
| Read public messages
|-
|-
|@
| @
|Post Office
| Post Office
|1
| 1
|Post Office sub-menu*
| Post Office sub-menu*
|-
|-
|P
| P
|Post a Message
| Post a Message
|3
| 3
|Post a public message
| Post a public message
|-
|-
|S
| S
|Scratch a Message
| Scratch a Message
|3
| 3
|Scratch a public message
| Delete a public message
|-
|-
|$
| $
|Show Directory
| Show Directory
|1
| 1
|Displays directory of current directory selection
|Games (8.10a default) - note that "*" is still available, if desired
| Games (8.10a default)
|4
| 4
|Takes user to games menu
| Games menu shortcut
|-
|-
|1
| 2
|User Profile
| User Profile
|1
| 1
|Allows user to customize email signature/banner
| Signature/banner editing
|-
|-
|%
| %
|Protocol Select
| Protocol Select
|3
| 3
|Allows selection of specific protocol for file transfer
| Select transfer protocol
|-
|-
|=
| =
|Post Network Mail
| Post Network Mail
|3
| 3
|Send public/private network message ***
| Network mail (if enabled)***
|-
|-
|&
| &
|Billing Maintenance
| Billing Maintenance
|9
| 9
|Billing / Node maintenance ***
| Billing/node maintenance***
|-
|-
|<nowiki>-</nowiki>
| -
|Release Public
| Release Public
|8
| 8
|Release public nets holding ***
| Release public nets holding***
|}
|}
<nowiki>*</nowiki> This is a menu of 5 options: Post a Message, Read / Send E-mail, Feedback, Membership List.
<nowiki>*</nowiki> Post Office includes: Post a Message, Read/Send E-mail, Feedback, and Membership List. Options not permitted by the caller’s access level will not be shown.<br />
If a caller doesn't have the access level to use an option, it will not be accessible.
<nowiki>**</nowiki> User Settings include: page-pauser lines, character delay, and 40/80 column selection.<br />
<nowiki>***</nowiki> Network commands are disabled if Network is not enabled. See the Network documentation for details.
----
=== SETUP – Color Code Setup ===
Defines the eight color values used by the system. To change a bar, type its number and then the color control code (example: 1 then COMMODORE/7 for medium blue). Adjust until satisfied, then press RETURN to continue.
<nowiki>**</nowiki> Change customized information such as the number of lines for the page-pauser, character delay, and 40/80 column selection.
----
<nowiki>***</nowiki> Network commands will be disabled if you chose not to run Network.
=== SETUP – Carrier Status ===
For information on these commands and the Restrict Posts setting, see the Network documentation.
Determines how the system detects modem carrier. This is critical for stable operation. Ensure the modem is connected, powered on, and not actively connected to a caller. If necessary, disconnect the phone line to avoid false detection.
<strong>SETUP - Color Code Setup </strong>
If you change modem types or relevant modem switches later, rerun SETUP and repeat this section.
The next screen is where you will define the 8 colors that Color 64 BBS will use. Throughout the program, whenever we want text in a different color, the BBS will select the next color from this sequence. You will see 9 reverse bars of numbers on the screen. To change the color for bar 1, just type 1 then type the control code for the desired color. For example, to make bar 1 medium blue, you would type 1 followed by Commodore/7. The bar will change colors right away. This gives you an idea of what these colors will look like next to each other. Keep adjusting the colors until you have this screen looking the way you like, then just press RETURN.
Press RETURN when ready.
----
<strong>SETUP - Carrier Status </strong>
=== SETUP – Saving the Parameters ===
This section of SETUP is used to determine how the system recognizes if the modem is detecting a carrier signal. This is important because it allows the BBS to know when someone is connected to the system, or if they have disconnected. If the carrier status is not correctly determined, then the system will most likely not work at all. The screen will tell you to make sure your modem is connected, turned on and ready to receive a call, but to make sure that no one is connected to it. It is recommended that you unplug the phone line from the modem to make sure no one is connected or that a dial tone will not generate a false carrier detect status. The BBS will now be ready to learn the carrier status of your modem. If at any time in the future you change modem types or switches insider your modem, it is important that you rerun SETUP with the modem connected so that the new carrier detect can be determined. Also, if you change your system from a non-SwiftLink system to a SwiftLink system or vice versa, you must run SETUP and select this section, otherwise your system will not run correctly.
After completing all sections, return to the SETUP main menu and select option 10 to save parameters.
When you are ready, press RETURN.
Two key files are created:
<strong>SETUP - Saving the Parameters </strong>
* √bbs.parms (stored on the Program Files drive). This includes drive assignments and system parameters required for normal operation and recovery.
* √password file (created on the drive assigned in Drive Assignments). This stores caller records including names, passwords, access, time remaining, last message read, etc.
If you are just setting up your system, you will return to the main menu once all sections have been completed. From the SETUP menu you should now select option 10 to save your parameters to your Program files. You should see some disk access while the SETUP program creates the necessary files. If you selected a large number for the Maximum Password Number, then it may take some time for the password file to be created.
After the initial SETUP, the password file includes a SYSOP account (member number 2) with name SYSOP and password SYSOP. Member #2 must remain reserved for SYSOP because feedback messages are delivered to this mailbox.
Before opening the board, change your sysop name/password using Password Maintenance (F6 at the waiting-for-call screen or “<” while online).
When finished, there should be two new files on your system.
The “√” (shifted @) prefix on system files hides them from callers and prevents download access.
* The first file is "√bbs.parms" and must always be on your Program disk or in your Program files. This file that stores the drive assignments which is critical for the BBS to know where to find the various file groups.
----
* The second file just created is the "√password file" and it will be created on the disk assigned by the Drive Assignments section. This password file is where all your caller's names, passwords, access levels, time remaining today, last message read, etc. are stored. After the first initial use of SETUP, there is only one password in the password file: Member number 2 with the name “SYSOP” and password “SYSOP”. The SYSOP must always have membership number 2 as all user’s feedback messages are sent to this user number.
=== SETUP – Editing/Changing Parameters ===
Use the Password Maintenance routine (F6 from the call waiting screen or "<" while online) to change your name and password (see description below) before putting the BBS online for the public to call.
To change any parameters later, rerun +setup. The existing √bbs.parms file is loaded, and previously saved values appear as defaults. Press RETURN to keep values you do not want to change, and edit only the items you do.
Notice that all these file names have a check mark (√) in front of their name. This same check mark (shifted @) will precede all BBS filenames. This special code prevents anyone from being able to download any of these files and possibly reading your password file, feedback, or someone else's mail.
When finished, select option 10 again to write an updated √bbs.parms file.
<strong>SETUP – Editing/Changing the Parameters </strong>
If you increase “Maximum password number,” SETUP will ask whether to expand the password file. Expanding can be done immediately (Y) or record-by-record later (N). Record-by-record expansion can be slower during live operation.
If at any time you decide that you need to change any of the above parameters, just load the "SETUP" program again. The existing "√bbs.parms" file will be read into memory and you will be able to select any of the sections displayed on the main menu. Previously stored values will be shown as the default for each of the questions and you can just hit RETURN to accept the current value, allowing you to quickly move through all the questions you don't wish to change; just keep hitting RETURN until you get to the parameter you want changed.
----
After you have edited all the sections you wish to change, just select option 10 from the main menu and a new "√bbs.parms" file will be written to disk. If you did not change the maximum password number, then the password file will not be affected. Reducing the maximum password number will not change the file either, but those records already stored beyond the maximum number will be inaccessible. If you increased the maximum password number, you will be asked if you wish to expand the password file to the new number. If you answer "N", then the system will simply add a new relative file record for each new member. If you answer "Y", the file will be expanded to allow new member records to be stored. The difference between these two is that adding new records one by one (answering "N" to expand the file) can be somewhat slow while a caller is online.
=== SETUP – Printing the Parameters ===
Option 12 prints the parameters. A printer must be available as device 4 and be online. You may print a single section or all parameters.
<strong>SETUP - Printing the Parameters </strong>
Next Section: [[prior to running|Prior to Running]]
From the SETUP main menu, you can also select option 12 to print a list of the parms you have entered. From the print menu, you can decide to print just one of the sections, or you can print all the parms. Be sure you have a printer hooked up to the computer as device number 4, and that the printer is online.
SETUP is where you define how Color 64 will operate on your system: message limits, credit rules, modem behavior, disk assignments, directories, time limits, categories, and command permissions. If you are unsure about a specific prompt, it is usually safe to accept the default value shown in brackets and fine-tune later. The notes below explain how each option affects day-to-day operation.
Main Parameters
The Main Parameters section controls core BBS behavior such as message limits, upload/download rules, credit handling, access levels, and modem settings.
Question
Description & Settings
Maximum lines per message
Limits the number of lines permitted in a single message.
Default: 100
Range: 20–200
Maximum columns per line
Sets the default word-wrap width used by local-mode tools (such as the editor).
Default: 38
Suggested: 38 for 40-column systems; 78 for 80-column output.
Maximum # of messages
Maximum number of public messages retained online. When the limit is reached, older messages are deleted as new ones are posted.
Default: 50
Range: 25–232
Considerations: 1541 disks allow only 144 directory entries per disk. SFD-1001 allows 224. Hard drive style systems may allow far more, but the BBS itself tops out at 232.
Maximum password number
Sets the maximum number of member records in the √password file.
Default: 100
Range: 25–9999
Considerations: 1541 limit is roughly 720 records. If exceeded, new callers will receive the “√membership full” message when attempting to apply. Roughly 1 disk block is used per user record.
This value can be increased later, but expanding repeatedly over time may fragment the file and slow access. See “Password File Fragmentation” hints below for a clean rebuild method.
Minimum blocks-cycle msgs
Minimum free blocks required on the Public Messages drive before messages begin cycling.
Default: 50
Recommended: 25–75
If free blocks drop below this value, each new public post will delete the oldest public message even if the maximum message count has not been reached.
Minimum blocks-allow uploads
Minimum free blocks required to permit uploads.
Default: 75
Recommended: 10–75
If private messages share this same disk, do not set below 25. The BBS will not allow private mail to be sent if free blocks fall below 25.
Never set below 10. Space is required for directory processing and temporary files after uploads. The “free upload space” shown to callers is automatically reduced by this value.
Maximum downloads per call
Maximum number of downloads allowed per caller session. Enter 99 for a practical “no limit.” Callers who reach the limit must log off and back on to continue downloading. Exemptions can be granted via “No DL file limit level.”
Download credits per call
Sets how many download-credit blocks a caller earns per block uploaded.
New mbr download credits
Free download credits granted to each new caller. Once used, callers must upload to earn additional credits (unless exempt).
Credit system exempt level
Access level at which callers become exempt from the credit system. If you are not using credits, set to 1 so all callers are exempt.
Max files on public msgs drive
Maximum directory entry count permitted on the Public Messages drive. The system checks after each user logoff.
Recommendations:
1541: ~135 messages
SFD-1001: ~210
SD2IEC / LTK: ~200–250, or enter 0 to avoid file counting
Higher limits increase message indexing time at boot and may reduce available memory.
Number of days to hold mail
Maximum days private mail is retained before automatic deletion.
When mail is purged, an entry is written to the caller log at midnight indicating the member number affected. A safety buffer prevents mass deletion if the system clock is accidentally wrong: if calculated mail age exceeds the purge value by more than 7 days, that mail will not be deleted.
New User Access Level
Sets the access level assigned to new callers. Some sysops prefer Level 1 until validation; others start users higher. Default level meanings are summarized below.
Typical use of levels (defaults):
1
Recommended for unverified new users
Read System Messages
Create Profile/Signature
Very limited system time
2
“Browse” level
Includes Level 1
Adds read access to public messages and text files
3
Standard contributor level
Includes Level 2
Adds posting, uploads, and downloads
4–5
Full normal access
Same abilities; use categories, time limits, and directory levels to differentiate
Common network approach: Level 4 non-network; Level 5 network-approved
6
Privileged callers
Exempt from per-call time limit
No download limit per call
No time-between-calls restriction
7
Helper sysops/moderators
Scratch public messages or downloads
Edit download descriptions
Release uploads
8
High-level sysop (co-sysop)
Set clock/date
Change user access levels (cannot elevate to sysop)
Read caller log
Warning: Level 8 can view other users’ passwords
9
Full sysop
Password maintenance
Full DOS functions
Should be limited to you (and possibly one trusted backup)
Mbrs expired access level
Level assigned automatically when a caller’s membership expiration date is reached. The expiration date is stored per user record and is checked at midnight. Useful for trial memberships or time-limited access.
Upload auto-release level
Determines what access level is required for an upload to be automatically released as a public download. Lower-level uploads can be held for sysop review.
System Baud Rate
Sets the maximum communications rate between the computer and modem/interface. The system can step down based on the caller’s capabilities (and modem requirements).
If you are not using SwiftLink, the practical maximum is 2400. With SwiftLink, 38,400 BPS is supported in many configurations, including TCPSER, where the computer-to-modem rate can remain high even if the modem-to-modem connection is lower, depending on the “Adjust BPS to connect rate” setting.
DD$ MCI on
Controls whether MCI commands may print the DD$ field from a caller’s password record. DD$ is an 8-character sysop-defined note field (for example SYSOP, GUEST, REMOTE). Answer N to keep DD$ private from MCI output.
Using Upload Descriptions
Enables download description files (stored as @filename). Most sysops should answer Y. If directory-entry limits are a concern (notably on SFD-1001), descriptions reduce the maximum number of downloads because each file consumes an additional directory entry. Manual description creation remains possible via the Edit Download Description command.
Mutiple dirs. per drive
Enables multiple logical directories on the same physical drive. When enabled, the BBS prefixes uploaded filenames internally with a letter (A–Z) for grouping. Callers do not see the prefix. If you manually add files, you must rename them with the correct leading letter. If you answer N, no renaming is required and everything resides in a single directory.
Daily Log Backup
Enables nightly caller log backup and rotation at midnight. If N, the caller log remains a running recent-history file. If Y, the log is dated and archived daily, then cleared. Log size trimming is governed by “Caller log max size blocks” and “Caller log trim blocks,” as well as the “Minimum blocks-allow uploads” threshold.
Rerun on Errors
Restarts the BBS automatically after BASIC errors. Normally this should be enabled. Disable only while actively modifying/testing overlays. When enabled, STOP is disabled; breaking requires SHIFT+COMMODORE+CTRL.
Screen Blanking
If enabled, blanks the local sysop screen when callers read or write private mail (excluding feedback to sysop and console-local use). Use this based on your privacy philosophy and moderation needs.
Does your modem support DTR
Indicates whether your modem/interface supports DTR drop for disconnect. Most Hayes-compatible modems and TCPSER support DTR. Some hardware behaves better with DTR disabled (notably certain 1670 setups). If unsure, answer N.
Adjust BPS to connect rate
Controls whether the computer should step down its BPS rate to match the modem connect rate. Many 1200/2400 modems expect this; some high-speed setups (including many TCPSER configurations) can run 38,400 computer-to-modem regardless of connect rate. This may require experimentation depending on your modem.
Run Network v1.26a
Enables Color 64 Network features (sharing messages/files between participating systems). New sysops should normally answer N until the system is stable and coordination with another network sysop is complete. If enabled, you must run +net setup afterward.
Modem Init Command
Initialization command sent to the modem before accepting a caller. Must start with lowercase “at”. Recommended strings vary by modem type. Verbose mode (v1) is essential. If the BBS shows OK at init, the string is accepted; if it shows ERROR, remove unsupported parts and test again in a terminal.
Sent before each outgoing network call. Some sysops disable error correction for network calls if their modem’s MNP interferes. Default (ate0) has worked well for many v8.1a network setups.
Scratch any msg level
Level required to delete any public message (not just the caller’s own). Default: 7
Category/Link level
Level required to change message category or thread link. Default: 7
Merge seq file level
Level required to merge a SEQ file into a message via the editor “*” command. Default: 7
Caller log delete level
Level required to delete the caller log. Default: 8
Message MCI level
Level required to use Message MCI commands. Default: 2
Variable MCI level
Level required to use Variable MCI commands. This should be restricted to trusted sysops due to crash potential from misuse. Default: 9
No DL file limit level
Level exempt from “Maximum downloads per call.” Default: 6
Min msg memory bytes
Minimum free memory permitted while editing before the system stops accepting new lines. Higher values reduce garbage-collection pauses; lower values allow larger messages. Typical values: 300–700.
Caller log max size blocks
Maximum size of the caller log file (blocks). If exceeded, the log is trimmed using “Caller log trim blocks.”
Default: 50
Range: 8–200
Caller log trim blocks
Blocks removed when trimming is triggered (by size or low disk space). Should not exceed half of “Caller log max size blocks.”
Default: 8
Range: 4–100
Validate via email level
Level required to validate a caller through e-mail workflows. Default: 8
Edit any message level
Level required to edit any public message (not only the caller’s own). Default: 9
Max chars/40 column header
Maximum header width when output is set to 40 columns. Default: 30
Max chars/80 column header
Maximum header width when output is set to 80 columns. Default: 70
No time restriction level
Level exempt from per-day time restrictions set in Time Limits. Default: 6
Edit DL Description
Level required to edit download descriptions after viewing them. Default: 7
Use fast garbage collect
Optional performance behavior. Leave at default unless you are tuning for stability/speed on your system.
Default: N
Additional Hints
Password File Fragmentation
If you expand the password database repeatedly and suspect fragmentation (slow reads), you can rebuild cleanly:
Use pswd tools to back up the √password file.
Create a new blank disk/partition.
Rerun SETUP to create a new password file at the new desired maximum size.
Use pswd tools to restore password records.
Copy remaining files from the old disk to the new disk.
This restores contiguity and can significantly improve performance.
Credit Exemptions
If a caller uploads files you do not want to count toward credits, adjust their “blocks uploaded” total in Password Maintenance to remove the undesired credit.
A utility program (pswd tools) can reset upload/download counters for all callers or a single caller if you want to restart the credit system.
Credits are calculated as:
(free credits) + ((uploads) × (credits per upload)) – downloads
If credits become ≤ 0, the caller must upload more before downloading again.
SETUP – Disk Drive Assignments
This section assigns each file group to a drive. It is where you balance storage across devices for performance and capacity. If you later change your mind, you can rerun SETUP, adjust assignments, and move the affected files.
Each assignment prompt requests four values (device, drive, and init):
The device number range is 8–30. The drive number is typically 0 or 1. The init string defines how the system selects the correct partition/LU/subdirectory for that file group. The example above shows an Lt. Kernal selection of LU 0/User 0 (“!l800”) plus initialization (“!i0”). These commands are sent to the command channel whenever the associated group is accessed. See “Drive Initialization Commands” for system-specific guidance.
Question
Description & Settings
Password File
Location of the √password file. The assigned drive must support REL files. SFD-1001 supports REL well; ICT chained partitions do not. 1581 and SD2IEC may require REL creation on a 1541/1571 first, then copying with a REL-aware copier.
System Files
Welcome/logoff messages, menus, membership list, membership-full file, and other system text/data. Drive should support REL files.
Help Files
All caller-readable help content.
Public Messages
Public message base and supporting files.
Private Messages
Private mail plus √questxx new-user application files.
Text Files
Caller-readable text files outside the help system.
Caller Log
Current caller log, “most recent call,” and optionally daily backups.
Program Files
All BBS overlays plus required ML files. If using REU, this must match the REU device number defined by RAMDOS.
Network Files
Network data and files (if Network enabled). Must support REL files.
AUX 1 Files / AUX 2 Files / AUX 3 Files
AUX 1: User Profile area (signatures and banners).
AUX 3: Games area (if used).
AUX 2: Reserved (unused) for future expansion.
IMPORTANT NOTE: If you are using the Epyx Fastload cartridge, you must use “ui” as the drive command for Program Files or you may experience intermittent lockups.
After completing the assignments, SETUP will ask “Is this correct?” Answer N to revise, or Y to continue to Upload/Download Directories.
SETUP – Upload/Download Directories
This section defines your upload/download directories (A–Z). Each directory has a name, upload/download status, access level, and its own device/drive/init settings.
You must create at least one upload and one download directory, even if you intend to restrict access. To effectively disable transfers for callers, set their access level to 9 (sysop) or 10.
Question
Details
Description
Display name for the directory (up to 30 characters). Quotes are not permitted.
Allow Downloads
Enables downloads from this directory. The first directory marked Y becomes the default download directory.
Allow Uploads
Enables uploads to this directory. The first directory marked Y becomes the default upload directory.
Access Level
Minimum level required to use the directory (unless it is the default upload/download directory). Use 10 to effectively disable.
Device, Drive, Init
Same structure as Disk Drive Assignments.
When finished entering directories, you will return to the edit prompt. Press RETURN to continue. If SETUP loops back instead of continuing, you likely did not mark at least one upload and one download directory as enabled.
SETUP – User’s Time Limits
Time limits apply by access level:
Per-call limits for Levels 1–5 (AM and PM), with higher levels exempt by default (controlled by “No time restriction level”).
Time-between-calls delay for Levels 1–5.
Daily time limits for Levels 1–9.
If a caller exceeds their time while downloading or composing a message, the system will not disconnect them mid-action. Instead, it “borrows” the extra time from the next day by storing a negative balance and restoring time nightly at midnight.
At the end, SETUP will ask “Is this correct?” Answer N to revise, or Y to continue.
SETUP – Caller Purge
Caller purge automatically removes inactive accounts based on access-level thresholds you define. Deleted accounts are permanently removed unless you restore from a √backup password file.
The purge runs nightly at midnight. A safety check prevents mass deletion if the system clock is incorrect: if the calculated inactivity exceeds your purge value by more than 7 days, the record is not deleted.
At the end, SETUP will ask “Is this correct?” Answer N to revise, or Y to continue.
SETUP – Message Categories
Defines message categories (2–18). Each category has a required access level. Callers below that level will not see or access the category.
Avoid quotation marks in category names; quotes can cause issues when reading √bbs.parms.
At the end, SETUP will ask “Is this correct?” Answer N to revise, or Y to continue.
SETUP – BBS Commands
This section lets you define each command key and the minimum access level required. You can change command letters to match your style, reserve features for higher levels, and disable unused “spare” commands by setting them to level 10.
Key
Name
Level
Description
R
Read Messages
2
Read public messages
@
Post Office
1
Post Office sub-menu*
P
Post a Message
3
Post a public message
S
Scratch a Message
3
Delete a public message
$
Show Directory
1
Display directory of current selection
D
Download a File
3
Single or multi-download
#
Change Directory
3
Select a different directory
U
Upload File
3
Upload a file
!
Edit User Settings
1
Caller preferences (pause, delay, 40/80, etc.)**
F
Send Feedback
1
Send sysop feedback
C
Page SYSOP for Chat
1
Chat request
A
Alter Password
1
Change caller password
O
Logoff
1
Log off and hang up
G
Graphics On/Off
1
Toggle graphics
H
Help
1
Read help files
W
Welcome Message
1
Re-read welcome message
M
Membership List
1
List/search members
I
Information
1
View BBS info file
E
Edit a Message
3
Edit a public message
↑
Set Time & Date
9
Change system date/time
>
DOS Wedge
9
SYSOP DOS wedge
<
Password Maintenance
9
User/password maintenance
N
New Downloads
3
Scan for new downloads
X
Scratch a Download
7
Remove a download
T
Text Files
2
View text file list
L
Caller Log
8
View caller log
+
Multi-Upload
3
Multi-upload (Punter)
Z
View DL Description
3
View a download description
Y
Release a Download
7
Approve upload for public access
*
Games/Modules
3
Module menu (8.0/8.1 default)
1
Games (8.10a default)
4
Games menu shortcut
2
User Profile
1
Signature/banner editing
%
Protocol Select
3
Select transfer protocol
=
Post Network Mail
3
Network mail (if enabled)***
&
Billing Maintenance
9
Billing/node maintenance***
-
Release Public
8
Release public nets holding***
* Post Office includes: Post a Message, Read/Send E-mail, Feedback, and Membership List. Options not permitted by the caller’s access level will not be shown.
** User Settings include: page-pauser lines, character delay, and 40/80 column selection.
*** Network commands are disabled if Network is not enabled. See the Network documentation for details.
SETUP – Color Code Setup
Defines the eight color values used by the system. To change a bar, type its number and then the color control code (example: 1 then COMMODORE/7 for medium blue). Adjust until satisfied, then press RETURN to continue.
SETUP – Carrier Status
Determines how the system detects modem carrier. This is critical for stable operation. Ensure the modem is connected, powered on, and not actively connected to a caller. If necessary, disconnect the phone line to avoid false detection.
If you change modem types or relevant modem switches later, rerun SETUP and repeat this section.
Press RETURN when ready.
SETUP – Saving the Parameters
After completing all sections, return to the SETUP main menu and select option 10 to save parameters.
Two key files are created:
√bbs.parms (stored on the Program Files drive). This includes drive assignments and system parameters required for normal operation and recovery.
√password file (created on the drive assigned in Drive Assignments). This stores caller records including names, passwords, access, time remaining, last message read, etc.
After the initial SETUP, the password file includes a SYSOP account (member number 2) with name SYSOP and password SYSOP. Member #2 must remain reserved for SYSOP because feedback messages are delivered to this mailbox.
Before opening the board, change your sysop name/password using Password Maintenance (F6 at the waiting-for-call screen or “<” while online).
The “√” (shifted @) prefix on system files hides them from callers and prevents download access.
SETUP – Editing/Changing Parameters
To change any parameters later, rerun +setup. The existing √bbs.parms file is loaded, and previously saved values appear as defaults. Press RETURN to keep values you do not want to change, and edit only the items you do.
When finished, select option 10 again to write an updated √bbs.parms file.
If you increase “Maximum password number,” SETUP will ask whether to expand the password file. Expanding can be done immediately (Y) or record-by-record later (N). Record-by-record expansion can be slower during live operation.
SETUP – Printing the Parameters
Option 12 prints the parameters. A printer must be available as device 4 and be online. You may print a single section or all parameters.
