[Coco] CoCo memory map WAS EDTASM Memory Map

[Robert Gault]

Stephen,

I told you exactly what you are asking. If you enter O in the EDTASM editor without any source code 
having been loaded, you will see under FIRST the lowest available memory and under LAST the highest 
available memory. Obviously as you add source code, FIRST will increase to indicate the size of the 
source code.

EDTASM runs in all RAM mode but will switch to RAM/ROM if any of the Basic ROM code is needed by the 
program. That means you can overwrite the ROMS if you want and test the changes with ZBUG.

So your code could be placed between FIRST and LAST but will not work when EDTASM6309 switches to 
RAM/ROM mode to use some of the ROM code. In sort, you will need to run tests to see if you can 
interface with EDTASM6309.
 From what you have said so far, I'd guess your code won't work. You would do better with an RGB 
monitor connected to your Coco3.

Robert

Stephen Pereira wrote:
> Robert and Barry, thank you very much for your responses.  You are not quite getting what I’m trying to ask.  Sorry for not being able to explain myself properly.
>
> My remote I/O code hooks into the CONSOLE input and CONSOLE output ROM routines, in order to provide keyboard input from and screen output to a remote terminal, along with the CoCo keyboard and screen.  This code can run at $7800 if I’m using DECB.  It also can run at $1800 if I am using Color Forth.
>
> I would like to use this remote I/O code along with EDTASM, so I can clearly read the 80 character lines on a remote terminal.
>
> Where in memory can I place this code (about 300 bytes) while using EDTASM, without having EDTASM clobber my code, or having my code clobber EDTASM?
>
> Thanks very much for listening!
>
> smp
> - - -
> Stephen Pereira
> Bedford, NH  03110
> KB1SXE