[Coco] What is the next "step" in my education?
Robert Hermanek
rhermanek at centurytel.net
Fri Jun 24 16:04:32 EDT 2016
Personally, I would get a pdf of the EDTASM+ manual, I'd get a copy of
either disk Edtasm or a cartridge if you're doing the cassette thing,
and I would just start with some very basic assembly language
programming. I started small back in the day -- learning how to use
registers, basic counting/loops, basic "pokes" via STA, STB, etc, for
displaying characters on the old 32 column screen, and eventually
learning how to call a few ROM routines from assembly, I think a few are
mentioned in the Edtasm manual, like waiting for a keystroke, or
printing a character to the screen, that sort of thing...
-RobertH
On 6/24/2016 12:50 PM, John Lochey via Coco wrote:
> Hi all,
> First off, thanks to everyone that has been a huge help to me so far!
> I have decided to focus on my CoCo2 and I have ordered an SDC (SD card reader) and case for it.
>
> Okay, I kind of asked this question awhile ago, but I want to reframe it.
> I'm looking for your suggestions on the next "step" in my education...
> I have read and worked through the Extended Basic Manual that came with my CoCo2 and found it very interesting... but I was left wondering what the next "step" is?
> Anyway, I have been working through the Rainbow magazines and have been learning a lot, but so many questions come up from the examples that I read like:
> - how does one learn the memory map of the 6809?
> - I see magazine examples and think, "why/how did the author know how/where to POKE/PEEK in that memory location", etc?
>
> - I'd like to POKE/PEEK around and try some stuff, but don't really know where to start, or what is where in memory.
>
> - what is the best way to experiment with more advanced BASIC, PEEKS and POKES, and ???
> I have been looking that the following books:
> - Color Computer Graphics - William Barden- Ultimate Color Computer Reference Guide and Toolkit - CMD Micro
>
> But I'm open to suggestions.
>
> Thanks and sorry if this is too vague!
>
>
>
> John
>
More information about the Coco
mailing list