Note to anyone that attempted to convert the MAME CHD to the checksums seen here and failed:
The audio track from MAME and hotaru's audio track have different checksums, but they seem to come from different ringcode discs.
I was able to convert the MAME audio to the hotaru checksum by rotating the bytes to a different offset using a custom tool that executter supplied.
This means that in all likelihood, neither of the dumps is bad. I won't be adding this one to the dats, since TOSEC rules don't allow to hack stuff to compliance if it doesn't match directly, but there are serious indications that there exist different ringcode versions of that game, which is a first for NAOMI discs. Sadly MAME ringcode is not known, so I can't really prove it. Until further proof is found or one of the dumps is verified, just keep in mind that the audio dumps are probably correct and data tracks definitely match.
@Maddog- received a few PMs 'bout TRACK02.RAW. i'm still w/o a computer here (until next week earliest) & teh dumping tools are loooong gone (don't loan out your gear kids) & to be replaced sooner than later so'll check my notes on the HD then... anywho, i'm going w/ i'm right & MAME's wrong 'bout the hashes for this track whereas our dumping meathod is concerned 'cos i donated the disc in question to The Dumping Project. http://maws.mameworld.info/maws/romset/ggxxsla hope that clears things up... raises some more questions.
btw, i must've this custom byte-rotating tool. (pretty please. sugar. cherries. all that jazz.)
Maddog wrote:The audio track from MAME and hotaru's audio track have different checksums, but they seem to come from different ringcode discs.
I was able to convert the MAME audio to the hotaru checksum by rotating the bytes to a different offset using a custom tool that executter supplied.
This means that in all likelihood, neither of the dumps is bad.
thanks for the information. using the CHD extraction method we obtain track02.raw CRC32 6ef6e618 & SHA1 f1c5e847c13f8496251337e5bb5e53224048b64f, then finally -using the offset tool with target crc FC3B5E15- we get a -452 offset corrected file...matching hotaru's hashes.