Search options (Page 1 of 2)

Great, it works with 716A. Thanks.
I didn't see the issues on GH.

Adding a warning or a stop (like when using ODD without latest firmware) when someone try to dump a multisession disc with PW4012 and other ODD not compatible: is it possible?

I pretty sure you will have some other users asking the same in the future

Latest dump for my GEX US on 4012a: GEX_US_4012_F-logs.rar
so with c2 and f params: no error on sector 97747, but 2 bad MSF and sector 98215 with ECC/EDC error.

I also added the T... logs in case you need them.

So I try to sum this up (for other users):
DIC + my 4012 ODD with [SS] GEX US disc:
- with c2 param: no c2 error reported but 1 sector (97747) with EDC/ECC error => bad dump
- with c2 param + f param: no c2 error reported, sector 97747 is good but 1 sector (98215) with EDC/ECC error and 2 MSF errors => bad dump
- with no c2 param: sector 97747 is good but a lot of errors: 697 MSF errors, 7 ECC/EDC errors, 60 invalid sync => bad dump
- with no c2 param + with f param: sector 97747 is good but 2 MSF errors + 7 ECC/EDC errors => bad dump
- same results with latest DIC test
[why the sector 97747 is bad with c2 param, but good without it ? Something I don't understand myself]

DIC + my 716a ODD with [SS] GEX US disc:
- with c2 param: no error => good dump
- without c2 param: no error  => good dump

DIC + my 4012 ODD: Speed param does not work correctly: it always dump at 2x

Other tools + my 4012 ODD with [SS] GEX US disc:
- T...: good dump
- cdtoimg: good dump (scrambled, no offset correction)
- Isobuster: good dump
- CD Manipulator: good dump

So at the moment, dumping with DIC on 4012 ODD is not 100% accurate as there could be errors not identified correctly.
For example, I think about PSX games where ECC/EDC errors could be normal, but, as seen with my GEX US [SS] disc, these errors could also be due to a problem with DIC+4012.
On the opposite, a game with intended errors could be dumped without error reported but DIC on 4012 ODD, whereas it must have errors.
=> with this setup (DIC+4012 ODD), you could have:
Games without intended error dumped with errors (no c2 error, but errors in MSF, ECC/EDC, etc.)
Or games with intended errors dumped without error.

How to avoid these problems with 4012 ODD ?
As other dumpers stated the 4012 ODD is the best Plextor drive to dump CDs, how could we help to improve the use of DIC with such ODD ?

Or any other users with [SS] GEX US disc and 4012 ODD ? To confirm the problem (or not).

[FYI, I also identified a bug with 755 ODD some months ago, when dumping 2 3DO games, Killing Time and Icebreaker 2 if I remember correctly].

4 more logs available.
With 716a: no problem, no error, good dump
With 4012 and DIC: sector 97747 without error, but a lot of new errors (697) on other sectors (MSF, ECC/EDC, sync). How is it possible when with c2 param there is no error on any of these sectors ?
With 4012 and DIC test (2 dumps made): sector 97747 without error, but a lot of new errors (677, so 20 less than with DIC official release) on other sectors (MSF, ECC/EDC, sync).

Ok, so I made more tests, all with the 4012 ODD. Here are the results:
- DIC: bad dump
- latest test DIC: bad dump
- Isobuster: good dump
- T...: good dump
- CD Manipulator: good dump
So DIC problem with 4012 ODD maybe ?

Difference could be seen in the picture attached: part of the EDC/ECC field of sector 97747, total of 96 bytes.

Do you need any other logs ?

I have some japanese Video CD Karaoke by clarion. I think they are not CD-G discs, just VCD discs (has CDI, KARAOKE, MPEGAV and VCD dirs) like Sega Prologue ones. They are seen by DIC as DiscType: CD-ROM XA Disc. I think they are not useful for redump.
So what to do with them also ?

sarami, could you check the log for this disc ?
http://forum.redump.org/topic/26845/pro … rihen-jpn/

If tests are needed, I also have this disc.

Thee are some spots and some linear scratches from center to outer. But I think the c2 errors are also due to how the disc was (badly) polished by the previous owner ( so the laser may be not reflected correctly ?).

2 different plextor drives gave me approx the same amount of c2 errors (with no luck with reread). I was able to dump the disc with isobuster with a non plextor drive with only a few low errors in the ecc/edc fields (all that could be repaired with cdmage).
So, something to try in the future for this disc, with multiple drives.

It works: for the log if you want to check it for the /s 2 param: TDDwith_s2-logs.rar

but still some scratches do not let me dump it without c2 errors. The disc seems to have been already polished, but the scratches that are still there produce c2 errors. I will see later what to do.
But for now, /s 2 did the trick for the internal error.

sarami, what can be the cause for this error message when dumping a cd ?

[L:1226] Internal error. Failed to analyze the subchannel. Track[02]/[09]

Scratches on cd, or something else ?

I got this for 1 cd, with 2 different drives.

I notice this today:
when dumping CD with DIC 20190708 115259,
the line "Creating .scm (LBA) xxx/YYY" do not have consistent YYY value (last sector).

For http://redump.org/disc/45731/ it reports 157995 [correct as the game has 157996 sectors, from 0 to 157995]

AppVersion
        x86, AnsiBuild, 20190708 115259
/c2 val2 is omitted. set [0]
E:\Redump\Release_ANSI\ISO\test\ doesn't exist, so create.
CurrentDirectory
        E:\Redump\Release_ANSI
WorkingPath
         Argument: ISO\test\test (1).bin
         FullPath: E:\Redump\Release_ANSI\ISO\test\test (1).bin
            Drive: E:
        Directory: \Redump\Release_ANSI\ISO\test\
         Filename: test (1)
        Extension: .bin
StartTime: 2019/09/18(Wed) 20:15:48
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-in -> OK
Checking SubQ adr (Track)  1/ 1
Checking SubRtoW (Track)  1/ 1
Set OpCode: 0xd8, SubCode: 8(Raw)
LBA[-00001, 0xffffffff]: Q[4101000000000000017404a1]
Checking SubQ ctl (Track)  1/ 1
Creating .scm (LBA) 157995/157995
No C2 errors
Copying .scm to .img
Descrambling data sector of img (LBA) 157995/157995
Exec ""E:\Redump\Release_ANSI\EccEdc.exe" check "E:\Redump\Release_ANSI\ISO\test
\test (1).img""
FILE: E:\Redump\Release_ANSI\ISO\test\test (1).img
Checking sectors (LBA) 157995/157995
[NO ERROR] User data vs. ecc/edc match all
Creating bin, cue and ccd (Track)  1/ 1
Hashing: test (1).scm
Hashing: test (1).img
Hashing: test (1).bin
EndTime: 2019/09/18(Wed) 20:20:52

For http://redump.org/disc/5305/ it reports 205250 [incorrect as the game has 205250 sectors, and so the last sector that must be reported is 205249]
But, on lines "checking sectors (LBA) xxx/YYY" and "Descrambling data sector of img (LBA) xxx/YYY" it reports 205249 which is correct.

StartTime: 2019/09/18(Wed) 18:57:21
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
Set OpCode: 0xd8, SubCode: 8(Raw)
LBA[-00001, 0xffffffff]: Q[4101000000000000017404a1]
Checking SubQ ctl (Track)  1/ 1
Creating .scm (LBA) 205250/205250
No C2 errors
Copying .scm to .img
Descrambling data sector of img (LBA) 205249/205249
Exec ""E:\Redump\Release_ANSI\EccEdc.exe" check "E:\Redump\Release_ANSI\ISO\JMFB
97\JMFB97 (1).img""
FILE: E:\Redump\Release_ANSI\ISO\JMFB97\JMFB97 (1).img
Checking sectors (LBA) 205249/205249
[NO ERROR] User data vs. ecc/edc match all
Creating bin, cue and ccd (Track)  1/ 1
Hashing: JMFB97 (1).scm
Hashing: JMFB97 (1).img
Hashing: JMFB97 (1).bin
EndTime: 2019/09/18(Wed) 19:04:06

Is it normal, or corrected in new version ?

No effect on the dump btw.

Edit:
another example:

StartTime: 2019/09/18(Wed) 19:44:45
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
Set OpCode: 0xd8, SubCode: 8(Raw)
LBA[-00001, 0xffffffff]: Q[4101000000000000017404a1]
Checking SubQ ctl (Track)  1/ 1
Creating .scm (LBA) 256450/256450
No C2 errors
Copying .scm to .img
Descrambling data sector of img (LBA) 256449/256449
Exec ""E:\Redump\Release_ANSI\EccEdc.exe" check "E:\Redump\Release_ANSI\ISO\FZ-S
M0401(DEMO)\FZ-SM0401(DEMO) (1).img""
FILE: E:\Redump\Release_ANSI\ISO\FZ-SM0401(DEMO)\FZ-SM0401(DEMO) (1).img
Checking sectors (LBA) 256449/256449
[NO ERROR] User data vs. ecc/edc match all

I will test the latest build of DIC tomorrow.