Re: Modern A2 successor

["Arkain" <rwking@no.usa.spam.net>]

**** **** <***@***.com> wrote in message
news:n%mf5.718$R43.110011@typhoon-news1.southeast.rr.com...
> Arkain,
<snipped>
>     Personally, I don't want emulation of a2 software, that hardly makes
it
> an 'apple'. A 6502 variant as a co-processor is almost as bad though. You
> could at one time buy a card for the mac or pc that was an apple2, and
this
> wasn't truly an apple either. Or if it was, it was horribly deformed by
> having that other computer attached to it. Though if this the only
possible
> solution...

Oh, but you misunderstand. I've only got 3 options to keep backwards
compatibility with the old A2 series:
    1) a coprocessor to handle the A2 stuff
    2) a newer 65xxx processor, possibly custom
    3) software emulation

3 isn't an option. 2 is unpalettable. That only leaves a co-processor.
Honestly, I'd prefer option 2, but that get's too expensive. Besides, I'm
not talking about software emulation, or even an all-in-one A2 card. I'm
saying that this new apple should be programmer friendly just like the old
apple, support everything the old apple did, and add newer, more modern
features on top of that. I'm setting up a backwards compatibility path that
doesn't depreciate the old design (too much). Using the 65816 as a
coprocessor gives me an option that even Macs and the GS didn't have, the
ability to run a native A2 app parallel to other applications with both
using the system in exactly the same fashion. You'll begin to understand
when I start posting the design sheets.

Arkain


> I would love to hear other's opinions too, even the goofy ones. Goofy
> opinions, not the goofy people.
>
> John
>
>