[Coco] Multipak redesign/replacement / New CoCo...

Mathieu Chouinard chouimat at gmail.com
Mon Feb 23 12:13:40 EST 2015


could always use a fpga for those
Mathieu

On Mon, Feb 23, 2015 at 12:12 PM, Louis Ciotti <lciotti1 at gmail.com> wrote:
> Wouldn't the problem with a new mother board be access to the older IC's
> namely the VDG and the 6809 itself?  These are not exactly stock components
> anymore.
>
> On Mon, Feb 23, 2015 at 12:03 PM, Zippster <zippster278 at gmail.com> wrote:
>
>> I would love to do this, and probably will give it a try with a CoCo2
>> replacement once I wrap up
>> a couple other projects, as it looks fairly straightforward.
>>
>> With the CoCo3 the problem would be decent documentation on the GIME.
>> From what I understand, it will have to be reverse-engineered based on
>> behavior.
>>
>> - Ed
>>
>>
>> > On Feb 23, 2015, at 10:52 AM, Steve Batson <steve at batsonphotography.com>
>> wrote:
>> >
>>
>> <snip>
>>
>> > Wouldn't it make more
>> > sense to focus on creating a new Fully CoCo 2/3 Compatible Motherboard
>>
>> <snip>
>>
>> > --
>> > Coco mailing list
>> > Coco at maltedmedia.com
>> > https://pairlist5.pair.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco



-- 
A te quaeso, sicut in Aeneidos libro quarto Aeneas, elocutus
desiderium erigendi suum obeliscum in templo Venereo Didonis, ab ea
quaesivit, tuae domi an meae?


More information about the Coco mailing list