LIGHTNING UK!

Forget all the others, you need Verbatim 2.4x DVD+R DL media. They're the only ones that give consistently good results.

Yeah, it's that or you've got a faulty batch of discs.

I'd be very surprised if the PC that burnt / verified the disc then failed to play it! The verify stage has proved it can read it, so if it won't play, maybe the files weren't right in the first place? What software are you playing the disc with?

Don't forget, it's normal for the device buffer to empty out when the drives perform WOPC type functions. Mine do it too.... don't worry about it too much!

If the drive won't verify, it's because the burn it just made was of low quality - well, it's that or the drive is faulty. Try burning at 8x, you might find it does a better job nearer the media's proper 'rated' speed (i.e. 16x) rather than the slowest it will do. No you should not just ignore verify errors, they signify problems somewhere in your config / setup.

If it burns and verifies in the laptop, the laptop drive MUST be able to read it ok - is ImgBurn set to eject the tray between burn / verify? (If not, what I've just said may not apply!) Or perhaps when you say you burn + verify and then 'put it back into my computer', you're actually talking about a different computer?

What do you mean 'why' ?! Ok, so it does depend on the exact error message you're getting, but that's pretty much the very question the FAQ answers! Follow the FAQ and do what it says. You'll then find the problem and hopefully can eliminate it.

Looks to me as if you have a duff image (the UDF filesystem is screwed) - or it's just one ImgBurn cannot read / doesn't support. What made the image? Where did you get it from?

Verify that same disc a few times against the same image. Does the error ever change? (by that, I mean the LBA of the error and the byte values) You could have a duff cable that's causing corruption to the data stream. It could also be your memory - run memtest+ on it.

RITEKF1 discs are useless. You'd do well to get some different ones. That image is CD size anyway, how comes you're burning it to a DVD? You could also check and see if there are any firmware updates available for your drive. Finally, next time you burn something, tell ImgBurn to 'Verify' the burnt disc too - it's just a little checkbox on the main screen. If it burns and verifies ok, there's no reason for other programs to not see the data - unless the image was screwed up in the first place. Maybe Windows just isn't refreshing properly?

You need another program. UltraIso, PowerIso etc should do the trick.

Recreate the image using ImgBurn's 'Build' mode. You can't use ImgTool Classic for double layer images.

I've already done this for the next version.

This is detailed in the FAQ.

hetster, Can't you post a log of one of your burns + verify failing.

As lmao2k said, you need to find an update for your usb enclosure too. Even with decent discs, it'll be no good if you keep getting... ... type errors.

Verify should be 100% accurate, yes. If you get an error when burning + verifying a DVD image, you've got a problem somewhere.

Why on earth would you join this forum and talk about Alcohol 120%?! Your drive doesn't support those discs. A firmware update may fix that but the discs are pretty awful anyway.

The warnings in the log weren't added for fun

From what I can remember, DVD Decrypter just tried to see if the sectors could be read back, it didn't compare the contents of the freshly burnt disc to that of the image file - this is something new to ImgBurn. As it says in the log, AnyDVD can cause issues with the verfiy as it changes stuff on-the-fly. It needs to be disabled when using that function within ImgBurn. Of course what I've said above only really applies if you're getting 'miscompare' errors. If you're getting proper I/O Errors, I'll have to think of something else!

Power Calibration Errors are caused by firmware that doesn't fully support the media you're using. Look for a firmware update or use different discs that the drive does support.

Nope, none of the authors get any money from those scams. As for how to burn things, you might like to try reading the 'Guides' section. That is, after all, what it's there for! http://forum.imgburn.com/index.php?showforum=4

No you can't disable the drives buffer. It wouldn't achieve anything even if you could! The drive doesn't have direct access to the system (program) buffer so basically it would ONLY have the data being sent to it at that second to work with - at least when the drive has some data in it's cache, it has a bit of time to get over any data streaming issues. As polopony said, burnproof protects you from longer streaming interruptions anyway. It will just 'pause' the burn until the drive's internal cache ('Device Buffer') is full again, at which point it'll resume burning. There's shouldn't be any noticable pause when reading back the disc over the areas where burning was paused. ImgBurn actually has a pause button you can use during burning if you need to. I've left mine paused for ages before (during testing) and the disc still came out perfectly fine. It's very hard to log when the buffer empties and normally a buffer underrun would have occurred... ok you might think it's easy, just look at when it reaches 0% - but as I mentioned earlier, some drives do that on purpose when they're performing WOPC stuff (this is where the drive checks the quality of the burn as it goes along). What exactly do you mean by that? I try hard to never change the basics of how the program works... what are you seeing that's different? The way I see it, you need to stop whatever's messing up during your burns and causing your machine to run at 100% cpu. It doesn't matter what it is or how harmless you think it is, stop it running!

That drive doesn't support the media properly. MKM-003-00 is an 8x MID but your drive is limited to 4x. You'd be better off buying the 2.4x rated ones with the MKM-001-00 MID instead.

Only the CLI commands - which you can read about in the 'readme.txt' file that gets installed alongside the exe.