To Anyone:
1) Is it really possible to stick Windows CE on top of pSOS or somehow merge the two OSs? In INTS' conference call, when they talked about working with CE, they used the automobile as an example, but they mentioned that CE would be used on the dashboard and INTS under the hood. Those are two different products and don't imply that the two OSs will actually work together. In the article yesterday, INTS said the target market for CE/pSOS would be for "developers who want to blend the determinism of an RTOS with the ease-of-programmability of Windows CE," All in all, the two statements coming from INTS are confusing to me.
2) how many more markets could CE reach if they are able to add the following features?
Accordingly, Microsoft will add a host of specific new features into the next release of CE to implement hard real-time support. Leading the list is a new prioritization scheme, which will boost CE's current five priority levels to 32 different priority levels. Microsoft will also add a real-time clock, support for thread-based device drivers, settable device-driver priorities,OS-level timing diagnostics, DLL mechanisms for real-time threads, semaphores and real-time isolation for non-real-time threads.
Seems like WIND would still have a sizable technical advantage over the improved CE. One of the major drawback of the current version of CE is its large size. Is it possible to add these new features, yet shrink the OS so it will fit in the deeply embedded systems that make up the core of Wind's current business? Or would they have to basically try and redesign CE from scratch again or maybe have a separate OS (which doesn't sound like it's in MSFT's plans unless they buy an established RTOS)?
Answers to any of these questions would be appreciated.
Regards,
Jason |
