LIGHTNING UK!

If you don't have a drive that can actually over burn (where you then wouldn't be prompted at all), you should use the truncate option so the burn doesn't end with a failure to write beyond the end of the disc.

I think you've muddled up what it's telling you to do. The only build mode prompt for audio is an mp3 disc and it would recommend iso9650+Joliet for that. It does that because they're the most compatible in standalone players that support such discs. If you want to stop it prompting you, go into the settings and tell it not to.

You should have used truncate and left verify enabled. Then we could have seen what was going on.

Opting out works just fine, you must have missed something. OpenCandy's policies wouldn't have it any other way.

Because the installer uses the opencandy advertising platform to make product offerings during the install. You can read about opencandy here - http://www.opencandy.com/

Which error exactly? The buffer one? Stop using your machine quite so much when burning, your hdd can't keep up the demand for data.

The default settings work just fine. Buy Verbatim MKM-003-00 discs and enable the drive's 'Force HyperTuning' option. Then burn at 4x and it should work just fine - use the current version though.

That isn't possible at the moment. I'll add support for it though.

Check the disc in your PC, I'm sure it'll say there are 19 tracks. As such, it's probably an issue with the headunit or your burner is creating a non compliant disc. Some older Samsung drives used to do that.

Yeah just burn the ISO as is using the 'write image file to disc' option. Just make sure ImgBurn mentions 'Bootable' next to where it says 'File Sys' in the 'Source' box once you've loaded the ISO.

New member cannot hijack other peoples threads. OpenCandy is just an advertising platform. It's serving up program offerings in the same way Google AdSense serves up adverts on a webpage. Whichever advertiser bids the highest for a given request is the one that gets shown to the user. There are several ways to install without ever seeing the OpenCandy offers and these have all been documented here on the forum (and in the OpenCandy FAQ). You can also just 7zip the setup exe and drag out the ImgBurn.exe file yourself. Nothing is going to get 'sorted out'. Just adapt and deal with it.

You can't rectify it, it's normal for iHAS B drives to fail with that error when the program attempts to set the layerbreak. It's already in the right place though, hence why the 'Effective' line is correct and the burn continues without you doing anything.

Install.bat calls installfilter.exe with the madflac.ax file as the parameter I've personally tried and tested madFlac. It was one of the only flac filters that would decode a flac file and give me a wav file that 100% matched the original wav file.

Not the advanced tab, advanced input mode. Click the 'input' menu at the top of the main window and then click advanced.

Like you said, the drive is old

Install the madflac directshow filter. It's linked at the bottom of the audio cd guide in the guides forum.

So the file is called '01.In Sharky Water.flac' but the CUE says it's '01 - In Sharky Water.flac' ? The names must match exactly. Can you get a screenshot of the folder in explorer for me please? Use 'Details' view and try to make sure the name column shows the complete filenames. Upload the actual CUE too please.

Do the files exist in the same folder as the CUE? Are they still called those names? (don't forget to make Explorer show file extensions if it isn't already doing so - you may end up with 'xxxx.wav.flac' or 'xxx.flac.wav' as a name otherwise). It should be quite easy to work out why it's not working when you have everything there infront of you.

They might be on your hdd but that doesn't mean they're ending up in different folders in the image / on the disc. You're probably just dragging both 'c' folders to the source box yeah? You'd have to 'preserve full pathnames' so that the different parent folders are added to the image to get around the clash. The program wouldn't error out if there wasn't a problem somewhere along the line. Take a screenshot of the error message and also of the main ImgBurn window showing the 'Source' box (ideally in 'Expanded' form). All of this stuff is made much easier/clearer by using Advanced input mode and the Disc Layout Editor window.

Sorry, I can't really tell / do anything without a log. Both methods work fine for me. What gets written to the image file or directly to disc is also identical. Can you burn to a BD-RE to try and capture the error? Technically, even just burning to DVD-RW / DVD+RW would do the job. Obviously this isn't a generic issue as ImgBurn is used by loads of people all over the world for BD burning. Lots of applications actually hook into it for that very purpose - BD Rebuilder etc. If it just flat out didn't work, I'd have known about it aaaaages ago.

Turn off 'perform opc before write', you don't need it on. You don't need the payload tool either, it's built into 2.5.8.0. As for the actual issue, I'd guess it's down to bad communication over your USB adapter. Can't you plug it in directly via sata/esata?

If they've been converted to flac files, you'll need to update the CUE file so it points to flac files and not the original wav files. Just do a find/replace on .wav" with .flac"

There's no difference between writing files/folders or writing an ISO. There's only 1 lot of code that does the actual burning.

When you're in Build mode, the 'information' tab is on the right of the main screen. You really can't miss it. Click the 'calculate' button on it and you'll get your progress / capacity bar. To enable Advanced input mode (and the disc layout editor window), just click the 'input' menu item at the top of the main window and select 'advanced'.

2 files with the same name can't end up in the same folder. If it's not obvious how the combination of several source folders will end up in your image, switch to Advanced input mode and use the more visual way of building your disc.