LIGHTNING UK!

In a sound editing program. Audacity maybe?

Play around with the hardware read error retries option. The time taken to report a read error is down to the hardware, not ImgBurn.

It's probably the 48khz bit that's stopping it from working. 44khz is normal and that's what audio CDs are.

They must be in a format your machine can't convert. What's the format of them? Open them in mediainfo and have a look.

I'd attempt to crossflash it if I were you. That may depend on the availability of certain files though. Maybe the people on the MyCE forums will be able to help?

The LTS from Drive#1 is wrong... a bug in its firmware or whatever. I don't know why that one works and the other one doesn't though, sorry.

It's nothing to do with what you're burning (a game or whatever), your drive just errors out (reporting a 'Write Error') when it tries to burn them.

Boot into safe mode and see if the same thing happens. If it does, come back on the forum and get the error up on the screen. Either screenshot and upload it for me please or press CTRL+C to copy it to the clipboard and then CTRL+V to paste it into your reply. It's important I have it *exactly* as displayed.

Your only option is to try enabling the 'perform opc before write' option in the settings. If your drive still can't burn them, give up and order some mkm ones.

In addition to that... Don't try and use a disc that's already failed. Reset ImgBurn's settings to their default values and don't mess with them, you don't need to.

Post the log please

LTSA is Logical Track Start Address LTS is Logical Track Size LRA is Last Recorded Address To me, it's the 2nd disc that looks correct. I'd expect LTS to match the LeadOut on a single session/track disc. You are checking the discs in the same drive yeah? It could be that one just reports different LTS. You can't tweak those values. If there aren't read from the disc itself, they're generated by the drive based on something that IS recorded on it (i.e. the TOC) How big was the source ISO? Was it actually 339110 sectors and the drives have rounded up (TOC wise anyway) to 339112? In which case, that's probably why the first one works... its LTS is correct. Which drive made which burn please? It would help to have all the info. It's probably easier (and more helpful for other people) if you post the entire chunk of text from the disc info box for each disc.

2nd hand I assume? Even the 1.09 firmware for those dates back to 2008!

Registry is fine. Just export HKCU\Software\ImgBurn and import it on your new one.

You do have the latest version of virtualbox installed yeah? There isn't much you can do if it's not doing what it's supposed to. Maybe try parallels instead.

Not if you just want the English one, no.

No to all of the above I'm afraid.

The DVD writer seems to have worked fine, it's just the BD writer that's getting stuck. Are they attached to the same controller on the motherboard? Perhaps try uninstalling the controller from within Device Manager and then reboot. You could also try installing the appropriate Intel Rapid Storage Technology Driver.

It should only ever really be a drive or media issue... so yeah, I'd say there's a good chance the drive has come to the end of its useful life.

Have you tried burning at a different speed? Give 4x a go. Maybe try enabling the perform opc before write option too. Have a go at burning from within safe mode to check it still occurs on a clean / minimal boot. I dare say your drive really is having trouble burning the 2nd layer and the bogus error is actually bogus itself in this specific case. Have you opened a new spindle of discs recently? The drive must be 8+ years old, it probably needs a clean and / or is past its best anyway.

They only do anything if you actually do a full erase on the disc. I think you just got lucky with that one.

As per the ReadMe.txt file, the switch to deal with the 'root folder' prompt is: /ROOTFOLDER <YES | NO> Used to automate the 'Root Folder' prompt you get when only adding a single folder to the source list. Only applies to STANDARD input mode within BUILD mode.The switch to deal with the 'information summary' is: /NOIMAGEDETAILS Used to stop the program from displaying details about the image. Only applies to BUILD mode.The command line switches just automate the GUI and I'm afraid there's no way to filter which files get added from a given directory.

I can't see any image.

There's no special method of doing that. If there was, ImgBurn would be doing it too. 1.3x is a very random speed for your drive to settle on. Can you post the log and maybe the graph data file? It's probably just some sort of 'riplock' to make it quiet while watching DVD video discs.

You could always beta test the changes I've made and see if it works ok now?