VISOR AND SPRINGBOARD MODULE RECORD
Purpose: Document one handheld/module combination and the complete task it can perform.
Repeat this record for each module; do not generalize one successful test to the entire Visor family.

Date / handheld model / OS:
Handheld condition / existing data:
Cradle or cable / desktop OS / Palm Desktop and HotSync:
Module manufacturer / model / hardware and software versions:
Required adapter (including detachable slot where applicable):
Module manual / supported handhelds / source and edition:
Power: handheld / own batteries / specified charging arrangement:
Required desktop software, media, maps or other dependencies:

BEFORE TESTING
Existing desktop copies preserved at:
Handheld and module data backup/export route:
Checked copies and remaining unique data:
Disposable test item and expected result:

TASK STAGES
Recognition: action / observed result
Main function: action / observed result
Saved item reopens: action / observed result
Export/transfer: action / observed result
Destination file/record opens: action / observed result
Exact errors / untested stages:

ARCHIVE
Module, attachment, cable and software stored together at:
Versions, instructions and license records retained at:
Data archive and second copy:
Conclusion for THIS combination:

INTERPRETATION
An application icon is evidence of recognition. Test capture, storage and export separately. For example, a camera image that opens on the handheld can still have an unresolved desktop-export dependency. Preserve existing data before trials and use the exact module's power instructions.

Yenra guide and source context:
https://yenra.com/handspring-visor/
Prepared October 6, 2026. Consult the linked guide and its model-specific primary references. Keep personal data and license keys out of shared records.