Ramsey,
I am by no means an expert on Y2K compliance. However, the fear by the popular media regarding "calamity" which will ensue in the hours following the year 2000 is to me a tad far-fetched. I have read numerous articles stating that most big corporations will be Y2K compliant well before Dec. 31 of next year. The problem, as I understand it, stems from the smaller companies which cannot afford a massive debugging. A bigger problem than this lies with the govt, both state and federal. If problems arise from Y2K, this is where I expect them to occur.
Y2K debugging is not required for every product. As Ian Stromberg said in one of his posts, there are many things which will not need Y2K compliance such as elevators. It will not make one iota of difference if the elevator thinks it is 1972 instead of 2000, unless of course it is linked to outside computers which is unlikely, though I well could be wrong.
I have spent enough time opining about a subject on which I know very little<GGG>
BK
FYI Anyone know where the term debugging came from? (see below)
.
.
.
.
.
.
.
.
.
.
.
.
.
.Way back when computers had vacuum tubes, there would be moth infestations which would blow the tubes, the circuits(then) of the computer. So, to get the computer running again, someone would have to open up the computer and clear the moths away, literally debugging the system. Just FYI |
