LIGHTNING UK!

The program doesn’t really set the speed, you do. If you leave it on the default setting, it’ll burn at MAX. Regions do not come into it. What you’re seeing there is the players (not) being able to read the disc properly.

Do you want me to write it for you?! There’s plenty of stuff out there if you Google for it. This is not a coding forum. Start with iso9660. Learn which descriptors are required and where they need to be located within the overall iso. Fill them out and build your image.

It all depends on which file systems you want to use in the ISO. Look up the specs for ISO9660, Joliet, UDF etc and build your program accordingly.

Your drive is misreporting info about that disc and it's causing something weird to happen.

If you only have things in 1 big wav or bin file, no, you can’t just remove things from the queue.

This won't be a bug. It'll be your drive not liking the disc you've put in it and not being 'ready' to burn. When it happens again, make note of what's written in the status bar at the bottom of the main window.

@Ch3vr0n Whilst that is one sort of 'lock' (tray lock), the one the OP is referring to is there to stop other programs from being able to access the drive and potentially mess up the burn. It either blocks apps from opening a 'handle' to the device or it blocks all operations on said 'handle'. @Robert333 As it locks for exclusive access before any burning starts, you're quite safe to pull the plug if it gets stuck for ages trying to lock it. I'd actually be interested to see what happens when you do that. Will the OS immediately return an error in response to the locking request (which is then displayed by ImgBurn) ? Who knows!

ImgBurn pre-dates Windows 10 and so doesn't know how to detect it. It's purely cosmetic.

The locking of the drive is a Windows API function, so if it's taking a while, it's because Windows is (still) trying to lock the drive. As for why it's taking a while, maybe some other program/service has an active connection to it? Try unplugging it and plugging it in again. They are probably tools you could use to check for open 'handles' to the drive - something like Process Explorer from Microsoft/sysinternals.

Some liteon drives remember how many discs they’ve burnt. Just dvd and bd though, not down to mid/did level.

If it doesn’t just work (auto reject after a while or whatever), it probably wasn’t something I’d considered during implementation. Perhaps I’ll revisit the code and improve things in this area.

I think it actually just copies the iso as-is to a folder on the usb somewhere. Meaning you can just keep adding boot options (bootable iso) until all the space has been filled up.

To be honest, I’ve only seen it recently and used it once! I used it to stick the acronis rescue disc iso image on usb. I think it allows you to put a menu in front of a bunch of bootable iso files and pick which one you want to load.

Try the YUMI route... on a usb stick. https://www.pendrivelinux.com/yumi-multiboot-usb-creator/ If you must stick with an optical disc, are your programs just DOS EXE files? Boot a DOS image via floppy emulation, make sure it loads optical drive drivers / extensions and then access the rest of the disc that way.

No, there is no option to control it.

I can't see anything that would make it do that, no. Best you could do is make a batch file that you drag + drop the folder on to, which then calls ImgBurn with the appropriate command line instructions.

Copy + Paste the contents of the ImgBurn log window once you've got that verbatim external drive connected.

You can have it ignore unreadable sectors (and zero fill the file) when using Read mode, yes. Once the stuff is on the disc though, you could use any old recovery type software to try and read as much of the disc as possible.... then rely on your par/par2 files to fix anything.

I see no problem with doing this. Just allow youself 10, 20, whatever% of the disc space for parity files of whatever you want to burn. So split your data (collection of files) in ~20gb chunks, generate 4gb worth of parity files and burn the whole lot to a 25gb disc. Going back many years, I know par and par2 files were heavily used on newsgroups... they probably still are.

You won't ever get it detected as a destination device, it can't burn anything and is purely a reader. You need to buy a DVD/BD writer.

Crashes in what way? Please try and screenshot it or something. Also, when it crashes, it offers to send a crash report to me... please do so.

I have no idea what the device actually is, but something about it must be presenting itself as a cd/dvd drive for it to become visible in ImgBurn. It's not going to harm the actual hard drive part of the device. It could just be that it's emulating one (a cd/dvd drive) in order to provide you with something to install some software from. I've seen devices do that before. So maybe it gives you d: or e: in order to access the hard drive data and then gives you f: to install some software from. Load the program up with the device unplugged from your system and copy + paste everything from the log window please. Then close the program, attach the device and do the same thing again please.

All supported CLI parameters are documented in the Readme.txt file. I don't recall there being one for this purpose. You could use 'reg' to turn on the autoloader stuff in the registry just before you fire up your autoloader instance of ImgBurn... and disable it in the internal drive script. HKEY_CURRENT_USER\SOFTWARE\ImgBurn Set the value of 'IO_EnumerateDevices_AutoLoaders' to 0 or 1. Enable: REG ADD HKCU\Software\ImgBurn /v IO_EnumerateDevices_AutoLoaders /t REG_DWORD /d 1 /f Disable: REG ADD HKCU\Software\ImgBurn /v IO_EnumerateDevices_AutoLoaders /t REG_DWORD /d 0 /f

If it doesn't work, it's probably unsupported. ImgBurn isn't really the tool to be using for this. Try an ISO editing program... PowerISO or whatever. It'll probably let you just replace the file in your existing ISO with a new one without having to rebuild the ISO (if the file is the same size or smaller).

It probably doesn't make a massive difference, but 2.50 / 2.60 is 'normal' for BD media and it's what I'd use now for most things that don't require a different version (i.e. DVD Video - 1.02). There's probably somewhere you can read about the differences between 1.02 and 2.50 / 2.60. The latter ones have a bit more redundancy in case of errors within the filesystem descriptors themselves.