LIGHTNING UK!

It doesn't look like that disc was burnt with ImgBurn. Actually, that doesn't look like a DVD video disc at all. Have you muddled them up somehow?! Do you have the log of the burn + verify operations?

Put the disc in and see if ImgBurn can read the cdtext back ok. Use the media info button when you're in read mode.

If you simply compare (hex type / byte level comparison) the files on your hdd to the ones on the disc, you'll see they're the same. That's why I can say it's nothing to do with the burning stage.

It burns exactly what you give it, so the issue is nothing to do with burning itself. You'll need to look elsewhere for the cause of the problem I'm afraid.

Post the log please.

Try at 8x rather than max and / or try some different discs.

Yeah there's nothing wrong with that burn.

If what you're doing doesn't work, it probably isn't possible.

You save the image as a png or whatever file and then attach it in your post.

Any current LiteOn model should do the trick. It'll probably end up being an iHAS124 / 324 revision E / F. I haven't tested the F revision personally, but I have tested the E and know it overburns just fine. And when I say 'overburns', I mean it can burn up to the extended capacity allowed by the burnermax payload.

Get a second drive and share the load between them. With regards to the drive just stopping burning, like I said, it could be the drive has just had enough and is now a bit temperamental. So if you get another drive, see if that also gets stuck randomly during burns. If it does, it must be your system as a whole. 4x is always what I've used in testing overburning on MKM-003-00 with the LiteOn drives.

It appears your drive just stopped burning or the system stopped processing I/O. Like you, ImgBurn is simply having to wait for other stuff to happen. That's why the rate decreases to zero and the remaining time goes to Unknown. Btw, 1x isn't possible (it would burn at 2.4x anyway) and 4x is the recommended burn speed for the mkm-003-00 discs. Looking at your log, your drive has burnt a lot of discs. It could be giving up the ghost or it could be a system issue. It's impossible for me to say.

The graph is easier to read than the text. Can you screenshot that please? That said, the max values look fine. So then like I said, it's down to the source image being correct and your playback device being able to play the disc correctly.

Well, burn and verify a disc so I can see that's all 100% OK. Then scan the disc at 4x using kprobe so I can see the burn quality. If they both check out ok, there's nothing more for us to do.

Chances are, the VMware driver isn't passing through the command. They need to allow unfiltered access to drive but many only pass through commands they understand... Not 'vendor unique' ones used for stuff like changing the book type settings. ImgBurn doesn't care that the name has been changed. If you're on the lg tab, it'll be sending lg commands.

Ideally I'd have liked to see the log from the verify operation too. If it burns, verifies and the kprobe scan looks ok, there's no reason for it not to work. The issue must then lie with the source image or the playback device. Your settings are fine.

Ok, so it burnt that time.

You're confusing queue files and cue files. Just load the cue in Write mode as if it were an image file. I.e. Load it via the 'source' box.

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.