LIGHTNING UK!

If you’re planning on making images of discs, you want to tell it to load up in read mode, not discovery mode. Discovery mode will only list writers and so that’s why it won’t go to the drive you’re selecting via /src.

Are you creating a legacy bootable disc or an efi bootable disc? Your bios needs to allow for whichever format you’re using. Legacy would normally require you to turn off secure boot and enable legacy booting in the bios. The guide is old and doesn’t really cover efi booting. I’ve no idea on the exact settings required for that. ImgBurn itself works fine on old/new hardware. Nothing has changed in the world of optical disc burning.

Track 29, Index 1 comes out to under 4 seconds long (before Track 30, Index 0 starts). I can only assume that's the issue your LG drive is moaning about. Some drives don't like tracks being under 4 seconds in length.

if it isn't in the middle of a video stream (which of course, IFO and BUP aren't), there's nothing to make seamless.

I said 7zip, not winzip. You may have to install it if you don’t already use it. Your install of winzip is broken too. Might as well uninstall that one!

I've never seen that before. Download it again? What OS are you using? It looks like riched20.dll is crashing. If all else fails, open the setup exe in 7zip and extract the files that way.

Not that person / thing hey? Oh yes you are! Go away cloudff... or should I call you gamemaniaco?

It’s enabled by default.

This topic very much reminds me of some posted by a certain someone a few years ago that were basically just asking nonsense theoretical/ technical questions. Please tell me you aren’t back again!

It’ll be due to the OS reading the files in an order that’s causing lots of ‘thrashing’ around. Access times for optical drives are awful.

You can only trust it if you compare against the image file. If you burnt in another program without the use of an intermediate image, you have no way of checking the data using ImgBurn. That said, if you verify every sector is readable using verify mode (with ‘compare against image file’ disabled) and do a file level comparison against the stuff on your HDD that you originally burnt using something like Beyond Compare, that’s enough to say the disc is ok.

Verify mode can work in 2 ways. It’ll always check the drive is capable of reading every sector on the disc, but it can also check if the data within those sectors matches what’s in a disc image file on your hard drive. No reason for it to take any longer than it takes to read the disc itself. The comparison side of things is much faster than the actual reading part. Optical drives are slow!

post the cue sheet please

It’s not the ‘cycle tray before verify’ option, but yes, the option to eject the disc once it has finished being burnt (and verified) already exists.

That doesn't look like standard Windows behaviour to me, so maybe you've set something in group policy or are running 3rd party software that's blocking access to the drive. I have no such issue on a Windows 10 workstation with a 'normal' user logged in.