15.4. Windows XP Embedded WinDriver Component


	Chapter 15. Driver Installation — Advanced Issues

When creating a Windows XP Embedded image using the Target Designer tool from Microsoft's Windows Embedded Studio, you can select the components that you wish to add to your image. The added components will be installed automatically during the first boot on the Windows XP Embedded target on which the image is loaded.

To automatically install the required WinDriver files — such as the windrvr6.inf file and the WinDriver kernel driver that it installs (windrvr6.sys), your device INF file (for a Plug-and-Play device — PCI/PCMCIA), and the WinDriver API DLL (wdapi1130.dll) — on Windows XP Embedded platforms, you can create a relevant WinDriver component and add it to your Windows XP Embedded image.
WinDriver simplifies this task for you by providing you with a ready-made component: WinDriver\redist\xp_embedded\wd_component\windriver.sld.
To use the provided component, follow the steps below.


	The provided windriver.sld component relies on the existence of a wd_files directory in the same directory that holds the component. Therefore, do not rename the provided WinDriver\redist\xp_embedded\wd_component\wd_files directory or modify its contents, unless instructed to so in the following guidelines.

For a Plug-and-Play device (PCI/PCMCIA) — modify the dev.inf file:
The windriver.sld component depends on the existence of a dev.inf file in the wd_files directory. The WinDriver installation on your development Windows platform contains a generic WinDriver\redist\xp_embedded\wd_component\wd_files\dev.inf file. Use either of the following methods to modify this file to suit your device:
- Modify the generic dev.inf file to describe your device. At the very least, you must modify the template [DeviceList] entry and insert your device's hardware type and vendor and product IDs. For example, for a PCI device with vendor ID 0x1111 and product ID 0x2222:
  "my_dev_pci"=Install, PCI\VEN_1111\&DEV_2222
OR:
- Create an INF file for your device using DriverWizard (refer to Section 4.2, Step 3) and name it dev.inf, or use an INF for one of WinDriver's enhanced-support chipsets [7] that suits your card and rename it to dev.inf. Then copy your dev.inf device INF file to the WinDriver\redist\xp_embedded\wd_component\wd_files directory.
- For a non-Plug-and-Play (ISA) device — remove the dev.inf installation from the WinDriver component: Remove or comment-out the following line in the installation file WinDriver\redist\xp_embedded\wd_component\wd_files\wd_install.bat (to comment-out the line, add two colons — :: — at the beginning of the line): wdreg -inf dev.inf install
Add the WinDriver component to the Windows Embedded Component Database:
1. Open the Windows Embedded Component Database Manager (DBMgr).
2. Click Import.
3. Select the WinDriver component —
  WinDriver\redist\xp_embedded\wd_component\windriver.sld — as the SLD file and click Import.
Add the WinDriver component to your Windows XP Embedded image:
1. Open your project in the Target Designer.
2. Double-click the WinDriver component to add it to your project.
  Note: If you already have an earlier version of the WinDriver component in your project's components list, right-click this component and select Upgrade.
3. Run a dependency check and build your image.

After following these steps, WinDriver will automatically be installed during the first boot on the target Windows XP Embedded platform on which your image is loaded.


	If you have selected to rename the WinDriver kernel module [15.2], you will not be able to use the provided windriver.sld component. You can build your own component for the renamed driver, or use the wdreg utility to install the driver on the target Windows XP Embedded platform, as explained in the manual.


15.3. Windows Digital Driver Signing and Certification		Appendix A. 64-Bit Operating Systems Support