LIGHTNING UK!

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.

You can adjust the size of single layer media on the 'media' tab such that it thinks it's building for a single layer disc.

That looks like 11.2, not 10.8 If you're going for the latest, I thought they were up to 12.8 now. In any case, if your port is just going to keep timing out early when the drive is processing a command, you're probably out of luck. If you've got any Slysoft / Elaborate Bytes software installed then you could try switching the I/O Interface over to ElbyCDIO in the setting. It may bypass whatever's making it time out early and causing the drive to vanish from the OS. What error were you getting when connected via USB?

I've no way to prove you got the opt-out screens and you've no way to prove you didn't - unless you just happened to be recording your screen at the time? All I know is that you should get them. I don't control them or have anything to do with them, that's all handled by OpenCandy.

Try installing v10.8 of the Intel Rapid Storage Technology driver.

When you're in Write mode within ImgBurn, just right click the 'Destination' drive selection drop down box. You'll find 'Family Tree' on the menu that pops up.

It looks like the drive is being removed from the OS. It could be a driver thing... which controller does that esata port run off? Right click the drive selection box and click 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the Log window please.

You have to make project files yourself... and no, it's not a log of the files you've burnt. There's no way of logging that info. The only thing that would give you that info (in one form or another) is using Advanced input mode and then saving the project once you'd added all the files. The project file contains the list of options selected for that given project and also a list of all of the files (when using Advanced input mode, NOT standard input mode which just saves exactly what you see in the little 'Source' box). You could get a directory list of the disc once you'd burnt it (using other tools), but that obviously wouldn't show you their original source path on your hdd or whatever, just where they've ended up on the disc.

http://forum.imgburn.com/index.php?showtopic=12200