LIGHTNING UK!

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?

It looks like something's preventing that device from being 'opened'. Another bit of software that's already locked it perhaps? It should just fail though if everything about the OS is working as it should be. What's the exact message in the status bar at that point?

Sorry, I'd assumed you were using a standalone DVD/HDD recorder device for putting your VHS onto disc. Is that not the case? Basically, I have no clue what you're actually doing. You asked if there was a problem going between media types... there isn't. If you create an image file by reading one disc, you can burn it to any other disc it'll fit on. (*assuming sector mode is the same - so maybe not CD -> DVD/BD) If your discs are unreadable / skipping, try using better discs / better drive / burning at a different speed. Whatever you're using for your VHS -> DVD conversion is nothing to do with ImgBurn. I have to assume your program has created/authored a valid set of files. You've said you aren't using Build mode, so ImgBurn hasn't created the file system on the initial disc or ISO. The more info you provide (background info, log files etc), the easier it is for us to help you.

If they verified ok, they're fine... at least according to the drive that burnt them. When a drive struggles to read the disc, they tend to jump around a bit and/or be unable to fast forward/skip/search in the player. If you're recording VHS directly to disc, I wouldn't mess around too much after it says it has run out of space. That extra info needs to also be recorded on the disc somewhere. Does your device not have a HDD in it that you can use as a 'staging' area? My dad has one and he records to the hdd, does his editing, menus, chapters etc. and then burns it to disc.

Pretty much the only things you could try are enabling the 'Perform OPC Before Write' option in the Settings and just fully formatting the disc a few more times. Maybe it'll sort itself out. After that, it's a case of trying different discs or a different drive.

The volume label is nothing to do with the file name. It's built into the file system and that'll be from your DVD recorder by the sounds of it. I'm sure your DVD recorder would be smart enough to handle the disc running out of space. There's an option in the tools menu that'll let you edit the volume label in an image file.

It'll be in the settings under the build tab.

I found a bin and cue one before I found your one. That should work.