Originally posted by caedusrulesallWhy measure the time? Why 1970 (and since 1970 is the start, to them, 1901 never happened)?
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.
Originally posted by caedusrulesallNot present it. They can't get confused if they have no concept of it. We can't get confused as to why there's like in the galaxy next to ours, we don't know of life in the galaxy next to ours. Nothing to get confused about, no confusion.
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?
Originally posted by caedusrulesallAll with a sense of time? I don't think so. Computers don't have that sense...or any sense.
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 caedusrulesallIt won't.
But I'm saying that just in case it does.
Originally posted by caedusrulesallI must find a mistake or an error in nealry every article. Usually when looking at music. A band website could say the band started in 1999 but a list of bands could say the band started in 98. I've seen the likes of that too many times.
Um...why? Wikipedia is managed by moderators that [B]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. [/B]
Originally posted by lord xyz
I must find a mistake or an error in nealry every article. Usually when looking at music. A band website could say the band started in 1999 but a list of bands could say the band started in 98. I've seen the likes of that too many times.
But have you ever found an entire article that is one giant mistake?
Originally posted by foolstation
In 2038 there will be no computers at all, because it`s a known secret that a WW3 will begin at 2013. And there`s not much to be left after that.
Oh, I never get tired of the hilarious craziness of stuff posted on this forum (except for this thread of mine, of course.)
🤣 😆 🤣 😆 🤣
Also, lord xyz, a computer related bug appears on a bunch of your posts: whenever you've edited a post, it comes up as "Last edited by lord xyz on Jan 1st 2000 at 00:00 AM". Look at your post above this one to see it.
Originally posted by caedusrulesallAlso, lord xyz, a computer related bug appears on a bunch of your posts: whenever you've edited a post, it comes up as "Last edited by lord xyz on Jan 1st 2000 at 00:00 AM". Look at your post above this one to see it.
please tell me you're being sarcastic lest i have to kill someone out of frustration at my fellow human beings
Originally posted by jaden101
i know that...it's part of his signature...it's deliberate...he wrote it
Oh...um. How am I supposed to know that? Seriously, one of the problems with Y2K38 is that since Y2K never happened, people assume the same will happen in 2038. It's a whole different scenario, one that has been tested and found that it will happen unless something is done about it! Y2K was about computers not knowing that it would be 2000 since they measured years in the last two digits (eg. 1999 would show as 99, 2000 would show as 00.) Since that problem was corrected, people believe that Y2K38 won't happen. It's a whole different situation! The UNIX code will wrap around at 3:14:08 on Jan. 19/2038, which is something completely different, and it's not just a matter of "Ok let's prepare in case something happens", it's a matter of "We need to prepare because it will happen". We need to prepare! Luckily we have 30 years to do so, but 30 years means nothing if people assume we're safe because the original Y2K didn't happen.
i think you need to watch this
Originally posted by caedusrulesallBeing as you admitted to yourself that you have no idea how this whole "32-bit UNIX code" stuff meant, it's no wonder that you're stupid enough to believe this could ACTUALLY happen.
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?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?
Or if something such as Y2K38 happens, all the important things won't work.
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.
Face it, it won't happen. It' CAN'T happen. Even if it could, it's not like we'll be using computers with the same internal clock anymore. Besides, how do you know what the specifics on government computers are. They're more advanced than any computer you've ever seen.
Stupid.
Originally posted by ~KoK!~
Being as you admitted to yourself that you have no idea how this whole "32-bit UNIX code" stuff meant, it's no wonder that you're stupid enough to believe this could ACTUALLY happen.
I have a basic understanding of how it works, and how this problem could arise. But I don't know computers inside out, so I don't know the specifics and intricacies of it.
Originally posted by ~KoK!~
Face it, it won't happen. It' CAN'T happen.
Why is it so impossible to happen?
Originally posted by ~KoK!~
Even if it could, it's not like we'll be using computers with the same internal clock anymore.
Some computers have lasted much longer than we ever thought they would. What's to say a computer built in our times right now couldn't survive to 2038? It doesn't matter when it was built, just that it has 32-bit processors/UNIX code.
Originally posted by ~KoK!~
Besides, how do you know what the specifics on government computers are. They're more advanced than any computer you've ever seen.
Not only government computers are automated, plus while they may be advanced they still have an internal clock that utilizes UNIX code, meaning that it could be 32-bit UNIX code that they use.
Originally posted by ~KoK!~
Stupid.
Workable.
For more information and a more in-depth explanation visit http://www.2038bug.com/index.html .
Originally posted by caedusrulesall
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.
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!
My computer has a 64 bit processor, and a 32 bit operating system. The clocks can't possible do anything bad even if they mess up. It would be really easy to just develop some sort of patch to fix the time. And to reset the time or wipe it out you just pull out the CMOS battery out of the motherboard.