PALM OS SOFTWARE PRESERVATION CHECKLIST
Purpose: document one reproducible device/application combination.
Use: protect originals, investigate compatibility, then test one small package.
Keep private license keys and personal data out of copies shared with others.

Reviewer / date:
Device model / Palm OS version / available internal memory:
Application name / version / requirements / dependencies:
Desktop OS / Palm Desktop / HotSync version / conduit version:
Connection and driver/transport:
Expansion card type, filesystem and intended destination:

SOURCE AND PERMISSION
Original publisher/package or source URL:
Retrieval date, license evidence and installer identity:
Checksum and algorithm (detects changes; does not prove trustworthiness):

PRESERVE BEFORE INSTALLING
[ ] Copy existing desktop profile, backups, installers and card files.
[ ] Preserve original folder structure and names.
[ ] Keep another copy on separate storage.
[ ] Inspect expected files and representative readable records.
[ ] Review target user, install queue and every enabled conduit action.
[ ] Establish the model-specific device backup method before altering unique data.
If a backup route is unresolved, stop the installation and preserve the device.

ONE-PACKAGE TEST
Package and required companions:
Documented installation route and source of instructions:
Target user / destination / available space:
Transfer result and log:
Does application open?
Disposable record created, closed and reopened successfully?
Export/sync test performed only after reviewing actions? Result:

FAILURE RECORD
Failing stage: connection / transfer / launch / data access / synchronization.
Exact error:
One variable changed and result:

ARCHIVE
Keep original package, documentation, settings and known-good copies together.
Record what was actually tested on this model and what remains untested.

Yenra guide and source context:
https://yenra.com/palm-software/
Prepared October 6, 2026. Recheck exact model/version documentation.