DiscImageCreator

[MrX_Cuci]

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.

[Nexy]

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.

[V.]

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).

[iR0b0t]

So far all dumps match on 2 different plextor drives.

Nexy, also different models?

[Nexy]

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

[F1ReB4LL]

"03 00 00 00 00 00 00 00 00" should be decoded as "ISRC 000000000000" and you just skip those, it's wrong.

[sarami]

"03 00 00 00 00 00 00 00 00" should be decoded as "ISRC 000000000000" and you just skip those, it's wrong.

"03" is ctl/Adr byte? If it's so, you are right.

[F1ReB4LL]

Yes, it's an ISRC sector. https://redump.info/disc/28248/ -- for this disc it gives me ISRCs for the first 6 tracks only.

[Enker]

The ISO 'Volume Space Size' is being logged incorrectly. My last post explains some issues with DVD dumping.

[sarami]

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

The ISO 'Volume Space Size' is being logged incorrectly. My last post explains some issues with DVD dumping.

fixed