LIGHTNING UK!

Look at the tooltip text on that button you're clicking. What makes you think you need to click that button to burn a disc?

Are you trying to read an original (and more than likely, copy protected) DVD-ROM there? If so, that's why it won't work. ImgBurn cannot copy protected discs and we cannot help with anything on the subject of circumventing that protection.

What does it say in the statusbar at this point?

Get yourself a USB 2.0 card too, you're burning with the drive constantly using the built in 'buffer underrun' (burn-proof) protection... and as the drive is now ancient, I doubt it's very good at it.

As mentioned in bold text in the pink box, please include a log where the burn / verify has failed.

That's was a lot more obvious once you told us it couldn't read originals in posts 3 and 5.

It'll happen when build mode gets a revamp.

Invest in some Taiyo Yuden / Verbatim discs and try again.

details? logs? You're not giving us much to go on!

Burn at 8x or 12x.

You shouldn't need any special to burn a disc, it just works (normally!). Can't you do a system restore from the cd/dvd that came with your laptop?

Look at your filter drivers (via the feature in the Tools menu), maybe there are some buggy ones in there. Feel free to copy + paste what's listed into your next post.

You need Verbatim DVD+R DL 2.4x (MKM-001-00 dye, made in Singapore). All other DL discs are rubbish in comparison.

At least you got an error that time. Your 'bus' should not be resetting itself (this is normally caused by a timeout in processing an I/O command). I would advise against using 'cable select'. Just set the drives up properly on master / slave and make sure you're using decent 80 wire cables. It might be an idea to forget about the DVDROM for now and just have the burner on its own channel (secondary), setup as a Master. The hdd should be on the primary channel, also setup as master.

Try and find some 2.4x Verbatims (MKM-001-00 dye) instead of the 8x (MKM-003-00 dye) ones, you might have more luck with them. Look for ones made in Singapore too if possible.

ImgBurn won't get around any protection on the discs, no. You'll need to look elsewhere for that.

It's not the image or anything else software related. It comes down to your drive / firmware / media combo.

If it's not active for 'Drive (For DVD+R media)' then it means the 'Drive (For DVD+R media) - Temporary' one will be. Changing the active setting is an option slightly lower down in the list. In any case, that should all be taken care of by the program automatically, you don't need to do anything, it's covered by the 'Auto Change Booktype' option which is enabled by default.

You can read the FAQ to sort that one out. For that one, try updating the firmware on the drive to v1.02 http://support.asus.com/download/download_...SLanguage=en-us If that doesn't work, invest in some better DL discs - i.e. Verbatim 2.4x DVD+R DL (MKM-001-00 dye, Made in Singapore).

If it moans again about the 'Data Zone Capacity Miscompare', no it's not ok to burn the disc - cancel out of it. If it doesn't moan, leave it burning. You've got a new drive and there won't be any firmware updates for it so you're stuck anyway. btw, you might find you get better burns at faster speeds on those discs - but it's going to be a case of trying them all (Speeds: 2.4x, 4x, 6x, 8x, 10x) and seeing what works best.

Those 2 numbers are the important ones. The first command is ImgBurn telling the drive to set the layer break at a give position (sector 1913760)... the second is it querying the drive to find out where the new layer break is. So long as they both match (which they do here), it means everything went just fine.

It means your drive is failing to set the layerbreak position (or at least report the new one correctly) and yet it didn't error out at all when the program told the drive about the new position. As for WHY it's failing, I have no idea, sorry! You certainly wouldn't want to burn the disc anyway, so cancel out of the burn if it happens again. What you could do now is attempt another burn but this time press F8 before you hit the 'Write' button. That'll capture all the I/O debug code in the log. Then just save it to a file and upload it (or copy + paste the text).

I've added a check within the program for this kind of thing now too. Only INDEX 00 and INDEX 01 are supported as the first ones in a TRACK. After that they must be sequential too - but that's already checked in the code.

Damn, I obviously wasn't looking hard enough at the screenshot. Here's the problem: It should be:

A blue screen can only be caused by a driver. Software apps (with no drivers) do not run at the right level to cause such things. As for formatting, you can read about why ImgBurn does what it does by searching the forum.