Troubleshooting: Loading a Driver
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
The following table shows descriptions and resolutions of problems you may encounter while your driver loads.
| Description | Resolution |
|---|---|
Your driver does not load. |
Verify the registry keys under the HKEY_LOCAL_MACHINE registry subkey. |
You are developing a PC Card driver, you have verified the settings under the HKEY_LOCAL_MACHINE registry subkey, and your driver does not load. |
Step through the PC Card source code and verify that the Plug and Play identifier read correctly. Because Windows Embedded CE is an embedded, real-time OS, when the PC Card signals that it is ready, there is not as much time for initialization as a PC Card on a Windows-based desktop platform. On Windows Embedded CE, if the PC Card signals that it is ready for initialization, the OS assumes that it is ready. The initialization time varies from one PC Card to another. On a Windows-based desktop platform, this is not a problem because there is extra time allowed for initialization. On Windows Embedded CE, this lack of extra time can prevent the OS from initializing the correct driver. |
Your driver loads correctly, and then immediately unloads. |
Ensure that your DriverEntry and DllMain functions are exported in the .def file for your driver. |
See Also
Tasks
Troubleshooting a Device Driver