-The \fBimagex capture\fR and \fBimagex append\fR commands create a Windows
-Imaging (WIM) image from a directory tree. The \fBimagex capture\fR command
-creates a new WIM file containing the captured image, while the \fBimagex
+The \fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR commands create a Windows
+Imaging (WIM) image from a directory tree. The \fB@IMAGEX_PROGNAME@ capture\fR command
+creates a new WIM file containing the captured image, while the \fB@IMAGEX_PROGNAME@
append\fR command appends the captured image to an existing WIM file.
Note: this man page primarily documents the UNIX behavior. See \fBWINDOWS
append\fR command appends the captured image to an existing WIM file.
Note: this man page primarily documents the UNIX behavior. See \fBWINDOWS
Yet another capture mode is entered when the \fB--source-list\fR option is
given. It is essentially an extension of the \fBNORMAL MODE\fR that allows
multiple files or directories to be incorporated into a WIM image using a single
Yet another capture mode is entered when the \fB--source-list\fR option is
given. It is essentially an extension of the \fBNORMAL MODE\fR that allows
multiple files or directories to be incorporated into a WIM image using a single
-This section documents the differences between \fBimagex capture\fR and
-\fBimagex append\fR in the Windows builds of wimlib versus the rest of this man
-page, which is written to document UNIX version.
+This section documents the differences between \fB@IMAGEX_PROGNAME@ capture\fR and
+\fB@IMAGEX_PROGNAME@ append\fR in the Windows builds of wimlib versus the rest of this man
+page, which is written to document UNIX build.
"NTFS" modes on Windows. There is simply one mode, and it uses the Windows API
to capture NTFS-specific information, including alternate data streams, reparse
points, hard links, and file attributes. So, you essentially get the advantages
of the "NTFS mode" documented above, but you can capture a WIM image from any
"NTFS" modes on Windows. There is simply one mode, and it uses the Windows API
to capture NTFS-specific information, including alternate data streams, reparse
points, hard links, and file attributes. So, you essentially get the advantages
of the "NTFS mode" documented above, but you can capture a WIM image from any
The \fB--source-list\fR option is supported on Windows, but the
\fB--dereference\fR option is not.
The \fB--source-list\fR option is supported on Windows, but the
\fB--dereference\fR option is not.
-Other than the differences documented in this section, the Windows version
-should be essentially equivalent to the UNIX version. However, one additional
-thing to note is that wimlib's Windows version of ImageX is NOT written to be
-command-line compatible with Microsoft's version of ImageX, although they are
-very similar.
+Except for the differences documented in this section, the Windows build of
+\fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR should be essentially equivalent to
+the UNIX build. However, one additional thing to note is that wimlib's Windows
+ImageX is NOT written to be command-line compatible with Microsoft's ImageX,
+although they are very similar.
\fB--check\fR
Include an integrity table in the new WIM file or the modified WIM file. If
this option is not specified, no integrity table is included in \fIWIMFILE\fR,
\fB--check\fR
Include an integrity table in the new WIM file or the modified WIM file. If
this option is not specified, no integrity table is included in \fIWIMFILE\fR,
.TP
\fB--compress\fR=\fITYPE\fR
Specifies the compression type for the new WIM file. This flag is only valid
.TP
\fB--compress\fR=\fITYPE\fR
Specifies the compression type for the new WIM file. This flag is only valid
must be the same as that of the existing WIM. \fITYPE\fR may be "none",
"maximum", or "fast". By default, it is "fast".
must be the same as that of the existing WIM. \fITYPE\fR may be "none",
"maximum", or "fast". By default, it is "fast".
Store the UNIX owner, group, and mode of regular files, symbolic links, and
directories. This is done by adding a special alternate data stream to each
directory entry that contains this information. Please note that this flag is
Store the UNIX owner, group, and mode of regular files, symbolic links, and
directories. This is done by adding a special alternate data stream to each
directory entry that contains this information. Please note that this flag is
option to create a WIM image from multiple files or directories. When
\fB--source-list\fR is specified, the \fISOURCE\fR argument specifies the name
of a text file, each line of which is either 1 or 2 whitespace separated
option to create a WIM image from multiple files or directories. When
\fB--source-list\fR is specified, the \fISOURCE\fR argument specifies the name
of a text file, each line of which is either 1 or 2 whitespace separated
Subdirectories in the WIM are created as needed. Multiple source directories
may share the same target, which implies an overlay; however, an error is issued
Subdirectories in the WIM are created as needed. Multiple source directories
may share the same target, which implies an overlay; however, an error is issued
Filenames containing whitespace may be quoted with either single quotes or
double quotes. Quotes may not be escaped.
Filenames containing whitespace may be quoted with either single quotes or
double quotes. Quotes may not be escaped.
The different capture modes only specify the data that is captured and don't
specify a special WIM format. A WIM file can contain images captured using
different modes. However, all images in a WIM must have the same compression
The different capture modes only specify the data that is captured and don't
specify a special WIM format. A WIM file can contain images captured using
different modes. However, all images in a WIM must have the same compression
stream chunk size of 32768. The only WIMs I've seen that are different from
this are some pre-Vista WIMs that had a different version number.
stream chunk size of 32768. The only WIMs I've seen that are different from
this are some pre-Vista WIMs that had a different version number.
mid-way through has a small chance of corrupting the WIM file. However, a
precaution is taken against this, so it should be very unlikely. In the event
mid-way through has a small chance of corrupting the WIM file. However, a
precaution is taken against this, so it should be very unlikely. In the event
extra data that may have been partially appended to the physical WIM file but
not yet incorporated into the structure of the WIM.
extra data that may have been partially appended to the physical WIM file but
not yet incorporated into the structure of the WIM.
git://wimlib.net / wimlib / blobdiff