Earlier quoted context omitted.
It's not "paper tape" (that's a digital storage medium), just a printout. And the numbers in the left half are not actually part of the source file, they are line numbers and machine code output produced by the assembler. You'd probably better not waste time transcribing them. Not trying to dissuade you, but here's some things you should consider: • Turn off your spell checker, it will only make this more difficult!…
There are PDP-10 emulators with well-maintained copies of the different operating systems for them, so someone could check that the typed up source can be assembled.
I'm manually transcribing the AltairBASIC source, ten lines a day starting today
41–47 of 47 posts
Re: I'm manually transcribing the AltairBASIC source, ten lines a day starting today
#42Re: I'm manually transcribing the AltairBASIC source, ten lines a day starting today
#43Re: I'm manually transcribing the AltairBASIC source, ten lines a day starting today
#44No AI or OCR here, just an idiot with too much free time. After seeing that the AltaBASIC source posted was a scan of paper tape , I thought having it in a digital document proper would be good for preservation and novelty's sake. I've never written Assembly, and I'm not a typography expert! Feel free to point and laugh at any silly mistakes. Let's see how many days it takes!
I recruited a team to transcribe a particularly important document, and I had us type each page to catch typos.
Re: I'm manually transcribing the AltairBASIC source, ten lines a day starting today
#45Gates and Allen used (stole computer time) at Harvard's PDP-10 and other computer resources in developing this proprietary code.
Re: I'm manually transcribing the AltairBASIC source, ten lines a day starting today
#46No AI or OCR here, just an idiot with too much free time. After seeing that the AltaBASIC source posted was a scan of paper tape , I thought having it in a digital document proper would be good for preservation and novelty's sake. I've never written Assembly, and I'm not a typography expert! Feel free to point and laugh at any silly mistakes. Let's see how many days it takes!
If you've spent 7 days so far and got as far as "F3", I wondering if this is actually some kind of elaborate troll. At the rate of one byte per week, you might finish transcribing the 4K ROM within 8 decades.
Interestingly, the large F3 appears to be a batch number for the print job, so it's just coincidental that it's the same as the first byte in the ROM. The first byte starts on line 732 and printed in octal not hex, so "000363" (the first byte of the output seems to be some kind of markup for addresses in multi-byte opcodes (immediate loads seem to have 000 for these).