In the series about the internals of the geoWrite WYSIWYG text editor for the C64, this article discusses the font manager’s system of caches for pixel fonts.
In the series about the internals of the geoWrite WYSIWYG text editor for the C64, this article discusses how the app manages to extend its usable RAM by 5 KB using a custom screen recovery solution.
geoWrite is a WYSIWYG rich text editor for the Commodore 64 GEOS operating system, which runs with a total of just 64 KB of RAM. In the series about the internals of geoWrite, this article discusses how it manages to fit 52 KB of code into the available 23 KB of application RAM.
The system software of the Commodore 64 has been extensively reverse-engineered. Next to disassemblies of the ROM, several “memory maps” have been published: tables that document system variables in the first kilobyte of RAM, and how to tweak the system software with
POKE. Now, I’m presenting the Ultimate C64 Memory Map: A C64 memory reference that shows eight sources side-by-side.
In this episode of computer archeology, we deconstruct a very interesting case of borrowing code from multiple places – but first try this D64 disk image with any Commodore 64 emulator or a real C64:
extract-adf is a tool for recovering files from broken Amiga OFS filesystem images. It can reconstruct directory hierarchies even for files that don’t have directory entries.
This article is about screen captures of the discontinued German online service Bildschirmtext/Btx.
The GEOS operating system for the Commodore 64 achieved to replicate much of the GUI of the original Macintosh on a 1 MHz 8 bit CPU with just 64 KB of RAM. The GEOS Demo is a presentation by Berkeley Softworks (BSW), the creators of GEOS, to showcase the features of GEOS and BSW’s applications.
Here are some hi-res photos of the Commodore 232 and Commodore 264 prototypes. The C-232 and C-264 were two1 of the planned models of the TED series, but neither shipped. The C-264 became the Plus/4, with productivity software preinstalled in ROM, and the low-lost C-232 was replaced by the even lower-cost C16 and C116 models.
I have previously analyzed the ROM images of some third party disk drives for the Commodore 64: The result was that most of them were just using the original binaries with some obfuscation, and some with some added features. This time, let’s look at another drive, the “Technica”, which is a little special in this regard.
I have this pile of broken GEOS disks that were sent in for replacements. In two previous articles (1, 2), I explored the reasons why the disks broke. Now let’s be constructive: Can we reconstruct the original bits by combining the correct parts? This article shows how it is possible with the help of a small tool that combines the good parts of several broken disk images.