LIGHTNING UK!

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.

For whatever reason, if it's still saying it can't create an ISO of a multi track disc, the '/MODE BUILD' parameter can't be reaching the program and it's still stuck in Read mode.

Yes, you should be able to just point build mode at the drive letter and have it make an ISO of everything on the disc as Explorer sees it. If you're having trouble with that, post the command line you're using.

Ok, sticking with 4x, try enabling 'Perform OPC before write' in the settings and giving it another go. If that still doesn't work, you'll have to try some other discs to see if the drive is just faulty.

Not really, it just takes an image of the entire disc. Use EAC or something like that.

It would appear the drive is no good at burning those MKM-003-00 discs at 8x. Try burning at 4x instead.

The error was from the OS (or filter/codec), not ImgBurn. The OS doesn't normally like paths over 256 (ish) characters. It'll usually start using the short names for folders when that starts happening (notice the path and '~' shown in mediainfo's info) but in this situation, I guess that couldn't happen. I could potentially do something in my code to help it along.

I guess at this point I could do with trying the flac file for myself. Can you upload it somewhere, email it or whatever? You may have other filters that are being pulled into the graph and messing things up... it's hard to say without checking everything. All I know is that madFlac normally works just fine. It's what I'm using for such things and I have the same Win 7 SP1 x64 setup. Just one thing though, if you use ImgBurn to create your CUE file using the 'Create CUE' tool, can you screenshot the error box that pops up please when you add a flac file to the source box? The error message you've mentioned in your previous posts doesn't fit with what I seem to recall the OS saying when no suitable filters were installed. You may like to uninstall madflac, capture the error, install it and capture it again. Maybe you could also use something like InstalledCodec to create a report on your codecs. You can create an 'All Items' HTML report using the View menu and let me compare it to mine. http://www.nirsoft.net/utils/installed_codec.html