Kit-Fox wrote:I hate to be the one to point this out but the 'millennium' bug wasnt bogus. There were lots of legacy systems around the world that were 'mission critical' systems that did need to be repalced/upgraded or otherwise fudged to make them work with the new dates.
However the problem wouldnt have occured at 00:00:01 on 01/01/00 as I recall, it was when the year clocked over to 01 that the problem would have happened on those systems.
You always here everyone say how it was one big scam, but dont fall for that. It was real and did affect older systems still in use back then & some are even still in use today.
What was bogus was the marketing to the 'public' ie retail consumers, as very few had systems that would be affected by the change over in the date. That was scaremongering & bogus, this however is just a very small part of the computing world and folks would do well to remember that.
System clocks were effected due to not having a full date, they all read 19**, they could not simply work as 1900 instead of 2000 because the year 2000 was a leap year and that through out the days/dates, and conflicts between system and software clocks not matching.
Software had a variety of problems, from reading system clocks which were wrong or using sequential numbering on digits of the date following the 19 presets on software clocks resulting in dates like year 19100.
Those making the computers knew this for decades and didnt change it until a mad selling frenzy and media panic a year or two before the end of the millennium.
Software clocks do NOT have to run from the system clock, they can easily run independently on key systems which are never switched off, and software on PCs with internet could easily have had software updates to confirm the date online or adjust from the wrong system clock reading.
In short, everyone who replaced hardware due to Y2K fear was ripped off. No computers sold before the late 90s were sold with warnings saying they would only last until 1999 so they were faulty by design and should have be upgraded/replaced at the manufacturers expense not the consumers.
Even then there was no need to replace hardware, only to update software, and since the software was faulty by design, that too should have been updated/replaced at the programmers expense not the consumers.
You buy a car or any other product which is later found to have a major design flaw the manufacturer has to do a recall and fix it, replace it or refund the purchase. This was worse, not only was the flaw there, but it was known at point of design and deliberately ignored, thats willful negligence.
Im surprised no lawyers took this on, could and should have been the biggest lawsuit in the world, but I guess they all feared the mighty, rich & powerful software and hardware producers. And bankrupting the tech companies would have set back tech advancement by decades and put vast numbers of people out of work.
Attack Mercs Killed (30) 459,329,001
Defence Mercs Killed (10) 2,918,478,517
Attack Soldiers Killed(60) 12,677,958
Defence Soldiers Killed(20) 226,236,488
Attack Super Soldiers Killed(300) 490,627,262
Defence Super Soldiers Killed(100) 4,131,482,551
Spies Killed(50) 4,256,505,842
Spy Killers Killed(50) 651,022,448
Mothership Weapons Destroyed(300) 35,583,034
Mothership Shields Destroyed(300) 39,498,511
Mothership Fleets Destroyed(200) 2,413,254
Planet Defences Destroyed(300) 358,539
Planets Taken(5000) 411
Naquadah Stolen(0.0001) 2,355,738,435,154,805
Untrained Kidnapped(50) 5,943,886,456
Weapon Points Destroyed (Sab+Att)(0.0001) 74,293,522,376,607
Attack Turns Used(1) 1,731,971