LIGHTNING UK!

You aren't looking for a button labelled 'clean image'. You add the drive letter (i.e. D:) to the source box and build a new image that way.

Obviously they aren't the same discs as the ones using mkm-003-00 dye / mid or they'd have the mkm-003-00 dye / mid! Being printable has nothing to do with anything. You can buy printable versions of any dye / mid.

Sounds like a driver issue to me. What chipset does the motherboard use? See if you can burn in safe mode without a problem.

Different dye, different MID, different burning strategy in the drive's firmware. If they're branded as verbatim, they're probably from their basic / value range. You're getting write errors because your drive can't burn to them. They might scan ok when you do get an ok one, but you get far more bad ones that just fail than you would with a spindle of mkm-003-00 discs.

The CCD is only made if you've told the program to do that. I'm sure it's off by default. It's made so you can mount the image in Virtual CloneDrive - which doesn't support CUE files. Burn the CUE.

For the amount of data, yeah you'd be right in thinking there's less to read if you just do copy+paste and therefore it shouldn't take as long. In reality though, depending on the number of files on the disc, you have the overhead of actually 'finding' the files on the disc (parsing the file system) and the files aren't always in the perfect order for copy+paste so you get a bit of random accessing and that can slow it down a lot.

Ok, what answer would you like to hear? They are nothing like MKM discs. Have you ever even paid attention to the MID / dye before?

Use the 'write files / folders to disc button'. Add your files to the source box, put a blank in your burner and click the big button to start it burning.

You appear to be using low quality UME discs rather than the decent MKM ones that everywhere/one recommends.

You can burn them 'as is', yes. It won't convert it to a DVD Video disc or anything though.

What are you actually trying to do?

It can't, no.

You aren't using an optical drive, that's why it won't eject anything. Pulling in files from a disc in build mode doesn't count, it's only for a proper source / destination drive. Obviously the 2.5.7.0 shouldn't be in there. I did say the readme.txt covers the additional switches you'd need to bypass certain prompts. Off the top of my head, it's /noimagedetails or something.

No, it's not dead. I'm just a bit busy with other things and the current release is working fine.

It doesn't come bundled with anything, the installer uses the OpenCandy plugin and that can offer 3rd party programs as part of the normal installation wizard. Just opt out of installing anything you're offered if you aren't interested. You do that the same way you opt out of anything... Usually by checking or unchecking a checkbox. What it offers can change each time you run the installation wizard as the whole thing is dynamic. There's nothing included (bundled) with the setup file itself.

If you're burning something it can detect (like DVD Video, BD Video etc), yes, it'll tell you if you're using the wrong options.

No, they work in all modes. Once your applauncher thing has done its job, fire up task manager and have it display the command line column. Check to make sure ImgBurn.exe has been called with the correct set of parameters. To my eyes, you don't have enough quotes in that string. Read the readme.txt file. It tells you all of the command line parameters.

Add an exception or turn it off for a few minutes.

Surely all you changed was the boot image bit and file system selection? The boot image option doesn't survive the app being closed and reopened. The file system option should be all you'll have to look at.

Are they still not visible after a reboot? What about if you boot into safe mode?

Your log is incomplete.... or perhaps just missing info I'm now too used to seeing - you're using a really old version of the program. You do have a BDRE drive so if it's returning that error, it must not like the media you're trying to use. That's nothing to do with ImgBurn.

As I said in my previous post, you'll have to try some different discs and/or return the drive.

The disc appears to be unreadable. That isn't an error code your drive should really be reporting though, maybe another bit of software is messing with the return codes or the firmware is just buggy. I see AnyDVD is mentioned in the log file... you have done what it says and disabled it yeah?

Try using isopuzzle.

Use build mode. Create image file from files/folders.