shadowcaster

Follw up : My next burn was from an ISO and it completed with no problems.

This isn't an imgburn question directly. When I burn a dl disc and then use Plextools to check for pi/po errors, the error rate is always greater from 0 to ~4gb then it is from ~4gb to the end. So, my question is, which layer is actually burned first, the top or bottom ? Logic would tell me that the second layer is burned first but I don't know. Edit: Ok, found the answer to the second part. The top layer (closet to the disc surface) is burned first. So, why does this layer always have more pi errors than the 2nd layer ? (Plextor 760a, VB DL/Singapore @ 2.4x)

Thanks Blutach. I'll do that. Here's a scan of a disc I burned from an image file , just prior to the above bad one. All things were equal EXCEPT the OTF burn of the bad disc. Also, interesting on this scan how much lower the error level is on the 2nd layer (and, of course, no pof's)

Lightning...I stand correccetd ! The scale was too low. I reset it to 500 and what a difference. Plus, now it shows 20 pof errors and the pi jumped from 362k to over 1.4 million ! Comments please.

I've burned other discs in the spindle before that bad one and they're fine. Now....I'll continue and burn more and see what happens from that one on down. [fingers crossed] I'll update what happens.[/fingers crossed]

Thanks for the reponses Lighting ! I guess it's a mystery why that burn went bad. Guess it was just a coincidence that it was the first time I burned files "on the fly". BTW I still use your "other" program all the time. The pi/po scale adjusts automatically to the highest level so no adjustment is necessary. I've had some discs on my old 716sl go through the roof, at the start of a disc. BTW, here's what DVDINFO Pro shows for that disc , with the media as DL. So, current profile under imgburn is wrong for some reason. Could that have been the cause of the bad burn ? Edit: I just checked a previously burned disc and it shows profile as dvd-rom as well, under both imgburn and plextools, just like the bad disc. However, it too, shows media as DL under DVDINFO Pro. Go figure. Media Information Disc Regions are 1,2,3,4,5,6,7,8 Media code/Manufacturer ID MKM 001 Media Product Revision Number 00h UDF Format Type V1.02 UDF Volume Name PLANET_EARTH_D1 UDF Application id ImgBurnv2.4.2.0 UDF Implementation id ImgBurn UDF Recording Date/Time (mm/dd/yyyy) 9/24/2008 17:04:36 Format Capacity 7.69GB(8.25GB) Book Type DVD-ROM Media Type DVD+R DL Data area starting sector 30000h Data area end sector 3D7E9Fh Layer 0 end sector 21BF4Fh Linear Density 0.293um/bit Track Density 0.74um/track Number of Layers 2 Layer Track Path direction (OTP) Opposite track path

Nice catch, I missed that . However the disc had already been burned , ejected and reinserted to run the "verify". So, a new log was created on a new read, so the DVD-ROM is probably correct because the book type was set, no ? If I put a blank dl disc in the drive it's recognized as "current profile DVD+R DL" and "media type DVD+R DL", under the device tab . Yes, I have Plextools and ran the PI/PO test before I posted here . There was an error when it ceased reading the disc at ~40% point. I'm running it again now and will post the graph when completed. BTW, I'm still curious if burns made on the fly, from files to disc, are as reliable as ones made from creating an image file on the HD first, and then burning ?. Edit : Here's the graph

Again , using Verbatim dl/singapore @ 2.4X Ok, re my post above #13, here is the log file : I 12:42:07 ImgBurn Version 2.4.2.0 started! I 12:42:07 Microsoft Windows 2000 Professional (5.0, Build 2195 : Service Pack 4) I 12:42:07 Total Physical Memory: 1,048,000 KB - Available: 298,904 KB I 12:42:07 Initialising SPTI... I 12:42:07 Searching for SCSI / ATAPI devices... I 12:42:07 Found 2 DVD-ROMs, 1 DVD-ROM/CD-RW and 1 DVD

@Lightning UK I have a similiar I/O to the OP. Don't remember the error code but the interpretation was the same-check condition. Verbatim DL discs-made in Singapore, Plextor 760a, P4 3.4ghz, 1 gb ram. Recording at 2.4X However, I only get that error when trying to burn the video files to a DL disc. If I create an image first and then burn the image to disc, it works fine. Is there something in the all in one process that makes it more susceprible to I/O errors? BTW, I never get this error in SL discs.