On Saturday, June 15, 2013 at 10:49 PM, Gregg Levine wrote: On Sun, Jun 16, 2013 at 1:18 AM, Mark Pizzolato - Info Comm <Mark at infocomm.com> wrote: On Saturday, June 15, 2013 at 10:01 PM, Gregg Levine wrote: On Sun, Jun 16, 2013 at 12:51 AM, Mark Pizzolato - Info Comm <Mark at infocomm.com> wrote: On Thursday, June 13, 2013 at 7:47 PM, Gregg Levine wrote: On Thu, Jun 13, 2013 at 9:07 PM, Mark Pizzolato - Info Comm <Mark at infocomm.com> wrote: On Tuesday, June 11, 2013 at 8:42 AM, Mark Pizzolato wrote: On Tuesday, June 11, 2013 at 8:36 AM, Sampsa Laine write: This looks cool, anyone try it? http://www.9track.net/simh/video/ Hi Sampsa, How timely of you to observe this today. Just last night I got code pieces from Matt Burke (the guy at 9track.net) to add VCB01 (QVSS) support to the simh codebase for the MicroVAX I and MicroVAX II simulators. I'm in the process of merging that code and adding the necessary build mechanisms to the makefile as we speak. This will be cleaned up and visible at https://github.com/simh/simh in at most a couple of days.... For folks who build their own binaries, the latest github code has a VAXStation I and VAXStation II with the MonoChrome QVSS video capabilities. sim> SET CPU MODEL=VAXSTATION enables the video subsystem. The VAXStation I has a limit of 4MB of RAM, the VAXStation II has a limit of 16MB. The makefile should just build the right thing if the development support for libSDL is installed on your platform. Please provide bug reports and/or other feedback with issues created at https://github.com/simh/simh/issues There is a glitch in my scripts which build and package the windows binaries which is failing to build the simulators with video support, so folks who count on the Windows Binaries will have to wait until I fix this. The Windows Binaries (including VAXStation I and VAXStation II) are now available at: https://github.com/simh/Win32-Development-Binaries Download the latest zip file. Hello! Nice to know Mark. Any suggestions for implementing it on a Raspberry Pi system w/ 512MB of memory? I don't see any reason it wouldn't work as long as you've got the right SDL development pieces available. I did get the code outside of your screen idea to build properly. I'm not sure what this sentence means.... what does "code outside of your screen idea" mean? - Mark Hello! Oh sorry. I meant everything contained within the entire SIMH retrieval except for the screen presentation method. I think you are trying to say that all simulators except the MicroVAX I (VAXStation I) and MicroVAX II (VAXStation II) built. OK, that is expected. Numerous folks are running the latest code on Raspberry Pi systems. The QVSS video on the MicroVAX I and MicroVAX II simulators was just merged into the code base last week. If you can't get the MicroVAX I and MicroVAX II to build, I'm going to need more information to help. Please create an issue at https://github.com/simh/simh/issues to record the problem and to contain the details of chasing this down to a solution. Please Include the output produced when you attempted to build these simulators. Thanks. - Mark Hello! That's just it Mark. After using the git pull <repository name> command to pull everything into the source directory I chose, I then entered the created one, examined everything briefly, and then entered the command make and off it went. I first made the BIN directory, and then did that. I did need to build the Altair ones out of sequence however. Also the Nova one as well. I did not make the ones for the older IBM machines or the other simulators that I wasn't familiar with. I found that the screen thing needed the SDL library and I wasn't ready to massage the repositories that make up Debian on Raspberry Pi to find that one so I let wait. My only complaint is that when I ran the vax simulation to confirm that was all working, it then told me that the IDLE function was disabled, that was when I asked it about the devices. Hi Gregg, Nothing in the new codebase should have changed idle behavior (or availability) for any simulator. Please provide the output of "SHOW VERSION" in the simulator which isn't behaving as you want. The complete output produced when the simulator was built will also be useful. - Mark