2,226

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.

2,227

DIC is over-dumping a DVD-R.

DIC logs: https://drive.google.com/file/d/15PsgjX … sp=sharing

I dumped twice with IsoBuster and once with IMG Burn to get the same hashes / size: 3.27 GB (3,515,416,576 bytes)

Here's IMG Burn analysis:

PLEXTOR DVDR   PX-755A 1.08 (USB)
Current Profile: DVD-R

Disc Information:
Status: Complete
Erasable: No
Sessions: 1
Sectors: 1,716,512
Size: 3,515,416,576 bytes
Time: 381:28:62 (MM:SS:FF)
Supported Write Speeds: 6x, 8x, 12x, 16x

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 1716511)
-> LeadOut  (LBA: 1716512)

Pre-recorded Information:
Manufacturer ID: TTH02

Recording Management Area Information:
PIONEER DVD-RW DVR-118L DVD-RW DVR-118L

Physical Format Information (Last Recorded):
Book Type: DVD-R
Part Version: 5
Disc Size: 120mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 1,913,119
Last Physical Sector in Layer 0: 0

Performance (Write Speed):
Descriptor 1...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 1716511 (0x001A311F)
-> RS: 16,620 KB/s (12x) - WS: 8,310 KB/s (6x)
Descriptor 2...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 1716511 (0x001A311F)
-> RS: 16,620 KB/s (12x) - WS: 11,080 KB/s (8x)
Descriptor 3...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 1716511 (0x001A311F)
-> RS: 16,620 KB/s (12x) - WS: 16,620 KB/s (12x)
Descriptor 4...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 1716511 (0x001A311F)
-> RS: 16,620 KB/s (12x) - WS: 22,160 KB/s (16x)

Issues properly dumping *-Rs seems to be a recurring theme with dic that's never been completely fixed over the years. Most discs do not have issues, but throughout the years, issues have arisen from dumping *-Rs in dic that work in IsoBuster properly.

2,228

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"?

2,229 (edited by Jackal 2019-11-02 16:15:39)

@sarami, TeamEurope dumped 4 DVD9's but we can't find the correct LayerBreak values in the disc log (logs attached).

If it's supposed to be the "LayerOneSector" number, then 3 of the 4 discs have an odd number. Can this be correct? The new disc form only accepts even numbers.

The last 4 submitted dumps all have even numbers:
http://redump.org/disc/65955/
http://redump.org/disc/65956/
http://redump.org/disc/65957/
http://redump.org/disc/65958/
so I dont know what's wrong.

Post's attachments

logs.rar 1002.57 kb, 3 downloads since 2019-11-02 

You don't have the permssions to download the attachments of this post.

2,230

Another Press Kit DVD-R overdump logs (in case they're useful for troubleshooting): https://drive.google.com/file/d/1537OZB … sp=sharing

2,231

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

2,232

sarami wrote:

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

Makes sense, thanks for clarifying

2,233

Jackal wrote:

Makes sense, thanks for clarifying

I think i speak for 90+% of people here when i say.... "nope. it's still all gobbledegook"

and this is why we arent mods big_smile

2,234 (edited by user7 2019-11-04 03:49:57)

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

2,235 (edited by sarami 2019-11-05 08:00:25)

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)

2,236

I dumped and submitted 2 Dreamcast Unlicensed MIL-CD (multisession) yesterday.
No errors during dumping (see logs below); however I now noticed the following:
-The 2 BIN files are 8MB total, while the IMG and SCM files are 34MB each
-If I open the CUE corresponding to the BIN files in IsoBuster and try to read session 2, there's an error "The path table (ISO 9600) couldn't be read properly. Only 0 of 1 blocks could be read. Read error at address: 13855. Device reported error: 05/63/03". The same error appears if I open just Track 2 BIN
-If I open the CUE corresponding to the IMG file in IsoBuster , I can read session 2 just fine, no errors.
-If I open the IMG directly in IsoBuster (without using the corresponding CUE file), it says it can't detect a filesystem.

Is this normal/expected?

Logs:
https://mega.nz/#!q6xQGKTY!bibbH9ssN5Z_ … kNQQp4mJ6E
https://mega.nz/#!iihiSAyC!DUR26IvUie6d … pIzuUhc0mo

2,237

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

2,238

Got it; thanks for the explanation smile

2,239 (edited by user7 2019-11-06 06:16:39)

When dumping a press kit CD-R, it crashes converting from img to bin: https://drive.google.com/file/d/1JOaw_r … sp=sharing

edcchk shows the .img has 0 errors.

isobuster is dumping the disc with consistent hashes, different than dic's .img hashes.

2,240

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

2,241

Works and matches IsoBuster, thanks!

2,242

Despite the improvement I'm still getting overdumps on some discs.

CD-R overdump: https://drive.google.com/file/d/1eTf-J5 … sp=sharing
DVD-R overdump: https://drive.google.com/file/d/1EXNDBR … sp=sharing

2,243

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

2,244 (edited by user7 2019-11-09 17:02:42)

I'll investigate the CD-R further, dic, isobuster and imgburn all have different results.

The new DIC build works for the DVD-R thanks!! (hashes match IsoBuster)

2,245 (edited by Madroms 2019-11-09 18:28:36)

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.

Saturn Database {-} Retro Deals search engine that helps you find stuff (plextor drives, games, etc.) easily on eBay {-} My Redump Logs

2,246

I'm unable to get DIC to dump using my drive.  I'm using a Pioneer DVR-XD09 with DIC 20191001 on Linux and am testing with PlayStation discs.

Using the basic arguments for dumping a CD:

./DiscImageCreator_linux.out cd /dev/sr0 foo.bin 24

I get the below output:

This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 1]
Failed to get write-offset
Retry 1/10 after 10000 milliseconds

What can I do?  Am I out of luck with this drive?

2,247

The readme in the OP has a list of supported drives. https://github.com/saramibreak/DiscImag … /README.md

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)

2,248

Nexy wrote:

The readme in the OP has a list of supported drives. https://github.com/saramibreak/DiscImag … /README.md

I know I've seen some other threads where unlisted drives were used to dump.  I was just wondering if there's any other troubleshooting I can do for my error.  Sounds like not.

2,249

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/

2,250

sarami wrote:
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/

See my sig to download the logs. There are:
TDDDEMO-logs.rar
TDDDEMO_4012TA-logs.rar

This is a US Saturn disc: Three Dirty Dwarves demo disc with scratches that make c2 errors.
ringcode: SATURN14004 P1H IFPI L238

Saturn Database {-} Retro Deals search engine that helps you find stuff (plextor drives, games, etc.) easily on eBay {-} My Redump Logs