LockerGnomeTech news and nostalgia for today's technology professionals
Subscribe

Search

RetroPalm OSRetrocomputing

A Palm OS developer opened a 1 GB archive of SDKs, examples and limited-release OS source

Recovering a handheld app means recovering its build environment, too. A programmer’s 2001 instructions show why preserved headers alone cannot finish the job.

Epoxy resin of Chris Pirillo: he sets a clear resin block holding an old Palm handheld
Illustration: LockerGnome

Palm OS development has escaped another aging hard drive. Developer Aaron Ardiri says much of this collection sat in backups for more than 25 years before he made it available on GitHub.

The archive contains the less glamorous things that make an old platform understandable: programming guides, headers, libraries, conference presentations, utilities and sample code. The folder you didn’t think to save in 2001 may explain more than a working handheld does today.

The examples cover databases, communication and memory management as well as graphics. That gives a researcher several ways into the collection: trace an API from its declaration to a sample, compare how an application stored records, or inspect the assumptions an old tool made about the operating system. The limited-release source is specifically identified as Palm OS 3.5, 4.0 and 5.0; the label does not make the entire platform an open-source release.

A Linux Palm Developer’s Quick Start Guide written by Jim Weller in 2001 shows how many pieces used to surround an SDK. Weller needed PRC Tools, GNU compiler tools, the Palm OS SDK and an emulator. His instructions patched GCC, binutils and GDB, then built a toolchain targeting m68k-palmos. An SDK was one ingredient in a fairly particular recipe.

Even the directory names mattered. Weller had to rename SDK folders for the Linux setup, and he found that older how-to examples used incorrect header names, types and compiler names for SDK 3.5. A folder full of source can look complete right up to the moment the compiler asks for something nobody has mentioned since the Clinton administration.

Ardiri’s own account is the source for the collection’s size and history. He says files are preserved in their original form where possible, with some incomplete or duplicated material. Ardiri describes the priority as “preservation first, modernization second.” Current operating systems and tools aren’t promised to run them.

If your first thought was to download a Palm and boot it, the exclusions deserve a look before you start: the repository doesn’t include ROM images, firmware dumps, simulator or emulator binaries, or unauthorized commercial applications. Those missing ingredients still need their own appropriately authorized sources before an old project can become something that actually runs again.

Weller’s account reaches an actual result: he reports running the compiled hello.prc in an emulator and on a Palm IIIe. That is a useful standard for revival work. “The source exists” and “the application runs” are separate milestones, with an executable file and a named target between them.

Ardiri welcomes contributions that document legacy utilities on modern systems, identify corrupted or duplicate files, and recover missing authors or context. Those small annotations could make the archive substantially easier to use without changing the artifacts themselves. A successful build recipe can sit beside the preserved original, so the next person gets both the history and a way through it.

Preserving original files keeps their context, but it also keeps their missing dependencies. A useful next contribution would be a documented path from one surviving example to a successful build, showing exactly which old tools it still needs.

More Retro

Every Retro story →