Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Wind River going up, up, up! -- Ignore unavailable to you. Want to Upgrade?

To: Erwin Sanders who wrote (5399)	6/7/1999 2:24:00 PM
From: Prognosticator	Respond to of 10309

OK. Here is a general question for this thread regarding Windows CE. Pardon my ignorance, but does Windows CE use the same protected-mode operation for its execution as all the other Windows 32-bits inherited as a legacy of Intel's x86 design? If so, does it still require all that nasty device-driver development environment to allow code at user-mode to communicate with devices? If so, then a 50us interrupt response time for Windows CE is irrelevant, since it will take much longer to get a round-trip to user-code and back. VxWorks, at least without an MMU, simply reads and writes registers to drive devices, and can respond to interrupts in 10 us or less, round trip. While lack of protected mode theoretically makes a VxWorks system less robust than Windows CE, I have never found this to be a problem in real embedded work. Plus, VxWorks is rock solid, whereas Windows never has been, and at less than 2 years old, Windows CE cannot possibly be. At least with VxWorks, I only have to worry about testing my own code. P.