Source review: October 11, 2026. Identify the console, cartridge, interface and expansion separately; similarly named BASIC releases do not have identical requirements.
Preserve cartridges and tape programs separately
A physical game cartridge, a BASIC cartridge, an audio recording and a printed program listing represent different preservation objects. Record each object's author or publisher, label, version and dependencies. A cartridge image does not become a cassette program by changing its filename, and an audio file does not establish which BASIC release can load it. Store the instructions with the data so a future owner can reconstruct the intended hardware arrangement without guessing.
Record the cassette format explicitly
Identify whether a recording targets the original 300-baud Bally BASIC interface or the integrated 2000-baud AstroBASIC interface. Retain an untouched audio capture and create working copies for filtering or level experiments. Save the recorder, capture settings, channel selection and any processing performed. Compare a known compatible recording before adjusting hardware. If a loader fails at a repeatable point, note the counter position and visible symptom; if it fails inconsistently, investigate the audio path and levels as hypotheses rather than immediately rewriting the program.
Check memory and language requirements
An expansion-dependent tape may require a particular Blue Ram configuration and BASIC release in addition to the console. The Perkins archive preserves several hardware and software generations, so record the actual RAM unit, switch settings and program instructions. A program that loads partly into an incompatible configuration is not evidence that the recording is corrupt. Keep the unmodified listing and any corrected version separately, with a short explanation of which interpreter, expansion and loader were used to verify the change.
Match a multicart to its documentation
The GaMBITS UltiMulti archive includes versioned cartridge listings, switch settings and program-specific instructions. Consult the documents for the actual cartridge revision before selecting a BASIC or multi-load program. Preserve the setting table and the program's loading sequence with the hardware. Switch-selected software support is a property of that design, not a universal rule for every programmable cartridge. For a different project, obtain its creator's supported image sizes, memory assumptions and update procedure instead of applying another product's switch positions.
Verify both data and behavior
For cartridge reads, retain raw repeat dumps, reader details and hashes before making emulator-specific conversions. For cassette material, retain original audio, processed audio, extracted data and the conversion tool version as separate artifacts. Test a representative sequence beyond the opening screen, including controller knob behavior, keypad options and any second loading stage. For a new BASIC program, preserve the source listing, recording format and tested configuration together. These records allow a later researcher to tell whether a discrepancy belongs to the capture, the loader, the interpreter, the expansion or the software itself.
Sources and project documentation
- Bally Alley: original Bally BASIC and AstroBASIC manuals and author documentation
- Perkins Engineering: archived Blue Ram manuals, schematics and software
- GaMBITS: original UltiMulti version, switch and loading documentation
- Adam Trionfo: original Astrocade and BASIC cassette-emulation tutorials
Continue with homebrew development and emulation.