yikes

thanks for the reply

are you referring to this : I 17:01:11 Source File File System(s): Special I 17:01:11 Destination Device: [2:0:0] PLEXTOR DVDR PX-870A 1.05 (Y:) (ATA) I 17:01:11 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3) (Speeds: 6x, 8x, 12x, 16x) I 17:01:11 Destination Media Sectors: 2,298,496 I 17:01:11 Write Mode: DVD I 17:01:11 Write Type: DAO I 17:01:11 Write Speed: 4x I 17:01:11 Link Size: Auto I 17:01:11 Lock Volume: Yes I 17:01:11 Test Mode: No I 17:01:11 OPC: No I 17:01:11 BURN-Proof: Enabled W 17:01:12 Write Speed Miscompare! - Wanted: 5,540 KB/s (4x), Got: 8,310 KB/s (6x) I 17:01:12 Filling Buffer... (40 MB) I 17:01:13 Writing LeadIn... I 17:01:49 Writing Session 1 of 1... (1 Track, LBA: 0 - 2294911) I 17:01:49 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2294911) I 17:11:07 Synchronising Cache... I 17:11:29 Exporting Graph Data... are burning speeds hard coded in the firmware? this same disk i was able to burn at 4x on the pio 116D thanks

hello i just replaced my failing pio 116D with a plex px-870A. these are both IDE drives. out of habbit ive alway burned certain things @ 4x. since changing over to the plex ive noticed it does not burn anything slower than 6x no matter if its +R or -R ( at least with imageburn...have not check other burn sw). although i dont think burning things @6x as opposed to 4x would make much of a differnce....is there a way to force it to burn @4x or is this hard coded into the plex firmware and nothing can be done about it? thanks

since both of my burners are pioneer ( 116D and 203bdk )is it safe to say thats is the reason why it failed...its firmware?? will changing the settings to incremental fix this issue? thanks

is this the burn log that you needed to see?

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)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (3 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (4 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (5 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (6 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (7 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (8 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (9 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (10 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (11 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (12 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (13 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (14 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (15 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (16 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (17 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (18 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (19 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:21:19 Retrying (20 of 20)... W 23:21:19 Retry Failed - Reason: Invalid Address For Write W 23:22:36 Retrying (21)... W 23:22:36 Retry Failed - Reason: Invalid Address For Write W 23:22:37 Retrying (22)... W 23:22:37 Retry Failed - Reason: Invalid Address For Write W 23:22:38 Retrying (23)... W 23:22:38 Retry Failed - Reason: Invalid Address For Write W 23:22:38 Retrying (24)... W 23:22:38 Retry Failed - Reason: Invalid Address For Write W 23:22:39 Retrying (25)... W 23:22:39 Retry Failed - Reason: Invalid Address For Write W 23:22:39 Retrying (26)... W 23:22:39 Retry Failed - Reason: Invalid Address For Write W 23:22:40 Retrying (27)... W 23:22:40 Retry Failed - Reason: Invalid Address For Write W 23:22:40 Retrying (28)... W 23:22:40 Retry Failed - Reason: Invalid Address For Write W 23:22:41 Retrying (29)... W 23:22:41 Retry Failed - Reason: Invalid Address For Write E 23:22:42 Failed to Write Sectors 3710048 - 3710079 - Reason: Write Error E 23:22:42 Next Writable Address: 3709328 I 23:22:43 Synchronising Cache... W 23:22:48 User opted to skip the 'Close Track/Session/Disc' functions. E 23:22:48 Failed to Write Image! I 23:22:50 Exporting Graph Data... just a recap of the events.... trilogy set all ripped with anydvd hd disk 1 burned fine disk 2 and disk 3 failed in various places with the above type of error tried 4-5 times before i gave up and decided "what the heck" lets tried clone and it worked. the same thing happened to another disk i did for a friend at first i thought the burner was dying until i tried it on my other burner and it did the exact same thing thanks

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

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.

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.

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

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

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?

i thank you for your reply but this is not self explanatory to me. this is the first time for me with bluray and ive never encounter these problems before. i just want to make sure this is an issue with the media and not with the burner. id hate to send it back and have it happen with the new one. the funny thing is that i did manage to get 2/3 to format with repeated tries. the 3rd one will not format at all. i also did try looking for a new firmware but this pio bdr203 is so new there isnt one. least none that i couldnt fine. also i havent seen anywhere that sells verbatim bd-re DL..please direct me please if you know where my apologies but i also forgot to mention i have no problems formatting ridata bd-re sl disks

can anyone tell me what positioning error is?

hello i tried doing a search on this but didnt not find anything on it. i just bought a pio bdr-203. im using windows xp with latest updates. i bought a 3 pack of tdk dl bd-re and a 5 pack of ridata sl bd-re disk. using the latest version of imageburn.... all the sl disk formatted without incident. the dl tdk however, been given me a bit of trouble. during initial scan before format i get this error : W 21:04:18 Potential 'WaitImmediateIO' Deferred Error - (97%, 0/4) - Positioning Error Detected by Read of Medium. this happens several times and once error is listed the scan restarts back to 0. it seems to happen at any random point in the scan. this happened like 15 times when image burn ejected the disk. i tried it agiain and after like 5-6 more failure i got lucky and it completed and formating began. it did complete its format but i have yet to try an actual burn on the disk. i decided to try a second bd-re dl hoping that maybe i got a bad first disk. this error happen once again but only once and the disk proceded to format. so far i have mad 1 burn on a bd-re sl disk and was suceessful. my question is...what does this error mean? do i have bad disks or a bad burner or both? thanks i just tried the 3rd disk and got the following after 6 tries: E 22:48:00 Failed to Erase Disc! - Reason: Positioning Error Detected by Read of Medium E 22:48:02 Operation Failed! - Duration: 00:05:08