D/CAS¶
A historical family of numbered compatibility profiles from the Working Group for Data Cassette Drive Compatibility, specifying recording formats through which conforming streamer-cassette drives and media could interchange data.
Core Idea¶
D/CAS is a historical family of numbered compatibility standards for streaming data-cassette drives and recording media. The strongest surviving primary evidence, TEAC's specification for its MT-2ST/F50 drive, expands the acronym as “The Working Group for Data Cassette Drive Compatibility” and states that the suffix in D/CAS-XX is the number of a standard approved by that group.[1] This corrects the commonly repeated expansion “Data/CASsette.” Products and media were described as D/CAS when they implemented one of those numbered profiles; D/CAS itself was neither one drive model nor one undifferentiated tape format.
The abstraction is the interoperability contract: a profile fixes enough physical-recording behavior—such as track organization, data format, density, direction, and compatible media/transport assumptions—that a conforming drive can interpret a tape written under the same profile. Later drives could declare read compatibility with earlier profiles. TEAC's F50, for example, declares D/CAS-103 write/read conformance with 21 tracks and downward read support for D/CAS-85 with 17 tracks and D/CAS-25 with 9 tracks.[1]
That evidence also disproves the frozen article's proposed invariant that D/CAS always used four tracks. A contemporary 1984 account identifies D/CAS-6 as the four-track profile; four tracks characterize that numbered member, not the whole family.[2] The corrected node therefore survives as a domain-specific standards-family abstraction. It supports format identification, compatibility assessment, media migration, and recovery planning without turning a brand, cassette shell, or backup product into the concept.
Structural Signature¶
The recognition center is
D/CAS working-group profile number + specified magnetic recording organization + conforming cassette medium and drive behavior -> data interchange within that profile.
- A numbered profile. A designation of the form
D/CAS-nidentifies one working-group-approved compatibility specification. Bare resemblance to a compact cassette is insufficient. - A recording contract. The profile governs physical or low-level logical recording characteristics such as track count and arrangement, recording density or flux-transition requirements, direction of traversal, and data framing needed by drives.
- A conforming medium. A data cassette with the tape formulation, geometry, length, recognition features, and quality required by the implementation carries the recorded signal.
- A conforming drive. A transport, head-positioning system, read/write channel, controller, and firmware implement the profile.
- A compatibility claim. A manufacturer or specification states which profiles the drive writes and reads; write support, same-profile read support, and backward read support are distinct.
- An interchange result. Data written according to the profile can be recovered by another compatible drive, subject to media condition and implementation tolerances.
- Profile-scoped parameters. Track count, density, speed, capacity, and encoding are attached to a numbered profile or product combination, not promoted to universal D/CAS invariants.
- A historical standards authority. The working group's approval and number are part of the identity; a proprietary cassette recording scheme does not become D/CAS merely by looking similar.
The TEAC F50 supplies a concrete profile transition: it records D/CAS-103 on 21 tracks at a specified streaming regime and reads D/CAS-85 and D/CAS-25 media using their 17- and 9-track organizations.[1] That is standards-family behavior—versioned compatibility—not evidence that all profiles share one layout.
What It Is Not¶
- Not “Data/CASsette” as the authoritative expansion. That phrase is a later shorthand or backronym; the manufacturer specification identifies the working group for Data Cassette Drive Compatibility.
- Not one physical cassette product. TEAC CT-series media, Verbatim or Maxell streamer cassettes, and individual drive models are implementations or claimed-compatible products.
- Not universally four-track. D/CAS-6 is documented as four-track, while D/CAS-25, -85, and -103 use 9, 17, and 21 tracks in the primary TEAC specification.
- Not a capacity class. “600 MB,” “155 MB,” or “60 MB” depends on profile, medium, formatted assumptions, and drive; none defines the family.
- Not ordinary Compact Cassette data encoding. Home-computer cassette systems often modulated audio-frequency tones through consumer cassette decks. D/CAS streamers used dedicated drives, data media, and numbered recording profiles.
- Not Digital Compact Cassette (DCC), DAT, or DDS. Those are different audio/data cassette systems with different recording mechanisms and standards.
- Not QIC or Travan generally. Historical D/CAS profiles borrowed from or coexisted with cartridge-tape practices, but QIC and Travan are separate format families.
- Not an application backup format. D/CAS does not by itself specify directory trees, archive semantics, file labels, operating-system backup commands, or retention policy.
- Not distributed compare-and-swap.
DCASin concurrency literature may mean double-word or distributed compare-and-swap; the atomic memory operation has no relation to D/CAS tape.
Scope of Application¶
D/CAS belongs to late-twentieth-century computer backup and magnetic-tape interoperability. Its literal domain includes drive and media specifications, legacy-system maintenance, storage-device compatibility, digital forensics, and migration of data from obsolete streamer cassettes.
The family is profile-sensitive. The contemporary Computers & Electronics account describes the D/CAS compatibility working group and D/CAS-6 as a four-track recording standard intended to promote cross-machine exchange.[2] The later TEAC specification documents D/CAS-25, -85, and -103 as distinct profiles and makes support direction explicit.[1] These sources establish continuity of the standards-family identity without requiring a complete reconstruction of every D/CAS number ever proposed.
Modern digital-preservation work may use D/CAS as a media-identification label, but successful recovery still requires the exact profile, a capable drive, controller/interface support, readable media, and knowledge of the higher-level archive or filesystem. The node governs the recording-compatibility layer, not the entire recovery stack.
Clarity¶
Identification proceeds in layers. First distinguish physical media from the standard: read model numbers, profile markings, recognition notches, and drive documentation. Second identify the numbered D/CAS profile rather than inferring it from cassette shape or advertised capacity. Third separate read capability from write capability; the F50's downward-read declarations do not imply that every D/CAS drive reads every earlier format. Fourth identify the host interface separately. In TEAC's F50 specification, SCSI conformance is listed under its own ANSI standard while recording format is listed under D/CAS, proving that host-command compatibility and tape-recording compatibility are different contracts.[1]
Finally, determine the application layer. A drive may reproduce low-level blocks correctly while the operating system lacks the backup software, block structure, labels, compression, or filesystem knowledge needed to restore files. Calling that failure “D/CAS incompatibility” would conflate layers.
Manages Complexity¶
The D/CAS profile number compresses a large compatibility matrix. Without it, an archivist would have to infer head geometry, track count, density, direction, tape speed, medium, and controller behavior separately for every drive/tape pairing. A conformance declaration supplies a first-pass answer to “which drive can read this recording?”
The family also makes evolution legible. A later drive can add density and tracks while declaring selected downward-read routes. Compatibility becomes a directed graph, not a vague claim that all streamer cassettes are alike. This prevents destructive trials with the wrong equipment and focuses preservation work on the remaining missing layers.
Abstract Reasoning¶
- If a cassette resembles an audio Compact Cassette but lacks a D/CAS profile or compatible-drive record, appearance alone cannot establish D/CAS identity.
- If a drive declares D/CAS-103 write/read and D/CAS-85 read-only, it may migrate older -85 data to new storage but cannot be assumed to create new -85 recordings.
- If two profiles use different track counts, the head-positioning and read-channel behavior must select the correct organization; “same shell” does not imply interchangeability.
- If a source says every D/CAS medium has four tracks, the existence of documented 9-, 17-, and 21-track profiles falsifies the generalization.
- If the drive reads blocks but restore software cannot parse them, physical recording compatibility succeeded and the application format remains unresolved.
- If a controller is SCSI-compatible but the transport lacks the needed D/CAS recording profile, host-interface compatibility does not make the medium readable.
- If an old profile has no surviving capable drive, the written specification alone cannot recover the signal; preservation requires both semantic documentation and working or emulated acquisition hardware.
- If
DCASappears in a concurrency paper beside atomic registers, linearizability, or compare-and-swap, it is not the storage standard. - If
D/CASappears in a drive specification beside a numbered suffix, track count, and data cassette, the compatibility-family reading is strongly supported.
Knowledge Transfer¶
Literal reuse stays within magnetic-storage specification, drive qualification, legacy support, and digital preservation. The same roles—profile, conforming writer, conforming reader, medium, recorded format, and directed compatibility—must remain present.
Portable structure is carried by existing primes. Standardization captures convergence on a shared specification. Interoperability captures the intended cross-drive result. Compatibility captures the relation between a particular drive, profile, and tape. Encoding and Decoding describes the round trip from blocks to recorded signal and back. Serialization is adjacent only when higher-level structured data is flattened for storage; D/CAS itself is lower-level and does not define general object reconstruction.
Examples¶
- D/CAS-6. A contemporary trade account describes this member as a four-track variation related to QIC-24 recording practice and submitted for ANSI consideration.[2] The four-track fact belongs here, not to every D/CAS profile.
- D/CAS-25 downward read. TEAC's F50 specification lists D/CAS-25 as a 9-track format the drive can read.[1]
- D/CAS-85 downward read. The same drive lists the 17-track D/CAS-85 profile as readable, distinguishing it from the new write format.[1]
- D/CAS-103 implementation. The F50 declares write/read conformance to the 21-track profile and nominal 600-million-byte formatted capacity with CT-600F media, while warning that capacity depends on tape and operating conditions.[1]
- Physical maintenance. TEAC's MT-2ST/20D-IO maintenance manual documents a D/CAS tape transport with reel motors, sensors, and a head-seek unit that moves to the selected track, showing the hardware implementing the recording contract.[3]
- Non-example—audio data cassette. A consumer audio deck records tones on an ordinary cassette for an eight-bit microcomputer. It is cassette data storage, but not thereby a D/CAS profile.
- Non-example—atomic DCAS. A concurrent algorithm atomically compares and swaps two words. Its state-transition guarantee has no magnetic medium, profile number, or compatibility group.
Structural Tensions¶
- shared shell vs. incompatible recording — similar cassette geometry hides different track and signal contracts;
- family name vs. profile number — “D/CAS” aids grouping but the suffix carries the operational compatibility decision;
- backward reading vs. universal compatibility — selected migration paths do not create an all-to-all matrix;
- standard vs. implementation — a document defines behavior while real drives and aging media determine whether recovery succeeds;
- physical blocks vs. logical files — recording compatibility can succeed while archive interpretation fails;
- capacity marketing vs. environmental qualification — nominal capacity is not an invariant under all tapes and conditions;
- historical shorthand vs. primary expansion — “Data/CASsette” is memorable but conflicts with manufacturer documentation of the working-group name;
- acronym compression vs. cross-domain collision — removing the slash can confuse the tape family with compare-and-swap terminology.
Structural–Framed Character¶
D/CAS is mixed. Track organizations and conformance behavior are structural and testable. Membership in the named family, profile numbering, and compatibility declarations are framed by a historical standards body and vendor documents. A physically similar proprietary recording could reproduce the engineering pattern without becoming D/CAS unless it implemented a recognized profile.
Structural Core vs. Domain Accent¶
The structural core is shared numbered specification + conforming implementations + directed read/write compatibility + interchange test. The domain accent is magnetic streamer-cassette media, linear serpentine tracks, heads, tape speeds, D/CAS suffixes, and backup-drive documentation. Without that accent, the node reduces to Standardization and Interoperability.
Instantiates / Related Primes¶
- Standardization — the working group's profile approvals are constitutive; this is the proposed minimal parent.
- Interoperability — cross-drive data exchange is the intended outcome.
- Compatibility — support is assessed for a specific drive/profile/media relation and direction.
- Encoding and Decoding — hardware maps data blocks to magnetic transitions and reconstructs them.
- Serialization — relevant only at a higher data-representation layer, not exact coverage.
The prospective DAG contains one strict composition/part_of edge to prime:standardization. Consensus and Concurrency are false semantic neighbors, not parent candidates.
Relationships to Other Abstractions¶
Current abstraction D/CAS Domain-specific
Parents (1) — more general patterns this builds on
-
D/CAS is part of Standardization Prime
the working group's profile approvals are constitutive; this is the proposed minimal parent.the working group's profile approvals are constitutive; this is the proposed minimal parent.
Hierarchy path (1) — routes to 1 parentless root
- D/CAS → Standardization
Neighborhood in Abstraction Space¶
D/CAS sits in a sparse region of the domain-specific corpus (100th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (1565 abstractions)
Nearest neighbors
- Chain code — 0.73
- Datum reference — 0.72
- Star domain — 0.72
- 26-bit computing — 0.72
- Reachability problem — 0.72
Computed from structural-signature embeddings · 2026-09-08
Not to Be Confused With¶
- a specific TEAC, Verbatim, Maxell, HP, NCR, or Maynard cassette product;
- the TEAC MT-2ST/F50 or any other individual drive;
- “Data/CASsette” treated as the primary institutional expansion;
- every streamer cassette or every compact-cassette-derived data medium;
- ordinary Compact Cassette tone storage, Commodore Datasette, or Kansas City Standard encoding;
- Digital Compact Cassette, DAT, DDS, QIC, Travan, or LTO;
- SCSI or QIC-02 host/controller interfaces;
- backup archive, filesystem, compression, labeling, or retention formats;
- Serialization as a general structured-data transformation;
- distributed consensus, concurrency control, double compare-and-swap, distributed compare-and-swap, or atomic CAS.
References¶
[1] TEAC Corporation, MT-2ST/F50 Streaming Cassette Magnetic Tape Unit Specifications, archived by Bitsavers, https://www.bitsavers.org/pdf/teac/MT-2ST/MT-2ST_Specifications.pdf. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h
[2] “Setting Standards,” Computers & Electronics, September 1984, p. 84, archived by World Radio History, https://www.worldradiohistory.com/Archive-Poptronics/80s/1984/CE-1984-09a.pdf. registry ↩a ↩b ↩c
[3] TEAC Corporation, MT-2ST/20D-IO Streaming Cassette Tape Maintenance Manual, document 10180354-01, archived by Bitsavers, https://www.bitsavers.org/pdf/teac/MT-2ST/10180354-01_Teac_MT-2ST_20D-10_Streaming_Cassette_Tape_Maintenance.pdf. registry ↩
[4] Museum of Obsolete Media, “Streamer Cassette,” https://obsoletemedia.org/streamer-cassette/. Used only as secondary object documentation. registry
[5] “D/CAS,” Wikipedia, frozen revision 1301032346, https://en.wikipedia.org/wiki/D%2FCAS. Discovery provenance only; its acronym expansion and four-track generalization are corrected by primary documentation. registry