LIGHTNING UK!

You need to reauthor the disc using software that supports such a thing - this is not something ImgBurn can do. Just Google 'combine dvds' or something

Hmm where are all the other buttons that are supposed to be on that window?! Padding is where ImgBurn fills up some sectors with 'zeroes' to move the data on the disc to a later LBA. i.e. if a file normally starts on LBA 10, I could add some padding to make it start on LBA 15. Padding is required so everything gets aligned properly. Basically, try to get the split as close to 50/50 as you can whilst picking a Cell that looks ok - use the 'Preview' feature for that and find a cell that's not part of a fast action scene. The Preview feature should be visible as a button down the bottom left.

A burn error would have nothing to do with checking for updates. (In these situations it helps if you provide the real / full error). It should go without saying that if you want the program to check for updates then you need to allow it through your firewall. Likewise, it's silly saying the program can check for updates and then blocking it from doing so at the firewall. That's like someone saying: Sure, you can drive my Ferrari.... but if you get within 10m of it you'll die.

You're in Write mode, switch to Build mode. It's probably easier if you take a look at the Guides, that's what they're there for.

You've got a driver installed that doesn't support (is blocking) the command used to format a disc - that's normally because the controller is meant for HDD's and not Optical drives. Look for driver updates and maybe the problem will go away.

Thanks for the donation AlienX69. I hope you enjoy using your new rig Merry Christmas and a happy new year to everyone too!

Rebuild the image using Build mode having first extracted the ISO content to your hdd somewhere (or mount the ISO in DAEMON Tools and build directly from the virtual drive).

I like PerfectDisk myself

You can actually just add 'DVD-R' / 'DVD+R' / 'DVD+R DL' to the list and do it that way. (i.e. any of the values that show up under 'Current Profile') That's as generic as it gets though.

*stuck* would be where it's still doing it after 10 minutes, not just 10 seconds. Do you have any DVD-R discs? Does it do the same on those?

It might be easier to just use DVDFlick or ConvertXtoDVD. They create the proper DVD Video file structure.

Are you using Vista? Point the 'Destination' to somewhere you actually have access to save to.

If it's stereo on your hdd it'll be stereo on the disc. ImgBurn doesn't change anything so there's no way in the world for that to happen.

When does this actually pop up? Before the burn or after it?

ImgBurn can't read the layer break info from NRG files so those images will be of no use to you if you want to burn with ImgBurn.

It all depends on what you're after. If you need all the extra stuff that Nero provides (conversion etc), obviously you'll favour Nero. If you just want a relatively simple burning tool, ImgBurn has some nice features.

If you're loading the .DVD file it shouldn't ask you to select a layer break position - it'll read it from the .DVD file. However, if the one in the .DVD file is not valid for the type of media you're burning to (can happen if going from PTP to OTP), it'll have to prompt you. To be fair though, there's no point at all in using CloneCD for the reading part if you going to burn with ImgBurn anyway. You might aswell just use 'Read' mode in ImgBurn, they do exactly the same thing.

If you install Nero Image Drive the securom program might not like it. ImgBurn is just an exe so it can't mess anything up.

I'd have to assume your drive is just making duff burns. Maybe try giving it a clean?

You should really post a copy of the burn log. You might also like to include a copy of the IBG file - export it manually via the 'File' menu if ImgBurn isn't set to do it automatically.

If you have an image you use Write mode.

Delete the DirectCD ones and update the Elaborate Bytes program you've got installed that uses the ElbyCDFL one. Alcohol uses a very low level driver for it's I/O so it basically just bypasses all the crappy filters that are causing issues with your setup.

As I kinda mentioned before, the 'cancel' does cancel... it takes it out of the retry loop. After that there's another bit of code for the last attempt that runs if the previous code (in the retry loop) failed. If the drive was working properly there's be no need for this bodge workaround you think you've come up with.

Check for firmware updates and buy Verbatims instead.

How are your buffers when burning? Are they rock solid on 100%? If not, that's why it won't burn faster - there's something in your system that's limiting the max speed. It doesn't matter what you *try* and set the speed to, the drive will ignore it and go to the next closest supported value.