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

[Albert Stinger]

I think I don't care what state rom is in because I have to make
sure Super Extended Basic is mapped in, so I can jump into the
EDITEX command. Should I save the rom mapping to put it back
when exiting the EDITEX command? I don't know yet, but hopefully
I will.

Looking at my EDITEX command patch to interface with EDIT
I see that the enhanced edit will be started with a input like

    this: EDITEX

    That's it that should put you into the enhanced edit command.
    Actually anything other then inputting a valid BASIC
    line number will get you there too.

<albertstinger24 at canada.com

> wrote in message news:d1v38b$i0l$1 at sea.gmane.org...

>I think I tackled the first part of a enhanced edit command.

> Interfacing with the old command. However, there are

> some questions before I can proceed. What is the state

> of the mc1& mc0 rom mapping if someone has a disk.rom

> plugged into the cartridge slot and then uses the edit

> command, is it the first state 0 & x ?

>

> MC1 & MC0 - ROM mapping

> 0  &  x  - Ext BASIC | BASIC | Cart ROM

> 1  &  0  - Ext BASIC | BASIC | Reset init | Sup Ext

> 1  &  1  -         32K  Cartridge ROM

>

> Albert Stinger

>

> <jdaggett at gate.net> wrote in message 

> news:424183A2.27863.12C4ADB at localhost...

>> Albert

>>

>> Now if you map the 8K space from $C000 to $DFFF as internal rom

>> and get rid of the author's picture you can recover about  7376

>> bytes. Otherwise you have about 1172 bytes give take a few. Could

>> be more depending on how much of the old DLOAD code is

>> patched and what isleft of it can be overwritten with a patch.

>>

>>

>> james

>>

>>

> -- 

> Coco mailing list

> Coco at maltedmedia.com

> http://five.pairlist.net/mailman/listinfo/coco

>