Perhaps “strange” was inappropriate above – CE is definitely different, but I guess I should let you form your own opinion.  I’ve already established that we don’t necessarily deliver what the end user sees.  Most of the time, in fact, a CE based device is delivered on hardware that we’ve never seen before.  The device manufacturers need to perform a lot of testing on these devices before they get to market, but we try to make the testing process as simple and effective for them as we can.  We provide a test kit (CETK) which they can use to test the low level functions of their board support package as well as all of their common device drivers.  The CETK also contains useful utilities (like App Verifier for CE, a CPU monitor, and others) which can be used both for testing, analysis, and investigation.  We provide a framework for writing tests (TUX), and we provide education on how to use these tools through our Windows CE Test Fests, and targeted lectures at embedded developer conferences.  Finally, we host a newsgroup where we answer questions and take feature requests.  We understand the challenges in getting an embedded device to market, and try to do as much as we can to ease the burden on device manufacturers.