.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "PRE_WRITE_MST_FIXUP" "9" "09 October 2005" "" ""

.SH NAME
pre_write_mst_fixup \- apply multi sector transfer protection
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int pre_write_mst_fixup  (NTFS_RECORD * \fIb\fB, const u32 \fIsize\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIb\fB\fR
pointer to the data to protect
.TP
\fB\fIsize\fB\fR
size in bytes of \fIb\fR
.SH "DESCRIPTION"
.PP
Perform the necessary pre write multi sector transfer fixup on the data
pointer to by \fIb\fR of \fIsize\fR\&.
.PP
Return 0 if fixup applied (success) or -EINVAL if no fixup was performed
(assumed not needed). This is in contrast to \fBpost_read_mst_fixup\fR above.
.SH "NOTE"
.PP
We consider the absence / invalidity of an update sequence array to
mean that the structure is not subject to protection and hence doesn't need
to be fixed up. This means that you have to create a valid update sequence
array header in the ntfs record before calling this function, otherwise it
will fail (the header needs to contain the position of the update sequence
array together with the number of elements in the array). You also need to
initialise the update sequence number before calling this function
otherwise a random word will be used (whatever was in the record at that
position at that time).