[Coco] [SPAM] Re: Multipak redesign/replacement / New CoCo...

[Louis Ciotti]

The thing for me would be the vintage hardware that you cannot use in an
emulator.  Joysticks would be a prime example.  To me the physical hardware
is part of the retro experience.  While I do use emulators, it just feels
"better" to be on the actual hardware.  Connecting a cartridge and
inserting a floppy, having to swap disks is all part of the experience to
me. But i am sure I am in the minority.

On Mon, Feb 23, 2015 at 12:34 PM, Zippster <zippster278 at gmail.com> wrote:

> At what point have you moved so much of the functionality to FPGA/CPLD and
> the like
> that you might as well just be running an emulator?  Or just have it
> completely emulated in
> an FPGA on a board with retro-compatible connectors for old peripherals?
>
> Serious question.
>
> - Ed
>
>
> > On Feb 23, 2015, at 11:23 AM, Steve Batson <steve at batsonphotography.com>
> wrote:
> >
> > Seems to make sense to use current, available technology and parts to
> simulate functions of older, hard to obtain components.
> >
> > Maybe even have some hooks into the system that allows enhancements to
> the CoCo by allowing it switch modes.
> >
> > Steve Batson
> > Batson Photography
> > "Today's Special Moments, Tomorrow's Priceless Treasures"
> >
> > Website: http://www.batsonphotography.com
> > Blog: http://www.batsonphotography.com/blog
> > Our Free Photography Site and Forum:
> http://www.digitalphotographerzone.com
> >
> >> On Feb 23, 2015, at 9:13 AM, Mathieu Chouinard <chouimat at gmail.com>
> wrote:
> >>
> >> 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?
> >>
> >> --
> >> 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
>