[Coco] Re: Re: Re: CoCo related question? (Better edit for coco3.rom)

[Albert Stinger]

Thanks for the tip Robert. I'll look at the graphic routines for examples.
Yes, I patched Edit to be the place where interrupts and turning on/off
rom is being handled. The edit command calls basic at certain points
and what I think is I'll need a jump table in edit to turn on/off the roms.

Albert

"Robert Gault" <robert.gault at worldnet.att.net> wrote 
in message news:424A1CAE.8060005 at worldnet.att.net...
> The best approach would be to have a small amount of code inserted into 
> the Edit command to turn off interrupts and switch to internal ROM mode. 
> Then you new code can do its work and jump back to the Edit patch. The 
> Edit patch would then return to RAM mode and restart the interrupts. You 
> can use the Super Extended Basic graphic routines as a model for this 
> approach.
>
> Ultimately, your new ROM code should patch Edit on startup to add new 
> vectors. That may be what you are now doing.
>
> Albert Stinger wrote:
>
>>  My thinking
>> is to run it from the rom shown above and that way it won't interfere
>> with any patches to the All RAM mode.
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>