The Windows CE Developer's Conference

It was quite an event! From the 6th to the 8th of April more than 2100 developers, engineers, and movers and shakers of the Windows CE world gathered in San Jose, California for the annual Windows CE Developer's Conference. Even when you subtract 150-200 Microsoft people and 50-100 press people, that's still quite a strong showing. Last year's developer conference was less than half that size.

Each morning various Microsoft higher-ups treated us to technical marketing presentations. The emphasis was on the technologies, the status of Software Developer Kits (SDKs), tools for developers, APIs, and the coming attractions for the next six-twelve months. Dave Wecker, Principle Engineer, Microsoft Mobile Electronics Product Unit, did an extended Palm-size PC demo that really gave us an idea of that device's capabilities. Randy Kath, Group Manager, Microsoft Windows CE Tools, talked about the various SDKs and tools. On the final day, Handheld PC Magazine columnist Andy Seybold talked about wireless data solutions and hosted a series of demonstrations.

The presentations were only part of the conference. During lunch, and the first three evenings (Sunday through Tuesday), the exhibits hall was open. There were 40-50 OEM manufacturers and vendors displaying Windows CE products and services. By far the largest percentage were hardware and chip manufacturers, system integrators, consultants, and other service companies that focus on helping companies bring Windows CE products to the marketplace (see Windows CE Developer's products and services, page 44). There were very few developers of commercial shrink-wrap applications. That's an indication of the relative newness of the Windows CE software market, plus the fact that a Windows CE device, right out of the box, has most of the basic applications that a user might want.

Afternoons consisted of as many as six parallel tracks, so it was almost impossible to attend everything of interest (a few sessions were repeated). The tracks focus on writing H/PC applications (for the Handheld PC, Palm-size PC, and Auto PC), Windows CE internals (threads, graphics, communications, synching, object store, and so on), and on embedded systems (writing drivers and shells, and hardware adaptations).

"Embedded Systems" developers well represented

One presentation, on the morning of the first day, asked for a show of hands of embedded, corporate, and commercial developers. Surprisingly, the largest percentage (easily over 50 percent) was embedded developers. Since last fall, when Microsoft introduced Windows CE 2.0 at the Embedded Systems Conference, they have stated that Windows CE is appropriate for embedded systems. At that time they also announced the componentization of the Windows CE OEM Adaptation Kit (OAK) so that system designers can readily pick and chose the pieces they want.

Apparently, embedded engineers and developers are starting to take notice. Many of the embedded developers were there just trying to figure out what Windows CE was and whether they should take it seriously.

Embedded systems are difficult to define (at least I'm still looking for a clear-cut definition). They typically aren't consumer products, but more specialized for industrial applications. Often, they require predictable real-time performance, including fast and guaranteed interrupt latency and response times, sophisticated scheduling, process and thread capabilities, very high mean times between crashes, and small memory footprints. Many of the developers I talked to were quite skeptical that Microsoft could deliver an operating system with those qualities. Microsoft did promise that within the next six months, they would deliver a beta version Windows CE with better real-time capabilities, more threads and priority levels, and solid performance. They committed to deliver a final hard real-time system within the next year.