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: Yoav Chudnoff who wrote (19603)	7/7/1998 12:48:00 AM
From: GoodQ	Respond to of 31646

Yoav: sorry I did not responded earlier, I don't use this SI feature so I normally don't check the mail. When I said Accumulative, it is actually a little different from what you are saying. Most people don't know and assume that the Y2K problem is that the software reads 00 as 1900. It turns out there are many more (especially embedded system where date are not used as dates but as frame of reference) programs which just can not intepret 00 and decides to just stop. In my experience, some Y2K problem don't happen with the first or first few occurances until at sometime(magically) it just suddenly crashes. These are the real bad problems. We found this out by accident. I can safely said that some company are truely believe they don't have a Y2K problem because they tested it and it pass. What they don't know is that their test may not include what I just said and they still have a problem. To replace a system with Y2K, you don't replace the whole floor. In most cases, only a few subsystem is affected in a major system. Therefore, it needs some engineer to know how to integrated new subsystems with old to do a good job.