Dumping Guides (Disc Image Creator)

Hi, I allowed myself to move your post to a new topic, i think it would overfill sarami's topic otherwise.

HashCalc (or any other checksum tool): Download, unzip, install.

Checksums MD5, SHA1, CRC32

I think, this step can be skipped. DIC should have its own ClrMamePro output for hashes, if not please ask sarami to include it into DIC outputs. I will add ClrMamePro support for DVD based discs soon as well.

Version: For PS2 games, mount the .iso and open "SYSTEM.CNF" in Notepad app, "VER" = version number.

Mounting is not really required, it also can be opened from the disc itself. Also if sarami can include it into DIC output please ask him.

Version: For PC games, right click on the game .exe or relevant file and click on "Properties"

I don't think this is a proper way to find the version. The version in EXE properties is referring to EXE version. Game version is either located in files like INI, CONFIG, README and or can (only) be obtained from in-game main menu.

Image size: Right click on one of the .iso files > Properties > and look for "Size" in bytes (NOT "Size on disk"). Save "Size" info for submission.

Layerbreak sector: 

DIC output?

Hi user7! I appreciate very much your guide for newbies as I find DIC difficult to use, and the DIC's main thread with 44 pages became impossible to read!

For example: what difference would it make to run DIC with the "CD" or "DATA" parameter?
Also, could you describe when to use the other parameters? Like /c2 /d8 or whatever

I guess I need to launch DIC with specific parameters according to the disc's protection.
Can you make a list of what to use with each? Or at least the most common one? SafeDisc 1, SafeDisc 2-3-4 and SecuROM

For PS1 and PS2 CDROM discs:
Discimagecreator cd cd_drive file.bin 8 /c2

replace cd_drive with your Plextor drive letter (don't forget the colon!)
replace file.bin with your filename

Of course don't forget the path to Discimagecreator (and use "" for any path with spaces in it)

- /nl is for LibCrypt, /ns for SecuROM, /sf for for PC copy protections that can be detected, /ss for other PC protections with c2 errors.
- size and hashes are in .dat file (doh)
- .cue that DIC created should always be used/included
- write offset is in the disc log txt
- SecuROM data is in the subintention .txt (when /ns parameter is used and the disc is in fact SecuROM-protected)

Also my suggestion would be to remove this part from the guide (until any of the drives are really verified):
'''Disc drives believed[http://forum.redump.org/post/49337/#p49337] to be compatible''' (move to verified list when confirmed):
* Apple 300, 300i (Sony CDU-8003, CDU-8003A) 
* Apple's "New" CD (Matsushita CR-8004) 
* Chinon CDS-535 (note: needs v2.0 firmware "Q20" or "R20") 
* NEC CDR 500, CDR 510, CDR 600 (MultiSpin 3x series) 
* NEC CDR 400 (MultiSpin 3xp portable) 
* NEC CDR 900 (MultiSpin 4x Pro quadruple speed) 
* NEC CDR 84-1 (74-1) needs special new firmware upgrade from NEC 
* Sony CDU-561 
* Toshiba XM 3301TE (Silicon Graphics version) 
* Toshiba XM 3401TA, XM 3401B 
* Toshiba XM 3401TE (Silicon Graphics, and Sun versions) 
* Toshiba XM 4101TA Toshiba XM 5301TA
* Hitachi 6750S

And also remove this:
Protected CD:
SecuRom 3
PLEXTOR
PX-4824A (ecc/edc of the 2 sector doesn't match)
CDS200, Label Gate, XCP
PLEXTOR
PX-4824A (doesn't get the TOC correctly)

It's no use mentioning individual issues for certain discs/drives. A lot of things can go wrong during dumping. The dumper needs to learn himself how to pick up on these issues.

Also the section 'Disc Compatibility' isn't really needed. DIC should work with any CD.

A guide should be as compact and easy to read as possible.

I fixed as DVD doesn't work by 'cd' command. Please use 'dvd'.

I haven't tested these drive yet.