RAM pack
RAM expansion cartridge
RAM pack, RAMpack, RAM expansion cartridge, RAM expansion unit (REU), memory expansion pak and memory module are some of the most common names given to various self-contained units or cartridges that expand a computer, games console or other device's own internal RAM in a user-friendly manner.
Such units are generally designed to be installable by an end-user with little technical knowledge, often simply by plugging them into an expansion or cartridge slot easily accessible at the rear of the machine (e.g. the Sinclair ZX81 or the VTech Laser 200), or via a user-accessible hatch (e.g. the Atari 800's CX852 and CX853 modules or the Nintendo 64 Expansion Pak).
The ZX81 16K RAM expansion gained particular notoriety for the "RAM pack wobble" problem because it was top-heavy and only supported by the edge connector. This could lead to it falling out, crashing the ZX81 and losing any program or data currently in the computer's memory.
Examples of such memory expansions include:
Jupiter Ace RAM Pack
Sinclair ZX80 RAM pack units (available in 1–3 KB and later 16 KB)
Sinclair ZX81 16KB RAM unit, commonly referred to as "RAM Pack" like its predecessor
Atari 1064 Memory Module (expanded the Atari 600XL's 16 KB RAM to 64 KB)
VIC-20 RAM cartridges officially available in 3 KB (with or without BASIC extension ROM), 8 KB, 16 KB, with 32 KB and 64 KB third-party cartridges also available
Commodore REU, a series of RAM Expansion Units (REUs) for the Commodore 64 and Commodore 128 computers (128 KB, 256 KB and 512 KB capacities)
Saturn carts, 1 or 4 MB of RAM, sold by SNK and Capcom respectively for use with their games.
Begin with the source’s own compact description: “RAM pack” is rAM expansion cartridge. The dossier treats that line as a proposition to test through pack, expansion and cartridge, not as a finished interpretation.
Why this record matters
The phrase “rAM expansion cartridge” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jul 18, 2025. The linked authority identifier is Q7275762. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1064.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “RAM pack”, its source revision and the description used here.
- Expand the search: follow RAM pack primary sources, RAM pack archive and pack research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “RAM pack”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “RAM pack” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.