14.3.1. Distribution to New Windows CE Platforms
The following instructions apply to platform developers who build Windows CE
kernel images using Windows CE Platform Builder or using
MS Visual Studio 2005/2008 with the appropriate Windows CE plugin. The
instructions use the notation 'Windows CE IDE' to refer to either of
To distribute the driver you developed with WinDriver to a new target Windows CE
platform, follow these steps:
If you have not already done so, modify
the project registry file — WinDriver\samples\wince_install\project_wd.reg — to add
an entry for your target device.
When defining ID values, take care
to use the correct format, as specified in the project_wd.reg comments
— hexadecimal in the case of PCI devices.|
Compile your Windows CE platform (Sysgen stage).
Integrate the driver into your platform:
Run the Windows CE IDE and open your platform.
Select from the
Copy the WinDriver CE kernel file —
WinDriver\redist\<TARGET_CPU>\windrvr1230.dll — to the
subdirectory on the target development platform (should be the current
directory in the new command window).
Append the contents of
%_FLATRELEASEDIR%\project.reg registry file.
Copy the contents of the
file to the FILES section of the binary image builder file —
Then uncomment the line that matches the target platform (see the
"TODO" comments in the copied text).
This step is only necessary if you want the WinDriver CE kernel file
(windrvr1230.dll) to be a permanent part of the Windows CE image
(NK.BIN), which is the case if you
select to transfer the file to your target platform using a boot disk.
If you prefer to have the file windrvr1230.dll loaded on demand via
the CESH/PPSH services, you do not need to perform this step until you
build a permanent kernel.
Select from the
menu to save the new image
Download your new kernel to the target platform and initialize it either by
selecting from the
menu, or by using a boot disk.
For Windows CE 4.x, the menu is called
Restart your target CE platform. The WinDriver CE kernel will automatically
Install your hardware-control application/DLL on the target.
If your hardware-control application/DLL uses
wdapi1230.dll (as is the case
for the sample and generated DriverWizard WinDriver projects), also copy this
DLL from the
directory on the Windows host development PC to the target's