PackDir

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(distinction from Quake PAK and Git Pack)
Line 42: Line 42:
  
 
== Identification ==
 
== Identification ==
Files begin with "{{magic|PACK}}", followed by {{magic|0x00}}. Note that this is not enough to distinguish them from [[Git]] pack format.
+
Files begin with "{{magic|PACK}}", followed by {{magic|0x00}}. Note that this is not enough to distinguish them from [[Quake_PAK]] pack format. However, it cannot be a [[Git]] pack format, because Git expects a 4 byte version number in big endian, which means byte {{magic|0x02}} or {{magic|0x03}} would be there.
  
 
== Software ==
 
== Software ==

Revision as of 13:44, 18 October 2023

File Format
Name PackDir
Ontology

PackDir is an archiving tool for RISC OS, and its associated file format. It can compress file using an LZW algorithm, or store uncompressed files.

The LZW algorithm is the variant used in the Zoo archiver, except that the "max bits" parameter is configurable.

Its RISC OS filetype is 68E.

Contents

File format

This section contains reverse-engineered information about the format.

32bit ints are in LSB format. Strings are NULL-terminated ASCII.

File/directory dates and times are stored in a RISC OS format: The low 8 bits of the "load" address, combined with the "exec" address, form a 40-bit integer representing the number of 0.01-second intervals since the beginning of the year 1900.

File format:

   Header
   object_entry_1
   object_entry_2
   ...
   object_entry_N

Header:

   String: "PACK\0"
   32bit_int: LZW maxbits - 12

object_entry:

   string: object_name (including trailing NULL)
   32bit_int: load (RISC OS load address)
   32bit_int: exec (RISC OS exec address)
   32bit_int: original_file_length if this object is a file, number_of_child_entries otherwise
   32bit_int: attributes (RISC OS read/write permissions)
   32bit_int: entry_type: 1 == directory, 0 == file.  NB: This field is missing for the first entry in the file -
              the first entry is always a directory

If the entry is a file, then these fields follow:

   32bit_int: Compressed_file_length or special code - If this field is -1 the file is not compressed,
              otherwise compressed with LZW.
   N bytes: archived file data.  N == compressed_file_length if file is compressed, otherwise original_file_length

Identification

Files begin with "PACK", followed by 0x00. Note that this is not enough to distinguish them from Quake_PAK pack format. However, it cannot be a Git pack format, because Git expects a 4 byte version number in big endian, which means byte 0x02 or 0x03 would be there.

Software

Example files

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox