LIGHTNING UK!

Normally its on discs that have audio tracks etc. If it's just a new (DVD) image you're trying to burn then chances are it's not multitrack at all and it's just a v2 mds file which ImgBurn doesn't support and throws up a bogus error message about it being multitrack. ImgBurn will not support v2 mds files because the DT people won't provide the specs.

copy + paste the text from the disc info box on the main screen please. That said , just click 'ignore' / 'continue' to the error and it'll probably continue on its merry way.

Drive needs cleaning? Drive on its way out? Bad spindle of discs?

You don't need anything other than 'Build'.

Writing isn't the same as reading, maybe your drive is on its way out?

I've just never bothered to add support for it. ImgBurn's support for MDS files goes so far as it needs it to - and as it only makes then for DVDs there's never been any real point in supporting more than single session/track ones. The flle must have been made with DT or Alcohol in the first place so why not burn with that too?

Nope, they're encrypted / compressed now and the DT people won't part with the info. It's kinda pointless anyway as you'd only use DT for protected discs you can't really burn those kinds of images - especially not when ImgBurn doesn't support RAW mode for burning.

I think that's just because it's a little slow at actually setting the LB. If you check the disc info after the burn I'm sure the layer break will be in the correct place. You shouldn't have aborted the burn though. The bit in bold (Disc Control Blocks) is info about the drive that burnt the disc - or in this case (because it's empty), what will be written to the disc when this drive burns it. No need to provide debug info unless I ask for it.

Please remember that ImgBurn is a burning tool.

Have you installed the latest nforce drivers from NVIDIA's site?

I'm not sure I see what you're getting at here? If you want to burn that lot to a disc then you'd just add the '[some random folder path]\MY_DVD' folder to the 'Source' box and then burn.

It might be a new v2 MDS file (that error can be bogus in any version up to and including v2.4.2.0).... ImgBurn doesn't support them, sorry.

What items are listed in device manager under those two branches I mentioned?

There isn't really much I can say! The drive is failing to burn to the discs you're using so the obvious thing is to stop using them and try something different. If the others (which should be Verbatim ones) don't work either then you'll know it's a problem with the drive... try running a cleaning disc on it a couple of time. If that doesn't work, buy yourself a new burner.

There isn't a setting that can cause it. Follow the cable from the back of the drive down to the motherboard, then see which port it goes into and look it up in the motherboard manual. Failing that, look in device manager under the IDE controllers branch and/or the SCSI one.

There's no magical fix for these errors. The drive generates them based on realtime problems between the drive / firmware / media combo. If the 3 aren't playing nicely together it'll throw up an error which ImgBurn then reports. Firmware updates are the first things to check for, then check you're using decent media (you are), then try cleaning the drive, then throw the drive in the bin. Happy shopping!

Have you tried with Verbatim / Taiyo Yuden media? Have you tried burning at 8x or 12x? What controller is the drive on? It's not normal for the drivers to report 'Fibre' for the Bus Type.

It really just comes down to bugs in powerdvd or issues with the source files - neither of which ImgBurn can help with.

Who knows. ImgBurn is only a tiny part of what it takes to burn a disc successfully. It relies upon good comms to the drive and the success / failure of a burn (burn quality) comes down to the drive / media / firmware. If your system works well, so will ImgBurn.

The layer break error is probably because you're reusing a disc that's already failed to burn for one reason or another. You should not get that specific error on a new disc. You already know the score with Verbatim DL so I won't mention it again.

It'll be waiting for some I/O to complete - during this time ImgBurn is not in control, your OS is. Update your motherboard chipset/controller drives, remove any dodgy fiter drivers. Update motherboard bios, drive firmware.

Do you know anything about the PC it's in? Is the PC 8 years old too? If not and it's just the drive, I need to know which chipset the motherboard uses - i.e. Intel, Via, SIS, NVIDIA etc. If you know the make and model of the motherboard I can probably work the rest out for myself.

Burning at 10x is a different problem. Lots of drives read at different speeds depending on the media you're using - so it's unfair to blame that on the port in use. A 16x burn should reach (at best) 16x no matter which controller it's connected to (usb and firewire being the exception).

Do all the things I mentioned to the original poster. Oh and you should really create your own topic if you have a problem. It's unfair to hijack someone elses when you're asking for help rather than just saying something like 'I did this and this and this and it worked!'.

So you get the same 'Unrecovered Read Error' error on MKM-001-00 discs? Have you tried cleaning the drive? It must be creating a disc with high errors rates and that's what's stopping it from being able to read back the 2nd layer. If cleaning doesn't work, invest in a new drive.