File Sequencing and How Files are Located

File Sequencing and How Files are Located

  • Comments 8

The File table in a Windows Installer package has a Sequence column that begins with 1. Besides determining in what order files are to be installed, this column serves another, relatively more important function: determining where the source files are located.

In concert with the Media table, a range of sequence numbers identify in which cabinet - if that range of files is even compressed - the files are located. The Media table has a column named LastSequence that is inclusive of the maximum sequence number of a particular file range. All files in the File table with a sequence number greater than the previous Media table entry's LastSequence and less than or equal to another Media table entry's LastSequence are contained in the latter media. To put that a little more plainly, see the following color-coded tables.

File table (partial)

File ... FileName ... Attributes Sequence
A_DLL ... a.dll ... 0 1
B_DLL ... b.dll ... 0 2
C_DLL ... c.dll ... 16384 3
D_DLL ... d.dll ... 16384 4

Media table

DiskId LastSequence DiskPrompt Cabinet VolumeLabel Source
1 2 Disk 1 AB.cab DISK1  
2 4 Disk 2 #CD.cab DISK2  

The files a.dll and b.dll may be compressed into AB.cab, while c.dll and d.dll will be compressed into CD.cab. CD.cab begins with a hash symbol (#) because, as documented for the Cabinet data type, that cabinet will be embedded as a stream within the .msi package. AB.cab would identify a cabinet in the root of the source tree specified in the Directory table.

You might also notice that I said the files a.dll and b.dll may be compressed into AB.cab because, depending on the Word Count, those files aren't explicitly attributed to be compressed. The Word Count Summary Property describes the default setting for whether files are compressed or uncompressed. As documented in Compressed and Uncompressed Sources, the Attributes column values of the File table override the Word Count property value. So, if the Word Count property specified that all sources were compressed then files a.dll and b.dll would be compressed into AB.cab; otherwise, if the Word Count property specified that all sources were uncompressed then only files c.dll and d.dll would be compressed into their respective cabinet.

Now, for example, b.dll needs to be patched. A patch must carry the new copy (or binary delta patch) of b.dll so it must change the file sequence of b.dll to match up with a new entry in the Media table to be added by one of the patch transforms for a particular product, as discussed in more detail in What's in a Patch. The transform beginning with a hash symbol (#) would make the following changes from the previous tables.

File table (partial)

File ... FileName ... Attributes Sequence
A_DLL ... a.dll ... 0 1
C_DLL ... c.dll ... 16384 3
D_DLL ... d.dll ... 16384 4
B_DLL ... b.dll ... 20480 5

Media table

DiskId LastSequence DiskPrompt Cabinet VolumeLabel Source
1 2 Disk 1 AB.cab DISK1  
2 4 Disk 2 #CD.cab DISK2  
3 5   #P1.cab   MspSrc3

PatchPackage table

PatchId Media_
{45F3433D-47C1-4AAF-9B4C-4FA759A02C0A} 3

Re-sequencing this file locates it in the the patch in the embedded stream named P1.cab. The attributes are changed to msidbFileAttributesPatchAdded (4096) + msidbFileAttributesCompressed (16384), the latter of which to override whatever the default Word Count is set for the .msi package being patched. The Word Count property value of the .msp file is used to identify the minimum version of Windows Installer required to install the patch and does not specify compression. Prior to Windows Installer 2.0 you had to guarauntee uniqueness of file sequence numbers for both the installer package for all patches, but starting with Windows Installer 2.0 you need only ensure that file sequences numbers are correct for a given package since Windows Installer 2.0 and newer will automatically adjust file sequence number as necessary.

When the transforms are applied from a patch and the files are re-sequenced, a reinstall of the affected features or all of the product is performed as documented in How Patching Works. The value in the Source column of the Media table for DiskId 3 is used to identify the location of the .msp file in order to locate the embedded cabinet.

Do note that the default schema of the File and Media tables allow for a maximum of 32,767 files including all changes made by any applicable patches. In the last set of tables, Windows Installer would view the product as now having 5 files. The reason is that the column data type is only a 2-byte signed integer. For more information about how to author a package with more initial files or to allow for many more patches, read Authoring a Large Package.

Leave a Comment
  • Please add 1 and 5 and type the answer here:
  • Post
  • Thanks!

    It helps me to make sure the patched/updated file would be re-sequenced automatically in the patch.

    Does this mean I need to reserve the file
    sequence numbers for those updated files, and allocate the follow-up numbers to the new added files in the patch?
  • Gary, beginning with MSI 2.0 file sequences from other patches can overlap. MSI will automatically fix-up sequences per-patch when installed. You cannot, however, overlap file sequences in the product package - only patches.

    See the comments for the FileSequenceStart column of the ImageFamilies table (found in a .pcp file for creating a patch) at http://msdn.microsoft.com/library/en-us/msi/setup/imagefamilies_table_patchwiz_dll_.asp.
  • Now that Visual Studio 2005 Service Pack 1 is released, some are wondering how to slipstream the patch

  • When installing Visual Studio 2005 Service Pack 1 , there are a number of errors that might occur due

  • When installing Visual Studio 2005 Service Pack 1 , there are a number of errors that might occur due

  • File versions in Windows Installer and properties like REINSTALL and REINSTALLMODE determine what files

  • File versions in Windows Installer and properties like REINSTALL and REINSTALLMODE determine what files

  • When installing a patch package , Windows Installer first determines if the patch is applicable. Depending

Page 1 of 1 (8 items)