4 ms·
6502 was my first assembly, though we didn't have an assembler - we entered raw opcodes into the Epyx FastLoad monitor on the C64. You kids with your symbol tab
by classichasclass 2y ago
6502 was my first assembly, though we didn't have an assembler - we entered raw opcodes into the Epyx FastLoad monitor on the C64. You kids with your symbol tables and your fancy mnemonics.
a9 01 8d 20 d0 a9 93 20 d2 ff ...
When we got a KIM-1, we were able to write meaningful programs on it in a weekend, since we already had memorized all the hex.
- scarface_74 2y agoEven on the Apple //e you could “call -151” to get into the assembler and then type “!” to use the mini assembler
- djmips 2y agoNot on the Microsoft laden Apple ][+ - they removed that... :`( Only on the OG Integer ROM Apple ][ and then again on the later 1985 enhanced ROM //e
- kstrauser 2y agoI've forgotten so much of that, but I'll go to my grave remembering that LDA #97 JSR $FFD2 writes "A" to the screen.
- scarface_74 2y agoFunny. I still remember it $FDED on the Apple // series. But printing text out like that was really slow. For fast text printing you had to write to memory locations between $400-$7FF and deal with the non continuous memory block -> screen location mapping. It was even more of a pain with 80 columns when half of the text was in the main memory and the other half was the bank switched memory.
- kstrauser 2y agoOuch. That sounds painful. Yeah, I usually ended up writing to screen RAM at $400. It was convenient to let the kernal manage cursor position and all that, though.
- scarface_74 2y agoYeah, in 40 column mode, each row was separate by 320 bytes. In 80 column mode, each even character on a line was in main memory and each odd column was in the second 64K block in extended memory.
- kstrauser 2y agoI’m certain there was a good reason for that. Woz was an engineer’s engineer. But wow, I can’t imagine what it would’ve been.
- JoachimS 2y agoWhite border with a cleared screen looks good.