LIGHTNING UK!

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.

Yes, you could modify the image to insert 358272 empty sectors at sector 1913760.

You can’t compare different images in different programs. It must be the same image in different programs. Please can you do the verify bit I mentioned? Put an mRDL burnt disc in the drive, load ImgBurn and go into Verify mode. Select the image you burnt it from and then click the start button. Once it has finished, copy and paste everything from the log window please.

Thanks for all of the posts but you don’t appear to have done anything I asked you to do. Can you re-read my post please and provide the required info. If you’re unsure on how to do anything I’ve asked, please ask for more help.

I don't recall even having heard of mRDL before... but it's old and very niche, so I've probably forgotten about it anyway! Please put one of the discs you've burnt with it into your drive and go into ImgBurn's Read mode. Copy and paste everything from the box on the right of the main window for me please. Can you also then use Verify mode to compare the disc against the image file and post the log file please? I'd like to see if they're changing anything being written to the disc.

Have you actually tried just burning one and seeing what happens? If the firmware in the xbox drive supports it, maybe it'll just work.

No, buy the correct discs.

They aren’t DVD+R DL discs, they’re DVD-R DL.

If you read a disc to an ISO using Read mode and then simply write the ISO to a new disc using Write mode, everything is preserved. The size of the ISO will match the number of used sectors on the disc (multiplied by the sector size). The size of the source disc is mentioned in the log window when the Read operation starts. It's also in the info box on the right of the main window when in Read mode.

Try enabling the ‘perform opc before write’ option in the settings. Once you’ve done that, burn at each of the supported write speeds again.

I'm sure you could work around the issue by using the right sequence of quotes (double / escaped quotes etc). The processor needs to deal with call to ImgBurn.exe and the arguments you're passing to it as a whole, not try and interpret the arguments you're passing to ImgBurn.exe itself. It needs to see the entire command as a single string - unless you're using a function that specifically wants an arguments parameter, whereby it's then 2 strings - 1 to call ImgBurn and another to for the parameters you're passing to ImgBurn. Does passing /s to cmd make a difference? i.e. cmd /c /s "C:\Users\user\Desktop\ImgBurn.exe" /MODE BUILD /SRC "C:\Users\user\Desktop\NI_33750_ZIP\DVD1\Relatorio\|C:\Users\user\Desktop\NI_33750_ZIP\DVD1\Relatorio\hashes.txt" /DEST "C:\Users\user\Desktop\NI_33750_ZIP\DVD1\imagemteste.iso" /FILESYSTEM "UDF" /UDFREVISION "2.60" /VOLUMELABEL_UDF "DVD1_teste_img_burn" /OVERWRITE YES /RECURSESUBDIRECTORIES YES /NOSAVELOG /NOSAVESETTINGS /START /NOIMAGEDETAILS /CLOSE

Try running it directly from the command prompt rather than powershell. It may be messing with the pipe.

It won't detect it as a BD Video disc unless the folder you're adding has a BDMV folder in it (directly in it, not a sub folder of it). So just double check what's in your source folder.

Any command that gets stuck being processed is down to something else going on with your machine. It could be a driver of some sort in the I/O chain that's not behaving as it should do. Commands should either work or fail... not get stuck. Indeed, the AWS stuff you've configured won't be having anything to do with it behaving itself a little better now, it'll be because you've changed to drive letter. That's not to say I recommend using drive letter - 'drive letter' enumeration doesn't support a few features that the others do. (The default options are usually the best)

If you're worried about anything, stick to building the ISO first, do your checks on it and then use Write mode to burn it to the disc. The only file system you need to include when using Build mode is UDF. Enable the option to include system / hidden files. What gets logged as being excluded?

Yes.

That dates back to the days of CDs. It’s nothing to do with any movie on the disc.

ImgBurn is for optical drives/discs, not hard drives.