LIGHTNING UK!

I'm seeing the drive report a 'write error' when attempting to burn MBI dvd+r dl discs and what I assume are verbatim DVD-r dl discs. As per the pinned topic about burning double layer discs, you should be using verbatim dvd+r dl media with the MKM dye/mid.

I guess the only way to know is to take a disc that fails to burn and verify in your aging 205 and try it in a new drive... the 209 perhaps. If it also fails (you'd probably have to try it a couple of times after doing another full format), you'll know it's the media.

Do what I said last time and let me know how you get on. I have no idea if it's copy protected or not, you could probably Google for that info.

I'd need to see the log from a failed burn from each drive you've tried and each different disc you've tried on that drive.

It might do it automatically. Burn one and see.

Post the log please.

You could try HDD regenerator or spinrite on the drive, but should probably look at replacing it ASAP.

Yes, that's the one.

ImgBurn already pops up a box when you do that. The OpenCandy switches have always been documented and I've mentioned them myself several times. The switch is handled by their plugin, it's not something authors have to deal with.

That doesn't mean they're right, I'm just more thorough.

Are you sure you made it scan the drive for bad sectors? Simply checking the file system for corruption isn't going to find this problem.

The problem is with your source drive. Have windows check it for errors and do a full surface scan to look for bad sectors.

Cycling the tray forces the drive to have to reinitialise the disc - it's not an 'unnecessary ejection', it's a key part of the verification process. If you really can't stand it happening, turn off the 'cycle tray before verify' option in the settings.

You're making a standard CD-DA disc there. 44khz, 16 bit, stereo. A DVD Audio disc is something very different and ImgBurn won't help you burn one of those. That aside, you may find there aren't any DirectShow filters available to enable conversion of your source files to that format (on the fly).

It hasn't filled it, you just can't write anything else to the disc because it's been 'closed' / 'finalised'. Don't rely on Explorer for info about a disc. It deals with file systems, not raw capacity.

I've no idea then db, sorry.

Forget ISO files then, they aren't going to help you. ImgBurn won't help you at all actually. Maybe makemkv or mkvmerge will do it?

ImgBurn doesn't convert anything, it burns as-is. You'll need another program that can output a DVD video folder structure for you.

I've only ever used madFlac as it's the only one that did what it was meant to when I tested a few. I've burnt lots of files from a drive that's different to the one where I put madFlac.

I guess they must be DVD+R DL rather than DVD-R DL if the booktype is showing up as DVD-ROM.... after all, it isn't supported with DVD-R (minus) format discs. It's odd that the drive doesn't list the current profile correctly though. Are you sure it's a recorded disc? Is there anything stamped around the middle of the discs? Maybe you could match a code up to a manufacturer.

I don't understand... can you not make a madFlac folder in your 'Program Files(x86) folder, put madFlac in it, register it and just leave it there? It shouldn't matter where the files you're decoding through it are located. As per my previous response, have you installed any codec packs?

Because the installer uses the OpenCandy plugin and I guess Norton have decided to quarantine anything that uses it. You can read about OpenCandy on their website. http://www.opencandy.com/

Noting in read or write modes when that blank is in the drive? Can you post the disc info from both modes from any and all drives you have in your PC at the moment please?

I see no log? That's a new error on me and certainly isn't hardcoded. I can only assume you've got a bad filter installed that directshow is trying to pull into the graph. Have you installed any codec packs?

Test mode doesn't attempt to write to the media, so obviously any issue related to actually doing that wouldn't occur. It's a 'theory' test rather than a 'practical' one.