FILE_ID.DIZ

FILE_ID.DIZ is a
Traditionally, a FILE_ID.DIZ should be "up to 10 lines of text, each line being no more than 45 characters long", according to v.1.9 of the specification.[3] The concept of .DIZ files was to allow for a concise description of uploaded files to be automatically applied.
History
Bulletin boards commonly accept uploaded files from their users. The BBS software would prompt the user to supply a description for the uploaded file, but these descriptions were often less than useful. BBS system operators spent many hours going over the upload descriptions correcting and editing the descriptions. The FILE_ID.DIZ inclusion in archives was designed to address this problem.
SysOps could add a common third-party script written in PPL, called "DIZ/2-PCB"[4] that would process, rewrite, verify, and format DIZ files from archives as they were uploaded to a BBS. The software would extract the archive, examine the contents, compile a report, import the DIZ description file and then format it according to your liking. During this time, it was usual practice to add additional lines to the description, such as ads exclaiming the source of the uploaded BBS.
Even since the decline of the
Formal structure
While real-world use among BBSs varied, with the
Plain, 7-bit ASCII text, each line no more than 45 characters wide.
- Program/file name: Ideally, all uppercase and followed by one space. Carriage returns are ignored in this file.
- Version number: In the format "v1.123", followed by a space.
- ASP number: Only if an actual ASP member, otherwise ignored.
- Description separator: A single short hyphen "-".
- Description: The description of the file. The first two lines should be the short summary, as older boards cut off the rest. Anything beyond that should be extended description, for up to eight lines, the official cut-off size. Additional text could be included beyond that but might not be included by the board.
Many archives would stick strictly to the 45-character plain ASCII format for the first 8 lines, then contain an appended 80-character wide 8-bit ASCII or
See also
- .nfo — another standard for description files
- README
- Portable Application Description — a newer and more verbose alternative
- Standard (warez)
- SAUCE — an architecture or protocol created in 1994 for attaching metadata or comments to files. In use today as the de facto standard within the ANSI art community.[7]
- DESC.SDI — a similar filename that had fairly wide support, including PCBoard. It tended to be limited to a single line (smaller than a FILE_ID.DIZ file).
- JP Software in 1989[8]
References
- PMID 8557407. "Short ANSI text file (31 characters wide) often automatically extracted by Bulletin Board Service programs."
- ISSN 1535-9891.
DIZ stands for Description in Zip.
- ^ Holler, Richard (1994-05-17). "FILEID.TXT v1.9".
- ^ Reimerdes, Shawn. "DIZ/2-PCB PPE script for PCBoard, ULBYE100.ZIP".
- ISBN 978-1-93-226698-6.
- ^ Copy of official FILE_ID.DIZ documentation.
- ^ Olivier "Tasmaniac" Reubens (2013-11-12). "Standard Architecture for Universal Comment Extensions". ACiD.
- pseudo-environment variables,.)
0xED
being reserved for Digital Research/Novell/Caldera,0xC2
used by Total Commander for multiline file descriptions, and0xFD
reserved for FreeDOS
Further reading
- Ashby, Bryan (2020-12-09). "Retro Standards - Part 1: File Descriptors".
External links
- FILE_ID.DIZ Specification v1.9 by Richard Holler.
- Public Service Announcement: file_id.diz