Cromemco Bytesaver
Cromemco S-100 memory board to program and read EPROMs

The Bytesaver, introduced by Cromemco in 1976, was the first programmable memory board for the MITS Altair and S-100 bus microcomputer systems. The Bytesaver had sockets for 8 UV-erasable EPROMs providing up to 8 Kbytes of storage. The EPROMs could be programmed by the Bytesaver, or read as computer memory. In the history of microcomputer systems, the Bytesaver was the first viable alternative to the use of punched paper tape for storing programs, and has been called “a great advance in microcomputer technology”.
Background
The Altair 8800, which began the personal computer revolution, was introduced in January 1975 with no hardware or software support for floppy disk or hard disk storage. When Paul Allen travelled to the MITS factory in Albuquerque, New Mexico to demonstrate what would become Microsoft BASIC, he brought with him a punched paper tape of the code that he and Bill Gates had developed. According to Allen, the 7168 byte program took 7 minutes to load from a Teletype Model 33 paper tape reader.
To reduce the time required to load software, and to support a more convenient storage medium than paper tape, Cromemco developed the first programmable solid-state storage system for the Altair microcomputer. Cromemco called it the "Bytesaver" and introduced it in the February 1976 issue of Byte magazine. With the Bytesaver the time to load Microsoft 8K Basic was reduced from 7 minutes to less than one second.
This brief starts where responsible research should: with the source description of “Cromemco Bytesaver” as cromemco S-100 memory board to program and read EPROMs. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as cromemco S-100 memory board to program and read EPROMs. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 23, 2025. The linked authority identifier is Q13418380. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1976 and 1975.
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 “Cromemco Bytesaver”, its source revision and the description used here.
- Expand the search: follow Cromemco Bytesaver primary sources, Cromemco Bytesaver archive and Cromemco 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 “Cromemco Bytesaver”?
- 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 “Cromemco Bytesaver” 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.