************************************************************ * Product: Intel(R) Chipset Device Software * Release: Production Version * Version: 9.2.0.

1025 * Target Products: Intel(R) 6 Series/C200 Series Chipset Family * 2nd generation Intel(R) Core(TM) processor family * Date: February 28 2011 ************************************************************ NOTE: For the list of supported chipsets, please refer to the Release Notes ************************************************************ * CONTENTS OF THIS DOCUMENT ************************************************************ This document contains the following sections: 1. 2. 3. 4. 5. 6. 7. 8. Overview System Requirements Contents of the Distribution Package List of Available Command Line Flag Options Contents of the Extracted Files Installing the Software in Interactive Mode Installing the Software in Silent Mode Installing the INF Files Prior to OS Installation 8A. Installing the Windows* 2000 INF Files Prior to OS Installation 8B. Installing the Windows* XP INF Files Prior to OS Installation 8C. Installing the Windows Server* 2003 INF Files Prior to OS Installation 8D. Installing the Windows* Vista INF Files Prior to OS Installation 8E. Installing the Windows Server* 2008 INF files Prior to OS Installation 8F. Installing the Windows Server* 2008 R2 INF files Prior to OS Installation 8G. Installing the Windows 7 INF files Prior to OS Installation 9. Installing the INF Files After OS Installation 9A. Installing the Windows* 2000 INF Files After OS Installation 9B. Installing the Windows* XP INF Files After OS Installation 9C. Installing the Windows Server* 2003 INF Files After OS Installation 9D. Installing the WINDOWS VISTA INF FILES AFTER OS Installation 9E. Installing the Windows Server* 2008 INF FILES AFTER OS Installation 9F. Installing the Windows Server* 2008 R2 INF FILES After OS Installation 9G. Installing the Windows 7 INF FILES AFTER OS Installation 10. Verifying Installation of the Software and Identifying the Software Version Number 11. Troubleshooting

************************************************************ * 1. OVERVIEW ************************************************************ The Intel(R) Chipset Device Software installs Windows* INF files to the target system. These files outline to the operating system how to configure the Intel(R) chipset components in order to ensure that the following features function properly: Core PCI and ISAPNP Services PCIe Support IDE/ATA33/ATA66/ATA100 Storage Support SATA Storage Support USB Support Identification of Intel(R) Chipset Components in the Device Manager

This software can be installed in three modes: Interactive, Silent and Unattended Preload. Interactive Mode requires user input during installation; Silent Mode and Unattended Preload do not. This software also offers a set of command line flags, which provide additional installation choices. The command line flags are not case sensitive. Refer to Section 4 for detailed descriptions of these flags. Important Note: The Intel(R) Chipset Device Software is distributed in two formats: self extracting .EXE files (INFINST_AUTOL.EXE) or compressed .ZIP files (INFINST_AUTOL.ZIP). Depending on which distribution format is being executed, the commandline syntax may differ. Refer to Section 4 for more details. ************************************************************ * 2. SYSTEM REQUIREMENTS ************************************************************ 1. Please refer to the Release Notes to view the list of chipsets that the software included with this distribution package is designed to operate with. 2. One of the following operating systems must be fully installed and running on the system before installing this software: Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Windows* Server 2003 Windows Server 2003 x64 Edition* Windows Server 2008 Windows Server 2008 x64 Windows XP Windows XP Professional x64 Windows 2000 Windows Vista Windows Vista x64 Windows 7 Windows 7 x64 Windows 2008 R2 Windows 2008 R2 x64

This software is designed for the latest Service packs releases of above operating systems. To verify which operating system has been installed onto the target system, follow the steps below: a. b. c. d. e. f. Click on Start. Select Settings. Select Control Panel. Double-click on the System icon. Click on the General system properties tab. Verify which OS has been installed by reading the System information.

3. It is recommended that the software be installed on systems with at least 64MB of system memory when using Windows* 2000, Windows* XP, Windows Server* 2003, Windows Server* 2008, and Windows* Vista. 4. It is recommended that there be a minimum of 5MB of hard disk space on the system in order to install this software. 5. The operating system must be fully installed and running on the system before running this software. 6. Close any running applications to avoid installation problems. 7. It is recommended that the Intel(R) Chipset Device Software be installed onto the target system prior to the installation of other drivers. Please check with the system provider to determine which operating system and Intel(R) chipset are used in the system. ************************************************************ * 3. CONTENTS OF THE DISTRIBUTION PACKAGE ************************************************************ The Intel(R) Chipset Device Software package contains the following items: File(s) ------INFINST_AUTOL.EXE -or- INFINST_AUTOL.ZIP README.TXT, RELEASE_xxx.HTM *** NOTE: Only the files that reference the currently detected devices are copied to the system. If the -A option is exercised, the files are not copied to the <Windows>\INF directory. Refer to Section 4 for more information. ************************************************************ * 4. LIST OF AVAILABLE COMMAND LINE FLAG OPTIONS ************************************************************ The Intel(R) Chipset Device Software supports several command line flags for various installation options.

Note that the '-L' and the '-S' flags MUST be specified at the end of the command line flag list. -A Extracts the INF files and Readme to either "C:\Program Files\Intel\InfInst" or the <Installation Path> directory specified using the '-P' flag. This flag works in Interactive Mode only. This flag is ignored if '-A' flag is specified. This flag works in Interactive Mode only. This flag works in Interactive Mode only. This flag works in Interactive Mode only. -F2 <path\filename> Specifies an alternate location and name of the log file created by InstallShield Silent. '-AONLY' will not return any INFs when used in conjunction with '-OVERALL' switch. -B Automatically reboots the system after installation. This flag works in either Silent Mode or Interactive Mode. -OVERWRITE Ignores the overwrite warning dialog when . all the needed INFs for the system will be extracted. 'Path' indicates the directory path where installation status is logged in file 'filename'. This option is used for silent installation from a CD. -OVERALL Updates ALL INF drivers on all available devices even if third party drivers are currently installed. -OVERIDE Updates the storage drivers even if a third party storage driver is currently installed. Flag ----? Description ----------Displays the list of available command line flags. This flag can be combined only with the '-P' flag. This flag works in Interactive Mode only.Below is a list of all the available command line flags that may be used with the program call. -L <number> Specifies the language of the setup dialogs. If the install has been run once successfully. -AONLY Extracts the needed INF files to install on the current system. The software will NOT install these INF files to the system. All other options will be ignored if the '-A' flag is specified.

CONTENTS OF THE EXTRACTED FILES ************************************************************ INF files are copied to the hard disk after running the . If this flag is not specified at the command line. but then a pair of double quotes (") must enclose the directory name. This flag and the '-L' flag must be placed at the end of the command line flag list.installing an older version of the software. only the Readme will be copied to <Installation Path>. -S Runs the Installer in Silent Mode (no user interface is displayed). -P<Installation Path> Specifies the hard disk location to which the INF program files are copied. The directory name can include spaces. There should not be any space between the switch '-p' and the directory name. the <Installation Path> directory is as follows: C:\Program Files\Intel\INFInst If this flag is used without the '-A' option. Below are the language codes used with the '-L' flag: <number> -------0401 0804 0404 0405 0406 0413 0409 040B 040C 0407 0408 040D 040E 0410 0411 0412 0414 0415 0416 0816 0419 040A 041D 041E 041F Language ---------Arabic (International) Chinese (Simplified) Chinese (Traditional) Czech Danish Dutch English (United States) Finnish French (International) German Greek Hebrew Hungarian Italian Japanese Korean Norwegian Polish Portuguese (Brazil) Portuguese (Standard) Russian Spanish (International) Swedish Thai Turkish ************************************************************ * 5. This flag works in either Silent Mode or Interactive Mode.

Run the InstallShield* installation program: Self-extracting . then the INF files are copied to the following directory: "C:\Program Files\Intel\INFINST" 2. You will be prompted to agree to the license agreement.TXT makes a CUSTOM.EXE 3. follow the on-screen instructions and accept default settings to complete the . The directories are classified according to the following: All\ Contains INF files designed for Windows* 2000.EXE Compressed .) ************************************************************ * 6. 4. Once the operating system reboots. The following table summarizes the locations of the INF files by operating system: NOTE: "<INF Extract Directory>" is abbreviated "<IED>" in the remainder of this section.. OEMs can incorporate this file into the Setup directory for the OEM Preload Kit. Verify that all system requirements have been met as described in Section 2 above. If you do not agree. Refer to Section 4 for more information on flag usage. Windows Server* 2008. These files and components are categorized according to the operating system. (Refer to Section 8 for more details.EXE -A"). Windows Server* 2003. the INF files and components are copied to the <INF Extract Directory>. If a '-P' flag is specified. Windows* XP. 2. INSTALLING THE SOFTWARE IN INTERACTIVE MODE ************************************************************ 1.EXE -A" or "SETUP.INF template that installs the INF files for Intel(R) chipsets during operating system setup.ZIP distribution: SETUP. the installation program will exit before extracting any files.e. and Windows* Vista Win7\ Contains INF files designed for Windows* 7 and Windows Server* 2008 R2 NOTE: INFAnswr.EXE distribution: INFINST_AUTOL. then the INF files are copied to the location listed immediately after the '-P' flag. "INFINST_AUTOL. After INF file extraction. If a '-P' flag is not specified. The location of the INF files depends on whether a '-P' flag is specified along with the '-A' flag: 1.Intel(R) Chipset Device Software executable with an '-A' flag (i.

verify the "install" value in the registry key specified in Step 3.txt. the system will automatically reboot if the update was successful. If the utility was invoked with the "-b" flag. 2. Data: "No" . Verify that all system requirements have been met as described in section 2. To determine whether the install was successful. When using Silent Mode the license agreement.EXE -b -s . In Silent Mode the utility will not display the license agreement.setup.EXE -s 3. The following describes the various parameters: Name: "install" Type: String Data: "success" The installation was successful. No INF files were copied to the system. Please read this agreement.EXE -b -s Compressed . will be placed in the following folder: Program Files/Intel/INFInst folder.EXE distribution: INFINST_AUTOL.or For silent install without auto-reboot: Self-extracting . NOTE: The system MUST be rebooted for all device updates to take effect. ************************************************************ * 7. INSTALLING THE SOFTWARE IN SILENT MODE ************************************************************ 1.EXE -s Compressed . license. Data: "fail" The installation was not successful.ZIP distribution: SETUP. 6. Run the InstallShield* installation program: For silent install with auto-reboot: Self-extracting . The utility will perform the necessary updates and record the installation status in the following system registry key: HKEY_LOCAL_MACHINE\Software\Intel\INFInst 4. Name: "reboot" Type: String Data: "Yes" A reboot is required to complete the installation.ZIP distribution: SETUP. 5.EXE distribution: INFINST_AUTOL.

\I386\). Refer to Section 8 for more details.EXE and WINNT32. 3. 1.No reboot is required to complete the installation.CAT) from <INF Extract Directory>\XXXX\All to the directory created in Step 4 above: . Create the following directory structure under the <WIN2000 Setup Directory>: \$OEM$\$$\INF 2. INSTALLING THE WINDOWS* 2000 INF FILES PRIOR TO * OS INSTALLATION ************************************************************ NOTE: The Windows* 2000 OEM Preload Kit distribution CD contains a setup directory with all the base operating system setup files and installation programs (WINNT. It is important to make sure there is enough disk space before beginning the copy process. The name of the directory may vary depending on the distribution CD (e. Copy the Windows* 2000 INF files and the catalog files (. Name: "version" Type: String Data: <varies> Current version number of the Intel(R) Chipset Device Software ************************************************************ * 8. The directories shall be referred to as follows: Windows* 2000 : <WIN2000 Setup Directory> Windows XP : <WINXP Setup Directory> Windows Server* 2003 : <WIN2003 Setup Directory> ************************************************************ * 8A. and selecting 'Properties'.EXE). INSTALLING THE INF FILES PRIOR TO OS INSTALLATION ************************************************************ This procedure requires a minimum of 5MB of hard disk space.. right-clicking on the correct drive. Create the following directory structure under the <WIN2000 Setup Directory>: \$OEM$\$1\drivers\IntelINF 4.g. Copy the Windows* 2000 INF files from <INF Extract Directory>\XXXX\All to the directory created in Step 1 above: <WIN2000 Setup Directory>\$OEM$\$$\INF NOTE: XXXX is the directory name for the chipset of interest. This can be done by opening 'My Computer'. Copy the operating system installation files from the setup directory to a directory on the hard disk.

<WIN2000 Setup Directory>\$OEM$\$1\drivers\IntelINF NOTE: XXXX is the directory name for the chipset of interest. Run "WINNT.EXE).TXT. Copy the Windows* XP INF files from <INF Extract Directory>\XXXX\All to the directory created in Step 1 above: <WINXP Setup Directory>\$OEM$\$$\INF NOTE: XXXX is the directory name for the chipset of interest.. 5. \I386\). ************************************************************ * 8B. Refer to Section 8 for more details. refer to the Microsoft Windows* 2000 OEM Preinstallation Kit (OPK) User Guide for more information about the \$OEM$ folder. Otherwise. The answer file must include the following information: [Unattended] OemPreinstall = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Device Software files is available at: <INF Extract Directory>\XXXX\All\INFAnswr. UNATTEND.TXT For more information about Windows* 2000 answer files and unattended installations. 6.EXE /u:<answer file name> /s:<WIN2000 Setup Directory>" to install Windows* 2000. INSTALLING THE WINDOWS* XP INF FILES PRIOR TO * OS INSTALLATION ************************************************************ NOTE: The Windows* XP OEM Preload Kit distribution CD contains a setup directory with all the base operating system setup files and installation programs (WINNT. If you are a computer manufacturer. refer to the Microsoft Windows* 2000 Deployment Guide. Either modify the default Windows* 2000 installation answer file. located in <All Setup Directory>. Create the following directory structure under the <WINXP Setup Directory>: .g. 3. or create a customized answer file. please refer to the Microsoft* Windows* 2000 Guide to Unattended Setup.EXE and WINNT32. Create the following directory structure under the <WINXP Setup Directory>: \$OEM$\$$\INF 2. The name of the directory may vary depending on the distribution CD (e. Refer to Section 8 for more details. 1.

5. If you are not a manufacturer. For more information about the \$OEM$ folder. INSTALLING THE WINDOWS SERVER* 2003 INF FILES PRIOR * TO OS INSTALLATION ************************************************************ NOTE: The Windows Server* 2003 OEM Preload Kit distribution CD contains a setup directory with all the base operating system setup files and installation programs (WINNT. Copy the Windows Server* 2003 INF files from <INF Extract Directory>\XXXX\All to the directory created in Step 1 above: <WIN2003 Setup Directory>\$OEM$\$$\INF . Either modify the default Windows* XP installation answer file..EXE and WINNT32. 1.g. 6.\$OEM$\$1\drivers\IntelINF 4. or create a customized answer file. refer to the Microsoft Windows* XP OEM Preinstallation Kit (OPK) User Guide. Refer to Section 8 for more details. Create the following directory structure under the <WIN2003 Setup Directory>: \$OEM$\$$\INF 2. The name of the directory may vary depending on the distribution CD (e.TXT If you are a computer manufacturer. refer to the Microsoft* Windows* XP Guide to Unattended Setup for more information about Windows* XP answer files and unattended installations. located in <WINXP Setup Directory>. Run "WINNT. The answer file must include the following information: [Unattended] OemPreinstall = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Device Software files is available: <INF Extract Directory>\XXXX\All\INFAnswr. ************************************************************ * 8C. \I386\). Copy the Windows* XP INF files AND the catalog files (.CAT) from <INF Extract Directory>\XXXX\All to the directory created in Step 4 above: <WINXP Setup Directory>\$OEM$\$1\drivers\IntelINF NOTE: XXXX is the directory name for the chipset of interest.EXE).TXT. UNATTEND. refer to the Microsoft Windows* XP Deployment Guide.EXE /u:<answer file name> /s:<WINXP Setup Directory>" to install Windows* XP.

Create the following directory structure under the <WIN2003 Setup Directory>: \$OEM$\$1\drivers\IntelINF 4. Microsoft* published a Wndows Automated Installation Kit(WAIK) which facilitates creation of answer files and image creation for unattended installs of Windows Vista To add drivers to an offline Windows image 1. 5. it is no longer the preferred method. Either modify the default Windows Server* 2003 installation answer file. Refer to Section 8 for more details. Locate the device driver . refer to the Microsoft Windows Server* 2003 Deployment Guide. located in <WIN2000 Setup Directory>. The answer file must include the following information: [Unattended] OemPreinstall = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Device Software files is available: <INF Extract Directory>\XXXX\All\INFAnswr. Run "WINNT.EXE /u:<answer file name> /s:<WIN2003 Setup Directory>" to install Windows* 2000.CAT) from <INF Extract Directory>\XXXX\All to the directory created in Step 3 above: <WIN2003 Setup Directory>\$OEM$\$1\drivers\IntelINF NOTE: XXXX is the directory name for the chipset of interest. 2. ************************************************************ * 8D. Use Windows System Image Manager (Windows SIM) to create . If you are a computer manufacturer. 3. refer to the Microsoft Windows Server* 2003 OEM Preinstallation Kit (OPK) User Guide for more information about the \$OEM$ folder.inf files that you intend to install on your Windows image.TXT. Otherwise. Copy the Windows Server* 2003 INF files and the catalog files (. INSTALLING THE WINDOWS* VISTA INF FILES PRIOR * TO OS INSTALLATION ************************************************************ NOTE: Although $OEM$ method is still supported. Refer to Section 8 for more details.NOTE: XXXX is the directory name for the chipset of interest.TXT For more information about Windows Server* 2003 answer files and unattended installations. UNATTEND. 6. please refer to the Microsoft Windows Server* 2003 Guide to Unattended Setup. or create a customized answer file.

Expand the Microsoft-Windows-PnpCustomizationsNonWinPE node in the answer file.an answer file that contains the paths to the device drivers that you intend to install. Add the Microsoft-Windows-PnpCustomizationsNonWinPE component to your answer file in the offlineServicing pass. For example: imagex /mountrw C:\windows_distribution\sources\install.log file during the driver package injection. Mount the Windows image that you intend to install the drivers to by using ImageX. Enable logging of specific device driver injection actions in a separate log file. <?xml version="1. The answer file must be similar to the following sample. Right-click DevicePaths.com/WMIConfig/2002/State"> <settings pass="offlineServicing"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArc hitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScop e="nonSxS"> <DriverPaths> <PathAndCredentials wcm:keyValue="1"> <Path>\\networkshare\share\drivers</Path> <Credentials> <Domain>Fabrikam</Domain> <Username>MyUserName</Username> <Password>MyPassword</Password> </Credentials> </PathAndCredentials> </DriverPaths> </component> </settings> </unattend> 7.wim 1 C:\wim_mount 8. 9. 5. specify the path to the device driver and the credentials used to access the file if the file is on a network share. Save the answer file and exit Windows SIM. 3. 6. Use Package Manager to apply the unattended installation answer .mic rosoft. 4. In the Microsoft-Windows-PnpCustomizationsNonWinPE component.0" ?> <unattend xmlns="urn:schemas-microsoft-com:asm.v3" xmlns:wcm="http://schemas. This lo g file will log all actions of the driver injection process. and then select Insert New PathAndCredentials. Edit the following registry key on the computer on which you are running Package Manager: Path: HKLM\Software\Microsoft\Windows\CurrentVersion\Device Installer Key: DebugPkgMgr Type: REG_DWORD Value: 0x01 This will create a Drivers.

inf. and then select Insert New PathAndCredentials. please refer to the Windows Automated Installation Kit (WAIK) User's Guide. This is to ensure unique naming for new drivers added to the computer. it is no longer the preferred method. INSTALLING THE WINDOWS SERVER* 2008 INF FILES PRIOR * TO OS INSTALLATION ************************************************************ NOTE: Although $OEM$ method is still supported. The . pkgmgr /o:"C:\wim_mount\.inf files referenced in the path in the answer file are added to the Windows image. Expand the Microsoft-Windows-PnpCustomizationsNonWinPE node in the answer file. Microsoft* published a Wndows Automated Installation Kit(WAIK) which facilitates creation of answer files and image creation for unattended installs of Windows Server 2008 To add drivers to an offline Windows image 1. 2.inf are renamed oem0. Specify a location for the log file to create. 5. You can open the Drivers. ************************************************************ * 8E. 11. For example. For example. Review the contents of the %WINDIR%\Inf\ directory in the mounted Windows image to ensure that the .C:\wim_mount\Windows" /n:"C:\unattend. A log file is created in the directory C:\Pkgmgrlogs\. Drivers added to the Windows image are named oem*. see Package Manager Comman d-Line Options. specify the path to the device driver and the credentials used .inf files that you intend to install on your Windows image.wim file and commit the changes.inf.inf and MyDriver2. 10.file to the mounted Windows image. The Windows image is ready to be deployed. 4. imagex /unmount /commit C:\wim_mount 12.txt" For more information about using Package Manager. the files MyDriver1. 3.xml" /l:"C:\pkgmg rlogs\logfile. Unmount the .inf and oem1. Use Windows System Image Manager (Windows SIM) to create an answer file that contains the paths to the device drivers that you intend to install. In the Microsoft-Windows-PnpCustomizationsNonWinPE component.inf files were installed. Add the Microsoft-Windows-PnpCustomizationsNonWinPE component to your answer file in the offlineServicing pass. Locate the device driver .log file and review the Package Manager driver injection actions. Driver log files are created in the directory that PkgMgr runs from. For example. For more information about Windows Vista answer files and unattended installations. Right-click DevicePaths.

The .xml" /l:"C:\pkgmg rlogs\logfile. You can open the Drivers.log file and review the .wim 1 C:\wim_mount 8.0" ?> <unattend xmlns="urn:schemas-microsoft-com:asm.v3" xmlns:wcm="http://schemas. <?xml version="1. Edit the following registry key on the computer on which you are running Package Manager: Path: HKLM\Software\Microsoft\Windows\CurrentVersion\Device Installer Key: DebugPkgMgr Type: REG_DWORD Value: 0x01 This will create a Drivers. 9.to access the file if the file is on a network share. Enable logging of specific device driver injection actions in a separate log file. This lo g file will log all actions of the driver injection process. For example. For example: imagex /mountrw C:\windows_distribution\sources\install. Specify a location for the log file to create. Save the answer file and exit Windows SIM. Mount the Windows image that you intend to install the drivers to by using ImageX.C:\wim_mount\Windows" /n:"C:\unattend. 6.mic rosoft. A log file is created in the directory C:\Pkgmgrlogs\. The answer file must be similar to the following sample. Driver log files are created in the directory that PkgMgr runs from. see Package Manager Comman d-Line Options. Use Package Manager to apply the unattended installation answer file to the mounted Windows image.log file during the driver package injection.txt" For more information about using Package Manager.inf files referenced in the path in the answer file are added to the Windows image. pkgmgr /o:"C:\wim_mount\.com/WMIConfig/2002/State"> <settings pass="offlineServicing"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArc hitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScop e="nonSxS"> <DriverPaths> <PathAndCredentials wcm:keyValue="1"> <Path>\\networkshare\share\drivers</Path> <Credentials> <Domain>Fabrikam</Domain> <Username>MyUserName</Username> <Password>MyPassword</Password> </Credentials> </PathAndCredentials> </DriverPaths> </component> </settings> </unattend> 7.

1. Autounattend. the files MyDriver1. For example. INSTALLING THE WINDOWS 7* INF FILES PRIOR * TO OS INSTALLATION ************************************************************ The simplest method for installing Windows? onto new hardware is to start directly from the Windows product DVD with an answer file called Autounattend. Unmount the .xml.wim file and commit the changes. For more information about Windows Server 2008 answer files and unattended installations. Microsoft* published a Wndows Automated Installation Kit(WAIK) (Must be the windows 7 version) which facilitates creation of answer files and image creation for unattended installs of Windows 7 with tools such as Windo ws SIM To create a configuration set you will need: Windows System Image Manager (Windows SIM) installed on a technician com puter. click Start. By default.inf are renamed oem0. 10.) A.Package Manager driver injection actions. Drivers added to the Windows image are named oem*. Create a New Answer File (In this step.xml must be located at the root of the removable media. ************************************************************ * 8F. point . you define basic disk configuration and other settings that are r equired for an unattended installation. On your technician computer. 11. Access to a network share or removable media with sufficient storage spa ce.inf and oem1. B. imagex /unmount /commit C:\wim_mount 12. Windows Setup searches all removable media for an answer file called Autounattend. Boot the computer with the Windows Setup media in the DVD drive and the configuration set available on an external drive.inf files were installed. The answer file enables you to automate all or parts of Windows Setup Includeing adding INF files. Copy the Install. insert the Windows 7 product DVD into th e local DVD-ROM drive. This is to ensure unique naming for new drivers added to the computer. On the desktop of the technician computer.inf. navigate to the \Sources d irectory on your DVD-ROM drive.inf. please refer to the Windows Automated Installation Kit (WAIK) User's Guide. For example.inf and MyDriver2. You can create an answer file by using Windows System Image Manager (Windows SIM). On the desktop of the computer. An authorized copy of a Windows Vista? product DVD.wim file from the Windows pro duct DVD to a location on the computer. The Windows image is ready to be deployed. Chipset device driver . C.inf files.xml. Open Windows SIM. Review the contents of the %WINDIR%\Inf\ directory in the mounted Windows image to ensure that the .

and then click Pass 1 windowsPE. In Windows SIM. Create subdirectories for each driver. you ar e prompted to select the Windows image to open. point to Microsoft Windows OPK (or Windows AIK). you add an out-of-box drivers (. In the Select a Windows Image dialog box. on the Tools menu. If the answer file validates successfully. click Tools. otherwise. and then c lick Windows System Image Manager. and then click Open.) A.wim file. B. you create a distribution-share folder on your technician compute r. Validate the Answer File (In this step. D. F. C. In the Distribution Share pane. and then click Validate Answer File. applications.clg file. C. in the Distribution Share pane.) A.to Programs. navigate to the location wh ere you saved the Install. On the File menu. "C:\MyDistributionShare\Out-of-Box Drivers\Chipset" 5. B. Select the driver path to add to the answer file. double-click the error to n avigate . The Create a Distribution Share dialog box appears. on the Insert menu. and then type a name for the folder.inf) to the Out-of-Box Drivers folder . Click New Folder. For example "C:\MyDistributionShareClick" E. The distribution share will store out-of-box drivers. C. If there is more than one Windows image in the .) A. C. The Browse for Folder dialog box appears. you validate the settings in your answer file and then save them to a file. Right-click to select Create Distribution Share. Create a Distribution Share (In this step. E. C:\MyDistributionShare\$OEM$ Folders C:\MyDistributionShare\Packages C:\MyDistributionShare\Out-of-Box 3. In Windows SIM. 4. error messages appear in the same location. and any reso urce files needed for your custom installation.inf) path to your answer file. in the Messages pane. Note: A warning will appear that a . D. click Select a Distri bution Share. Windows SIM automatically creates the following folder structure. and then click OK. Copy your device driver files (.clg file does not exist. If an error occurs. 1. 2. click Select Windows Image. For example. click New Answer File. The Distribution Share window opens. a "success" message appear s in the Messages pane. create directories "Chipset" and "Video" in the Out-of-Box Dr ivers folder. On the File menu. Close the distribution share folder. D. In Windows SIM. click Driver Path. Click OK to create a . For example. the distribution share folder opens. select Explore Distribution Share.wim file. B. B. Add a Device Driver to the Answer File (In this step. Add Drivers and Applications to Distribution Share A. In Windows SIM.

Turn on the new computer.) A. F. Microsoft* published a Wndows Automated Installation Kit(WAIK) (Must be the Windows Server 2008 R2* version) which facilitates creation of ans wer files . 7. Create a Configuration Set (In this step. Autounattend. insert the drive directly in to the primary set of USB ports for the computer. and then reseal the computer by using the generalize option For more information about Windows Server 2008 answer files and unattended installations. Note: This example assumes that the hard drive is blank.exe) begins automatically.x ml. ************************************************************ * 8G. After Setup completes. E. You can create an answer file by using Windows System Image Manager (Windows SIM). B. you create a configuration set that will gather all of the resour ce files that you specified in your answer file into one location.xml.xml. D. please refer to the Windows Automated Installation Kit (WAIK) User's Guide. By default. validate that all customizations were applied. Select a removable dirve such as a USB flash drive (UFD). C. The answer file enables you to automate all or parts of Windows Setup Includeing adding INF files. Specify a destination location where you intend to publish the config uration set D.to the incorrect setting. 6. Boot the computer with the Windows Setup media in the DVD drive and the configuration set available on an external drive. B. Save the file as Unattend. On the File menu. Note: When using a USB flash drive. By default. Deploying a Configuration Set Without a Network A.xml must be located at the root of the removable media. and then cl ick OK. C. INSTALLING THE Windows Server 2008 R2* INF FILES PRIOR * TO OS INSTALLATION ************************************************************ The simplest method for installing Windows? onto new hardware is to start directly from the Windows product DVD with an answer file called Autounattend. Change the setting to fix the error. Windows Setup searches all removable media for an answer file called Autounattend. Autounattend. click Save Answer File. For a desktop c omputer. In Windows SIM.xml must be located at the root of the removable media.xml. this is typically in the back of the computer. Restart the computer by pressing CTRL+ALT+DEL. Windows Setup searches all removable media for an answer file called Autounattend. and th en revalidate the answer file. Insert both the removable media containing your configuration set and the Windows 7 product DVD into the new computer. The Create Configuration Set window opens. on the Tools menu. Windows Setup (Setup. select Create Configuration Set. G.

wim file from the Windows pro duct DVD to a location on the computer. B. B. Click New Folder. and then c lick Windows System Image Manager. the distribution share folder opens. Windows SIM automatically creates the following folder structure. C. B. click Start. select Explore Distribution Share.and image creation for unattended installs of Windows Server 2008 R2* with tool s such as Windows SIM To create a configuration set you will need: Windows System Image Manager (Windows SIM) installed on a technician com puter. click Select a Distri bution Share. On the desktop of the computer. click New Answer File. Create a New Answer File (In this step. Note: A warning will appear that a . Add Drivers and Applications to Distribution Share A. insert the Windows Server 2008 R2* prod uct DVD into the local DVD-ROM drive. applications. On the desktop of the technician computer. Access to a network share or removable media with sufficient storage spa ce. An authorized copy of a Windows Vista? product DVD. The Create a Distribution Share dialog box appears. For example "C:\MyDistributionShareClick" E.clg file. On your technician computer. D. navigate to the \Sources d irectory on your DVD-ROM drive.) A. click Select Windows Image. Create a Distribution Share (In this step.) A. If there is more than one Windows image in the . Right-click to select Create Distribution Share. Click OK to create a . On the File menu. navigate to the location wh ere you saved the Install. D. Open Windows SIM. you define basic disk configuration and other settings that are r equired for an unattended installation. In Windows SIM. point to Microsoft Windows OPK (or Windows AIK). Copy the Install. On the File menu. In the Select a Windows Image dialog box. and then type a name for the folder. The distribution share will store out-of-box drivers. F.wim file. you create a distribution-share folder on your technician compute r. and then click Open. In Windows SIM. 1. C. on the Tools menu. Chipset device driver . you ar e prompted to select the Windows image to open.inf files. point to Programs. E.wim file.clg file does not exist. C:\MyDistributionShare\$OEM$ Folders C:\MyDistributionShare\Packages C:\MyDistributionShare\Out-of-Box 3. 2. in the Distribution Share pane. In the Distribution Share pane. . The Distribution Share window opens. and any reso urce files needed for your custom installation.

select Create Configuration Set. and then cl ick OK.exe) begins automatically.) A. E. this is typically in the back of the computer. In Windows SIM. you validate the settings in your answer file and then save them to a file. F. Save the file as Unattend. C. C. "C:\MyDistributionShare\Out-of-Box Drivers\Chipset" 5. The Create Configuration Set window opens. 6. a "success" message appear s in the Messages pane. For a desktop c omputer. you create a configuration set that will gather all of the resour ce files that you specified in your answer file into one location. error messages appear in the same location. validate that all customizations were applied. 7. Create subdirectories for each driver. you add an out-of-box drivers (. On the File menu. C. In Windows SIM. G. Insert both the removable media containing your configuration set and the Windows Server 2008 R2* product DVD into the new computer. on the Tools menu. 1. and th en revalidate the answer file. and then click OK. Validate the Answer File (In this step.x ml. and then reseal the computer by using the generalize option .C. Copy your device driver files (. Create a Configuration Set (In this step. D. Deploying a Configuration Set Without a Network A. insert the drive directly in to the primary set of USB ports for the computer. If an error occurs. Select the driver path to add to the answer file. and then click Pass 1 windowsPE. Note: This example assumes that the hard drive is blank. Windows Setup searches all removable media for an answer file called Autounattend. In Windows SIM. Change the setting to fix the error. Autounattend. Restart the computer by pressing CTRL+ALT+DEL. B.inf) to the Out-of-Box Drivers folder . 4. create directories "Chipset" and "Video" in the Out-of-Box Dr ivers folder. Close the distribution share folder.xml must be located at the root of the removable media.) A. The Browse for Folder dialog box appears.inf) path to your answer file. Add a Device Driver to the Answer File (In this step. in the Messages pane. If the answer file validates successfully. on the Insert menu. C. click Save Answer File.xml. Windows Setup (Setup. Select a removable dirve such as a USB flash drive (UFD). B. click Tools. By default. Note: When using a USB flash drive. Turn on the new computer. D. otherwise. B. Specify a destination location where you intend to publish the config uration set D. For example. For example.) A. double-click the error to n avigate to the incorrect setting. After Setup completes. B. and then click Validate Answer File. click Driver Path.

Click on MPS Uniprocessor PC -OR. ************************************************************ * 9. Select Control Panel. Copy the contents of the <INF Extract Directory>\XXXX\All directory to the root directory of the floppy disk (A:\). 8. 4. Select "Devices by connection" under the View menu. 5. 10. Close all programs currently running on the system.MPS Multiprocessor PC.For more information about Windows Server 2008 R2* answer files and unattended installations. Click on the Device Manager button. 2.) 13. 6. NOTE: Only one of the above items will be displayed for a given system. NOTE: XXXX is the directory name for the chipset of interest. 3. please refer to the Windows Automated Installation Kit (WAIK) User's Guide. Right-click on the line containing the description PCI standard host CPU bridge -orPCI standard ISA bridge -orPCI standard PCI-to-PCI bridge -orPCI System Management Bus -orStandard Dual PCI IDE Controller -orStandard Universal PCI to USB Host Controller (This line will be selected. INSTALLING THE INF FILES AFTER OS INSTALLATION ************************************************************ ************************************************************ * 9A. . Click on Start. 7. 9. Refer to Section 8 for more details. 1. so it may not be necessary to use the INF files provided by this software to update Windows* 2000. Click on the Hardware tab. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows* 2000. Select Properties from the pull-down menu. The following steps describe the installation process of the Windows* 2000 INF files. 11. Click on PCI bus. INSTALLING THE WINDOWS* 2000 INF FILES AFTER OS * INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows* 2000. Select Settings. Double-click on the System icon. 12.

INSTALLING THE WINDOWS* XP INF FILES AFTER OS * INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows* XP so it may not be necessary to use the INF files provided by this software to update Windows* XP. 16. 11. Click on the Update Driver button. 20.14. Copy the contents of the <INF Extract Directory>\XXXX\All directory to the root directory of the floppy disk (A:\). The following steps describe the installation process of the Windows* XP INF files. 12. Select the Control Panel. 24. Refer to Section 8 for more details. 19. Select Next. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows* XP. 2. Select Settings. Ensure that the following choice is selected: Search for a suitable driver for my device (recommended) 18. NOTE: XXXX is the directory name for the chipset of interest. Windows* 2000 will list locations from where the updated driver file can be found. Select Next. Windows* 2000 will launch the Upgrade Device Driver Wizard. 5. 4. Click on MPS Uniprocessor PC -OR. Click on the Driver tab. Select "Devices by connection" under the View menu.) Select Next. 3. Select Finish. Double-click on the System icon. 10. 7. Reboot the system when prompted to do so. 1. Right-click on the line containing the description PCI standard host CPU bridge -or- . 6. 15. Click on the Device Manager button. 17. Click on PCI bus.MPS Multiprocessor PC. 22. Ensure that the following choice is selected: Floppy disk drives 21. Windows* 2000 should report that a driver has been found: (The detected device name will be displayed. Select Next. NOTE: Only one of the above items will be displayed for a given system. Click on Start. Insert the floppy containing the Windows* 2000 INF files into the floppy drive. 23. 8. Close all programs currently running on the system. Click on the Hardware tab. 9. ************************************************************ * 9B.

. The following steps describe the installation process of the Windows* XP INF files. 17. 8. Copy the contents of the <INF Extract Directory>\XXXX\All directory to the root directory of the floppy disk (A:\). Windows* XP will launch the Upgrade Device Driver Wizard. Click on the Device Manager button. INSTALLING THE WINDOWS SERVER* 2003 INF FILES AFTER * OS INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows Server* 2003 so it may not be necessary to use the INF files provided by this software to update Windows Server* 2003. Close all programs currently running on the system. Click on the Update Driver button. Select the Control Panel. Refer to Section 8 for more details. 5. PCI standard ISA bridge -orPCI standard PCI-to-PCI bridge -orPCI System Management Bus -orStandard Dual PCI IDE Controller -orStandard Universal PCI to USB Host Controller (This line will be selected. 7. Select Settings. 6. Click on Start. 16. NOTE: XXXX is the directory name for the chipset of interest. 4. 3. 20. 23. 2. 24. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows Server* 2003. 1. 19.13. ************************************************************ * 9C. Select Next. Select Finish. Double-click on the System icon.) Select Next. 21. Windows* XP should report that a driver has been found: (The detected device name will be displayed. Click on the Hardware tab. 15. 18. 22.) Select Properties from the pull-down menu. Windows* XP will list locations from where the updated driver file can be found. Click on the Driver tab. Select Next. Ensure that the following choice is selected: Search for a suitable driver for my device (recommended) Insert the floppy containing the Windows* XP INF files into the floppy drive. Reboot the system when prompted to do so. Ensure that the following choice is selected: Floppy disk drives Select Next. 14.

Windows Server* 2003 should report that a driver has been found: (The detected device name will be displayed. Windows Server* 2003 will launch the Upgrade Device Driver Wizard. Ensure that the following choice is selected: Floppy disk drives 21. 12. Click on the Update Driver button. Right-click on the line containing the description PCI standard host CPU bridge -orPCI standard ISA bridge -orPCI standard PCI-to-PCI bridge -orPCI System Management Bus -orStandard Dual PCI IDE Controller -orStandard Universal PCI to USB Host Controller (This line will be selected. 19.) 13. 22. Select "Devices by connection" under the View menu. 11. 1. The following steps describe the installation process of the Windows* Vista INF files. 23. NOTE: Only one of the above items will be displayed for a given system. 14. 17. INSTALLING THE WINDOWS VISTA INF FILES AFTER * OS INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows Vista so it may not be necessary to use the INF files provided by this software to update Windows Vista. Click on MPS Uniprocessor PC -OR. Copy the contents of the <INF Extract Directory>\XXXX\All directory to the root directory of the floppy disk (A:\). Select Properties from the pull-down menu. Select Next. Reboot the system when prompted to do so. Click on PCI bus. NOTE: .MPS Multiprocessor PC. Select Next. Ensure that the following choice is selected: Search for a suitable driver for my device (recommended) 18.) Select Next. 16.9. ************************************************************ * 9D. Click on the Driver tab. Select Next. Select Finish. 20. 15. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows Vista. Windows Server* 2003 will list locations from where the updated driver file can be found. Insert the floppy containing the Windows Server* 2003 INF files into the floppy drive. 24. 10.

6. 10. The window Will Display the Device that was installed 21. Close all programs currently running on the system. Select "Devices by connection" under the View menu.XXXX is the directory name for the chipset of interest. . Windows Vista will launch the Upgrade Device Driver Wizard. Click on the Update Driver button. Reboot the system if prompted to do so. Click on PCI bus. Select Properties from the pull-down menu. 11. Select Browse my computer for the driver software. 7. Select the Control Panel. 2. Click on the Device Manager button. 17. The following steps describe the installation process of the Windows Server* 2008 INF files. Refer to Section 8 for more details. 1. 8.MPS Multiprocessor PC. Ensure that the Include Subfolders checkbox is checked 19. ************************************************************ * 9E. 9. Click on the Driver tab. 15. Click on MPS Uniprocessor PC -OR. 12. Enter "A:\" in the Combo Box 18. Click on Start. INSTALLING THE Windows Server* 2008 INF FILES AFTER * OS INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows Server* 2008 so it may not be necessary to use the INF files provided by this software to update Windows Server* 2008. Right-click on the line containing the description PCI standard host CPU bridge -orPCI standard ISA bridge -orPCI standard PCI-to-PCI bridge -orPCI System Management Bus -orStandard Dual PCI IDE Controller -orStandard Universal PCI to USB Host Controller (This line will be selected. Double-click on the System icon. NOTE: Only one of the above items will be displayed for a given system. 5. 3. Select Next 20. 14. Copy the contents of the <INF Extract Directory>\XXXX\All directory to the root directory of the floppy disk (A:\).) 13. 4. Select Close 22. 16. Click on the Hardware tab. Select Settings. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows Server* 2008.

15. Double-click on the System icon. Copy the contents of the . Select Browse my computer for the driver software. Refer to Section 8 for more details. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows 7*. Select Settings. Close all programs currently running on the system. 6. Ensure that the Include Subfolders checkbox is checked 19. Enter "A:\" in the Combo Box 18. Select Next 20. Click on the Hardware tab. ************************************************************ * 9F. 7. Click on PCI bus. Select Close 22. Click on the Device Manager button. 11. 2.NOTE: XXXX is the directory name for the chipset of interest. Click on MPS Uniprocessor PC -OR. Click on the Driver tab. Select the Control Panel. 3. Windows Vista will launch the Upgrade Device Driver Wizard. Click on the Update Driver button. 8. 14. 1. 5.) 13. Reboot the system if prompted to do so. 4. 17. 10. The following steps describe the installation process of the Windows 7* INF files. INSTALLING THE Windows 7* INF FILES AFTER * OS INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows 7* so it may not be necessary to use the INF files provided by this software to update Windows 7*. Select Properties from the pull-down menu. Right-click on the line containing the description PCI standard host CPU bridge -orPCI standard ISA bridge -orPCI standard PCI-to-PCI bridge -orPCI System Management Bus -orStandard Dual PCI IDE Controller -orStandard Universal PCI to USB Host Controller (This line will be selected. The window Will Display the Device that was installed 21. Click on Start. Select "Devices by connection" under the View menu. 16. 12. NOTE: Only one of the above items will be displayed for a given system. 9.MPS Multiprocessor PC.

Refer to Section 8 for more details. The window Will Display the Device that was installed 21. Select Properties from the pull-down menu. 7. You may need to repeat these steps to update all Intel(R) chipset devices not supported . Click on the Driver tab. Select Close 22. 10. 16. Enter "A:\" in the Combo Box 18. 3. ************************************************************ * 9G. Select "Devices by connection" under the View menu. Right-click on the line containing the description PCI standard host CPU bridge -orPCI standard ISA bridge -orPCI standard PCI-to-PCI bridge -orPCI System Management Bus -orStandard Dual PCI IDE Controller -orStandard Universal PCI to USB Host Controller (This line will be selected. Select the Control Panel. 12.MPS Multiprocessor PC. The following steps describe the installation process of the Windows Server* 2008 R2 INF files. 15. Select Next 20. Select Browse my computer for the driver software. Click on the Device Manager button. Click on the Hardware tab. NOTE: Only one of the above items will be displayed for a given system. Click on Start.<INF Extract Directory>\XXXX\Win7 directory to the root directory A removable media. 8. 14. Click on PCI bus. Close all programs currently running on the system. 2. INSTALLING THE Windows Server* 2008 R2 INF FILES AFTER * OS INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows Server* 2008 R2 so it may not be necessary to use the INF files provided by this software to update Windows Server* 2008 R2. Ensure that the Include Subfolders checkbox is checked 19. 6. NOTE: XXXX is the directory name for the chipset of interest. 17. 4. such as a USB flash drive (UFD) or floppy disk (A:\). Reboot the system if prompted to do so. 9. Double-click on the System icon. Click on MPS Uniprocessor PC -OR. 11. Click on the Update Driver button. Select Settings. Windows 7* will launch the Upgrade Device Driver Wizard. 5.) 13.

9. 10. The correct version number is shown at the top of this file. Reboot the system if prompted to do so. Windows Server* 2008 R2 will launch the Upgrade Device Driver Wizard. Click on the Device Manager button.by Windows Server* 2008 R2. Enter "A:\" in the Combo Box 18. 2. Ensure that the Include Subfolders checkbox is checked 19. 8. Click on the Update Driver button. Click on PCI bus. Copy the contents of the <INF Extract Directory>\XXXX\Win7 directory to the root directory A removable media. Refer to Section 8 for more details. Click on MPS Uniprocessor PC -OR. Select "Devices by connection" under the View menu. Close all programs currently running on the system. The window Will Display the Device that was installed 21. 5.) 13. Select Properties from the pull-down menu. Select Close 22. 6. Click on the Hardware tab. NOTE: XXXX is the directory name for the chipset of interest. NOTE: Only one of the above items will be displayed for a given system. 11. such as a USB flash drive (UFD) or floppy disk (A:\). Select Browse my computer for the driver software.MPS Multiprocessor PC. Click on Start. 12. . Select Settings. Select Next 20. 17. IDENTIFYING THE SOFTWARE VERSION NUMBER ************************************************************ The version numbers displayed by Device Manager for a given device may not be the same as the Intel(R) Chipset Device Software version. 15. 3. 7. 4. Select the Control Panel. Click on the Driver tab. 16. Right-click on the line containing the description PCI standard host CPU bridge -orPCI standard ISA bridge -orPCI standard PCI-to-PCI bridge -orPCI System Management Bus -orStandard Dual PCI IDE Controller -orStandard Universal PCI to USB Host Controller (This line will be selected. ************************************************************ * 10. Double-click on the System icon. 1. 14.

QFE (822603) installed . . TROUBLESHOOTING ************************************************************ It is assumed that the system requirements in Section 2 above have been satisfied. If devices are listed properly and the system experiences no further problems. This problem only occurs when using Windows XP with SP1 or Windows 2000 Server with SP4 on a system configured with a USB keyboard and/or mouse. This condition is temporary until a system reset. For additional information. the USB keyboard and mouse will stop functioning.INF file restore process was successful.Latest Chipset Utility Software installed.Windows XP or Windows Server 2003 installed .[LN]. reinstall the operating system.QFE (921411) installed . Issue: System locks up during Device Manager Remove or during restart. then the .Latest Intel(R) Chipset Device Software Issue: At the end of executing the Chipset Device Software.aspx?scid=kb. For additional information. reboot the machine and view Device Manager. Solution: System lockup can occur during reboot as a result of several possible system issues.com/default.Windows XP installed with SP1 .************************************************************ * 11. In the event of system lockup. If devices are not configured correctly.microsoft. please refer to the KB article located at http://support.com/kb/921411/en-us Please use the following installation procedures: .822603 Please use the following installation procedures: . Solution: A recommended fix has been provided by Microsoft in Knowledge Base article(822603). If this does not fix the issue or further issues are experienced. Solution: A recommended fix has been provided by Microsoft in Knowledge Base article(921411).microsoft. please refer to the KB article located at http://support. try re-running the procedures outlined in Section 3. Issue: USB devices no longer work correctly after you install the Intel Chipset Software Installation Utility in Windows XP or in Windows Server 2003.

Windows reports that it cannot find one of the following files: UHCD. Click OK.The current system does not contain a supported chipset. Windows reports that it cannot find the following file: ISAPNP. Windows reports that it cannot find one of the following files: ESDI_506. locate the <Windows>\System\IOSubsys directory.SYS USBHUB.pdr Solution: Click Browse in the dialog box where this issue occurs. Click OK. or -or. The system should be able to locate this file in this directory and continue re-enumerating for the new devices. Issue: After running the setup program and rebooting the machine. The system should be able to locate this file in this directory and continue re-enumerating for the new devices. Issue: After running the setup program and rebooting the machine.VXD Solution: Click Browse in the dialog box where this issue occurs and locate the <Winnt>\System directory. the HKLM\Software\Intel\InfInst key was not created or the data of the value "install" is not "success". Issue: After performing the silent install.Issue: After running the setup program and rebooting the machine. Verify that the System Requirements are met as .The current system does not contain a supported operating system. The system should be able to locate the files in this directory and continue re-enumerating for the new devices.SYS Solution: Click Browse in the dialog box where this issue occurs and locate the following directory: <Winnt>\System32\drivers Click OK. Solution: This is caused by one of the following scenarios: .SYS USBD.

Intel reserves the right to make changes to this document at any time. express or implied. * Other brands and names are the property of their respective owners. merchantability or infringement of any patent. The Intel(R) SOFTWARE LICENSE AGREEMENT (OEM / IHV / ISV Distribution & Single User) completely defines the licensed use of this software. or life-sustaining applications. 1997-2010 . Intel(R) products are not intended for use in medical. without notice. ************************************************************ * DISCLAIMER ************************************************************ Intel is making no claims of usability. efficacy or warranty. copyright or other intellectual property right. ************************************************************ Intel Corporation disclaims all warranties and liabilities for the use of this document and the information contained herein. and assumes no responsibility for any errors which may appear in this document. and Intel disclaims any express or implied warranty relating to sale and/or use of Intel(R) products. ************************************************************ ************************************************************ * Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Intel assumes no liability whatsoever.outlined in Section 2. including liability or warranties relating to fitness for a particular purpose. Copyright (c) Intel Corporation. by estoppel or otherwise. ************************************************************ Information in this document is provided in connection with Intel(R) products. No license. life saving. nor does Intel make a commitment to update the information contained herein. to any intellectual property rights is granted by this document.

Sign up to vote on this title
UsefulNot useful