LIGHTNING UK!

Does the drive show up in device manager? Any issues with it? Does it show up in Explorer?

It's probably your drive not burning anything correctly. The discs must be coming out as if they're still blank.

Right well what I'd do here is install the latest Intel rapid storage technology driver.

Yes, there's loads of other stuff in the mds but ImgBurn doesn't use it. It's meant for tools released by the teams that created the mds spec in the first place - daemon tools / alcohol.

Right click the drive selection box and pick 'family tree'. Close the prompt that comes up and then copy and paste everything from the log window please.

It could interfere with anything it works with... so that's just DVD/ HDDVD / BD video discs. You should be fine with everything else as it won't be processing those.

Almost all of those commands are erroring out and no additional sense info is being reported. That's probably related to the controller the drive is attached to or the driver.

You can't always get a layer break position from the image itself and its loads easier to just record it in a separate file. If your image layer break position matched the mds one, yes, they'll be identical. It's just a number (lba).

There's no way around it in build mode. If you use the latest version, you could build an oversized ISO and then opt to truncate it when burning in Write mode. As you're only burning a DVD video disc,, it's trivial to shrink it down to a size that'll fit properly... that's the route I'd go.

Yes, sounds like a USB 2.0 issue. Your drive wants data faster than the system can supply it.

You're mapping a share on your nas as a drive letter (y:), the path you're mapping it to can be put straight into ImgBurn. So it might be '\\nas\media\image.iso'. I don't really know why the OS would think it has disappeared. You could run process monitor alongside ImgBurn to capture what it's doing with the file and maybe see more info around when it errors out. If clicking retry just returns the same error, can you then check the state of y: in explorer and see if it's accessible? If it is, click retry again. You could also continuously ping the nas to check it doesn't vanish when the file on it is being written to. Where are the source files coming from? Are they also on the nas?

Sorry, I've no idea. I guess the method it uses to run programs just isn't compatible.

Is the disc dirty / scratched? It looks like a simple case of your drive being unable to read it. If the disc isn't copy protected, try reading it in a different drive (after ensuring it's clean).

For whatever reason, the link to your nas (at least on the Y: drive) has an issue. It's the OS API call (that writes data to a file) that's failing with that error, I just report the failure. What happens if you do it via a UNC path?

It's on the options tab when you're in build mode.

It's nothing to do with what's in the image or how it was made. It's purely a size thing. You take the size of the file in bytes, convert it to a numbers of sectors and ask the drive to reserve a track of that size. You should update the firmware regardless of this issue. They release them to fix problems and improve burn quality.

The option to recurse subdirectories does that. It's enabled by default so if they aren't being included, you must have turned it off.

I'm not sure how you can come to that conclusion after what I've told you. The program issues the 'reserve track' command. It hangs during processing and control is not being given back to the program. That's it.

Try installing the current firmware for your Pioneer 207D drive. Yours is quite an old one. http://www.firmwarehq.com/Pioneer/BDR-207D/files.html

It's always something with the drive/firmware/ media combo. You'll have to try and get some verbatim mkm-003-00 discs.

That still looks like elbycdio to me No service pack 1 for Windows 7 either. Start the machine up in safe mode and try again After that, run memtest+ for a few passes. Either your system as a whole is playing up or your drive is.

You said it got stuck when reserving the track, so surely you know exactly where it dies? It tells you exactly what it's doing in the status bar. What was the other drive that also hung?

Which drives have you tried it with? Specific model numbers and firmware versions please. In fact, it's probably better if you just copy + paste everything from the log window at the point where the reserve track command is issued and never completes. It's definitely nothing to do with the image itself... or rather its content. The command purely sends a size (number of sectors). In theory, it would also get stuck if you used Discovery mode and set the size to the same value as the size of the image. Discovery mode just burns zeros.

Reserve track is a single command sent to the drive with the size it needs to reserve. Basically, it's foolproof from a software point of view. You must be running into a bug in the drives firmware or your system as a whole. Commands should complete successfully or error out, not just get stuck and make the program look like it has hung.

If the drive gets it into its head that 6x is the max speed, that's all you're going to get from it. The only time the trick will work is if the max speed is listed at 16x or whatever and the 'current' speed is lower. You can't make a drive (and its firmware) do something it doesn't want to do. Eject and reinsert the disc a few times. Maybe it'll work eventually.