LIGHTNING UK!

Why have you turned smartburn off? Enable it again. Burn quality has nothing to do with the OS so don't waste your time dropping back to safe mode.

Exactly how you did it last time, but change the 'Output' to 'Image File' in the menu at the top. Or you could select 'create image file from files/folders' on the initial screen.

Build an image rather than writing to disc directly. Burn that image and hope it verifies ok. Once you've done that, go into Verify mode and verify it manually a couple more times. If you get random miscompare errors in various sectors, you may have a memory issue - run memtest or similar.

That was your drive's decision. I don't know why it decided to do it, it just did. It was told to burn at 14x but 14x isn't a supported speed for your drive/firmware/media combo. The drive chose to use 12x instead (hence the log entry)... but even then it must have changed its mind and just stuck to 6x

Please post the log - as per the pink box up the top

Like I said, ImgBurn defaults to picking the right file type for the disc you've inserted when it automatically generates the destination file name. Just let it do its thing. If you really must mess around with it, use BIN for CDs and ISO for everything else. You can't really go wrong with that. 'All Files' just makes the box display all file types... not just those with the selected file extension (be it .bin, .img, .iso etc). It isn't an actual file type itself.

Yes

Like I said, it's just a file extension. You could name the file 'image.toliet' if you so wish. The point being, DVDs only have 2048 bytes per sector. That's all it's ever going to end up as in an image file... no matter which file extension you give it. For CDs, you can tell a drive to return 2352 bytes per sector or to return 2048 bytes per sector (assuming you're reading a track that supports it - i.e. Mode 1 or Mode 2/Form 1). Single session/track Mode 1 CDs are fine to be saved as 2048 bytes per sector ISO images. For all other CDs, you should use the BIN+CUE format. The program does this stuff automatically so just let it do its job and don't worry about it.

It's what you see in explorer when you put a disc in.

You don't need to keep making new threads, unless you're trying to take over the entire first page of the forum of course The two fields are for data and audio. So data tracks are read at whatever speed you select in the first drop down box and audio tracks are read at whatever speed you select in the second one.

You'd use BIN+CUE for CD and ISO for every other format. IMG isn't really a format, it's just a file extension. In reality, it's probably just an ISO (2048 bytes per sector) or BIN file (2352 bytes per sector).

Yes.

Nope, CD only. DVDs only support 2048 byte sectors and CD-DA is 2352 bytes.

Not with ImgBurn, no.

Maybe they don't? Maybe they don't compare the data at all? Or if they really want to compare CD-DA sectors, maybe they take a best guess at the offsets by comparing what's coming from the image and what's coming from the drive and try to match a certain number of bytes to find out when they're in sync... I've no idea. I just know that when you write a sectors worth of CD-DA to a given sector and then read it back again, what you get back is normally different.

You do realise that the payload tool appearing to support your drive and your drive actually being able to support overburning are 2 very different things yeah? I very much doubt your drive supports overburning DVD+R DL discs, and even if it did, I doubt it would do it on a cheapo CMC ones. They tell you to use Verbatim MKM-001-00 or MKM-003-00 for a reason. Feel free to mess around with the drive's advanced settings in the hope that some combination of them will produce a working disc. My advice... buy the recommended hardware/media. I only went back as far as the DH20* series of drives, but they didn't work. http://forum.imgburn.com/index.php?/topic/21033-various-drives-burnermax-payload-mkm-003-00/

Post the log please - as per the pink box up the top.

I really can't do anything with this. I'd go to the trouble of locating and buying that specific model drive but I know it would end up working just fine for me and be a waste of time and money. Searching the forum, I found 2 other threads (from 2010) where people were using GH22NS50 drives (very similar to yours internally I expect) and both had miscompare errors pop up (starting) at sector 7168. You can see from my own tests with the GH22NS50 drive (in the 'Drives' forum) that I didn't have that problem with it. If you want to spend some time looking into the issue you're having, I'd start by trying the drive with other discs... CDs, DVD-RW / DVD+RW etc. and see if the problem persists. Then try it in another PC and try another drive in your PC - see if the problem follows it or goes away. I don't know which SATA controller you've got the drive attached to at the moment, but if you have more than one on your motherboard, try it on the other one.

Am I to assume the burnt discs don't actually work? Your drive appears to be producing discs that aren't quite right. Without trying them in other drives etc, it's impossible to say if the discs are 100% useless or it's just your burner that's having trouble reading them back. I'd probably start by buying some decent Taiyo Yuden CDs and giving those a shot. If you're still getting the same problem, try cleaning the drive with a cleaning disc. If it still doesn't work, you can probably just write your drive off as being faulty.

I'm not 'shipping' it with anything. The installer just uses OpenCandy to provide program offers, I don't have the ability, time or desire to go through everything in their library. If you have a problem with something OpenCandy is offering, you need to talk to them about it - or better still, go direct to whoever made what you've installed. I'm too far removed from the equation to have anything to do with any of it.

It would be quicker to just google it. I'm sure something will come up or another program will support removing it.

Is there nothing in the normal 'programs and features' section within control panel? Beyond that, I have no idea, sorry. The opencandy team are supposed to vet the programs for that kind of thing.

You appear to have also enabled OPC... you shouldn't need it. Try and get some MKM-003-00 discs. If you can't burn those either (with the same settings - apart from turning off 'Overspeed'), buy a new drive.

That log shows it's detecting miscompares in 32 sectors... which just happens to be the number the program reads in one go (2 ECC blocks). Obviously there's nothing wrong with the ones before or after and when you run the standalone verify function straight after (which you're saying is fine), it's running the exact same code again. There is no 'bug' here, it's just that the sequence of commands is showing an anomaly with your system/drive. So I can't explain it, but your system/drive is messing up and returning invalid data to the program. It can only work with what it's given. Try going into the Settings, I/O tab, Page 2 and change the I/O Transfer Length to 'Manual' and make sure it's set on 32 KiB. I wonder if you'll then just have 16 sectors that miscompare, it'll remain being the same 32 sectors or if it'll be totally fine.

Clear the drive's OPC history and burn them at 4x.