[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bill G's status?



On Sat, 14 Aug 2004 17:16:15 -0400, Bill Garber wrote:

> 
<snip>
> Glad to hear it. Now could you tell me what the hell version
> those Docs are for????  :o)  I can't get the one I'm using to
> do anything and I've printed them out already.  LOL
> 
	The third page (near the start of Chapter 2) states the manual is for the
DOS 3.3 version. Although I was after the ProDOS version, this one got me
going.

Quick reference:
	There are only two modes to care about. It's not as complex as the manual
suggests, but the arrangement is a bit screwy.

	The first is the command mode. This lets you do system level stuff. The
commands are listed so there are only three of them requiring an
explanation.

	The source (the file is appended with a .S) and object (binary) file are
saved separately. The object needs to be compiled first (more on this
later).

	The second mode is the editor. Started by the "E" key from the command
mode.

	To create some source press the "A" key. This is sort of a full screen
editor. Normally we are used to using the <TAB> key to move from field to
field. This editor uses the <SPACE> bar. The arrow keys also work.

	In ProDOS there are a couple of important changes. <APPLE-Q> quits.
Either <APPLE-D> or <APPLE-K> will delete a line.

	Apart from ORG I haven't tried out any of the other pre-processor
commands.

	There should be a way to access 65C02 encoding. I haven't found it. The
assembler defaults to 6502 encoding. This means instructions like BRA,
PHX, and PHY won't work.

	After you have some source, exit back to the editor mode. Type "ASM" to
assemble the code. Take care of any bugs. Then go back to the command
mode. Save your object and source as necessary.

	There are probably things to make life easier, but this should be enough
to get you up and running...

				Later
				Mike