The Milenium Bug....
X_Stickman
Not good enough for a custom title. Join Date: 2003-04-15 Member: 15533Members, Constellation

in Off-Topic
<div class="IPBDescription">I know i'm late, but i have a question</div> What exactly was it meant to be? I was thinking about it last night (was watching the "da boom" episode of family guy) and i realised that all i knew about it was that all the computers were gonna do something and bad things would happen. Exactly what about the year 2000 was gonna harm computers?
Comments
However, Neil was simply too tired to carry out the heinous deed, and we were saved. Phew.
I need some sleep.
Some companies went over the top though. I saw a tin opener online that was Y2K compliant <!--emo&:D--><img src='http://www.unknownworlds.com/forums/html//emoticons/biggrin.gif' border='0' style='vertical-align:middle' alt='biggrin.gif' /><!--endemo-->
EDIT: Rofl, two people beat me to it.
If a computer is Y2K compliant then it means it wouldn't mess up on the year 2000. However, a lot of companies weren't too sure of the full meaning so they just put "Y2K compliant" on all thier products so people would still buy them even though there is no chance they will be effected in the year 2000.
I have no idea how a can opener can be Y2K compliant. <!--emo&::nerdy::--><img src='http://www.unknownworlds.com/forums/html//emoticons/nerd.gif' border='0' style='vertical-align:middle' alt='nerd.gif' /><!--endemo-->
BigMad explained it pretty well. The problem was that database information would become completely inaccurate, automated systems with schedulers would fail, etc. I was consulting for a very large insurance company during the year before and part of the year after Y2K, and a guy sitting next to me had come out of retirement in Florida to make an ancient IBM RPG database work after 2000 - he had to get a copy of his compiler from a Reel-to-reel tape that IBM dug out of some warehouse where it had been dropped in the early 80's. He spent 6 months fixing the application (mainframe based), and if they had just let it try and run January 1, 2000, the main backend personal insurance information of about 1 million customers would have not been accesible. Nasty stuff...
I was at my Grandparents when 99 turned 00, it was awesome... anyway, Y2K was stupid, if our race/civilization is still here when 3000 rolls around it'd be fun to see if they get panicked like we did, lol.
~ DarkATi
Fear the Y10K bug!
How about <a href='http://www.amiannoying.com/(mjnlzbufz401jn55nq1b3q45)/view.aspx?ID=3444' target='_blank'>Hiroo Onoda</a>
<!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->Hiroo Onoda is the last Japanese Soldier to surrender from official duty during WW II <b>(1974)</b> <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
By being "told" that the war was over, he was simply just bombed with pamphlets that the war had ended, which he dismissed as propaganda.
But 1974... incredible.
When I heard about all that **** I was like "Oh well **** happens."
As for those that scoff at how the bug was overblown, it was only 'overblown' because so many hard-working programmers and engineers and testers fought the problem for several years before it would have been a problem. I can say from personal experience that if Insurer I had been consulting for had ignored the issue, most of their mainframe and Unix backend apps and databases would have failed and thrown the company and their customers policies into chaos, and put them out of business. People calling to get their medical insurance payments for an upcoming operation do not want to hear 'uhhh, our database thinks it's 1900 and we can't access any of your info in our reports. Please call back in a few months when we have it all sorted out. Oh, and sorry for that automated bill you were sent for a 100-years worth of late payments, we'll try to get that $45,000,000 debt lifted off your credit report.'
<!--emo&:)--><img src='http://www.unknownworlds.com/forums/html//emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif' /><!--endemo-->
As for those that scoff at how the bug was overblown, it was only 'overblown' because so many hard-working programmers and engineers and testers fought the problem for several years before it would have been a problem. I can say from personal experience that if Insurer I had been consulting for had ignored the issue, most of their mainframe and Unix backend apps and databases would have failed and thrown the company and their customers policies into chaos, and put them out of business. People calling to get their medical insurance payments for an upcoming operation do not want to hear 'uhhh, our database thinks it's 1900 and we can't access any of your info in our reports. Please call back in a few months when we have it all sorted out. Oh, and sorry for that automated bill you were sent for a 100-years worth of late payments, we'll try to get that $45,000,000 debt lifted off your credit report.'
<!--emo&:)--><img src='http://www.unknownworlds.com/forums/html//emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif' /><!--endemo--> <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
I didn't scoff...
I'm just saying, to some degree, I feel it was blown out of proportion. (Like people hiding in caves and stuff, isn't that overblown to you Monsieur? People killing themselves or waiting for the mother ship to come back for us all, lol.) Anyway, I'm not saying it wasn't a problem, I'm saying everyone freaked out and lots of companies made lots of money off of Y2K apps that didn't always do anything at all. (Like a program I bought that just had one .dll file and a text file, it told you where to stick it in your WINDOWS/System32 dir and that was it... turned out I had a later version then the one distributed in the "fix."
So, to say it again, I understand it was a real problem and I agree, if people like you spoke of Monsieur, hadn't updated their systems then all hell would have broken loose most likely but even after most people were done patching everything they could think to the media still felt the need to talk about how terrible it was gonna get, I don't think I saw but one or two stories on how things were being fixed to avoid it or about how things HAD been fixed to avoid it, it was all about "doomsday" LOL.
EDIT: About the Y2038 Bug, why not create a time.h library that holds time data in an insane amount of bytes? Like 16 Bytes, that would get you to a long time... (don't feel like doing the math right now) Anyway, I don't program so I don't really know what I'm talking about. <!--emo&:p--><img src='http://www.unknownworlds.com/forums/html//emoticons/tounge.gif' border='0' style='vertical-align:middle' alt='tounge.gif' /><!--endemo-->
~ DarkATi
How about <a href='http://www.amiannoying.com/(mjnlzbufz401jn55nq1b3q45)/view.aspx?ID=3444' target='_blank'>Hiroo Onoda</a>
<!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->Hiroo Onoda is the last Japanese Soldier to surrender from official duty during WW II <b>(1974)</b> <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
By being "told" that the war was over, he was simply just bombed with pamphlets that the war had ended, which he dismissed as propaganda.
But 1974... incredible. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Thats the one, thanks.
*chuckle* no, you don't <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html//emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif' /><!--endemo-->
~ DarkATi <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
according to monse's article, you are right on the money.
<!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->This problem is somewhat easier to fix than the Y2K problem on mainframes, fortunately. Well-written programs can simply be recompiled with a new version of the library that uses, for example, 8-byte values for the storage format. This is possible because the library encapsulates the whole time activity with its own time types and functions (unlike most mainframe programs, which did not standardize their date formats or calculations). So the Year 2038 problem should not be nearly as hard to fix as the Y2K problem was.<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->