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 : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?

To: foobert who wrote (9059)	11/1/1999 7:22:00 PM
From: daffodil	Respond to of 9818

>>Since no one else volunteered to bring an accordian, I will. And I promise not to play it. (Definition of a gentleman: Man who knows how to play an accordian but does not.)<< Oh, nooooooo! You must come, and you must bring and play your accordion! How better to keep the blood flowing on those chilly nights than to dance a little polka and drink a little vino? (Definition of a music lover: Person who can appreciate the glories of both Aida and the accordion) :) }=>-------->>>>

To: foobert who wrote (9059)	11/1/1999 10:57:00 PM
From: foobert	Respond to of 9818

This one on topic. When changing time back yesterday to standard time from daylight savings time, I got to thinking of all the "billions of imbedded chips" that the doomsters fear will bring on TEOTWAWKI in a few short days. Who changes the time on those chips? I reset a VCR, microwave oven, programmable thermostat, a HEX calculator with a clock and calendar functions, and an assortment of watches and clocks. So if these imbedded chips (or systems) are not set/reset as we enter and leave daylight savings time, you can expect armeggedon to show up as early as 11:00 PM on Dec 31. (if you are so inclined) My point is: for an imbedded chip to cause a Y2K failure on some critical process at the year 2000 transition, it must know the current time and date. To know the current time and date, there must be some way to set it. If you have a way to set it, then you know about the existence and location of the critical chip. If you cannot set the time and date on a critical imbedded chip, then you can not be sure that it is in step with the actual current time and date. As a result, it may then fail ANYTIME. Doesn't sound like a robust design to me. Methinks the people counting "billions" of imbedded chips are counting mostly digital watches. Comments?