1.9. How Do I Develop My Driver with WinDriver?


	Chapter 1. WinDriver Overview

1.9.1. On Windows and Linux

Start DriverWizard and use it to diagnose your hardware — see details in Chapter 4.
Let DriverWizard generate skeletal code for your driver, or use one of the WinDriver samples as the basis for your driver application (see Chapter 7 for details regarding WinDriver's enhanced support for specific chipsets).
Modify the generated/sample code to suit your application's needs.
Run and debug your driver in the user mode.
If your code contains performance-critical sections, refer to Chapter 10 for suggestions on how to improve your driver's performance.


	The code generated by DriverWizard is a diagnostics program that contains functions that read and write to any resource detected or defined (including custom-defined registers), enables your card's interrupts, listens to them, and more.

1.9.2. On Windows CE

Plug your hardware into a Windows host machine.
Diagnose your hardware using DriverWizard.
Let DriverWizard generate your driver's skeletal code.
Modify this code, using MS eMbedded Visual C++, to meet your specific needs. If you are using MS Platform Builder, activate it and insert the generated *.pbp into your workspace.
Test your driver on the target embedded Windows CE platorm.

If you cannot plug your hardware into a Windows host machine, you can still use DriverWizard to generate code for your device by manually entering all your resources in the wizard. Let DriverWizard generate your code and then test it on your hardware using a serial connection. After verifying that the generated code works properly, modify it to meet your specific needs. You may also use (or combine) any of the sample files for your driver's skeletal code.


1.8. Limitations of the Different Evaluation Versions		1.10. What Does the WinDriver Toolkit Include?