[Coco] Programs larger than 32K?

[Arthur Flexser]

That doesn't sound workable, because the variables you're copying include
things like the program's length.  You want to be able to have DIFFERENT
program's in the two banks that just share variable values, which are
stored after the end of the program, not in low memory.

Art

On Tue, Jan 22, 2019 at 8:51 AM Robert Gault <robert.gault at att.net> wrote:

> You could have a loader program that set up ALL RAM mode, copied the RAM
> from 0-$E00 to $C000-$CE00
> and then switched back to RAM/ROM. Then any software that switched banks
> would have all the Basic
> variables in each bank.
>
> Robert
>
> Arthur Flexser wrote:
> > Actually, I don't know for sure if the KEY264K used peeks and pokes to
> > share data between the two banks, and switched via interrupts.  I only
> know
> > the program from having skimmed some of its docs a long time ago.  But
> now
> > that I think about it, it seems to me that things could also be set up to
> > allow the two banks to both have access to the same Basic variables and
> > arrays, by manipulating pointers to the variable space so that they
> matched
> > up between the two banks.
> >
> > Art
> >
> > On Mon, Jan 21, 2019 at 10:17 PM Arthur Flexser <flexser at fiu.edu> wrote:
> >
> >> This switching of 32K banks is exactly what the KEY264K program does.
> >> They had it so you could either run 2 programs independently, each in
> one
> >> bank, or have the bank switching controlled by interrupts so that in
> >> effect, the two programs time-shared with one another and perhaps could
> >> access common data via peeks and pokes.
> >>
> >> Art
> >>
>
>