[Coco] mess newbie

[David Ladd]

The thing I have found with MESS is if you use any ROM image that has been
modified in any way that doesn't match the original ROM that has been
dumped out of the CoCo 1, 2, or 3.  MESS will complain about the ROM's not
matching its internal hash for them.

MESS looks by default for a zip file called by the name of the machine you
are trying to start.

Example if you are trying to start a CoCo2B you will need a zip file in the
ROM's folder that is called coco2b.zip which contains the ROM files.

I know there are a few sites that have the zip files on them so you could
download and put in the ROM's folder, but sadly you will have to google for
them as I myself don't have the links handy right now.

Basically though you should be able to do a google search for coco2.zip
coco2b.zip and coco3.zip  then just put those zip files in the ROM's folder
for MESS and it should be able to start.

I hope that helps you at this given time.
On Feb 12, 2015 3:05 PM, "Nick Marentes" <nickma2 at optusnet.com.au> wrote:

> On 13/02/2015 6:18 AM, Robert Hermanek wrote:
>
>> The old Keil emulator, which was always my favorite back in the day,
>> doesn't work on modern Windows... it seems VCC is also problematic. MESS
>> still seems supported, but I've never used it. What are the most basic
>> first steps for a windows user?
>>
>> 1) download latest MESS from mess.org and unzip into \mess
>> 2) what files/roms/etc do I need to have present?  In a subdirectory?
>> 3) what commandline to start mess.exe and launch a coco3 emulator?
>>
>> I'll start sifting through online docs, but thought if there are a few
>> very easy first steps to get a basic coco3 up and running, I'd be
>> interested in knowing.  Or is MESS not the way people are leaning these
>> days?
>>
>>
> That is exactly the process I followed and it failed. Added the ROM and
> ran the program but didn't work.
>
> Seems it's not so "plug-and-play".
>
> Nick
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>