LIGHTNING UK!

Drivers for what? I can't imagine it wouldn't be able to get itself up and running in one form or another.

Why not just get win 7 installed and then worry about drivers? You could get them on by downloading them to it directly from the Internet or via a USB stick etc. There's lots of info about adding drivers to a custom win 7 disc if you search Google.

It's 5am here in the UK. Don't expect 24/7 support! You've provide no technical details for us to do anything with. What are you actually trying to burn, just a video_ts folder or do you already have an ISO? If working with the video_ts folder, post the image information the program puts in the log window before it starts the burn. Logs are saved automatically when the program is shut down and can be accessed via the help menu when you next load it up. If a 3rd party app is calling up ImgBurn itself, it may save the log elsewhere. If the other program hasn't deleted your encoded stuff, there's nothing stopping you from adding the video_ts folder into Build mode and regenerating that info manually.

To be honest, I'd have expected yours to work just fine. Most previous LiteOn models have. I wonder if it's just an issue with your discs? Did you check the packaging to see where they were made? Failing that, get an Optiarc 5280S-CB-Plus / Robot drive. They're normally available on Amazon.

I guess the clump of pif around the middle are where your issue lies. The drive hasn't done a very good job of burning the discs. I have no personal experience of the 'F' version of that drive. It could be that it just can't overburn DVD+DL media like previous revisions could or perhaps the quality of your MKM-003-00 discs isn't what it should be. Check on the packaging and see where it says they were made.

Then you might be out of luck. Scan the disc at 4x using kprobe and post the graph + results so we can see please.

Burn at 4x.

It isn't, no.

If the option to recurse subdirectories is enabled, yes, they're included too. It's enabled by default. Yes, that browse for source folder option is the same. Advanced mode is the only way to modify what's in a folder.

Why would you manually set the LB to 64? Your disc won't burn like that. At least set it to the normal size of the first layer. Build your images correctly in the future and you won't have a problem. Things are meant to be aligned in s certain way for double layer DVD video discs.

Standard or advanced input mode? What's the root folder's name? What are the names of bits it's adding? I'm sure there's a reason for it doing what it's doing.

You drive appears to be going through the motions of burning the disc but it's then unable to read anything on it once it's finished and the tray has been cycled. If you go back into Write mode and put that burnt disc back in, does it still think the disc is empty? Try cleaning the drive with a cleaning disc and / or try with different discs.

It may not be possible. Are you building the images yourself (from the video_ts folder) or are they images (copies) of actual discs? The only time you should run into that issue is when burning an image taken from a PTP double layer disc and the layer break can't be used on an OTP blank double layer disc.

It looks like your usb adapter is timing out too quickly, hence the bus reset. Maybe try another adapter?

The layer break position is read from the .dvd file. You aren't meant to specify it manually at all... ever. Again, incorrect guides. If you don't have the correct drive, you won't get a working disc. Even if it seems to burn ok, it'll just be unreadable around the layer break position.

Not really, no. Scan the disk at 4x with kprobe and post the results.

You should revert ImgBurn to the default settings and when it says about enabling hypertuning, let it enable it. Most guides on the web about certain settings and buffer sizes etc have no clue what they're talking about.

Do remember that ImgBurn is a gui app, not a command line one. What you specify via command line just configures certain gui fields. If you're doing something that the program knows to be incorrect, it's still going to be incorrect and prompt you in the normal way. Now from what you're saying and have shown me, you're attempting to set the filesystem to UDF, but that option isn't being applied to the GUI drop down box and it's therefore left on the default one of iso9660+UDF and that's what's causing the prompt. What happens if you simplify your command line to just include the basics? Make it start in build mode and set the filesystem to UDF.

I see 2 warnings, no errors. The first one that's about setting the layer break position is normal for what you're doing / using. The second about read errors is where your drive had a problem reading the disc. The drive may have then read it successfully after ImgBurn asked it to try again or you've opted to continue anyway and ignore the error if it prompted you. Either way, it then got to the end and that's enough to complete the operation.

If it's giving you that prompt, it must not be seeing the /filesystem parameter. I'm pretty sure that parameter works fine to adjust the value in the GUI's drop down box, so break your command line down until you find out what you're doing that stops it working.

ImgBurn doesn't have to release anything. It calls the DeviceIoControl API function and sits there waiting for the OS / drive to process it and to return control. It may well be that other apps don't send the command at all. It could be that it isn't strictly required for BDR.

That error is from your OS. You may have installed drivers that block the command. ImgBurn doesn't need to see a drive as a certain something. If you tell it to do something, it'll send the command regardless.

Turn the PC off and on again.

The reserve track command only takes a single parameter and is impossible to get wrong. For whatever reason, your machine is getting stuck processing it. Boot into safe mode and see if you have the same issue. Problems like these are usually due to something in the I/o chain - a driver or whatever.

Something external to ImgBurn is crashing there. Quartz.dll to be exact. I'd be happy to try one of the files you can't convert if you email it over to the address in the About box.