Skip to main content
Retrocomputing

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    At a certain point, I agree that doing the actual coding on a modern system will save a lot of grief, but part of this is actually a nostalgia thing, so I want to work inside the Apple IIe for now at least. Thanks for the detailed answer, though! Commented Mar 23, 2020 at 23:59
  • @AlGorithm That's perfectly fair! For your use case, I would start with the first two examples I gave (Easy 6502, which even ends with implementing a (very) simple game, followed by a bit of EDASM). My post on EDASM gives links to a disk image and the manual I uploaded to archive.org, as well as some hints to get you going on that. From there you might go with a more advanced (1985-level rather than 1979-level) assembler hosted on the Apple II, or move on to cross-development. Commented Mar 24, 2020 at 1:09
  • 1
    For comparison, here's what John Brooks was using for Apple IIgs development under Mac OS X: groups.google.com/d/msg/comp.sys.apple2.programmer/tw902RdWxBE/… . Using Merlin on the Apple II may be beneficial as the code can often be cross-assembled with Merlin 32 without changes; at the very least you won't have to learn a new assembler when moving from retro-assembly to cross-assembly. Commented Mar 24, 2020 at 14:51
  • @fadden Thanks for that link! There's further information here and here, too. I wouldn't worry too much about learning a new assembler, though; that's not difficult and often enlightening. Commented Mar 24, 2020 at 23:25