Re: Caution on AP-64E EPROM Programmer

["Mark Cummings" <NOTfigjams@primus.com.au>]

"Marsha" <menacechgo@aol.com> wrote in message
news:Xns9356B28E0DAFDmenacechgoaolcom@206.141.192.32...
<snip>
> Depending on what assembler you use to reassembl the code, you would need
> to define origin, register size and mabey even convert from Object Module
> Format to straight binary file.

currently I have disassembled the code using the ORCA/M v4.1 Assembler using
a //e. The source file created only just fits in the available RAM. I'm not
sure if I'll have room to make comments without breaking the code in half.

One problem/question I have with ORCA/M...
Is it possible to disassemble the code as if were located elsewhere in
memory ?
For example: I copied the Expansion ROM off the card from $C800..$CFFF down
to $2800.$2FFF while the Expansion ROM was still active, saved that to disk
then disassembled that. This was necessary because of the way that the Apple
expansion cards have to disable the expansion ROM when first accessed. This
includes the disk interface, which is used during the save process. The
unfortunate side affect is that some absolute jumps are no longer correct.
ie a JSR to $CA96 is still the same after it is relocated, however the code
has moved. Obviously if I re-assemble it with an ORG of $C800 things should
be OK, but if I modify the code later, there will need to be a lot of
editing.

Any thoughts or workarounds ?

Mark