Troubleshooting the Camera and DirectShow Integration Test (Windows Embedded CE 6.0)
1/6/2010
The following table shows troubleshooting tips for the Camera and DirectShow Integration Test.
| Item | Solution |
|---|---|
Test cases 100-113 are failing. |
These test cases can fail if certain sets of hardware are unavailable (for example, if the device is missing audio support), or if no camera driver is detected. Detailed output is given to assist with troubleshooting. |
Test cases 200-216 are failing. |
These test cases can fail if the camera driver does not transition states correctly, or from any condition which causes tests 100-113 to fail. |
Test cases 300-309 are failing. |
These test cases can fail from driver issues preventing preview from running, or from any condition which causes earlier tests to fail. |
Test cases 400-405 are failing. |
These test cases can fail from driver issues preventing a still image capture, or from any condition which causes earlier tests to fail. |
Test cases 500-512 are failing. |
These test cases can fail from driver problems when doing video capture. |
Test cases 507 and 510 are failing when using the Logo Test Kit (LTK) user interface (UI) |
The work-around for these failures is to run these test cases from within the Windows Embedded CE UI instead. |
Test cases 600-605 are failing. |
These test cases can fail from driver problems when doing video capture. |
Test cases 700-711 are failing |
These test cases can fail from problems with the DirectShow filters or components. |
Test cases 800-807 or 900-908 are failing. |
If these tests fail, verify that the driver property tests succeed and that the properties are settable. This test does not verify screen contents, so properties which do nothing will pass. |
Note that SYSGEN_DSHOW_CAPTURE (DirectShow capture) and SYSGEN_NULLCAM for the sample camera driver are required in the operating system build.
For more troubleshooting help, see Troubleshooting the CETK Tests.