Creating INF Files for Multiple Platforms and Operating Systems

By using system-defined platform extensions to INF file sections and directives, you can create a single INF file for cross-platform installations. The extensions enable you to create decorated section names, which specify which sections and directives are relevant to each target platform and operating system. For example, you can create an INF file that installs a device only on x64-based systems, only on Itanium-based systems, only on x86-based systems, or on all systems that are supported by Windows 2000 and later versions of Windows.

The following table summarizes the system-supported platform extensions that can be added to the names of sections that support extensions.

On Windows Server 2003 Service Pack 1 (SP1) and later, INF files must decorate entries in the INF Models section with .ntia64, .ntarm, .ntarm64 or .ntamd64 platform extensions to specify non-x86 target operating system versions. These platform extensions are not required in INF files for x86-based target operating system versions, but are strongly recommended. The same platform extension decoration or .nt platform extension is optional on all other sections that support platform extensions.

For sections that support optional platform extensions, Windows selects which section to process, as follows:

1. Windows checks for a section-name.nt<architecture> section and, if one exists, processes it. Windows checks for the .nt<architecture> extension in the INF file that is being processed and in any included INF files (that is, any INF files that are included with Include entries).

2. If a section-name.nt<architecture> section does not exist, Windows checks for a section-name.nt section in the INF file or any included INF files. If one exists, Windows processes the section-name.nt section.

3. If a section-name.nt section does not exist, Windows processes a section-name section that does not include a platform extension.

For sections where .nt and .nt<architecture> platform extensions are optional, the simplest approach to create and to maintain a cross-platform system INF file is not to use platform extensions on those section names and include the .nt<architecture> extension only on the names of INF Models section sections. However, this assumes that the INF file does not need to copy architecture specific versions of files and that install settings are the same across architectures. For more advanced scenarios for cross-platform INFs, see Combining Platform Extensions with Other Section Name Extensions.

To create such a simple cross-platform INF file, do the following:

1. Create a valid INF file that contains the generic entries that are required in all INF files, as described in General Guidelines for INF Files.

2. Include an INF Manufacturer section that includes a manufacturer-identifier that specifies the INF Models section name for the device and that specifies the .nt<architecture> platform extension. For example, the following Manufacturer section specifies an INF Models section name of "AbcModelSection" for an Abc device and the .nt<architecture> platform extension.

   [Manufacturer]
   ; The manufacturer-identifier for the Abc device.
   %ManufacturerName%=AbcModelSection,nt<architecture>
   

3. Include a Models.nt<architecture> section whose name matches the Models section name that is specified by the manufacturer-identifier in the Manufacturer section. For example, the following AbcModelSection.nt<architecture> section for an Abc device includes a device-description that specifies an install-section-name of "AbcInstallSection."

   [AbcModelSection.nt<architecture>]
   %AbcDeviceName%=AbcInstallSection,Abc-hw-id
   

4. Include a DDInstall section whose name matches the install-section-name that is specified by the Models section. For example, the device-description in an AbcModelSection section specifies the following AbcInstallSection section for an Abc device.

   [AbcInstallSection]
   ; Install section entries go here.
   ...
   

5. Include other device-specific sections that are required to install the device, but do not include an .nt<architecture> platform extension on names of these sections. For more information about INF file sections and directives, see Summary of INF Sections and Summary of INF Directives.

See also

• Cross-Platform INF Files
• Combining Platform Extensions with Other Section Name Extensions
• Combining Platform Extensions with Operating System Versions