Official Software Updates
C64 OS is under active and on-going development.
Get the latest software updates here.
System updates have never been easier.
Find below the appropriate update for your current version and download the CAR (C64 Archiver)
file. Copy the file to a device accessible to C64 OS and double-click it in File Manager.
The Installer Utility opens automatically. Click the install button to begin. When it's done,
reboot C64 OS.
Install Updates in the Correct Order
Software updates must be installed in the correct order! There is no check to make
sure that what you're installing is appropriate for updating your current version.
- Check your current version number. (Utilities Menu → Settings → About)
- Install the appropriate update for that version first.
- Reboot. (Options Menu → Quit to BASIC → Load and run C64 OS again.)
- Repeat from step 1, if there are additional updates to be installed.
RECOMMENDED: Make a backup of your system directory in case something
goes wrong, like an unexpected power outage in the middle of updating an important file.
No better way to transport C64 files than in a CAR.
C64 Archiver is an Application for C64 OS that creates archive files that contain C64 files,
including all CBM FS metadata and also retains their structure in nested subdirectories.
The archive files produced are called CAR files.
CAR files are the standard way of distributing C64 OS software, but can also be used to
distribute regular C64 software and other resource files too. Read the
C64 Archiver and Installer guide to learn more about how
to use these tools and a more detailed description of
how to install system updates.
Software Licensing
C64 OS System Updates, regardless of how they are acquired, whether directly from OpCoders Inc.
on a physical SD Card, downloaded from c64os.com, or from any other source,
are licensed under the same end-user license agreement that governs a commercial copy of C64 OS.
https://www.c64os.com/legal/software-license-agreement/
By downloading C64 OS system updates, you are agreeing to be bound by the software license
agreement. C64 OS system updates may not be distributed in any way without the prior written
consent of OpCoders Inc.
C64 OS System Updates
System updates will be added here as they become available.
This release introduces a new universal Commodore 64 graphics file format called, Commodore
Grafix, or CGFX. It is a RIFF/CGFX container with support for different native and non-native
video modes, metadata, format and frame size information. Additionally it supports multiple
frames for panoramas, matrices for 3D models and look-around scenes, and short animations up
to 256 frames.
Image Viewer receives a major update with support for CGFX. All image datatype loaders have
been refactored. New image datatype savers allow you to save any HiRes or MultiColor frame
as a custom boot screen. Screen captures now save with their custom character set, and can
be viewed with Image Viewer.
The sidplay library gains new support for metadata, and a new Utility, SID Preview, can
be used to listen to PSID music files. The sid search webservice at
services.c64os.com has been rebuilt
offering a searchable database of over 34,000 SIDs from HVSC that have been relocated for
compatibility with C64 OS.
Many bugs have been fixed. New drivers for TurboChameleon64 and MMC64. New customizable
boot options, and numerous new system-level features and improvements are found throughout.
WARNING: Mind the required version #
Pay attention to the required version # !!
Check your current version number to know which update to install first.
| Filename |
Release Date |
Required Version # |
Version # |
File Size |
CRC32 checksum |
| 1.04.upd1.0p.car |
2023-06-08 |
1.0p or 1.02 |
1.04 |
291 KB, 1148 blocks |
7913abc8 |
| 1.04.upd1.03.car |
2023-06-08 |
1.03 |
1.04 |
205 KB, 806 blocks |
5c1fe535 |
|
Only one of the update files listed above is required. Choose the one that corresponds with
the version of C64 OS which you are updating from.
New Features
- Commodore Grafix file format. A RIFF/CGFX container format for C64 graphics in multiple modes and formats.
- Image datatype loader for Commodore Grafix files, with .cgx extension.
- Image datatype loader for PETSCII Bots, with .pbot extension.
- Image datatype loader for matrix images in 3D Koala format, with .3dk extension.
- Image datatype savers for Koala (MultiColor) and Art Studio (HiRes) formats.
- RTC driver for TurboChameleon64 and MMC64.
- Boot components, boot.koala.o and boot.art.o for displaying custom bitmap bootscreens.
- Screen grabs are now saved in PETSCII graphics format v2, which includes the custom character set.
- Limited support for VICE FS as a legacy device (single directory only.)
- Gallery
- Menu options for split and fullscreen graphics modes.
- Double click center of graphics screen to toggle between split and fullscreen graphics modes.
- Click top row in fullscreen graphics mode to leave fullscreen graphics mode.
- Image Viewer
- Menu option to save current MultiColor or HiRes bitmap frame as a custom bitmap boot screen.
- Menu options for split and fullscreen graphics modes.
- Double click center of graphics screen to toggle between split and fullscreen graphics modes.
- Click top row in fullscreen graphics mode to leave fullscreen graphics mode.
- Utilities
- SID Preview Utility, for playing PSID music (relocated for C64 OS compatibility.)
- In About C64 OS, click the version number to toggle to the build number.
- File Info Utility enables support for file locking on SD2IEC (requires the latest MarkusC64 firmware.)
- Move and Copy Utilities now have an option to overwrite existing files.
- COMMODORE+C keyboard command in Open Utility copies selected file/place to the clipboard.
- C64 Tools
- Included 3 machine language monitors.
- Suite of install tools (c64os, c64os setup, and c64restore) have been updated to allow restore.car stored on one device to be installed to a different device.
- C64 OS booter (//os/c64tools/:c64os) now offers to open Configure Tool after completing setup.
- Configure Tool (//os/settings/:configure) updated to let you choose TurboChameleon64 RTC driver.
- Configure Tool now has Ultimate Command Interface detection, with an not-detected warning, if 1541UII+/Ultimate64 RTC driver is selected.
- Petsciiview is now much faster and includes support for new v2 PETSCII graphics format.
- New Tool, BSOD64 ("Blue Screen of Death" 64) by KrocCamen. Can used as a boot component to assist developers.
- New Tool, filecopy. Single file 2-drive file copier. Copies a PRG or SEQ file between any two devices, including from VICE FS.
- FileCrop Tool can be used to cut arbitrary segments out of any file up to 64KB.
- LoadTo Tool can be used to put any file of any type at any arbitrary address in memory.
- CGFX Creator Tool can be used to create new Commodore Grafix files.
- BigBotView Tool can be used to view big (12x16) PETSCII Bots.
- Backup v3.1 now includes JiffyDOS detection, and exits cleanly if JiffyDOS is not detected.
- Added sample code to "s" startup script to configure an SD2IEC's date/time from another IEC device.
Changes and Improvements
- components.t and modules.t files may now have blank lines; first character of line must be $0d.
- components.t and modules.t files may now have comment lines; first character of line may be either "#" or ";".
- A single commented line may only be up to 32 characters long.
- SD2IEC boot component sets the date/time of all SD2IEC devices from the first detected CMD HD, CMD FD, RAMLink or IDE64.
- SD2IEC boot component temporarily changes configuration of all SD2IEC devices to improve compatibility with C64 OS.
- Limited the number of fast app-switching REU banks to 32.
- Bank 0 of REU, if present, is now reserved automatically as operating system workspace.
- Added a set of 5 media control icons.
- Added 3 new pointer sprites, 4-directional arrow, up/down arrow, left/right arrow.
- KERNAL call formerly called strcpy has been renamed memncpy.
- New custom boot modes. Hold Commodore+1, 2, 3, or 4 to select an alternative boot mode.
- Each mode loads from a custom componentsX.t file.
- Safe Mode (minimal number of core components, REU disabled, manual RTC driver selected.)
- Custom Mode 1
- Custom Mode 2
- Developer Mode
- New boot components for loading custom workspace memory images.
- The sidplay.lib gains support for reading chip and system metadata.
- Pressing STOP key while keyboard focus is in a TKInput field removes focus from that field.
- The gfx.lib gains support for all VIC-II character modes in split and fullscreen.
- The fcopy.lib gains support for overwrite.
- New fname.lib for common filename-related tasks.
- New memory.lib adds realloc routine.
- New subdirectory of programming headers //os/s/t/ for datatype header files.
- Includes definitions for PETSCII graphics v2, Commodore Grafix, and PSID.
- Time Utility issues low memory warnings in an effort to free memory for its SID alarm tune.
- New programming headers for TurboChameleon64 and MMC64.
- New Message Command defined for requesting REU bank/page allocation.
- In File Manager, Go → Parent and Go → Root menu options disabled on legacy devices.
Bug Fixes
- c64restore tool now detects SD2IEC and temporarily puts it in XE2 mode for correct filename compatibility.
- Fixed a problem sidplay.lib had converting PSID metadata from ASCII to PETSCII.
- Fixed a problem that sometimes caused a lock up when using COMMODORE+F or COMMODORE+L during boot to force it to File Manager or App Launcher respectively.
- Booter no longer locks up if the STOP key is pressed. STOP can now be used to cleanly exit the C64 OS boot process and return to the READY prompt.
- Pressing STOP no longer interferes with loading a library, but could still interfere with other kinds of loads.
- Fixed a bug in which fopen would not return an error code under some circumstances.
- Fixed a bug in the Move Utility that might delete the original even after it failed to be copied.
- Fixed a problem in which the Scratch Utility to scratch a directory containing hidden files.
- Fixed a problem in which Opener would not extract the File Type and Extension correctly on first file on IDE64.
- Fixed a bug in Copy and Move Utilities that was preventing the animated file from appearing if only copying/moving 1 file
- Backup Tool changes to standard colors now, so its options appear correctly.
- Fixed restoring IDE64 BASIC vectors if used with the JiffyDOS KERNAL ROM.
- Fixed a bug that set the wrong file type when copying a file to an IDE64.
- Fixed a bug in which the status bar showed the wrong filename after Copying multiple files.
- Fixed a bug in which the status bar and the Copy and Move Utilities were out of sync by one file.
- Improved the reliability of recursive Copy and Move between two places on a CMD HD.
- Fixed a bug preventing Copy or Move from working between two places on an IDE64.
- Fixed a bug in C64 Archiver when creating an archive without an REU.
Known Issues
- The Copy button in the File Info Utility is not working on IDE64.
Show Less...
|
Booter and Install Tools
The booter and install tools (c64os, c64os setup, and c64restore) typically reside outside
the system directory, in the root directory of the system partition. Updated versions of these
have been installed in //os/c64tools/. Although not strictly necessary, after updating to
v1.04, it is recommended to copy "//os/c64tools/:c64os" and "//os/c64tools/:c64os setup" to
the root directory, overwriting the older versions there.
The new copy of the booter is a clean copy that's not setup. The first time you boot with
the new version it'll ask you to confirm you've read the EULA, and will ask you how you
want to setup:
- s) System Card first run (default)
- f) Fresh installation
- c) Change installed location
Choose either System Card first run, or Change installed
location. After confirming the installed location of C64 OS, the new setup gives
the option of running the Configure Tool. It's not a bad idea to run through this at least
once to update your core settings, pick available drivers, configure mouse settings, etc.
After going through the setup, you do not need to retain a copy of "c64os setup" or
"c64restore" in the root directory, as fresh copies of those are found in //os/c64tools/.
This release includes some new core features. Mainly, the ability to mount Disk Images in
File Manager, and mouse wheel support with new MicroMys mouse driver.
| Filename |
Release Date |
Required Version # |
Version # |
File Size |
CRC32 checksum |
| 1.03.update.car |
2023-01-16 |
1.02 |
1.03 |
90 KB, 356 blocks |
3349e5ca |
|
This release includes some new core features. Mainly, the ability to mount Disk Images in
File Manager, and mouse wheel support with new MicroMys mouse driver.
New Features
- New Checksum Utility (CRC8, CRC16, CRC32 on selected file.)
- New crc32 tool (//os/c64tools/:crc32 computes true CRC32.)
- New MicroMys mouse driver (port 1.)
- Mouse wheel support in all Toolkit scroll views.
- New Mount Utility (mounts disk images to SD2IEC non-boot partitions.)
- 13 new sample desktop backdrops.
Changes and Improvements
- C64 OS boot screen now dynamically shows version number (//os/settings/:version.t).
- New checksum library (checksum.lib, backends Checksum Utility)
- New defined datatype text/hexdec.
- Window shade can now be toggled with right click on Utility title bar.
- Mouse Utility now includes settings for mouse wheel direction and sensitivity.
- TextView Utility now shows PETSCII/ASCII radio buttons, instead of ASCII checkbox.
- Added an unmount menu option to File Manager's options menu.
- Configure Tool (//os/settings/:configure) updated to let you choose MicroMys mouse driver.
- New assigns for .d64, .d41, .d71, .d81 and .dnp to Mount Utility
- cksum tool (//os/c64tools/:cksum) internal messages changed from "crc32" to "cksum".
- Updated TKFileMeta class (used by Clipboard Utility) to recognize text/hexdec data type.
- Updated //os/docs/:memory.t with new mouse wheel workspace memory values.
- SD2IEC component now puts all SD2IEC devices (temporarily) in PRG disk image mode (XI0).
Bug Fixes
- Fixed a bug in Places Utility that prevented it from noticing some changes.
- Fixed a bug in KERNAL booter that could lead to a lockup if settings files are malformed.
- Fixed a bug in dir.lib that retained transparent bytes ($A0) from disk headers.
- Fixed a bug in backup tool (//os/c64tools/:backup) that could lead to a lockup.
Known Issues
- Copying certain files between devices using an REU can sometimes lead to a lockup.
- Pressing STOP/RESTORE but lingering with STOP held down interferes with an
Application's ability to save its state and close gracefully. May corrupt the
Application's config.i file. Solutions are being explored.
Show Less...
cksum number: 2630579159 See: C64 Archiver and Installer → Versions and Upgrades.
|
This release is very small, it only updates the Installer Utility. It fixes a critical bug
that prevented Installer from reliably extracting files with filenames longer than 14 characters.
| Filename |
Release Date |
Required Version # |
Version # |
File Size |
CRC32 checksum |
| 1.02.update.car |
2023-01-16 |
1.01 |
1.02 |
4 KB, 14 blocks |
42022f62 |
|
This release is very small, it only updates the Installer Utility. It fixes a critical bug
that prevented Installer from reliably extracting files with filenames longer than 14
characters.
Bug Fixes
- Fixes an issue that prevented Installer Utility from updating files with names longer than 14 characters.
- Fixes an issue copying the note from a CAR file from the Installer Utililty to the clipboard.
cksum number: 1791257261 See: C64 Archiver and Installer → Versions and Upgrades.
|
This release mainly fixes bugs, but also includes a couple new things such as the 1351 port 2
driver and an improved version of the PRG Alias Creator tool.
IDE64 compatibility WARNING
If your current version is 1.0p (the 1.0 patched for IDE64 compatibility) DO NOT install
this update, or it will break the 1.0 patch.
| Filename |
Release Date |
Required Version # |
Version # |
File Size |
CRC32 checksum |
| 1.01.update.car |
2022-11-20 |
1.0 (not 1.0p) |
1.01 |
53 KB, 209 blocks |
70a2acfc |
New Features
- bootsect.128 in //os/c64tools/ allows C128 mode to autoboot C64 OS.
- Added 4 new desktop backdrops: home, door, joystick inv, and settings.
- Added the default desktop 5 backdrop to the backdrops directory.
- Added 1351 mouse driver for port 2.
Changes and Improvements
- Quit to BASIC now returns you to the root directory.
- Quit to BASIC now restores IDE64 functionality.
- File Info now updates a subdirectory's header when it's renamed.
- Added new "System Card first run (default)" option to Setup Tool (//os/c64tools/:c64os setup)
- Added option to booter (//os/c64tools/:c64os) to run Configure Tool after System Card first run set up.
- Added option for 1351 mouse in port 2 to drivers in Configure Tool.
- Improved clarity and usability of PRG Alias Creator tool.
- STOP/RESTORE now reloads or returns to Homebase, instead of crashing.
- Improved various programming headers.
- crc32 in c64tools was renamed to cksum in anticipation of new crc32 tool.
Bug Fixes
- Fixes an issue that prevented creating favorites in File Manager.
- Screen Editor (//os/desktop/backdrops/:screenedit) no longer requires JiffyDOS.
- Fixed a bug in strlen and strcpy in the KERNAL.
- Fixed a bug in PRG Runner that prevented it from running regular BASIC programs.
- Fixed a bug that caused a crash by pressing RESTORE key.
Known Issues
- Pressing STOP/RESTORE but lingering with STOP held down interferes with an
Application's ability to save its state and close gracefully. May corrupt the
Application's config.i file. Solutions are being explored.
Show Less...
cksum number: 1531689060 See: C64 Archiver and Installer → Versions and Upgrades.
|
This is a special patch that is only required for some IDE64 users, with certain combinations
of IDE64 hardware and IDEDOS versions.
Who needs this patch?
This patch is only necessary if you have installed v1.0 on an IDE64, but File Manager crashes
upon loading. To solve this problem, follow the instructions below.
| Filename |
Release Date |
Required Version # |
Version # |
File Size |
CRC32 checksum |
| ide64patch |
2023-06-04 |
1.0 |
1.0p |
1.6 KB, 7 blocks |
a06da2fb |
| init.o |
2023-06-04 |
1.0 |
1.0p |
2 KB, 9 blocks |
bffe373a |
Installer |
2023-06-04 |
1.0 |
1.0p |
3.2 KB, 14 blocks |
9980c8ca |
Do I need this patch?
You only need this patch if:
- You have version 1.0 installed on an IDE64, and
- Your installation crashes trying to launch File Manager.
If you are using an IDE64 and the File Manager opens without any issue, you
do not require this patch. You can proceed as normal to download and install
the software updates as usual.
How do I proceed after installing this patch?
If you need this patch, and you install it, your installation will have
been updated to version 1.0p.
Each software update specifies what version it requires. Only the 1.04
update specifies that it can be installed overtop of 1.0p, and so that is
the update that must be installed after this patch.
You will, therefore, go from v1.0 → v1.0p → v1.04.
How do I install this patch?
Download all three of the files listed above: ide64patch, init.o, Installer.
Transfer them to your IDE64. Save them in the root directory of the same
partition where C64 OS v1.0 is installed. (The system directory must be named "os",
which it is by default.)
All three files must be of the file type "PRG".
The filenames must have the correct capitalization.
Switch your C64 to use the lowercase/uppercase character set by holding the SHIFT
key and tapping the COMMODORE key. While in lowercase/uppercase mode, list the
directory where the patch files have been saved. You should see them on the C64's
screen with exactly the following capitalization:
- ide64patch
- init.o
- Installer
I.e., all filename characters must be in lowercase, except for the "I" of Installer.
Load and run "ide64patch".
A brief explanation of this patch is printed to the screen, followed by a reminder
not to install 1.01, 1.02 or 1.03 overtop of 1.0p. It then validates that it is
able to find the system directory, and confirms that the system directory is
currently version 1.0.
It will then proceed to patch File Manager and the Installer Utility. It will
tell you if the patch was successful. If it cannot find either "init.o" or "Installer"
it will tell you that the patch failed. If, for example, somehow the capitalization
of the files is not correct and it can't find one of the files, you can correct the
spelling and run the patch again.
After the patch is successfully completed, the system directory's version number will
be updated to 1.0p. At that point, the ide64patch program will no longer run, because
it notices that the system directory has already been patched.
After the patch has been installed, you are safe to scratch the three files from
the root directory: ide64patch, init.o and Installer.
Show Less...
cksum numbers:
ide64patch: 4048791698
init.o: 4190311738
Installer: 3169850499
See: C64 Archiver and Installer → Versions and Upgrades.
|
Other C64 OS Software Releases
Other C64 OS software releases are added here as they become available.
Resource and Software bundles come in CARs too.
CARs (C64 Archive files) can also be used for transporting other software and resource
bundles, such as collections of media files, like SID music, Commodore Grafix sample packs,
and backgrounds for your App Launcher desktops. Double-click a general CAR from the File
Manager. It opens the Installer Utility, but shows the type as "General." Click the extract
button and a subdirectory full of new stuff is created, right where the CAR file is found.
| Filename |
Release Date |
C64 OS Version # |
Version # |
File Size |
CRC32 checksum |
| cgfxsamples1.car |
2023-05-06 |
1.04+ |
1.0 |
1525 KB, 6149 blocks |
893e1057 |
CGFX Samples, Set #1, Includes
- 6 x Commodore Grafix sample files for use in Image Viewer
- 1 x 3D Koala, Matrix Image
The CGFX files all end with the extension .cgx, the 3D Koala ends with the extension
.3dk. 3D Koala is a more primitive format, whose functionality with greater flexibility
is built into the CGFX format. Nonetheless, C64 OS includes datatype loaders for both
CGFX and 3D Koala.
3D Koala is used for matrix images, of exactly 5 rows by 40 columns, in which every
frame is in the Koala (MultiColor bitmap) format. The image included in this sample
pack is based upon a 3D model of a teapot.
CGFX is a container format which supports variable matrix sizes, in multiple frame formats,
sizes and video modes. CGFX can be used for 3D models, look-around-scenes, panoramas, and
short animations. It can also be used to wrap standard still images in HiRes and MultiColor
bitmap modes, Standard, MultiColor and Extended Background character modes, as well as
providing options for interlacing and other common CPU-assisted non-standard video modes.
This sample pack includes two panoramas, an animation of a continuously rotating planet
Earth, an animation sequence of the USS Enterprise (NCC-1701-D) jumping to warp, a
classic animated meme of Dr. (Bones) McCoy and Captain Kirk, plus a 3D model of
black Porche.
All of these require the Image Viewer Application, datatype loaders and updated gfx.lib
in C64 OS v1.04 or greater.
Show Less...
|
| Filename |
Release Date |
C64 OS Version # |
Version # |
File Size |
CRC32 checksum |
| petsciibots.car |
2023-05-06 |
1.04+ |
1.0 |
231 KB, 931 blocks |
f8897bbc |
PETSCII Bots, Includes
- Over 2400 Small PETSCII Bots, 5x7 characters
- 14 x Big PETSCII Bots, 12x16 characters
- 1 x Original CSDB release README file
All of these PETSCII Bots are drawn by Cal Skuthorpe
(buzz_clik on X/Twitter.) These were released
as SEQ files with a special C64 viewer program on CSDB, April 1, 2023,
https://csdb.dk/release/?id=231072.
C64 OS, starting in v1.04, includes support for graphics in all 3 standard character modes,
in split screen and fullscreen. Also include in C64 OS v1.04 is a PETSCII Bot datatype
loader for viewing these files in the Image Viewer Application.
The files in this collection have been reorganized into 24 subdirectories containing
exactly 100 PETSCII Bots each. Each file has been given the extension .pbot so they can
be assigned a default viewing Application, and so they have a unique datatype that can
be paired to datatype loader. (The originals had the generic extension .c64)
Show Less...
|
| Filename |
Release Date |
C64 OS Version # |
Version # |
File Size |
CRC32 checksum |
| backdrops1.car |
2023-01-09 |
1.0+ |
1.0 |
59 KB, 231 blocks |
acad6174 |
Backdrops Set #1, Includes
- 56 x Backdrop samples for use in App Launcher
- screenedit and savescreen tools
These are the backdrops that were included in the original version 1.0, and the additional
backdrops included in update 1.01 and 1.03. Providing these as a separate downloadable
bundle allows you to delete the ones you don't care about from your System Card, because
you can download them again later.
Also included are the screenedit and screensave tools. With both tools in the same
directory, load and run screenedit. Follow the on-screen instructions to specify a
filename for a new backdrop or to edit an existing one.
Show Less...
|
Commodore 64 Software Releases
Other Commodore 64 software releases, that do not require C64 OS, are added here as they
become available.
Executable files have no file extension, and should be transferred to the C64 as PRG-type
files.
| Filename |
Release Date |
Platform |
Version # |
File Size |
CRC32 checksum |
| filecopy |
2023-05-29 |
Commodore 64 |
1.0 |
551 bytes, 3 blocks |
85e1c6ec |
Filecopy
Universal, 2-Drive, 1-File, File Copier
Copies one file between the current directory and partition of any two devices. Virtually
all devices supported. Filecopy is designed to be as barebones and agnostic as possible.
It asks for a source device number, a destination device number, a filename, and a target
file type: PRG or SEQ. It then copies the file with that name between the two devices.
Nothing more, nothing less.
• Filecopy is extremely small, just 551 bytes. It can be loaded from any device, including
from VICE FS and IDE64 PCLink, in order to bootstrap copies from those devices to any
other.
• Filecopy has no additional hardware or software requirements. It can run from a
stock C64, using only standard BASIC and KERNAL calls.
• No file size limits. Filecopy can be used to copy files as small as a few bytes
to files that are hundreds of megabytes, give the destination device has sufficient
storage capacity.
• Only PRG and SEQ type files are supported.
• No disk speed enhancement is required. But if a disk speed enhancement is available,
such as JiffyDOS, FastLoad, ActionReplay, etc., it will be taken advantage of according
to its support for the device types involved.
• No device type detection is performed. As a consequence, filecopy is compatible with
every conceivable C64-compatible storage device which can be used with the standard
BASIC commands: open and close.
• Devices which support multiple partitions and subdirectories are fully supported.
Send DOS commands to both devices first, to set their current partition and current
directory. Filecopy copies between the default locations on each device.
The following device types are known to be supported: (This list is not exhaustive.)
- 1541
- 1571
- 1581
- CMD FD
- CMD HD
- CMD RAMLink
- SD2IEC
- IDE64
- IDE64 PCLink
- VICE FS
Show Less...
|
| Filename |
Release Date |
Platform |
Version # |
File Size |
CRC32 checksum |
| monitorc |
2023-07-20 |
Commodore 64 |
1.0 |
4098 bytes, 17 blocks |
434d2334 |
MonitorC
Versatile Machine Language Monitor
A versatile machine language monitor, one of the most featureful available for the C64.
The original author of this tool is unknown. This monitor is from a collection of native
development tools for the Commodore 64 available on the public FTP server c64.rulez.org.
MonitorC can disassemble code, examine memory contents, load and save blocks of binary
data to and from disk, search memory, transfer memory and much more.
Loading Instructions
MonitorC loads to $C000.
With JiffyDOS or similar DOS wedge:
£monitorc
Without JiffyDOS:
load"monitorc",8,1
sys49152
Quick Command Reference
| Command |
Syntax |
Usage Notes |
| Assemble |
.a 2000 lda #$20 |
Assemble code at $2000. Auto-calculates branch offsets. |
| Breakpoint |
.b 1000 |
Set a breakpoint at $1000. See: Quick Trace. |
| Compare |
.c 1000 2000 c000 |
Print the locations of bytes from $1000 to $2000 that are unequal to corresponding memory at $c000. |
| Decimal Conversion |
.#64738 |
Converts the decimal number 64738 to hexadecimal, $fce2. |
| Disassemble |
.d 2000 3000 |
Disassemble memory from $2000 to $3000, second parameter is optional. |
| Edit Character |
.ec 6000 7000 |
Display memory visualized in 8 bit rows for editing character data, second parameter is optional. |
| Edit Sprite |
.es 6000 7000 |
Display memory visualized in 24 bit rows for editing sprite data, second parameter is optional. |
| Exit |
.x |
Exit the monitor back to BASIC. |
| Fill |
.f 1000 2000 ff |
Fill memory from $1000 to $2000 with $ff. |
| Go |
.g 1000 |
Execute code at $1000. If parameter omitted, continues executing from PC. |
| Hexadecimal Conversion |
.$ffd2= |
Converts the hexdecimal number $ffd2 to decimal, 65490. |
| Hunt |
.h 1000 2000 'term
.h 1000 2000 a0 b0 c0 |
Search memory $1000 to $2000 for string "term".
Search memory $1000 to $2000 for byte sequence $a0 $b0 $c0.
|
| Load |
.l "//:filename",0c |
Load filename on device 12 (0c) to the load address of the PRG file. |
| Memory |
.m 2000 3000 |
Display memory from $2000 to $3000, second parameter is optional. |
| Quick Trace |
.q 1000 |
Traces code starting at $1000, or from PC if address is omitted. Stops on
established breakpoints and disassembles. *
|
| Registers |
.r |
Display the current PC, NMI, Accumulator, X and Y registers, stack pointer,
and processor flags. |
| Save |
.s "//:filename",0c,2000,3000 |
Save to filename on device 12 (0c) memory from $2000 to $2fff (end address -1) |
| Transfer |
.t 1000 2000 3000 |
Memory from $1000 to $2000 is transfered to $3000.
|
| Walk |
.w 1000 |
Single step code from $1000, or from PC if address is omitted. Disassembles
each instruction to be executed next. *
|
* Press STOP during a Quick Trace or Walk to stop executing and return to the monitor's
prompt.
* Press "j" during a Quick Trace or Walk to leave the monitor by jumping to that
point of the program and begin executing directly.
Show Less...
|
Last modified: Sep 21, 2023
