LIGHTNING UK!

Put one of the Verbatim discs in the drive, switch to 'Write' mode and then bring up the automatic write speed configuration screen. It'll auto-populate the Disc ID field. Failing that, you'd probably set the speed within DVDFab itself and it'll then pass it to ImgBurn.

The exclusive access lock is provided by the OS. It locks it in such a way that the OS commands used to 'open' the drive then fail. It's out of ImgBurn's hands.

Then you probably changed something on your previous install because it's working how it's supposed to now. That's the whole idea behind locking the drive for exclusive usage during the burn... nothing else can touch it and mess things up.

You can open multiple instances and have them all see the drive if you aren't actually burning to it in one of them.

Not that I can think of. So are you saying that if you drag a folder from the explorer pane (or from an explorer window itself) over into the disc layout pane (this is all within the DLE window) that contains empty folders, those folders aren't added? It works fine for me.

That's driver stuff (not my domain) and Virtual CloneDrive is free and already does a great job of it.

I don't know why but your drive seems to be having some issue with those TYG02 discs. Do you have any others you can try?

Sometimes drives will pad a disc so its size is a multiple of 16. So if you burn an ISO that is made up of 17 sectors, the disc will appear to be 32 sectors. ImgBurn would read all 32 when making the new ISO using 'Read' mode.

Yes, I take a copy of the folder on the day I release a public version and name it accordingly.

You won't need to cross flash anything. It'll either be based on a LiteOn drive (and work) or it won't be.

That's exactly what it was.... DVD Decrypter's 'Write' mode.

Some models (or versions of models) work, some don't. Can't you find any Lite-On 'iHASx24 E' drives?

That means nothing.

What are the buffers doing on the slow drives? If they're both full, they must have slowed themselves down for some reason. I see nothing in your post saying 2 and 3 ever work as quickly as the rest. Maybe it's the way they're connect or how their channels are configured - PIO / DMA mode etc.

Sorry, I don't know. I don't follow the Asus drives.

Rubbish discs, read this... http://forum.imgburn.com/index.php?showtopic=8000

Try installing the latest Intel Rapid Storage Tech driver. https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23538&ProdId=2101&lang=eng&OSVersion=%0A%09%09%09%09%09%09%09%09%0A%09%09%09%09%09%09%09&DownloadType= You could also try another port / cable / power plug. If possible, try it in another machine too. If you still have problems, try booting into safe mode and see if you have the same problem. Even the rewritables you tried were a cheapo dye, ideally I'd like to see what the drive does when presented with decent Taiyo Yuden or Verbatim discs. If it fails with those too then it's probably faulty.

Some online shops will mention the MID / dye being used. They'll be 8x and just make sure they aren't 'Value' ones. Read any reviews that have been posted by people buying them and check the comments.

No, get the right ones online if you can't buy them locally.

Right click the drive selection box and select 'Family Tree'. Close the prompt and then copy + paste everything from the log window. The drive seems to be erroring out and resetting itself. It could be faulty, yes. I'd check a few other things first though.

Turn the PC physically off and on again.

Do you have any decent discs you can test with? 'UME02' are low quality.

Stop using your machine / hdd so much for other stuff during the burn. Hopefully that'll stop you getting the buffer problems. Your discs are the cheapo 'CMC' dye and not the proper MKM one you should be using. Buy the better discs, not the value range if yours really are Verbatim at all.

Yeah, I believe that's the same thing as our 209EBK. We just have a different naming scheme for some reason.

Can you copy + paste the bit from the auto-saved log for that session please? The device list is only rescanned when the program isn't busy with things (otherwise it's queued up). There's code to ignore it at the end of an erase/format if it was being done automatically before a write operation.