LIGHTNING UK!

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?

It only works if the ISO has been built for positioning at the exact LBA it'll end up being positioned at - i.e. all the fields in the file system must have the correct LBA offset.

That IFO file is in a VIDEO_TS folder yeah? Just drag + drop that folder to the 'Source' box in Build mode. If you have problems from there, please explain exactly what they are.

Discovery mode just burns from memory - you know that yeah? As such, it must be a hdd read speed issue then... or at least it is when you're trying to 'write' to the dvd burner at the same time. You could also try running process monitor (from sysinternals) and seeing which processes are performing file I/O on your machine. Maybe you'll spot something making a lot of drive accesses that really shouldn't be - like indexing or something.

It's kinda by design. The program is still doing stuff and will eventually return the normal error about the file being invalid or unsupported. All that's happening is that the quick image format checks have failed and so a really thorough one (testing for a sequence of known bytes within the first 80 sectors worth of data or so) will be taking place. It's slow going and I expect network file I/O latency etc makes things run even slower.

It just means the drive doesn't like the disc. If you can't get hold of another drive to try it in you'll just have to get another copy of the disc from somewhere.

ImgBurn isn't really aimed at mass duplication and I very much doubt I'll ever bother to support simultaneous burns.

burham, make your other thread please. Do not hijack other peoples.