LIGHTNING UK!

Have you deactivated AnyDVD? It could be rewriting the drives response to that command?

There is no 'express' option in imgburn's installation process. If that's what you saw then it was for an opencandy product offering.

Pay more attention when you install programs. You had the chance to opt out of installing whatever the opencandy platform offered you during the installation of ImgBurn, you just missed it.

The command used to obtain that info must be failing for some reason. Go into write mode without a disc in the drive, press F8 to enable debug mode and then insert your disc. Save the contents of the log window via the File menu and upload it so I can take a look.

Are you sure it's hanging and you aren't just looking at the disc % used / capacity bar?

That log doesn't contain any actual 'operation' info from 2.5.8.0. The log file is only updated when you shut the app down. If it's still running, just copy + paste everything from the log window.

If you have an ISO (an image file), you'd use the top left option - 'Write image file to disc'.

You can't predict anything will work or not work. Try enabling the 'Perform OPC Before Write' option. It's one of the only things software can do that might make the slightest bit of different to how a drive burns a disc. The software has very little to do with the process, all it does is feed the drive with data.

Only by editing your source files, it's not coming from ImgBurn. Sometimes the directshow filters used in any required conversion could be responsible too I guess. For foolproof 'no gaps', use a lossless codec (or raw/wav/pcm).

You aren't using the right 'mode' for creating an Audio CD. Read the Audio CD guide if you don't know what you're doing.

All I can see in the log is that the drive thinks it's burning the discs ok but is then unable to read back what it just wrote. So either it did a bad job of burning the disc (low quality burn) or it has a general issue with reading discs. Max speed rarely produces the best quality burns. It's only ever going to be your drive or the media at fault here. If you were able to burn and verify ok at 16x on those discs before then it could just be that your drive is dirty or it's slowly dying.

Please post the log file - as per the pink box up the top

Verify your burns. Without it, we can't see if your drive actually burnt the disc properly. This applies here too. http://forum.imgburn.com/index.php?showtopic=8000

If it's locking up then it could be a driver issue. Right click the drive selection box and pick 'Family Tree'. Close the prompt and then copy + paste everything from the Log window.

Post the log please so we can see what happened - as per the pink box up the top.

Post number 2 still applies.

Try installing some of the intel rapid storage technology drivers. Start at v10.8 and see if that goes on ok. If it doesn't (i.e. your motherboard's chipset isn't supported by it), try one of the v11.x versions instead. Your drive reports it can burn Blu-ray discs so ignore what the Dell forum people are telling you.

You'd have to show us what you're doing. Get a screenshot of the main window once you've loaded your CUE file.

Try burning at 8x or something rather max speed, your drive may do a better job on those discs at that speed.

The installer uses the OpenCandy platform now for handing the product offerings during installation rather than physically bundling the Ask.com toolbar. No software is physically bundled with ImgBurn now. You can read all about OpenCandy, how it works, what their policies are etc. on their website. http://www.opencandy.com/

Converting something to a single vob file doesn't make it DVD Video disc compliant. You need the complete folder structure and other files (IFO/BUP). Use DVDFlick or ConvertXtoDVD to convert your MP4 files into DVD Video format and then burn the VIDEO_TS folder.

Just add the drive letter of your optical drive to it - e.g. 'D:'

Update the firmware on your drive and try burning at 8x instead of 'MAX'. http://www.firmwarehq.com/Samsung/SH-S223Q/files.html

Right click the destination drive box and click 'Family Tree'. Close the message box that pops up and then copy + paste everything from the Log window please. At the moment it looks like an issue with your drivers - the real error may be getting lost.

There's no bug, either the function call is successful or it fails - as is the case here. I have no say in it working or not.