[T-8107N] Fur Fighters

Post your NTSC-U dump information here. See this thread for a how-to.

Moderator: Moderators

Post Reply
-=FamilyGuy=-
Posts: 20
Joined: Mon Sep 24, 2007 3:29 pm

[T-8107N] Fur Fighters

Post by -=FamilyGuy=- »

Here's my second 2352 DUMP for the Dumpcast, I hope it'll help to verify some games !!

It's dumped with the Parallel port ripper, a 25¢ 100kB/s ripping cable that can rip in data/2352 mode!


Name: Fur Fighters
Region: NTSC-U
Publisher: ACCLAIM
Box ID: T-8107N
Ringcode: *3S* T-8107NB B7 B
Barcode: 0 2148 83218 8
Notes: 2352 RAW dump, using dcpprip

Header info:

Code: Select all

Hardware Identifier : "SEGA SEGAKATANA"
	Hardware Vender ID : "SEGA ENTERPRISES"
	Media ID : "B4C1"
	Media Information : "GD-ROM1/1"
	Compatible area symbols : " U"
	Peripheral Information : "07D9A10"
	Product number : "T-8107N"
	Version number : "V2.001"
	Release date (dd/mm/yyyy): 29/06/2000
	First read file : "1ST_READ.BIN"
	Maker Identifier : "T-81"
	Game Title : "FUR FIGHTERS"
GDI: (Handwritten)

Code: Select all

3
1 0 4 2352 track01.bin 0
2 825 0 2352 track02.raw 0
3 45000 4 2352 track03.bin 0
Filesizes & Checksums:

Code: Select all

track01.bin 
size 1940400 
crc fd0c7927 
md5 926d785df1db8d4854ccdfa86e53fd9e 
sha1 d299801d5ae7c584499066927aaa54d4fe8b5ba1

track02.raw 
size 1237152
crc 4a71b7f2 
md5 95e6cf1e69fdf66f720effa4708ed8ea 
sha1 3966a3ca64e73dfcbc5fa83e889c002c875c537e

track03.bin 
size 1185760800 
crc bef5d874 
md5 62b3ddb55e509ee5dcd8e61e3c171f93 
sha1 34d23ac4b81dd93c5ec93c54c908f7a57b281f97
I hope I've been of help !

More games to come...

FG
User avatar
Maddog
is awesome
is awesome
Posts: 1599
Joined: Sat May 12, 2007 4:12 pm

Post by Maddog »

Hi FamilyGuy!
I think you have been quite helpful by posting this. Thanks! :D

First the (very!) good news: track02 and track03 match a submission we have. track03 matches for F355 too, but I can't compare track02 there since the submissions we have have different ringcodes *5S* and *6S* and weren't expected to match anyway.
This means that the method seems to be producing constantly good dumps and presents an inexpensive way to rip DC discs to same checksums as httpd-ack (as long as you are patient enough...)
track01 can't be compared, since your method produces dumps 150 sectors larger (seems it rips the 150 sector/2 second gap as well, or it just adds zeroes there). I don't know if the parallel port ripper has any settings to choose which sectors to rip. If it has, you can try reducing that by 150 sectors.
Since ripping track01 in a normal PC drive produces same checksums as httpd-ack (at least for the several discs I tried), I tend to think that it's a minor fault of the parallel port ripper.
Try cutting off the last 352800 bytes of your track01 and let me know of your new checksum. To help you see if things go well, here's part of our checksum: track01.bin size 1587600 crc 0cb2XXXX. Post your new checksums of the cropped file and I'll let you know ASAP if it matches fully.
I'd also like to see a rip from a disc with CDDA on the high density track, if you have any. One correct track02 indicates that there's no problem with ripping audio, but I'd still like to see how it behaves with track04+
-=FamilyGuy=-
Posts: 20
Joined: Mon Sep 24, 2007 3:29 pm

Post by -=FamilyGuy=- »

Here's the Fur Fighter 1st track info with 150 sectors chopped off, I didn't did it for F355 as it ain't from the same version as the one already dumped by you (you being you all in here).

Code: Select all

track01.bin 
size 1587600 
crc 0cb222c7 
md5 8db75bfeb08e172993b72e186be6de0a 
sha1 e1619e32643319b2d86884b158fd4ba77bd08bfa
According to the filesize and begining of crc, it might be good :P

Also, yes the software allows for specific sectors ripping, it's actually the trick to make it rip data/2352 sectors, you specify the sectors to be ripped as audio, but since it can't read data as audio it simply reads in 2352 mode... I've contacted to author of dcpprip aout this and he added that info to his website: http://f17.aaa.livedoor.jp/~takotako/index.php#dcpprip

So for anybody else with a printer cable, four 100ohm resistors and 2 minutes to solder:
bin image ripping tips: (for dcpprip)
dcpprip -s <start>,<size>,<'a'(2352)> trackxx.bin ... '-s' sector dump option
get track03.bin ex.) dcpprip -s 45000,504150,a track03.bin
This will make a compatible dump for the dumpcast.

To be clear, it won't be a problem at all to do a little substraction each time I'll rip a game, and I still have 6 non-verified titles (at least 2 of them are GDDA games ;)

I'm glad that I've helped this cool project !

FG
User avatar
NU-NRG
Posts: 17
Joined: Sun May 13, 2007 4:38 am

Post by NU-NRG »

You should start selling these cables as I'm sure there would be a market for them. ;)
User avatar
Maddog
is awesome
is awesome
Posts: 1599
Joined: Sat May 12, 2007 4:12 pm

Post by Maddog »

Yeah, cropped track matches perfectly. :D
Please post the F355 cropped checksums on that game's thread too. Atm it's unverifiable due to diff track02, but some future submission could verify any of the 3 known ringcodes we have now, including yours. Heck, I am inclined to go buy a random F355 disc since it's very likely to verify one of the 3 (and hope I don't hit a 4th ringcode!) :lol:
Post Reply