LIGHTNING UK!

I'm not so sure those errors are anything to do with media. Verbatim DVD+R media (i.e. the MCC-004-00 dye you're using - assuming it's not fake!) is typically better than their DVD-R discs.

ImgBurn doesn't require a reboot, it's just an exe file. Your drive probably needed one and that happens when you reboot the pc. ImgBurn doesn't limit the write speed selection box, it's left to the user. Supported write speeds are shown in the disc info panel on the right. As for absolute paths, did you perhaps tick the box for preserve full pathnames?

Read the FAQ?

Don't bother, the drive is still ancient and not built for today's media. You'll just be changing one relic into another one.

If you open ImgBurn manually when DVD Flick is open, does it work? I'm just wondering when exactly the drives are being opened - either incorrectly or for exclusive usage. Of course neither of those are wanted / required.

It's probably just windows getting confused. Close ImgBurn down, open my computer and eject the disc from the drive, refresh 'computer' so it knows there's not a disc in the drive and then insert it again. Once windows actually tries to parse the disc properly it should work fine. Do you have autorun/autoplay enabled?

9L09 firmware is out now, you should update. Try burning at 8x or 12x. Trying 'MAX' on rubbish media is never going to end well!

So some other program has the drive open and isn't sharing them so other apps can use them - hence the 'Access is denied' message. Maybe it's in part of DVD Flick's code where it detects the drives available and passes your selection to ImgBurn.

You should only use Dell firmware on a dell drive, they can tweak the hardware and you could end up damaging the drive or rendering it useless. Rebooting/cycling the power is the first thing anyone in IT would tell you to do if you run into a problem.

Which of those filter lists is the new/current one?! The top picture is showing a 'clean' system, the other one has junk installed.

ImgBurn reads in 64k chunks which is pretty much the norm.

Are there easy steps for me to reproduce this? - or does it just never work?

It's Samsung and if your drive supports changing the booktype ImgBurn will have done it automatically.

It's the nforce drivers.

I assume you've tried again after rebooting the pc / cycling the power? Your drive accepted all the 'Write' commands so it's the one pretending to burn, not ImgBurn.

You've got bad controller drivers on, try updating them. Your drive should not be showing up as 'Fibre'.

Use a custom media size for single layer (done within the GUI) and set it to some large value... then the program will think you're always building discs that'll fit on single layer media and hence never prompt for LB info.

I guess the burn quality isn't all that great. Try a different speed, the drive might then do a better job.

Eject the disc and reinsert it. Does the message in the status bar change to something else before then saying no media is present? If so, your drive just doesn't like the discs. Buy different discs or buy a new drive.

Yeah it was a link to moneybookers or some crap like that - and with a Referral ID attached to it. I have no interest in joining any other company for handling donations.

If you got an actual ISO file on the disc that you can see via My Computer you obviously used Build mode and not Write mode - or the original disc was also like that.

Of course drives are picky, they're all different and each firmware version is an attempt to improve the situation - for that specific drive. Hell, even different models by the same manufacturer can behave totally differently with the same media.

I guess your player just doesn't support DVD video content on a BD disc. The only way around that would be to convert it to BD format and that's not something ImgBurn (nor I) can help you with.

DVD Flick uses ImgBurn for burning and Nero will of course use it's own engine for burning and it'll be part of the conversion program. You don't need to make an ISO, you can burn on the fly. It's still done in Build mode but you set the 'Output' to 'Device' rather than 'Image File'.

Buy new discs or buy a new drive (assuming the firmware update doesn't fix it), take your pick.