Creating boot files: Difference between revisions

Latest revision as of 17:35, 23 February 2026

Installation – Creating the Boot Files

Creating the Boot Files

The next step in the installation process is to use the included bootmaker utility to generate the boot programs required to start Color 64. All boot programs begin with a “+” symbol. The +bbs file you previously copied to the Boot Files is an example.

These boot programs are essential because they store important configuration parameters, including whether you are using hardware such as the SwiftLink RS-232 cartridge or a TurboMaster CPU.

The bootmaker utility works by loading the +bbs program into memory, modifying it based on your selections, and then saving updated boot files back to disk. For this reason, the +bbs file must already exist on your Boot disk before running bootmaker.

Running the Bootmaker Program

Insert your Boot disk, then LOAD and RUN the program named:

bootmaker

During execution, you will be prompted for device numbers, drive numbers, and initialization commands.

Device numbers must be between 8 and 30.
Drive numbers must be 0 or 1.
Initialization commands may be up to 16 characters.

Refer to the section Drive Initialization Commands for proper syntax.

When entering drive initialization commands:

Do not remove or add quotation marks.
Multiple commands may be separated with “!”
The boot programs can access only drive 0 or drive 1 of a device.

You may press RETURN to accept defaults where appropriate.

Bootmaker Questions Explained

Device, Drive, and Init Command for Boot Programs

Enter the parameters for the drive containing your Boot Files. This drive must contain the +bbs program.

For SD2IEC users operating in native directory mode (not disk images), ensure your folder structure is finalized before running bootmaker.

Example SD2IEC folder layout:

Folder	Purpose	Example Init Command
ROOT (//)	Program and System Files	0:!cd//
PUBMSGS	Public Messages	0:!cd//pubmsgs
PRIVMSGS	Private Messages	0:!cd//privmsgs
UD64UPLOADS	Upload Area	0:!cd//ud64uploads
UD64GAMES	Download Area – Games	0:!cd//ud64games
UD64UTIL	Download Area – Utilities	0:!cd//ud64util
HELP	Help and Text Files	0:!cd//help

Running System with Ram Expansion Unit

You will be asked whether you are using a Commodore 17XX-series REU.

If this is your first installation, it is recommended to complete setup without the REU first. Once the system is stable, you may rerun bootmaker and SETUP to enable REU support.

Answer “Y” only if you intend to run overlays from the REU.

Boot Drive

Enter the device, drive, and initialization parameters for your Boot drive. This is the drive from which you will load +SETUP and other boot utilities.

This may be the same as your Program drive if sufficient space is available.

Program Drive

Enter the parameters for the drive containing your overlays.

If you are using a single disk drive and must swap disks during boot, use the same parameters as the Boot drive.

If using an REU:

This refers to the device from which overlays will be loaded before transfer to RAMDOS.
Drive will always be 0.
ICT users should note that the included ICT utility assumes the REU is device 15.

Need to Swap Disks

If Boot and Program drives are identical and you have only one physical drive, answer “Y”.

If using the smaller “bm small” utility, this question will not appear.

Using TurboMaster CPU

Answer “Y” if you are running the Schnedler Systems 4.09 MHz TurboMaster CPU.

Using SwiftLink Cartridge

Answer “Y” if you are using a CMD SwiftLink cartridge (or SwiftLink CRT image in VICE).

Using Lt. Kernal HD

If you answered “N” to SwiftLink, you will be asked whether you are using a Lt. Kernal hard drive. Answer “Y” if applicable.

SwiftLink Address

If SwiftLink is enabled, you must specify its memory address.

Factory default: $DE00

Optional hardware modifications may set it to:

$DF00
$D700

If unsure, use $DE00. If modem communication fails, verify the correct address.

Completion

After all questions are answered, bootmaker will create the necessary boot programs on the disk containing +bbs.

Standard boot files created include:

+reboot
+setup
+net setup
+editor
+shell

If REU support was enabled, the following will also be created:

+ram.start
+ram.restart
+ram.reinit
+ram.bbs
+ram.reboot

These files are approximately three disk blocks each and will be used regularly during system operation.

Next Section: Boot Program ("+") Details"

Installation

@@ Line 1: / Line 1: @@
-[[installation|Installation]] - <strong>Creating the Boot Files</strong>
+[[installation|Installation]] – '''Creating the Boot Files'''
-The next step to accomplish is to use the included "bootmaker" utility to create the boot programs that start the essential BBS operations.  All the boot programs begin with a "+" (plus sign) symbol; the +bbs program you copied to the boot files is an example of this.  Creating these boot programs is very important because you set some important parameters for the system, such as whether you are using the SwiftLink RS-232 cartridge.
+== Creating the Boot Files ==
+The next step in the installation process is to use the included ''bootmaker'' utility to generate the boot programs required to start Color 64. All boot programs begin with a “+” symbol. The +bbs file you previously copied to the Boot Files is an example.
+These boot programs are essential because they store important configuration parameters, including whether you are using hardware such as the SwiftLink RS-232 cartridge or a TurboMaster CPU.
-The bootmaker utility creates your boot programs by loading in the +bbs boot program, modifying it, and then storing it back to disk along with the other boot programs.  For this reason, it is necessary that you already have the +bbs program present in the Boot Files.
+The bootmaker utility works by loading the +bbs program into memory, modifying it based on your selections, and then saving updated boot files back to disk. For this reason, the +bbs file must already exist on your Boot disk before running bootmaker.
-<strong>Running the Bootmaker Program</strong>
+----
-Insert your boot disk, then LOAD and RUN the "bootmaker" program.
-Note: You will be asked several times for device, drive, and init commands for disk drives.  In all the questions, these parameters are limited to specific ranges.  The device number must be in the range of 8 to 30, the drive number must only be 0 or 1, and the init command can be a maximum of 16 characters.  Read the section entitled "Drive Initialization Commands" for information on the proper init command for your disk drives.  Note that the drive init command is always preceded by a quotation mark in the bootmaker questions.  This allows special characters like colons to be entered in the init command, but the quote mark will NOT be part of the drive init command.  Do not delete the quote mark, or enter any other quote marks, or you may cause an error.  One more note about the drive init command: You can separate multiple commands with the “!” (exclamation point) character, but the "i" command will not change the default drive number as described in the section "Drive Initialization Commands".  If you are not familiar with this feature, just remember that the boot programs can only access drive 0 or 1 or a disk device.  In the drive parameter questions you can simply press RETURN to accept the default.  You can also edit the line by retyping it or by using the left and right cursor keys.
+=== Running the Bootmaker Program ===
+Insert your Boot disk, then LOAD and RUN the program named:
-The following questions will occur:
+bootmaker
-* Device, Drive and Init command for boot programs:
-:The first question you will be asked is the device, drive, and init command for the drive your boot programs are stored on.
+During execution, you will be prompted for device numbers, drive numbers, and initialization commands.
-:For this question, you should enter the information for the drive that you copied all the boot files to; it must have the "+bbs" program stored on it.  Edit this if necessary and press RETURN.  The program will then notify you that it is loading the "+bbs" program into memory.
+* Device numbers must be between 8 and 30.
+* Drive numbers must be 0 or 1.
+* Initialization commands may be up to 16 characters.
-:For SD2IEC using raw directory (not disk images), ensure your folder structure is the way you want it prior to running this step. For example, a folder called “Help” for help files, one for “Aux3” for games, or “System” for your system folder. Here is an example of a good folder breakdown on SD2IEC:
+Refer to the section ''[https://www.color64wiki.itchybutt.org/index.php/Initialization_commands Drive Initialization Commands]'' for proper syntax.
-:{| class="wikitable
+When entering drive initialization commands:
+* Do not remove or add quotation marks.
+* Multiple commands may be separated with “!”
+* The boot programs can access only drive 0 or drive 1 of a device.
+You may press RETURN to accept defaults where appropriate.
+----
+=== Bootmaker Questions Explained ===
+'''Device, Drive, and Init Command for Boot Programs'''
+Enter the parameters for the drive containing your Boot Files. This drive must contain the +bbs program.
+For SD2IEC users operating in native directory mode (not disk images), ensure your folder structure is finalized before running bootmaker.
+Example SD2IEC folder layout:
+{| class="wikitable"
 |-
-!Folder
+! Folder
-!For
+! Purpose
-!Drive/Initialization Command
+! Example Init Command
 |-
-|ROOT (//)
+| ROOT (//)
-|Program/System Files
+| Program and System Files
-|0:!cd//
+| 0:!cd//
 |-
-|PUBMSGS
+| PUBMSGS
-|Public Message Area
+| Public Messages
-|0:!cd//pubmsgs
+| 0:!cd//pubmsgs
 |-
-|PRIVMSGS
+| PRIVMSGS
-|Private Message Area
+| Private Messages
-|0:!cd//privmsgs
+| 0:!cd//privmsgs
 |-
-|UD64UPLOADS
+| UD64UPLOADS
-|Upload Area
+| Upload Area
-|0:!cd//ud64uploads
+| 0:!cd//ud64uploads
 |-
-|UD64GAMES
+| UD64GAMES
-|Download Area – 64 Games
+| Download Area – Games
-|0:!cd//ud64games
+| 0:!cd//ud64games
 |-
-|UD64UTIL
+| UD64UTIL
-|Download Area – 64 Utilities
+| Download Area – Utilities
-|0:!cd//ud64util
+| 0:!cd//ud64util
 |-
-|HELP
+| HELP
-|Help Files / Text files
+| Help and Text Files
-|0:!cd//help
+| 0:!cd//help
 |}
-* Running system with Ram Expander
-: Next, you will be asked if you are going to run your system with a Commodore 17XX series Ram Expansion Unit.  When first setting up your system, consider waiting on this option until you are familiar with the system and have a successful setup. Once you are in a good state, you can re-run bootmaker and your SETUP program to reconfigure your system.  Otherwise, answer "Y" to this question if you have an REU and you want to run your overlays on it.
-* Boot Drive
-:Next, you will be asked to enter the device, drive, and init parameters for your Boot drive.  This is the drive that you will be running your Boot Files on; with all the files you use to create your Boot disk.  This can be the same as your Program Files drive if you have the available drive space.  The boot programs will use this information when loading your utilities like +SETUP, so this must be the drive that you will always use to load your boot programs from.
-* Program Drive
-:After this, you will be asked to enter the parameters for the Program drive.  This is the drive that the Program Files (overlays) are stored on.  If you have a separate Program disk, and you will need to swap the disks during the boot operation, then this should be the same as the Boot drive question.
-:External Drive: If you are using a REU on your system, then this will be the device your Program Files will be loaded from (Device 15 is commonly used but is user-defined when RAM Dos is run). Drive will always be “0”. ICT HD users note: The included ICT utility overlay assumes you have your REU set to device 15.
+'''Running System with Ram Expansion Unit'''
-* Need to Swap Disks
-:If you entered the same parameters for your Boot drive and Program drive, the system will ask if you need to swap disks when booting your BBS system.  If you have separate Boot and Program disks and only one disk drive to boot from then you need to answer "Y" to this question.  If you are using the "bm small" program, then this question will not be asked.
+You will be asked whether you are using a Commodore 17XX-series REU.
-* Using TurboMaster CPU
-:Next, you will be asked if you are using the Schnedler Systems 4.09 Mhz  TurboMaster CPU.  If you have one and you wish to run your system with the Turbo Master device, answer "Y" to this question.
+If this is your first installation, it is recommended to complete setup without the REU first. Once the system is stable, you may rerun bootmaker and SETUP to enable REU support.
-* Using SwiftLink Cartridge
-:The next question asks if you are using the Creative Micro Designs SwiftLink RS-232 cartridge.  If you do have the cartridge (or have the CRT file attached in VICE) and you want to use it with your system, answer "Y" to this question.
+Answer “Y” only if you intend to run overlays from the REU.
-* Using Lt. Kernal HD
-:The next question depends on your answer to the SwiftLink question.  If you answered "N" to the SwiftLink question, then you will be asked if you are using a Lt. Kernal Hard Drive on your system.  You must answer "Y" to this question IF you are using Lt. Kernal.  Otherwise, the system will not run properly.
+'''Boot Drive'''
-* SwiftLink Address
-:If you answer "Y" to the SwiftLink question, then you will be asked a technical question regarding the installation of your SwiftLink cartridge.  The SwiftLink cartridge must use a certain portion of the computer's memory to allow programs to interface with the cartridge.  The stock SwiftLink cartridge shipped by CMD is set to occupy the section of memory known as page $DE00.  There is an optional hardware modification that users can perform to change this address to either $DF00 or $D700.  If you have never modified your SwiftLink cartridge, then simply use $DE00.  Otherwise, those who have modified their cartridge will know what the address is set to.  If you are not sure then just use $DE00, and then if the BBS program is not sending or receiving from the modem you will know that this needs to be changed to one of the other two addresses (a little experimentation may be necessary).
+Enter the device, drive, and initialization parameters for your Boot drive. This is the drive from which you will load +SETUP and other boot utilities.
+This may be the same as your Program drive if sufficient space is available.
+'''Program Drive'''
+Enter the parameters for the drive containing your overlays.
+If you are using a single disk drive and must swap disks during boot, use the same parameters as the Boot drive.
+If using an REU:
+* This refers to the device from which overlays will be loaded before transfer to RAMDOS.
+* Drive will always be 0.
+* ICT users should note that the included ICT utility assumes the REU is device 15.
+'''Need to Swap Disks'''
+If Boot and Program drives are identical and you have only one physical drive, answer “Y”.
+If using the smaller “bm small” utility, this question will not appear.
+'''Using TurboMaster CPU'''
+Answer “Y” if you are running the Schnedler Systems 4.09 MHz TurboMaster CPU.
+'''Using SwiftLink Cartridge'''
+Answer “Y” if you are using a CMD SwiftLink cartridge (or SwiftLink CRT image in VICE).
+'''Using Lt. Kernal HD'''
+If you answered “N” to SwiftLink, you will be asked whether you are using a Lt. Kernal hard drive. Answer “Y” if applicable.
+'''SwiftLink Address'''
+If SwiftLink is enabled, you must specify its memory address.
+Factory default: $DE00
+Optional hardware modifications may set it to:
+* $DF00
+* $D700
+If unsure, use $DE00. If modem communication fails, verify the correct address.
+----
+=== Completion ===
+After all questions are answered, bootmaker will create the necessary boot programs on the disk containing +bbs.
+Standard boot files created include:
+* +reboot
+* +setup
+* +net setup
+* +editor
+* +shell
+If REU support was enabled, the following will also be created:
+* +ram.start
+* +ram.restart
+* +ram.reinit
+* +ram.bbs
+* +ram.reboot
+These files are approximately three disk blocks each and will be used regularly during system operation.
-You made it through your first stage of setup! You will observe the system create the boot programs on the disk with the "+bbs" program on it. These include “+reboot”, “+setup”, “+net setup”, “+editor” and “+shell”. If you opted for REU use, you will also see “+ram.start”, “+ram.restart”, “+ram.reinit”, “+ram.bbs” and “+ram.reboot” created. These will be the files you frequently use in the operation of your system and each of them are approximately 3 blocks in size.
+Next Section: [[boot program details|Boot Program ("+") Details"]]
 [[installation|Installation]]