LIGHTNING UK!

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

If you've already got the file open then directshow shouldn't be able to stop you from writing to it... you did get there first after all! If you don't get there first, that's when you run into problems as the method you're using to open the file must agree with whatever else has it open. I didn't change how the DS filter opens the file, I simply added the FILE_SHARE_WRITE flag so that it can open files even when others have them open for read+write already. If another program has them open for read+write and that flag isn't specified (even if I only want read access), the call to CreateFile will fail.

You did verify against the image file yeah? (otherwise it just checks the disc is physically readable). It could be corruption of some sort on the bus, try a new USB cable. You could also give memtest a quick go incase it's related to memory errors - although I doubt it with that many errors in a sector.

Chances are that you can't burn at 2.4 in ImgBurn either. Put the blank disc in and look at the 'Supported Write Speed'. They're all your drive will do on that media and you can't force it to do something it doesn't want to. If you set it to a speed it doesn't support it'll just use the next one closest to it.

It's not ready yet or I'd have sent it! You really don't need to keep reminding me, honest!

That's because you're not using a blank disc. (i.e. you've tried to burn to it before and it failed.) That's because you've messed up the settings (and forced ImgBurn to use 'CD' burning mode), reset them to default.

No.

Verify it again using Verify mode and see if you get the exact same errors in the exact same locations.

Your drive doesn't support the commands used for changing the booktype. Maybe you can find a firmware for it that does? (or maybe it just does it automatically anyway?)

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!