betpet wrote:
I agree. I used to type in all capitals because I couldn't always tell if it was a 1 or I, O or 0, or even 8 and B in places. No wonder I had such a hard time debugging.
Is there a particular issue or two you want typed up? I'm up for a bash
Well
this webpage shows what's missing - Typeins from Issue 5-15 aren't currently being worked on. I'm working on Typeins from Issue 16. At the moment that webpage is only up to Issue 24, so anything between Issue 18 and 24 isn't being worked on.
I've got most of the programs from Issue 16 working, but now I've got this horrible Machine Code program which I cannot seem to find the bug. I think the problem is like what you said - "B" could be an "8", machine code data lines don't use "l" or "i" because their Hexadeciminal opcodes ("0-9" and "A" to "F"), though it's annoying because I was one digit off the correct checksum code and haven't been able to track it down!

I've disassembled the program and found one error with it, though haven't been able to track down what the others could be (because it still doesn't add up properly with the checksums!). Even more annoying because it doesn't tell you which line the fault is.
What I found to be easier was to type in the program in Winape, and have the Type in onscreen and blowup the picture which makes it a bit easier to read and work out what's what, but beware the typeins with machine code routines in them cause you'll be pulling your hair out!