LIGHTNING UK!

Is it possible that the files on the hdd may have changed in the time between you starting the backup and it finishing? All I'd suggest is making an image file and burning that, rather than burning the files on the fly. The content of the image file won't change so verification will be more accurate. You should also try burning at 8x, it'll give you a better quality burn.

This could depend on the media being used. For DVD+RW/BD-RE media, the quick erase just makes ImgBurn write zeros to the first few hundred sectors. That just wipes out the file system. You could read the remaining sectors and still access the data, but without the file system, you have no fool proof way of knowing where files start/end (or their names etc). For everything else, the quick erase wipes out the TOC. This is a drive function. You won't be able to read anything on the disc because the drive will see it as being empty and the read commands will simply fail. No idea about TOC recovery... I doubt it though.

If the program says there's no medium present in the status bar when you've got a disc in the drive, that's what the drive is telling it. The problem therefore lies between your drive and the media.

That's because it isn't digitally signed. I don't own a certificate. If there's no obvious 'no' on the offer screens you're shown, selecting the 'custom' option will no doubt give you more options - including one that allows you to say 'no'.

Click the 'change advanced setting' button down by where you set the write speed. Switch to the LiteOn tab, select the 'clear opc history' option in the 'change for' drop down, select 'clear' in the 'new setting' drop down and then click the 'change' button.

Burn at 4x instead of 8x. If that still doesn't work, clear the drive's OPC history and try again.

Post the complete log please.

That advice might be true if you'd just left them burning at max speed, but you haven't. 2x obviously isn't working very well, so now is the time to try the remaining supported speeds / other discs / cleaning the drive / a different drive.

Your drive may be producing low quality (hard to read) burns on that media. Have you tried at 4x? You don't need to think/worry about the layer break on BD discs, they're to be treated like a large single layer disc. The player's buffer gets around any pause during the layer transition - but that of course relies on the disc being readable!

It seems that Windows just creates a file with an alternate data stream or something when you pass a file name with a colon in the name like that. When I just tried it, it wasn't easy to delete the file either lol I've added a check for that now, thanks.

If you weren't using BD-RE (but just normal BD-R instead), you'd obviously skip the whole formatting process. BD-RE can normally only be burnt at 2x (or 2.3x) too... BD-R can be burnt at up to 16x on modern drives (not so for DL discs though). I guess it all comes down to why you're using BD-RE in the first place and if you wanted to be able to use them again or not. I certainly wouldn't use a BD-RE for something I had no intention of overwriting.

BD-RE discs are rewritable. They're the ones that need formatting before the drive will accept any 'Write' command to write data to them. ImgBurn has no 'copy' mode, so yeah, you have to make an image and then burn it. Technically, you can point Build mode at a source drive (your bdrom) and have the destination set as your writer. That'll copy all of the file present on the source disc to the destination disc but it won't be a true 'copy' because ImgBurn will have created a new file system.

It'll always zero the sectors after the drive has finished doing its own thing as part of the full format. The discs only need formatting once though and after that you can just overwrite any data that's already been burnt to it. The program handles all of that stuff automatically.

A full format with full certification will normally take the drive about 1 - 2 hours. Then it's another hour or so to write zeros to all of the sectors. It's not something you need to do again and at least it should pick up on any potential problems with your drive/media combo. That text you're reading (about PM's (= private message) etc) is just my signature. It wasn't specifically aimed at you, just people in general and gets added to every post I make.

If it didn't work on ATA either (and assuming that change really did put the controller back in ata/ide mode - the device name would then be totally different), I doubt the driver will make a difference. Maybe the drive has developed a fault?

Is that the latest rapid storage technology driver you can use on your chipset? (v8.8.0.1009) Have you tried switching the controller back to IDE mode instead of AHCI mode - just to see if that makes a difference?

It could be a driver issue. Right click the drive selection box and click 'Family Tree' on the menu that pops up. Close the prompt and then copy + paste everything from the log window please. As a side note, you could just burn that ISO to a DVD if they're working ok. It doesn't need to go on a CD.

You can't have 2 files with the same name in the same folder... that's pretty much all there is to it. If you use the 'Advanced' input mode (use the menu at the top to change the input mode), you should be able to rename the duplicate file as it's added to the disc compilation.

In what way does it 'crash' and then respond? The file dialog boxes are a Windows thing. The program can't do anything if they're open, it's sitting there waiting for the API function to return control back to it.

I can't see that would have ever worked. Even if ImgBurn didn't look for invalid characters in the file name, the OS wouldn't have been able to create the file and so that API function would (should) have failed and ImgBurn would have errored out.

If this doesn't work... http://forum.imgburn.com/index.php?/topic/6380-how-to-copy-a-disc-using-imgburn/ ... we can't help you.

Have you pointed the boot image file field at the etfsboot file as per the guide?

That's correct, it only looks for index 0 and 1 when reading a disc. I honestly can't see that changing, sorry.

That's the way 8.1 reports it to programs that don't specifically say they support 8.1 via something in the manifest file. The next version will list it properly.

No, nobody likes them. They add no value to the program. I can tell you just think they're 'cool', in which case, add them into a program you create yourself.