I get an error but it still continues which is weird.

102

The ANSI build is crashing on CD-TEXT CDs with these two versions:
20130222
20130203

Enker wrote:

The ANSI build is crashing on CD-TEXT CDs with these two versions:
20130222
20130203

fixed

104

I found some CCD file issues:

CloneCD wrote:

[TRACK 1]
MODE=0
FLAGS= DCP
INDEX 1=30

DiscImageCreator wrote:

[TRACK 1]
MODE=0
INDEX 0=0
INDEX 1=30

Here are the .ccd files: http://www.mediafire.com/?z3idm72x26751d8

105

That's a bug in CloneCD

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

Enker wrote:

I found some CCD file issues:

CloneCD wrote:

[TRACK 1]
MODE=0
FLAGS= DCP
INDEX 1=30

I don't write "FLAGS" in ccd file at the present.
Fix at the next release.

Enker wrote:
DiscImageCreator wrote:

[TRACK 1]
MODE=0
INDEX 0=0
INDEX 1=30

Here are the .ccd files: http://www.mediafire.com/?z3idm72x26751d8

I don't know a specification in detail about a disc including "INDEX 0" to "TRACK 1".
need or not "INDEX 0" in "TRACK 1"?

in case of clonecd
don't write "INDEX 0" in "TRACK 1". in cue & ccd file.
in case of CDRWIN
write "INDEX 0" in "TRACK 1" in cue file.

107 (edited by Enker 2013-03-09 03:56:11)

I agree with Nexy, the missing INDEX 0 for Track 1 is a bug with CloneCD. The .cue files here on redump don't have an INDEX 0 for Track 1 when INDEX 1 is >00:00:00. This should be fixed.

I noticed that the last track for my disc is being underdumped. The last 30 sectors are lost with DiscImageCreator and not with other tools.

108 (edited by sarami 2013-03-10 01:46:42)

Enker wrote:

I found some CCD file issues:

CloneCD wrote:

[TRACK 1]
MODE=0
FLAGS= DCP
INDEX 1=30

Enker wrote:

I noticed that the last track for my disc is being underdumped. The last 30 sectors are lost with DiscImageCreator and not with other tools.

fixed

109

Thanks! I tested it and everything is working fine smile

I sent a message to iR0b0t about the redump .cue file issue.

110

All tools just assume when burning, that track 1 has a pre gap of 2:00. Dunno why this is, or if you can even burn the real pre gap even if you dumped it in dao mode.

The cue/ccd is there to recreate the TOC on the original disc, if subs are burned too they can of course conflict with TOC like on many discs. Quite interesting how firmwares get around these inconsistencies. Protections could however check for these non-standard conditions... but rainbow books specs are rarely followed to the letter.

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

111

Here are some DVD dumping issues/requests:


Only L0 is dumped on the following disc type (example):
TrackPath: Parallel Track Path
NumberOfLayers: Double Layer

Checking for "PhysicalFormatInformation: L1" will probably fix this issue.
Opposite Track Path DVD-9 discs are also being overdumped.


Could you please add TOC+Layer Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 4169567)
-> LeadOut  (LBA: 4169568)
Layer 0 Sectors: 2084944
Layer 1 Sectors: 2084624

112

Done some safedisc disc testing now. It is able to dump safedisc's bad sectors reliably. So far all dumps match on 2 different plextor drives. So far one disc , Daikatana, has been verified from 2 different discs (mine and DJoneK's). However, I think that such discs can ONLY be dumped on plextor drives.

This is both good and bad, the good is safedisc and probably laserlok can be dumped properly now. The bad news is all of those discs in the db need to be dumped again, or invalidated.

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

113 (edited by Jackal 2013-03-19 20:10:21)

Nexy wrote:

Done some safedisc disc testing now. It is able to dump safedisc's bad sectors reliably. So far all dumps match on 2 different plextor drives. So far one disc , Daikatana, has been verified from 2 different discs (mine and DJoneK's). However, I think that such discs can ONLY be dumped on plextor drives.

This is both good and bad, the good is safedisc and probably laserlok can be dumped properly now. The bad news is all of those discs in the db need to be dumped again, or invalidated.

IIRC the drive reports c2 errors on those sectors, so who's to say that the data is dumped 1:1 and it isn't some pattern that is unique to plextor drives (otherwise why do audio trap dumps on non-plextor drives give different data)? I'd rather hear first what truong and ripper discovered in their research and how they implemented safedisc dumping into trurip (afaik they talked to the designers). And is there any real point in redumping all these hundreds of discs (many of which will be unavailable and have to be bought again)? Error sector = error sector and I doubt it can be burned and then dumped again 1:1? And then we also have to redump all SafeDisc etc. DVD's into RAW?  roll

114 (edited by Nexy 2013-03-19 23:48:02)

why would the raw read data vary from drive to drive ... that doesn't really make any sense. scrambling is not the complicated process it seems, it's just EOR of a pattern and I found that pattern in the firmware too. I think that was only an issue on very early hardware. I would like to have a dump of the disc done with an audio trap CD tho.

I also highly doubt they even know who the designers were, sounds like ripper BS to me.

Also, redump is about preservation right? It's not about "because it works"... or am I wrong? If it is... maybe I am in the wrong place.

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

115 (edited by MrX_Cuci 2013-03-20 13:23:04)

Back in the day you had so called sheep burners (referring to the CloneCD mascotte)

I googled somewhat and found:
Here are two drives capable of reading the weak sectors of Safedisc
http://www.cdrinfo.com/Sections/Reviews … p;PageId=3
http://www.cdrinfo.com/Sections/Reviews … p;PageId=4

They in turn produce a working copy when burned back to disc. (without using protection emulation) Look up your own drive for capabilities. (maybe we should make our own chart?)

http://club.myce.com/f81/sheep-test-guide-101608/

There was a chart ones, but can't seem to find. (which reader / burner was good for dumping)

My guess is these versions are the same:
http://redump.org/disc/10567/
http://redump.org/disc/18847/
But produced different hashes due to the drive being used. I tested my dump using Daemon Tools without Safedisc emulation. Do not know if Nexy did this aswell. (or anyone else tried)

As far as I know there is no DVD drive capable of dumping DVD protections correctly

MrX_Cuci wrote:

My guess is these versions are the same:
http://redump.org/disc/10567/
http://redump.org/disc/18847/
But produced different hashes due to the drive being used.

That's bullshit.. safedisc dumps should give identical hashes on different drives.. are you sure that you dumped it correctly? Did anyone compare these images?

117 (edited by MrX_Cuci 2013-03-20 14:02:06)

I still have the discs. Dumping it now on a different drive. I am not sure if I did this back then.

Now I know why I did not do it. Unable...DDump won't let me dump it on my LG drive. Isobuster comes up with a replace sectors message which you should not do if I am correct.

I checked my logs and game was dumped twice on my Plextor

Can't you try clonecd? it should give the same results

119

You could check the bad sectors in cdmage to see if they contain the 0x55 pattern?
If not, then changing those sectors to 0x55 should match up Nexy's dump if it's the same.

We SHOULD dump SafeDisc discs in two different drives before submite the hashes to the DB!
But in battlefield Vietnam case this could be normal...
The only difference in this dumps: http://redump.org/disc/7447/ and http://redump.org/disc/9924/ are a couple of bytes in sector 16 (if i recall well) so nothing to do with the unreadable sectors.

"Did you ever wonder why we had to run for shelter when the promise of a brave new world unfurled beneath a clear blue sky?"

121 (edited by MrX_Cuci 2013-03-20 18:18:05)

Same hashes as cloneCD dump indeed. (different drive) Weird to me. Why were there crackers back in the day when they just could have used clonecd? The only reason I can think of is that a lot of burners couldn't write such an image properly. As posted in the above forum link.

122

Use plextor, dump with clonecd and also dump with disk image creator.

That stuff is bs with being able to read the bad sectors, the images will work if the sectors are just bad, not really what is on the disc.

As for burning, seems it's firmware bugs not being able to burn all patterns in proper order, the buffers get written to the disc in the wrong order but the data is there.

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

123

MrX_Cuci wrote:

Same hashes as cloneCD dump indeed. (different drive) Weird to me. Why were there crackers back in the day when they just could have used clonecd? The only reason I can think of is that a lot of burners couldn't write such an image properly. As posted in the above forum link.

Safedisk 2 has a few sectors in them which were designed to not be writable (due to overloading the writers EFM encoder).
However, some writers were capable of doing this still in those days.
Nowadays, I think all writers are fast enough to be able to do this.
In any case, these are not the bad sectors which you get on read, those are a reading protection (the idea was to make dumping the disk take ages)
Also, safedisk 2 was devised in a time when disk emulators like daemon tools and alcohol were not invented yet (or just barely invented).

Nexy wrote:

So far all dumps match on 2 different plextor drives.

Nexy, also different models?

PX-760A (+30), PX-W4824TA (+98), GSA-H42L (+667), GDR-8164B (+102), SH-D162D (+6), SOHD-167T (+12)

125

ir0b0t: yes, 2 different HW revision 5224a and 760a

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)