Microsoft KB Archive/921280

= A customized Windows PE ISO image that you create by using the CIS may not contain the OEM network adapter drivers that you add in the Extranics folder or the Extranics.x64 folder =

Article ID: 921280

Article Last Modified on 11/22/2007

-

APPLIES TO


 * Microsoft Windows XP Professional
 * Microsoft Windows XP Tablet PC Edition
 * Microsoft Office Professional Edition 2003
 * Microsoft Solution Accelerator for Business Desktop Deployment

-



SYMPTOMS
Consider the following scenario. You create a customized Microsoft Windows Preinstallation Environment (Windows PE) International Standards Organization (ISO) image by using the Computer Imaging System (CIS) from the Solutions Accelerator for Business Desktop Deployment (BDD). You add original equipment manufacturer (OEM) network adapter drivers to the Computer Imaging System\Boot Disks\WINPE\Extranics folder or to the Computer Imaging System\Boot Disks\WINPE\Extranics.x64 folder.

In this scenario, the image that you create may not contain the OEM network adapter drivers that you add to the Extranics folder or to the Extranics.x64 folder.



CAUSE
This issue occurs because the Drvinst.exe file cannot locate the files that the OEM .inf file references.

The driver download package from the OEM typically extracts the drive files to different directories according to operating system, such as Microsoft Windows XP, Microsoft Windows 2000, and Microsoft Windows NT 4.0. However, the .inf files that the OEMs provide frequently include driver information for Windows XP, Windows 2000 and Windows NT 4.0 in the same file.

The Drvinst.exe file does not determine the files that are actually needed for the driver to work in Windows XP or Windows PE. Instead, it tries to add all files that the OEM .inf file references. If the Drvinst.exe file cannot locate the files, it cannot add the drivers to the image.



RESOLUTION
To resolve this issue, add all the files that the OEM .inf files reference to the Extranics folder or the Extranics.x64 folder. To do this, follow these steps:
 * 1) After you create the ISO image, locate the %temp% folder for the account that you are using, and then find the BuildCD.log file.
 * 2) Search the BuildCD.log file for the Drvinst.exe file to identify the names of the OEM files that are missing.
 * 3) Download the files that you identify in step 2, and then add the files to the Extranics folder or to the Extranics.x64 folder.
 * 4) Build the Windows PE ISO again.



MORE INFORMATION
For more information about the Computer Imaging System Feature Team Guide from the Solution Accelerator for BDD, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/library/bb490286.aspx

For more information about the Solution Accelerator for BDD Enterprise Edition, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/desktopdeployment/default.aspx

Keywords: kbtshoot kbprb KB921280

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.