[Coco] Assembly .BIN -> .CCC/.ROM = SOLVED!

[Chad H]

Having often-played .BIN files on a .ROM is of value if you don't wish to
find a floppy and wait for it to boot, that's if you even have a floppy
drive.  Driverwire is no faster and requires external components.  Is the
CoCoSDC available?  How does the cost of it compare with loading several
.ROM's on a cheap EPROM board compare in value?   These are all things that
can't be fixed but depend on the desires and needs of the user.

-----Original Message-----
From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Nick Marentes
Sent: Friday, September 05, 2014 6:38 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] Assembly .BIN -> .CCC/.ROM = SOLVED!

I would also question the value of being able to run game roms.

Every game that appeared on rom is now available on a standard dsk image.

You can access these with Drivewire or if you have the excellent CoCoSDC,
put all your disk images on the SD cart and access there.

With the CoCoSDC you can store every file created for the CoCo in the one
cartridge.

Nick


On 6/09/2014 9:13 AM, S Klammer wrote:
> I wish every success and enjoyment with a project such as this.
>
> As a product (IMHO), something like the CocoSDC (
> http://cocosdc.blogspot.ca/) has more functionality.  As a floppy 
> controller it functions like a charm and I'd certainly hope that more 
> will be produced and/or even more functionality is added into a new
version.
>
> It has eight 16K flash banks that could be used for alternate DOSes or 
> ROM carts... and as with SDC-DOS, a "Game Selector" ROM could be 
> written into one of those banks, accessing the SD card to load in ROM 
> images 'on the fly'.  Or, just load your 7 favourite ROMs and use
RUN@<banknumber>.
>
> Shain
> On Sep 5, 2014 6:23 PM, "Kandur" <k at qdv.pw> wrote:
>
>


--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco