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: Cheeky Kid who wrote (6713)	7/18/1999 5:36:00 PM
From: C.K. Houston	Respond to of 9818

<Explain all the "critical Y too Kay" dates that have passed with out a hitch??> Same deal as what I explained here: Message 8651506 Cheryl

To: Cheeky Kid who wrote (6713)	7/18/1999 10:27:00 PM
From: daffodil	Read Replies (1) \| Respond to of 9818

<<Explain all the "critical Y too Kay" dates that have passed with out a hitch?? Y too Kay bugs were going to start appearing Jan.01/99, were are they?>> Hi, Cheeky. Although your question was directed to Cheryl, I hope you don't mind if I chime in. Your question is an excellent one. I don't know if you recall my posts on this board quite some time ago, but I'm one of the folks who got us into this predicament back in the late '60's and early '70's. All of the dates that have passed so far are what I call "application program" dates. In other words, they are dates that have significance in mainframe applications like accounting, payroll, inventory, etc. Their programs may have been written in 3rd and 4th generation programming languages such as BASIC, COBOL, FORTRAN, and their progeny (I go as far back as ARGUS<g>). If there are bugs in these types of programs and applications, they are relatively easy to find, fix, and test. In fact there have been plenty of glitches in fiscal year programming as we rolled over to '00 quarters this year, but they have been easily fixed and have received very little publicity because they were just that...glitches. As far as I understand the dates to date, they would not be expected to impact embedded chips and, therefore, critical systems which would take longer to fix. The date I'm most interested in is 9/9/99. That's the easiest programming of all to find in mainframe applications, but I haven't been able to find anyone who is aware of this date in an embedded system. Therefore, I expect that this date will also pass without any significant problems. It's the rollover to '00' in embedded systems that remains the big unknown. Sorry for the long read, but I hope this helps.