INF File Platform Extensions and Itanium-Based Systems

The following table summarizes Windows support for platform extensions for Itaniums-based systems that run Windows XP and later.

Platform extensionPlatform extension support (Windows Server 2003 SP1 and later)Platform extension support (Windows Server 2003 and Windows XP )

.ntamd64

Not supported.

Not supported.

.ntia64

Required on INF Models section names. Optional on other sections that support extensions.

Recommended, but optional, on INF Models section names. Optional on other sections that support extensions.

.ntx86

Not supported.

Not supported.

.nt

Not supported on INF Models section names. Optional on other sections that support extensions.

Optional on sections that support extensions.

(No platform extension)

Not supported on INF Models section names. Optional on other sections that support extensions.

Supported by default on all sections.

 

For more information about how to use platform extensions with Itanium-based systems, see the following sections:

Platform Extensions and Itanium-Based Systems (Windows XP and later)

Creating INF Files for Itanium-Based Systems (Windows XP and Later)

Platform Extensions and Itanium-Based Systems (Windows XP and later)

On Windows Server 2003 SP1 and later, an .ntia64 platform extension is required on an INF Models section. An .ntia64 or .nt platform extension is optional on all other sections that support platform extensions.

On Windows Server 2003 and Windows XP, an .ntia64 platform extension is recommended, but optional on an INF Models section. An .ntia64 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.ntia64 section and, if one exists, processes it. Windows checks for the .ntia64 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.ntia64 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.

Creating INF Files for Itanium-Based Systems (Windows XP and Later)

In general, you cannot use a single INF file that differentiates between device installations that are based on the operating system version. For example, if the files or registry settings that support a device differ between versions of Itanium-based operating systems, you must create an operating system-specific INF file for each version.

However, if a device does not require operating system-specific installation, you can create a single cross-operating system INF file for Itanium-based systems that run Windows XP and later.

Because Windows Server 2003 SP1 and later require an .ntia64 platform extension on an INF Models section, but do not require this extension on other sections, the simplest approach to create and to maintain a cross-operating system INF file for Itanium-based systems is to include the .ntia64 extension only on Models section names.

To create such a cross-operating system 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 .ntia64 platform extension. For example, the following Manufacturer section specifies a Models section name of "AbcModelSection" for an Abc device and the .ntia64 platform extension.

    
    [Manufacturer]
    ; The manufacturer-identifier for the Abc device.
    %ManufacturerName%=AbcModelSection,ntia64
    
    
  3. Include a Models.ntia64 section whose name matches the INF Models section name that is specified by the manufacturer-identifier in the INF Manufacturer section. For example, the following AbcModelSection.ntia64 section for an Abc device includes a device-description that specifies an install-section-name of "AbcInstallSection."

    
    [AbcModelSection.ntia64]
    %AbcDeviceName%=AbcInstallSection,Abc-hw-id
    
    
  4. Include a DDInstall section whose name matches the install-section-name that is specified by the INF Models section. For example, the device-description in the 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 .ntia64 platform extension on the names of these sections. For more information about INF file sections and directives, see Summary of INF Sections and Summary of INF Directives.

For information about how to create a single cross-operating system INF for all platform types, see Cross-Platform INF Files.

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft