mmalves

Have you tried burning at 8x or 6x? If that still doesn't work then you should get Verbatim 2.4x (MKM-001-00 dye) Made in Singapore DVD+R DL blanks. By the way, CloneDVD didn't report an error simply because it doesn't look for possible error at all (here's an example).

With ImgBurn in Write mode, insert the disc(s) and look at the Status field on the right: if it says Empty then the disc can be burned with another burner. If it says anything else then the disc was damaged.

The ability to open/modify ISO images has already been suggested before and The Boss isn't interested in adding that to ImgBurn. You can create bootable discs with ImgBurn (while in Build mode look in Advanced -> Bootable Disc). ImgBurn does have a portable mode and can read/save settings to a .INI file (please have a look in ImgBurn's Read Me).

Your drive produced a bad burn. Try again with a new blank disc. If it doesn't work, try with better media, such as Verbatim and Taiyo Yuden.

ImgBurn already has a portable mode by using /PORTABLE in the command line, so I don't see any advantage is using ThinApp.

Yep, it's a nvidia chipset. Their drivers are buggy and, for the moment, a known workaround is to switch the Interface to ASPI in ImgBurn's settings (I/O tab).

Please post the log from that burn (you can find it at Help menu -> ImgBurn Logs).

No one knows for sure the root cause of this problem so all you can do is try some workarounds to get it working again.

Please read this bit again: I'm sorry but we can't help you copy your protected discs. If you somehow manage to copy them (Google is your friend) and have trouble burning them then we may be able to help you

donta go easy on the

I'm sorry but this isn't related to ImgBurn nor burning so we can't help you

There's nothing much you can do. Make sure you have the latest drivers for your motherboard's chipset. Search the forum for "semaphore timeout" and you'll see other suggestions that may or may not work

Please post the log from the failed burn (you can find it at Help menu -> ImgBurn Logs).

I think your burner is giving up: at the time of burning, it didn't correctly identify the media and possibly used a generic write strategy that didn't work well, resulting in a bad burn. You can see that, at the time of verifying the disc, the burner correctly identified the media (notice the available write speeds). Burners are pretty cheap nowadays so you might want to get a new one

I'm glad I could help

DVD+R DL is better supported by burners and reader devices alike, not to mention it's superior to DVD-R DL. For example, you can't change the layerbreak position on the DVD-R DL standard, and this is needed for DVD-Video/console games/navigation discs/etc. Since less people use DVD-R DL, the manufacturers don't tweak much their burners' firmwares for this type of media, and, in the end, you get low quality burns on this media, if they burn at all.

Please update to the latest ImgBurn version

If it burned and verified ok then the disc was properly burned. It may be that your console is having problems reading that disc, so please read this: http://forum.imgburn.com/index.php?showtopic=8000

Try burning at 8x or 12x for a possibly better burn. You might also want to try firmware 1.05 for your burner (remove any disc and close the tray before flashing and reboot after it has finished).

What's the brand, model and firmware version of your burner?

I don't mean to be rude, but how is this related to ImgBurn? DVD Flick only uses ImgBurn to burn the converted DVD, so I think you'd get better answers if you posted at DVD Flick's forum.

There's firmware 1.09 in the page I've linked to

There's also firmware MS0R available for your burner. Remove any disc and close the tray before updating. Reboot after it has finished. Also, in the future, please don't hijack other people's thread, as this only makes it more difficult to help everyone.

You're right, TSSTcorp drives are Samsung. ImgBurn already booktypes +R media to DVD-ROM on Samsung drives (provided that the drive supports booktyping) so you don't need to worry about it

Install Ner0 ASPI (available at ImgBurn's Download page) and switch the interface to ASPI in ImgBurn's settings (I/O tab). That should work for now. As for that Disc ID, that's common for DVD-R media and isn't a problem. What's important is that the drive recognized the media (RITEKF1) and shows available write speeds for it (4x, 8x, 16x in your case).