Full Version: Glitch in 32-bit software will render 2038 the next Y2K -- relevant to Pyramid texts
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
This man is very intelligent and respected in the A.R.E. community which revolves around Edgar Cayce

Years ago he wrote of the year 2038 as being significant according to research done on the Pyramid texts

short version
long detailed version with plenty of fascinating Egyptian kundalini artwork

It turns out that same year, is the year that there will be an error in the code of all 32-bit software rendering them unactivated. John makes no mention of this.

There's other videos on youtube showing how Y2K did create some problems giving people inaccurate data mostly. Most big things were fixed in time, but this definitely seems like a more serious glitch from what I've read.

Imagine even if things like satellites, GPS trackers failing. There was a satellite that failed as a result of this. Imagine all the satellites right now potentially running on this code. I don't think things like missile silos and submarines will run in to this problem because of course some people know, but this will impact a loooot of devices.

even small things like watches and old phones just imagine the amount of mishaps this will create. Old hospital equipment in underdeveloped countries than can't be reprogrammed without a technician. weird correspondence.
Considering absolutely nothing happened during Y2K, that seems a total non-concern.
The Wikipedia article Navaratna linked to explains the 2038 problem far better than the summary. To quote, "The Year 2038 problem (also called Y2038 or Y2k38 or Unix Y2K) relates to representing time in many digital systems as the number of seconds passed since 00:00:00 UTC on 1 January 1970 and storing it as a signed 32-bit integer. Such implementations cannot encode times after 03:14:07 UTC on 19 January 2038. Similar to the Y2K problem, the Year 2038 problem is caused by insufficient capacity used to represent time."

It does not cause all 32-bit software to error out, or become "unactivated". It means that whatever depends on accurate time values, and uses 32-bit Unix time, will break if the software is not updated to a fixed version before that time.

Just like the Y2K problem, the 2038 problem can be fixed. The reason Y2K became a non-event is that the necessary effort to update software was undertaken ahead of year 2000. The problem was fixed before it became a problem in practice.

The 2038 problem is similarly well-understood, has been discussed for a long time, and more and more systems which would be impacted have been fixed in advance over the years. Not all, but there's a decade to go before it's critical. The simplest fix is to use 64-bit time. 32-bit systems can deal with 64-bit numbers; it's simply a little less performant.
This video you can fast forward to 10:00 of the way through and it details the scope of the problem of fixing the Y2K issue and the many many many billions that had to be spent fixing it.

I can think of many systems which can't be fixed without manual engineering because they don't have the right plugs. Many vehicles, older satellites, video game systems/phones.

Look at how much s*** Y2K caused. the billions upon billions that needed to be spent. It is not correct to say "nothing happened" there were errors in nuclear reactors in Japan for example which did not become serious, but potentially could have. There were all kinds of bugs. There's countless scattered examples of electronic vending machines acting erroneously, hospital equipment giving false data, even a deep space satellite losing contact with Earth with one of these errors. It's not like there's a complete list because after all no one took the time to calculate and log each one but there were many

Imagine if there was an emergency trigger in response to the radiation readings at those plants in Japan. The reason why a lot of major things like hydroelectric dams didn't glitch is because of the massive effort governments put in to fixing them. They needed to get involved and spend very many billions fixing Y2K.

It's just a strange correspondence I noticed. 2038 isn't some apocalyptic prophecy it's just the year of transformation John van Auken indicates and many many millions of devices are going to be disrupted simultaneously.

I spoke with a technology engineer and imagine the effort which is going to have to go in to reprogramming industrial control systems with this error in mind.