3 ms·
Nasir Gebelli was a game programmer that created some of the classic early games for the Apple ][ (Space Eggs, Gorgon). He eventually went on to create Final F
by joezydeco 13y ago
Nasir Gebelli was a game programmer that created some of the classic early games for the Apple ][ (Space Eggs, Gorgon). He eventually went on to create Final Fantasy at Square.
When programming his games in 6502 assembly for the Apple, Gebelli used the built-in mini assembler from the command line. No text editor, and according to most accounts no printer either. All in his head, by hand.
- vidarh 13y agoI don't know the Apple mini assembler, but that sounds similar to what I meant. Either we'd load a tiny "monitor" which is what they were typically called in the Commodore world at least, and you'd have a primitive REPL with commands like ".D C000 C100" to disassemble addresses 0xC000 to 0xC100 or ".A C000" to get a prompt with the address 0xC000 after which you could enter one instruction, press enter and have it instantly assembled and get the next address (with no support for labels). If you needed to correct something, you'd press enter to exit back to the prompt, type ".A [address to correct] [new instruction]" and hopefully you wouldn't need to alter the length of the instruction as then you'd have the fun task of remapping absolute addresses and copy the following code around. Then when you wanted to test something, you'd do ".G C000" and hope your program didn't crash things so bad you had to load things back in... Scarily enough it was common at least in demo circles to not even save before each test as it was too slow with a tape or floppy and so we just hoped we wouldn't lose changes too often from bugs overwriting our program etc. Often not all variables might even be reinitialized on starting the program again either, and so the program might differ depending on test runs... When we saved the programs it was often just a raw memory dump of the locations we'd assembled stuff to... (e.g. .S "filename" C000 C3FF might save the 1K range from 0xC000 to 0xC3FF) (I keep using C000 by habit, even after 25 years or so away from the C64 - 0xC000 to 0xCFFF was free space in between the BASIC ROM and memory mapped registers for the graphics and sound chips, and BASIC would not touch memory above 0x9fff, so putting stuff at 0xC000 was popular since you could e.g. load basic programs without wiping it)
- 300bps 13y ago>I keep using C000 by habit It's been over 25 years since I last programmed in Assembly on my Commodore 64 but I will never forget typing: SYS 49152
- cgh 13y agoYes, the starting address of the 4KB of "protected" memory that we'd poke our assembler opcodes into. All us C64 programmers (loosely used term in my case, I was ten years old or so) have that address burned into our brains forever.
- lurkinggrue 13y agoSYS 64738
- geocar 13y agoThe Apple II had a monitor you could reach via: ]CALL -151 and you could type a program such as: *300:AD 30 C0 88 D0 FD 4C 00 30 but while there was a disassembler (300 L) there was no assembler! Fortunately, if you had Integer Basic, you could do: ]INT to get to Integer basic, then go into that monitor: >CALL -151 then jump into the "mini assembler" inside Integer Basic: *F666 G and now you're in something resembling an assembler: !300:LDY#$0 !302:JMP$309 !305:JSR$FDED !308:INY !309:LDA $320,Y !30C:BNE $305 !30E:JMP$FF65 !$320:48 45 4c 4c 4f 20 48 41 !$328:43 4b 45 52 20 4e 45 57 !$330:53 21 00 !303G