LIGHTNING UK!

Reset ImgBurn's settings. There's no reason to change anything and half the stuff you read on the internet is complete rubbish. The program will tell you which drive settings to change (and offer to do it for you) when you're using the recommended MKM-003-00 discs. Basically, just enable the 'force hypertuning' option. The others are left alone. Burn them at 4x and you don't need the payload tool as 2.5.8.0 does it automatically.

The order comes from the names of the files. If you want them in order, you'd need to find how the playback device reads them and adjust to suite. Numbering with 001, 002 etc prefixes is the normal way of doing it.

ImgBurn always sends data to the drive as quickly as possible, so any slowdowns are from the drive itself or your system being bogged down. Lots of drives adjust the laser power as they burn and that calibration is often the reason a drive stops for a split second - which then reduces the averaged write rate.

Ok so physically burnt or not, the disc still looks blank. You'll have to try another drive if cleaning it didn't fix it.

Have you tried cleaning the drive? If it isn't working properly, replace it.

Go into Read mode, insert one of your 'burnt' (but non verifying) discs into the drive and then copy + paste everything from the info box on the right once it's been populated.

Put the disc in another drive, does it see what you burnt on it? You could try cleaning your drive with a cleaning disc.

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.