LIGHTNING UK!

These are general cd/dvd terms. I'm sure Googling would return some results.

Right click the drive selection drop down box and select 'Family Tree'. Close the prompt that comes up and then copy + paste the family tree info from the log window.

Mount them in DAEMON Tools and read to a new image?

What I'm saying is that the error might not actually exist at all. Had you not have built+burn on the fly, I'd have told you to verify the disc against the same image again. Now you'll have to use something like Beyond Compare to re-check the file on the disc against the file on your hdd. Don't forget about memtest.

2.5.6.1 shouldn't be doing it. If it is, please go back in the beta forum and let's deal with it in there.

ImgBurn is written around the MMC specs and all drives (in the last X years anyway) comply with them. No, it's nothing to do with the layer break either. Your drive is reporting a 'Write Error' at the end of the burn as it tries to write what's in its cache to the disc. It looks like the retry was successful but you never really know with these things. Then of course the drive had a problem trying to finalise the disc. As you burnt that disc at max speed (6x), do one of the things recommended in that thread I linked you to and try the remaining supported write speeds - start with 4x.

Are you using the 2.5.6.1 beta?

It's 1 bit in a byte. I can't tell you what it'll do to the stream... at a guess though, nothing. Such errors are usually related to memory issues. Run memtest86+ for a few passes to test it. btw, you should be using ImgBurn v2.5.6.0 and your Pioneer drive could do with having its firmware updated - http://www.firmwarehq.com/Pioneer/DVR-108/files.html

The program version has no bearing on your drive's ability to burn a disc. http://forum.imgburn.com/index.php?showtopic=8000

It doesn't look like that disc is fully readable in your drive. That could be due to a fault / scratch / dirt, or it could be some sort of copy protection.

Your drive might burn those discs or it might not. Try it and see. The burn quality probably won't be up there with the likes of Verbatim discs but it might just be enough to pass the Verify phase. Mount the ISO in a virtual drive (or just extract it to a folder somewhere) and try building a new image from said virtual drive (or folder) with ImgBurn.

Yes, it works fine with whatever discs you throw at it... even the BDXL ones (which your drive doesn't support). Failure to format is down to your drive/firmware/media combo. The drive is doing the work, not the program.

There are some BD media scans in the 'Drives' section (only for Blu-ray drives obviously!). Have a look and see how various ones performed. I didn't test many DL discs... and certainly not any Taiyo Yuden ones. The cdfreaks/MyCE forums might have a few though.

That looks fine but you may find it gets worse again as you burn more discs (like mine did when I tested about 12 discs from a spindle). Keep an eye on it.

Can you scan the disc you got from your friend and post the screenshot of the results please. If it looks the same as the others you've posted, just say it's producing bad burns at the end of Verbatim MKM003 DL discs - and that you've tried 2 spindles. It might be worth you loading the latest official firmware and burning one more with that (still at 4x) just to double check it's bad (post the scan screenshot of that too).

Is your friend able to (over)burn their MKM003 without issues? Can they burn yours too? I guess you could have a faulty drive (or at least one that can't overburn very well), yeah.

You must have a bad spindle of discs. You aren't even just getting a spike at the overburnt layer break position (as is the norm for most 'bad' burns), you're getting high error levels before, in and after the overburnt area. When looking at my results (with the iHAS124 drive) you have to take into account that some of the tests may have been done without using anything beyond normal disc capacity (so no overburning as allowed by the 'max' firmware). My Aone discs wouldn't overburn without failing to verify.

If the OS doesn't see the disc, normally it's because you (or some other app) has killed (disabled) the autoinsert / media control notification stuff built into Windows. I have no problem with it here, Windows usually pops up the 'Autorun' box between a Write and Verify operation - exactly as it should do. Your drive totally vanishing from Explorer isn't a good sign! Look at post #6 here - http://forum.imgburn.com/index.php?showtopic=19159

Why can't you just ditch the Pioneer and put the Asus in its place? You don't need to 'save' your burner just for burning. Save electricity and remove the Plextor too. Personally I'd steer clear of slimline drives and USB drives in general. Slimline drives are rubbish burners and USB has its own issues (semaphore timeouts).

What controller have you attached the drive to? It looks like a general system/controller/driver issue - hence all the 'Potential Bogus Driver Error Detected!' messages.

Those settings worked fine for me in testing - you can check my results in the 'Drives' section (maybe you already did and that's where you got them from?) You don't need to clear OPC every time when using them. I only cleared it before using them for the first time. After that, I didn't touch it. Have you tried another spindle of discs?

You know 2.5.6.0 is the current release yeah? 2.5.3.0 started using the newer method of calling up Microsoft's open/save file boxes. That's probably where the way it worked changed. The correct way to edit the volume label of a currently selected image would be to right click the one that's currently displayed (having already selected a file in Write mode) and then clicking 'Change'. That makes the 'change volume label' dialog load the current image automatically. Basically, when you 'browse' on the 'change volume label' dialog, the way it works is this... 1. It'll check to see if the option to always use the configured 'Image File' folder is set - if it is, it'll use that folder. 2. After that it'll attempt to use the folder of the currently selected image file (i.e. the last file you changed the volume label of). If you close and reopen the window, this can't happen as it's not a persistent value. Just hit 'Apply' and then load your next file if you need to do several in a row. 3. After that it'll use the configured 'Image File' folder. I've just made a change (so it'll be in 2.5.7.0) where the program will attempt to use the most recently used (selected via the 'Browse' box) folder between existing steps 2 and 3 - and this value IS persistent.

If you burnt directly to disc, there isn't going to be one.

If it hasn't already been emptied, try playing the 'C:\Users\Ronnie\Documents\dvd\dvd\video_ts.ifo' file in 'Media Player Classic - Home Cinema' and see what it says for the length.

No offence but I think you're confused or just making things up. If you're burning pre-existing images, the file system and revision of file system aren't (and weren't ever) options you have to worry about.