Preconfigured builds: Difference between revisions

From Color 64 BBS Wiki
No edit summary
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[installation|Installation]] – '''Pre-Configured Builds'''
[[installation|Installation]] – '''Pre-Configured Builds'''


Three pre-configured builds of Color 64 v8.1a are available in the Downloads section. Each build includes customized overlays appropriate for its intended configuration. The original, unmodified overlays are also included in the directory “D64 Masters” should you wish to revert or reference them.
== Pre-Configured Builds ==
Three pre-configured builds of Color 64 v8.1a are available in the Downloads section. Each build includes customized overlays tailored to its intended configuration. The original, unmodified overlays are also included in the directory “D64 Masters” for reference or restoration purposes.


= SD2IEC Build (Commodore 64 / 128 in 64 Mode) =
----
 
'''Color 64 v8.1a SD2IEC Build'''
 
This build is designed for use on a Commodore 64 or Commodore 128 (in 64 mode) utilizing an SD2IEC device assigned to drive 8. The configuration was developed and tested using an SD2IEC drive and a WiModem (cbmstuff.com).
 
An REU (RAM Expansion Unit) is recommended but not required. While the system operates properly without one, an REU can improve performance, particularly when loading larger overlays. Users running JiffyDOS or similar acceleration solutions may also experience improved loading performance.
 
== Image Format ==


The download is provided as a 4GB SD card image. It may be written to an SD card using tools such as:
=== SD2IEC Build ===


* Balena Etcher
This build is designed for use on a Commodore 64 or Commodore 128 operating in 64 mode with an SD2IEC device assigned as drive 8. The configuration was developed and tested using an SD2IEC device in combination with a WiModem (cbmstuff.com).
* Raspberry Pi Imager


Once written to a freshly formatted SD card, the system is immediately usable with no additional installation steps required. Running +SETUP after first boot is strongly encouraged to review and customize configuration settings.
An REU (RAM Expansion Unit) is recommended but not required. While the system functions without one, an REU improves performance when loading larger overlays. Systems using JiffyDOS or similar acceleration solutions may also experience improved load times.


The build may be expanded beyond SD drive use through +SETUP modifications if desired.
The download is provided as a 4GB SD card image. It may be written to an SD card using tools such as Balena Etcher or Raspberry Pi Imager.


== Included Directories ==
Once written to a freshly formatted SD card, the system is immediately usable. No additional installation steps are required. Running +SETUP after first boot is strongly encouraged to review and customize configuration settings.


The SD2IEC image includes the following pre-configured folders:
If you are using TurboMaster, SwiftLink, an REU, or Lt. Kernal HD, re-run the BOOTMAKER 8100 program to properly configure the system for your hardware. Otherwise, the system is ready to operate as imaged.


* '''Aux1''' – Auxiliary 1 drive; supports the BBS.PROFILE module (user profile area) 
'''Included folders in this build:'''
* '''Aux2''' – Auxiliary 2 drive 
* '''Aux3''' – Auxiliary / Games drive 
* '''Uploads''' – Storage location for uploaded files 
* '''Downloads''' – Storage location for downloadable files 
* '''Dracopy''' – File copy utility included for system management 
* '''Help''' – Help and text files 
* '''Network''' – Supporting files for Network 1.26a 
* '''Primsgs''' – Private messages 
* '''Pubmsgs''' – Public messages 
* '''Pswd''' – Password storage 
* '''BBS Documents''' – Documentation for PC use (this manual) 


If you are using TurboMaster, SwiftLink, an REU, or Lt. Kernal HD, you must re-run the BOOTMAKER 8100 program to configure the system appropriately for your hardware. Otherwise, the system is ready to operate immediately after imaging the SD card.
* Aux1 – Auxiliary 1 drive; supports the BBS.PROFILE module (user profile area)
* Aux2 – Auxiliary 2 drive
* Aux3 – Auxiliary / Games drive
* Uploads – Storage location for uploaded files
* Downloads – Storage location for downloadable files
* Dracopy – File copy utility included for system management
* Help – Help and text files
* Network – Supporting files for Network 1.26a
* Primsgs – Private messages
* Pubmsgs – Public messages
* Pswd – Password storage
* BBS Documents – Documentation for PC use (this manual)


----
----


= LTK Builds (Linux and Windows PC) =
=== The LTK Builds for Linux and Windows PC ===


The LTK builds are designed for use with VICE and TCPSER on either Linux (tested on Kubuntu and Fedora 43) or Windows 11 systems.
The LTK builds are designed for use with VICE and TCPSER on either Linux (tested on Kubuntu and Fedora 43) or Windows 11 systems.
Line 49: Line 41:
These builds are pre-configured and are in a near ready-to-run state. Three Logical Units (LUs) are defined with the following assignments:
These builds are pre-configured and are in a near ready-to-run state. Three Logical Units (LUs) are defined with the following assignments:


== Logical Unit Assignments ==
==== Logical Unit Assignments ====


* '''LU 0 / User 0''' – Programs, System files, Help files, Text files, Caller Log, Network files
* LU 0 / User 0 – Programs, System files, Help files, Text files, Caller Log, Network files
* '''LU 1 / User 0''' – Public and Private messages
* LU 1 / User 0 – Public and Private messages
* '''LU 1 / User 1–5''' – Download categories 1 through 5
* LU 1 / User 1–5 – Download categories 1 through 5
* '''LU 1 / User 15''' – Uploads
* LU 1 / User 15 – Uploads
* '''LU 2 / User 0''' – Auxiliary 1 files (includes user signature information)
* LU 2 / User 0 – Auxiliary 1 files (includes user signature information)
* '''LU 2 / User 1''' – Auxiliary 2 files (not utilized in this build)
* LU 2 / User 1 – Auxiliary 2 files (not utilized in this build)
* '''LU 2 / User 3''' – Auxiliary 3 files (Game area)
* LU 2 / User 3 – Auxiliary 3 files (Game area)


== Build Details ==
==== Additional Details ====


* LTK-specific performance modifications from the Color 64 v8.0 disks have been incorporated into the overlays as recommended by the original developers. See the “Faster Disk Access” section of [[Ltkernal|LTK Specific System Requirements]].
* LTK-specific performance modifications from the Color 64 v8.0 disks have been incorporated into the overlays as recommended by the original developers. See [[Ltkernal|LTK Specific System Requirements]] for details.
* BOOTMAKER has already been completed.
* BOOTMAKER has already been completed.
* Modification of Main Parameters within +SETUP is not required but strongly recommended prior to deployment.
* Modification of Main Parameters within +SETUP is not required but is strongly recommended prior to deployment.
* The MODEM INIT string in +SETUP is preconfigured for TCPSER operation at 38400 baud.
* The MODEM INIT string in +SETUP is preconfigured for TCPSER operation at 38400 baud.
* Two games are pre-installed. Additional games are included on Disks 4 and 5 (D64 files) in this distribution.
* Two games are pre-installed. Additional games are included on Disks 4 and 5 (D64 files) in this distribution.
* After adding or modifying games, update the file “√games menu” located on LU 2 / User 3. See [[Adding_games|Adding Games]] for details.
* After adding or modifying games, update the file “√games menu” located on LU 2 / User 3. See [[Adding_games|Adding Games]] for instructions.


----
----


= Installation =
==== Installation ====


== Linux ==
Linux users:
* Follow youtube video: https://youtu.be/gZ7ZIUoozGw?si=nqisVV5DO1Ui04YV
* Extract the build into your home directory.
* Open a terminal in the extracted directory.
* Run: ./vicebuild.sh


1. Extract the build into your home directory.
Windows users:
2. Open a terminal in the extracted directory.
* Follow youtube video: https://youtu.be/kHbFkHLsW88?si=8BuSQAUF90obOBzX
3. Run:
* Extract the build into a local user directory such as Documents.
* No build script is required.


  ./vicebuild.sh
Mac OS users:
* Download Mac LTK package
* Extract into home directory
* Follow README.TXT file included with package
* Ensure all scripts (.sh) are executable (or perform chmod +x on them)
* Begin installation by either double-clicking "install bbs.command" or by running "./vicebuild-macos-v2.sh" in terminal


== Windows ==
[[File:Linux LTK operations.png|450px]]


1. Extract the build into a local user directory (such as Documents).
<i>Itchy Butt and Westwood BBS on Linux</i>
2. No build script is required.


----
----


= Optional: Email Notification Feature =
==== Running the LTK Build ====
 
If you would like to enable email notifications of BBS activity:
 
1. Install Python 3 (if not already installed).
2. Edit '''notify.py''' to configure:
  * SMTP server information 
  * BBS login username and password 


3. Modify '''√BBS.INIT''' at lines 35705–35706:
Linux:
  * Set the username and password to match notify.py 
* Open a terminal in the color64_v81a_ltk directory.
  * Verify your PC’s IP address is correctly defined 
* Run: ./mybbs.sh


4. Edit '''mybbs.sh''' (Linux only):
Windows:
  * Remove the remark from the python3 execution line 
* Open Windows Explorer.
* Double-click mybbs.bat.


5. While the BBS is running:
Mac OS:
  * At the call screen, press the Up Arrow key (mapped to "\" on a PC keyboard) to enable or disable notifications.
* open Finder and go to installed directory (default: color64bbs in home folder)
* double-click on "run bbs.command" or execute in terminal with "./mybbs-macos.sh"


See [[email notification|Email Notification Option]] for full configuration details.
This launches both VICE and TCPSER. Default port is 8502.


----
----


= Running the LTK Build =
==== Operating the System ====


== Linux ==
From the READY prompt:


1. Open a terminal in the color64_v81a_ltk directory.
* L +BBS – Load and run the BBS
2. Run:
* L +SETUP – Enter system configuration
* L +EDITOR – Load the screen editor


  ./mybbs.sh
----
 
This launches both VICE and TCPSER. The default port is 8502.
 
== Windows ==
 
1. Open Windows Explorer.
2. Double-click:
 
  mybbs.bat
 
This launches both VICE and TCPSER. The default port is 8502.


----
=== Optional: Email Notification Feature ===


= Operating the System =
To enable email notifications of BBS activity:


From the READY prompt:
* Install Python 3 if not already installed.
* Edit notify.py to configure SMTP server information and your chosen BBS login credentials.
* Modify √BBS.INIT at lines 35705–35706:
** Ensure the username and password match those defined in notify.py.
** Verify your PC’s IP address is correctly defined.
* At your PC, edit mybbs.sh and remove the remark from the python3 execution line.
* While the BBS is running, at the call screen press the Up Arrow key (mapped to "\" on a PC keyboard) to enable or disable notifications.


* '''L +BBS''' – Load and run the BBS 
See [[email notification|Email Notification Option]] for complete configuration details.
* '''L +SETUP''' – Enter system configuration
* '''L +EDITOR''' – Load the screen editor 


Next Section: [[bbs operation|BBS Operation]]
Next Section: [[bbs operation|BBS Operation]]


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

Latest revision as of 02:14, 9 May 2026

InstallationPre-Configured Builds

Pre-Configured Builds

Three pre-configured builds of Color 64 v8.1a are available in the Downloads section. Each build includes customized overlays tailored to its intended configuration. The original, unmodified overlays are also included in the directory “D64 Masters” for reference or restoration purposes.


SD2IEC Build

This build is designed for use on a Commodore 64 or Commodore 128 operating in 64 mode with an SD2IEC device assigned as drive 8. The configuration was developed and tested using an SD2IEC device in combination with a WiModem (cbmstuff.com).

An REU (RAM Expansion Unit) is recommended but not required. While the system functions without one, an REU improves performance when loading larger overlays. Systems using JiffyDOS or similar acceleration solutions may also experience improved load times.

The download is provided as a 4GB SD card image. It may be written to an SD card using tools such as Balena Etcher or Raspberry Pi Imager.

Once written to a freshly formatted SD card, the system is immediately usable. No additional installation steps are required. Running +SETUP after first boot is strongly encouraged to review and customize configuration settings.

If you are using TurboMaster, SwiftLink, an REU, or Lt. Kernal HD, re-run the BOOTMAKER 8100 program to properly configure the system for your hardware. Otherwise, the system is ready to operate as imaged.

Included folders in this build:

  • Aux1 – Auxiliary 1 drive; supports the BBS.PROFILE module (user profile area)
  • Aux2 – Auxiliary 2 drive
  • Aux3 – Auxiliary / Games drive
  • Uploads – Storage location for uploaded files
  • Downloads – Storage location for downloadable files
  • Dracopy – File copy utility included for system management
  • Help – Help and text files
  • Network – Supporting files for Network 1.26a
  • Primsgs – Private messages
  • Pubmsgs – Public messages
  • Pswd – Password storage
  • BBS Documents – Documentation for PC use (this manual)

The LTK Builds for Linux and Windows PC

The LTK builds are designed for use with VICE and TCPSER on either Linux (tested on Kubuntu and Fedora 43) or Windows 11 systems.

These builds are pre-configured and are in a near ready-to-run state. Three Logical Units (LUs) are defined with the following assignments:

Logical Unit Assignments

  • LU 0 / User 0 – Programs, System files, Help files, Text files, Caller Log, Network files
  • LU 1 / User 0 – Public and Private messages
  • LU 1 / User 1–5 – Download categories 1 through 5
  • LU 1 / User 15 – Uploads
  • LU 2 / User 0 – Auxiliary 1 files (includes user signature information)
  • LU 2 / User 1 – Auxiliary 2 files (not utilized in this build)
  • LU 2 / User 3 – Auxiliary 3 files (Game area)

Additional Details

  • LTK-specific performance modifications from the Color 64 v8.0 disks have been incorporated into the overlays as recommended by the original developers. See LTK Specific System Requirements for details.
  • BOOTMAKER has already been completed.
  • Modification of Main Parameters within +SETUP is not required but is strongly recommended prior to deployment.
  • The MODEM INIT string in +SETUP is preconfigured for TCPSER operation at 38400 baud.
  • Two games are pre-installed. Additional games are included on Disks 4 and 5 (D64 files) in this distribution.
  • After adding or modifying games, update the file “√games menu” located on LU 2 / User 3. See Adding Games for instructions.

Installation

Linux users:

Windows users:

Mac OS users:

  • Download Mac LTK package
  • Extract into home directory
  • Follow README.TXT file included with package
  • Ensure all scripts (.sh) are executable (or perform chmod +x on them)
  • Begin installation by either double-clicking "install bbs.command" or by running "./vicebuild-macos-v2.sh" in terminal

Itchy Butt and Westwood BBS on Linux


Running the LTK Build

Linux:

  • Open a terminal in the color64_v81a_ltk directory.
  • Run: ./mybbs.sh

Windows:

  • Open Windows Explorer.
  • Double-click mybbs.bat.

Mac OS:

  • open Finder and go to installed directory (default: color64bbs in home folder)
  • double-click on "run bbs.command" or execute in terminal with "./mybbs-macos.sh"

This launches both VICE and TCPSER. Default port is 8502.


Operating the System

From the READY prompt:

  • L +BBS – Load and run the BBS
  • L +SETUP – Enter system configuration
  • L +EDITOR – Load the screen editor

Optional: Email Notification Feature

To enable email notifications of BBS activity:

  • Install Python 3 if not already installed.
  • Edit notify.py to configure SMTP server information and your chosen BBS login credentials.
  • Modify √BBS.INIT at lines 35705–35706:
    • Ensure the username and password match those defined in notify.py.
    • Verify your PC’s IP address is correctly defined.
  • At your PC, edit mybbs.sh and remove the remark from the python3 execution line.
  • While the BBS is running, at the call screen press the Up Arrow key (mapped to "\" on a PC keyboard) to enable or disable notifications.

See Email Notification Option for complete configuration details.

Next Section: BBS Operation

Installation