LIGHTNING UK!

I just meant within ImgBurn. There's nothing in the erasing code that looks at the value of the 'Write Speed' box.

Your firewall might be blocking the update check badly - to the point where control isn't being returned to the program after a call to a windows API function. If you're going to block it, turn off the update checking feature.

You can't do it on the latest 'E' drives, they don't support it - or at least not via the same command as the old versions and none of the official liteon tools support it (yet?) either.

ImgBurn is burning *exactly* what you give it 'as-is'. If you want things to loop (or don't), then they need to be configured to do that as part of the authoring process. Depending on how exactly you're creating the disc (are you using a proper BD Video structure or just some HD files on a disc?), the player itself could be doing it. But again, none of this is anything to do with ImgBurn

This is nothing to do with the actual burning phase, it's down to your source files / the player.

The data type option doesn't apply to anything other than CD media. DVD and BD only support Mode 1/2048 and the program is well aware of that. The file system selection is really just a personal preference thing. Some are newer than others and so have more features / less limitations. Windows can read all 3 (iso9660, Joliet, Udf) just fine so there's no problem there when it comes to reading files on the disc. The drive has the final say on the write speed it uses. If it says it only supports burning those discs at 2x (as yours does), it'll only ever burn at 2x, even if you select 48x in the program. Imgburn will ask it to burn at 48x but it'll just semi ignore it and use the closest supported speed. The write errors your drive reported were purely a hardware thing (drive/media) and nothing to do with ImgBurn or it's settings.

I guess a drive can just think it has done an ok job of writing stuff when really it didn't. They don't check as they burn, so some mistakes go unnoticed. As you say, it's only catastrophic errors that the drive ever reports back to the program and would then get shown to the end user.

Neither of those fields contain values that ImgBurn is putting there. The implementation ID one would be the same if the same program is creating the file system. It's nothing to do with what burns the disc, just the actual creation part. The volume label is whatever you want it to be. Again, yours isn't coming from ImgBurn.

Your drive doesn't like those discs (or rather the 'CMC MAG. AM3' MID/dye), buy some better ones. Cleaning the drive with a cleaning disc may also help.

Both would produce the same result as ImgBurn should recognise you're trying to burn a bd video disc. There's a guide for bd video burning in the guides forum.

They might be ok for certain flashing related purposes but should be avoided at all other times. Connect it to the main controller on your motherboard. Oh and you should only enable overspeed when using mkm-001-00 media.

Try connecting it to another port. It's probably worth unplugging the optic and drive and connecting the sony to that port. Something is different about how they're both connected currently because one the start of the device interface identifier is different. IDE vs SCSI.

The 'Write Errors' you were getting were nothing to do with any settings in ImgBurn. Your drive was just unable to burn that 'CMCMAG-CN2-000' MID BD-RE disc nicely/properly.

What controller is the drive attached to? It's not working well with your optical drives.

How is your Sony drive connected to the machine? It looks like the controller it's attached to (or the drivers installed for it) doesn't (don't) really like it being there. The functions used to get certain info should either work or fail, not hang as they're doing on your PC. I'm afraid that kind of thing is out of my hands.

OpenCandy is just an advertising platform plugin that the installer uses. It doesn't get 'installed' or run outside of the installer - apart from doing its job of installing any programs you were offered and opted in to (or not opted out of) installing during the installation process.

I'd try some other disc if I were you. You've got 2 drives that don't appear to like them.

There's no way of doing that automatically, you'd need to drag over 4.37GB worth of data yourself and do each disc individually.

Yes, your drive has real issues with the DVD+RW you put in it, hence all of the failed writes.

The write speed for erasing discs can't be configured. Like you say, it's always done at max speed and this is by design - not really for any specific reason, it just is!

I still can't reproduce this at all. In any case, it's a ComboBoxEx control, I don't do anything with it except populate it at the start. I have no idea how you're making it lose its selected item text.

It could be because your drive is in the process of becoming ready. Give it more time or eject the disc from the drive if it's having trouble reading it.

Yeah, then you'd be able to mess with it until your heart's content. I'm using C++ Builder 2007.

They have the 'look' the OS gives them. You might be able to bodge an Aero themed listbox, but that isn't how the OS draws them. Just drop the address bar down from within an Explorer window and you'll see what a ListBox is supposed to look like (Explorer is usually the 'go to' app for these things). ListViews and TreeViews are already manually being told to use the 'Explorer' theme so they get the aero selection style.

Sorry, no. Try the NVidia forums.