Kure Technologies Inc V.KUR.H

RE: Looking good

[ErickSodhi]

Some thoughts here: There are already a number of real-time operating systems out there. They've been around for years and are proven, reliable, and well-understood by the development community. They do the job. The object of an RTOS is to provide an efficient infrastructure for applications to deal with the hardware on which they're running. For those who are at a loss here, think of your microwave oven, your cordless phone, your cell phone, your car, and so on. The brains of these devices are generally microprocessors. The more sophisticated of them are based on RTOSs on top of which the applications are written. For example, the application deals with what to do when a button is pressed, but the RTOS is responsible for telling the application that the button has been pressed; or you have a device that has to display a graphic - the applications decides what graphic to display and the RTOS figures out how to make the display hardware render it. I've over simplified this to the point that some of the technocrats in the audience are going to flame me (please don't - this is for the benefit of the people who don't know better). For those doing research into the marketplace for next generation embedded systems, check out QNX and NTE (embedded Windows NT). You also need to be aware of Windows CE, and of course the "legacy" systems such as VxWorks, etc... (hint: do a web search on "embedded operating system" or "real-time operating system",). Hope this helps.