Convert v2 CAB Stored Control
Valid single-file Microsoft Cabinet using uncompressed CFDATA for bounded legacy extraction tests Stable P8 artifact p8-convert-legacy-cab.
- control.txt
Specifications
- Members
- 1
- Delivery Mode
- download-only
- Compression
- none
- Files
- 1
- Provider
- converter-v2
- Provenance
- Synthetic deterministic P8 fixture generated by generation/p8_content.py; seed namespace 2026082300
- Fixture Reserve
- convert-v2
Testing contract
Expected to pass- Scenario
- Parse the MSCF cabinet, locate its one folder and one file, and extract the stored CFDATA block.
- Expected result
- control.txt extracts to the exact CRLF-terminated text 'P8 CAB extraction control' and no secondary volume is requested.
What is a .cab file?
CAB is Microsoft's Cabinet archive format for bundling compressed files and installation resources. An MSCF header points to folder and file tables; data blocks may use no compression, MSZIP, Quantum, or LZX, and a cabinet can participate in a multi-volume set.
How to use this file
Use an example .cab file to test MSCF signature and table parsing, member names and sizes, bounded block decompression, unsupported-codec reporting, path-traversal defenses, and comparison with a published member manifest.
How to use this file for testing
“Convert v2 CAB Stored Control” is a deterministic Novus Examples fixture for Conversion testing, Compression testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
Documented properties for this file: CAB · 107 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Archive fixtures are documented down to their member list (shown on this page) and are deliberately safe — no zip bombs, executables, or hidden payloads. Test extractors against nested, unicode, empty, and encrypted variants.
Related files
- lz4LZ4 — Single FileA text file compressed with the LZ4 frame format (.lz4) — the container-free codec on its own — for testing LZ4 decompression and codec detection.
- tarTAR Containing Three ZIP ArchivesA tar carrying three ZIPs: two byte-identical and a third holding the same content stored rather than deflated. A deduplicating packer should notice the first two are the same object; a content-addressed one should notice all three extract to the same files.
- tbz2TBZ2 - Empty ArchiveThe empty tar under bzip2. Its payload is 1024 identical bytes, which is the run-length case bzip2's block sorter treats specially, so this doubles as the smallest sane bzip2 stream to test a decoder against.
- tgzTGZ Containing a TGZA gzipped tar whose second member is another gzipped tar. Tools that apply decompression greedily - gunzip until the bytes stop being gzip - skip straight past the outer tar and report the inner archive's two members as if they were the whole thing.
- zipZIP - All Members DeflateA ZIP whose every member uses compression method 8 (deflate). Its twin holds byte-identical content under the other method, so an extractor, a size estimator, or a repacking pipeline can be compared on the same payload with only the storage method changed.
- zipZIP - All Members StoredA ZIP whose every member uses compression method 0 (stored). Its twin holds byte-identical content under the other method, so an extractor, a size estimator, or a repacking pipeline can be compared on the same payload with only the storage method changed.
Generated by generation/p8_content.py. Free for any use, no attribution required — license.