4 ms·
64 coder here too! The border changing thing has just reminded me how bad the development process was using the commodore assembler with a 1541 drive which was
by cesaref 4y ago
64 coder here too!
The border changing thing has just reminded me how bad the development process was using the commodore assembler with a 1541 drive which was horribly slow. assemble, dump image, reboot, crash, reboot, load assembler, try and work out what had happened :)
At some point I ended up with a PC running a system called, I think PDS, which was a cross assembler with dongle to push the image straight into the memory of the C64. I even think you could inspect and change memory on the running machine - it was amazing!
- jimsmart 4y agoYeah, we all used PDS too, although not originally. Pretty good system, particularly for that era, and cost/capability-wise (though they weren't that cheap, and folk eventually started cloning the boards for them, IIRC). I remember it was annoying to have only 8 main source files in PDS though, most big projects went past the 8 files of however many kb (although it could also handle include files, which was how one got around that limit). Although when I actually started out as a C64 games dev, my dev system was a BBC Micro B, linked to a C64. Not quite a cool as PDS, but it could assemble code 2x the speed of the C64 (the processor clocked twice the speed on the Beeb), and it was great having a separate 'host' system for development.
- jimsmart 4y agoHere's a link to info about the PDS kit, in case anyone is interested: https://www.cpcwiki.eu/index.php/PDS_development_system https://www.cpcwiki.eu/index.php/PDS_development_system