Hello everyone,

I'm a recent member and I just joined after a long time of using this website to verify my dumps of games that I own. I appreciate what this site is doing and everyone who has participated has my thanks.

Now then, I was reading the wiki trying to find out how does everyone here dump their games. A lot of the tools are windows exclusive and/or use proprietary extensions files. Right now I'm using windows for my video games, but I prefer to use linux for my main operating system usage. Usually I've dumped my games with bin/cue and/or iso but I've realized that bin/cue is better since the bin is a raw format. Now I'm learning about all these weird copy protection mechanisms on pc games and I'm trying to find my way around this.

On windows, I've been using imgburn, since infrarecorder doesn't support reading to bin files, only iso. So with imgburn I can make bin/cue files but I wanted to ask everyone if this is ok. I've already verified the bin files with the games in your database and they've checked out but is the cue good enough. I have no idea the difference between cue, mds, and ccd; but, don't they store the same information just in different ways? If so, sticking with cue shouldn't hurt. I don't want to have to use mds and ccd since those are exclusive to alcohol 52/120 and clonecd respectively and not only are those proprietary software but they also have trials that I really don't want to have to deal with. Is cue good enough for detailing all the intricacies of the disc or is there some more information? Also is bin/cue or some other raw format the ideal solution. Basically avoid iso if possible. I know with my gamecube and wii games I cannot avoid iso as I use cleanrip which automatically makes the games into iso.

Any help is greatly appreciated. By the way I have two games that I would love to add to the pc section which are:

the chronicles of riddick: escape from butcher bay
cryostasis: sleep of reason

If I can figure out the proper technique then I'll be sure to add these.

As long as the program and platform you run use the standard 0xBE read command, the dump is raw (2352 bytes per sector) and you have a minimally decent drive everything is OK and extension doesn't matter actually. Anyway, for CD discs we don't add cooked dumps, 2048 bytes per sector.

To put this simple taking as example a conventional, without Safedisc, SecuROM and these things, PC CD game with just a data track extracted by Isobuster in raw mode, CloneCD (when using this one TURN OFF regeneration of data in the read profile, we don't want that CloneCD fixes in the fly user data of damaged sectors using the stored ECC because this is as dumping a disc into raw mode to fix later bad sectors using CDmage, dumps shouldn't be modified in this sense) and Alcohol 120%.

bin of bin/cue = img of ccd/img/sub = mdf of mds/mdf (only if subcodes weren't read, if so mdf will contain interleaved subcode data and you need the 2448to2352 program by themabus to split the mdf file into main channel and subcode). Simple as that.

Problem are discs with audio tracks, you have to find a program for Linux which can:
-Perform a secure ripping, either by multiple reads or C2 pointers.
-Correct the offset, any value you desire once detected the proper one.
-Detect properly gaps and append them to the next track.
*-Detect possible CATALOG/DCP/ISRC flags (this ideally for discs with only a data track as well).
-Extract to headerless files, or at least run sox to remove RIFF headers.

*Answer to the "Is cue good enough for detailing all the intricacies of the disc or is there some more information" question. To detect them PR is good and for discs without copy protections and with just a single data should work even without a real Plextor drive.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Thanks for the help. I'm trying to understand. So is the wiki still up to date and accurate? I'm attempting to follow this guide as I have Silent Hill 2 for the pc which is not in the database. It contains securom so I'm following this wiki specifically:

http://wiki.redump.org/index.php?title= … protection

So let me get this straight, I first dump with cd manipulator or clonecd, whichever I prefer, and I obtain an img file with a cue sheet. Then I dump again with alcohol 52 or 120 to obtain a mds file. I can discard the mdf file as I only care about the mds. Finally I redump with clonecd to obtain a ccd file and I can disregard the img or bin file created with clonecd. In all of these cases I'll make sure the md5 checksum matches with the raw image file. So at the end of the day I'll have this:

bin/img file: obtained from cd manipulator
cue file: obtained from cd manipulator
mds file: obtained from alcohol 52
ccd file: obtained from clonecd
(edit) sub file: obtained from subdump

Is this correct? Will this be all the information I need? Oh I almost forgot, could I get a copy of that subdump program and instructions on how to use it. This way I can get a sub file and add it to the above list.

So what I'm asking is: Is all this necessary? Wouldn't the the img/bin and cue file from cd manipulator be enough? Maybe throw in a sub file but that's it. Do I really need the mds and ccd file? I don't know if mds will be useful without a corresponding mdf file and same can be said for ccd. Plus obtaining the mds and ccd file will require installing more software. I'm just trying to obtain a correct dump so I can later, in my choosing, burn these files to a cd or dvd and know that I this copy that I would have made would be perfectly identical to the original in every way. That is my goal.

4 (edited by pablogm123 2014-05-18 04:20:10)

That page contains updated and accurate data, was written by MrTikki after asking me and others lots of questions to write the best possible guides yet easy of understand.

Guide basically says that you should extract the data track as usual using IsoBuster, raw mode. You should dump the disc at least twice and make sure that dumps are identical, better yet if using different drives when possible.

Nothing more is needed for the DB, except obviously the errors count (1 expected error in the postgap zone) and perhaps a quick and dirty subcode dump got by CloneCD/CDManipulator (subdump only if are really interested in getting the cleanest subcodes possible, but it's very time consuming and for detecting CATALOGs and so on even a quick and dirty subcode dump by CloneCD is good enough) to determinate properly if the disc contains CATALOG and other possible flags. One good strategy and efficient would be dumping the disc as usual using IsoBuster, and then a CloneCD/CDManipulator (see the screenshot posted below) dump with the proper profile to kill two birds with one stone: to verify the IsoBuster dump and to get the quick and dirty subcode dump that you can upload (subcodes compressed are very small files).

For you personal backup and archive perhaps you could desire to create a mds file for that disc. Create it and archive it. If the dump by Alcohol lacks of subcodes mdf file must match the dump got by IsoBuster and/or CloneCD/CDManipulator.

http://i.imgur.com/XandKMo.png

P.S.: CDManipulator can create .ccd files if you choose that in the file output options once selected the multi-session mode. Just use any plain text editor to delete the ficticious ISRCs which uses to add due to random errors in the subcode not properly ignored.

[TRACK 1]
MODE=1
ISRC=0@41=0100013
INDEX 1=0

[TRACK 1]
MODE=1
INDEX 1=0

Subdump:
https://www.dropbox.com/s/dmkd2l490mtdrm1/subdump.zip

Reference of command line for a non-real Plextor drive:

subdump.exe -i g: -f test.sub -mode 1 -rereadnum 25 -speed 8 -flushspeed 8 -fix 2

Optimal speed depends on the drive used. Certain drives read better at lower speeds (4x/8x), others one at higher speed (24x and higher).

If there is a  real Plextor drive which supports D8 command:

subdump.exe -i g: -f test.sub -mode 2 -rereadnum 25 -speed 8 -flushspeed 8 -fix 2

And if you are just interested in getting a quick and dirty subcode dump, somewhat cleaner than the one got by CloneCD/CDManipulator and verifying the linearity of subcodes frames add the -quick parameter.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

5 (edited by TheDrifter363 2014-05-18 10:00:52)

Hmm so I'm rather confused, should I save my backups as:

bin and cue

or

img, ccd, and sub

or

mdf and mds

Which one is best? All three contain raw data, their metadata deals with copy protection differently which is what I am aiming at. I'm using cd manipulator instead of isobuster. Which one is the best for archival purposes?

Also when creating a sub file with subdump it freezes after a while towards the end where it was reading the drive but I only saw a blinking cursor in the command prompt. How long does subdump usually take without the quick option?

bin/cue should be good enough for every common disc layout. ccd/img/sub is needed actually in certain discs which contains mixed type pregaps (75 sectors of data + 150 of audio, being the first ones marked as data in the subs). bin/cue cannot handle this layout, ccd/img/sub can because actual .subcode is present. mds/msf for this protections which measures physical disc positions.

Anyway, converting bin/cue to ccd/img/sub if you prefer this format in the future is trivial: just mount the image, create a CloneCD/CDManipulator dump (.img file created should match the original .bin) and replace the .sub created with the one dumped by subdump.

Even if the disc is in near mint condition and not affected by discrot, subdump takes some time to dump the subcode (not protected by CIRC, so no error correction is offered and a high ammount of rereads is needed to get uniform and constant data). For a disc in good condition with more or less 70 minutes (740,880,000 bytes of data extracted into raw mode), without any class of deep scratch, expect easily 45-60 minutes.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Ah thank you I forgot that subdump can dump sub files from img/bin files. Though can you explain more on mds/mdf and its benefit for copy protection? Isn't bin cue or img ccd sub good enough for copy protection like safedisc or securom? Also I've read somewhere that if I create a mds/mdf copy that in the future I would always need to have alcohol to play the burned copy on another computer. I don't want to have to do that. I want to burn the copy and play it on another computer without worrying about installing more software.

Can I burn a mds/mdf copy and then play it on another computer without installing alcohol on that computer?

8 (edited by pablogm123 2014-05-19 04:15:14)

Only MDS format can capture data of physical measurements (due to that it's suggested in the guide to create one MDS file for personal use), needed for SecuROM and StarForce. ccd cannot capture that, it's a simple .txt file similar to a .ini file which describes the TOC, but nothing related to physical measurements. I doubt that a personal backup will work without doing anything special due to the physical measurements performed by the protections.

RPMS needed to burn and Alcohol to emulate DPM data. Perhaps Daemon Tools with SPTD installed, to enable advanced emulation options can mount the image (or even create it in certain advanced editions) and get this image acting as the original disc in order not to wear the precious original disc.

For Safedisc, a decent burner capable of burning weak sectors (decent EFM encoder) and done, as far I remember.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

I have a question about the mds/mdf files. So I'm trying to rip a securom game like the chronicles of riddick: escape from butcher bay. It is a CD based game with the first cd containing securom 5 or 4. I've ripped it 3 times but each time the md5 checksum is different. Is this accurate? For two of the files, there is a data read examination error which I'm guessing is the securom error. This error happens at the exact same sector. For the other one, I got a disc read error at 0 but I believe that's a mistake. I'll try again, but why am I getting 2 different checksums with files that should be identical. Both of their error spots were at the exact same spot. How can I verify if my mds/mdf copy is valid?

It's extremely unlikely that you rip to mds/mdf once CD several times and you get the same hashes, or directly impossible due to random errors in the subcode:

http://www.mediafire.com/?p8on996xtmrb8

2448to2352 can split the MDF file into main channel and subchannel. Main channel should be always identical and uniform for these these discs. Subcode is always affected by random errors.

2352to2448 to do the reversed process: convert a clean subcode and the raw dump into a MDF file reusing the MDS previously created.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Thank you very much. So should I keep my subcode separate from the mdf file or should I combine the two? Which do you recommend?

Also sometimes when using alcohol 120, with securom discs, I get "disc read error at 0". This doesn't happen all the time, only some times. Should I dump the game again if I see this error since it doesn't appear all the time?

Separated compatibility is better, can be used as bin/cue, ccd/img/sub image and opened by programs as IsoBuster and CDmage. The major thing is understand that MDFs of CD discs won't match due to random errors in the subcode, nothing more. Once separated, main channel should match if the dumps are good (and should match IsoBuster, CDManipulator's... imgs if disc doesn't contain audio tracks).

Erroneous sector of CDs discs protected by SecuROM is in the postgap, the 4th sector from the end. This sector reminds the last sector of data tracks of PS1 discs without EDC in form 2 sectors and with audio tracks, looks very similar, a mode 2 sector with erroneous ECC data.

A read error doesn't sound good, even if sectors 0-15 are don't contain normally useful data in PC games, it's normally used only for console discs (header and whatnot of Saturn games, logo and license of PS1 discs...).

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

I was able to work around the read error in the beginning by re ripping. I have a question about that program that extracts subdata from mdf files. If I use it and create a new mdf file with a new sub file, will the mds file I initially created still be valid? Will I still be able to burn it with alcohol 120?

Also is subdata useful for anything? I know its important for copy protection but how about for games that don't have copy protection? For example, disc 2 of the chronicles of riddick escape from butcher bay doesn't have copy protection, so if I click get subdata in alcohol, will it be useful?

Lastly, when choosing a format with subdata for non copy protected discs or non securom discs, which one should I choose: mdf/mds or ccd/img/sub? I want to be able to burn these with subdata in the future and I know I can burn mdf/mds with alcohol 120 but how about ccd/img/sub? Can I burn that type of file with subdata without using clonecd? Can cd manipulator burn ccd/img/sub with sub file included? Will it use the subdata/sub file?

It's a lossless process, converting from MDF to img+sub (2448to2352) and reconverting img+sub to 2448 (2352to2448) and then renaming to MDF gives the original MDF file. And that .sub file can be replaced with the extracted by subdump and the MDS will be still valid of course.

Subcode data is mainly useful for multitrack discs, to detect accurately the gaps of tracks and imperative for these EUR PS1 discs protected by LibCrypt. For normal PC discs with just a data track even bin/cue is just fine, so perhaps ccd/img/sub (accepted by CDManipulator in RAW DAO 96 mode, by ImgBurn as well, but will ignore the sub and subcode will be generated by the burner) is the optimal solution.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

I understand. So for securom protected pc games, I will use mds/mdf because of the protection. However for all other pc games that use protection I can use img/ccd/sub. I have a question: How come alcohol doesn't offer tages copying? Also what about the newer protections like solidshield or gameshield. An example is dead space 2 which uses solidshield and la noire which uses gameshield. Also the chronicles of riddick assault on dark athena uses solidshield and tages; though that game can be obtained drm free from GOG so it is less of a worry for me.

Also will cd manipulator use the sub file in img/ccd/sub. You said imgburn will ignore the sub file but will cd manipulator accept it?

CD Manipulator does support RAW DAO 96 burning, subcodes generated by the software (when no sub is available) or read from the sub file. ImgBurn is simply RAW SAO, subcodes generated by burner according to the cuesheet sent.

Regarding dumping of Tagès:

http://club.myce.com/showthread.php?t=51912
http://club.myce.com/showthread.php?t=89212

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Thank you very much. Now I have some games that I have dumped. Are there instructions on how do I present these to the redump staff?

18 (edited by pablogm123 2014-05-22 14:43:45)

This subforum:
http://forum.redump.org/forum/11/dumps/

As template, but specifying more clearly what is mastering ring code, mastering SID code, toolstamp, mould SID code and additional mould text, layer from that code and we put <TAB> for any ammount of multiple spaces:
http://forum.redump.org/topic/13553/

Taking this as example, would be this way:

http://redump.org/disc/29391/

Mastering ring code:
Sony DADC<TAB>5057288DVD 01

Mastering SID code:
IFPI LY33

Mould SID code:
IFPI AEW37

And because it's a single layer DVD, only there is codes in that layer, as general rule (certain DVD-5 discs can contain a dummy second layer with codes more or less readable depending on how the artwork cover these codes).

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

I know it's been forever since I posted in this topic but I have a dilemma. I've always dumped my games with alcohol 120 using img, ccd, sub for cds, and mds mdf for certain copy protections like securom. In both of these cases, I make sure to get the subchannel data when it comes to cds. However, I have a new case to deal with: Half Life the original which contains a data track along with 21 or 22 audio tracks. How do I dump this correctly? What are the current tools that people recommend? I used cd manipulator to get the data track but how do I get the audio tracks. Also I don't have a plexor drive so any specific methods for that drive, I don't think will work. On the guide there have been mentions of plexor drives.

Also my main point, how am I supposed to obtain the subchannel data of this game. My normal method of using alcohol 120 will not work. Should I just use the subdump program?

For ripping PC discs with audio tracks, ideally a real Plextor drive should be used, or at least a drive which supports the audio trap disc method to dump the entire disc into scrambled form, and process it manually. My Pioneer DVR-107D, 110D and Optiarc AD-7240S supports audio trap disc method via ejecting the tray by the emergency hole just fine. And my Lite-On LH-20A1P and LTR-48246S support audio trap disc too, but for that these drives have to be dissablembled and used externally to hotswap manually (for that I have many spare magnetic disc holders ripped from the top cover of dead drives) inserted disc without resetting the TOC, so drive thinks disc inserted is a CDDA and can be dumped into scrambled form without modifications.

For more or less *standard PC discs with audio tracks, the classic IsoBuster+EAC method once detected the combined offset should be fine, anyway.

There are currently 5 Half-Life discs of that region in the DB:

http://redump.org/disc/10506/
http://redump.org/disc/26040/
http://redump.org/disc/16573/
http://redump.org/disc/26001/
http://redump.org/disc/25966/

You cannot dump properly track 2 of /disc/26001/ with neither a real Plextor or a swappable drive. Anothers ones yes, assuming that last track isn't truncated by the offset when drive used lacks of overreading into lead-out hability (my Pioneer DVR-107D/110D and my Hitachi-LG GCE-8526B are conventional drives and they can read into the lead-out).

*: no mastering errors, no scrambled data sectors in the first audio track's pregap, no audio sectors in the data track and a generous amount of digital silence in the ending of last track.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

21 (edited by TheDrifter363 2014-06-22 00:33:14)

Um, ok. Lol. So I have an external LG blu ray drive that I use for most of my dumping. I've dumped the first data track with cd manipulator. I didn't have any audio in the data track and I verified it against the other dumps. I've seen scrambled data in track 2's pregap, it had a read+write offset of 651. I'm having trouble determining the read offset. Every time I use EAC, it says overread lead in only, and cd not found in database. What am I supposed to do now? I want to determine the read offset so I can properly dump these tracks. Oh, also this burner supported c2 errors, should I have it enabled or forget about it? Man these discs with audio tracks are hard.

Now if for some reason, my drive's not good enough to submit to your website, is there any way for me to have a good backup of these drives? I wish to preserve them.

Edit: So I did some more reading and I've determined these things. When I detect pregaps for half life the original, I get a 2 second pregap in track 2 and a 2 second pregap in track 1, which is the data track. I used isobuster's sector viewer to determine my read+write offset and I got 651 samples. I found my drive in accuraterip's database and they listed 667 samples for the read offset. This means the value I will put in EAC will be 651. My factory write offset is -16. Also when detecting the pregap, track 6 does not have a read crc, but does have a test crc. I will give some more findings, but it seems as if I'm going to have different checksums as compared to the other dumps. If so, why is this? Games with audio will have different checksums depending on which drive you use? That would make the redump database very large. Maybe I'm not doing something right.

Also with all of this information, is there any way for me to back up these games that contain audio data? Should I just use a ccd, img, sub as I've been doing before. Can ccd capture all the audio tracks successfully?

Edit2: Ok so I ripped the files with EAC and I have some questions. In the log file it said track 6 and 7 were at 99.8 and 99.5 percent accuracy but the crc values matched on both of them. Also none of the music bin files match up with the database. Lastly I have no idea how to mount these files into am image which I can use to install the game. Any help would be appreciated.

22 (edited by pablogm123 2014-06-22 20:25:13)

This is not explained in the official guide, because majority of "hardcore" dumpers started to use real Plextor drives and therefore manual method was considered obsolete...

When in the pregap there is at least one entire scrambled data sector (=2352 bytes/588 samples) or more scrambled data with a visible header, first visible header should be observed very carefully.

http://i.imgur.com/2cmh2uy.png

Requested sector is 22:19:25, and because that sector is marked as audio by the subs drive won't correct the offset. Neither unscramble data.

Drive provides a part of 22:19:20 and the beggining of 22:19:21, that header you can see. Drive is reading 4 sectors before than expected, plus 2324 bytes (because sector 22:19:21 [23:99:21 in scrambled form] starts at 0x914 offset in that screenshot).

2352*4 bytes +2324 bytes = 11732 bytes. Read offset of drive used: +6 samples, +24 bytes.

(11732 bytes - 24 bytes)/4 bytes per sample = 2927 samples, the expected one and verified via a real Plextor drive:

http://redump.org/disc/29165/

With the classic way, user will see that there are 16436 bytes of scrambled data, so that will think that offset once subtracted the read offset of the drive is 4103 samples. Very wrong, because in that pregap there are two scrambled data sectors which belong to the audio track.

Sample of pregap used, untouched and the valid sectors unscrambled, being 22:19:21 the first one.

https://www.dropbox.com/s/t0h467nl9y84v … 0offset.7z

==========

Once properly detected and configured the offset, any drive should dump the very same audio tracks, if there are mismatches (without taking into account read errors themselves):

-First audio track with data in the pregap. In the posted example, if you delete the first 11732 bytes matches the pregap extracted via a Plextor drive and cdtoimg-d8. Sometimes pregaps with scrambled data sectors can be recovered by extracting the pregap range via IsoBuster, adding a few of extra sectors to correct the offset. In this case, extracting 100300-100460 (10 extra sectors to overdump a little) sectors, deleting the first 11732 bytes and resizing the bin so that size is 352800 bytes (deleting now useless data from the ending, not from the beggining). That would be the pregap with data, which could be pasted into the track dumped by EAC to restore it.

-Gaps badly detected, use another drive or another method of detecting gaps in the drive's properties, until getting gaps which make sense. And always configure EAC to analyze EAN aka MCN aka CATALOG and ISRCs, another thing not mentioned in the guide, to get more complete cues, because many discs have the typical CATALOG 0000000000000.

-Last track truncated. With a +667 drive it is somewhat likely that certain last tracks are truncated. Hot swap method (any useless [or not useless if you treat it well and carefully in the process] CDDA disc bigger (speaking of size in sectors) than the disc to dump is fine for that) and then you can run to recover the lost audio samples. Extract the first sectors of lead-out (previously known that sector, for Fury^3 is 191780) and replace the xyz bytes of the track dumped by EAC with the xyz bytes of the lead-out, where xyz is the combined offset for that disc/drive combination. An easier alternative would be another drive where combined offset for that disc is negative (for example, +6 drive for -22 and -12 discs, at least to dump the last track, never the first one unless you restore the possible missing data) or a drive which can overread into the lead-out.

For that drive:
C2 error reporting enabled.
Cache defeating disabled, because caches audio data under 64 KB of audio. 37/39 KB as far I remember.
And of course, makes use of Accurate Stream, because any decent drive since 1998~2000 offer Accurate Stream = constant and predictable offset, not something like +113 in a read, +115 in other, +116 in other... an 8x CD-ROM drive by Panasonic which jitters.

And try +667-12 for that disc, -16 samples isn't a common offset. -12 is.

To mount the image, don't forget to replace MODEx/2xxx with the proper one (MODE1/2352 or MODE2/2352, pretty obvious seeing the byte 15 of the dumped data track, 01=MODE1 and 02=MODE2) and replace every .wav" WAVE with .bin" BINARY, because audio tracks dumped following the guide lack of header.

==========

CCD question: make a CloneCD dump and replace the img created with bins concatenated:

copy /b "Track 01.bin"+"Track 02.bin"+"Track 03.bin"+"Track 04.bin"+... "Name of the IMG.img"

Done, CCD image with the audio ripped securely and with corrected offset. And additionally sub could be replaced with the dumped by subdump if you care.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

23 (edited by TheDrifter363 2014-06-22 04:38:31)

So I dumped the game finally, and it matched! Though I'm having a hard time mounting it. Here is my cue file:

REM DISCID BC0F651C
REM COMMENT "ExactAudioCopy v1.0b3"
PERFORMER "Unknown Artist"
TITLE "Unknown Title"
FILE "01 Track01.bin" BINARY
  TRACK 01 MODE1/2352
    TITLE "Track01"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "02 Track02.bin" BINARY
  TRACK 02 AUDIO
    TITLE "Track02"
    PERFORMER "Unknown Artist"
    INDEX 00 00:00:00
    INDEX 01 00:02:00
FILE "03 Track03.bin" BINARY
  TRACK 03 AUDIO
    TITLE "Track03"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "04 Track04.bin" BINARY
  TRACK 04 AUDIO
    TITLE "Track04"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "05 Track05.bin" BINARY
  TRACK 05 AUDIO
    TITLE "Track05"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "06 Track06.bin" BINARY
  TRACK 06 AUDIO
    TITLE "Track06"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "07 Track07.bin" BINARY
  TRACK 07 AUDIO
    TITLE "Track07"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "08 Track08.bin" BINARY
  TRACK 08 AUDIO
    TITLE "Track08"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "09 Track09.bin" BINARY
  TRACK 09 AUDIO
    TITLE "Track09"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "10 Track10.bin" BINARY
  TRACK 10 AUDIO
    TITLE "Track10"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "11 Track11.bin" BINARY
  TRACK 11 AUDIO
    TITLE "Track11"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "12 Track12.bin" BINARY
  TRACK 12 AUDIO
    TITLE "Track12"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "13 Track13.bin" BINARY
  TRACK 13 AUDIO
    TITLE "Track13"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "14 Track14.bin" BINARY
  TRACK 14 AUDIO
    TITLE "Track14"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "15 Track15.bin" BINARY
  TRACK 15 AUDIO
    TITLE "Track15"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "16 Track16.bin" BINARY
  TRACK 16 AUDIO
    TITLE "Track16"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "17 Track17.bin" BINARY
  TRACK 17 AUDIO
    TITLE "Track17"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "18 Track18.bin" BINARY
  TRACK 18 AUDIO
    TITLE "Track18"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "19 Track19.bin" BINARY
  TRACK 19 AUDIO
    TITLE "Track19"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "20 Track20.bin" BINARY
  TRACK 20 AUDIO
    TITLE "Track20"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "21 Track21.bin" BINARY
  TRACK 21 AUDIO
    TITLE "Track21"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "22 Track22.bin" BINARY
  TRACK 22 AUDIO
    TITLE "Track22"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "23 Track23.bin" BINARY
  TRACK 23 AUDIO
    TITLE "Track23"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "24 Track24.bin" BINARY
  TRACK 24 AUDIO
    TITLE "Track24"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "25 Track25.bin" BINARY
  TRACK 25 AUDIO
    TITLE "Track25"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "26 Track26.bin" BINARY
  TRACK 26 AUDIO
    TITLE "Track26"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "27 Track27.bin" BINARY
  TRACK 27 AUDIO
    TITLE "Track27"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00
FILE "28 Track28.bin" BINARY
  TRACK 28 AUDIO
    TITLE "Track28"
    PERFORMER "Unknown Artist"
    INDEX 01 00:00:00

With the way this is right now, it will not mount. It says corrupt image.

Edit: I was able to figure it out. Apparently my mounting software cannot handle multiple bins. I concatenated them with the copy /b command and sure enough it mounted. Will the ccd file I make from alcohol 120 or clonecd be compatible with the concatenated img file? I ask because the img file from the concatenation is not the same img file from alcohol 120.

Edit2: So I made the ccd file with alcohol 120 and am using the img file made from the concatenation. I have one issue. I'm using CDMage to verify any errors and I should have none. With the bins and cue files, I get no errors; however, with the ccd file I get 150 errors. I noticed that the cue file shows 150 at pause for track 2. When I load up the ccd file, there is no 150 at pause for track 2. The number is 0. How do I add this 150 at pause for track 2 in the ccd file? This should fix the ccd issue.

I am writing this reply to personally thank you pablogm123. You have helped so much in dumping these games, and I wanted to make sure I got them dumped as best as possible. Thank you very much and I very much appreciated what you have done for me.

Delete the REM, TITLE and PERFORMER lines. REM are comments/remarks, unneeded because these ones don't say anything useful. TITLE and PERFORMER only should contain data, in my opinion, data extracted from the actual CD-Text info encoded in the disc when available, not data provided by an online database.

To concatenate the dump, CDmage and Save as. Will create the proper cue (possible CATALOG, ISRCs and another possible flags are lost) for a single file dump, and the bin created by CDmage must match the created by copy /b. Once mounted that image, you can create a CCD/IMG/SUB (can coexist with the cue once edited the cue so that references the proper IMG file) or MDS/MDF dump from the virtual drive.

Regarding CDmage and scanning the image, seems that only can determinate the pause for images opened via a cue, not for ccd files.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot