LIGHTNING UK!

It sure is

Going by this thread... http://club.myce.com/f44/what-drive-atapi-dh16ayh-233245 ...your drive is a Lite-On 165H6S. That would make more sense as it's far too old to be an Optiarc 724x one. Setting the layerbreak to '2133520' isn't physically possible with that drive, it'll just error out if you try. It won't cause a 'Write Error' though. The one you got with the BenQ drive was just because it didn't support the MKM-003-00 MID and couldn't write to the discs very well/at all. It's up to you if you update the firmware. I don't know exactly what changed with the newer versions but I typically always run the latest of everything. You can backup your current firmware easy enough using the LiteOn flasher tool from the MyCE forums and flash it back later if you don't like the newer one.

The firmware for your BenQ drive doesn't support the MKM-003-00 MID. The Lite-On looks like it does though... but you should put the latest firmware on it. http://www.firmwarehq.com/Lite-On/DH-16AYH/files.html I'm afraid I can't tell you that it'll work 100% perfectly, I have no control over such things. It's all down to the drive/firmware/media combo.

The 'ANY!' folder comes from AnyDVD and is nothing to do with ImgBurn. If it messed up when modifying the file system, I'm afraid that's out of my hands. Please examine that disc in IsoBuster. Once the correct drive has been selected, right click the 'UDF' entry in the tree on the left and select 'Folder tree and file information' -> 'List tree-info (in txt file)' -> 'LBA, Full Path'. Save the file somewhere on your computer and then upload it here on the forum.

That'll make the drive ignore what's in the firmware and build a new write strategy 'on the fly'. Be careful though... sometimes it works, sometimes it doesn't. When burning with the drive configured like that, burns are less consistent and because it's a drive setting (and nothing to do with the software you're using), it's applied to every burn you do and on all media.

This isn't an xbox forum. Ask on one of those instead please.

The drive says it only supports the discs at 4x and you can't make it do something it doesn't want to - it'll just ignore any request for an unsupported speed. Nothing about what you're burning can cause a burn to fail. So the file system etc don't even come into it. This is purely a drive/firmware/media combo issue.

PL05 is the latest firmware for that drive. http://www.firmwarehq.com/Lite-On/iHBS112%2B2/files.html Your drive is reporting a 'Write Error' as it tries to burn the disc... so it must be running into some issue with it. Try discs with a different (better) dye / MID. Perhaps the iHBS112 (at least with PL04 firmware) isn't very good at burning 'CMCMAG-DI6-000' discs.

'Default Destination' on the 'Read' tab in the 'Settings'. It defaults to the drive with the most free space.

It looks to me as if you're overburning the discs and they just can't handle it. Why not use the discs they tell you to use? When you try and go beyond what something is designed/certified for, you have to expect problems/failures. You can mess around with the drive's advanced settings and swapping firmware strategies etc in the hope it'll work.... but that's nothing to do with ImgBurn.

Post a log please - as per the pink box up the top.

Nope, sorry. I'm sure there are tools out there that can split based on a CUE file.

You can't, ImgBurn always finalises. If you want multisession data burning, just use what's built into Windows.

That one is nothing to do with me, Explorer makes it based on user selection.

You can google for that warning message, there's tons of info out there on it. I never found it to cause a problem with burning, it just slowed down reading/verifying. If you don't want the potential problem of it slowing down I/O on your machine, get rid of the SPTD driver (usually installed with stuff like Alcohol 120%, DAEMON Tools etc). If you think your machine is slow at burning the DL discs, post a log from such a burn we'll take a look.

% complete of a (non 'Quick') DVD+RW erase/format comes from the drive itself. If it's not finishing the format, again, that's down to the drive. Perhaps it doesn't like the media you're using? Posting a log would help.

That's fine if it doesn't, I just wanted to make sure I had everything You can go ahead and apply the fix I mentioned in post 8 now. I've tweaked the installer (uninstaller) so that other (the incorrect 'ImgBurn.AssocFile.ape' - and others like it) entry will get removed upon uninstallation of the program. Previously, it would have only removed it if it was the correct 'ImgBurn.AssocFile.ibb' one.

I'm sure they'll be fine. Put one in the drive and copy + paste the disc info from the box on the right when you're in Write mode.

Because like I said above, they used ImgBurn to create (build) the disc they used as the 'master' - which they then duplicated / had pressed and eventually sold. EDIT: oops, not 'above' but in another topic exactly the same as this one (and I'm sure it was by the same person too ). http://forum.imgburn.com/index.php?showtopic=20599

I don't fully understand why you're using a virtual burner at all? Why not just copy the pictures/videos to your hard drive and burn them straight to disc with normal burning software? Virtual CD's virtual burner can be told to mount discs and output as ISO files. I'm fairly sure that doesn't mean what you think it means. All you're doing is burning the actual picture/video files. You're certainly allowed to have both on a data disc. If the virtual burner you're using only saves in VDD format, just mount that VDD file in the virtual drive and then point ImgBurn's 'Read' mode at the virtual drive and have it create a new ISO (or BIN/CUE is reading a complex CD). Then burn that ISO (or BIN/CUE) in Write mode.

You'd have to ask the people that made your virtual drive program about stuff that's specific to the files it creates. ImgBurn will make an attempt to burn anything that's semi like an ISO, but you have no way of knowing if what it's burning is anything useful / correct. The safer option would be to mount the VDD and use ImgBurn to make a 'supported' image from the virtual drive. Out of interest, what program is it that you're using?

That's not how the queue works. The values get set when the burn starts, not before. That's why you have to tick the box to say you want to 'Set' things.

Ok well that's an easy one but I've no idea how it would have happened. [HKEY_CLASSES_ROOT\.ibb] @="ImgBurn.AssocFile.ape" The 'default' value should be 'ImgBurn.AssocFile.ibb', not 'ImgBurn.AssocFile.ape'. ***BEFORE*** you change it, please just also export the following for me (if they exist)... HKEY_CURRENT_USER\Software\Classes\.ibb HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.ibb

Burning is nothing to do with the software and everything to do with the drive/firmware/media combo. Try cleaning your drive with a cleaning disc. Try discs from another spindle - perhaps get MKM-003-00 instead of MKM-001-00 (as you say you've already got a new pack of MKM-001-00).

ok well you need to export a couple of registry keys for me to look at. 1. HKEY_CLASSES_ROOT\.ibb 2. HKEY_CLASSES_ROOT\ImgBurn.AssocFile.ibb Just select them, then right click and choose 'Export'. Type a name for the file (i.e. 'ibb.reg' and 'ImgBurn.AssocFile.ibb.reg' would make sense) and save them somewhere easily accessible. Then upload both files here - you'll have to use the 'More Reply Options' button to be able to upload them.