It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Some features of ATS will be disabled while you continue to use an ad-blocker.
The Linux kernel always stores and calculates time as the number of seconds since midnight of the 1st of January 1970 UTC regardless of whether your hardware clock is stored as UTC or not. Conversions to your local time are done at run-time. One neat thing about this is that if someone is using your computer from a different timezone, they can set the TZ environment variable and all dates and times will appear correct for their timezone. If the number of seconds since the 1st of January 1970 UTC is stored as an signed 32-bit integer (as it is on your Linux/Intel system), your clock will stop working sometime on the year 2038. Linux has no inherent Y2K problem, but it does have a year 2038 problem. Hopefully we'll all be running Linux on 64-bit systems by then. 64-bit integers will keep our clocks running quite well until aproximately the year 292271-million.
Originally posted by John Titor
The first "leg" of my trip was from 2036 to 1975. After two VGL checks, the divergence was estimated at about 2.5% (from my 2036). I was "sent" to get an IBM computer system called the 5100. It was one the first portable computers made and it has the ability to read the older IBM programming languages in addition to APL and Basic. We need they system to "debug" various legacy computer programs in 2036. UNIX has a problem in 2038.
Originally posted by jprophet420
His story was pre 64bit chips and operating systems. There are no 32 bit (pc) cpu's in production now and havent been for a while now. Everything is 64 bit, and what isnt soon will be. By the time 2038 rolls around, there will be no 32 bit chips and there will be no 32 bit operating systems. The y2k38 bug is fixed, therefore the whole basis fo the story is false.
I'm not exactly sure what the technical issue is but I believe some sort of UNIX system registry stops in 2038...
As you are probably aware, UNIX will have a timeout error in 2038 and many of the mainframe systems that ran a large part of the infrastructure were based on very old IBM computer code. The 5100 has the ability to easily translate between the old IBM code, APL, BASIC and (with a few tweaks in 1975) UNIX. This may seem insignificant but the fact that the 5100 is portable means I can easily take it back to 2036. I do expect they will create some sort of emulation system to use in multiple locations.
I do believe that "your" UNIX will also have a problem in 2038. I don't think that's a secret but maybe someone should put a 5100 aside for thirty years or so.
You said you are confused by the 5100 story. I will explain further. In 2036, it was discovered (or at least known after testing) that the 5100 computer was capable of reading and changing all of the legacy code written by IBM before the release of that system and still be able to create new code in APL and basic.
That is the reason we need it in 2036.
Originally posted by jprophet420
What legacy code might he be refering to if not the 2038 bug?
He states that the Nuclear strike will be in 2015. If you understand moores law, you realize 32 bit chips will be at least 2 generations old by then. This is assuming that all microchip evolution and manufacturing stops the day the bombs drop.
This would be the equivilant of 8 bit computers being used today.
A demand of extremely high availability is commonly the case in computer reservation systems, air traffic control, energy distribution (power grids), nuclear power plants, military defense installations, and other systems critical to safety, security, traffic throughput, and/or economic profits. For example see the TOPS database system.
Legacy means the software and hardware are antiquated . Right now windows 98 and prior is 'legacy'. 32 bit processors and prior are already legacy, and software code can remove the y2k38 bug as of current. (in a 32 bit procesor)
technology does not de-evolve. a nuclear war would certainly stop or seriously retard it, agreed. but as of 2007 we are past the problem that I directly quotet from John Titor saying he is here to fix.
I found a picture of the mainframe this 5100 can 'debug'...
for his story to be true, he would have to be debuging that in 2038.
[edit on 17-7-2007 by jprophet420]
Originally posted by hikix
I personally think that if you are found with one piece of hoax evidence then you are no longer credible. It was shown that John Titor took a picture of his TV screen claiming that what the picture was, was human-alien hybrids (or something to that fashion). So if he had to fake that, then why would anything else be real?!?
Orginnaly posted by John Titor
No new information there (on UFOs and aliens). I find that an interesting subject myself. Personally, I think "UFOs" might be time travelers with very sophisticated distortion units. But that might be a bit wacky.
Originally posted by theindependentjournal
I wonder if his mom and dad, from now who saw him be born, know he is lieing to everyone. Have him tell you who the president will be in 2015, when the bomb drops and in 8 years if he is ight it will add credence to his story, although I am like the others. He is a prankster playing with the gullible...
Originally posted by Tiloke
Have you read his posts or the John Titor story?
The term "legacy code" means any program that is out of date and no longer supported, so he could literally be referring to any type of code. Let me say this again for the THIRD time. Titor NEVER EVER said they needed it to repair the 2038 bug. The way he talks about it suggests that they need it to trasfer the responsibilities of a unix system to another one because of the bug. HE IS NOT TRYING TO REPAIR UNIX HE IS TRYING TO KEEP HIS IINFASTRUCTURE GOING WHEN 32BIT UNIX STOPS. Why do you keep insisting he meant something other than what he said? Because thats the only way to prove your "theory"?
Originally posted by Where2Hide2006
Sorry JProphet but Titor is not debunked by your topic here. He has WAY too many hits at this point for anyone to consider him a fraud.
At worst, he was a VERY good predictor of things to come.
At Best, he was time travelor from the year 2036.
His words should not be taken lightly. Read Them Again.
Few machines remain. Despite being sold in very large numbers for a mainframe system of its era, only a few System/360 computers are known to exist today in working condition. Most machines were scrapped when they could no longer profitably be leased, partly for the gold and other precious metal content of their circuits, but mainly to keep these machines from competing with IBMs newer computers, such as the System/370. As with all classic mainframe systems, complete System/360 computers were prohibitively large to be held in storage, and too expensive to maintain. The Smithsonian Institution owns a System/360 Model 65, although it is no longer on public display. The Computer History Museum in Mountain View, CA has a non-operable System/360 Model 30 on display. The University of Western Australia has a complete System/360 in storage at its Shenton Park warehouse
The IBM 5100 portable computer, introduced in 1975, offered an option to run the System/360's APL\SV programming language through a hardware emulator. IBM used this approach in order to avoid the costs and delay in creating a version of APL specific to the 5100.