DL Coasters from ISO

[ibu]

Hi, I've checked the guides, the FAQ, and the forums, but I still haven't been able to figure out why I've been making so many coasters.

 

Almost every time I try to burn a disk, I get an error at some point. To give you guys something concrete, I saved the error text and log from the most recent attempt.

 

Here's the error text:

I/O Error!

Device: [1:1:0] PBDS DVD+-RW DH-16W1S 2D14 (F:) (ATA)

ScsiStatus: 0x02
Interpretation: Check Condition

CDB: 28 00 00 1F EF 60 00 00 01 00
Interpretation: Read (10) - Sector 2092896

Sense Area: 70 00 03 00 00 00 00 0A 00 00 00 00 11 05 00 00 00 00 00 00 00 00 00 00
Interpretation: L-EC Uncorrectable Error

 

Here's the annotated log:

I 08:57:58 ImgBurn Version 2.3.2.0 started!
I 08:57:58 Microsoft Windows Vista Home Premium Edition (6.0, Build 6000)
I 08:57:58 Total Physical Memory: 3,142,988 KB  -  Available: 2,260,220 KB
I 08:57:58 Initialising SPTI...
I 08:57:58 Searching for SCSI / ATAPI devices...
I 08:57:58 Found 1 DVD-ROM/CD-RW and 1 DVD±RW!

First I ran it in test mode.  No problems:
I 09:00:47 Operation Started!
I 09:00:47 Source File: C:\NAME_OF_MYDVD3_D3.MDS
I 09:00:47 Source File Sectors: 3,595,395 (MODE1/2048)
I 09:00:47 Source File Size: 7,363,368,960 bytes
I 09:00:47 Source File Volume Identifier: NAME_OF_MYDVD3_D3
I 09:00:47 Source File Implementation Identifier: Daikin U.S. Comtec Lab
I 09:00:47 Source File File System(s): ISO9660, UDF (1.02)
I 09:00:47 Destination Device: [1:1:0] PBDS DVD+-RW DH-16W1S 2D14 (F:) (ATA)
I 09:00:47 Destination Media Type: DVD-R DL (Disc ID: RITEKP01) (Speeds: 2x, 4x)
I 09:00:47 Destination Media Sectors: 4,172,816
I 09:00:47 Write Mode: DVD
I 09:00:47 Write Type: DAO
I 09:00:47 Write Speed: MAX
I 09:00:47 Link Size: Auto
I 09:00:47 Test Mode: Yes
I 09:00:47 BURN-Proof: Enabled
I 09:00:47 Optimal L0 Data Zone Capacity: 1,804,112
I 09:00:47 Optimal L0 Data Zone Method: Copied From Original Disc
W 09:00:49 Cannot set the layer break position when burning DVD-R DL media in DAO mode.
I 09:00:49 Filling Buffer... (40 MB)
I 09:00:50 Writing LeadIn...
I 09:01:14 Writing Image... (LBA: 0 - 3595394)
I 09:01:14 Writing Layer 0... (LBA: 0 - 2092895)
I 09:14:11 Writing Layer 1... (LBA: 2092896 - 3595394)
I 09:23:39 Synchronising Cache...
I 09:28:15 Cycling Tray after Test Write...
I 09:28:21 Image MD5: 2c2006ee9e303888a2afc6d5a7ee1df8
I 09:28:21 Operation Successfully Completed! - Duration: 00:27:34
I 09:28:21 Average Write Rate: 5,346 KB/s (3.9x) - Maximum Write Rate: 5,604 KB/s (4.0x)

Then I ran it with test mode off and verify on. The write had no errors:
I 09:29:10 Operation Started!
I 09:29:10 Source File: C:\NAME_OF_MYDVD3_D3.MDS
I 09:29:10 Source File Sectors: 3,595,395 (MODE1/2048)
I 09:29:10 Source File Size: 7,363,368,960 bytes
I 09:29:10 Source File Volume Identifier: NAME_OF_MYDVD3_D3
I 09:29:10 Source File Implementation Identifier: Daikin U.S. Comtec Lab
I 09:29:10 Source File File System(s): ISO9660, UDF (1.02)
I 09:29:10 Destination Device: [1:1:0] PBDS DVD+-RW DH-16W1S 2D14 (F:) (ATA)
I 09:29:10 Destination Media Type: DVD-R DL (Disc ID: RITEKP01) (Speeds: 2x, 4x)
I 09:29:10 Destination Media Sectors: 4,172,816
I 09:29:10 Write Mode: DVD
I 09:29:10 Write Type: DAO
I 09:29:10 Write Speed: 1x
I 09:29:10 Link Size: Auto
I 09:29:10 Test Mode: No
I 09:29:10 BURN-Proof: Enabled
I 09:29:10 Optimal L0 Data Zone Capacity: 1,804,112
I 09:29:10 Optimal L0 Data Zone Method: Copied From Original Disc
W 09:29:15 Cannot set the layer break position when burning DVD-R DL media in DAO mode.
I 09:29:15 Filling Buffer... (40 MB)
I 09:29:16 Writing LeadIn...
I 09:31:15 Writing Image... (LBA: 0 - 3595394)
I 09:31:15 Writing Layer 0... (LBA: 0 - 2092895)
I 09:57:53 Writing Layer 1... (LBA: 2092896 - 3595394)
I 10:17:00 Synchronising Cache...
I 10:26:04 Image MD5: 2c2006ee9e303888a2afc6d5a7ee1df8
I 10:26:04 Operation Successfully Completed! - Duration: 00:56:53
I 10:26:04 Average Write Rate: 2,619 KB/s (1.9x) - Maximum Write Rate: 2,723 KB/s (2.0x)

However, the verify failed:
I 10:26:04 Cycling Tray before Verify...
W 10:26:11 Waiting for device to become ready...
I 10:26:28 Device Ready!
I 10:26:28 Operation Started!
I 10:26:28 Source Device: [1:1:0] PBDS DVD+-RW DH-16W1S 2D14 (F:) (ATA)
I 10:26:28 Source Media Type: DVD-R DL (Book Type: DVD-R) (Disc ID: RITEKP01) (Speeds: 2x, 4x)
I 10:26:28 Image File: C:\NAME_OF_MYDVD3_D3.MDS
I 10:26:28 Image File Sectors: 3,595,395 (MODE1/2048)
I 10:26:28 Image File Size: 7,363,368,960 bytes
I 10:26:28 Image File Volume Identifier: NAME_OF_MYDVD3_D3
I 10:26:28 Image File Implementation Identifier: Daikin U.S. Comtec Lab
I 10:26:28 Image File File System(s): ISO9660, UDF (1.02)
I 10:26:28 Verifying Sectors... (LBA: 0 - 3595394)
I 10:26:28 Verifying Layer 0... (LBA: 0 - 2092895)
I 10:36:27 Verifying Layer 1... (LBA: 2092896 - 3595394)
E 10:55:35 Failed to Read Sector 2092896 - L-EC Uncorrectable Error
E 10:55:35 Sector 2092896 maps to File: VIDEO_TS\VTS_01_4.VOB
E 10:55:35 Failed to Verify Sectors!
E 10:55:36 Operation Failed! - Duration: 00:29:07
I 10:55:36 Average Verify Rate: 2,395 KB/s (1.7x) - Maximum Verify Rate: 11,127 KB/s (8.0x)

 

Any ideas?

 

Thanks in advance.

Edited January 27, 2008 by ibu

[cornholio7]

two things, you shouldn't be burning video to -R dual layer discs.

only use +R and make sure they are Verbatim MKM-001 made in singapore

all other D/L discs are a waste of time

[ibu]

two things, you shouldn't be burning video to -R dual layer discs.

only use +R and make sure they are Verbatim MKM-001 made in singapore

all other D/L discs are a waste of time

Thanks a lot for the quick response. I have to say that that was really not what I wanted to hear. I have a spindle of about 20 RiDATA -R DL disks, and I'd hate to have to essentially throw them away (are they good for anything?). The disk ID is RITEKP01.

 

Sorry if I'm getting hung up on noobish stuff, but I'm just starting out.

 

Does it seem strange to you that the problem occured right after the layer switch?

I 10:26:28 Verifying Layer 0... (LBA: 0 - 2092895)

I 10:36:27 Verifying Layer 1... (LBA: 2092896 - 3595394)

E 10:55:35 Failed to Read Sector 2092896 - L-EC Uncorrectable Error

E 10:55:35 Sector 2092896 maps to File: VIDEO_TS\VTS_01_4.VOB

E 10:55:35 Failed to Verify Sectors!

Or is that typical.

 

Also, I don't know if it is helpful, but I have some Pioneer +R disks, so I decided to try those. (ID: CMC MAG-D01-00) I got the following error:

I 13:35:12 Verifying Layer 0... (LBA: 0 - 1804111)

I 13:43:08 Verifying Layer 1... (LBA: 1804112 - 3595394)

E 13:44:49 Failed to Read Sector 1836384 - L-EC Uncorrectable Error

E 13:44:49 Sector 1836384 maps to File: VIDEO_TS\VTS_01_4.VOB

E 13:44:50 Failed to Verify Sectors!

E 13:44:50 Operation Failed! - Duration: 00:09:37

(I burned at x1 again)

Again, it happened right after the layer switch, though not RIGHT after like with the previous time.

 

So how can I find Verbatim disks from the Singapore plant? I looked on Amazon and found the following review:

Verbatim DL used to be by far the best DL media available. Reliable, stable in storage, and consistent high quality made by Mitsubishi in their Singapore plant, one of the highest quality DVD production plants in the world.

Not any more. Verbatim has outsourced a large part of their DL production to a plant in India, and now when you buy this media you have a high chance of getting made in India - this product is poor, often with obvious physical defects in the media like bubbles, holes and foil delaminates.

It is possible to still find made in Singapore cakeboxes on store shelves, but if you can't actually read the disk label before buying you are rolling the dice when you buy.

It is a real shame Verbatim does not offer the Singapore product as a diferent grade. It would be worth a few extra bucks to get a cakebox that had a 95% success rate vs. the 50% rate the made in India product gives.

Verbatim has really gotten a black eye in my book with this stunt. 

 

Is there a way to tell where a given spool was manufactured? Can you recommend any good online stores for DVD+Rs?

 

Thanks in advance.

[LIGHTNING UK!]

It all depends on where you live.

 

Here in the UK most of us probably use www.svp.co.uk

 

** OFF TOPIC **

 

Whilst you're here, could you please do me a favour and see if the 'Lite-On' booktype options work on that drive at all?

 

Just click Tools -> Drive -> Change Book Type.

 

Then switch to the liteon tab and see if they all come up 'failed' or if they work.

[ibu]

Whilst you're here, could you please do me a favour and see if the 'Lite-On' booktype options work on that drive at all?

They all come up failed.

 

By the way, since we are talking about the drive, I just got it on a new Dell XPS 420. Do you think that the drive might be the source of my woes?

 

Device: [1:1:0] PBDS DVD+-RW DH-16W1S 2D14 (F:) (ATA)

[LIGHTNING UK!]

Ok cool that saves me doing any work then

 

The drive is probably ok, I think they're liteon clones anyway and it appears to be a recent enough model.

 

To be honest I don't recall ever seeing DVD-R DL besides Verbatim ones!

 

I'd kinda hoped nobody else would bother making them (and that Verbatim would stop) but it seems RITEK felt they needed to.

 

Once you've tried the Verbatim 2.4x DVD+R DL's, you'll know if the drive is any good or not. If it can't burn those it probably can't burn any DL discs.

 

If the drive offers multiple 'supported write speeds', make sure you try them all in case of failure.

[blutach]

There's lots of technical reasons about -R DL not being good for DVD Video, which I won't mention in detail save to say that it's a bitch to set the layer break properly.

 

They will be fine for large data disks (of course, the quality of the Ritek disks still sucks) but not useful at all for DVD Video.

 

Regards

[bob465]

There's lots of technical reasons about -R DL not being good for DVD Video, which I won't mention in detail save to say that it's a bitch to set the layer break properly.

 

They will be fine for large data disks (of course, the quality of the Ritek disks still sucks) but not useful at all for DVD Video.

 

Regards

 

The EXACT same thing has been happening to me with +R DL media but only with "certain" DVD VIDEO_TS folders built into ISOs (with imgburn). Tried endlessly fiddlin' with the layer break etc. I finally tried the exact same troublesome ISOs with NERO and they all burned and verified flawlessly the FIRST time. Other DVD VIDEO_TS folders built into ISOs burned just fine with imgburn ... The truth is there is something more specific going on with imgburn!

[bob465]

There's lots of technical reasons about -R DL not being good for DVD Video, which I won't mention in detail save to say that it's a bitch to set the layer break properly.

 

They will be fine for large data disks (of course, the quality of the Ritek disks still sucks) but not useful at all for DVD Video.

 

Regards

 

The EXACT same thing has been happening to me with +R DL media but only with "certain" DVD VIDEO_TS folders built into ISOs (with imgburn). Tried endlessly fiddlin' with the layer break etc. I finally tried the exact same troublesome ISOs with NERO and they all burned and verified flawlessly the FIRST time. Other DVD VIDEO_TS folders built into ISOs burned just fine with imgburn ... The truth is there is something more specific going on with imgburn!

 

Forgot to clearly state that NERO burned the same troublesome ISOs with the SAME media ...

 

Bob

[LIGHTNING UK!]

The read errors have nothing to do with the layer break or which option you select. Nor are they anything to do with specific image. The drive doesn't give a monkey's uncle what you're burning.

 

There are other things you could try (like using Incremental instead of SAO/DAO) but you have to want to get it working first. If people just whinge about stuff then I can't be bothered to help them.

[dontasciime]

The EXACT same thing has been happening to me with +R DL media but only with "certain" DVD VIDEO_TS folders built into ISOs (with imgburn). Tried endlessly fiddlin' with the layer break etc. I finally tried the exact same troublesome ISOs with NERO and they all burned and verified flawlessly the FIRST time. Other DVD VIDEO_TS folders built into ISOs burned just fine with imgburn ... The truth is there is something more specific going on with imgburn!

 

 

[Q] How is it I have built/burnt hundreds of DL media on 11+ computers using over 30 dvd writers and never come across this scenario. Whereby someone says ImgBurn fails and Nero works.

 

[A] It's your hardware, lack of knowledge, ability to maintain and install a functional operating system and therefore you have a shitty, unclean corrupted operating system.

[bob465]

The EXACT same thing has been happening to me with +R DL media but only with "certain" DVD VIDEO_TS folders built into ISOs (with imgburn). Tried endlessly fiddlin' with the layer break etc. I finally tried the exact same troublesome ISOs with NERO and they all burned and verified flawlessly the FIRST time. Other DVD VIDEO_TS folders built into ISOs burned just fine with imgburn ... The truth is there is something more specific going on with imgburn!

 

 

[Q] How is it I have built/burnt hundreds of DL media on 11+ computers using over 30 dvd writers and never come across this scenario. Whereby someone says ImgBurn fails and Nero works.

 

[A] It's your hardware, lack of knowledge, ability to maintain and install a functional operating system and therefore you have a shitty, unclean corrupted operating system.

 

Typical Jerk.

I'm an Electrical Engineer who is rather adept at anything PC related describing the EXACT scenario with a cleanXP pro build using a brand new Samsung SH-S203N DVD Burner. The exact same behavior was exhibited with the EXACT same ISOs on a different system with a Sony DRU-830A (Samsung OEM I believe) burner, both burners with the latest firmware. Now, granted I'm NOT an imgburn expert in particular nor an optical media expert in general HOWEVER you cannot legitimately dismiss the EXACT same ISOs burning flawlessly using NERO that didn't burn using imgburn regardless of your abysmal and disrespectful attitude. I am NO fan or NERO's and actually would MUCH RATHER support imgburn and all that the author as contributed the the world of optical media!

 

With all due respect,

Bob

[bob465]

The read errors have nothing to do with the layer break or which option you select. Nor are they anything to do with specific image. The drive doesn't give a monkey's uncle what you're burning.

 

There are other things you could try (like using Incremental instead of SAO/DAO) but you have to want to get it working first. If people just whinge about stuff then I can't be bothered to help them.

 

Thanks Lightning UK. I haven't spent the time learning the ins and outs of imgburn and perhaps should do so. I'm certainly not here to complain but to get information + I didn't actually study the logs that were presented in a careful manner and can't with any certaintly say that I got the exact same errors however and once again, my scenario cannot be dismissed given my clean XPpro builds ...

[dontasciime]

you ain't got a time machine so how do you know the disc that burnt in Nero would equally not have burnt in ImgBurn and vice versa with the failed ones.

 

Can you post a log file from failed ImgBurn writes

 

Also post the Filter driver load order captured from clipboard from ImgBurn's tools/menu

[bob465]

-

Edited January 30, 2008 by bob465

[bob465]

you ain't got a time machine so how do you know the disc that burnt in Nero would equally not have burnt in ImgBurn and vice versa with the failed ones.

 

Can you post a log file from failed ImgBurn writes

 

Also post the Filter driver load order captured from clipboard from ImgBurn's tools/menu

 

I'll try and gather the information you request. This problem has been going on for quite some time now. I suppose any given spindle can have good and bad discs but I doubt it simply because non of my DL media has given me problems with simple data archiving at any time. It's only burning ISOs (that i've created from VIDEO_TS folders using imgburn), I'm not saying that this is directly relavent nor am I saying that there is a determininistic distinction between how imgburn and NERO get the image burned on the disc because I've not taken the time to develop an expertise in that arena however I can say that I'm an expert at gathering empirical data in a controlled environment given my professional training and the scenario I outline, while not controlled, is repeatable over time.

 

Once again, i'm not here to complain or get in a peeing contest with over-inflated egos ,,, rather i'm here to gather information ...

 

Thanks for your time,

[dontasciime]

There is only 1 (99.999%) consistent DVD+R DL media

 

Verbatim [singapore] MKM-001-00

 

Anything else is hit and miss in any given combination and those samsung drives are a bit picky with even the best Verbatims wrote @ normal write speed.

[LIGHTNING UK!]

Bob, (if that's your real name?!)

 

There's really nothing between Nero and ImgBurn. If one fails, so should the other one.

 

I couldn't make your burner fail to burn if I tried - that's something it has to do all by itself. The drive has complete control over burn quality etc, all the software does is provide it with the data to burn.

 

Lots of the errors we see on DL media are during the Verify stage... does Nero even verify anything by default? (ImgBurn does).

 

Does it retry when it hits a sector that the drive says it can't read? (ImgBurn doesn't - that would defeat the purpose of verification)

 

The only real difference there could be is in the 'Write Type' used by the software. ImgBurn defaults to SAO/DAO but 'Incremental' is an option. Nero may default to 'Incremental'.

 

So all you have to do is change that option in the settings (on the Write tab) and then try again.

 

Don't get me wrong, both these 'Write Types' should perform exactly the same. I've no idea why sometimes one works better than the other on a specific drive (and I don't mean a certain model of drive, I mean the individual drive having the problems).

 

There are just a handful of people that run into these issues out of the hundreds of thousands of actual users. Nothing is perfect for everyone, I read stories all over the place where Nero and other tools have failed where ImgBurn succeeds. Lets face it, nobody takes the times to go on a support forum and post about a successful burn!

[bob465]

Bob, (if that's your real name?!)

 

There's really nothing between Nero and ImgBurn. If one fails, so should the other one.

 

I couldn't make your burner fail to burn if I tried - that's something it has to do all by itself. The drive has complete control over burn quality etc, all the software does is provide it with the data to burn.

 

Lots of the errors we see on DL media are during the Verify stage... does Nero even verify anything by default? (ImgBurn does).

 

Does it retry when it hits a sector that the drive says it can't read? (ImgBurn doesn't - that would defeat the purpose of verification)

 

The only real difference there could be is in the 'Write Type' used by the software. ImgBurn defaults to SAO/DAO but 'Incremental' is an option. Nero may default to 'Incremental'.

 

So all you have to do is change that option in the settings (on the Write tab) and then try again.

 

Don't get me wrong, both these 'Write Types' should perform exactly the same. I've no idea why sometimes one works better than the other on a specific drive (and I don't mean a certain model of drive, I mean the individual drive having the problems).

 

There are just a handful of people that run into these issues out of the hundreds of thousands of actual users. Nothing is perfect for everyone, I read stories all over the place where Nero and other tools have failed where ImgBurn succeeds. Lets face it, nobody takes the times to go on a support forum and post about a successful burn!

 

Got it.

I'm not at home and will have to get to the logs later.

 

Ok so I assumed that at a low level, the software would have access to the specifics of how the data is burned : i.e. access to different efficiencies/efficacies at the burning level but what I hear you say is that that is not the case, rather the drive's HW/firmware makes that determination. If that's the case then I see nothing beyond happenstance and astrology being at the root of my observations. ----quite surprising given the longevity of my issue but what do they say about truth being stranger than fiction. Perhaps I've taken enough of your time and we can forget about the logs ...

 

and yes, my name is Bob

[blutach]

Bob,

 

Until we know the exact media you are using, it's all a bit academic. The fact is anything other than the Verbs 2.4x +R MIS are, as donta (who is not a jerk) says, hit and miss. You may have missed with ImgBurn and hit with Ner0. Just the luck of the draw.

 

We'll know more when you post your logs.

 

Regards

[The Last to Know]

May I ask a question regarding burning using Imgburn on Verbatim 2.4x DL disks made in Singapore that I just did today?

 

The whole disc plays fine except for the first chapter ONLY. My DVD player has played all other burnt Verbatim disks fine (that I have noticed so far). If I fast forward or skip in the first chapter it freezes and I can only turn off the DVD player to get it going again (even my computer froze while fast forwarding that section).

 

Also when the play mode reached a certain point it then skipped to chapter 2. But when I fast rewound it back to the point of the skip area (and before) it PLAYED fine and forward fine.

 

Herewith attached is the log. Did I make an error, is the disc that .0001% messup or is my less than 1 yr old burner a problem (if anyone can tell?) Thanks for the assist.

 

; //****************************************\\

; ImgBurn Version 2.3.2.0 - Log

; Friday, 01 February 2008, 11:56:16

; \\****************************************//

;

;

I 10:38:53 ImgBurn Version 2.3.2.0 started!

I 10:38:53 Microsoft Windows Vista Ultimate Edition (6.0, Build 6000)

I 10:38:53 Total Physical Memory: 2,881,408 KB - Available: 2,089,504 KB

I 10:38:53 Initialising SPTI...

I 10:38:53 Searching for SCSI / ATAPI devices...

I 10:38:53 Found 1 DVD±RW/RAM!

I 10:41:06 Operation Started!

I 10:41:06 Building Image Tree...

I 10:41:06 Checking Directory Depth...

I 10:41:06 Calculating Totals...

I 10:41:06 Preparing Image...

I 10:44:41 Using Layer Break LBA: 1223137 -> 1749296 (VTS_04, PGC: 1, Chapter: 7, Cell: 19, Vob/Cell ID: 1/10, Time: 00:51:25, SPLIP: No)

I 10:44:41 Checking Path Length...

I 10:44:41 Image Size: 7,165,116,416 bytes

I 10:44:41 Image Sectors: 3,498,592

I 10:44:41 Operation Successfully Completed! - Duration: 00:03:35

I 10:45:18 Operation Started!

I 10:45:18 Building Image Tree...

I 10:46:24 Checking Directory Depth...

I 10:46:24 Calculating Totals...

I 10:46:24 Preparing Image...

I 10:49:23 Using Layer Break LBA: 1223137 -> 1749296 (VTS_04, PGC: 1, Chapter: 7, Cell: 19, Vob/Cell ID: 1/10, Time: 00:51:25, SPLIP: No)

I 10:49:23 Checking Path Length...

I 10:49:23 Image Size: 7,165,116,416 bytes

I 10:49:23 Image Sectors: 3,498,592

I 10:49:31 Operation Successfully Completed! - Duration: 00:04:13

I 10:49:31 Operation Started!

I 10:49:31 Source File: -==/\/[bUILD IMAGE]\/\==-

I 10:49:31 Source File Sectors: 3,498,592 (MODE1/2048)

I 10:49:31 Source File Size: 7,165,116,416 bytes

I 10:49:31 Source File Volume Identifier: LAPUTA Castle in the Sky

I 10:49:31 Source File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER!

I 10:49:31 Source File Implementation Identifier: ImgBurn

I 10:49:31 Source File File System(s): ISO9660, UDF (1.02)

I 10:49:31 Destination Device: [1:0:0] PIONEER DVD-RW DVR-K16RS 1.35 (D:) (ATA)

I 10:49:31 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x)

I 10:49:31 Destination Media Sectors: 4,173,824

I 10:49:31 Write Mode: DVD

I 10:49:31 Write Type: DAO

I 10:49:31 Write Speed: 2.4x

I 10:49:31 Link Size: Auto

I 10:49:31 Test Mode: No

I 10:49:31 BURN-Proof: Enabled

I 10:49:31 Optimal L0 Data Zone Capacity: 1,749,296

I 10:49:31 Optimal L0 Data Zone Method: IFO Cell Boundary, 'SPLIP' Flag Not Set

I 10:50:00 Filling Buffer... (40 MB)

I 10:50:00 Writing LeadIn...

I 10:50:02 Writing Image... (LBA: 0 - 3498591)

I 10:50:02 Writing Layer 0... (LBA: 0 - 1749295)

I 11:09:15 Writing Layer 1... (LBA: 1749296 - 3498591)

I 11:28:02 Synchronising Cache...

I 11:28:03 Closing Track...

I 11:28:10 Finalising Disc...

I 11:29:10 Image MD5: e969a812c96d9c6d367806762170d739

I 11:29:10 Operation Successfully Completed! - Duration: 00:39:38

I 11:29:10 Average Write Rate: 3,070 KB/s (2.2x) - Maximum Write Rate: 3,471 KB/s (2.5x)

I 11:29:10 Cycling Tray before Verify...

W 11:29:14 Waiting for device to become ready...

I 11:32:34 Device Ready!

I 11:32:34 Operation Started!

I 11:32:34 Source Device: [1:0:0] PIONEER DVD-RW DVR-K16RS 1.35 (D:) (ATA)

I 11:32:34 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x)

I 11:32:34 Image File: -==/\/[bUILD IMAGE]\/\==-

I 11:32:34 Image File Sectors: 3,498,592 (MODE1/2048)

I 11:32:34 Image File Size: 7,165,116,416 bytes

I 11:32:34 Image File Volume Identifier: LAPUTA Castle in the Sky

I 11:32:34 Image File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER!

I 11:32:34 Image File Implementation Identifier: ImgBurn

I 11:32:34 Image File File System(s): ISO9660, UDF (1.02)

I 11:32:34 Verifying Sectors... (LBA: 0 - 3498591)

I 11:32:34 Verifying Layer 0... (LBA: 0 - 1749295)

I 11:43:09 Verifying Layer 1... (LBA: 1749296 - 3498591)

I 11:53:41 Device MD5: e969a812c96d9c6d367806762170d739

I 11:53:41 Image MD5: e969a812c96d9c6d367806762170d739

I 11:53:41 Operation Successfully Completed! - Duration: 00:21:07

I 11:53:41 Average Verify Rate: 5,522 KB/s (4.0x) - Maximum Verify Rate: 7,897 KB/s (5.7x)

I 11:56:16 Close Request Acknowledged

I 11:56:16 Closing Down...

I 11:56:16 Shutting down SPTI...

I 11:56:16 ImgBurn closed!

[spinningwheel]

Your media and drive appear to be fine. I would venture to say that whatever means you used to get the Anime to your HDD is the culprit...and remember...we DO NOT discuss ripping programs or methods here...your answer is on Google.

[The Last to Know]

Your media and drive appear to be fine. I would venture to say that whatever means you used to get the Anime to your HDD is the culprit...and remember...we DO NOT discuss ripping programs or methods here...your answer is on Google.

 

Thanks for your help spinningwheel.