• Registered: 2017-05-01
  • Posts: 87

Hi.  Brief background, with specific questions to follow:

I'm ripping my entire PC media collection, mostly older games for DOS, early Windows, and Linux.  I'd like to verify my rips and contribute where possible, but the PC ripping guide and recommend software is entirely Windows-centric.  I don't run Windows, so that's a problem for me.

I found that the DiscImageCreator CLI version has a Linux port available, which is great (thanks, sarami!).  I don't seem to have one of the specifically recommended drives, but doing some basic testing with a Quake III CD I seem to get positive results.  The resulting bin file matches as does the PVD timestamps.  I can also rip the disc with cdrdao + toc2cue and get identical results as far as the bin/cue files go.

So that all seems promising as far as verification, but submission is a different store.  DiscImageCreator creates a LOT of files.  The guide says that DCUI will put the important bits in !submissioninfo.txt, but I don't have that file as, presumably, I'm using DiscImageCreator directly.

My questions:

1. Given the above (ripping under Linux and not using a "certified" drive), is it worth submitting rips for games that you don't already have included in the database, or would it be seen as untrustworthy?

2. If it's worth submitting, can someone point me to any templates or directions on how to manually assemble the information necessary for submission from the resulting DiscImageCreator files?

3. Once verified and/or submitted, is there any practical benefit to keeping all the additional files *besides* the bin/cue?  CloneCD images are not well supported on Linux, I don't know what to do with the SCM or other files, and all of the text output, while interesting, don't seem particularly useful for my needs down the line.  Just want to make sure I'm not missing I may regret later.

Thanks, all.  Appreciate any guidance.

  • zcal
  • zcal
  • Dumper
  • Offline
  • Registered: 2019-10-27
  • Posts: 28

Sorry for bumping an older post, but I'm also interested in the answer to question #2.  And furthermore, would manually assembled information that would otherwise be included in !submissioninfo.txt be trusted enough for a database submission?  This is assuming that all other relevant output files from the dump were included and an approved drive was used.

zcal's Website

  • Registered: 2017-05-01
  • Posts: 87

Hi, zcal.  From what I've pieced together, !submissioninfo.txt basically just compiles information from the various files creatd by DiscImageCreator.  I'm pasting the output below from one rip as an example:

It just makes it easier to copy/paste your submission.  It's possible to run DICUI.Check_1.15-net462.zip under Linux with wine/mono, but you can also manually add the data using this as a template and not bother with !submissioninfo.txt.

Just as an FYI, I had some discussion and got a few additional questions answered in the following thread.  May be helpful for you as well.

http://forum.redump.org/topic/22980/add … nux-cdrom/

And last of all, welcome!

Common Disc Info:
        Title:
        Foreign Title (Non-latin):
        Disc Number / Letter:
        Disc Title:
        System: IBM PC Compatible
        Media Type: CD-ROM
        Category: Games
        Region: World (CHANGE THIS)
        Languages: Klingon (CHANGE THIS)
        Disc Serial:

        Ringcode Information:
                Mastering Code (laser branded/etched):
                Mastering SID Code:
                Data-Side Mould SID Code:
                Label-Side Mould SID Code:
                Additional Mould:
                Toolstamp or Mastering Code (engraved/stamped):
        Barcode:
        Error Count: 0
        Comments: [T:ISBN]
        Contents:

Version and Editions:
        Version:
        Edition/Release:

Extras:
        Primary Volume Descriptor (PVD):

0320 : 20 20 20 20 20 20 20 20  20 20 20 20 20 32 30 30                200
0330 : 31 30 39 30 37 31 35 31  32 34 37 30 30 00 32 30   1090715124700.20
0340 : 30 31 30 39 30 37 31 35  31 32 34 37 30 30 00 30   01090715124700.0
0350 : 30 30 30 30 30 30 30 30  30 30 30 30 30 30 30 00   000000000000000.
0360 : 30 30 30 30 30 30 30 30  30 30 30 30 30 30 30 30   0000000000000000
0370 : 00 01 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................

Copy Protection:
        Copy Protection: (CHECK WITH PROTECTIONID)

Tracks and Write Offsets:
        DAT:

<rom name="Serious Sam - The First Encounter.bin" size="583524144" crc="a6d4f0f4" md5="1649a1a19ed2fb611cadc62a81279457" sha1="ef85bbc07a2f281db93734e954ddce8913258d9b"/>

        Cuesheet:

FILE "Serious Sam - The First Encounter.bin" BINARY
  TRACK 01 MODE2/2352
    INDEX 01 00:00:00

        Write Offset: -12
  • zcal
  • zcal
  • Dumper
  • Offline
  • Registered: 2019-10-27
  • Posts: 28

Thanks, nitro322!

I've seen that format in others' submissions, so I figured that was coming from !submissioninfo.txt.  I'll see what I can do about piecing the bits together.

In the other thread that you linked you noted how (it appears) you get the PVD.  Any idea how you w/should do this for multi-track discs?  I've got some Sega Saturn discs that generate ~20 .bin files each when dumped.

Also, I noticed in the other thread that you asked if your dump was going to be added to the database.  That was in December.  Did you have luck with other dumps that you've done with Linux getting entered?

zcal's Website

  • Registered: 2019-04-12
  • Posts: 107

zcal wrote:

Did you have luck with other dumps that you've done with Linux getting entered?

The OS you're dumping on has no bearing on when your dumps are processed. As long as you use the proper software, a compatible drive and supply all of the required info you're good.

Since there's only a handful of people who have the authority to add discs and they have to review the dump info the time it takes for a dump to be added varies. Sometimes they're added in a few hours, sometimes a few weeks.