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.

Strategies & Market Trends : Gorilla and King Portfolio Candidates -- Ignore unavailable to you. Want to Upgrade?

To: John Stichnoth who wrote (16790)	1/29/2000 11:27:00 PM
From: Boa Babe	Read Replies (1) \| Respond to of 54805

Doncha just hafta love a guy who can use "hegemony" in a sentence and not look smug about it? <g>

To: John Stichnoth who wrote (16790)	1/30/2000 10:35:00 AM
From: the hube	Read Replies (2) \| Respond to of 54805

But, Guy--If what you say is a primary consideration ("the embedded OS creates an common environment where new systems fit best if they all use the same OS"), then I'd think that this would give msft a huge advantage going forward. They've already got the OS that works with printers and scanners and the web, and etc. Surely, all they'd have to do would be to develop an OS extension that would be compatible with Windows. The point is that MSFT doesn't have an OS that works with printers and scanners and the web, etc. They have Windows, which is and, imo, will always be, the primary OS for human/machine interface where you think of a computer. There are very few printers that run on a MSFT OS. Most of them currently use VxWorks. I'm talking about the OS for the printer itself, not for the "computer" to which it is attached. I would strongly recommend that you read up on I2O and its derivatives, such as future IO, NG I/O, and currently Infinniband. The common element to all of them is that they rely on IxWorks, a specialized version of VxWorks to run the processor on the I/O device (modem, disk drive, etc.). At some point in time, all peripheral devices will have their own processor and OS, and the CPU running on Windows, Linux or Unix will act as a concert director, managing all of the offloaded resources. For the peripheral device vendors, this is a major benefit. Rather than having to write device drivers for each OS, they write to an open standard, and it will work regardless of which OS is used. To really understand the potential of WIND, you have to stop thinking about computers and operating systems. Think about all of the things that you use on a daily basis, and how they might be better with more intelligence in them. Things like gas pumps, cameras, HDTV's, DVDs, factory tools, medical devices, etc. One good way to see the future of MSFT and WIND interrelating in the future is to look at factory automation. MSFT would like to see all of the tools running embedded NT, which could be directed and controlled by a PC running NT. With WINDs recend support of DCOM wrs.com there is the same level of reporting and control with VxWorks running the tools. VxWorks is much more suited for this type of operating environment than NT (its a build up approach where you start with a kernel and add the parts you need rather than a tear down approach where you start with everythink and take out parts that are not needed).