Windows Driver Kit: Device Installation
INF SourceDisksFiles Section
[SourceDisksFiles] |
[SourceDisksFiles.x86] |
[SourceDisksFiles.ia64] | (Windows XP and later versions of Windows)
[SourceDisksFiles.amd64] (Windows XP and later versions of Windows)
filename = diskid[
,[
subdir][
, size]]
...
A SourceDisksFiles section names the source files used during installation, identifies the installation disks that contain those files, and provides the path to the subdirectories, if any, on the distribution disks containing individual files. In order for a driver file or an application file to be included as part of a signed driver package, the file must have a corresponding INF SourceDisksFiles section entry. Note that the file should also have a corresponding INF CopyFiles directive.
Do not use a SourceDisksFiles section to copy INF files. See Copying INFs.
Entries
- filename
- Specifies the name of the file on the source disk.
- diskid
- Specifies the integer identifying the source disk that contains the file. This value and the initial path to the subdir(ectory), if any, containing the named file must be defined in a SourceDisksNames section of the same INF.
- subdir
- This optional value specifies the subdirectory (relative to the SourceDisksNames path specification, if any) on the source disk where the named file resides.
If this value is omitted from an entry, the named source file is assumed to be in the path directory that was specified in the SourceDisksNames section for the given disk or, if no path directory was specified, in the installation root.
- size
- This optional value specifies the uncompressed size, in bytes, of the given file.
Comments
A SourceDisksFiles section can have any number of entries, one for each file on the distribution disks. Any INF with a SourceDisksFiles section also must have an INF SourceDisksNames section. By convention, SourceDisksNames and SourceDisksFiles sections follow the Version section. (These sections are omitted from a system-supplied INF, which instead specifies a LayoutFile entry in its Version section.)
To support distribution of driver files on multiple system architectures, you can specify an architecture-specific SourceDisksFiles section by adding an .x86, .ia64, or .amd64 extension to SourceDisksNames. Note that, unlike other sections such as a DDInstall section, the platform extensions for a SourceDisksFiles section are not .ntx86, .ntia64, or .ntamd64. For example, to specify a source disk names section for an x86-based system, use a SourceDisksFiles.x86 section, not a SourceDisksFiles.ntx86 section. Similarly, use a SourceDisksFiles.ia64 section to specify an Itanium-based system and a SourceDisksFiles.amd64 section to specify an x64-based system. During installation, SetupAPI functions look for architecture-specific SourceDisksFiles sections before using the generic section. For example, if, during installation on an x86-based platform, Setup is copying a file named driver.sys, it will look for the file's description in SourceDisksNames.x86 before looking in SourceDisksNames.
Example
The following example shows a
SourceDisksNames section and a corresponding
SourceDisksFiles section.
[SourceDisksNames]
;
; diskid = description[, [tagfile] [, <unused>, subdir]]
;
1 = %Floppy_Description%,,,\Win98
2 = %Floppy_Description%,,,\WinNT
[SourceDisksFiles]
;
; filename_on_source = diskID[, [subdir][, size]]
;
aha154x.mpd = 1,, ; on distribution disk 1, in subdir \win98
[SourceDisksFiles.x86]
aha154x.sys = 2,\x86 ; on distribution disk 2, in subdir \WinNT\x86
; ...
See Also
CopyFiles, DestinationDirs, RenFiles, SourceDisksNames, Version