- Intel Itanium
- Advanced Micro Devices (AMD) AMD64 processors and Intel Extended Memory 64 Technology (EM64T)
Note The .NTamd64 decoration in the following .inf file excerpt is used for all AMD64 or EM64T platforms. Conversely, the .NTia64 decoration is used for Intel Itanium platforms.
%mycompany% = MyCompanyModels, NTamd64
%MyDev% = mydevInstall, mydevHwid
Decorations and installation behaviorThe following table describes the Microsoft Windows operating system installation behaviors for decorated and undecorated .inf files:
|Undecorated||Decorated for x86||Decorated for Itanium||Decorated for x64|
|Microsoft Windows 2000 x86-based||I||NI||n/a||n/a|
|Microsoft Windows XP x86-based||I||I||NI||n/a|
|Windows Server 2003 SP1 x86-based||I||I||NI||NI|
|Windows Server 2003 SP1 Itanium-based||I/NI*||NI||I||NI|
|Windows Server 2003 SP1 x64-based||NI||NI||NI||I|
Decorations and installation behavior notes(I) Device models that are within the corresponding .inf file are found, and are matched for potential installation.
(NI) Device models that are within the corresponding .inf file are not found, and installation does not occur.
(*) Undecorated .inf files for Itanium-based platforms are allowed for packages with a DriverVer date that is before the date that is defined in Windows Server 2003 x64 editions. This is to avoid problems that may be caused by device driver packages that are developed before the date that is defined in Windows Server 2003 x64 editions.
Device driver .inf files that are used for multiple platformsDevice driver .inf files support the following multiple platform configurations:
- Decorated sections for x64 and Itanium-based platforms.
- Undecorated or decorated sections for x86-based platforms.
The following two methods are supported with device driver packages for multiple platforms:
- Method 1: Provide an individual .inf file for each operating system.
- Method 2: Provide a single multiple-platform .inf file for all supported platforms.
The following example shows a multiple platform .inf file:
%mycompany% = MyCompanyModels, NTx86, NTia64
%MyDev% = mydevInstallx86, mydevHwid
%MyDev% = mydevInstallia64, mydevHwid
Backward compatibility with Windows Server 2003 for Itanium-based platformsWindows compares the DriverVer date of an .inf file to determine whether a decorated [Models] section is required. For backward compatibility purposes with Itanium-based platforms, Windows Server 2003 x64 editions do not enforce .inf decorations for device drivers if the DriverVer date is earlier than the date that is defined in Windows Server 2003 x64 editions.
The enforcement date is maintained in the following registry subkey:
|0-4||Day. The day of the month, 1-31.|
|5-8||Month. 1 represents January, 2 represents February, and so on.|
|9-15||Year. The year is offset from 1980. Add 1980 to obtain the current year.|
Technical support for x64-based versions of Microsoft WindowsIf your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you must have technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server 2003 x64 edition separately, contact Microsoft for technical support.
For product information about Windows XP Professional x64 Edition, visit the following Microsoft Web site:
Article ID: 888728 - Last Review: Jun 18, 2008 - Revision: 1