Preserve more than the cartridge bytes
A Pico preservation set should retain the cartridge image, the attached book and the interaction context. Photograph the label, regional markings, every page, the drawing-area overlay if supplied, and any instructions or accessory requirements. Capture pages squarely and without cropping printed targets. Keep untouched high-resolution masters separately from emulator-sized derivatives, recording page order and any missing or damaged material.
Identify the cartridge board and the reader's documented Pico support before connecting hardware. Related processor architecture or a similar edge connector does not establish safe compatibility with a Genesis dumper. First-hand hardware research includes cartridge and revision-specific observations, but is not a current universal reader or flash-cart recommendation. Where a verified reader is available, retain repeated ROM reads, hashes, tool versions and the adapter documentation. Do not write to an original cartridge as part of a read-only preservation session.
| Artifact | Preservation note |
|---|---|
| Cartridge image | Repeated read result, hash, reader and exact format. |
| Page masters | Physical order, complete artwork and printed selection targets. |
| Instructions and accessories | Pen, keyboard or other requirements for the actual title. |
| Hardware test record | Console revision, page sequence and input observations. |
Configure a documented emulator
PicoDrive's project documentation describes Storyware page and pad-overlay PNG support and mouse-based pen input. Follow the naming conventions and controls in the readme for the installed build; port-specific hotkeys are not interchangeable. Store the ROM hash, emulator revision, page assets and configuration together. Verify selecting printed targets as well as drawing-area movement, and compare every available page rather than stopping when the title boots.
Keep native saved data, where a particular cartridge supports it, separate from emulator states. Do not assume every Storyware title has persistent storage. A state may depend on the exact emulator build and configuration. Missing artwork can make a program difficult to use without proving the ROM is bad, while a mouse-accessible activity does not verify the original console's pen hardware.
Make research reproducible
The original Pico reverse-engineering notes document input behavior and clearly distinguish observations from guessed ranges. Preserve that distinction in new contributions. Begin a software experiment with an identified game or a minimal Pico-target test program, record the relevant input reads, and change one behavior at a time. An ordinary Genesis build does not automatically exercise Pico pen, page or speech hardware.
For emulator work, pin the source commit, retain a small patch and record the input sequence needed to reproduce the result. Publish your own source and test assets with their licenses, without treating copied commercial resources as original homebrew. Original-hardware execution additionally requires a documented delivery method for that board; do not promise a generic flash-cart route. Link results back to input troubleshooting with the exact title, revision and limits of the experiment.