[Triforce] GDROM BOOT UPDATE [GDT-0011]

Post dump information for NAOMI, NAOMI 2, Chihiro, Triforce GD-ROMs here. GD-ROM media only. See this thread for a how-to.

Moderator: Moderators

Post Reply
User avatar
Posts: 261
Joined: Mon Apr 18, 2016 10:15 pm

[Triforce] GDROM BOOT UPDATE [GDT-0011]

Post by majorpbx » Sat Oct 12, 2019 12:28 pm

The MAME-SHA1 does not match MAME so either this is a bad rip or MAME is off. I'll leave it to the MAME experts for that determination. I wouldn't be surprised if my disc is off as it does have some scratches.

Media ID: 1F7C
Media Config: GD-ROM1/1
Regions: J
Peripheral String: 0000000
Product Number: GDT-0011
Version: V1.000
Release Date: 20031110
Manufacturer ID:
Mould SID Code: IFPI 39B7
Inner Ring Code: GDT-0011 1MS1 C 3Y
Mastering SID Code: IFPI L223
PIC Outer Label:
PIC Chip Stamp:
PIC Chip Type: PIC16F628A-1/P
PIC DES Key: E0B9043E4C4F40BC (Worked for me though not sure it's original!)

Hardware: Dreamcast USA HKT-3020 (1) with Broadband HIT-0400
Software: httpd-ack-20080711 on Windows 10 with Chrome, and custom PowerShell script

Code: Select all

1 0 4 2352 track01.bin 0
2 600 0 2352 track02.raw 0
3 45000 4 2352 track03.bin 0
disc.gdi size 87 crc 468c1495 md5 346fea58ab1a55c577138c5b04319157 sha1 980036e44ad9d694ea1699cd05c86ccd0c894c47
TRFBU_Unencrypted.bin size 7274496 crc dc72709a md5 4b2059e21901e847541bbdb558282cbb sha1 ef8a14e8b9950e863b8e8d7b316285759042a041
TRFBU_Encrypted.BIN size 7266816 crc fd257337 md5 405ad15e3d2461c85b3667603597392b sha1 9e236cda92ed93762582744de9e1b8effc1d726e
GDT-0011.chd size 15326123 crc 2b603003 md5 e2307dac2d7acfdfdbf9820e59abe545 sha1 9067cab1d840b06b65d772c0d343d932d43dc4a2 MAME-sha1 fbfd7960ca7070721e25c08ccc428a2e0cf4766f
track01.bin size 1058400 crc 195a3b84 md5 e289b7e283f63e9e922e8ffb2c9629a8 sha1 17842e4044c7f15018301ee86dbc087a0ef93fc3
track02.raw size 3179904 crc 288f3d54 md5 63cd7feee11bcbe7aac7e3737c84a976 sha1 51215f79c15584d9885ab49df675e3effaf43000
track03.bin size 1185760800 crc 389c43da md5 f6c544107359ea96672a632e2bc38add sha1 6c47202165009c173f5a70a851d6bdb5f383faef
User avatar
is awesome
is awesome
Posts: 1478
Joined: Sat May 12, 2007 4:12 pm

Re: [Triforce] GDROM BOOT UPDATE [GDT-0011]

Post by Maddog » Fri Oct 25, 2019 1:00 am

A pretty good way to see if your dump is good is to redump it 1-2 more times. If hashes are consistent, it is extremely unlikely that your dump is faulty.
To possibly save some work, try first the track02.raw, as audio tracks are far more prone to errors than data tracks. Any time I had a problem audio track, checksums would change EVERY time I dumped the track again (it's the nature of error correction in audio that makes it behave like that). If you arrive at this crc 288f3d54 3 times in a row, then its' solid IMHO. If it changes, you know what is wrong already.

On the other hand, data tracks usually come back with an obvious error message when faulty, but as there have been historically a few cases where the dump finished but the hash was off, it is worth trying to dump those another couple of times too, but only after you are sure your audio track is correct.
User avatar
Posts: 261
Joined: Mon Apr 18, 2016 10:15 pm

Re: [Triforce] GDROM BOOT UPDATE [GDT-0011]

Post by majorpbx » Fri Oct 25, 2019 10:00 am

Thank you for the knowledge, it will help going forward. I thought it was odd as the tracks were perfect but the generated CHD SHA1 did not match MAME's SHA1. MetalliC contacted me and he verified the dump is good and turns out MAME was wrong. My updated dumping method turns out to fix all the initial bad track issues I experienced all the time when I first started.
Posts: 11
Joined: Sun May 18, 2014 3:05 pm

Re: [Triforce] GDROM BOOT UPDATE [GDT-0011]

Post by MetalliC » Fri Oct 25, 2019 10:40 am

right, GDT-0011 dump from MAME had bad sectors.

speaking in general, I'd say it is enough to dump data tracks once and check them using "EccEdc" or similar tool, if there will be no errors - I see no good reason to redump these tracks.
only audio tracks should be dumped several times to make sure sectors was dumped stable same.
Post Reply