rules enforced by NTFS as to what these last 48 bytes contain. Contrast this with the first 16 bytes of an object ID, which can be used to open the file, so NTFS requires that they be unique within a .<57> FSCTL_SET_OBJECT_ID_EXTENDED This message returns the results of the . If the file system of the containing the specified file or directory does not support the use of ObjectIds, the request will not succeed. The error code returned in this situation varies, depending on the file system. The only data item this message returns is a status code, as specified in section 2.3. The status code returned directly by the function that processes this MUST be STATUS_SUCCESS or one of the following. Error code Meaning STATUS_INVALID_PARAMETER The handle is not to a file or 0xC000000D directory, or the input buffer's length is not equal to the size of an EXTENDED_INFO structure. STATUS_ACCESS_DENIED The handle was not opened with 0xC0000022 write data or write attribute access. STATUS_OBJECT_NAME_NOT_FOUND The file or directory has no 0xC0000034 object ID. STATUS_INVALID_DEVICE_REQUEST The file system does not support 0xC0000010 the use of object IDs. FSCTL_SET_REPARSE_POINT Request This message requests that the server set a on the file or directory associated with the handle on which this was invoked. The message contains a or a (including subtypes) data element. Both the REPARSE_GUID_DATA_BUFFER and REPARSE_DATA_BUFFER structures begin with a ReparseTag field. The ReparseTag value uniquely identifies the driver that creates/uses the reparse point, and the filter driver processes the reparse point data as either a REPARSE_GUID_DATA_BUFFER or a REPARSE_DATA_BUFFER, depending on the structure implemented by the filter driver for that type of reparse point. This message is applicable only to a file or directory handle, not to a handle.
rules enforced by NTFS as to what these last 48 bytes contain. Contrast this with the first 16 bytes of an object ID, which can be used to open the file, so NTFS requires that they be unique within a .<57> FSCTL_SET_OBJECT_ID_EXTENDED This message returns the results of the . If the file system of the containing the specified file or directory does not support the use of ObjectIds, the request will not succeed. The error code returned in this situation varies, depending on the file system. The only data item this message returns is a status code, as specified in section 2.3. The status code returned directly by the function that processes this MUST be STATUS_SUCCESS or one of the following. Error code Meaning STATUS_INVALID_PARAMETER 0xC000000D The handle is not to a file or directory, or the input buffer's length is not equal to the size of an EXTENDED_INFO structure. STATUS_ACCESS_DENIED 0xC0000022 The handle was not opened with write data or write attribute access. STATUS_OBJECT_NAME_NOT_FOUND 0xC0000034 The file or directory has no object ID. STATUS_INVALID_DEVICE_REQUEST 0xC0000010 The file system does not support the use of object IDs. FSCTL_SET_REPARSE_POINT Request This message requests that the server set a on the file or directory associated with the handle on which this was invoked. The message contains a or a (including subtypes) data element. Both the REPARSE_GUID_DATA_BUFFER and REPARSE_DATA_BUFFER structures begin with a ReparseTag field. The ReparseTag value uniquely identifies the driver that creates/uses the reparse point, and the filter driver processes the reparse point data as either a REPARSE_GUID_DATA_BUFFER or a REPARSE_DATA_BUFFER, depending on the structure implemented by the filter driver for that type of reparse point. This message is applicable only to a file or directory handle, not to a handle.