LIGHTNING UK!

They're just different roads to the same destination, it doesn't matter which one you take. That said, I use SPTI all the time so that's the one that gets all the testing.

Yeah it means the drive doesn't support the command. That's to be expected, only certain drives with certain firmware support the entire set of booktype commands. So ignore the temporary one and look at the 'Drive (For DVD+R DL Media)' one instead. Make that say DVD-ROM and the drive will remember it forever. Oh and just because your bothers laptop works with the discs it doesn't mean yours will. We ONLY recommend Verbatim DVD+R DL discs here for DL burning.

Well then it probably wasn't present on the original. The flag goes in the cue file, you know that yeah?

Fluke bad burn - defect in the dye perhaps or dirt on the disc, nothing to worry about. Do as you say you've done and just burn it again.

If the temporary ones don't work then the one stored in the firmware probably will - and it's not something you have to change every time. You set it once and forget about it. ImgBurn handles the temporary ones (when they're supported) as part of it's 'auto change book type' setting... so again, it's not something you need to worry about.

No, there's no 'copy' feature. That'll probably come in a later version - for everyone that's too lazy to do a read and then write.

This is a dupe of a previous request. Please search before posting.

This is a question, not a bug report. The answer is yes it can and does.

You should be loading the .DVD file... and that's not on the virtual drive, it's on your hard drive.

Got a new log? If you look at the PMA thread at the top of this forum you'll see that most applications don't look for / care about errors during the finalisation stage, ImgBurn does.

Yes, the discs are the problem. As we tell everyone with DL burning issues... buy Verbatim DVD+R DL 2.4x discs (MKM-001-00 dye, Made in singapore).

You can change the size of the buffers to suit your needs. The program itself is about 24mb when first loaded.

Try burning at one of the other supported speeds.

mmalves is correct,

If you've managed to make such an image then surely you should have the software to burn it too? It might happen one day but it's very low priority because such images aren't really all that common.

Ok I've added load and save queue buttons to the bottom left of the window. Hopefully that will do!

If you add a single folder to the source box and try to 'build' it, it'll ask if that folder should represent the root folder of the disc. i.e. only the content of that folder is present in the root of the disc. If you say no then the actual folder will be present in the root. ImgBurn is meant for burning an existing disc structure... it's not flexible and I'm well aware of that, it was 'by design' at the time.

post 2 deleted. I like xcopy in a command window with verify enabled.

The brand name stamped on the media doesn't mean anything, it's the dye the disc uses that's important - and in the case above that's 'SONY16D1'. As SONY16D1 is a 16x media and your drive only list 8x, I'd say that they're not an ideal match for your burner. Try getting some 8x Verbatim or Taiyo Yuden discs instead. If that still fails (and you've tried a lense cleaner), invest in a proper external drive and ditch the slimline thing. Slimlines are nowhere near as good as the normal size drives.

You'd have to write it down using a pen and paper then I guess. Or use a camera to get a screenshot and the post that up. I only really need the last few line - one of which should include something about 'CDB' and the name of the drive it's going to (but if you only have 1 drive that's not so important).

That would be me

I would think most sata enclosures don't have any cables in them now, the connector is fixed to the PCB and the drive just slots straight onto it.

It works just fine. Are you sure you're not just confused?

Yes

Does it need to actually say 'yes' ? Down load the firmware and run it. You don't need to make any changes to your PC in order to flash the drive with newer firmware, none of us ever do. What I meant by written and double checked is that the firmware update program will send the updated firmware to the drive, the drive will confirm that it was successful and then it'll probably read it back from the drive so it can compare. If the two match ok it'll tell the drive to commit the update firmware to the chip. So if there's a problem it just won't tell the drive to commit the firmware and your drive will remain unmodified.