TTCOMP
From Just Solve the File Format Problem
(Difference between revisions)
(Documented identification bytes) |
|||
| Line 13: | Line 13: | ||
== Identification == | == Identification == | ||
| − | The first byte of a TTComp file | + | The first byte of a TTComp file indicates the type of compression: |
| + | * <code>0x00</code>: binary compression | ||
| + | * <code>0x01</code>: ASCII compression | ||
The second byte of a TTComp file specifies the size of the dictionary as follows: | The second byte of a TTComp file specifies the size of the dictionary as follows: | ||
| Line 20: | Line 22: | ||
* <code>0x06</code>: 4096 bytes | * <code>0x06</code>: 4096 bytes | ||
| − | Most TTComp files begin with bytes <code>0x00 0x06</code>. | + | Most TTComp files begin with bytes <code>0x00 0x06</code> indicating binary compression and a 4K dictionary. |
== Software == | == Software == | ||
Revision as of 20:39, 3 February 2014
TTComp archive is a compressed file format. It was apparently used by some software installation utilities.
It uses Shannon–Fano coding for data compression. It is probably identical, or nearly identical, to ZIP's obsolete "IMPLODE" compression method.
Though it may be called an "archive" format, it appears to store nothing more than a stream of compressed data.
Contents |
Sample files
Identification
The first byte of a TTComp file indicates the type of compression:
-
0x00: binary compression -
0x01: ASCII compression
The second byte of a TTComp file specifies the size of the dictionary as follows:
-
0x04: 1024 bytes -
0x05: 2048 bytes -
0x06: 4096 bytes
Most TTComp files begin with bytes 0x00 0x06 indicating binary compression and a 4K dictionary.
