In the October 13 documentation, under the section:
Windows Mobile-based Device Features > Graphics and Multimedia Technologies

It indicates that:

Dear,
How to caculate the total duration of one single test case from the log file?
At the bottom of the LOG file, there several lines like this :
*** Cumulative Test Execution Time: 0:32:45.037

CETK5.0 Graphics Device Interface Performance Test Failed. But it does not
mention any reasons for the fail in the log file
"Graphics_Device_Interface_Performance_Test.log".  Is that correct?

 I have a TESTPROCAPI ActivateDevice test in my TuxDll but it fails as my I2C driver
which i am testing has already been loaded as its a built in device. I've stepped through
code to see where it fails in devload.c. Does one not normally test ActivateDevice in
a TuxHarness. I was ...

I'm developing a test environment for a device running Windows CE and a very-
nice-to-have feature would be that the (controlling part of the) test
environment could restart an entire test in case the test crashed. I
contemplated on using the

I've run Remote Display Control for Pocket PC.  Now I'm looking for the cab
file to install the client on a Windows CE 4.1 or 4.2 device.  Does anyone
know where I can get that?
Thanks.

CETK5.0 DirectDraw Test #500 to #520 aborted. However, if run the single test
from #500 to #520, it either passed or skipped.  
Is it a known issue?  are the above tests aborted acceptable for submitting
the log?

I've been wanting to run the CETK Storage Device Block Driver API test
against a USB device that gets multiple DSKn: descriptors opened for it when
the device is plugged in.
However, when I enter the command

Running windows CE .NET Test Kit v 4.2 service packed to Q2 2005
Picked this one up when running StorageDevice\File System Driver test
5027 on a 128 MB compact flash card with two partitions
test invokes  CMtdPart::FillDiskMinusXBytesWithSetEndOfFile() method in