FILE_ID.DIZ is a plain text file containing a brief content description of the archive in which it is included.[1] It was originally used in archives distributed through bulletin board systems (BBS), and still in the warez scene.

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.

FILE_ID stands for "file identification". DIZ stands for Description In Zipfile.[2]

Clark Development and the Association of Shareware Professionals supported the idea of this becoming a standard for file descriptions. Clark rewrote the PCBDescribe program and included it with their PCBoard BBS software. The ASP urged their members to use this description file format in their distributions. Michael Leavitt, an employee of Clark Development, released the file specification and his PCBDescribe program source code to the public domain and urged other BBS software companies to support the DIZ file.

SysOps could add a common third-party script written in PPL, called "DIZ/2-PCB"[3] 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.

Traditionally, a FILE_ID.DIZ should be "up to 10 lines of text, each line being no more than 45 characters long." according to the specification v1.9.[4]

The concept of DIZ files was to allow a concise description of uploaded files to be automatically applied. Advertisements and "high ASCII" artwork were specifically prohibited.

Even since the decline of the dial-up bulletin board system, FILE_ID.DIZ files are still utilized by the warez scene in their releases of unlicensed software. They are commonly bundled as part of the complete packaging by self-described pirate groups, and indicate the number of disks, and other basic information. Along with the NFO file, it is essential to the release.[5] Especially in terms of unlicensed software ("warez"), it was common for each file in a sequential compressed archive (an archive intentionally split into multiple parts at creation so the parts can then be individually downloaded by slower connections like dial-up. Example: .rar, .r00, .r01, .r02, etc.), to contain this file. This probably contributed to its extended popularity after the decline of the bulletin board system in the late 1990s and early 2000s until now, since even casual consumers of unlicensed software would have stumbled upon it due to its abundance.


Formal structure

While real-world use among BBSs varied, with the NPD world and even different BBS brands coming up with expanded versions, the official format is:

Plain, 7 bit ASCII text, each line no more than 45 characters wide.

  1. Program/file name: Ideally, all uppercase, and followed by one space. Carriage returns are ignored in this file
  2. Version number: in the format v1.123, followed by a space
  3. ASP number: only if an actual ASP member, otherwise ignored
  4. Description separator: a single short hyphen "-"
  5. 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 cutoff 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 ANSI graphic page with better-formatted documentation after that.[6]

See also


  1. ^ Fong, B. C.; Doyle, D. J. (1995). "Renal function tests for windows — a model for the development and distribution of medical software on the Internet". International Journal of Bio-Medical Computing. 40 (1): 69–75. doi:10.1016/0020-7101(95)01126-Y . PMID 8557407 . "Short ANSI text file (31 characters wide) often automatically extracted by Bulletin Board Service programs."
  2. ^ White, Ron (July 2001). "Mystery Files". Ziff Davis Smart Business. 14 (7): 100. ISSN 1535-9891 . DIZ stands for Description in Zip.
  3. ^ Reimerdes, Shawn. "DIZ/2-PCB PPE script for PCBoard". Missing or empty |url= (help)
  4. ^ Holler, Richard (1994-05-17). "FILEID.TXT v1.9" .
  5. ^ Craig, P.; Honick, R.; Burnett, M. (2005). "The Release". Software Piracy Exposed . p. 95 . doi:10.1016/B978-193226698-6/50030-1 . ISBN 978-1-93-226698-6.
  6. ^ Copy of official FILE_ID.DIZ documentation
  7. ^ Olivier "Tasmaniac" Reubens (2013-11-12). "Standard Architecture for Universal Comment Extensions" . ACiD.

External links

Categories: Bulletin board systems | Filenames | Third-party DOS files | Warez

Information as of: 21.06.2020 11:00:24 CEST

Source: Wikipedia (Authors [History])    License : CC-BY-SA-3.0

Changes: All pictures and most design elements which are related to those, were removed. Some Icons were replaced by FontAwesome-Icons. Some templates were removed (like “article needs expansion) or assigned (like “hatnotes”). CSS classes were either removed or harmonized.
Wikipedia specific links which do not lead to an article or category (like “Redlinks”, “links to the edit page”, “links to portals”) were removed. Every external link has an additional FontAwesome-Icon. Beside some small changes of design, media-container, maps, navigation-boxes, spoken versions and Geo-microformats were removed.

Please note: Because the given content is automatically taken from Wikipedia at the given point of time, a manual verification was and is not possible. Therefore does not guarantee the accuracy and actuality of the acquired content. If there is an Information which is wrong at the moment or has an inaccurate display please feel free to contact us: email.
See also: Legal Notice & Privacy policy.