The original source code to thse applications were destroyed in 2015.
At present the SCAMP prototype, an APL machine that was the unique forerunner of the first production personal computer, resides in the collection of the Smithsonian Institution in Washington, DC.
http://www.research.ibm.com/journal/sj/304/ibmsj3004C.pdf
Posted by John Titor on 02-19-2001 11:03 AM
Suggesting there is a war coming is a bit different than saying avoid Washington DC at 3:45 AM on March 12, 2015.
Of all people, I would think that you would understand precisely why it is not falsifiable. It is due to your most favorite feature of the John Titor story: INFINITE WORLDLINES. You do realize, I hope, that this feature of the story means that anything and everything John Titor ever "predicted" is subject to the "out" or "cover" of saying "well, the reason it didn't happen as Titor predicted is because it happened on a worldline with a larger divergence from Titor's worldline." This is precisely why one should have a crystal clear, scientific definition of how divergence is measured... something Titor never provided.I do wonder WHY the John Titor story is not falsifiable.
The production machine was designed at IBM’s General Systems Division laboratory at Rochester, Minnesota, and was made available as a product, the IBM 5100 machine, in 1974-less than a year and a half from the start. This remarkably short development cycle for such a complex new product can be attributed in large part to the fact that emulation was used again, even in the final product. This time, however, although the same Palm internal engine was used, System/360 architecture was emulated rather than 1130 architecture,
If I recall correctly, one of the nitpicks against MadIce's plethora of data on this System/360 issue was related to the belief that "actual" System/360 code was used, and NOT just emulation. I can go back and find the post that MEM was whining about this. However, it is clear from this document that it is NOT as MEM has claimed... rather that the machine does, indeed, ONLY emulate the original System/360 instruction set.
This time, however, although the same Palm internal engine was used, System/360 architecture was emulated rather than 1130 architecture, so that the up-to-date APLSV product system could be used as the APL facility with virtually no modification.
Posted by John Titor on 02-08-2001 09:40 AM
Based on what I know about the 5100, it has a few very interesting and worthwhile properties that make it worthwhile for a time traveler to recover. Also, please keep in mind that civilization is recovering from a war. Yes, we do have the technology but many of the tools were lost.
http://www.bsp-gmbh.com/turnkey/cookbook/hercules/hercfaq.html
With that opcode chart anyone could make a simple dissasembler in a couple days.
Not according to titor:rather that the machine does, indeed, ONLY emulate the original System/360 instruction set.
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. However, that information was never published by IBM because it would have probably destroyed a large part of their business infrastructure in the early 70s. In fact, I would bet the engineers were probably told to keep their mouth’s shut.
I am referring to the following statement made by you earlier in this thread:I don’t understand your point. What do you mean by “actual†System/360 code? Complete the sentence.
Hercules: But it was impossible to make an s/360 emulator before 1998.
Hercules: The machine did have a s/360 emulator hard coded into it. That is what is needed in 2036 according to the Titor Story. They cannot debug anything related to APL cuz the original source code are destroyed in 2015.
But MadIce has clearly shown that there were plenty of IBM System/360 emulators after the mid 70s. BOTH HW AND SW EMULATORS OF THE S/360 PROTOCOL. This nullifies John Titor's "need" to travel back in time to the 1970s in order to get an IBM 5110. There was never any need to go back that far. We have them today, in 2005, so they could have only had to come back to 2005. But we also had them all through the 90s and 80s, as MadIce has shown. S/360 emulators, in both HW and SW configurations have not exactly been scarce over the last 25 years...OK? /ttiforum/images/graemlins/smile.gifHercules: From the Hercules emulator in our worldline(2000) they can easily make a disassembler in 2036 in Titor’s Worldline.
Not according to titor:
In reply to:
--------------------------------------------------------------------------------
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. However, that information was never published by IBM because it would have probably destroyed a large part of their business infrastructure in the early 70s. In fact, I would bet the engineers were probably told to keep their mouth’s shut.
Yeah it is a hardware emulator released by IBM in 1983. You did NOT get my point. I am talking about a software emulator like the one I pointed out(Hercules developed by Roger Bowler).
I CHALLENGE you that you cannot find one that is developed before April 1998. This is the key point in the Titor story.
Reduce Costs for Mainframe Development:
Now there is no need to work off-hours to get your assemblies done. You can get instant turn-around even when the mainframe is at its busiest. You don’t even need to be attached to the mainframe to get your work done. All you need is the Tachyon 390 Cross Assembler or Tachyon z/Assembler and your source code on your workstation.
The Tachyon 390 Cross Assembler and Tachyon z/Assembler have enhanced assembler statement validation not available with the IBM assemblers. It can detect coding errors that could result in unwanted midnight phone calls. Don’t let errors in seldom executed code slip by your testing. Use the “LINT†feature on all of your code before you even start testing.
When you do start testing, the Tachyon 390 Cross Assembler and Tachyon z/Assembler can generate symbolic debugging information for your testing tools. There is even a direct interface to Cole Software’s XDC debugger and the Tachyon Operating System debugger, including support for long symbol names.
http://www.tachyonsoft.com/txaover.html
TITOR WAS NOT TALKING ABOUT AN EMULATOR! Go back and read his posts.
Unfortunately, OS/360 was not Y2K clean. IBM never provided patches for it. . So I decided to learn assembler to fix OS/360, while ignoring people telling me, that a fix is impossible. It was much easier than thought. The affected parts of the source sometimes had comments with 'please patch here', if one is used to read between the lines.
http://open360.copyleft.de/Open360/OS_360_Y2K.html
A PERFECT example of this is Intel's Itanium processor, the IA-64, which used emulation hard coded into the chip to convert on the fly, instructions, into x86. That is PRECISELY what we are talking about. If you can rip the data from the chip, you can build an emulator to duplicate how the instructions are read, processed, converted into the IBM Legacy instruction set, and thats all it is people. However you can't just do this from scratch, having to reverse engineer a compiler conversion utility without the original documentation from IBM would be virtually impossible, making the hardware absolutely necessary to acquire in order to accomplish your task.
You are either mistaken, or you are purposefully trying to change the subject from one topic to another. Let's review how the conversation went:Please go back and read what I wrote. I addressed MadIce’s statements, It was he who did not address mine.
Hercules: But it was impossible to make an s/360 emulator before 1998.
MadIce: No it wasn't. The IBM PC/XT 370 is even a hardware emulator. Specially equiped for the job with additional hardware that was not available on the IBM 5100. We are talking about 1983 here.
Right there you did not see that he showed your statement was incorrect. You said it was IMPOSSIBLE (a key word) to make a s/360 emulator before 1998. Clearly it was possible, since he gave you an example of a HW emulator in the PC/XT 370. In fact, I used to use these computers when I was designing autopilots for McDonnell-Douglas commercial aircraft. We used the s/360 emulation in those machines to make it easier to do mainframe commands and database queries directly from our desktop PCs.Hercules:Yeah it is a hardware emulator released by IBM in 1983. You did NOT get my point. I am talking about a software emulator like the one I pointed out(Hercules developed by Roger Bowler).
This is also where you change the subject, and try to avoid what MadIce showed you. Why is it all of a sudden MadIce who has to prove anything? He was the one showing that your statement was incorrect. He did that. Your wishing to change the subject does not avoid that you were incorrect, and certainly should not mean that MadIce has to prove anything. However... if you were to ask him nicely, I bet MadIce could, indeed, find a SW s/360 emulator prior to 1998. I know I found one, and it was not that hard. How hard did you look? Were you only looking for commercial applications that would run under Windows? I know of at least one SW s/360 emulator that worked under DOS. I used it in the 80s to enter my work times into the s/360 mainframe that was used for timekeeping and payroll.Hercules:I CHALLENGE you that you cannot find one that is developed before April 1998. This is the key point in the Titor story.
I can tell you why he did not reply: He did not have to. You changed the subject, and were trying to avoid the fact that you made an incorrect statement (and used the word "impossible" to boot, a dangerous word to use). If you really, REALLY want MadIce to continue (and if he does it might make things a bit more difficult for you), I bet I can get him to come back and address some of your statements.Hercules:I wrote this because I wanted to find out whether MadIce could find a software emulator that can run on any PC like Hercules before 1998. But there was no reply from MadIce
Once again: MadIce was simply pointing out that what you had claimed was incorrect. Just because you cannot show you were correct does not somehow turn the burden of proof on to MadIce. MadIce proved you wrong. He does not have to prove you RIGHT. That is YOUR job, and that is exactly what the methods of science also say: It is YOUR job to prove you are right, not someone else's job to prove you are wrong! /ttiforum/images/graemlins/tongue.gifHercules:My question: Can you find an emulator SIMILAR to Hercules BEFORE 1998? There was no answer.
Pardon me while I wipe a tear from my eye after reading this wonderful story... :oops: You see, Larry Moss is one of my idols because he was one of the earliest, and most effective, SYSTEMS ENGINEER. And that is also my chosen profession. So I get a bit of a chill when I read about the huge successes in systems design that are part of the history of the systems engineering science that I am trying to build upon. Claude Shannon is another guy from that era that I would suggest you read up on. We are still only barely coming to grips with what Shannon's Information Entropy really means when it comes to exchanging Energy and Information seamlessly.THE BIRTH OF EMULATION
The concept of emulation was invented by systems engineer Larry Moss of IBM back in 1964 as part of the development effort behind the IBM System/360 family of mainframe computers. They were quite revolutionary for their day, being the first mainframes to use integrated circuits all the way throughout their design, which meant that programs hard-coded for older, transistorized IBM computers would not work with the new product line. Three approaches were tried by IBM - first, a series of computer simulations running entirely in software (sound familiar?), then next came the Moss proposal, and finally a straightforward firmware approach that resulted in the IBM 1410S (that sounds familiar, too). Neither of the two extremes would work with the System/360 product line, though - the "software simulations" were just too slow and the firmware approach used in the IBM 1410S was way too machine specific. There had to be a comfortable middle ground in there somewhere, and that is where Larry Moss stepped into the picture.
Moss used the word emulator to set his proposed project apart from the pure software and firmware approaches by others. His design "strove to be like" the real McCoy without actually being it (per the dictionary definition of the word), running the same programs at a comparable speed but on a completely different system. The actual emulator was a mix of hardware and software components, which worked in conjunction with each other to allow higher-end System/360 computers to behave as if they were an IBM 7070 mainframe, one of the top computers of its day. Moss believed then, as the passing years have shown, that the closer the hardware in the target system was to the system being emulated, then the better the emulator would function. This is why he chose the "combo" approach, as it offered the best compromise between portability and cost. It had only those hardware components that were really required for effective emulation at a decent speed , with the remaining issues being handled by the emulation software. Stuart Tucker, who was in charge of System/360 development issues, liked the idea and gave Moss the go-ahead. The rest, as they say, was history. The System/360 went on to become IBM's best-selling product line of that era, and the 7070 Emulator by Larry Moss was so successful that many customers were running their old software under emulation well into the early 1970s without a hitch. Thus it was that the technology known as emulation was born, as well as the three basic approaches to designing an emulator, and we owe it all to Larry Moss and his coworkers at IBM. For his achievement, Larry Moss is today considered to be the father of computer system emulation.
You are so very right, Creedo. The human body is currently the most intricate and complex device for transforming Information to Energy (and vice-versa) that we know of. Our bodies are amazing systems, aren't they?In response to Rainmans last say on the exchange of energy and information seamlessly. It's already been done.
Again, you are correct, Creeds. In fact, I do believe that one of concepts behind Systems Theory is that any system which closes a control loop (instead of operating in an open loop manner) is transforming Information to Energy. A further corollary to this is that the physical sensors that are used in any closed loop control system are devices that convert Energy into Information. The Information created by the sensor is what is used by the control system processing element to close the loop, and achieve a steady state output.The systems themselves, did it.
That statement as it stands is clearly incorrect, since HW emulation of the S/360 was all over the place. So then you indicate (and so you are claiming) that it was impossible to create a SOFTWARE S/360 emulator before 1998. That is even more problematic, for clearly if an algorithm can be represented in hardware, it can certainly be represented in software. That is, in fact, the definition of emulation. In fact, how about we review the history of emulation to find out why you are not only incorrect in your claim, but why it is that HW emulation was more popular in the 80s and most of the 90s than SW emulation...
Would you like to try to prove your claim about the possibility of HW or SW emulation of S/360 prior to 1998? It's OK to say you were wrong.
An important decision taken then, which would influence the progress of APL in ways that even now are not completely understood, was to hold back the source code and release only object code to customers.
No, I didn't. You were simply being challenged on one of the statements you made that you claimed supported your point. We call that a statement of foundation to support your point. And that foundational statement was not correct.But you should notice, that you missed my point.
Well, I am sorry that I HAVE to say you are changing the subject, because you are. This statement you make right here is not related to the subject of your claim that a S/360 emulator could not be produced before 1998. Really, they are two different things.Don’t say I am changing the subject here. All I wanted to know was how Y2K was fixed in OS/360 as Roger Bowler claimed it was very easy.
MadIce? You wanna jump into this at all? I mean, I don't want to use your name in vein, or anything like that! /ttiforum/images/graemlins/smile.gifMadIce still hasn’t responded to this thread.
So then you agree that the following statement you made is completely incorrect:I agree with you that there are hardware emulators in IBM and they used software emulation in IBM products. I agree with you there.
Hercules: But it was impossible to make an s/360 emulator before 1998.
OK< this is something completely different then. It has nothing to do with whether or not a HW or SW S/360 emulator could be produced before 1998.BUT the software emulator CANNOT be ripped from the ROMs due to a “specific lock†which no one understands except the IBM engineers themselves.
That is the reason why no Third Party OTHER than IBM can make a software emulator LIKE Hercules before 1998. Please note that I am talking about a Third Party software emulator that can RUN on ANY PC, NOT the ones released by IBM.
But how do we know that this statement you have made here is true? Are you certain that no one has ever "ripped from the ROMs", whatever you define that to be?