[Coco] 26-3022 disk interface question

[Arthur Flexser]

True.  You did mention that it was 16K, but it didn't register that of
course that meant no ROM to RAM copy.

Art

On Fri, Jun 12, 2015 at 1:30 AM, Barry Nelson <
barry.nelson at amobiledevice.com> wrote:

> Except that I am pretty sure it was mentioned in an earlier post that this
> is a 16k CoCo 2. If it had 64k of ram then that would work.
>
> On Jun 12, 2015, at 1:18 AM, coco-request at maltedmedia.com wrote:
>
> > Date: Thu, 11 Jun 2015 17:49:51 -0400
> > From: Arthur Flexser <flexser at fiu.edu>
> > To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> > Subject: Re: [Coco] 26-3022 disk interface question
> > Message-ID:
> >       <
> CA+LuDccPTQTkgODeXZWFv9OtmYnO4BGCzanwNBZzS2NK3yBM9Q at mail.gmail.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > Sure, you can't just load it in from cassette to the $8000 address it is
> > supposed to occupy.  But a cassette program could readily be written to
> > copy the Color Basic ROM to RAM, then copy the Extended Basic code to RAM
> > at $8000 (after loading a copy in from cassette to some lower address),
> and
> > then simulate a cold start into Extended Basic.  Probably not worth the
> > trouble to do so, though, since an adapter plus an EPROM, or an original
> > Extended Basic ROM, would do the job so much better.
> >
> > I recall doing something similar with Disk Basic when I still had a
> > cassette system, just out of curiosity rather than for any practical
> > benefit of having Disk Basic commands available with no controller or
> disk
> > drive for them to act on.
> >
> > Art
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
>