The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Just saw this just now on the simpsons. The Y2K bug was just a load of B******t.
First of all most computer Geniesis said there is no need to worry. When i went in school and said it was a load of Bul ocks. They said how would you know?
Well secondly it was a bug not a worm/virus/trojan* Delete as appropriate.
so it wouldnt spread from a bugged machine to another one. The Y2K bug was not really a big deal the world was not run on computers. When people say well what about nuclear powerstations that are controlled by computers. Computers for non-home use are programmed to do there job not keep the time!!
If you got any things you want to say about this please do
First of all most computer Geniesis said there is no need to worry. When i went in school and said it was a load of Bul ocks. They said how would you know?
Well secondly it was a bug not a worm/virus/trojan* Delete as appropriate.
so it wouldnt spread from a bugged machine to another one. The Y2K bug was not really a big deal the world was not run on computers. When people say well what about nuclear powerstations that are controlled by computers. Computers for non-home use are programmed to do there job not keep the time!!
If you got any things you want to say about this please do
The Y2k bug did exist, it just didn't have the effect that people dreaded, probably because of it being sorted.
My old 486 PC fell subject to it, checking the PC just into the start of January I noticed the date was January 1900. Now I'm no genius but going 100 years back in time can cause problems.
Say as plane was planned to arrive (I know no planes were in the air at the turn of new years but still) at 00:15 on Jan 1st 2000. Say the autopilot was set to land it at that time. The journey was all planned out using times for each co-ordinate.
Just as it's descending, to clock goes 100 years back in time, so the plane supposedly won't have to land for another 100 year...
What will happen? See?
That was why people were scared, nobody knew what would happen if clocks were to be wrong...
It could have been a complete disaster, but wasn't...
My old 486 PC fell subject to it, checking the PC just into the start of January I noticed the date was January 1900. Now I'm no genius but going 100 years back in time can cause problems.
Say as plane was planned to arrive (I know no planes were in the air at the turn of new years but still) at 00:15 on Jan 1st 2000. Say the autopilot was set to land it at that time. The journey was all planned out using times for each co-ordinate.
Just as it's descending, to clock goes 100 years back in time, so the plane supposedly won't have to land for another 100 year...
What will happen? See?
That was why people were scared, nobody knew what would happen if clocks were to be wrong...
It could have been a complete disaster, but wasn't...
Buck1 wrote:
> All they done was patch up there system
Patch up is just another term for fix.
Would you want to go into open heart surgery, if the computers controlling the respirator etc weren't Y2K proofed, and there was even the smallest chance that they may fail?
> All they done was patch up there system
Patch up is just another term for fix.
Would you want to go into open heart surgery, if the computers controlling the respirator etc weren't Y2K proofed, and there was even the smallest chance that they may fail?
All they done was patch up there system to the max and that cost allot of money
Well no offence, but leading governments didn't spend billions of pounds trying to ensure their systems were 'safe' if there was no possibility of there being a glitch.
I'm doing a degree in computers, and I also find it difficult to understand how there could have been a problem, but that doesn't mean there isn't potentially one there.
Updating systems controlling trivial processes such as the construction of cars, or other construction related areas, is probably a waste of money - if something goes wrong, it's no big problem to fix.
But would you want to take even the slightest risk that something may happen, when it comes to crucial systems such as bank computers, military computers, or even civil computers which control such things as air traffic control? Computers are unpredictable to start off with, without throwing in such a wildcard to add more potential for things to go wrong.
I'm doing a degree in computers, and I also find it difficult to understand how there could have been a problem, but that doesn't mean there isn't potentially one there.
Updating systems controlling trivial processes such as the construction of cars, or other construction related areas, is probably a waste of money - if something goes wrong, it's no big problem to fix.
But would you want to take even the slightest risk that something may happen, when it comes to crucial systems such as bank computers, military computers, or even civil computers which control such things as air traffic control? Computers are unpredictable to start off with, without throwing in such a wildcard to add more potential for things to go wrong.
I remember getting a guarantee thingy and receipt from Dixon's two weeks into 2000 and the date on the guarantee as puchase date was stated as January 1900!
*We're.
I just had to.
I just had to.
The thing was they wernt Y2K proof but they didnt need to know the date anyway for there systems to function. Being a someone who programs in my spare time. Ive looked at code which has had the authority to know the date-for no reason but for the program to simply know it.
By Soviet, I obviously meant Russian.
The real risk of the Y2K bug was still unknown on the 11th hour. It is widely known that both the Soviet and American Military computers, were not completely 'Y2K proofed', and as neither side were willing to switch off the computers controlling the launch of nuclear cruise missiles, amongst other things, there was a very real risk that something terrible could have happened.
That's the immaturity and paranoia of the human psyche for ya ....
That's the immaturity and paranoia of the human psyche for ya ....
Just saw this just now on the simpsons. The Y2K bug was just a load of B******t.
First of all most computer Geniesis said there is no need to worry. When i went in school and said it was a load of Bul ocks. They said how would you know?
Well secondly it was a bug not a worm/virus/trojan* Delete as appropriate.
so it wouldnt spread from a bugged machine to another one. The Y2K bug was not really a big deal the world was not run on computers. When people say well what about nuclear powerstations that are controlled by computers. Computers for non-home use are programmed to do there job not keep the time!!
If you got any things you want to say about this please do
First of all most computer Geniesis said there is no need to worry. When i went in school and said it was a load of Bul ocks. They said how would you know?
Well secondly it was a bug not a worm/virus/trojan* Delete as appropriate.
so it wouldnt spread from a bugged machine to another one. The Y2K bug was not really a big deal the world was not run on computers. When people say well what about nuclear powerstations that are controlled by computers. Computers for non-home use are programmed to do there job not keep the time!!
If you got any things you want to say about this please do