here - OSTA - Optical Storage Technology Association

More documents

Recommendations

Info

2.3.5.1 Uint16 StrategyType The content of this field specifies the ICB strategy type used. For the purposes of read access an implementation shall support strategy types 4 and 4096. Shall be set to 4 or 4096, see NOTE . NOTE: Strategy type 4096, which is, defined in the appendixsection 6.6, is intended for primary use on WORM media, but may also be used. Strategy type 4096 is allowed only for ICBs in a partition with Access Type write-once recorded on rewritable and overwritablenon-sequential write once media. 2.3.5.2 Uint8 FileType As a point to clarification a value of 5 shall be used for a standard byte addressable file, not 0. The value of 248 shall be used for the VAT (refer to 2.2.102.2.11). The value of 249 shall be used to indicate a Real-Time file (see Appendix 6.11). Values of File types 250, 251 and 252 shall be used for the Metadata File, Metadata Mirror File and Metadata Bitmap File respectively. See section 2.2.13 for more details. File types 253 to 255 shall not be used. 2.3.5.2.1 File Type 249 Files with FileType 249 require special commands to access the data space of this file. To avoid possible damage, if an implementation does not support these commands it shall not issue any command that would access or modify the data space of this file. This includes but is not limited to reading, writing and deleting the file. 2.3.5.3 ParentICBLocation TheFor strategy 4 this field shall not be used and contain all zero bytes. For strategy type 4096 the use of this field is optional. NOTE: In ECMA 167-4/14.6.7 it states, “If this field contains 0, then no such ICB is specified.” This is a flaw in the ECMA standard in that an implementation could store an ICB at logical block address 0. Therefore, if you decide to use this field, do not store an ICB at logical block address 0. 2.3.5.4 Uint16 Flags Bits 0-2: These bits specify the type of allocation descriptors used. Refer to the section 2.3.10 on Allocation Descriptors for the guidelines on choosing which type of allocation descriptor to use. UDF 2.01 55 March50 April
Bit 3 (Sorted): For OSTA UDF compliant media this bit shall indicate (ZERO) that directories may be unsorted. Shall be set to ZERO. Bit 4 (Non-relocatable): For OSTA UDF compliant media this bit shall indicate (ONE) if the file is non-relocatable. If ONE, an implementation shall set the bit to ZERO if a modification will contravene the definition of this bit in ECMA 167-4/14.6.8. Should be set to ZERO unless required. NOTE: This flag is not a lock on the file in any way. It is used to indicate that an implementation has arranged the allocation of the file to satisfy specific application requirements. In these cases, any remapping of a written block (see UDF sparable partitions) or defragmentation of the file might not be desired. If a file with this flag set to ONE is copied, then the new copy of the file should have this bit set to ZERO. Bit 9 (Contiguous): For OSTA UDF compliant media this bit may indicate (ONE) that the file is contiguous. An implementation may reset this bit to ZERO to indicate that the file may be non-contiguous if the implementation can not assure that the file is contiguous. Should be set to ZERO. Bit 11 (Transformed): For OSTA UDF compliant media this bit shall indicate (ZERO) that no transformation has taken place. Shall be set to ZERO. The methods used for data compression and other forms of data transformation might be addressed in a future OSTA document. Bit 12 (Multi-versions): For OSTA UDF compliant media this bit shall indicate (ZERO) that multiversioned files are not present. Shall be set to ZERO. UDF 2.01 56 March50 April
Page 1 and 2:
Universal Disk Format ® Specificat
Page 3 and 4:
REVISION HISTORY 1.00 October 24, 1
Page 6 and 7:
CONTENTS 1. INTRODUCTION ..........
Page 8 and 9:
6.4 OSTA Compressed Unicode Algorit
Page 10 and 11:
1. Introduction The OSTA Universal
Page 12 and 13:
1.2 Compliance This document requir
Page 14 and 15: Media Block Address NOTE 1: This is
Page 16 and 17: 1.3.3 Terms May Optional Shall Shou
Page 18 and 19: non-overlapping Partitions with 2 p
Page 20 and 21: 2.1 Part 1 - General 2.1.1 Characte
Page 22 and 23: length of the field. The characters
Page 24 and 25: 2.1.5.2 char Identifier[23] Unless
Page 26 and 27: The Suffix Type column in the above
Page 28 and 29: For an Application Entity Identifie
Page 30 and 31: 2.2 Part 3 - Volume Structure 2.2.1
Page 32 and 33: NOTE: This field is used to determi
Page 34 and 35: 2.2.4 Logical Volume Descriptor str
Page 36 and 37: 2.2.5 Unallocated Space Descriptor
Page 38 and 39: EntityID. The scope of this EntityI
Page 40 and 41: 2.2.7.2.2 dstring LogicalVolumeIden
Page 42 and 43: Layout of Type 2 partition map for
Page 44 and 45: • Bits 1-7: Reserved. Shall be se
Page 46 and 47: Virtual Allocation Table structure
Page 48 and 49: the offset and length of a partitio
Page 50 and 51: The Metadata Partition Map (see2.2.
Page 52 and 53: 2.2.13.1 Metadata File (and Metadat
Page 54 and 55: 2.2.13.4 Procedure for de-allocatin
Page 56 and 57: } struct EntityID byte byte Impleme
Page 58 and 59: 2.3.2 File Set Descriptor struct Fi
Page 60 and 61: 2.3.2.7 struct EntityID DomainIdent
Page 62 and 63: In order to assist a UDF implementa
Page 66 and 67: 2.3.6 File Entry struct FileEntry {
Page 68 and 69: 2.3.6.8 FileLinkCount Hard links to
Page 70 and 71: Descriptors should be used. For exa
Page 72 and 73: 2.3.11.2 Uint32 PreviousAllocationE
Page 74 and 75: 3.2 Part 3 - Volume Structure 3.2.1
Page 76 and 77: 3.3 Part 4 - File System 3.3.1 File
Page 78 and 79: 3.3.2.1.2 Macintosh Bits 6 & 7 (Set
Page 80 and 81: 3.3.3 File Entry struct FileEntry {
Page 82 and 83: would be considered writable if the
Page 84 and 85: 3.3.3.5 byte Extended Attributes Se
Page 86 and 87: ignored and the file creation time
Page 88 and 89: 3.3.4.5.1.1 FreeEASpace This extend
Page 90 and 91: MacVolumeInfo format RBP Length Nam
Page 92 and 93: UDFFXInfo format (Volume IV, page 1
Page 94 and 95: The ApplicationUse area for this ex
Page 96 and 97: stream directory. If present, there
Page 98 and 99: Since the streams listed above have
Page 100 and 101: Object Logical Block Number is the
Page 102 and 103: mechanism for the host software to
Page 104 and 105: Vendor ID - The Vendor ID reported
Page 106 and 107: The OS2EA Stream contains a table o
Page 108 and 109: 4.2.2 File Identifier Descriptor st
Page 110 and 111: Definitions: A FileIdentifier shall
Page 112 and 113: 3. Invalid Characters: A FileIdenti
Page 114 and 115:
4. Trailing Periods and Spaces: All
Page 116 and 117:
If there is a file extension then t
Page 118 and 119:
defined as space that is not direct
Page 120 and 121:
UDF 2.01 111 March50 April
Page 122 and 123:
6.2 UDF Entity Identifier Values En
Page 124 and 125:
8 0 BeOS - generic 9 0 Windows CE -
Page 126 and 127:
} } returnValue = unicodeIndex; } r
Page 128 and 129:
} return crc; #ifdef MAIN unsigned
Page 130 and 131:
6.6 Algorithm for Strategy Type 409
Page 132 and 133:
nameLen = udfNameLen; } else { /* A
Page 134 and 135:
} needsCRC = TRUE; /* Append the CR
Page 136 and 137:
if (index < udfLabelLen || index ==
Page 138 and 139:
UDF 2.01 129 March50 April
Page 140 and 141:
unicode_t *udfName, /* (Input) Name
Page 142 and 143:
} #ifdef (OS2 | WIN_95 | WIN_NT) /*
Page 144 and 145:
6.8 Extended Attribute Checksum Alg
Page 146 and 147:
• The data of each file shall be
Page 148 and 149:
Read the File Identifier Descriptor
Page 150 and 151:
• An intermediate state is allowe
Page 152 and 153:
• The host shall perform read/mod
Page 154 and 155:
6.10.2.6.3 Level 3 No restrictions
Page 156 and 157:
ISO 9660 converted to UDF 1 st sess
Page 158 and 159:
For File Structure: 5. Unallocated
Page 160 and 161:
6.13 Recommendations for DVD+R and
Page 162 and 163:
6.13.1.4.2 Anchor Volume Descriptor
Page 164 and 165:
6.13.2.1 Requirements • The packe
Page 166 and 167:
6.126.15 UDF Media Format Revision
Page 168 and 169:
Description DCN Updated in UDF Revi
Page 170 and 171:
Registration Form Disk Format Speci
Page 172 and 173:
L Logical Block Size, 8, 9, 2425 Lo
show all

here - OSTA - Optical Storage Technology Association

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?