ISO 9660: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content deleted Content added
m Directory record padding is only needed if the identifier length is even, not odd, as stated in ECMA-119 section 9.1.12. |
m According to ECMA-119 / 9.1.11 and my observations. The standard's wording also suggests that a directory identifier cannot be empty, but it's unclear. |
||
| Line 255: | Line 255: | ||
| 152 || 4 || Location of Optional Type-M Path Table || int32_MSB || LBA location of the optional path table. The path table pointed to contains only big-endian values. Zero means that no optional path table exists. |
| 152 || 4 || Location of Optional Type-M Path Table || int32_MSB || LBA location of the optional path table. The path table pointed to contains only big-endian values. Zero means that no optional path table exists. |
||
|- |
|- |
||
| 156 || 34 || Directory entry for the root directory || - || Note that this is not an LBA address, it is the actual Directory Record, which contains a |
| 156 || 34 || Directory entry for the root directory || - || Note that this is not an LBA address, it is the actual Directory Record, which contains a single byte Directory Identifier (0x00 or 0x01), hence the fixed 34 byte size. |
||
|- |
|- |
||
| 190 || 128 || Volume Set Identifier || strD || Identifier of the volume set of which this volume is a member. |
| 190 || 128 || Volume Set Identifier || strD || Identifier of the volume set of which this volume is a member. |
||