Ar (Haruhiko Okumura)

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Created page with "{{FormatInfo |name=ar (Haruhiko Okumura) |formattype=electronic |subcat=Archiving |released=1990 }} {{DISPLAYTITLE:ar (Haruhiko Okumura)}}'''ar''' is a compressed archive util...")
 
(Software)
Line 42: Line 42:
 
* {{CdTextfiles|sourcecode/msdos/arc_lbr/ar002.zip|AR002.ZIP}} - Source code + DOS binary
 
* {{CdTextfiles|sourcecode/msdos/arc_lbr/ar002.zip|AR002.ZIP}} - Source code + DOS binary
 
* https://oku.edu.mie-u.ac.jp/~okumura/compression/ar002/
 
* https://oku.edu.mie-u.ac.jp/~okumura/compression/ar002/
 +
* See also [[LHA#Software]].
  
 
== Links ==
 
== Links ==
 
* [https://oku.edu.mie-u.ac.jp/~okumura/compression/history.html History of Data Compression in Japan]
 
* [https://oku.edu.mie-u.ac.jp/~okumura/compression/history.html History of Data Compression in Japan]

Revision as of 17:09, 12 August 2021

File Format
Name ar (Haruhiko Okumura)
Ontology
Released 1990

ar is a compressed archive utility developed by Haruhiko Okumura. It is not related to the Unix ar archiver.

Contents

Discussion

ar was essentially a preview of the influential family of compression methods used by LHA version 2.x: the "lh5" method and related methods.

There seem to have been two main versions of ar. Neither has a clear version number, but based on the distribution filenames, and other information from Okumura, we may call them ar001 (or "ar v0.01"), and ar002 (or "ar v0.02").

ar was distributed mainly as source code, though most distributions of ar002 include a DOS binary.

ar001 uses its own file format, not known to be compatible with anything else. ar002 uses LHA file format.

Format details

ar's compression is based on LZ77 with static Huffman coding. ar001 by default uses a 4K history buffer, like LHA's "lh4" method. ar002 by default uses an 8K history buffer, like "lh5". It's unclear whether the ar compression methods are 100% compatible with the standard LHA methods, but they're at least very close.

The CRC-16 algorithm used by ar001 is not the same as the one used by ar002 and LHA. It seems to be the one called "CRC-16/IBM-SDLC" by CRC RevEng.

Identifiers

Neither version has a default or recommended filename extension.

Identification

ar001 files have no signature. Robust identification would probably have to involve verifying the header CRC.

For ar002, refer to LHA#Identification.

Specifications

For the header formats, see the comments near the beginning of the ar.c file in the corresponding distribution.

See also LHA#Specifications.

Software

ar001:

ar002:

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox