SI
SI
discoversearch

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

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: daffodil who wrote (9784)9/3/2000 9:49:30 PM
From: foobert  Read Replies (2) of 9818
 
Not so fast mister,

Would you believe that there are people out there still expecting problems?

I saw this posting recently on the comp.software.year-2000 forum:

<<<
The "two digit date" within embedded chips and old programming will cause a divide-by-zero error when the date flips from "00" to "01".

There were a limited number of problems going into the year 2000 because the previous two-digit year was "99" and a date could still be calculated by the logic within the embedded chips.

The real Y2K will strike on January 1st, 2001 because a "00" being calcualted to form a "01" will cause a divide by zero error inside the internal logic of embedded chips. This would mean that the relatively smooth passing into the year 2000 was too good to be true, just like a scam. All of the cosmetic Y2K remediation, pardon the pun, was for naught.

Y2K is Alive
>>>

And then there is this guy. I'm sure he will be ready

tampatrib.com

As for myself, I was on phone standy for the (non) event. We really didn't expect any problems at the site I worked at. We did the Y2K remediation well ahead of time, and tested twice, so we were pretty sure we would be OK. The only concern was the external factors that may have arisen.

I did find and fix several small Y2K problems both at work and on the home computers, all easily solved.

foobert
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext