LIGHTNING UK!

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.

post the log please

Doesn't it just eventually error out and then let you carry on with the devices that have been successfully initialised? You could load it twice with autoloader support disabled and then enable it in 1 instance.

I’m pretty sure it defaults to formatting without spare areas. So if you do a full erase on your bd-re, it should then burn at full speed. No spare areas = no defect management = full burn speed You don’t need to format bd-r unless you specifically want to enable that defect management feature (by formatting with spare areas).

It could be a result of the issue/error, yes.

From your log file... That's why it took ages to burn. The drive was verifying as it burnt - an internal process and nothing to do with ImgBurn. Formatting discs without spare areas gets around the drive doing that.

Post the log from one of the burns that took a while. Maybe it’ll give us more of a clue.

Try with some better discs. Your drive seems to have a problem with 'RITEKF1' media.

You'll need to provide more info in order for anyone to answer that. How big are the files? What exactly are they? (disc images - ISO files etc or something else) If they're disc images, what do they contain? Basically, 1 disc image = 1 disc. You might be able to extract and then combine the contents of multiple disc images, but it all depends on what's in them. For other types of files, you can add as many files as will fit on the disc using Build mode.

The error is coming from the drive, not the software. Have them try burning at a slower speed. Maybe 'MAX' isn't the way to go. They could also try enabling the 'perform opc before write' option in the settings on the 'Write' tab.

Get yourself some better discs. 'RITEKF1' aren't known for being good quality.

Please read the guides. Also, this is the ImgBurn Support Forum. If you're here, you're asking for help with ImgBurn - so asking 'What software should I use' is somewhat strange.

Don't be sad, be happy.

If your drive works, it works. Ideally, you'd be able to get proper passthrough of all I/O working (if that's even possible), so ImgBurn can see it as the LG drive that it is. You'll soon find out how reliable it is by reading and writing a few 'cheap' 25GB discs. Don't jump straight to the 100GB MDisc ones. ImgBurn marks the UDF file system as readonly and always closes discs when it burns, so you can't add anything to them. UDF 2.5 or 2.6, it doesn't really matter. DVD and BD are always Mode 1. Only CD can be Mode 2. DVD and BD are always SAO/DAO. Only CD can be TAO.

That’s a very old drive... same internals as the lite-on 812S. I doubt it has firmware support for mkm-003-00 does it?! Are any supported write speeds listed in the box on the right when in Write mode with a blank disc in the drive?

All you do is Read the disc using Read mode and then Write the image using Write mode. There's nothing special involved. If you run into issues during the Write (and Verify.... make sure the leave that enabled) phase, post a log please.

It might be worth trying something like the DMA fix from the FAQ. Uninstall the controller from within device manager and reboot so it finds it all again. If you haven’t already tried all that of course

The option in the tools does it there and then... possibly only for dvd, I can’t remember. The program sets the speed again when starting any sort of read/write operation (based on the value in the drop down box from that mode), so the speeds chosen from tools->drive will no longer apply.