during my GDI test, about 3 hours after clicking "quick start". WinCE OS
dialog box says :
Program is very low.You must select one task to close, or increase the
amount of program memory, if available.

my flash test
testcase 1001 1002 1003 1004 appears to be passed
during the testcase 2000,there's an error.
No results file is available for this test.

Edit command line tux -o -d flshwear -c "/disk DSK1 /store"
I know here are some helpful posts here, and I do that as follows. But the
result is disappointing.
opening a handle to storage device "DSK1"

I have written my own display. When I test this driver with gdiapi test
using the default command line, some of the tests fails. But if I run
the test suite again without a recompilation of the kernel and the
drivers, other test cases fails. This happens each time when I run the

ykliu has postet the same problem that i have,
the main poblem is on the OAL Timer Test cases 102,111,121 - all are going
for latency. ykliu wrote:

I am runnign Serial Communication Test but I get a test abort. Test case 30
(Test Transfer(Round Trip) Time for 9600) is always aborted. Output is:
In Comm.cpp @ line 48:  Open Device by Name(COM1:) return handle =8b0c03
In PSerial.cpp @ line 161:  Begin Test Synchronization for ...

i am on serial communication testing for a arm4-based device. the test fails
and the report tells:
BEGIN TEST: "TempleteTest", Threads=0, Seed=3698
In PSerial.cpp @ line 157:  Begin Test Synchronization for 0x0000000A