LIGHTNING UK!

There are still file name length limitations, illegal chars and Unicode support that ImgBurn has to take care of - along with ensuring unique file names within a folder. The 'generating udf compliant names' bit just covers anything the program has to do for that file system. 2.50 and 2.60 have 'mirrors' of certain file system descriptors - this is already supported (and always used) by ImgBurn. The only benefit of those is the duplicate file system descriptors.

Playback of MKV would depend on your playback device. ImgBurn is just burning the file(s) as-is.

Use a proper hdd backup tool like Acronis TrueImage.

Try with some proper Verbatim 8x DVD+R DL discs (MKM-003-00 MID). If they also fail, get a new drive, yours must be faulty or something. You could try clearing the drive's opc history.

Try some other discs - your drive doesn't appear to like those.

It looks like controller / driver issue to me.

Verifying doesn't change the outcome (make a burn more / less successful), it just tells you if the disc is readable in that drive and that what's read from the disc matches what should be on the disc (comparing it to the source image/data). It's enabled by default because I believe it's always worth checking the discs. I'd never just rely on the drive not erroring out during the write phase to mean the burn was ok.

I'm sure if you search the internet, you'll find something telling you exactly what to do.

Ok so it burnt and verified ok. Now you'd check the burn quality using something like kprobe. If it's a decent burn, the issue must be with the source image or the playback device.

You didn't verify the burn so I can't see any error.

If you're formatting with spare areas enabled, the drive will be verifying as it burns... Or in this case, as the programs writes zeros to each sector. That'll be slowing it down a lot. For a really fast format, you also need to disable the 'prefer properly formatted discs' (or whatever it's called) too.

There wouldn't be much in it but I think the DVD+RW would win.

Assuming you aren't previewing a single cell, it's where the cell number changes in the box at the top.

So it plays ok in the drive that burnt it? Try and verify it again as a standalone operation.

Right click the drive drop down selection box and click 'Family Tree'. Close the message box that pops up and then copy + paste everything from the Log window please. It could be a controller / driver issue.

I believe the way that dialog box works (it's a Windows one and nothing to do with ImgBurn), you can either select the folder (so it's highlighted) or go into it and then click the 'Select Folder' button (assuming you don't select anything else from within the window). If you want more control, use the 'Advanced' input method - select it in the 'Input' menu at the top.

CD+G requires subchannel info and ImgBurn doesn't read or write that.

What message is written in the status bar of the main window when this happens? Don't try and close the program, just see what your system is having trouble processing and causing ImgBurn to hang.

The padding is nothing to do with the program, your drive is doing it.

Please post a link to the firmware update if possible so I can take a look myself.

What is it meant to be of? Maybe it's not any sort of valid disc image.

Does it actually play? Your drive is correcting stuff as it burns. If you need to burn uncorrected, you'd need to use a different program that supports raw mode burning. I.e. CloneCD.

Are you attempting that with ImgBurn? Don't. Use a proper hdd imaging tool like Acronis TrueImage or macrium reflect.

The lack of easy multisession support means making such discs isn't exact easy. I have explained how it could be done (in theory at least) a couple of times here in the forum. Have a search and see if you can find anything. I'm mobile at the moment so it's not as easy for me to do it for you.

It could vary by drive/firmware implementation, but I'd expect it to burn up to at least the 1GB mark if it's bothering to pad at all. The only time it'll be quicker is if you burn beyond that point. Burning the padding will take as long as burning real data and vice versa.