I can contribute to some pages like the the symbols & logos guide. Would love to have a Wiki account. Thank you!

2

(3,520 replies, posted in General discussion)

sarami wrote:

Uploaded.
https://www.mediafire.com/file/eq80y20l … st.7z/file

This subRtoW is rare. Not to detect as suberror.

========== OpCode[0xd8]: SubCode[2]: Check Drive + CD offset ==========
========== LBA[000000, 0000000]: Sub Channel ==========
      +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B
    P FF FF FF FF FF FF FF FF FF FF FF FF
    Q 41 01 01 00 00 00 00 00 02 00 28 32
    R 7F FF FF FF FF FF FF FF FF FF FF FF
    S 7F FF FF FF FF FF FF FF FF FF FF FF
    T 7F FF FF FF FF FF FF FF FF FF FF FF
    U 7F FF FF FF FF FF FF FF FF FF FF FF
    V 7F FF FF FF FF FF FF FF FF FF FF FF
    W 7F FF FF FF FF FF FF FF FF FF FF FF

The test build works like a charm. Thanks Sarami!

3

(3,520 replies, posted in General discussion)

Hi Sarami,

I recently had a couple of discs that produced huge subError.txt (>900MB) files. The dumps were fine but the huge subError files made MPF go haywire. At first I thought it was because the discs got scratches but this one I'm dumping right now is really mint. Could you check the logs?

The game is a rerelease of Panzer General.

Logs: https://1fichier.com/?abkgq2klazswbcbdn42e

4

(3,520 replies, posted in General discussion)

Hey Sarami.

I ran into some issue when trying to capture the console output of DIC into a log file using the >.

Descrambling data sector of img:  10276/ 10297
Descrambling data sector of img:  10277/ 10297
Descrambling data sector of img:  10278/ 10297
Descrambling data sector of img:  10279/ 10297
Descrambling data sector of img:  10280/ 10297
Descrambling data sector of img:  10281/ 10297
Descrambling data sector of img:  10282/ 10297
DescrFILE: D:\Program\Media\Dumping\DiscImageCreator\20210401\1.img

Checking sectors:      0/ 10297
Checking sectors:      1/ 10297
Checking sectors:      2/ 10297
Checking sectors:      3/ 10297

.....


Checking sectors:  10293/ 10297
Checking sectors:  10294/ 10297
Checking sectors:  10295/ 10297
Checking sectors:  10296/ 10297
Checking sectors:  10297/ 10297
[NO ERROR] User data vs. ecc/edc match all
ambling data sector of img:  10283/ 10297

Descrambling data sector of img:  10284/ 10297
Descrambling data sector of img:  10285/ 10297
Descrambling data sector of img:  10286/ 10297
Descrambling data sector of img:  10287/ 10297
Descrambling data sector of img:  10288/ 10297
Descrambling data sector of img:  10289/ 10297
Descrambling data sector of img:  10290/ 10297
Descrambling data sector of img:  10291/ 10297
Descrambling data sector of img:  10292/ 10297
Descrambling data sector of img:  10293/ 10297
Descrambling data sector of img:  10294/ 10297
Descrambling data sector of img:  10295/ 10297


As you can see in the marked sections, some lines seem to be out of place. Is this a bug of DIC or the > redirect command?

Could you add the option to automatically saves the final console output to a log file when dumping is completed?

Like this:

N@N-PC D:\Program\Media\Dumping\DiscImageCreator\20210401
# DiscImageCreator.exe cd j HIOCTANE.bin 8 /c2 /log

HIOCTANE.log:

AppVersion
        x86, AnsiBuild, 20210401T101950
/c2 val1 was omitted. set [4000]
/c2 val2 was omitted. set [0]
CurrentDirectory
        D:\Program\Media\Dumping\DiscImageCreator\20210401
WorkingPath
         Argument: HIOCTANE.bin
         FullPath: D:\Program\Media\Dumping\DiscImageCreator\20210401\HIOCTANE.bin
            Drive: D:
        Directory: \Program\Media\Dumping\DiscImageCreator\20210401\
         Filename: HIOCTANE
        Extension: .bin
StartTime: 2021-05-30T18:19:58+0800
Set the drive speed: 1411KB/sec
This drive supports [OpCode: 0xd8, SubCode: 0]
This drive supports [OpCode: 0xd8, SubCode: 1]
This drive supports [OpCode: 0xd8, SubCode: 2]
This drive supports [OpCode: 0xd8, SubCode: 8]
Checking reading lead-out -> OK
Checking SubQ adr (Track)  1/ 1
Checking SubRtoW (Track)  1/ 1
Checking Pregap sync, msf, mode (LBA)  -1497
Reading DirectoryRecord    7/   7
Set OpCode: 0xd8, SubCode: 8(Raw)
Checking SubQ ctl (Track)  1/ 1
Creating .scm (LBA)  10298/ 10298
No C2 errors
Copying .scm to .img
Descrambling data sector of img:  10297/ 10297
Exec ""D:\Program\Media\Dumping\DiscImageCreator\20210401\EccEdc.exe" check "D:\Program\Media\Dumping\DiscImageCreator\20210401\HIOCTANE.img""
FILE: D:\Program\Media\Dumping\DiscImageCreator\20210401\HIOCTANE.img
Checking sectors:  10297/ 10297
[NO ERROR] User data vs. ecc/edc match all
Creating cue and ccd (Track)  1/ 1
Creating bin (Track)  1/ 1
Hashing: HIOCTANE.scm
Hashing: HIOCTANE.img
Hashing: HIOCTANE.bin
EndTime: 2021-05-30T18:20:50+0800

5

(3,520 replies, posted in General discussion)

Hi Sarami,

Just wondering if you could make DIC save the console output into a log file automatically, like the one below?
I know all the necessary information can be found in other files but this could give us a quick overview of the whole dumping process. What do you think?


EBE_A.log:

# DiscImageCreator.exe cd j EBE_A.bin 8 /c2 /s 2
AppVersion
        x86, AnsiBuild, 20210301T232713
/c2 val1 was omitted. set [4000]
/c2 val2 was omitted. set [0]
CurrentDirectory
        D:\Program\Media\Dumping\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: EBE_A.bin
         FullPath: D:\Program\Media\Dumping\DiscImageCreator\Release_ANSI\EBE_A.bin
            Drive: D:
        Directory: \Program\Media\Dumping\DiscImageCreator\Release_ANSI\
         Filename: EBE_A
        Extension: .bin
StartTime: 2021-04-12T20:31:53+0800
Set the drive speed: 1411KB/sec
This drive supports [OpCode: 0xd8, SubCode: 0]
This drive supports [OpCode: 0xd8, SubCode: 1]
This drive supports [OpCode: 0xd8, SubCode: 2]
This drive supports [OpCode: 0xd8, SubCode: 8]
Checking reading lead-out -> OK
Checking SubQ adr (Track) 25/25
Checking SubRtoW (Track) 25/25
Checking Pregap sync, msf, mode (LBA)  -2245
Set OpCode: 0xd8, SubCode: 8(Raw)
Checking SubQ ctl (Track) 25/25
Creating .scm (LBA) 265829/265829
No C2 errors
Copying .scm to .img
Descrambling data sector of img:  66611/ 66611
Exec ""D:\Program\Media\Dumping\DiscImageCreator\Release_ANSI\EccEdc.exe" check "D:\Program\Media\Dumping\DiscImageCreator\Release_ANSI\EBE_A.img""
FILE: D:\Program\Media\Dumping\DiscImageCreator\Release_ANSI\EBE_A.img
Checking sectors: 265828/265828
[ERROR] Number of sector(s) where user data doesn't match the expected ECC/EDC: 75
Total errors: 75
Total warnings: 0
Creating cue and ccd (Track) 25/25
Creating bin (Track) 25/25
Hashing: EBE_A.scm
Hashing: EBE_A.img
Hashing: EBE_A (Track 01).bin
Hashing: EBE_A (Track 02).bin
Hashing: EBE_A (Track 03).bin
Hashing: EBE_A (Track 04).bin
Hashing: EBE_A (Track 05).bin
Hashing: EBE_A (Track 06).bin
Hashing: EBE_A (Track 07).bin
Hashing: EBE_A (Track 08).bin
Hashing: EBE_A (Track 09).bin
Hashing: EBE_A (Track 10).bin
Hashing: EBE_A (Track 11).bin
Hashing: EBE_A (Track 12).bin
Hashing: EBE_A (Track 13).bin
Hashing: EBE_A (Track 14).bin
Hashing: EBE_A (Track 15).bin
Hashing: EBE_A (Track 16).bin
Hashing: EBE_A (Track 17).bin
Hashing: EBE_A (Track 18).bin
Hashing: EBE_A (Track 19).bin
Hashing: EBE_A (Track 20).bin
Hashing: EBE_A (Track 21).bin
Hashing: EBE_A (Track 22).bin
Hashing: EBE_A (Track 23).bin
Hashing: EBE_A (Track 24).bin
Hashing: EBE_A (Track 25).bin
EndTime: 2021-04-12T20:41:01+0800

6

(3,520 replies, posted in General discussion)

sarami wrote:
RibShark wrote:

A lot of SafeDisc games have this error pattern

Please upload all logs if possible. If not possible, tell me these discs info (title, region, barcode, etc)

In fact, all SafeDisc protected CDs I've encountered in the past few month triggered the same error warnings.

Here are the logs of a disc I just dumped, which is the 3rd CD of the Japanese release of Painkiller.

Barcode: 4 537243 038416

Logs: https://1fichier.com/?h295u1wlv4h7u1tg6bsz

7

(3,520 replies, posted in General discussion)

Hey sarami, can you kindly explain what the /s option for DVD does exactly? I'm dumping a DVD-Video disc protected by CSS/CPPM with it. DIC is reading the disc at an extremely slow speed. Is it normal? Thanks in advance.
# DiscImageCreator.exe dvd i DVD_VIDEO.iso 16 /c
AppVersion
        x86, AnsiBuild, 20190303  04942
CurrentDirectory
        E:\Program\Media\Dumping\DiscImageCreator\Test
WorkingPath
         Argument: DVD_VIDEO.iso
         FullPath: E:\Program\Media\Dumping\DiscImageCreator\Test\DVD_VIDEO.iso
            Drive: E:
        Directory: \Program\Media\Dumping\DiscImageCreator\Test\
         Filename: DVD_VIDEO
        Extension: .iso
StartTime: 2019/03/05(Tue) 13:34:13
Set the drive speed: 22160KB/sec
Writing CMI log(LBA)   780663/ 2103663

Now it's 22:37:00

8

(3,520 replies, posted in General discussion)

sarami wrote:
sarami wrote:

291610 is missing. This is a bug of EccEdc.exe. I'll fix it.
Last sector is correct as ecc/edc, but MSF is incorrect. I'll add this bad MSF as an error.

Test version
20190208 (Windows)
http://www.mediafire.com/file/eq80y20l9 … or_test.7z
20190208 (Linux)
http://www.mediafire.com/file/uw3e03kdk … x_test.tar

Tested working.

Here are the new logs: https://www18.zippyshare.com/v/rM1dACiJ/file.html

9

(3,520 replies, posted in General discussion)

sarami wrote:
nightson wrote:

The test version didn't output the  (Subs indexes) files but the bin file has the same hash as before.

Logs and bin of last 2 sectors and scm of last 2 sectors, please.

Logs: https://www76.zippyshare.com/v/jimIUXBM/file.html

10

(3,520 replies, posted in General discussion)

sarami wrote:
nightson wrote:

Any idea what caused the problem?

Try the latest test version and re-report.
http://www.mediafire.com/file/eq80y20l9 … st.7z/file

nightson wrote:

DIC found no C2 errors but CDmage reports 2 errors at the very end.

Perhaps, last 2 sectors are mastering error.

nightson wrote:

I tried to dump it with two drives (PX-760 and PX-755) at both 4X and 8X but got the same result.

Try 12x, 16x, 20x, 24x, 28x, 32x, 40x and 48x. Low-speed is not always good.

Tried 12x, 24x and 48x with the 20181022 release. The results are exactly the same.

The test version didn't output the  (Subs indexes) files but the bin file has the same hash as before.
Can we safely say it's mastering error?

11

(3,520 replies, posted in General discussion)

Hey sarami,

I tried to dump the Chinese release of Kyrandia III. Everything went well but DIC outputted the (Subs indexes) files along with the normal files. What's weird is that the hashes of the (Subs indexes).bin and (Subs indexes).cue match the normal ones. DIC found no C2 errors but CDmage reports 2 errors at the very end. I tried to dump it with two drives (PX-760 and PX-755) at both 4X and 8X but got the same result. I also tried to dump the CD with IsoBuster but encountered an error at the very end and ended up with a corrupt image. The CD itself is scratch free,  be the way.

Any idea what caused the problem?

Logs:
https://www38.zippyshare.com/v/JpNEaYqx/file.html

12

(3,520 replies, posted in General discussion)

sarami wrote:
nightson wrote:

This particular disc outputs huge subError.txt file. Is it normal?

Not normal.

There were no C2 errors though. Can it be considered as a good dump?

13

(3,520 replies, posted in General discussion)

sarami wrote:

It's the line number of source code. No problem you ignore it.

Thanks! This particular disc outputs huge subError.txt file. Is it normal?

I also noticed that the subError.txt will differ every time even for the same disc. The sub files always match though.

Another thing I don't understand: The _drive.txt file DIC 20180304 outputs always has a value in the WriteSpeed sections, while with DIC 20180419 the WriteSpeed is always 0KB/sec. Why was the write speed set when I'm just reading the disc?

========== SetSpeed ==========
        RequestType: CdromSetSpeed
          ReadSpeed: 1411KB/sec
         WriteSpeed: 199KB/sec
    RotationControl: CdromCAVRotation

Thanks!

14

(3,520 replies, posted in General discussion)

Hi Sarami!

Just curious what the link number at the end of each line in the _subInfo.txt mean? I dumped the same disc with DIC 20180304 and 20180419. The bin files match but I notice that the _subInfo.txt are different.

DIC20180304

LBA[000000, 0000000]: Track[01]: Index is changed from [00] to [01] [L:845]
LBA[000000, 0000000]: Track[01]: 1st LBA of this data track [L:893]
LBA[165616, 0x286f0]: Track[01]: Last LBA of this data track [L:812]
LBA[165617, 0x286f1]: Track[02]: TrackNum is changed [L:816]
LBA[165617, 0x286f1]: Track[02]: Index is changed from [01] to [00] [L:860]
LBA[165767, 0x28787]: Track[02]: Index is changed from [00] to [01] [L:845]
LBA[181043, 0x2c333]: Track[03]: This track doesn't exist the pregap [L:795]
LBA[181043, 0x2c333]: Track[03]: TrackNum is changed [L:820]
LBA[194472, 0x2f7a8]: Track[04]: This track doesn't exist the pregap [L:795]
LBA[194472, 0x2f7a8]: Track[04]: TrackNum is changed [L:820]
LBA[206003, 0x324b3]: Track[05]: This track doesn't exist the pregap [L:795]
LBA[206003, 0x324b3]: Track[05]: TrackNum is changed [L:820]
LBA[219512, 0x35978]: Track[06]: This track doesn't exist the pregap [L:795]
LBA[219512, 0x35978]: Track[06]: TrackNum is changed [L:820]
LBA[233761, 0x39121]: Track[07]: This track doesn't exist the pregap [L:795]
LBA[233761, 0x39121]: Track[07]: TrackNum is changed [L:820]
LBA[246577, 0x3c331]: Track[08]: This track doesn't exist the pregap [L:795]
LBA[246577, 0x3c331]: Track[08]: TrackNum is changed [L:820]
LBA[260299, 0x3f8cb]: Track[09]: This track doesn't exist the pregap [L:795]
LBA[260299, 0x3f8cb]: Track[09]: TrackNum is changed [L:820]
LBA[275122, 0x432b2]: Track[10]: This track doesn't exist the pregap [L:795]
LBA[275122, 0x432b2]: Track[10]: TrackNum is changed [L:820]
LBA[288982, 0x468d6]: Track[11]: This track doesn't exist the pregap [L:795]
LBA[288982, 0x468d6]: Track[11]: TrackNum is changed [L:820]
LBA[303086, 0x49fee]: Track[12]: This track doesn't exist the pregap [L:795]
LBA[303086, 0x49fee]: Track[12]: TrackNum is changed [L:820]
LBA[314460, 0x4cc5c]: Track[13]: This track doesn't exist the pregap [L:795]
LBA[314460, 0x4cc5c]: Track[13]: TrackNum is changed [L:820]
LBA[327697, 0x50011]: Track[13]: Last LBA of this disc [L:906]

DIC20180419

LBA[000000, 0000000]: Track[01]: Index is changed from [00] to [01] [L:865]
LBA[000000, 0000000]: Track[01]: 1st LBA of this data track [L:918]
LBA[165616, 0x286f0]: Track[01]: Last LBA of this data track [L:832]
LBA[165617, 0x286f1]: Track[02]: TrackNum is changed [L:836]
LBA[165617, 0x286f1]: Track[02]: Index is changed from [01] to [00] [L:885]
LBA[165767, 0x28787]: Track[02]: Index is changed from [00] to [01] [L:865]
LBA[181043, 0x2c333]: Track[03]: This track doesn't exist the pregap [L:815]
LBA[181043, 0x2c333]: Track[03]: TrackNum is changed [L:840]
LBA[194472, 0x2f7a8]: Track[04]: This track doesn't exist the pregap [L:815]
LBA[194472, 0x2f7a8]: Track[04]: TrackNum is changed [L:840]
LBA[206003, 0x324b3]: Track[05]: This track doesn't exist the pregap [L:815]
LBA[206003, 0x324b3]: Track[05]: TrackNum is changed [L:840]
LBA[219512, 0x35978]: Track[06]: This track doesn't exist the pregap [L:815]
LBA[219512, 0x35978]: Track[06]: TrackNum is changed [L:840]
LBA[233761, 0x39121]: Track[07]: This track doesn't exist the pregap [L:815]
LBA[233761, 0x39121]: Track[07]: TrackNum is changed [L:840]
LBA[246577, 0x3c331]: Track[08]: This track doesn't exist the pregap [L:815]
LBA[246577, 0x3c331]: Track[08]: TrackNum is changed [L:840]
LBA[260299, 0x3f8cb]: Track[09]: This track doesn't exist the pregap [L:815]
LBA[260299, 0x3f8cb]: Track[09]: TrackNum is changed [L:840]
LBA[275122, 0x432b2]: Track[10]: This track doesn't exist the pregap [L:815]
LBA[275122, 0x432b2]: Track[10]: TrackNum is changed [L:840]
LBA[288982, 0x468d6]: Track[11]: This track doesn't exist the pregap [L:815]
LBA[288982, 0x468d6]: Track[11]: TrackNum is changed [L:840]
LBA[303086, 0x49fee]: Track[12]: This track doesn't exist the pregap [L:815]
LBA[303086, 0x49fee]: Track[12]: TrackNum is changed [L:840]
LBA[314460, 0x4cc5c]: Track[13]: This track doesn't exist the pregap [L:815]
LBA[314460, 0x4cc5c]: Track[13]: TrackNum is changed [L:840]
LBA[327697, 0x50011]: Track[13]: Last LBA of this disc [L:931]

I also attached logs that have differences in the attachment FYI.
I'm new to redump so please bear with me if this is a stupid question tongue
Thanks!

15

(5 replies, posted in General discussion)

user7 wrote:

We pretty much only use Disc Image Creator here due to it's features and logs, here is more info smile

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

You're welcome to message me if you have any questions, I wrote the guide.

Thanks! I just bought a PX-760A and a PX-755A a while ago and starting dumping my PC games recently with DIC. Will need to learn more about dumping though. I have little knowledge of CD data structure such as sub channel. Is there any detailed guide somwhere that can help me have a comprehensive understanding of CD and DVD?

16

(5 replies, posted in General discussion)

Jackal wrote:

Advertisement?

Of course not. I just came across it and wanted to know if it is capable of replacing CloneCD or CD Manipulator. I never heard of it before, nor do I anything to do with the developer. Sorry if my post broke any rules here. Should I delete it?

17

(5 replies, posted in General discussion)

I just came across this program when searching other stuff. Has anyone tried it before? How does it compare to CloneCD or CD Manipulator (which it's claimed to be base on)?

https://www.rizonesoft.com/downloads/carbon-cd/

Description from the official site:

Use Carbon CD to make backup copies of your music or data CDs. Copy (Clone) most CDs in just a few mouse clicks. Create perfect 1:1 copies or save your CDs to your computer. If you are familiar with Clone CD, you should feel right at home using Carbon CD. The biggest difference between the two is that Carbon CD does not support DVDs yet (Still working on it).

Carbon CD is based on the CD Manipulator code created by Y. Kanechika. Originally in Japanese, It now supports English by default. I upgraded the project from Visual Studio 2005 to Visual Studio 2010 and cleaned the code. I also upgraded all the graphics, worked on skinning, beautified all the dialog boxes and sorted all the bugs I could find. Let me know if you find more.
Carbon CD Main Screen

General Features

    Create 1:1 copies onto CD-Rs and CD-RWs.
    Supported formats: ISO, IMG, CUE, CCD, CDM
    Does not require an ASPI driver.
    Show Drive capabilities.
    MSF Calculator.
    Erase CD-RW media.
    CD and Image File mastering.
    Rip audio tracks.
    Copy Protect CDs.

Reading Features

    Copies CDs in Single-Session mode or Multi-Session (RAW) mode.
    Analyze pregap.
    Analyze sub code.
    Ignore read errors.
    Fast error skip.
    Intelligent bad sector scanner.
    Swap audio channel.

Writing Features

    Perform Optimum Power Calibration.
    Buffer-Underrun Protection.