LIGHTNING UK!

It's not infinite. There's a little fall back mechanism where if one variation of the command fails, another one is attempted. In the generic I/O error boxes, there's no way to differentiate between you telling it not to retry the same command (i.e. 'cancel'), or to totally give up. Depending on exactly which command you 'cancel', there should only be a few extra (slightly different) attempts at that specific function (be it closing the track, closing the session, closing the disc etc). Just don't have any failures and it won't be an issue! It's certainly not one for me.

The 'Media' tab has nothing to do with anything.

You're getting EXACTLY the same error? Have you not tried the 1.21 firmware yet?

ASPI is old now and ImgBurn doesn't use it, it uses SPTI instead (which is built into Windows). If you build an image rather than doing it on the fly (and then burn it), check and see if a manual verify returns errors in the exact same place - repeat the verify a few times, maybe even in different drives if you have access to any. Check and see if you're always getting errors in the same sector etc on multiple burns. Look for patterns basically!

If you look at the LBA column, you'll see that 4 and 5 are essentially the same thing, just different representations of it. What you need to remember (or learn!) is that the order of files goes... IFO -> VOBs -> BUP, (next VTS set) IFO -> VOBs -> BUP, (next VTS set)...... So by putting the IFO at the start of the 2nd layer, it's exactly as Blutach says - 'having the whole of VTS3 (and higher VTSs) on a single layer' - whereby 'single layer' is of course the 2nd one.

If the flag is set to show the burn failed, it'll now prompt before performing sync cache and the finalise disc commands (subject to further testing). I'm not so sure it's a good idea because drives can get confused if a write operation doesn't finish off properly and you just end up with loads of 'command sequence error' errors.

DMA is covered in the FAQ.

You cannot use ImgBurn for that, license an SDK off one of the big players.

I'd be inclined to go for the 3rd one down, but it's really not a big deal.

I'm not so sure that's true. If it errors out, you can abort it. This is a program suggestion more than a bug. I'll move it for you.

Unless you have DMA issues, there's nothing to fix.

The program that submits the write commands shouldn't make a difference. The only thing it can be if 'FreeEasyBurner' REALLY does always work 100% of the time and ImgBurn always fails is that it's using the Packet/Incremental write type rather than DAO, which ImgBurn defaults to. Either way, it's still a drive issue. Both write types should work, or both should fail. Just try changing the 'Write Type' setting to Packet / Incremental in ImgBurn's settings. Of course the media is the root cause of your problems and as everyone has already said, you should ditch it and start using some good stuff. Don't ever go by the brand name, it doesn't mean anything.

Just because the Verbatim disc works doesn't mean you should forget about the firmware update. The drive being up-to-date firmware wise is a very important part of the burning process.

You didn't need I/O debug mode on, it's only useful when I actually ask for it. That aside, you can see the error there... 'Das Zeitlimit f

If the original isn't mode 2, I don't see why you'd ever need to convert it. If it IS mode 2, just read another image from your original. One of the ISO editing utils might be able to convert it. I could tell you how to do it manually but you'd be there all year editing every sector!

It doesn't appear to be reporting the disc info properly. Notice it says 'Status: Complete' rather than 'Status: Empty'. Try looking for a firmware update for the drive.

Put ImgBurn back on the SPTI interface. When you've done that and have burnt another disc (or at least tried to), post the FULL log (from that burning session).

The only thing that can cause power calibration errors is the drive/media combo. As you're already using the best media available, it's pretty much got to be the drive.

Update your drives firmware to 2.1B and buy some decent Verbatim DVD+R DL media. The other brands are useless. http://forum.rpc1.org/dl_firmware.php?download_id=1904 If that doesn't work, buy a new drive.

Indeed, a write error means exactly what it says. The drive had a problem when trying to write to the disc. Change the media or change the drive. Simple as that I'm afraid.

Something is misbehaving and it's impossible to know what from the info you've provided. I'd need a complete log with I/O debug mode enabled before you click the 'Write' button. (press F8 to enable it). Enable it, start the burn, disable it. SAVE the log to a file and upload the file.

Dirty lens on the drive? Try a cleaning disc or something.

ok well you can't convert to that format with ImgBurn. Actually, you can't convert to anything with ImgBurn, only FROM something (when burning on the fly etc).

What bit is it stopping on? Writing the leadin or when writing the actual image? (look in the log window) It wouldn't hurt if you actually copied the log to your next post so we can see what's up. The program only ever submits commands and waits for a response. If it doesn't get one, there's nothing I can do about it, it's just some glitch with the I/O interface.

ImgBurn is just a standalone exe. If it's not running, the machine wouldn't even know it exists. There are no DLL files or drivers for it. As such, you need to look elsewhere for the cause of your problems.