C64 OS USER'S GUIDE
Chapter 2: Installation
This chapter discusses the minimum and recommended hardware requirements to run C64 OS. In addition to original hardware, C64 OS can be installed on a Mac or PC running VICE.
The installation instructions vary slightly depending on the hardware you have. This guide does not teach you how to use the features of the drives but it does make recommendations that make installing C64 OS easier.
What you need to run C64 OS
A common base configuration for a Commodore 64—such as for a game or a demo competition—is the C64 itself plus a 1541 disk drive and typically a joystick. C64 OS's base requirements are very close to this, with the exception of storage.
Minimum hardware requirements
C64 OS is designed around many small modular parts. The operating system consists of over 1000 files organized into a sensible hierarchy of over 50 nested subdirectories. The 1541, 1571 and 1581 are low-capacity, legacy storage devices that do not support subdirectories. So, while C64 OS can make use of these for data storage, and can help you manage the data on your disks, a mass storage device with support for native CMD-style subdirectories is required for the system drive.
A wide variety of SD2IEC devices are commercially available today. Check out the storage section of the Commodore 8-Bit Buyer's Guide for an overview of what drives are available for purchase. IDE64 has only just become unavailable due to world-wide components shortage, hopefully this will be temporary. Both of these device families are fully supported and can be used as the C64 OS system drive.
Although the original CMD HD and RAMLink are no longer commercially available, they are fully supported. The Rear Admiral ThunderDrive, a clone of the CMD HD, is also supported. A CMD FD 2000 or 4000 is technically supported, but all of the system files and installed Applications and Utilities must be contained on a single disk. It is possible to run C64 OS from a CMD FD, but this is only practical if the system directory is stripped down to contain a reduced set of required drivers, libraries, Applications and Utilities. This guide does not cover the procedure for installation on a CMD FD.
- Commodore 64 computer
- Joystick
- SD2IEC drive* **
* 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
C64 OS extends the C64 KERNAL ROM to maintain maximum compatibility with all standard storage devices. It does not implement its own speedloader. JiffyDOS is fully compatible with C64 OS and is highly recommended because the IEC routines in the stock C64 are notoriously slow. JiffyDOS strikes a balance between performance and compatibility that makes it ideal for use in an operating system.
JiffyDOS is also commercially available, and we want C64 OS to help drive a healthy commercial ecosystem for Commodore 64 compatible hardware.
The CMD RAMLink provides the C64 with a JiffyDOS KERNAL. The CMD HD and SD2IEC both implement support for the JiffyDOS protocol and benefit from its use. If you are using an IDE64 you won't need JiffyDOS. The IDE64 provides its own speedloader and is very fast on its own.
C64 OS uses a mouse and menus based interface. Although it is possible to use a joystick, the joystick is a digital input device. A 1351 or compatible mouse is an analog and proportional input device. The experience of using a proportional input device is far superior to using a digital input device, and is therefore highly recommended.
Although the 1351 mouse itself is no longer commercially available, the MicroMys and MouSTer adapters are commercially available for PS/2 and USB mice that are 1351 compatible. Check out the input section of the Commodore 8-Bit Buyer's Guide for an overview of mouse adapters available for purchase.
- 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)
* 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
Make a backup
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 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.
About .P00 and .S00 file wrappers
There are two copies of C64 OS on the System Card. One copy is contained within the .CAR file in the root directory. The other copy is already installed and ready to be run from an SD2IEC.
What is a CAR file?
CAR stands for "C64 Archive." It is a new archive format used by C64 OS that is similar to TAR used on Linux and Unix, but which encodes C64-specific file system features. Its main advantage over other C64 archiving formats is that it supports recursively archiving directory trees. This makes it an ideal format for the C64 OS installation archive, since C64 OS consists of an organized directory system.
The tool, carsearch, in the //os/c64tools/ directory can be used to view the contents of a .CAR file from the READY prompt. The carsearch tool is useful but only works on an SD2IEC, because it depends on SD2IEC's file seek feature. See Appendix I: C64 Tools → Car Search.
The copy already installed on the System Card consists of the booter file "c64os" in the root directory, and the contents of the "os" subdirectory. The files in the "os" subdirectory are in .P00/.S00 format. This is a wrapper format that allows files stored on a PC file system to retain C64-specific file system features such as PETSCII filenames and CBM file types.
When viewed on a C64 with an SD2IEC, .P00 and .S00 files are automatically and transparently unwrapped. However, they cannot be directly transferred from a PC or Mac to an IDE64 or CMD device because the transfer process will not unwrap them, and IDE64 and CMD devices do not natively unwrap .P00 and .S00 files. The .CAR file is used to make it easy to transfer the whole system to an IDE64 or CMD device, where it is then unarchived during the installation process. The .P00 and .S00 wrappers are not used on the files within the CAR file, because CAR already encodes the the C64-specific file system features.
How to install C64 OS
C64 OS can be installed on three main families of device: SD2IEC, IDE64 or a CMD HD or RAMLink. C64 OS can also be installed on VICE. There are separate instructions for installing C64 OS on TheC64, which also runs a version of VICE. Follow the instructions for the device family you are installing to.
- Set up on SD2IEC
- Installation on SD2IEC
- Installation on IDE64
- Installation on CMD HD or RAMLink
- Installation on VICE
- Installation on TheC64
- About 1541, 1571, 1581, Pi1541, 1541 Ultimate, Ultimate 64, etc.
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.
This runs the 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.
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".
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 Chapter 3: Configuration and Settings.
Understanding SD2IEC Blocks Free Calculation
The C64 OS System Card has been divided into two partitions, each formatted with the FAT16 or FAT32 file system. The cluster size on the System Card is 512 bytes. This is two times the 256-byte block size that is standard on Commodore disk drives and CMD storage devices.
SD2IEC reports blocks free as the number of available 512-byte clusters. But the block size of a file in the directory listing is in Commodore standard 256-byte blocks. This can lead to some confusion. It is important to be aware that these two numbers are not in the same units.
Installation on SD2IEC
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.
You only need to perform a fresh install on SD2IEC if you want to use the install tools and installation archive to create a new C64 OS system directory, either on a different SD Card, or because the original system directory was damaged. For example, if you accidentally scratched important system files, all is not lost; you can perform a fresh installation to get back to a working system directory.
If you are just setting up C64 OS for the first time on the original System Card, you do not need to perform an installation, see the section above instead, Set up on SD2IEC.
C64 OS must be installed in the root directory of the SD Card. (SD Cards can be partitioned, and the System Card comes with two partitions. C64 OS can be installed in any partition, but partition 1 is most convenient.) If you are installing on a different SD Card, transfer the four files from the root directory of the System Card to the root directory of the new SD Card 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 | CRC32 |
|---|---|---|---|
| c64os | C64 OS booter. | Transfer to root directory of SD2IEC partition. | 54fadd28 |
| c64os setup | Installation setup program. | Transfer to root directory of SD2IEC partition. | 68055da2 |
| restore.car | Installation archive file. | Transfer to root directory of SD2IEC partition. | 2ce8f514 |
| c64restore | Installer program. | Transfer to root directory of SD2IEC partition. | 46bd47ea |
Note about Filename Compatibility
The SD2IEC device family supports different modes for filename compatiblity with the C64 and with other computers like PC or Mac. C64 OS requires the SD2IEC to be in the mode that is maximally compatible with the C64 during a fresh installation. Later versions (v1.04+) of the c64restore tool perform this setting change for you. But on any earlier version, you need to ensure this mode is set before beginning the installation.
Set SD2IEC to Extension Mode 2 (Maximum C64 Compatibility)
The following commands assume your SD2IEC is on device 8. Change the 8 in the command to the device number of your SD2IEC.
With JiffyDOS: @"xe2" Without JiffyDOS: open15,8,15:print#15,"xe2":close15
For more information about configuring SD2IEC settings, See: SD2IEC User's Manual → Settings
Load and run "c64os setup" from the SD2IEC drive. It does not have to be device #8.
This runs the 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.
Press "f" to begin a 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 Chapter 3: Configuration and Settings.
For additional installation options see: Advanced fresh installation.
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 are setting up a virtual IDE64 in VICE, be sure to review the Installation on VICE instructions first.
If you do not have an SD2IEC, you can transfer the files from a Mac or PC to IDE64 via PCLink. For further information about how to best set up your IDE64, configure and use PCLink, see the Advanced set up for IDE64 section of this User's Guide. Or consult the IDE64 User's Guide for further information about configuring the IDE64 and 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 | CRC32 |
|---|---|---|---|
| c64os | C64 OS booter. | Transfer to root directory of IDE64 partition. | 54fadd28 |
| c64os setup | Installation setup program. | Transfer to root directory of IDE64 partition. | 68055da2 |
| restore.car | Installation archive file. | Transfer to root directory of IDE64 partition. | 2ce8f514 |
| c64restore | Installer program. | Transfer to root directory of IDE64 partition. | 46bd47ea |
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.
This runs the 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.
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 Chapter 3: Configuration and Settings.
For additional installation options see: Advanced fresh installation.
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 are setting up a virtual CMD HD in VICE, be sure to review the Installation on VICE instructions first.
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 | CRC32 |
|---|---|---|---|
| c64os | C64 OS booter. | Transfer to root directory of CMD native partition. | 54fadd28 |
| c64os setup | Installation setup program. | Transfer to root directory of CMD native partition. | 68055da2 |
| restore.car | Installation archive file. | Transfer to root directory of CMD native partition. | 2ce8f514 |
| c64restore | Installer program. | Transfer to root directory of CMD native partition. | 46bd47ea |
Load and run "c64os setup" from the CMD device. It does not have to be device #8.
This runs the 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.
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 Chapter 3: Configuration and Settings.
For additional installation options see: Advanced fresh installation.
Installation on VICE
C64 OS is able to run on almost a stock C64, but requires a storage device with support for native subdirectories. VICE has had support for the IDE64 for a while, and VICE version 3.5 added support for the CMD HD.
C64 OS ships as two bundles. The Starter Bundle (16 MB or 32 MB System Card) contains the installation archive and tools that can be used to install C64 OS on a real CMD HD or IDE64, or to a virtual CMD HD or IDE64 that has been created, configured and partitioned under VICE. The Standard Bundle (64 MB System Card) also includes two pre-configured hard drive images, partitioned and pre-installed with C64 OS. One image is for a virtual CMD HD, the other for a virtual IDE64.
Configure MicroMys or 1351 mouse
Before proceeding with any other VICE configuration, C64 OS requires an input device for the mouse pointer. VICE has support for emulating both the 1351 mouse and the MicroMys mouse adapter. Either will work, however, MicroMys is recommended because it is backwards compatible with the 1351 and adds extensions for the mouse's scroll wheel which can be used by C64 OS.
In VICE, choose "Settings..." from the Preferences menu. From the left sidebar, unfold the Input devices section. Select the Control port option under the Input devices section heading. In the main configuration area on the right there are select boxes to specify which devices are connected to Control Ports 1 and 2.
From the select box for Control Port 1, choose "Mouse (Micromys)". If for some reason this option is not available, choose "Mouse (1351)" instead. From the select box for Control Port 2, you can choose either "None" or "Joystick".
Configure Control Port 1 for MicroMys or 1351 mouse
Close the settings window by clicking the close button in the bottom right corner. Then save VICE's settings by choosing "Save settings" from the Preferences menu.
Change mouse control from host OS to VICE
In order for the mouse on the host operating system to control the mouse pointer in VICE it is necessary for VICE to grab the mouse. When you want your mouse to control VICE, choose "Mouse grab" from the Preferences menu, or press ALT+M on Windows or CMD+M on macOS.
Once VICE has grabbed the mouse, you can no longer use the mouse to deselect the option from the Preferences menu. Press ALT+M on Windows, or CMD+M on macOS, again, to deselect the mouse grab option and return mouse control to the host operating system.
Simplified VICE set up
The simplified instructions show you how to perform basic configuration of VICE, to enable the drives with ROMs and how to attach the pre-configured hard drive image.
Set up VICE with CMD HD image
Set up VICE with IDE64 image
Advanced VICE set up
The advanced instructions are only for the courageous and the adventuresome. These show how to create a new CMD HD hard drive image from scratch, how to install the CMD HD DOS on that image and partition it. Alternatively, they show how to create an IDE64 hard drive image from scratch, how to create and attach the IDE64 cartridge image, and how to partition the IDE64 hard drive image.
The advanced instructions end with how to transfer the installation files from the host file system to the newly minted virtual CMD HD or IDE64. From that point on, installation proceeds in the identical manner to the instructions given above for CMD HD or IDE64.
Set up VICE for CMD HD from scratch
Set up VICE for IDE64 from scratch
Installation on TheC64
TheC64 (mini and Maxi) runs a custom version of VICE. It is possible to put an IDE64 hard drive image, with C64 OS already installed, on USB storage media. Along with a .CRT image of the IDEDOS and a specially crafted update script. With the USB media plugged in, TheC64 can be booted to the READY prompt, where C64 OS can then be booted from the virtual IDE64.
The IDE64 hard drive image can either be the pre-configured image which ships on the System Card as part of the C64 OS Standard Bundle, or it can be created from scratch by following the instructions above, under Advanced VICE set up, for IDE64.
Set up VICE on TheC64 for IDE64
About 1541, 1571, 1581, Pi1541, 1541 Ultimate, Ultimate 64, etc.
C64 OS is able to run on almost a stock C64, but requires a storage device with support for native subdirectories. Please see minimum hardware requirements.
C64 OS cannot be installed on a 1541, 1571 or 1581 disk for two major reasons; they are much too small, and they don't support CMD-style native subdirectories. A base installation of C64 OS is around 2MB, and consists of over 1000 files organized in more than 50 subdirectories.
A trimmed down version of C64 OS could be installed on an FD-2000 disk, but only by judiciously excluding drivers, libraries, Applications and Utilities that come in the base installation but that are not strictly necessary.
A Pi1541, 1541 Ultimate, Ultimate 64's built-in drives, and other similar solutions are modern replacements for legacy floppy disk drives. Although C64 OS can access and make use of these drives, the C64 OS system directory itself cannot be installed and run from any of these storage devices.
About the installation location
Everything in C64 OS is organized in a sensible directory tree, all contained in a single system directory. The system directory is named "os", by default, and must reside in the root directory of its partition. Additionally, the booter program named "c64os" must also remain in the root directory.
Documentation References to the System Directory
Although the name of the system directory can be changed, be aware that path examples found throughout the C64 OS User's Guide and Programmer's Guide refer to the system directory's default name. Like this:
//os/settings/ //os/desktop/2/
For more information about the system directory, see Chapter 8: File System → System Directory
During installation and set up three other files must be in the root directory; the installation archive (restore.car), the installer program (c64restore) and the installation setup program (c64os setup). After installation is complete, clean copies of "c64os", "c64restore" and "c64os setup" can be found in the c64tools directory in the system directory (//os/c64tools/).
If you have made a backup—as was recommended earlier in this chapter—then after installation and set up is complete you can scratch (delete) these three files from the root directory.
| Filename | Purpose | Notes |
|---|---|---|
| restore.car | Installation archive file. | May be scratched, if backed up. |
| c64restore | Installer program. | Can be scratched. A backup is found in //os/c64tools/ |
| c64os setup | Installation setup program. | Can be scratched. A backup is found in //os/c64tools/ |
The booter knows where C64 OS is installed
The booter ("c64os") is a self-modifying BASIC program. In its initial or clean state it assumes that C64 OS has not yet been installed, so it automatically loads and runs the C64 OS Setup Tool. The Setup Tool auto-detects the device # from which it was loaded, and auto-detects the current partition # from which device it was loaded. The default system directory is filled in as "os" because that is what the installer creates.
After accepting the auto-detected defaults, the device #, partion # and system directory name are embedded into the booter program itself. By design, the booter's ability to successfully boot C64 OS is very robust. For example, regardless of the current partition and directory, the booter can be loaded like this: (where the partition # and device # are specified appropriately for your installation location.)
Without JiffyDOS:
load"1//:c64os",12
With JiffyDOS:
↑1//:c64os
After the booter is in memory, it is possible to change to another path, partition or device number, and even to list a directory (using JiffyDOS's @$, for example) before running the booter. And yet, the booter will still successfully boot C64 OS. This robustness is intentional, and it is possible because the booter has explicit knowledge of where C64 OS is installed.
How to change the installation location
There are several ways that the installation location of C64 OS could change:
- The system device # is changed
- The system directory name is changed
- The system directory is moved or copied to a different partition
If any of these are changed, it is necessary to load and run the C64 OS Setup Tool, and specify the new device #, partition #, and system directory name. The Setup Tool updates the booter with the new information. If you've already scratched the original Setup Tool, it is not necessary to copy it to the root directory, it can be loaded and run from the c64tools directory.
To do this, change to the partition where C64 OS is installed, then load and run the Setup Tool, like this: (specifying the correct device #, partition # and path for your installation location.)
Without JiffyDOS:
open15,8,15,"cp1":close15 load"//os/c64tools/:c64os setup",8 run
With JiffyDOS:
@cp1 ↑//os/c64tools/:c64os setup
If you want to change the installation location, change the actual installation location first, then at the end use the Setup Tool to specify the new location details. For example, perhaps you would like the system directory name to include its version number. From the READY prompt, first rename the system directory from "os" to "os1.2", then load and run the Setup Tool. Like this:
Without JiffyDOS:
open15,8,15 print#15,"cp1" print#15,"cd//" print#15,"r:os1.2=os" close15 load"//os1.2/c64tools/:c64os setup",8 run
With JiffyDOS:
@cp1 @cd// @r:os1.2=os ↑//os1.2/c64tools/:c64os setup
When the Setup Tool asks you for the system directory name, type in "os1.2". The Setup Tool takes the details you specify, confirms that an instance of C64 OS is installed there, then updates the booter.
Information for Programmers
Although you can rename the C64 OS system directory and it will run correctly with an alternative name, if you plan to do C64 OS programming—on your C64—the installation against which you assemble and run your code should use the default name "os".
This is because some programming headers and macros are required to specify the full path, and for this reason are hardcoded to use the default system directory name. Further information about C64 OS software development can be found in the C64 OS Programmer's Guide.
For more advanced installations, such as how to install multiple copies of C64 OS for different versions or configurations, see Chapter 8: File System → Multiple Installations
Advanced fresh installation
The instructions for a fresh installation given above, either to SD2IEC, IDE64, CMD HD or RAMLink, are simplified to minimize confusion and make the process as straightforward as possible.
The C64 OS install tool, c64restore, beginning in version 1.04, has the ability to open and extract the restore.car install archive from a device that is different than the target device on which C64 OS is being installed.
This can be taken advantage of in a number of contexts to eliminate the step of first copying the, rather large, restore.car file to the installation device. The following table shows some examples of how this can be used.
| Target Device | Source Device | Notes |
|---|---|---|
| CMD HD | SD2IEC | Installing to CMD HD from System Card in SD2IEC. |
| RAMLink | SD2IEC | Installing to RAMLink from System Card in SD2IEC. |
| IDE64 | SD2IEC | Installing to IDE64 from System Card in SD2IEC. |
| IDE64 | IDE64-PCLink | Installing to IDE64 over PCLink from a Mac or PC. |
| CMD HD | VICE FS * | Installing to virtual CMD HD from host file system in VICE. |
| FD-2000 | SD2IEC | Installing to an FD-2000 disk from System Card in SD2IEC. |
| FD-2000 | CMD HD | Installing to a small FD-2000 disk from a CMD HD. |
Example, to IDE64 from IDE64-PCLink
Start by copying the three small installation files:
- c64os
- c64os setup
- c64restore
using the filecopy tool or the IDE64 built-in file manager, from the PCLink device to the primary IDE64 device. This is fast because each of these files is less than 20 blocks. Do not copy restore.car to the IDE64's primary device, but leave it accessible in the current directory of the PCLink device.
In this example, IDE64 has been configured such that the primary device is 12 and PCLink is device 14. Load and run "c64os setup" from the primary device.
load"c64os setup",12 run
Press "Y" to acknowledge that you have read and agree to the software license agreement.
From the main options, press "F" to begin a fresh installation. Next it asks for the Source Device #. This value defaults to the current device #, the device from which the Setup Tool was loaded and run. Press the plus and minus keys (+/-) to change the source device to 14 (the PCLink device in this example,) and press RETURN.
Next it asks for the Target Device #. This also defaults to the device from which the Setup Tool was loaded, but in this case that is the correct target device. Press RETURN to accept the default of 12 (the primary IDE64 device in this example.)
Press RETURN again to accept the auto-detected current partition as the Target Partition #.
Fresh installation from IDE64-PCLink in VICE.
The fresh installation proceeds as normal, except that the restore.car install archive file is opened and read directly from the PCLink device, and the files extracted from it are written to the primary IDE64 device.
Existing system directory moved aside
During any fresh installation, if the install tools find that there is already an item (a directory or a file) named "os" in the root directory, it automatically renames that item to "os.bak". It does this in order to move it aside and make room for the new system directory that is about to be created.
Advanced installation in summary
Using the options provided by the C64 OS Setup Tool, it was not necessary to copy the restore.car file from PCLink to the primary IDE64 device first. This saves a step and saves the time it takes to copy the file.
It also saves storage space on the target device. C64 OS can be installed in a native-mode partition on an FD-2000 or FD-4000 disk. By keeping the restore.car file on another storage device, such as an SD2IEC, CMD HD, RAMLink or IDE64, the maximum storage space is left available on the floppy disk into which the c64restore tool can extract the C64 OS system directory.
Additional combinations of devices and partitions that can be used with these advanced options are left as an exercise for the adventuresome user.
Next Chapter: Configuration and Settings
Table of Contents
This document is subject to revision updates.
Last modified: Jan 17, 2024