LIGHTNING UK!

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.

Yup that's exactly right. ADIP is 'read only' and the Last Recorded one is updated at the end of the burn (this is done by the drive, not the program). As the finalisation failed, that's probably why you're getting bogus info. Samsung drives seem very bad at this.

It all boils down to the same thing, the drive can't burn the media. Get some Taiyo Yuden or Verbatim media and try again.

Eject it and reinsert it, the drive obviously hasn't initialised it properly and is returning rubbish.

Whilst you're in the updating mood, put service pack 2 on!

You'd do well to invest in a new burner, yours is ancient now.

The 'Last Attempt' is actually slightly different to the normal one and is performed as one final attempt to get you a working disc. You have to understand that errors during the final stages are NOT supposed to happen, and if they do it's typically once in a blue moon. The 'Last Attempt' is therefore not really a big deal for most people but I can appreciate that if your drive bombs out on all discs then you may well get annoyed with it happening. You shouldn't get 2 sessions because there's never a 2nd one opened that need closing. That would be a drive / firmware issue if it's actually happening. The samsung drives seem to be the worst ones for these errors, hopefully the next firmware release will fix it. See if it makes any difference having the 'DVD+R Reserve Track' checkbox ticked in the settings (on the Write tab)

When you pick the ISO, if there's a DVD file with the same name it'll tell you to use that instead and will automatically switch to it. Think of the DVD file in the same way you would a CUE file (that normally goes along with a BIN file). The .DVD file contains the names of the files which make up the image data. Your .DVD file should have contained the name of the .ISO but it was wrong and had a name of a file in it that simply didn't exist.

Those values are only really used when you have too much to fit on single layer media. The size difference between the DVD-R and DVD+R ones is exactly what corny said - if you select DVD+R you'll need to go double layer ever so slightly before you would do if you used DVD-R.

Did you read the bit in red at the top of this forum? What are you burning? What 'Mode' are you in within ImgBurn? (i.e. Write mode, Build mode, Read mode etc.)

Use Verbatim DVD+R DL discs. They're more expensive because they actually work. You could try cleaning the drive too.

It wasn't the number so to speak, it was the order in which/the way they're processed.

If the program found your drive in the list then don't worry about the aspi thing. I guess if it doesn't want to update then you're stuck.

When you think it's stuck on the sync cache bit, press the F8 key and look in the log window. If you see lines being added to it ever second, the drive (or some rogue driver) is just saying it's still busy doing something - I'm afraid there's nothing I can really do about that. Press F8 again when you're done to turn off I/O Debug mode again.

http://www.ricohpmmc.com/download/DVD/loader/RFlash.zip Try the rflash.exe program in this zip, it's a bit newer. You could also try installing the legacy Adaptec ASPI and changing the 'compatibility' flags on rflash.exe so it thinks it's being run under Win 95 /98 etc.

I did a (far) more complex build with almost 200,000 files, 150,000 of which were dupes. Found the problem and fixed it. Many thanks

You might have discs that your drive doesn't support. How old is the drive? Does it support both format discs? i.e. DVD-R and DVD+R ? Have you tried updating the firmware on it? Have you tried some totally different discs? (Don't go by brand names, you need to find out the dye the disc uses)

It's of all the actual data. Like CRC only better and more reliable. If it passed verify (ignore the MD5 values, they're cosmetic and nothing to do with a verify pass/fail), the disc is 100% fine (Well, it's content matched what was read from the file anyway!).

The padding value comes from burning a file that doesn't have a 'number of sectors' that's divisible (exactly) by 16. When you burn to DVD+R media the drive will always pad the image (disc) so the size is divisible by 16 - so if you read the disc back you'll get the MD5 shown in the 'padded' line and not the other one.