LIGHTNING UK!

CIF files aren't really supported, I know nothing about the file format. ImgBurn just looks for the ISO9660 header within a file (this is the thorough fallback) and tries to work it out from that. Send me the first 5 mb of the CIF file and I might be able to do it properly.

Are you burning them as a data disc or an audio cd via the 'create cd cue file' feature? Have you read the guide on burning an audio cd?

If the discs you've already burnt have an audio_ts and video_ts folder on them, they're already in DVD Video format and should work just fine in your new player. So basically, what files / folders are on the ones that you say don't work?

Write mode burns disc images.... an AVI file is not a disc image. If you don't know how to use the program, please read the guides.

Logs are saved automatically. Look in the 'Help' menu within the program. ImgBurn has a fallback thorough check for images that aren't generally supported. I've never tested it with a CIF image - mainly because EasyCD 5 is ancient and I haven't run into one.

It's not for ImgBurn to recognise it, it's for Wine to make it available. Configure Wine correctly and ImgBurn will work just fine.

Wii games are protected against casual copying. Your drive probably won't read them at all (hence the problem) and nor will ImgBurn. Conversations on this matter do not belong on this forum, sorry.

You've got DMA issues, as can be seen from the initial error code. What controller is your drive attached to? Have you tried a new cable? (the shorter the better) Is the drive setup as a 'master/slave' drive properly and not on 'cable select' ?

Take the disc out of the drive. Does it then say medium not present when you load it and switch to read mode? As a side note.... 48MB free memory, do you have lots of other apps open? You're leaving yourself a little short.

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'.