LIGHTNING UK!

I'm sure the Mac will read iso9660 and udf, even if it doesn't support Joliet. As such, the default settings will work fine.

Post the log please. If it worked ok before, you're using verbatims and have tried cleaning the drive, yeah it's probably died and you should buy a new one.

No, I mean where you've configured the boot image options within ImgBurn.

That log doesn't add up. Have you manipulated it? Post the real unedited version of you burning a disc in your drive please.

Your drive is reporting that status, so it doesn't think there's a disc in it. If it can't see discs, try cleaning it with a cleaning disc.

The payload appears to work ('enable') on lots of drives, that doesn't mean it will actually work. Like I said, specific hardware and media is key. Can you post the log of the actual burn please?

It's a bit hard to answer that without seeing exactly what you did, what your source files were and more technical info about your machine. Is it even attempting to load from the DVD? Are you using UEFI? Why are you making another disc if you already have one that works? If you're customising it, I guess not everything is equal. Could I ask that you please post the log from the build / burn so we at least have that to look at. A screenshot of the boot image tab would help too.

You're lucky it's ever done anything on that disc. Multi session DVDs aren't supported. Read mode blocks them, verify mode doesn't appear to (I probably forgot) but obviously doesn't work. It's reading from the wrong places, so verification is pointless on such a disc and for whatever reason, it's trying to read faaaar too much in one go and that's why you've got the error about the user buffer. Edit: oops not far too much, it's trying to read backwards or something as it hits session 2.

There's a guide for it in the guides forum.

Nope, sorry.

You need the right hardware and media to successfully overburn DVD+R DL discs. Post the log please.

That's a windows thing and would just be to do with your file associations. I believe *.log defaults to opening with notepad, so if that isn't working, something has broken that association.

The log is just a text file, open it with notepad.

You can't do it with ImgBurn I'm afraid.

File systems (certainly iso9660 anyway) require the files to be listed alphabetically in the file system descriptors. That's why ImgBurn rearranges them. If you want them to playback in a certain order, you may need software that can create a queue or playlist and play based on that.

The other two options to play around with are 'perform opc before write' and the 'write type'. They're pretty much the only ones that can make your drive behave differently. Otherwise, software has very little to do with the actual burn.

That shouldn't be necessary, I'm sure the discs that showed as having no files on them are actually fine. Sometimes windows just needs a kick to make it read the disc. Rebooting usually does the trick.

OpenCandy is a plugin for installers that inserts 3rd party program advert pages in the wizard. There's nothing wrong with the plugin itself and it doesn't do anything outside of the installation program. You may not like the software it offers, in which case, you just opt out of installing them. If you weren't offered anything, you've nothing to worry about. No, the installer hasn't changed.

Is some files aren't visible, your player is probably filtering them out because it doesn't support them.

A firmware update for the drive may fix that... can you post a log so we can see which model you've got?

You're burning in build mode aren't you? Therefore you'd never have an MDS file to burn from (and it doesn't apply). As for the amount on each layer, that's whatever it lists as the free capacity on the blank DL disc and then divide it by 2.

If it's prompting you to pick a layer break position, it's because whatever you're burning won't fit on layer 0 alone. Don't forget, layers on a DL disc are smaller than the layer on a SL disc. 2 x SL disc does not equal 1 x DL disc. The DL disc holds less.

You should have let it verify. Without it, there's no way of knowing if the disc is actually readable. Drives often go through the entire burn process without erroring out, but the disc is still a coaster.

Post the whole log please.

All I/O commands should complete within seconds. You'll probably have to reboot and try again.