LIGHTNING UK!

Post the log please!

Although you'd think that's the case, it actually doesn't mean anything! You need to snoop in on the commands to find out what it's really using. I did a while back and found it used the incremental write type.

I'd recommend 8x or 12x for burning btw.

Have you tried burning at 8x or 12x? Maybe the 4x write strategy just doesn't work (4x is what it would use because it's the closest available to the 1x you selected) Try burning with 'Test Mode' enabled too, that'll at least tell you the system should be capable of burning the disc. (Turn it off again to do a real burn) How are the buffers when the drive appears to get stuck, are they both still full up?

There is no option to skip the erase/format. When burning onto DVD+RW media, either its 'Formatted' status is 'Yes' and the program will do direct overwrite or it's not and it'll prompt to format. If you don't format you can't continue.

No, this isn't the place for that.

Hit and miss burning is of course a problem with the drive/firmware/media combo. If it wasn't an issue it wouldn't have failed in the first place!

It's visible in all modes and is a pretty fundamental part of the program so it won't be changing.

So do as I mentioned before and mount the ISO in DT and compare the folder content. Just because the images are different sizes doesn't mean it's wrong. It will have built the image based on the options you'd selected. Do both images (ImgBurn and Nero) have the same number of files in them? If not, maybe some were hidden / system and you'd not enabled the option to include those types files. Oh and you might like to make sure you've got ImgBurn from the ImgBurn.com mirror. I made a couple of 'after last minute changes' on 2.4.1.0, one of which was to do with correcting OS installation disc settings. I doubt the other mirror sites picked up on it and so would have a slightly different build/version of 2.4.1.0

The first error before the retries kick in is the real error.

You don't set the layer break manually, leave ImgBurn to do it automatically (it'll provide you with options in a window). If you're burning DVD Video DL, read the Guides. It's all in there and with pretty pictures to boot.

Drives will always report the full size (2,295,104 sectors) of DVD+RW media when the 'GET CAPACITY' command is issued and DVD+RW media is present, that's just how they work. Try verifying when you burn, it might actually show a problem with the disc. I bet there's no problem installing from a disc in virtual server when it's 100% readable. It's not supposed to remember it. Nothing on that tab gets remembered as it's not something you'd generally use. Make a project file if you want certain settings for a particular build.

The first error (before all the retries) is the REAL error. In your case: "W 13:53:11 Failed to Write Sectors 33888 - 33919 - Reason: Write Error"

Nope, there's no real way to tell. Your media is just hit and miss. Even the ones that don't error out could be rubbish burns. Personally I'd just ditch whatever you have left out of that spindle and wait until some good discs turn up.

Booktyping happens at the end of the burn, the log entry is at the start and simply shows what the drive *should* be changing it to. If you get an error during the burn then it's very likely the drive will fail to change the booktype to DVD-ROM. You should leave the auto booktype thing enabled. It works fine when your drive / media do.

That would probably break the 'themes' support.

Ok well the one on the CD is bound to be out of date so now I'd goto the marvell site and download the latest one.

Please post the log (even if it's not complete)

If the drive keeps erroring out on that media (typical of CMC stuff), all you can do is try slowing the burn down, updating the drives firmware and ditching the CMC's in favour of some decent Verbatim / Taiyo Yuden discs.

What motherboard do you have? Most modern ones don't even have an 'on chip' IDE interface so the manufactures add a 3rd party controller chip. I'm guessing that's the case here too as other wise the device wouldn't be showing up as 'SCSI', it would say 'ATA'. Motherboard bios updates usually update the bios for the controller chip too, so be sure to look into those whilst you're hunting down updated drivers.

If the program isn't still open, the stuff in the log window won't help. In that case, you can find the log file via the 'Help' menu.

I wonder if the errors might be heat related? How's the ventilation in your case?

Please post a copy of the log (take it from the log window) Update your drives firmware and make sure you're using decent discs.

It's probably down to whatever drivers you've got installed for the controller the drive is connected to.

Go back and verify that first disc again in the standalone 'Verify' mode. As you burnt it from files (via Build mode) you'll obviously need to uncheck the 'Verify Against Image File' checkbox. The PIPO scan for the disc looks fine so I'm not really sure why the drive would be returning L-EC errors when ImgBurn attempts to read those sectors. As software has no say in the burn quality you might like to take this problem to the optiarc forum over at cdfreaks, where fellow 7191A users can comment. It is of course not unheard of that some drives perform better on certain media as certain speeds - especially where new drives are tailored to burning quickly (to the point of overspeeding) on the better MID's. btw, you're probably better off (for the sake of accuracy) doing PIPO scans at 4x on that drive.