476 Reply by sarami

(3,497 replies, posted in General discussion)

It looks like no UDF disc.

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- fixed: Use "Volume Space Size" if there is not UDF (when disc is BDR, BDRW, DVDRW).

Go to forum: General discussion

477 Reply by sarami

(3,497 replies, posted in General discussion)

It's written in "Logical Volume Integrity Descriptor"

========== LBA[000273, 0x00111]: Logical Volume Integrity Descriptor ==========

        Minimum UDF Read Revision: 0x250
        Minimum UDF Write Revision: 0x260
        Maximum UDF Write Revision: 0x260

Go to forum: General discussion

478 Reply by sarami

(3,497 replies, posted in General discussion)

F1ReB4LL wrote:

http://redump.org/disc/66810/ - why was the 2nd track misdetected as audio? Marked as data in the subs as usual, TOC in disc.txt also says the track type is Data.

Try to use latest test version.

Go to forum: General discussion

479 Reply by sarami

(3,497 replies, posted in General discussion)

Your disc is UDF 2.50
UDF 2.50 says

NOTE: An AnchorVolumeDescriptorPointer structure shall be recorded in at 
least 2 of the following 3 locations on the media: 
• Logical Sector 256. 
• Logical Sector (N - 256). 
• N

N is last sector.

_disc.txt

Detected Anchor Volume Descriptor Pointer: LBA 16669398

Perhaps, last LBA is 16669398 (size is 34138929152).

Go to forum: General discussion

480 Reply by sarami

(3,497 replies, posted in General discussion)

user7 wrote:

Thank you, I've redumped with updated firmware and new DIC as well as IsoBuster https://drive.google.com/file/d/15PSYB6 … sp=sharing

dic size: 34,139,484,160 bytes
isobuster: 34,138,947,584 bytes (same size as before)

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- added: Detect Anchor Volume Descriptor Pointer

Go to forum: General discussion

481 Reply by sarami

(3,497 replies, posted in General discussion)

Resistiv wrote:

Is there at least some indication of what's happening based on the logs?

Failed to get the pregap of 1st track of 2nd session.

Resistiv wrote:

I haven't got any other (functional) Plextor that can dump at the moment.

Then, try to change the other PC if you have.

Nexy wrote:

bushound

I don't understand how to see this log.

Go to forum: General discussion

482 Reply by sarami

(3,497 replies, posted in General discussion)

Resistiv wrote:

DIC is having issues dumping an Enhanced CD

No problem with my 5224TA  (also 4824TA and 755SA). If you have other plextor, try it.

Go to forum: General discussion

483 Reply by sarami

(3,497 replies, posted in General discussion)

user7 wrote:

With LITE ON iHBS112-04 2 drive:

Try to update the firmware https://www.firmwarehq.com/Lite-On/iHBS … files.html

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- fixed: UDF logs

Go to forum: General discussion

484 Reply by sarami

(3,497 replies, posted in General discussion)

Maddog wrote:

I was wondering how a disc with C2 errors can still come back with the correct checksums?

Due to rereading, all sectors with c2 errors turned no error sectors. See _c2Error.txt

user7 wrote:

which size is correct?

I don't know now.

Go to forum: General discussion

485 Reply by sarami

(3,497 replies, posted in General discussion)

ReadCapacity is also same as ReadTOC.

========== ReadCapacity ==========
    Max LBA + 1: 23652352 (0x168e800)

I can't fix this problem now. By the way, how about other BD-R?

Go to forum: General discussion

486 Reply by sarami

(3,497 replies, posted in General discussion)

DIC and other drive are also 48440016896...

added READ CAPACITY log http://www.mediafire.com/file/eq80y20l9 … st.7z/file

user7 wrote:

Dumping slows WAAAAAY down.

It still exists but give me logs.

Go to forum: General discussion

487 Reply by sarami

(3,497 replies, posted in General discussion)

user7 wrote:

2. DIC and other drive                => fails (goes super slow towards the end)

Are there logs?

user7 wrote:

3. Isobuster and PS3 OEM drive => 48440016896
4. Isobuster and other drive       => 34138947584 (size of data on disc)

It looks like PS3 OEM drive problem...

Go to forum: General discussion

488 Reply by sarami

(3,497 replies, posted in General discussion)

1. DIC and PS3 OEM drive          => 48440016896
2. DIC and other drive                => ???
3. Isobuster and PS3 OEM drive => ???
4. Isobuster and other drive       => ???

2 is 34138947584? or 48440016896?
3 is 34138947584? or 48440016896?
4 is 34138947584? or 48440016896?

Go to forum: General discussion

489 Reply by sarami

(3,497 replies, posted in General discussion)

user7 wrote:

DIC is overdumping PS4 kiosk demo (BD-R).

TOC says

========== TOC ==========
      Data Track  1, LBA        0 - 23652351, Length 23652352
                                              Total  23652352

23652352 * 2048 = 48440016896

DAT says

    <rom name="2019 Summer Refresh - Game 89.iso" size="48440016896" crc="747e62f9" md5="1aca828231c4834fa632f87810ad648a" sha1="fad60cc0796f063c7dcba46ea41d38ef82e204b0" />

Is it really overdumping?

Go to forum: General discussion

490 Reply by sarami

(3,497 replies, posted in General discussion)

Madroms wrote:

It is not so hard-damaged, just a few scratches not on the good place

But DIC reports 1206 C2 errors. It's a lot of errors. Not only scratches but other factor give the damage to disc. (e.g. humidity, heat, sunlight, and so on)

Go to forum: General discussion

491 Reply by sarami

(3,497 replies, posted in General discussion)

pool7 wrote:

however there are 4496 errors.

It's error of the lead-in area. Almost all lead-in are unreadable for Plextor.
DIC is padding this area by zero except 1st 16 bytes like this. 1st 16 bytes are generated manually.

LBA[072175, 0x119ef] Read error. padding [2352byte]
========== LBA[072175, 0x119ef]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 17 84 25 61   ..............%a

Lead-in area of this disc is mode 1. Mode 1 disc has edc/ecc but DIC is padding by zero, so EccEdc.exe reports errors.
As a result, 4496 errors can be ignored.

Madroms wrote:

but still some scratches do not let me dump it without c2 errors

Why not get another one if it is possible? C2 errors are problem of the disc, not DIC. DIC (and other dumping tool) is not perfect for hard-damaged disc.

Go to forum: General discussion

492 Reply by sarami

(3,497 replies, posted in General discussion)

Madroms wrote:

TDDDEMO-logs.rar

Try this.

DiscImageCreator.exe cd g ISO\TDDDEMO\TDDDEMO (1).bin 8 /c2 100 /s 2
Madroms wrote:

Three Dirty Dwarves demo disc with scratches that make c2 errors.

I think you should remove scratches. (Disc should be polished.)

Go to forum: General discussion

493 Reply by sarami

(3,497 replies, posted in General discussion)

zcal wrote:

some other threads

Tell me please.

Madroms wrote:

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

See 1st page. http://forum.redump.org/topic/10483/discimagecreator/

Go to forum: General discussion

494 Reply by sarami

(3,497 replies, posted in General discussion)

user7 wrote:

CD-R overdump

Is this really overdump?

user7 wrote:

DVD-R overdump

Up
http://www.mediafire.com/file/eq80y20l9 … st.7z/file
http://www.mediafire.com/file/uw3e03kdk … ar.gz/file

Go to forum: General discussion

495 Reply by sarami

(3,497 replies, posted in General discussion)

Up http://www.mediafire.com/file/eq80y20l9 … st.7z/file
Test please.

Go to forum: General discussion

496 Reply by sarami

(3,497 replies, posted in General discussion)

-The 2 BIN files are 8MB total, while the IMG and SCM files are 34MB each

Yes. Because IMG and SCM include 11400 sectors (lead-out, lead-in, pregap of 1st track of 2nd session). 11400 sectors = 26812800 bytes.

-If I open the CUE corresponding to the BIN files in IsoBuster...

Because this CUE is the original format of redump'org.

-If I open the CUE corresponding to the IMG file in IsoBuster...

Because this CUE is based on IsoBuster.

-If I open the IMG directly in IsoBuster...

Without CUE, IsoBuster can't recognize what it is.

Go to forum: General discussion

497 Reply by sarami

(3,497 replies, posted in General discussion)

user7 wrote:

Still getting overdumps: https://drive.google.com/file/d/12nwgBR … sp=sharing

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
http://www.mediafire.com/file/uw3e03kdk … ar.gz/file
- fixed: FormatCode 0 (ECMA-349 is used for DVD+R)

Go to forum: General discussion

498 Reply by sarami

(3,497 replies, posted in General discussion)

user7 wrote:

DVD-R overdump

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
http://www.mediafire.com/file/uw3e03kdk … ar.gz/file
- fixed: FormatCode 10 (ECMA-279 and 359 are used)

Jackal wrote:

If it's supposed to be the "LayerOneSector" number, then 3 of the 4 discs have an odd number. Can this be correct?

4 discs are "Parallel Track Path", not "Opposite Track Path". I think "LayerZeroSector" number is layerbreak.
e.g. 

========== SectorLength ==========
    LayerZeroSector: 1708076 (0x1a102c)
          :
          :
========== SectorLength ==========
    LayerOneSector: 2079572 (0x1fbb54)
    LayerAllSector: 3787648 (0x39cb80)

L0 is 0 - 1708075 (Length is 1708076). L1 is 1708076 - 3787647 (Length is 2079572).

Go to forum: General discussion

499 Reply by sarami

(3,497 replies, posted in General discussion)

Two PFI exist in DVD-R/-RW.

MMC wrote:

6.27.3.1 Format Code 00h: Physical Format Information
For DVD-R/-RW media, this Format code returns the last updated Physical format information.
Therefore, e.g., if a medium is recorded with multi-bordered area, this information is retrieved from
the last Border-in.  If Control Data Zone information in the Lead-in is required for DVD-R/-RW media,
use format code = 10h.  For all other DVD class media, format code 00h returns information from the
Control Data Zone in the lead-in.

MMC wrote:

6.27.3.17 Format Code 10h: Format Information of Control Data Zone in the Lead-in
This format is available only for DVD-R/-RW media.  For other media, this format is invalid and
reserved.
This Format code returns Physical format information of Control Data Zone in the Lead-in area even if
the disc is recorded with multi-bordered area.

Your logs

FormatCode: 00, Sendable:  No, Readable: Yes
FormatLength: 2052
========== PhysicalFormatInformation ==========
           BookVersion: 5
              BookType: DVD-R
           MinimumRate: Not Specified
              DiskSize: 120mm
             LayerType: Layer contains recordable data
             TrackPath: Parallel Track Path
        NumberOfLayers: Single Layer
          TrackDensity: 0.74um/track
         LinearDensity: 0.267um/bit
    StartingDataSector:  196608 (0x30000)
         EndDataSector: 1913119 (0x1d311f)
    EndLayerZeroSector:       0 (0)
               BCAFlag: No
         MediaSpecific: 
FormatCode: 10, Sendable:  No, Readable: Yes
FormatLength: 2052
========== PhysicalFormatInformation ==========
           BookVersion: 5
              BookType: DVD-R
           MinimumRate: Not Specified
              DiskSize: 120mm
             LayerType: Layer contains recordable data
             TrackPath: Parallel Track Path
        NumberOfLayers: Single Layer
          TrackDensity: 0.74um/track
         LinearDensity: 0.267um/bit
    StartingDataSector:  196608 (0x30000)
         EndDataSector: 2495103 (0x26127f)
    EndLayerZeroSector:       0 (0)
               BCAFlag: No
         MediaSpecific:

EndDataSector is different. I don't know yet why it's different. What is "multi-bordered area"? "last Border-in"?

Go to forum: General discussion

500 Reply by sarami

(3,497 replies, posted in General discussion)

user7 wrote:

does this look good?

Yes.

user7 wrote:

Do I have to change my drive region to dump?

Or you need to get a new DVD drive same as region of DVD-Video.

Go to forum: General discussion