LIGHTNING UK!

If your drive is failing to burn various different disc MIDs, it's probably the drive at fault.

It's something to do with your Samsung DVD-rom drive. As the log gets as far as showing the device Id and the next line should be about the drive letter, I guess the message in the status bar is something along those lines? ('Getting drive letter...') Which controller is your samsung dvd rom drive on?

cda files don't really exist, they're just something windows displays to the end user. To burn music files in Audio CD format, follow this guide... http://forum.imgburn.com/index.php?/topic/5555-how-to-write-an-audio-cd-from-music-files-using-imgburn/

If it's showing a % and that % hasn't changed in a long time, your drive must have given up/got stuck. ImgBurn isn't actually doing anything other than querying the drive each second to see if it's still busy formatting and if so, how far it's got. I'd probably reboot and try again if I were you. Can I get you to post the 'family tree' info for your drive please? Right click the drive selection box when you're in Write mode and click 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the Log window. Thanks.

Sometimes opencandy can offer 2 things, you must have missed the opt-out option for one of them.

You had the option to opt out of installing whatever opencandy offered you, you just didn't.

Ok, I'm sure you know a lot more about this stuff than I do. *sigh*

Do you have any idea what you installed? I have no idea what you were offered and didn't opt-out of. I can't see that anything would survive a format and reinstall of Windows... maybe your problem lies elsewhere?

Not that ImgBurn supports reading it from, no. You can embed the CUE in a FLAC though...so if you're looking to tidy things up on your hdd and only have a single file (I guess that's where you're coming from with this question yeah?), that's one way to do it.

I don't mean that kind of overburning. All drives will fail to do that on DVD+R DL media. I'm talking about the ones that can make a disc look bigger than it usually is and therefore burn oversized amounts of data without any overburn/truncate prompt.

Autorun.inf would be a good start.

Make an autorun.inf file (find the syntax of the file via Google search) and burn it to the disc alongside the exe using Build mode (write files/folders to disc).

If your drive just keeps erroring out with a 'write error' when you try and burn those 'CMC' MID discs, invest in some other / better ones. That image could actually go on a CD if you have any of those lying around.

Look at the media documentation for your drive - I.e. Over at the LG website. The only ones I've seen that did 16x were some with a 'sony' MID.

The speeds are down to the drive, firmware and media combo. ImgBurn has no say in the matter. Decent discs are often supported at speeds beyond what's specified on the packaging, but that varies from drive to drive.

It really doesn't matter what else I use within the installer, people always complain. I went through the exact same thing when I bundled the Ask.com toolbar 3 or so years ago. I'm forever being asked to install toolbars, browsers and any number of other programs by various bits of software I install or update (Java, most Adobe freeware etc) but I don't care because it takes 2 seconds to opt out and then I can use said software an unlimited number of times without ever seeing another advert/offer. It's a small price to pay. The whole world revolves around the 'small print', people should be more than used to it by now. If you feel you want to stop using ImgBurn on principle, that's your loss and I hope you manage to find a similar piece of software that's 100% free of offers/adverts in its installer.

AWS means the AWS feature is active. http://forum.imgburn.com/index.php?/topic/4249-how-to-use-the-automatic-write-speed-aws-feature-in-imgburn/ What does the box say that's popping up? If you cancel out of it, you should still have extra bits in the log that'll help me see what's going on.

Update 1... The ISO burnt and verified fine with an LG BH12LS38 FW:1.02-D0 on a Verbatim BD-RE. It played perfectly (I tried every chapter) in a Sony BDP-S570 and Sony PS3. It also played in PowerDVD 11 and TMT 5 on the PC. Update 2... The BDMV folder burnt and verified fine with an LG BH12LS38 FW:1.02-D0 on a Verbatim BD-RE. It played perfectly (I tried every chapter) in a Sony BDP-S570 and Sony PS3. It also played in PowerDVD 11 and TMT 5 on the PC.

You went from one extreme to the other with that one... 2x to 'Max' (12x). Try something in the middle - especially if you're saying they're rated for 6x burning. Oh and don't forget about the firmware update I mentioned. Don't cut off the verify section of the log either please. The results of that are important.

If the last version to work correctly for burning BD Video discs was 2.5.1.0, you'd surely find tons of similar threads here on the forum... and obviously that's not the case at all. The code that does the actual burning hasn't really changed between that version and the current one. If you logged every single I/O command from each version, you'd see they're identical - there's very little scope for change with these things! I don't like to dismiss reports like yours though so what I'll do now is burn a BD25 ISO (with a file system created by something else) to a BD-RE and test it in my Sony standalone and also my PS3 - sorry but they're all I have available. I'll then do the same with a BDMV folder (so ImgBurn is actually building the file system) and report back when I'm done. There's no doubt in my mind that both will work just fine. btw, you should update the firmware on your drive. http://www.firmwarehq.com/Pioneer/BDR-205/files.html

'Create image file from disc' is a shortcut to 'Read' mode, nothing more, nothing less. Those buttons are meant to dumb the program down for new users. Ok so you ended up with an image of the disc on your hdd. Congrats. Maybe it was a double layer disc and that's why you ended up with what I guess was an MDS file. The MDS file is a little info file that contains extra info about the source disc - namely, the original layer break position. When an MDS (or .DVD) file is present, that's the file you're supposed to select when you want to burn the image back to a new DVD. If you instead select the ISO file itself, the program will try to educate you - which is what you ended up seeing. You didn't know what you were doing and so panicked and closed it down rather than just going ahead and burning - which I'm sure would have worked just fine. I can't comment on your machine hanging, obviously there's something wrong with it somewhere. ImgBurn is a single exe file. If it isn't running (and that's something you'd have to do yourself, it doesn't autostart or anything), it has no effect on your PC - so thinking that uninstalling it was a magic fix is just plain wrong.

Mount that ISO in a virtual drive program (or extract it with any number of compression programs - WinRAR, 7zip etc) and then use Build mode to create a new ISO from the VIDEO_TS folder. The one you've got there can't be burnt to a DL disc nicely with a proper layer break position.

Your log shows you trying to burn to 'LGEBRA-S06-000' media twice. The only 'LG' discs I've had any experience with were rubbish... perhaps try some others? Anyway... one burn appears successful (no warnings/errors recorded) and the other failed right at the start. You didn't verify the one that worked so we've no way of knowing if the burnt disc was actually readable. 2x may not be the best speed for your drive/firmware/media combo and faster speeds may produce better results. There's a firmware update available for your drive too. http://www.firmwarehq.com/LG/WH12LS38/files.html

Both really. Only certain drives can overburn DL discs and Verbatim DL are the best for overburning.

Without trying the media in another drive, you can't really rule out the drive as being the issue. Drives/firmware often prefer certain discs over others. Have you looked into cross flashing it to a LiteOn and using the latest firmware for the LiteOn model? It may fix the issue. Of course that doesn't really make sense if it's burnt 'VERBAT-IMd-000' perfectly fine in the past. Did you get a new spindle of discs? Are you sure they're the same MID (i.e. 'VERBAT-IMd-000') as before? Crossflash to a Liteon, keep the drive for scanning and invest in a new Pioneer drive or something.