LIGHTNING UK!

Yes, just untick the box. (Tools -> Settings -> General -> Page 1 -> Display Warnings -> Overburning)

You probably did but it's pointless. Why make something less compatible when there's no benefit in doing so? ImgBurn uses BIN/CUE when it needs to and ISO when it doesn't. For a Mode 1 disc, ISO is 100% as accurate as BIN/CUE. You're over-thinking things.

Now you've done your little test, I recommend you put it back on DAO/SAO.

Where are you getting that from?! To quote their privacy policy...

No, the drive doesn't use an online database. It does/can remember certain things about previous burns though (and use that info to 'help' with future burns) - but only Lite-On really know what the drive does internally.

BIN/CUE and ISO have nothing to do with file name lengths. The one the program uses by default all depends on the way the disc was written (Mode 1 or Mode 2). Yes, the program will tell you about file/folder name truncation etc in the Log window - keep it open at all times.

The DRW-22B2L is handled automatically by ImgBurn (2.5.6.0 anyway), you don't need to mess with any booktype stuff.

ImgBurn uses the DAO/SAO write type by default and drives tend to burn a minimum of 1GB to DVDs when that's being used - it makes the disc more compatible. If a program were to use the Incremental write type instead and the drive then only burns the 700MB image (without padding to 1GB), that would explain why it takes less time. So it's not actually faster (that's impossible as the drive controls the speed), it's just doing things differently.

The default write strategy in the firmware doesn't seem to play nicely with the overburning. It kept failing to verify around the layer break point for me during testing. When no strategy exists (as would be the case if the original is renamed), the drive automatically uses HT and OHT to burn the disc. HT and OHT are part of 'SmartWrite' - http://www.liteonit.eu/en/smartwrite/smartwrite.html My results were very inconsistent until I turned off OHT (by enabling FHT). Don't forget to clear the drive's OPC history before starting. Are your Verbatim discs made in Singapore? The ones from there seem to produce the best results.

Take a look at post #20 here - http://forum.imgburn.com/index.php?act=findpost&pid=136519 Pay attention to Attempt 8.

That's covered by the overburning warning option.

This is a Windows problem at the moment, ImgBurn is doing exactly what it should be doing. Eject the disc, load the program, switch to read mode (create image file from disc), insert the disc.

Have you build a BD disc with the current version? 2.5.6.0 ? If you want to test with PowerDVD (you'd need the 'Ultra' version), just build an ISO, mount it in something like Virtual Clone Drive and then see if it works. If it does, there's no reason it shouldn't also work once burnt to disc. Rather than wasting loads of BD-R discs, use a BD-RE disc until you figure out what's going wrong. It would help us if you post a log of you burning + verifying a disc. Problems usually come from having invalid/incomplete source files/folders. ImgBurn just burns what you give it.

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

Last one of those I got was a Sumvision Tempest. I can't answer that. You just have to try things yourself. Buying either of them could fix the problem. Worst case scenario, you have to buy both.

Not really, I've never had to buy one! Assuming your laptop has one of those expresscard slots on the side, try just ebaying 'expresscard nec' and look for a USB 3.0 one.

Well, it's not the *only* thing but it's probably the easiest. What I'd do after that is get an Renesas (NEC) chipset USB card (usb 3.0 maybe) for the laptop. To check the chipset the enclosure uses, open it up and read the name off the main chip!

Nobody really knows the reason behind the 'semaphore timeout' issue, it's just one of those things and we've chalked it up to a conflict between the USB chipset in the enclosure and the USB chipset on the motherboard. So all I can suggest at the moment is trying a different enclosure. Out of interest, which one did you buy?

What format are the files you're downloading? Having 4 of something just means you perform the usual burning method 4 times (to 4 discs). Don't make it harder than it actually is.

There's a whole section of Guides, it might be an idea to read them if you don't know how the program works.

That option doesn't do what you think it does

MP3 obviously isn't a lossless format - what you encode is not what you end up with after decoding. That's why you can end up with a 'less than perfect' decoded file. Audio manipulation is not my thing so I'm sorry but you'll never get this option in ImgBurn.

Try uninstalling the ide/atapi controller entries in device manager and rebooting. I assume there aren't any connections/cables you can check? (slimline drive - right?) The next thing after that would be drivers / filter drivers.

Going by the erroneous (and missing) characters in the device id string I'd say you've got some sort of corruption happening. That corruption will then be causing certain drive capabilities to go unnoticed.

Correct. If the manual/specs say it can play MKV files from a disc, you should just be able to burn it using Build mode.