failed burn on dl dvd

yikes · September 18, 2010

i just bought the star wars trilogy and wanted to make copies of it so my daughter can use them. i almost always use image burn to burn. the first disk burned well but the other 2 failed in various places. many disks later and i had to try something else. these other 2 disk burned successfully using cloneCD. unfortunately i didnt save the exact error msg but it was something like failed to burn blah blah and it just times out. its also unfortunate to get the exact error msgs i will have to sacrifice another disk for it. i thought this was an anomoly so i didnt think anything of it until today when a friend ask me to copy a disk he bought so his kids can have their own. same deal...imageburn failed to burn the dl disk and cloneCD was able to complete the burn. oh btw..i have 2 burners a pio 116 and a pio 203 and they both fail to complete it using imageburn.

am i doing something wrong in the setup somewhere?

yikes · September 19, 2010

btw i did read the the sticky on bad dl disk and i felt this isnt the case here since clonecd burns it fine

**ianymaty** · September 19, 2010

They are copyprotected discs and ImgBurn can't and won't do anything to get arround that copyprotection.

**LIGHTNING UK!** · September 19, 2010

This is a drive issue.

CloneCD uses the 'Incremental' write type.

Sometimes, dodgy drive/firmware/media combos work better with one write type over the other write type. (SAO/DAO Vs Incremental)

You should have posted a burn log so we could see exactly what you were talking about.

yikes · September 20, 2010

They are copyprotected discs and ImgBurn can't and won't do anything to get arround that copyprotection.

i am fully aware that they are copy protected...as the owner of those disks i am

allowed to have a copy of them.

also note that i said burn and not rip....

thanks for the reply though

Edited September 20, 2010 by yikes

yikes · September 20, 2010

This is a drive issue.

CloneCD uses the 'Incremental' write type.

Sometimes, dodgy drive/firmware/media combos work better with one write type over the other write type. (SAO/DAO Vs Incremental)

You should have posted a burn log so we could see exactly what you were talking about.

yes i wish i had a burn log to post here but at the time i was just trying to find a way to complete the burn and closed the program. perhaps its would be a better idea to not have 2 burners that are both pioneers. thank you for your explanation cause it was baffling as to why one sw can burn it and another couldnt.

Edited September 20, 2010 by yikes

**ianymaty** · September 21, 2010

note that i said burn and not rip....

You said burn but not mention about what program used to make the image so I presumed you used the same program in both cases to make the image and then burn it back with it.

CloneCD uses RAW-Mode to copy to image so it could make a good image, instead with ImgBurn it could render in a defective image due to copyprotection and I think it worned you about that and you accepted.

**LIGHTNING UK!** · September 21, 2010

There's no 'RAW-Mode' for DVD, all apps are created equal

For the burning stage it'll just be the difference between SAO/DAO and Incremental write types.

ImgBurn can be told to use either.

yikes · September 21, 2010

note that i said burn and not rip....

You said burn but not mention about what program used to make the image so I presumed you used the same program in both cases to make the image and then burn it back with it.

CloneCD uses RAW-Mode to copy to image so it could make a good image, instead with ImgBurn it could render in a defective image due to copyprotection and I think it worned you about that and you accepted.

sorry there you lost me with that last sentence? warned me about what? i didnt use clonecd either...i used the latest version of anydvd hd to rip it. ( which i bought )

its used mostly to backup my blurays so that my 7 yr old daughter can have her own copies to do as she pleases. so i rarely do dvds but i was able to buy the star wars trilogy for dirt cheap so i grabbed it.

Edited September 21, 2010 by yikes

yikes · September 21, 2010

There's no 'RAW-Mode' for DVD, all apps are created equal

For the burning stage it'll just be the difference between SAO/DAO and Incremental write types.

ImgBurn can be told to use either.

i havent looked into the options since i set it when i first got imageburn. your saying if i can set it to incremental write i shouldnt have a problem burning the iso then?

thanks

**LIGHTNING UK!** · September 21, 2010

You shouldn't have a problem anyway, but seeing as you say you do, setting the 'Write Type' to 'Incremental' may fix it for you.

If it doesn't, at least you'll have a log you can show me.

(Logs are saved automatically btw, get at them via the 'Help' menu)

yikes · September 21, 2010

hi thanks for your help...i guess i do have the burn log after all...i will paste this here ( i hope this is what is needed )

I 22:41:13 Source File Sectors: 3,991,363 (MODE1/2048)

I 22:41:13 Source File Size: 8,174,311,424 bytes

I 22:41:13 Source File Volume Identifier: EMPIRE_STRIKES_BACK

I 22:41:13 Source File Volume Set Identifier: 30AD7E86

I 22:41:13 Source File Implementation Identifier: MEI

I 22:41:13 Source File File System(s): ISO9660, UDF (1.02)

I 22:41:13 Destination Device: [2:0:0] PIONEER DVD-RW DVR-116D 1.09 (Y:) (ATA)

I 22:41:13 Destination Media Type: DVD+R DL (Disc ID: RITEK-D01-01) (Speeds: 2.4x)

I 22:41:13 Destination Media Sectors: 4,173,824

I 22:41:13 Write Mode: DVD

I 22:41:13 Write Type: DAO

I 22:41:13 Write Speed: 4x

I 22:41:13 Link Size: Auto

I 22:41:13 Lock Volume: Yes

I 22:41:13 Test Mode: No

I 22:41:13 OPC: No

I 22:41:13 BURN-Proof: Enabled

W 22:41:14 Write Speed Miscompare! - Wanted: 5,540 KB/s (4x), Got: 3,324 KB/s (2.4x)

I 22:41:14 Advanced Settings - Optimal Writing Speed: No

I 22:41:14 Optimal L0 Data Zone Capacity: 2,030,752

I 22:41:14 Optimal L0 Data Zone Method: Copied From Original Disc

I 22:41:36 Set L0 Data Zone Capacity Succeeded!

I 22:41:36 Filling Buffer... (40 MB)

I 22:41:36 Writing LeadIn...

I 22:41:38 Writing Session 1 of 1... (1 Track, LBA: 0 - 3991362)

I 22:41:38 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3991362)

I 22:41:38 Writing Layer 0... (LBA: 0 - 2030751)

I 23:03:11 Writing Layer 1... (LBA: 2030752 - 3991362)

W 23:21:14 Failed to Write Sectors 3710048 - 3710079 - Reason: Write Error

W 23:21:14 Retrying (1 of 20)...

W 23:21:18 Retry Failed - Reason: Invalid Address For Write

W 23:21:18 Retrying (2 of 20)...