LIGHTNING UK!

What bugs are you referring to? I’m pretty sure I’d have fixed anything that was actually a bug at the time it was reported. Of course, me fixing them is very different to me fixing them AND releasing a version that includes those fixes. The version that I’ve very occasionally worked on over the last 7 years will eventually be released, of course it will, I just have a very bad habit of sitting on things. I honestly do keep thinking I need to get back to it and get it done. In all honesty, I think I went a year without even having the development environment on my machine. I probably installed it all again and got it to the stage where I can actually compile the code again about a month ago. That’s some serious progress right there! I have a no point said to myself that I’m done with ImgBurn. If I had, this forum wouldn’t be here.

You're crazy.

Have you only ever burnt them at 'MAX' (8x) speed? Maybe your drive(s) would do a better job at one of the slower speeds they claim to support those discs at.

There's probably nothing you can do about that. Either the drive can read the disc or it can't. Just make sure it's clean and not covered in finger prints etc. You probably also have the option of cleaning the drive itself in case it isn't running at 100%.

It remembers its last position.

Do you really need to extract the files from the original ISO? The reason you gave in your initial post made no sense. The images direct from Microsoft burn and boot without a problem.

I've just checked and my 1909 image (SW_DVD9_Win_Pro_10_1909_64BIT_English_Pro_Ent_EDU_N_MLF_X22-17395.ISO) is over single layer size, but not by much. The exact size is 5,292,945,408 bytes, which Windows calls 4.92GB. There would be no problem at all putting that on a DVD+R DL disc... which is what I burnt it to.

The guide does work, yes. Have they really got to the point where it won’t fit on a double layer dvd now? I’m sure the last one I burnt did, and that would have been the Windows 10 1909 edition or whatever it was before 2004 came out

I think you misunderstand what discovery mode is for. Read mode will tell you what you need to know.

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.

Is it actually Windows 8 or is it Windows 10? Not really sure why it's trying to open the device by drive letter, it should default to 'Device Interface' on that OS. Have you adjusted some settings trying to get it to work? Please revert to defaults. It shouldn't have a problem using SPTI on Windows 8 / 10, even when you aren't running with admin rights.