Source review: October 11, 2026. Identify the console, region and project revision before applying a hardware or software procedure.
Identify the physical cartridge
Record the label, case, board marking and game revision before cleaning or opening a cartridge. Preserve photographs and instructions alongside any digital image. Turn the console off for cartridge changes, insert without forcing the mechanism and investigate a damaged slot rather than repeatedly pressing harder. A failure confined to one cartridge should be compared with a known working cartridge and the built-in games before declaring a console-wide fault.
Understand the unusual interface
Sean Riddle's first-hand dumping work explains why ordinary Channel F program-storage chips cannot simply be treated as a conventional EPROM. The F8 system uses a different control arrangement. His research also documents additional SRAM in Videocart 10, showing that a cartridge image alone does not describe every hardware requirement. Keep a cartridge's interface and extra-memory information with its dump rather than assuming that equal file sizes imply identical hardware.
Preserve a dump with its method
Use a dumper designed for the actual cartridge interface. Save its hardware revision, firmware or program version, read settings and output format with the raw read. Perform repeat reads and compare cryptographic hashes; disagreement is evidence to investigate contacts, timing or reader support. Preserve the first unmodified files even if a later tool produces a normalized emulator image. Describe any conversion explicitly. This creates a traceable record without discarding information that a future emulator or researcher might need.
Read multicart claims narrowly
Riddle's MultiGame project is a documented historical hardware design based on the SABA Schach cartridge and its interface circuitry. It is not an instruction sheet for every contemporary programmable cartridge. Before buying or building a different design, obtain that creator's supported file sizes, bank-switching details, firmware requirements and extra-RAM compatibility. A menu listing a title does not establish that every cartridge-specific behavior has been reproduced. Keep the original project documentation with the exact board used.
Check preservation beyond a title screen
Test game selection, both controllers, console options, restart behavior and a representative period of play. For a game with special hardware, choose a test that exercises it. If an image works in one emulator but fails on a multicart, record both versions and the precise symptom rather than overwriting the image to make it look different. A preservation entry should separate physical condition, repeat-read agreement, image identity and observed execution. For a homebrew release, include its author, license, source revision and intended cartridge target, so original code and later repackaged collections retain a clear history.
Sources and project documentation
- Sean Riddle: original Channel F hardware and cartridge research
- Sean Riddle: original MultiGame cartridge design
- Fairchild: F8 Guide to Programming, 1976 (archived scan)
Continue with homebrew and emulation.