LIGHTNING UK!

PLEASE turn off debug mode when you post logs. You never need that enabled unless I ask for it - it just makes everything harder to read.

Are you perhaps just using the ISO9660 filesystem? That only supports uppercase in it's standard form. If you add Joliet and/or UDF into the equation that limitation is removed. ImgBurn defaults to ISO9660 + UDF so if it's not working (and not on that already), you must have changed something.

Barakban12, Again, we don't need debug info. If I need it, I'll ask for it. Adding it yourself just makes it 100 times more difficult to read the logs. Your drive is failing to close the disc. Ditch the CMC discs and get some decent Taiyo Yuden or Verbatim ones instead.

If you already have the original discs, just use Read mode to create your image. It'll already be bootable that way without you having to mess around with anything.

Try burning at 8x. That's decent media and you've no need to slow it down. I can't be sure on the make of your burner but it looks like it could be emprex/btc (from a quick google search). All their drives were rubbish so if it's one of those, do yourself a favour and get another one. Shame on whoever made your new pc for fitting one of those instead of a decent make.

The eeprom one just means it'll remember it between reboots - so you can set it once and then forget it.

That's a little weird, it should do! I had to force the detect duplicate files code off when building DVD Video because of the whole IFO/BUP thing.

IF your drive can't verify the disc, it must have produced a bad burn (assuming it can read other stuff of course). Try burning at 8x or 12x. If you get the same problem, find yourself some TYG02 or TYG03 media and try that. If you can find some Verbatim DVD+R MCC dye media, that may work too. If none of them work, try cleaning the drive and failing that, get yourself a new one.

Oooh only on the BS0A firmware, wow that's a lot of updates you've missed out on.

Microcosmo, When you had that error you could have tried just ejecting + reinserting the drive tray. Barakban12, If it burns and verifies ok, the problem lies elsewhere.

Get some TYG02 Taiyo Yuden discs. If they don't work either (burning at 8x), get yourself a new drive.

'Check Condition' is a generic term, it's something for me rather than you The actual error is this one: E 14:36:13 Failed to Read Sector 4705 - No Seek Complete So the drive has produced a disc it can't actually read back - i.e. a low quality burn. You could try speeding up the burn a bit, it might actually be better. Failing that, look for firmware updates and then try getting some better media (you get what you pay for!)

Tools -> Settings -> Write tab -> Queue Options -> Eject tray before next write. Or Tools -> Settings -> Device tab -> Options -> Eject tray after write. The first option won't eject the tray after the last image has finished burning - so your drive won't get so dusty if you leave it

An 'Ignore verify errors' checkbox is doable and I'd be much happier to implement that over a /QUIET switch that turns off all dialog box error reporting. The next question is do I make that box also ignore miscompare errors? For consistencies sake, it shouldn't do.

I can't see any use for this at all really - at least not when ImgBurn is used for personal use. Either way, it's not something I'm interested in doing I'm afraid. You'll have to go with emailing yourself a copy of the log.

As does ImgBurn. A verify is not what I consider a read operation. Just because DVD Dec / ImgBurn will retry on a failed read does not mean the OS / other programs will - hence it's important that the Verify DOES NOT retry automatically. I'm fairly sure DVD Dec's verify didn't auto retry either. btw, if you're just backing up to an RW, why not just make an image to a different hdd / machine somewhere? Then if you need to restore you can burn the image/disc as and when required. You might also like to consider using DVDRAM discs instead.

The CLI options automate gui checkboxes and stuff like that. If you want a CLI program, try one of the tools from the DOS version of cdrwin - www.goldenhawk.com. At the end of the day, ImgBurn is a GUI app and I actually don't want to make it any easier for people to use it without the end user being made aware of it. As for your verify issue, might I suggest you try and fix your drive/firmware/media combo so these kinds of issues don't pop up.

Blimey, could you imagine how many emails I'd get if every I/O error resulted in me getting an email?!

Try updating the drives firmware (to KS0B) http://forum.rpc1.org/dl_firmware.php?download_id=2056

Are you running Vista? You may have to point the destination file to somewhere you can actually save to - i.e. not the root of the drive.

Have you done anything recently like updating the firmware?

If Verify fails, you've got issues. Do not ignore them - ask for help.

If you abort when it's saying the leadin is being written, it's already too late if you're trying to avoid a coaster. ImgBurn doesn't actually do anything with the LeadIn, it's a drive function. Different drives handle it in different ways. Some will write it when the first 'Write' command is sent to the drive and that command won't finish being processed until the leadin has been written and the 'Write' has completed. Others will accept write commands until the buffer is full AND THEN go about doing the leadin. As such, it's a 'best guess' situation. Either way, if it's taking far too long to move onto the 'Writing Image' stage, it's a sign the drive is having issues writing to the media. If your drive is decent, it's firmware up-to-date and you're using decent media then there shouldn't be any problem.

What's telling you they're too big? If that drive really is formatted using NTFS, I don't see why 4GB would be an issue.

Oh I'm with you. Ok well that can't really happen or a custom ordering wouldn't be possible. (well, not without more options, context menus etc) Sorry but this is your issue really!