lazybasic VS virtualagc

I wrote a script that builds seamless background images out of sets of smaller images, kind of like contact sheets. This started for a comic book themed web site so that the background image could be a collage of comic covers with a special theme ( Christmas, celebration of a comic artist, ...etc. ) I am still cultivating the script so that it'll be friendly enough for public use. I'll place it on Github when that happens.

I like to tinker with my own compilers / interpreters. I had read an article recently about someone building an example Linux shell and I wanted to try a couple of ideas where I thought I'd take a different approach than the author. I ended up building a very, very tiny BASIC interpreter in C. My proof that the interpreter was "good enough" was whether or not I could write a script in the dialect of BASIC to display the lyrics to the song "The Twelve Days of Christmas."

https://github.com/jimlawless/lazybasic

I don't think that's a great example.

For instance, I can step through and even modify that code using tooling like AGC emulators like this one http://www.ibiblio.org/apollo/#gsc.tab=0

What makes it open source is access to the same level of source access that the original developers worked in.

That's what's missing here. Mistral's engineers do not simply open this binary in their editor to do their job.

Glad you're enjoying the videos! I'm Mike from them. :) The Apollo 14 code I linked above was reconstructed in the same way as Luminary 69/2, but the process was far, far too involved for a video. Like I said above, I probably won't be much help with math, but I'd be more than happy to assist with finding documentation or navigating AGC code whenever you want!

The fact that all the information about the computer and software is public and you can verify it yourself like thousands of people have. https://www.ibiblio.org/apollo/

If you’re curious about the the technical specs of the AGC check out Ron Burkey’s website, it’s even got the source code for you to see for yourself: https://www.ibiblio.org/apollo/

Of course you should be able to tell us because all the hardware architecture and software can be found here. So you must have fully reviewed it and located the issues. Right? Than please point out where the error is.

It had manually encoded ROM in the form of "core rope memory", which is pretty wacky, but it was a digital computer. In fact, it was the first IC computer.

You can learn way too much about it and even operate (a simulation of) one here: http://www.ibiblio.org/apollo/