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 : TAVA Technologies (TAVA-NASDAQ) -- Ignore unavailable to you. Want to Upgrade?

To: CalculatedRisk who wrote (14103)	4/5/1998 12:05:00 PM
From: C.K. Houston	Read Replies (2) \| Respond to of 31646

Calculated Risk, <BTW, I have developed several embedded systems for telecommunication and medical device companies.> Then perhaps you might be interested in my 53 page medical device report which documents actual failures. LOL I think it's fascinating how many shorts who come on this thread tell us they have "embedded systems" background. You're not the first. We've had a couple of others over the past few months. Mike Winn was the most memorable. <BTW, most "embedded" systems are 1) not date dependent and 2) can only be updated by the manufacturer of the product.> Saw this post from you on another thread. Message 3857195 Most IS people, and even some engineers, are unaware of where and how problems can occur. A non-date dependent embedded system may be integrated with a date or time dependent system .... Do dates really matter? More examples of potential Embedded System Failures Message 3312951 It's definitely possible for non-compliant firmware to trash a system despite the fact that none of the applications reference the date. Message 3398913 Identifying embedded systems with potential time-related problems Message 3220305 You are right. Most are not date dependent. It's estimated that only 5% of embedded systems (out of 25 billion) will fail. Biggest problem is finding the ones with problems and then determining how to handle the fix. Here's a situation that I ran into recently where some engineers were unaware that they had a Y2K embedded system problem until I gave them some info: Message 3686169 Apparently something here is what alerted him: Message 3329770 They've since found some other problems. <Perhaps you can share what types of embedded systems you have developed?> Everyone who's been around for a while knows I'm not an engineer. I'm an ex-owner and founder of a national research company. Had 15 full-time people in-house and 7,000+ "part-timers" nationwide. Also designed & programmed customized software applications for my company and others ... particularly my ex's company which he eventually sold to a NYSE listed company. Back in the early 80's I was one of the first women in advertising to manage a multi-million dollar high-tech account. I'm a research specialist ... a conduit of information ... not an engineer. I leave the in-depth technical discussions to the engineers on this thread. Cheryl