LIGHTNING UK!

Did you burn and verify? Please post a log once you've done that.

Firmware is for the drive and the OS has nothing to do with anything. Stick 1034 on.

No idea but I can tell you that setting it to TAO and burning a DVD will do nothing different to having it on DAO/SAO. If you look at the log you should even see that it still says DAO.

That's clever when TAO doesn't apply to DVD and Imgburn will ignore the setting and use DAO/SAO anyway.

Update your firmware, 1.0f is out now.

Do not put optical drives on 'RAID' enabled controllers. If you really, really, really have to, make sure the drivers for the controller are up-to-date. Which controller is your drive connected to? And by that I mean who makes it? Intel, Nvidia, Silicon Image, JMicron etc?

You need different discs, your writer just doesn't support those at all. (It's too old and the MID isn't in the firmware)

Yeah I did look at it and although I didn't get the error you mentioned, I did notice that it had the same problem with the info in its header that another file I'd just looked at had - basically where the file says it's bigger than it actually is. I'm not sure if that's exactly what was causing the issue on your machine but a fix/workaround had already been put in place for such files.

No idea then, sorry. ImgBurn is working just fine given the info the drive is reporting. Try it with DVD+R Reserve Track turned on. (It's only 1 more disc, right?! ) I assume you have tried installing the latest chipset drivers from the intel site? And if your controller is set to AHCI or RAID mode in the bios, make sure you install the latest Intel Matrix drivers off that site too.

They're about

Ask on an xbox forum, this one is for ImgBurn and not really the best place for you to get the answers you seek.

Tayio Yuden DVD-R 8x (TYG02 dye) is it then. Your drive only appears to support 8x anyway so firmware support for 8x discs might be better than 16x ones.

I was asking for a log from the burn of a decent disc rather than just a log in general... yes the thing in your first post was a log Hopefully the firmware update will help you this time but your drive is still old and these things don't last forever. Not only that, the world of technology changes at a very fast pace. You've got a Model T Ford there where most people are now driving BMW M3's

Try using the incremental write type, ImgBurn itself works fine on x64. Your drive/system is the thing saying it's still busy burning (assuming the debug info in the log extract below kept scrolling in the window)

Yeah I'd give some Verbatim DVD+R 8x or Taiyo Yuden DVD-R 8x a shot.

If you can't find a firmware update for it and you aren't willing to try some (or show us a log if you already have?) decent media (Verbatim / Taiyo Yuden) then you're out of luck.

The file shouldn't have anything to do with it, the drive doesn't care what you're burning... it's all just 'data'.

Is that your first/only failure? If so, just ignore it, it was probably a fluke bad disc or something.

That's normally because I think they're rubbish and only benefit the person making it in the first place.

If you're not using Verbatim 2.4x DVD+R DL (MKM-001-00 dye and and in Singapore), forget about it. http://forum.imgburn.com/index.php?showtopic=8000

It's entirely up to you. Maybe you can pickup a cheap cleaning disc on ebay or something - and you can use them several times so it might be handy anyway, even if you do end up getting a new drive.

With a cd/dvd cleaning disc. You can buy them in most electrical shops. The only problem is, you can pay

Did you try all 3 of the things under the 'Close' option? Do them one after the other starting at the top ('Track' I believe).

Please write in proper English, save that other crap for your homies. If a drive supports double layer at all then it's most likely to support the very discs you're already using because they've been around for the longest time and are by far the best. As such, I feel your drive is to blame. Try cleaning it or get yourself a new one - yours is probably faulty.

Switch to Build mode and try again. Write mode is just for (disc) Image files.