LIGHTNING UK!

Yes, drives get worse with time. Nothing lasts forever Running a cleaning disc on the drive might help it live a little bit longer. The default write type in ImgBurn is SAO/DAO. It's the most capable. I only mentioned TAO because it might get you going again.

Ok, I didn't really want to see the graph file, I just wanted you to look at it and see which filters were being pulled in. Anyway, I can see it goes... Source -> MPEG-I Stream Splitter -> Arcsoft Audio Decoder HD -> Default DirectSound Device From that I can only assume the Acrsoft Audio Decoder HD filter is causing the problem. Use 'DirectShow Filter Manager' to change the 'Merit' on that filter to a lower level - so a different filter gets pulled in instead - and hopefully that one will work. http://www.softella.com/dsfm/index.en.htm

Verify your burns too, especially if you know you're having problems!

Go for 8x discs if that's all the drive can handle. Personally I'd go for Taiyo Yuden 8x (TYG02 dye) if you want DVD-R. I think the TY DVD-R discs are better than the Verbatim ones (assuming the verbs aren't TY dye anyway!). The opposite is true for DVD+R discs though where I then prefer Verbatims to Taiyo Yuden

The built-in burner might be using the TAO write type. Your best chance of success is to use Taiyo Yuden CD's. They're by far the best.

Yes, the specific audio track file that isn't decoding nicely.

Have you tried burning at each of the available speeds? Have you tried cleaning your drive?

That file isn't used in Vista I don't think, it uses some other filter / DMO. Load the problem file in GraphEdit and see what gets added to the graph.

I've no interest in this, sorry.

Ah now that's a very good point, it's at byte offset 1094 within that sectors but it doesn't show the relative sector number within the file! As such you have to work it out based on the start LBA of that file. i.e. ((93539 - start of file LBA) * 2048) + 1094 = total offset within file. It's easier to just open the iso / disc in IsoBuster and view that sector. You can also use ImgBurn but the ISO would need to be mounted in a virtual drive because ImgBurn can only display sectors on a drive.

Where's a log of the failed burn?!

It doesn't matter about the box but obviously it's need to be inside the warranty period - I don't know what that is off the top of my head. Yes but it'll probably cost you 50% of a new drive to send it to them so you might as well just buy a new one and save yourself the effort.

1. Are you perhaps in 'Write' mode when you should be in 'Build' mode? 2. ImgBurn doesn't support multisession - hence you cannot add to a disc.

I do not recommend changing the LB thing as it messes it up for everything else. Let the .DVD/.MDS file take care of forcing a certain LB position. 1x write speed is total rubbish. You can't burn DVD+R DL (or any DVD+ format disc for that matter) at anything less than 2.4x. Burn at whatever speed your drive produces the best quality burns at. There's no rule saying 2.4x will be the best. Every drive / firmware / media combo will produce different results.

Log file?

RMA the drive.

Your drive says it can't write to the discs you're using. Try this... http://forum.imgburn.com/index.php?showtopic=8000

Tell it to make an ISO of the files and terminate the process if/when it gets stuck. Then you could just mount the ISO and use something like Beyond compare to see which files match up and which don't. Feel free to PM me a debug enabled log or perhaps it's best we go the email route.

The image would already be in that format if it was required - so basically just burn it.

Do you have the latest chipset and controller drivers installed for your motherboard (i.e. Intel or nvidia) ? Have you tried running memtest for a couple of hours? Have you tried looking at that specific sector on the disc / within the image file to see which of those two values is actually the correct one? (i.e. 0xD1 or 0xF1)

None.

What sort of failures are you actually getting? Where's the log?

http://forum.imgburn.com/index.php?showtopic=8000

http://forum.imgburn.com/index.php?showtopic=8000

Put it back on DAO/SAO for the Write Type, does that then work?