From cartridge
to permission.

The Odyssey introduced the ritual of inserting a numbered object to change games, but the playable work was distributed across console circuitry, screen overlays, rules, cards, dice, and tokens.

The selector card alone is not the game. A faithful archive needs the console, overlays, instructions, and physical play pieces as well as the card.

A microprocessor remained in the console while each Videocart supplied a different program. The same hardware could now support a growing retail library.

The buyer retained a specific executable copy independent of the console. Preserving it means capturing the ROM and documenting the cartridge board, connector, and hardware behavior.

Later cartridges used techniques such as bank switching and added circuitry to exceed the assumptions of the launch hardware. The carrier could be part program and part hardware expansion.

A useful preservation record identifies the ROM and any mapper or special chip on the cartridge board; a bare file name is not always enough to reproduce behavior.

The original 13-sector format stored 116,480 bytes; the later 16-sector DOS 3.3 format stored 143,360. A purchased game could now modify the same physical object that carried it.

Magnetic decay, drive alignment, unusual encodings, and copy protection mean preservation may require a flux-level disk image—not merely copied files.

The base supplied the display, power, and shared controls; the inserted object supplied more of the machine than a conventional ROM shell.

A Microvision cartridge is not interchangeable data alone. Losing its processor or physical control assembly can destroy access even when the display unit survives.

Tape was sequential, slow, and sensitive to recording level and head alignment—but it was cheap, familiar, and easy for owners and small publishers to reproduce.

Tape stretch, dropout, magnetic loss, and loader-specific timing make the original waveform part of the evidence. Decoded program bytes alone can omit behavior.

The format paired a stable console interface with cartridges that could carry ROM and, in later releases, additional memory or support hardware.

The object is transferable, but an accurate record still needs board revision, region, special chips, and save-memory condition—not only the printed label.

The same physical carrier could hold different games over its life. Nintendo continued the rewrite service until September 30, 2003.

A surviving disk may not match its label or original sale state. Provenance requires imaging the actual contents and recording signs of rewriting.

Laser-read discs offered far more data and recorded audio without the per-unit cost of large semiconductor ROMs, but required a mechanical optical drive and add-on interface.

The disc remains a transferable copy, yet access depends on a compatible drive, system card, console, and region-specific hardware context.

Compact solid-state media tolerated travel and could carry battery-backed save RAM, allowing the program and the player’s history to move together.

ROM and save state age differently. A depleted battery can erase progress while leaving the program intact, so both need separate preservation.

CD enabled recorded audio, video, demos, and larger data sets at lower replication cost. Read-only media also forced player progress into separate proprietary storage.

The disc travels independently, but the saved experience does not. Preservation requires the disc image, compatible reader behavior, and separate save media.

Save architecture varied by title. Many games wrote to the Game Pak; others used a Controller Pak, so one platform did not have one uniform ownership model for progress.

An on-cartridge save travels with a lent copy. A Controller Pak save travels separately. Both can fail independently of the program ROM.

The disc held the game; the VMU held saves and small companion programs; the modem connected supported software to remote services.

Three collections must be documented separately. A GD-ROM needs its specialized reader, VMU files need preservation, and network modes may require unavailable services.

A mass-market console drive became a multi-format household reader. Games still launched from transferable discs while progress stayed on removable proprietary cards.

Disc, drive, firmware, and memory card are distinct failure points. Owning one does not preserve the others.

The smaller proprietary carrier gained optical replication economics while remaining bound to a platform-specific reader and separate save cards.

The disc is transferable but cannot be read as an ordinary consumer DVD. Compatible drives and memory cards remain part of the preservation chain.

The purchased disc remained the portable software object, but more of the working experience accumulated on a non-removable, failure-prone drive.

A readable disc may outlive the console state it relied on. Preservation must include hard-drive data, system software, keys, and network behavior as well as the DVD.

Two portable systems solved capacity, durability, saves, and sharing differently. PSP later added downloads; DS retained a GBA slot and wrote saves through the inserted card.

DS software and some saves stay together. UMD software and Memory Stick data do not—and UMD lost hardware compatibility with PlayStation’s next handheld.

The box could contain a transferable base product while additions, updates, and downloadable companions followed a console or account entitlement.

Disc ownership does not automatically preserve patches, DLC, or online functions. Store closure can stop new acquisition before it stops redownloads—and those are separate provider decisions.

A retail hardware variant could belong to the same platform family while being physically unable to use the family’s existing packaged library.

UMD ownership did not become usable PSPgo media. Access depended on catalog availability, account activation, download delivery, and local storage.

Nintendo stated that downloaded 3DS software was tied to receiving hardware and could not be shared like a Game Card. Vita downloads required PSN and activation; cards remained bearer objects.

One edition can be lent or resold. The other depends on hardware or account bindings, storage, and continued redownload support even when the executable content is nominally identical.

The optical object shifted from direct execution medium toward fast installation source and portable proof of possession.

A disc remained lendable, rentable, tradable, giftable, and resalable. Downloaded editions did not gain those bearer-object properties.

The case is evidence at title level: the box carried a substantial base, but not the full advertised launch configuration.

Preserving the disc alone does not preserve the release-day product. This does not prove every patched disc is incomplete; each title and revision needs its own audit.

The presence of a cartridge no longer establishes completeness. Saves, updates, downloadable content, and sometimes required game data live elsewhere.

A serious catalog must record the on-card payload, required download, playable offline portion, update history, and whether replacement downloads remain obtainable.

The platform could support the same software family while one retail machine had no path to read the customer’s existing discs.

A technically compatible game can still be inaccessible because the selected hardware lacks its reader. Preserving software and preserving a usable access path are different tasks.

Backward compatibility now depended on the exact hardware SKU as well as software support. A disc library could be compatible with the platform but unusable on the purchased model.

Long-term access requires preserving not just discs, but a drive-equipped machine or a later compatible reader. Digital replacements remain separate licenses.

Buying, downloading again, updating, and playing are distinct service functions. A storefront can close them on different dates.

Continued redownload access is a provider commitment, not a self-sufficient copy. Physical releases avoid reacquisition for their on-media payload but not necessarily patches or DLC.

The drive and disc can both be physically present, yet the reader itself has a first-use service dependency.

Future play depends on whether an unpaired replacement drive can still complete setup. Hardware activation belongs in the preservation record beside disc condition.

Acquisition, redownload, multiplayer, and preservation access operate under different technical systems and legal rules.

The disc preserves its payload. Add-ons and digital-only works depend on continued account delivery; multiplayer depends on each publisher; institutional exemptions do not create ordinary consumer ownership.

A Game-Key Card requires a first download, remains inserted for play, can move to another console, and needs no Nintendo Account for that download. A redeemed code does not remain a bearer authorization object.

The package label is insufficient. A catalog must record payload presence, initial download, account binding, carrier requirement after install, and whether the object remains transferable.