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: Jim Privat who wrote (3155)	5/6/1998 10:40:00 PM
From: Allen Benn	Respond to of 10309

I work in software development, and I see the Y2K problem as a "test to find the problem areas, then patch them" type of problem. I can't imagine rewriting an entire system simply because of Y2K. My initial reaction was exactly like yours. If you re-read my post www3.techstocks.com you can see what caused my to change my mind. Here's another point. While it is perfectly understandable that WIND should connect up with a software testing outfit like Silicon Valley Networks, as announced in biz.yahoo.com , isn't it a remarkable coincidence that the announcement corresponds to exactly what the Y2K doctor would order? Allen

To: Jim Privat who wrote (3155)	5/7/1998 3:21:00 AM
From: Snowshoe	Respond to of 10309

Jim, some links on Y2K impacts of embedded systems: 1996 leap year software bug causes major damage at aluminum plant homepages.iol.ie Cassandra Project Embedded Systems/Chips Links millennia-bcs.com Automation 2000 (For an insight into this engineer's experience, click on "Information", then "How I was bitten by the bug ... The experience that convinced me of the problem that we all face.") auto2000.ndirect.co.uk Embedded Systems and Y2K (IEE) uthscsa.edu Wind River Systems Y2K Statement wrs.com