[Coco] mess newbie
David Ladd
davidwladd at gmail.com
Thu Feb 12 16:38:49 EST 2015
On Feb 12, 2015 3:23 PM, "Nick Marentes" <nickma2 at optusnet.com.au> wrote:
>
> On 13/02/2015 7:15 AM, David Ladd wrote:
>>
>> 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.
>>
>
> Thanks. Got it running.
That's good you got it going :D
>
> Now to get rid of that god-awful DOS front end!
Well I have to run it from the command line most of the time as I run with
a modified becker ROM file with offsets so I can use both HDBDOS and
Nitros9 on the same image.
Since MESS complains about the ROM image having wrong hash I have to over
ride it from the command line.
>
> Next challenge is the Windows GUI. I didn't like the screenshots I saw
but it was better than using that DOS front end.
>
>
> Nick
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
More information about the Coco
mailing list