Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All ThreadsShow in Flat Mode*


SubjectRe: goodlynx 0.999.4 datfile Reply to this message
Posted byRoman
Posted on07/27/03 06:29 AM



> I think this has something to do with byte-swapped headers or something like
> this as I recall. I get the same thing with many of the GOODxxx sets ;)
>

The reason for this is:

The Good*** Tools don't care about possible headers. ClrMamePro does. For most datfiles you need your roms headerless. The datfile information (romnames + crc32 values) are directly taken from the goodtools binary itself. So it's correct. It's just that ClrMamePro doesn't skip possible headers and so the crc32 is calculated not over the pure romdata but also over the header. Removing the romheaders manually or by a tool which cuts off headers will fix your roms.

GoodLynx (and some others) are an exception. These roms seems to NEED the headers and the belonging datfile was created on an existing collection and not on the imported data from the goodtools binary. So you simply need the exact roms which were taken for the datfile creation.

Roman Scherzer
ClrMamePro

-
Entire Thread
Subject  Posted byPosted On
*goodlynx 0.999.4 datfile  Discord07/26/03 03:12 PM
.*Re: goodlynx 0.999.4 datfile  jmmijo07/26/03 04:06 PM
...Re: goodlynx 0.999.4 datfile  Roman07/27/03 06:29 AM