[GDL-0033A] GUILTY GEAR XX SLASH

Post dump information for NAOMI GD-ROMs here. See this thread for a how-to.

Moderator: Moderators

Post Reply
hotaru
Posts: 98
Joined: Thu Jun 28, 2007 8:41 pm
Location: twilight

[GDL-0033A] GUILTY GEAR XX SLASH

Post by hotaru » Fri Oct 24, 2008 9:36 pm

Code: Select all

________________________________________________________________
GD-ROM PART NO. [GDL-0033A]
RINGCODE: [GDL-0033A 10MS1 C 58]
________________________________________________________________

TRACK01.BIN 150 599 1058400
TRACK02.RAW 750 2882 5016816
TRACK03.BIN 45150 549299 1185760800

3
1 0 4 2352 TRACK01.BIN 0
2 600 0 2352 TRACK02.RAW 0
3 45000 4 2352 TRACK03.BIN 0

BKY0

"BKY0",   0x0000000, 0x0F000000

game (
	name "[GDL-0033A] GUILTY GEAR XX SLASH"
	description "[SEGA SEGAKATANA][SEGA ENTERPRISES][0EB4][GD-ROM1/1][J][0000000][GDL-0033A][V2.000][20050825][GUILTY GEAR XX SLASH][NAOMI][SEGA ENTERPRISES,LTD.][GUILTY GEAR XX SLASH]"
	rom ( name TRACK01.BIN size 1058400 crc C552E47F md5 1F93F05B24973370D75449D9C6B28F2A sha1 EF8CEA0ACBBB8352C68D04FE04C75BC0C2755D8B )
	rom ( name TRACK02.RAW size 5016816 crc FC3B5E15 md5 960FF95749321F67F2CECB76D0E2C288 sha1 CDA906A60B340447D8C8EE42E627373FCA8A52A6 )
	rom ( name TRACK03.BIN size 1185760800 crc 6D7C1BFA md5 D70730C20CFD34BD8A3AB83E0620E413 sha1 E032C2D6323E5A976DD9E2F8A54E6FA38276D2CC )
	rom ( name GUILTY_GEAR_XX_SLASH.CUE size 84 crc 148D0345 md5 B7AC8C53A719759C3825834972A7784C sha1 F29648CBE8E021D7AFE587041F260898CC27D88E )
	rom ( name GUILTY_GEAR_XX_SLASH.GDI size 87 crc 51CB9AA6 md5 288CF2EF6EE4A8DDEC2A1560CE939776 sha1 395712C58DA0D38F7B67080120AE4C0380A2E672 )
	rom ( name BKY0 size 251658240 crc 53662237 md5 0F77044FC9D01648052AED89037021FF sha1 D8E5180232401C09FCFF596BA319A48E56EF5295 )
	rom ( name BKY0.LST size 38 crc 26795F6A md5 E7A79D36F1FA3784E584A4BCCBABBD3C sha1 B157342615327F9D18EEB38D6FEA5A9BC8ED6917 )
)
dumped w/ Dreamcast MODEL No.HKT-3000 and httpd-ack v20071123 server.
User avatar
Maddog
is awesome
is awesome
Posts: 1345
Joined: Sat May 12, 2007 4:12 pm

Post by Maddog » Fri Jul 10, 2009 1:34 am

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.
hotaru
Posts: 98
Joined: Thu Jun 28, 2007 8:41 pm
Location: twilight

Post by hotaru » Fri Jul 10, 2009 3:22 pm

@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.)
AvS
Posts: 53
Joined: Tue Aug 26, 2008 10:26 am

Post by AvS » Sun Aug 09, 2009 1:42 pm

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.

thanks a lot, executter & maddog.
Post Reply