Image Map Image Map
Page 13 of 13 FirstFirst ... 3910111213
Results 121 to 128 of 128

Thread: Honeywell 200 resurrection

  1. #121


    I did some work on punch card data processing equipment, although not the 129 Keypunch machine. You can see that here:

  2. #122
    Join Date
    Jan 2007
    Pacific Northwest, USA
    Blog Entries


    Very similar to the IBM 1620 and 1401, but in particular, the 1620.

    Fields and records, addressed respectively, from the low-order position and from the high-order position.

    On the 1620, there's no way to directly (or indirectly) read the P-counter, though, I suppose, it's possible to guess it by modifying instructions. The calling sequence generally looked like.

    Exit: Branch (filled in by caller)
    Branch to Exit

    The 1620 did have a "hidden" register that would save the location of the next instruction before a "branch and transmit" instruction was executed, but said register was operated on only by the "branch back" instruction, which made the facility useful only for a single nesting level.

    The subroutine calling method was shared by quite a number of machines, including the CDC 6000-7000 supercomputers. ("Return jump" instruction). PDP-8 certainly uses that as well.

  3. Default

    Quote Originally Posted by durgadas View Post
    I have setup a project page for my effort. There is a download page linked from there where you can get the "jar" file for the virtual H2000. I'm still hoping to find folks that can help, with either more details on how the machines operated or with code to run.
    Cool! I'll be trying your emulators.

    Looks like the FORTRAN manual you posted ( is the next edition of the one I mentioned upthread. I have not scanned mine yet.

  4. #124


    I should note, that the FORTRAN manual is just a redistribution from bitsavers - for convenience sake. Not a personal collection or otherwise unavailable document. Same goes for nearly all documents I post.

    Also, a disclaimer about my FORTRAN and EasyCoder emulations. Neither is a complete implementation of the respective language. I implemented enough to (hopefully) make them useful. Plus, some features require more information, that I don't yet have.

  5. Default

    Pardon my Java noobness, but when I try to run CardPunch.jar, I get the error: "Could not find the main class. Program will exit." My JRE is version 6, which came with the Arduino IDE. Am I doing it wrong?

  6. #126


    I'm pretty sure the problem is Java version. I compiled on Java 8, but used backward-compatibility options for Java 7. Java 6 is very old. The error message is odd, and not very helpful, but I would not expect that JAR to run on Java 6. Can you get Java 7 or 8?

  7. #127


    I have just received a scanned copy of the H200 Main Memory Setup Manual from a contact in Switzerland. This is a very useful document for me as it isn't just a field engineer's guide but the full 49 page instruction manual for setting up the memory when it is first built. Hence it's exactly what I need to ensure that I adjust the unit for optimum reliability ... if it works at all of course. That's yet to be discovered. Some of the driver boards definitely aren't working correctly at present, so it may be a while before I know.

    Rob -
    The Internet is a winch to get your project off the ground ... but always have a parachute handy.

  8. #128


    I have now installed an Arduino Mega 2560 board as a temporary USB interface between the memory unit buses and a PC, so yesterday I was able to run dynamic tests on every memory location in the two magnetic core stacks to verify that they are fully functional, which they are. These stacks were salvaged from a scrap heap decades ago and were just static mementos until now. Knowing that they are in full working order is an incentive for me to get on with the project work this year. There is much more to do before I can actually store data in the memory unit but this is a positive step forward and good news.

    Before I ran the read-write tests I dumped the existing contents of the memories. Magnetic core memories retain data persistently, so there was still data present from the last time that the computer that originally contained them was used decades ago. Although the data was still readable it wasn't possible to extract any meaningful information from it. In fact it was so ingrained into the magnetic cores that it took several read-write cycles to erase it entirely. For a while I thought that the stacks were faulty, but they just needed some exercise after being inactive for so long. At my age I know how they feel sometimes, especially just after the Christmas holiday.

    A Happy New Year to all at VCF.
    Rob -
    The Internet is a winch to get your project off the ground ... but always have a parachute handy.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts