LIGHTNING UK!

The first error is the important one, not a thing that pops up after a retry. Your drive reported a ‘write error’ while trying to burn the disc. So, it didn’t like something about it. if there’s no better firmware you can use, there’s little you can do about it. if it’s a fluke failure, try another disc. If it keeps failing, you could try enabling the ‘perform opc before write’ option to see if it enables the drive to do a better job. Enabling defect management is also an option, but that slows down the burn and uses up disc space.

I’d always use Sao/dao. I do recall a few discs needing raw-dao 96 due to early copy protection efforts, and of course, ImgBurn doesn’t support that.

Blimey, that’s a definite ‘check the code and see what’s going on’ type of question. Leave it with me and I’ll get back to as soon as I can.

You need the right sort of drive and the right discs for it to work. I’m afraid your log snippet isn’t big enough to tell us either bits of info.

All the message boxes within the app behave the same way (they flow through one function). Generally speaking, the 'owner' window parameter of the MessageBox Windows API call is set to the one that's active when they're displayed. For the 'operation successfully completed' ones, that would be the main window. I'm not sure why it would be going behind the log window as I'd expect it to be centred relative to its owner. Where is your log window in comparison to the main window? Is it maximised? I don't really recall it being a problem, but we are going back 10+ years!

Get rid of the /MAKEIMAGEBOOTABLE one, like I mentioned in your other thread, it doesn't exist. Please also remove the /START one. When you've done that, run the command again and check the config on the Advanced -> Bootable Disc tab within Build mode. Post a screenshot of how it's been configured based on your CLI parameters.

Screenshot the actual prompt you're seeing please. There is no 'MAKEIMAGEBOOTABLE' parameter, the 'checking' of the 'Make Image Bootable' checkbox is controlled by the existence of a valid value for /BOOTEMUTYPE.

Please provide a log where you've actually burnt something (a full disc) and that will therefore show the issue.

Looks like you’ve clicked on an advert on the digital digest website. DD host this website and forum. So, no, I can’t remove that one from the list. The download button below the big one is the real one, but it would appear that’s ’download manager enabled’. The text in the above screenshot show you can download it without the download manager by clicking on the ‘here’ text. What mirrors sites do with the file I send them is their own choice. You should take it up with them. Of course you could just download it direct from the ImgBurn mirror in the first place.

You're still a 'New Member' and that group of users has certain restrictions in place. Once you move beyond it, you'll have more freedom.

You can pick the disc type when erasing. It isn’t showing a mid so I’m only going by what the Op said they’d purchased disc wise.

Why are you trying to erase dvd+R DL discs? You can’t.

No it doesn't.

Examine the files using Media Info. What format are they actually in? There must be something 'different' about them or your system would support them without the need for extra filters.

It could be that the 2 image.dat files are just raw sector dumps, the same as an iso. are their sizes a multiple of 2048? try and open the one from the layer 0 folder in Write mode. if that use the ‘create .dvd file’ option in the tools menu and add both files to the list. Specify the layer break as whatever the size of layer 0 image.dat is, divided by 2048. Save the .dvd file and then load that in Write mode. you could test the .dvd file by mounting it in virtual clonedrive. If you can see the contents by browsing the virtual drive, go ahead and burn the .dvd to disc in write mode.