Posts: 7

Topic: DIC dumping questions

I’m new here and I’m trying to understand the dumping process. I have a collection of Sega Saturn (PAL and JP) games together with a minor collection of PS1 (PAL) games and I’d like to create backups of all my discs. I’d also like to contribute dumps/verifications to the redump database if possible, but it’s a bit of a challenge to know exactly where to start. :-)

Anyway, I’ve recently acquired three Plextor drives (PX-755A, PX-716SA and a Premium) and upgraded all of them to the latest firmware, since that seems to be the general recommendation. I think they should be supported by DiscImageCreator. Please correct me if I’m wrong here.

I’ve read the DIC thread[1] and I have DIC, EccEdc and the necessary MS VC++ packages installed on a Win7 x64 machine. If anything else is needed, again, please tell me.

So, I started with Guardian Heroes[2] for Sega Saturn. I ran DIC with the following command line options:

> DiscImageCreator.exe cd F: disc.bin 8 /c2

and I got a large set of files as the result. It took about 8 minutes. However, I don’t see any resulting large ”disc.bin” in the DIC directory. Did I do something wrong?

Comparing the md5/sha1 hashes of all the small .bin tracks with the values in the redump database shows no differences. Hash values are the same. I guess that’s a good thing at least. Is that enough to know that I have a good dump?

Last question - in the redump database entry[2] for Guardian Heroes, ”Cuesheet” is marked as blue, ”Rings” is marked as yellow and ”Header” is marked as blue. With the dump I got, can I submit enough info in a verification in order to bring these into confirmed/green status?

Re: DIC dumping questions

The resulting large ”disc.bin” should be there, except maybe if dumping process was aborted / incomplete.

If you have no differences to the database you are most likelly good to go

”Cuesheet”: can only be set as green (verified) if we have full dumping logs (DIC logs are for the most part good enough).”Rings”: setting to green require a clear disc scan from from data side.”Header”: i think you will figure this out yourself, somewhere in private discussions.

Re: DIC dumping questions

OK, I got it. DIC doesn't produce a single bin+cue if it's a multi-track disc. So the file name specified on the command line isn't actually used the way I thought it would be. Somewhat confusing, but I understand why.

It would be nice if DIC had an option to also create a single bin+cue though.

Re: DIC dumping questions

behemoth wrote:

It would be nice if DIC had an option to also create a single bin+cue though.

bin+cue, img+cue, iso+cue is the same thing. You can rename .img to .bin by yourself (don't forget to do the same inside the .cue). You can even rename it to, dunno, "dump.abc" + "dump.cue" and it will still work.

Re: DIC dumping questions

F1ReB4LL wrote:

behemoth wrote:

It would be nice if DIC had an option to also create a single bin+cue though.

bin+cue, img+cue, iso+cue is the same thing. You can rename .img to .bin by yourself (don't forget to do the same inside the .cue). You can even rename it to, dunno, "dump.abc" + "dump.cue" and it will still work.

Yes, thanks. I was thinking about it and did a cksum on disc.img and converted it to hex and it matches the CRC-32 "total" value in the database. Awesome.