LIGHTNING UK!

It doesn't look like that drive should have a problem burning DVDs. What message is displayed in the status bar when you put a blank dvd in and switch to Write mode?

I doubt it's anything to do with the burning process itself. The files you provide the program with are what gets burnt. You can compare them yourself (MD5 / SHA-1 etc) and you'll see nothing has been changed. Maybe the player ignores HDR when playing from BD-R? Check with whoever makes it. Lots of them have weird limitations when using certain types of media.

Copy and paste everything from the Log window please.

That should not be the case. There’s nothing in the program to be aware of any other instances. Perhaps check the log file when it closes and see if anything gets mentioned. Are you actually enabling any sort of option to make the program close when it has finished anyway? If you are, stop doing so. If not, perhaps something else is actually terminating it.

You said you were burning multiple copies of the same, so I tailored my response accordingly. You can burn what you like, as many times as you’d like. The program will only be closing when it thinks it has finished all the work you’ve given it - assuming you’ve also told it to close when done.

You’d just tell both instances to burn the same image to a different drive multiple times. Sounds like you had 1 instance burning a single copy to one drive and another instance burning multiple copies to the other drive.

Put a new blank disc in and then try to burn. The disc you put in is not empty. The disc info shown on the right says as much. The ‘unknown’ bits are meant to be there. You haven’t selected an image file or anything to burn.

That’s the /noimagedetails command if I remember correctly. Take a look in the readme txt file.

That’s not bytes, it’s sectors - and that’s all the disc has on it. The issue would be with burnplot, it was made before TL discs existed.

So the IMG was 0 bytes in size? That goes along with what's displayed in your screenshot. I don't suppose it'll work unless you have a file that's the size of what's to actually be burnt.

It could just be a CCD that it doesn't like very much. CCD is CloneCD's native file format. My implementation is just a 'best guess' at it. What does the accompanying IMG file look like? Size in bytes etc. Feel free to upload the CCD so I can take a look at it.

You may need RAW mode writing for that... which ImgBurn doesn't support. The image is / was meant for Padus DiscJuggler, but they've shut down, so you probably can't get it now - not legitimately anyway.

ImgBurn won't be shifting anything, so the issue lies elsewhere. Stick to using the special software.

How are you even telling it to start the verify process? I don’t recall giving the user an option to speed things up. It cycles the tray and then proceeds once the drive thinks it’s ready again. If you have to push the tray in manually, it would just wait longer.

I'm pretty sure it's just based on the name of the disc. You might be able to force a name and the program will then try to make it unique (add a '(1)', '(2)' etc to it), but don't quote me on that! There's definitely no support for grabbing names from a CSV or whatever.

The first error is the one you need to focus on. So, your drive is reporting a 'Write Error'. Which other drives have you tested?

If the inserted media doesn't appear to be rewritable (or cannot be determined), you're given the option to override. So the user probably just selected DVD+RW. I've never seen rewritable DVD+R DL media... have you?

You'll have to use a new blank one, you've wasted that one I'm afraid. Your discs are 'Write Once, Read Many' (WORM) discs and cannot be erased / overwritten.

There is no absolute end of life like that. It works until it doesn’t. At that point, you’ll get write errors or it won’t be readable (verify will fail).

Did you use Read mode to make the image of the disc? It should have created a CUE file to go with that BIN file, you shouldn’t be doing it manually. To actually use the BIN/CUE, you then need to mount the CUE in a virtual drive program.

There's nothing obviously wrong with what you've done. As 'invalid parameter' is often to do with memory alignment, I'd guess you just need to tweak things a little so everything is happy. I have a 'DWORD filler' between your 's' and 'sense' to realign on dword boundaries - going by the comment next to it anyway

The plus/robot drives just basically have burnermax built in. As you know, the XGD3 images are too big to burn to a DVD+R DL under normal circumstances. Burnermax allowed for a bit of overburning on specific drives and these vinpower ones support overburning by default and that’s all that matters (not the burnermax bit) You will not get good results trying to overburn anything other than the verbatim discs. Alternative manufacturers weren’t even that reliable for regular sized images, let alone oversized ones.

Yes, the optiarc, piodata and plextor ‘plus’ / ‘robot’ models all support dvd+r dl over burning out of the box.

You can still buy brand new drives from vinpower that’ll do the job. No need for a B drive, most versions after B worked just fine.

Modifying the image using your hex editor is the quickest way right now, but ultimately you want ImgBurn to be able to insert the padding by itself.