LIGHTNING UK!

At least that one verified ok, but the scan is still bad. Not sure why it's bad over quite an area around the layer break position. You can't even really just put that down to the fact you're over burning. Perhaps try another one having turned off 'force hypertuning'. If that's the same, do another one with force hypertuning enabled and online hypertuning enabled too.

and have you tried clearing the drive's OPC history and burning another disc? After that, it's a case of cleaning the drive with a cleaning disc and/or trying discs from another spindle of Verbatim MKM-003-00.

Try clearing the drive's OPC history and give it another go. Also, please right click the drive selection box and pick 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the Log window. Thank you.

And that's with a different drive too?! Are they the new discs? Where were they made? Can you post the log from that burn / verify session please?

Tools -> Settings -> Write -> Page 2 -> Overburning -> Don't Prompt Optimal Settings

Can you screenshot that error please and post it for me to look at?

Yes but why not install win 7 from the basic disc and then add drivers via a USB stick later on? If the machine is too old / weird for win 7 to provide basic support (and by that I mean install successfully) for it out of the box, it probably shouldn't have win 7 installed on it anyway. The only time I've ever had an issue with installing an OS is where it didn't have built in drivers for a scsi card and that was running the only HDD the machine had in it. So basically, no scsi driver = no HDD = nowhere to install the OS to.

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.