See more on Chunks in general.
This is more detailed timestamp information, used when the simple time value within the INDX chunk is not enough.
The a (correlated) and b (subtype) Flagsmust be set.
The r (range of instances) , p (multi-part) & c, and y (payload specification) flags are all available. The i (instance sizes field is present) flag is always cleared.
The y flag may be present. COMP#71 might be particularly useful.
TIME-nd has a distinct meaning, documented below.
The Subtype must be set to 64.
The Instance Number matches the Instance Number of the DATA it applies to, as with any a-flagged chunk type.
The Payload contains 3 uintVs specifying the last-write time, creation time, and last-access time. Times are specified as the number of 100-nanosecond intervals since January 1, 1601 (UTC). This is the FILETIME value used in Windows, and appears to be as precise as any file system uses.
This value, if present, overrides the time in the INDX chunk. If this last-write time is inconsistant with the time value in the INDX chunk (the INDX chunk ought to have the same time but possibly noted at lower precision) it is not a fatal error, and this chunk takes precedence (but a warning would not be a bad idea). Alternativly, the INDX chunk may record 0 for its timestamp value, without being considered a contradiction.
TIME-nd indicates that the specified instances are in a different file in a multi-part archive.
This works the same as with DATA-nd chunks.
Page content copyright 2003 by John M. Dlugosz. Home:http://www.dlugosz.com, email:mailto:email@example.com