Help me!! Broadband My Dumping not TOSEC CRC...

This forum is for discussing Dumpcast or the TOSEC project itself. Post suggestions or ask questions about the project or the website here.

Moderator: Moderators

Post Reply
yamada
Posts: 4
Joined: Sat Jun 16, 2007 7:38 am

Help me!! Broadband My Dumping not TOSEC CRC...

Post by yamada » Sat Jun 16, 2007 8:16 am

I did a broadband passport and Dump was done by way of experiment.
However, Track1&2 becomes CRC different from TOSEC.
What problem is thought?

Moreover, I saw the message that the track of CDDA never became the same as DAT of TOSEC in the forum in Japan.
They said.
CDDA is not corresponding to CRC of TOSEC at all.
As for doing Dump personally, the same title as the title registered in TOSEC is meaningless.
The file of same CRC as DAT of TOSEC will not be able to be obtained as long as the file of TOSEC is not downloaded.

http://www.megaupload.com/?d=13KD2TAF
User avatar
darcagn
Site Founder & Admin
Site Founder & Admin
Posts: 330
Joined: Fri Apr 06, 2007 11:12 am

Post by darcagn » Sat Jun 16, 2007 11:00 am

I examined your tracks 1 and 2 with a hex editor.

Track 1 has a single byte of difference between them. Track 1 is probably a bad dump.

Track 2 appears to be made with a different offset than our dump. It may not be wrong, but it could be a different version of the disc.

What is the ring code on your disc? It can be found on the bottom side of the disc in the center. It will be a long line of letters and numbers.
User avatar
Maddog
is awesome
is awesome
Posts: 1516
Joined: Sat May 12, 2007 4:12 pm

Post by Maddog » Sat Jun 16, 2007 11:44 am

As darcagn says, crcs in TOSEC dat for Broadband Passport only apply to the disc with ringcode 610-7883-0442 1M1 C 06 (it shows this in the filename too). This is verified by two independent dumps and is sure to be correct.
We know another disc with ringcode 610-7883-0442 2M1 C 18, which has different track02, but this isn't verified by a second dumper and so it doesn't appear in the dats. The part in bold seems to be the important one to determine if discs CDDA will match. Data tracks generally match if version in header is the same.

What is your ringcode?
I also assume you are using httpd-ack and a DC to read the track. If you used a PC drive for track02, it will always be different, since PC drives have different offsets from the Dreamcast drive.
yamada
Posts: 4
Joined: Sat Jun 16, 2007 7:38 am

Post by yamada » Sat Jun 16, 2007 4:32 pm

My ringcode 610-7883-0442 2M1C18

Because I had not become it as well as CRC of TOSEC, Dump was done several times.
However, everything becomes same CRC.

The same problem was discussed in the forum in Japan.
His CRC is the following.
track02.raw
crc bf610169
md5 709e6eedad732eff20a5856f38825989
sha1 facbfdd2acb4ed9e7c9df75b1fb97c89f79f87be
They said.
It is likely to become same CRC as long as Dump is done with same DC.
However, when Dump is done with another DC, CRC of CDDA might not become the
same.
User avatar
darcagn
Site Founder & Admin
Site Founder & Admin
Posts: 330
Joined: Fri Apr 06, 2007 11:12 am

Post by darcagn » Sat Jun 16, 2007 5:56 pm

yamada wrote:They said.
It is likely to become same CRC as long as Dump is done with same DC.
However, when Dump is done with another DC, CRC of CDDA might not become the
same.

We have determined that all Dreamcasts have the same CDDA read offset. The problem actually is with the production equipment. The production equipment has different CDDA write offsets. Therefore, if 2 discs have the same ring code, it was made on the same equipment, so it should have the same audio track. Sometimes different ring codes have different CDDA, meaning the machines had different write offsets.

The information we currently have for the disc with ringcode 610-7883-0442 2M1 C 18 is as follows:

Code: Select all

track01.bin
size 705600 crc 782c0fe2 md5 19b0f29373f92676d3a4a9b264ba1772 sha1 c4fdb781fe4da7e655da7b98c495902a00677f83

track02.raw
size 1641696 crc bf610169 md5 709e6eedad732eff20a5856f38825989 sha1 facbfdd2acb4ed9e7c9df75b1fb97c89f79f87be

track03.bin
size 1185760800 crc b180eb77 md5 1fd9fa42a32c45dd4c8da143f86c4ed0 sha1 fcdd538d1523bfea1931c0fced062f461b061a24
This is not verified yet, though.

Because your disc has a different checksum for track 1, I would say that your disc is probably damaged.
User avatar
Maddog
is awesome
is awesome
Posts: 1516
Joined: Sat May 12, 2007 4:12 pm

Post by Maddog » Sun Jun 17, 2007 11:10 am

As you can see, your ringcode is ...2M1... and the audio track02 matches with our checksum for that disc, which is yet unverified and doesn't appear in official dats. If you do redump your track01 and come up with the correct CRC for that too, we can add that disc in the dats as well. Let us know if this happens. We'll also be very happy if you have any other games to dump for the project.

Method was checked extensively before going public and works fine. Results are always reproducible. It's actually lucky that Dreamcasts seem to have the same offset always, otherwise it would be very hard or impossible to get any matching crcs. As it is now, all discs with same ringcode will match.
yamada
Posts: 4
Joined: Sat Jun 16, 2007 7:38 am

Post by yamada » Mon Jun 18, 2007 9:19 pm

Thanks all !!

I thought that the cause of this problem was in any of PC or DC or LAN.
Then, I obtained new DC.

CRC became it as follows.
track01.bin
size 705600 crc 782c0fe2 md5 19b0f29373f92676d3a4a9b264ba1772 sha1 c4fdb781fe4da7e655da7b98c495902a00677f83

track02.raw
size 1641696 crc bf610169 md5 709e6eedad732eff20a5856f38825989 sha1 facbfdd2acb4ed9e7c9df75b1fb97c89f79f87be

track03.bin
size 1185760800 crc b180eb77 md5 1fd9fa42a32c45dd4c8da143f86c4ed0 sha1 fcdd538d1523bfea1931c0fced062f461b061a24
I thought that confirming doing of all Dumper a broadband adaptor Dump first of all and becoming CRC of TOSEC and same CRC was necessary.

The first DC of me doesn't have the problem in the play of the game either.

However, Dump is not accurately done.
I am anxious what the difference of these two DC is.
User avatar
darcagn
Site Founder & Admin
Site Founder & Admin
Posts: 330
Joined: Fri Apr 06, 2007 11:12 am

Post by darcagn » Tue Jun 19, 2007 9:15 am

yamada wrote:Thanks all !!

I thought that the cause of this problem was in any of PC or DC or LAN.
Then, I obtained new DC.

CRC became it as follows.
track01.bin
size 705600 crc 782c0fe2 md5 19b0f29373f92676d3a4a9b264ba1772 sha1 c4fdb781fe4da7e655da7b98c495902a00677f83

track02.raw
size 1641696 crc bf610169 md5 709e6eedad732eff20a5856f38825989 sha1 facbfdd2acb4ed9e7c9df75b1fb97c89f79f87be

track03.bin
size 1185760800 crc b180eb77 md5 1fd9fa42a32c45dd4c8da143f86c4ed0 sha1 fcdd538d1523bfea1931c0fced062f461b061a24
I thought that confirming doing of all Dumper a broadband adaptor Dump first of all and becoming CRC of TOSEC and same CRC was necessary.

The first DC of me doesn't have the problem in the play of the game either.

However, Dump is not accurately done.
I am anxious what the difference of these two DC is.
Thanks; since you have posted your dump we can now verify it with one of our previous dumps and include it in our database.

The reason your disc plays completely correctly in both Dreamcasts is because they both have good track 03 files. Since track 03 is where the game data is, the Dreamcast has no problem.
Quzar
Posts: 52
Joined: Mon Apr 23, 2007 1:22 pm
Location: Miami, FL
Contact:

Post by Quzar » Tue Oct 16, 2007 10:24 pm

darcagn wrote:We have determined that all Dreamcasts have the same CDDA read offset.
Sorry to bump an old topic, but how exactly was that determined?
I only upload the information, not images.
User avatar
Maddog
is awesome
is awesome
Posts: 1516
Joined: Sat May 12, 2007 4:12 pm

Post by Maddog » Tue Nov 06, 2007 7:10 am

While developing httpd-ack, this was the first thing to be tested quite extensively and further tests have been conducted by comparing dumps once the program was released in the wild.
The mere fact that httpd-ack always yields the same results for CD/DA tracks (same binary stream) on every console tested so far means the read offset for the drive used in the console is always the same.

Since we have had matching dumps from many consoles of all regions and all over the world (even from several people that are not members of the project, like those that independently uploaded their httpd-ack dumps to UG), it's quite reasonable to assume that all Dreamcasts have the same offset. Our results so far include PAL consoles from different European countries, NTSC-U consoles and even NTSC-J ones. And let's not forget Shoometsu's dumps from South America either. In any case, we have a decently widespread coverage of all DC regions (and it's probably safe to assume these consoles can not possibly all be from the same production batch either). This shows that there's (in all probability) indeed only one offset for all Dreamcasts.
Of course, if one wanted to be the devil's advocate, it's not completely impossible that some console revision somewhere has a different offset, but we haven't encountered one yet. ATM I am waiting for my new Treamcast to be delivered, when this is done we'll have the chance to test a 3rd party console too.
Post Reply