C64 OS GETTING STARTED GUIDE

Document version:
C64 OS: User's Guide.

Step 1. Requirements:
What you need to run C64 OS

C64 OS lives to take advantage of new hardware that you can add to your Commodore 64. It starts with mass storage, but that's just the beginning.

If you missed it, checkout the showcase of C64 OS + Hardware Collections. These example combinations show a range of hardware expansions from the simplest necessary to get more out of your C64 with C64 OS, to more advanced hardware that looks great and provides more opportunities that C64 OS can take advantage of.

Your hardware investments are made better and more powerful with C64 OS.


Minimum hardware requirements

  • Commodore 64 computer
  • Joystick
  • SD2IEC drive* **
A C64 Breadbin. A standard C64 Joystick. One of many SD2IEC drives.

* C64 OS can access all your floppy disk drives, but a mass-storage device with support for native CMD-style subdirectories is required for the system drive. Check out the Commodore 8-Bit Buyer's Guide for a wide range of mass storage devices commercially available for the C64.

** SD2IEC is the least expensive of the supported storage device families. But, IDE64, CMD HD, RAMLink, or an CMD FD Series drive can be used in place of an SD2IEC.

JiffyDOS or another speedloader that SD2IEC supports, such as an Epyx FastLoad Reloaded cartridge, is a practical requirement for reasonable load times.


Recommended hardware alternatives

  • Commodore 64, C64c, SX-64, Ultimate 64, C128, C128D or compatible computer
  • 1351 mouse, or MicroMys or MouSTer compatible adapter
  • IDE64, SD2IEC, CMD HD or RAMLink
  • 17xx REU or compatible
  • JiffyDOS KERNAL ROM*
  • A ZiModem WiFi Modem (support coming in the future)
A C64c, or Ultimate 64. A 1351 Mouse. One of many SD2IEC drives.
A 1541 Ultimate II+ provides an REU up to 16MB. JiffyDOS KERNAL ROM Upgrade. Link232 WiFi, highspeed WiFi Modem with ZiModem firmware.

* An Epyx FastLoad Reloaded cartridge or other speedloader that SD2IEC supports can be used as an alternative to JiffyDOS, but C64 OS boots nearly 2X as fast with JiffyDOS as it does with FastLoad.


Alternative requirements

C64 OS can also be installed in the VICE emulator, and use VICE's support for an emulated 1351 mouse and CMD HD or IDE64.

  • A Mac or PC
  • VICE version 3.5 or greater

Step 2. Installation: How to install C64 OS

Make a backup first

A commercial copy of C64 OS ships on an SD Card called the System Card. If you have a Mac or PC, you should make a backup of the contents of the System Card first. Insert the card into an SD Card slot on your Mac or PC and copy all the files and directories to a folder on another device for safe keeping.

Backups are for your personal use only. Help support software development on the Commodore 64, and don't share your backups. Developers — OpCoders Inc.

C64 OS can be installed on three main families of devices: SD2IEC, IDE64 or a CMD HD or RAMLink. Follow the instructions for the device family you are installing to.

For installation on VICE, see Chapter 2: Installation of the C64 OS User's Guide.


Set up on SD2IEC

If you have an SD2IEC and you want to use it as your C64 OS system drive, the System Card comes ready for use on your C64. Insert the card into your SD2IEC device. If your SD2IEC device uses a mini or micro SD Card slot, use a Mac or PC to transfer the contents of the original System Card to a card that is compatible with your drive.

Load and run "c64os" from the SD2IEC device. It does not have to be device #8.

Load and Run c64os.

This runs the C64 OS Setup Tool.

C64 OS Setup Tool.

If you have not yet read the C64 OS Software License Agreement, you should read that first. Press "y" to confirm that you have read it and agree.

C64 OS is already installed on the System Card, but the booter needs to be set up for the correct device #, partition # and system directory name. Press "s", or press RETURN, to begin the System Card first run set up.

C64 OS Setup Tool - First Run Installation Set up.

Press RETURN to accept the default values for device # and partition #. Press RETURN to accept the default of "os" for the system directory name. To confirm that these are correct and continue, press "y".

C64 OS Setup Tool - Final Option.

Although C64 OS is ready to be booted, some configuration is recommended for your specific hardware before you boot C64 OS for the first time.

Press "c" to load and run the C64 OS Configure Tool. This is described in the configuration section below.


Installation on IDE64

The System Card contains two copies of C64 OS. One copy is already installed on the System Card, ready for use on the C64 with an SD2IEC. The second copy is in the form of an installation archive file and the installer tools.

If you have an SD2IEC but prefer to install C64 OS to IDE64, you can use SD2IEC to transfer the installation files to IDE64.

If you do not have an SD2IEC, you can transfer the files from a Mac or PC to IDE64 via PCLink. Consult the IDE64 User's Guide for further information about using PCLink to transfer files.

C64 OS must be installed in the root directory of an IDE64 partition. Transfer the four files from the root directory of the System Card to the root directory of the partition on your IDE64 where you want to install C64 OS. Only the file "c64os" and the directory "os" will need to remain in the root directory after installation is complete.

Filename Purpose Notes
c64os C64 OS booter. Transfer to root directory of IDE64 partition.
c64os setup Installation setup program. Transfer to root directory of IDE64 partition.
restore.car Installation archive file. Transfer to root directory of IDE64 partition.
c64restore Installer program. Transfer to root directory of IDE64 partition.

Note about PCLink

If you use PCLink, you must run the ideservd server program with the -P or --allprg option. This ensures that the files transfer to your IDE64 as PRG type files.

Confirm that all four files are of type PRG on the IDE64 before proceeding. If they are not PRG type files, something went wrong and installation will not proceed correctly.


Load and run "c64os setup" from the IDE64 device. It does not have to be device #8.

Load and Run c64os setup.

This runs the C64 OS Setup Tool.

C64 OS Setup Tool.

If you have not yet read the C64 OS Software License Agreement, you should read that first. Press "y" to confirm that you have read it and agree.

You have only copied the installation tools and the installation archive file to the IDE64. You now have to perform an installation. Press "f" to begin a fresh installation.

C64 OS Setup Tool - Fresh Installation.

Press RETURN to accept the default source device # and target device #. Press RETURN again to accept the default target partition # and proceed with the installation. The default device and partition numbers are autodetected as the current device and partition when the Setup Tool was loaded.

The installer program is run automatically. It states that it is opening the restore.car file, and outputs the note from that archive file. It then proceeds and outputs the name of each directory and file that is extracted from the installation archive.

When the installer finishes it says "Unarchiving Complete" and you are returned to the READY prompt. Although C64 OS is ready to be booted, some configuration is recommended for your specific hardware before you boot C64 OS for the first time. This is described in the configuration section below.


Installation on CMD HD or RAMLink

The System Card contains two copies of C64 OS. One copy is already installed on the System Card, ready for use on the C64 with an SD2IEC. The second copy is in the form of an installation archive file and the installer tools.

If you have an SD2IEC but prefer to install C64 OS to a CMD HD or RAMLink, you can use SD2IEC to transfer the installation files to the CMD device.

If you have an IDE64 but prefer to install C64 OS to a CMD HD or RAMLink, you can use the IDE64 and PCLink to transfer the installation files to the CMD device.

If you do not have an SD2IEC or IDE64, an alternative method of transferring the installation files to your CMD HD or RAMLink is required. SD2IEC is probably the easiest method for transferring files from a Mac or PC to a C64. SD2IEC devices are available in a variety of form factors and price points, most are reasonably inexpensive. Even if you prefer to use a CMD HD or RAMLink as your C64 OS system drive, purchasing an SD2IEC is a solid investment.

C64 OS must be installed in the root directory of a CMD native partition, with at least 9000 blocks free. Transfer the four files from the root directory of the System Card to the root directory of the partition of the CMD device where you want to install C64 OS. Only the file "c64os" and the directory "os" will need to remain in the root directory after installation is complete.

Filename Purpose Notes
c64os C64 OS booter. Transfer to root directory of CMD native partition.
c64os setup Installation setup program. Transfer to root directory of CMD native partition.
restore.car Installation archive file. Transfer to root directory of CMD native partition.
c64restore Installer program. Transfer to root directory of CMD native partition.

Load and run "c64os setup" from the CMD device. It does not have to be device #8.

Load and Run c64os setup.

This runs the C64 OS Setup Tool.

C64 OS Setup Tool.

If you have not yet read the C64 OS Software License Agreement, you should read that first. Press "y" to confirm that you have read it and agree.

You have only copied the installation tools and the installation archive file to the CMD device. You now have to perform an installation. Press "f" to begin a fresh installation.

C64 OS Setup Tool - Fresh Installation.

Press RETURN to accept the default source device # and target device #. Press RETURN again to accept the default target partition # and proceed with the installation. The default device and partition numbers are autodetected as the current device and partition when the Setup Tool was loaded.

The installer program is run automatically. It states that it is opening the restore.car file, and outputs the note from that archive file. It then proceeds and outputs the name of each directory and file that is extracted from the installation archive.

When the installer finishes it says "Unarchiving Complete" and you are returned to the READY prompt. Although C64 OS is ready to be booted, some configuration is recommended for your specific hardware before you boot C64 OS for the first time. This is described in the configuration section below.


Step 3. Configuration: How to configure C64 OS

The C64 OS system directory contains a settings subdirectory in which are found most of the C64 OS settings files. In the settings directory is a program called "configure" that runs from the C64's READY prompt. This configures a C64 OS installation for your specific hardware.

Most settings can be configured from within C64 OS. The Configure Tool ensures that C64 OS is able to make use of the hardware that is connected to your C64 on the first run. If your hardware configuration changes (for example, if your mouse breaks and you need to use a joystick) you can re-run the Configure Tool at any time, from the READY prompt.

To manually start the Configure Tool, change the current directory to "//os/settings/" on the C64 OS system drive and partition. Then load and run "configure". The device in the examples below is #10. Use the devide # assigned to your C64 OS system drive.

With JiffyDOS:

@cd//os/settings/
/configure
run

Without JiffyDOS (example with device #10):

open15,10,15,"cd//os/settings/":close15
load"configure",10
run
Load and Run configure from //os/settings/.

Date and time

The yes or no questions about date and time may be answered according to your personal preference.

Press RETURN to accept the default option and proceed to the next question.

Date and Time configuration.

Mouse input

C64 OS comes with 4 built-in mouse pointer styles, choose whichever style you prefer, or press RETURN to accept the default pointer style.

Following are several mouse accessibility settings. The defaults are reasonable and can be accepted by pushing RETURN, but if you have special requirements you can adjust them using the "+" and "-" keys.

If you use a proportional mouse, like a 1351 or compatible adapter, mouse speed affects the acceleration of the pointer. If you use a joystick, mouse speed affects the maximum speed the pointer can attain.

Mouse pointer styles.

The double-click delay is the time that is allowed to pass between two clicks that still register as a double-click. If you have difficulty double-clicking quickly, this number can be increased.

The inner and outer colors of the pointer can be changed. The defaults are a pleasant black and light grey, but if you have difficulty seeing the pointer, you can adjust the colors to have a higher contrast against typical backgrounds.

The mouse can be configured for left-handed or right-handed use, which swaps the roles of the left and right buttons. Mouse wheel settings only take effect if you are using a MicroMys or MouSTer mouse adapter, with the appropriate driver, and you are using a PS/2 or USB mouse with a wheel. The option reverse the direction of scrolling when the wheel is rolled.

Mouse Input configuration.

For additional information about mouse input configuration, see Chapter 3: Configuration of the C64 OS User's Guide.


Global system settings

The CPU busy indicator is a clock animation that appears in the top left corner of the screen if the CPU is occupied for longer than a few seconds. It indicates that activity is taking place that could cause the user interface to become unresponsive. Press "y" to enable this feature, or press RETURN.

There is then a series of questions about keyboard shortcuts that trigger system-level features. You can press "y" or RETURN to accept the defaults. These options also serve to show you that these features exist and how they can be triggered. You can customize them if the defaults are inconvenient.

Global System Settings.

The status bar has three display modes. You can choose which mode to start up in, according to your preference. If you do not have a preference, press RETURN to select the default.


Expansion memory

C64 OS makes use of expanded memory from a 17xx (or compatible) RAM expansion unit to enable a feature called "fast app switching." (See note, below.)

You can choose how much memory to allocate to fast app switching and how much to reserve for applications to use for other purposes. When an REU is available, C64 OS always reservse the first 64KB bank (bank 0) for operating system workspace; temporary cache memory, screen compositing, etc. After that, C64 OS uses one additional 64KB bank for each fast-switched app and manages the use of that space dynamically.

Model Size Banks Notes
1700 128KB 2 Very small
1764 256KB 4 Small
1750 512KB 8 Medium
1750XL 2MB 32 Large
Ultimate 64 / 1541 Ultimate II+ Up to 16MB 256 Very Large

If you dedicate all available banks to fast app switching, then an Application that can make use of expanded memory operates as though no REU is available. A happy balance would be to dedicate a few banks to fast app switching, and still leave some for use by Applications that can benefit from more memory.

Press RETURN to accept the default of 0 banks for fast app switching, or use the "+" and "-" keys to adjust the number of banks.

Fast app switching: Coming soon.

Fast app switching is currently under development and is scheduled for release in C64 OS v1.05.

Prior to v1.05, you should choose 1 bank for fast app switching. This reserves the zeroth bank of the REU for system workspace, and avoids any possible conflict with an Application that might also try to use the REU. This issue has already been resolved in the beta of v1.05.

Expansion Memory.

The amount of available main memory is displayed at the right end of the status bar. The Utility that is opened when you double-click the available memory is configurable. Press "1" or press RETURN to choose the default option, the Memory Utility. The Memory Utility provides a visual map of how main memory is currently allocated.

C64 OS displays memory quantities in various places. Choose whether you want to see memory represented as 256-byte pages, roughly the same as a disk block, or to see memory in kilobytes. Press RETURN to accept the default and showing memory in kilobytes.

Representation in kilobytes is less accurate than pages, but is more familiar for users of modern computers.


Hardware drivers

Drivers for alternative hardware devices are configured separately from the settings for how the devices behave. The Configure Tool provides options for a realtime clock source for setting the system's date and time, and input device drivers for controlling the mouse pointer.

Additional driver types are under development, such as for printers, networking hardware and game controllers.

Drivers for Realtime Clock.

If you have a storage device that provides a realtime clock (RTC) choose the IEC RTC driver. You are given an additional choice either to specify the device # or to allow the driver to auto-detect and use the first supported device. The storage device that provides the RTC does not need to be the C64 OS system drive.

If you are using a 1541 Ultimate II+ or an Ultimate 64, you may choose the UCI RTC driver. The Ultimate Command Interface must be enabled in the menu system of the 1541 Ultimate II+ or Ultimate 64, and the device's firmware should be updated to the latest.

If you do not have a device which supplies a realtime clock, press "4" or press RETURN to select none of the above.

For advanced options and additional information about RTC configuration, see Chapter 3: Configuration of the C64 OS User's Guide.

Drivers for Mouse Input.

Next you can select the pointer input driver for the hardware you have. If you have a 1351 or compatible mouse, choose the 1351 mouse driver. This driver is available for control port 1 or 2.

If you are using a MicroMys or MouSTer adapter you should choose the MicroMys/MouSTer driver. Although a MicroMys or MouSTer can be used as a generic 1351, the more advanced driver adds support for the mouse wheel. The MicroMys/MouSTer driver is only available on control port 1.

If you only have a joystick choose the joystick driver, either for control port 1 or 2.


Go-menu places

In File Manager, there are 4 configurable places accessible from the Go menu. The Configure Tool can be used to set these automatically to default, valid places. If you choose to accept this option, 4 additional directories are created in the root directory of this partition:

  • documents
  • games
  • music
  • pictures
Go-menu places.

These places can later be changed from within C64 OS. If you've already configured these places and you re-run this Configure Tool, you can say no to this option and it will leave your places set as you've configured them.


Remember

None of your decisions made here are set in stone. You can run the Configure Tool at any time to make different choices and change essential settings. This may be necessary if your hardware setup changes. For example, if you switch from a mouse to a joystick or other input device.

C64 OS configuration is now complete and you are ready to boot up for the first time.


Step 4. Booting up: Start using C64 OS

You are now ready to boot C64 OS for the first time. Load and run "c64os" from the root directory of the device and partition where C64 OS is installed.

Load and run c64os from the root directory.

You can change to the partition and root directory where C64 OS is installed first and then simply load and run "c64os". However, the C64 OS booter also knows about its installation location; you can load it using a path to specify its partition and the root directory and it will still successfully launch.



Without JiffyDOS (example with device #10, partition #1, changing defaults first):

open15,10,15,"cp1"
print#15,"cd//":close15
load"c64os",10
run

Without JiffyDOS (example with device #10, partition #1, loading with path):

load"1//:c64os",10
run

With JiffyDOS (example with device #10, partition #1, changing defaults first):

@cp1
@cd//
↑c64os

With JiffyDOS (example with device #10 as default, partition #1, loading with path):

↑1//:c64os


You see a progress meter as the booter loads the system files. Next the settings files are loaded in, drives are detected and mapped, and expanded memory is detected and checked for available capacity.

C64 OS booting up. C64 OS booting up.

Once the system files are loaded in, C64 OS automatically opens the App Launcher.* This standard splash screen is displayed while launching an Application, showing its installed path and custom icon.

C64 OS launching the App Launcher.

* If you have booted into C64 OS before, the booter returns you to the Homebase Application you were last in. This could be either App Launcher or File Manager.

When the App Launcher is finished launching, you see a desktop with aliases to Applications and Utilities that you can open by double-clicking.

The C64 OS App Launcher desktop.

Note: The desktop that you see may not look exactly like the example shown below.


Congratulations

C64 OS is up and running on your Commodore 64. You can now explore the user interface and built-in Applications and Utilities.

To get the most out of C64 OS, be sure to checkout the complete online User's Guide.



Made For C64 OS Logo

Look for this logo to know when a software package or hardware device is designed to be used with C64 OS.

For more information about the use of this logo, see: C64 OS Media Resources, Made for C64 OS.

Table of Contents



This document is subject to revision updates.

Last modified: Sep 10, 2023