You got lucky with Y2K...

Ok, everyone. Remember the whole Y2K conspiracy/craze? How everyone thought that computers were going to blow up (not literally) in 2000 because they measured time in the last two digits, and we thought that they would think that the year 2000 (00) would be displayed as 1900 (also 00), causing huge problems? Yeah, remember that? We got lucky with Y2K not happening. But we have its second go-'round coming in 30 years! May I present to you...

The Year 2038 Problem!

Also known as...

Y2K38!

Note: This is a mix of conspiracy and fact, so it does belong in the conspiracy forum.

What is it?
To measure time, computers use something known as UNIX code. What UNIX code really is is the number of seconds that have passed since the UNIX's date of "birth", which is January 1, 1970 (e.g. 01/01/70 and 00:00:01 would have a UNIX code of 1, 00:01:00 would have a UNIX code of 60, etc.). The computer then converts the number of seconds into a proper time. To store this, a "time_t" data type that is a "signer 32-bit integer" (honestly, people, I have no idea what these are) is used. However, this signed 32-bit integer can only reach a certain number of seconds before the time wraps around, meaning that it will change to a different value: that value, only in negative. Meaning that if it was at 1000 when it wrapped around, it would become -1000, and the time would show at not 1000 seconds after its start-up date, but rather as 1000 seconds before its start-up date. This is exactly what is going to happen. On January 19, 2038, at 3:14:08 in the morning (GMT), the 32-bit UNIX code will wrap around. Instead of being at 2147483647 seconds, it will be at -2147483647 seconds, meaning computers will show the time as December 13, 1901, at 20:45:52. This will cause problems similar to those envisioned by the Y2K disaster.

How do we stop it?
This is more difficult than stopping Y2K. That was simply tweaking the computers so they would show the date as 2000 and not 1900. This will be much more difficult. However, there are a few ways. Many computers use the bug-prone 32-bit UNIX code. However, if every computer switches to a 64-bit UNIX code, our codes will last until the year 32,000 (approx.) However, this means that every system that has a 32-bit processor(s) will have to be changed. This change is already underway, but will every system be changed by 2038? Only time will tell.

A demonstration

The following is a GIF image from Wikipedia showing what would happen to a 32-bit UNIX code at the time of disaster. Watch the times (real and computer), the decimal number (the amount of seconds) and the binary numbers. Watch and observe. At 3:14:08 it will happen. After 3:14:07 the next number will be the false 1901 number. It loops around, just so you know.

In twenty years, computers will be so far advanced from where they are currently, that this will be even less of an issue to concern ourselves with than shapeshifting interdimensional reptiles.

Reptiles will be gone by then. Keanu Reeves will have wiped them off the face of the Earth.

Originally posted by caedusrulesall
Ok, everyone. Remember the whole Y2K conspiracy/craze? How everyone thought that computers were going to blow up (not literally) in 2000 because they measured time in the last two digits, and we thought that they would think that the year 2000 (00) would be displayed as 1900 (also 00), causing huge problems? Yeah, remember that? We got lucky with Y2K not happening. But we have its second go-'round coming in 30 years! May I present to you...

The Year 2038 Problem!

Also known as...

Y2K38!

Note: This is a mix of conspiracy and fact, so it does belong in the conspiracy forum.

What is it?
To measure time, computers use something known as UNIX code. What UNIX code really is is the number of seconds that have passed since the UNIX's date of "birth", which is January 1, 1970 (e.g. 01/01/70 and 00:00:01 would have a UNIX code of 1, 00:01:00 would have a UNIX code of 60, etc.). The computer then converts the number of seconds into a proper time. To store this, a "time_t" data type that is a "signer 32-bit integer" (honestly, people, I have no idea what these are) is used. However, this signed 32-bit integer can only reach a certain number of seconds before the time wraps around, meaning that it will change to a different value: that value, only in negative. Meaning that if it was at 1000 when it wrapped around, it would become -1000, and the time would show at not 1000 seconds after its start-up date, but rather as 1000 seconds [B]before its start-up date. This is exactly what is going to happen. On January 19, 2038, at 3:14:08 in the morning (GMT), the 32-bit UNIX code will wrap around. Instead of being at 2147483647 seconds, it will be at -2147483647 seconds, meaning computers will show the time as December 13, 1901, at 20:45:52. This will cause problems similar to those envisioned by the Y2K disaster.

How do we stop it?
This is more difficult than stopping Y2K. That was simply tweaking the computers so they would show the date as 2000 and not 1900. This will be much more difficult. However, there are a few ways. Many computers use the bug-prone 32-bit UNIX code. However, if every computer switches to a 64-bit UNIX code, our codes will last until the year 32,000 (approx.) However, this means that every system that has a 32-bit processor(s) will have to be changed. This change is already underway, but will every system be changed by 2038? Only time will tell.

A demonstration

The following is a GIF image from Wikipedia showing what would happen to a 32-bit UNIX code at the time of disaster. Watch the times (real and computer), the decimal number (the amount of seconds) and the binary numbers. Watch and observe. At 3:14:08 it will happen. After 3:14:07 the next number will be the false 1901 number. It loops around, just so you know.

[/B]

**** ALL HAPPENED!

Also, how to computers get confused or break down because their clocks are wrong? And we survived 2000? you mean it was a bunch of obvious bullshit.

Pshh yeah right. Like I told you before, this isn't going to happen. The human race will keep growing and learning, so we will find out a way to reset something as simple as a clock!

Technology will keep being updated, so this problem is not that large of a threat. Time itself isn't going to go back, just the numbers on the computers will go back. All we have to do is reprogram the time, that isn't hard, is it?

Originally posted by pepsa
Pshh yeah right. Like I told you before, this isn't going to happen. The human race will keep growing and learning, so we will find out a way to reset something as simple as a clock!

Pepsa, it's not a matter of resetting it. You can't just reset the internal clock. You can reset the clock in the bottom right-hand corner of your screen, but the internal clock keeps ticking away without any changes. So no matter if you've set your clock to whenever, in 2038 the internal clock will still roll backwards. 'Sides which, we are already growing and learning, which is why we have learned that this is going to happen.

Oh, and BTW, it's human species, not human race. Human is a species, and different races exist within the human species.

Originally posted by pepsa
Technology will keep being updated, so this problem is not that large of a threat. Time itself isn't going to go back, just the numbers on the computers will go back. All we have to do is reprogram the time, that isn't hard, is it?

As I said before, you can't reprogram the time, and even if you could, it wouldn't do much good if the computer keeps using its 32-bit UNIX code. And given, time wouldn't reset, but think of how much of everything is automated. And now think of how much of that automation involves using times. Now imagine everything thinks it's a different time than it actually is. Truly, making most personal computers 64-bit isn't going to be that difficult to accomplish in 30 years, but think of all the mainframes that all sorts of other technologies rely on. To convert them from 32 to 64 bit would mean shutting down them and everything that relies on them (one example being controls at a nuclear power plant. Just an example). Imagine the problems that would cause!

Originally posted by pepsa
Pshh yeah right. Like I told you before, this isn't going to happen. The human race will keep growing and learning, so we will find out a way to reset something as simple as a clock!

Technology will keep being updated, so this problem is not that large of a threat. Time itself isn't going to go back, just the numbers on the computers will go back. All we have to do is reprogram the time, that isn't hard, is it?

Lord xyz is actually right. Nothing is going to happen, and computers won't have a sense of the time 1901.

I knew the Y2K thing was bollocks when it came out, as did anyone who knew a diddle about computers. This is also daft.

The only thing which worries me is how everything is computer controlled, if something happened like a meteor taking out the energy supply or intensive solar flare activity frying the satellites. If these things go down a lot of important things won´t work anymore, causing chaos.

We have all our eggs in one basket, just hope it doesn´t get dropped

Then The Amish will be making fun of everyone.

haha...i just reset my computer clock to a minute before that time and let it run down and got a "sony vaio system error" message...the clock kept going...and my computer kept working....but i did actually get an error message..

That error message will destroy reality.

yeah...its happening now....there's a big black hole opening up on my laptop screen and it's swallowing what appears to be a giant purple headed python

Originally posted by lord xyz
1901 was never programmed into computers because they weren't around back then

And if computers aren't programmed with 1901, and suddenly the UNIX code has a number that would make it 1901, what do you think is going to happen?

Originally posted by lord xyz
and computers don't compute according to a time schedule.

True, they don't, but so much is controlled by computers, and if all these computers stop working on account of the Y2K38 bug, what will happen?

Originally posted by Bicnarok
The only thing which worries me is how everything is computer controlled, if something happened like a meteor taking out the energy supply or intensive solar flare activity frying the satellites. If these things go down a lot of important things won´t work anymore, causing chaos.

Or if something such as Y2K38 happens, all the important things won't work.

Originally posted by jaden101
haha...i just reset my computer clock to a minute before that time and let it run down and got a "sony vaio system error" message...the clock kept going...and my computer kept working....but i did actually get an error message..

The reason your computer kept working (or the clock, for that matter) is because the internal clock still said it was 2008, while only the bottom right-hand corner clock said it was 2038.

Also, I accept no accountability/liability/responsability/etc. if you try setting your computer to the Y2K38 time and something happens to your computer. Not my fault, you tried it, aware of what I was saying would happen, so it's not my fault.

The reason your computer kept working (or the clock, for that matter) is because the internal clock still said it was 2008, while only the bottom right-hand corner clock said it was 2038.

Also, I accept no accountability/liability/responsability/etc. if you try setting your computer to the Y2K38 time and something happens to your computer. Not my fault, you tried it, aware of what I was saying would happen, so it's not my fault. [/B]

die

Originally posted by Bicnarok
I knew the Y2K thing was bollocks when it came out, as did anyone who knew a diddle about computers. This is also daft.

The only thing which worries me is how everything is computer controlled, if something happened like a meteor taking out the energy supply or intensive solar flare activity frying the satellites. If these things go down a lot of important things won´t work anymore, causing chaos.

We have all our eggs in one basket, just hope it doesn´t get dropped

Originally posted by caedusrulesall
And if computers aren't programmed with 1901, and suddenly the UNIX code has a number that would make it 1901, what do you think is going to happen?

Originally posted by caedusrulesall
True, they don't, but so much is controlled by computers, and if all these computers stop working on account of the Y2K38 bug, what will happen?

Originally posted by caedusrulesall
Or if something such as Y2K38 happens, all the important things won't work.

Originally posted by caedusrulesall
The reason your computer kept working (or the clock, for that matter) is because the internal clock still said it was 2008, while only the bottom right-hand corner clock said it was 2038.

Originally posted by caedusrulesall
Also, I accept no accountability/liability/responsability/etc. if you try setting your computer to the Y2K38 time and something happens to your computer. Not my fault, you tried it, aware of what I was saying would happen, so it's not my fault.

Edit: Changed my clock, like I predicted, **** all happened.

Originally posted by lord xyz
Of course, these computers have a secret clock that's counting every second since whenever...for some reason...and apparently it resets when it reaches 100000000000000000000000000000000 in binary...for some reason, and when it reaches that a second time (or whenever it started) it gets confused somehow and crashes. Yep, very likely.

It's not a secret clock. It's an internal clock, and reread my first post if you want to know what will really happen.

Originally posted by lord xyz
Edit: Changed my clock, like I predicted, **** all happened.

I'm just covering all my bases, I don't want anyone accusing me of ruining their computer. Not my fault, not my fault.

And to all you doubting people, look on Wikipedia and then do a Google search. All this stuff will come up. Read it, then respond again. It's more likely to happen than Y2K ever was.

Originally posted by caedusrulesall
It's not a secret clock. It's an internal clock, and reread my first post if you want to know what will really happen.

I'm just covering all my bases, I don't want anyone accusing me of ruining their computer. Not my fault, not my fault.

And to all you doubting people, look on Wikipedia and then do a Google search. All this stuff will come up. Read it, then respond again. It's more likely to happen than Y2K ever was.

No one will accuse you of ruining their computer because, like I said, it doesn't ruin your computer.

look on Wikipedia

aaaaannnndd therin lies your problem

Originally posted by lord xyz
An internal clock, what for? How do computers get confused? These are important questions, why aren't you answering them?

An internal clock because every computer has an internal clock. It is what will always measure the time, and it measures it in the UNIX code of seconds since 1970. As for computers getting confused when the time says 1901 because of:

A: As you said yourself earlier, they don't have a sense of 1901. A computer can't present a non-presence, so what will they do?
B: Everything that is automated that requires a sense of time will go haywire. And there's a lot of automated stuff!

Originally posted by lord xyz
No one will accuse you of ruining their computer because, like I said, it doesn't ruin your computer.

But I'm saying that just in case it does.

Originally posted by jaden101
aaaaannnndd therin lies your problem

Um...why? Wikipedia is managed by moderators that are employed by Wikipedia . They make sure everything is fact-checked, and if you write something stupid they'll correct you, and they most certainly would get rid of an entire article if it was just a piece of crap.