LIGHTNING UK!

It must be EXACTLY the same error in EXACTLY the same place.

It's the auto retry upon the finalisation error that seems to be messing it up.

Untick the 'automatic change booktype' (or something like that) in the settings on the Write tab.

It shouldn't matter

Sorry, it's just a Windows API function that I call with the specified size. It's failing and that's the reason Windows is reporting.

On the Write tab in settings, untick the 'Finalise Disc - Auto Retry' option and the one to the right of it too (without a name/caption).

What does that error say in english? The API call is failing, it's nothing to do with ImgBurn.

You only need double layer discs if what you're burning requires a double layer disc! (that image doesn't) You're ok to buy DVD+R or DVD-R (i.e. both the available formats)

The drive doesn't support the discs you're using. Get some 8x Verbatim / Taiyo Yuden ones. You could also check with whoever manufacturers your laptop to see if there are any firmware updates available for the drive.

Try some better media. Some proper 'write once' (i.e. not rewritable) media maybe - by either Verbatim or Taiyo Yuden.

Please post the log.

sorry I should have said that you need Immediate I/O enabled (or rather not disabled!) when doing the F8 debug testing!

You didn't burn anything going by those logs.

Try doing one with 'Immediate I/O' disabled in the settings - you might get a different error code as the drive then won't return control to the program until it's finished finalising - rather than ImgBurn polling to check if it's done and detect any errors. What would be interesting actually is to capture the full error in the log. Next time you burn and it gets to the finalising bit (or just before it), press the F8 key to enable I/O debug mode. Then if you could copy+paste the chunk of the log (or save and upload), I'll take a look at it. ImgBurn *could* ignore these error at the end - which I bet most programs do - but that doesn't really solve anything. If there wasn't a problem, the drive shouldn't be reporting that there was.

You might have more luck with DVD+R discs, at least they're supported up to 8x rather than just 4x. Really though you could just do with investing in a new drive.

right click the drive in explorer -> properties -> tools. Tick both the checkboxes and click start.

Ah, read mode... I thought we were talking about build mode. Yes the file name comes from the volume label and changing underscores to spaces has never been an option. You can still change the name to whatever you want though, it just means you have to do it manually and that'll take a minute of your time.

If the program can't read from a file then you probably have an issue with your hard drive. Run check disc (chkdsk) on it and check event viewer for related errors.

No it's not, ImgBurn isn't doing the decoding. It's feeds DirectShow the mp3 data and then burns the PCM data 'as-is' that it returns.

Update the firmware and try again. If it still errors out you should invest in a new drive. http://www.plextor.com/english/support/dow...s/firm_708A.htm btw, trying to burn at 1x on 16x media isn't always a good idea. You'll often get better burns at a speed closer to its actual rating.

Oh I guess you mean that when you fill out the ISO9660 and UDF volume labels the program then suggests a name based on it for the destination image file and you don't want underscores in that one. I'd work the other way around - fill out the destination file name and let it generate the volume label from that.

The firmware wouldn't have fixed the noise, that'll be from the filters your machine is using to decode the files probably. Load ImgBurn, press f6 and then load your CUE file. The log window will list which filters the conversion is using and there might be a clue in there as to what the problem is.

You can call the destination file anything you want, it's free text.

Tray cycling is very important in my opinion - hence why it does it by default. You know that UDF 2.60 is new and not really compatible with anything except the very latest OS yeah? You'd be better off sticking to 1.02.

The minimal radius option should only apply when there's no a lot of info on the disc. The drive then automatically pads the burnt area to 30mm (from the centre hole) to make it more compatible with drives. It would be a bit odd if the drive throws up the PMA error with that switched on but not with it off.