LIGHTNING UK!

Yes. Like I said, lots of drives automatically / default to changing it to DVD-ROM on DVD+R DL disc. And even if they don't, ImgBurn has its own go at doing it - but that failed on your drive.

I think they may have switched chipsets (inside the drive) recently and it's probably going to take them a while to iron out the problems.

They're totally independent processes and ImgBurn can only use (Read from / Write to) 1 optical drive at a time.

You will only see what the drive has set it to once the burn has finished and the 'verify' part starts.

You told me about a problem with a drive and provided everything I asked for - you couldn't have done anything else Nah, I don't think it was done on purpose, I think it was another oversight in the firmware. I guess they just aren't doing enough testing with things.

Chances are, it does it automatically. Not only that, the booktype doesn't matter anyway.

See if enabling the 'Always use buffered I/O' option in the Settings on the I/O tab makes any difference. Ideally you'd be reading each image from a different physical hdd.

ok, you can now consider this done. Previously... I 14:04:21 -> Drive 9 - Info: HL-DT-ST DVDRAM GH24NS95 RN00-J0 (G:) (USB) Now... USB 2.0 port (with USB 2.0 -> SATA adapter)... I 14:09:46 -> Drive 9 - Info: HL-DT-ST DVDRAM GH24NS95 RN00-28 (G:) (USB 2.0) USB 2.0 port (with USB 3.0 -> SATA adapter)... I 14:06:05 -> Drive 9 - Info: HL-DT-ST DVDRAM GH24NS95 RN00-28 (G:) (USB 2.0) USB 3.0 port (with USB 2.0 -> SATA adapter)... I 14:11:28 -> Drive 9 - Info: HL-DT-ST DVDRAM GH24NS95 RN00-28 (G:) (USB 2.0) USB 3.0 port (with USB 3.0 -> SATA adapter)... I 14:02:59 -> Drive 9 - Info: HL-DT-ST DVDRAM GH24NS95 RN00-28 (G:) (USB 3.0)

Yeah, not gonna happen.

If the buffers are empty, it can't get enough data (quickly enough) from your hdd.

Windows only ever shows 32 characters. ImgBurn will see the full thing. PowerDVD and TMT are the two main 'licensed' software BD players. Yes, they might be slightly more forgiving than a standalone but I'm sure they'll be close enough. If in doubt, burn to BD-RE and test it.

No, the drive's firmware is causing it. The next version will have a workaround for its bug.

and virtual drives make it easy to work with ISO files. Mount them in such a thing and you have instant access to the files, no need to extract anywhere etc.

They all only work on certain drives... only certain drives have the ability to do that kind of scanning.

ImgBurn doesn't convert anything video related. If you want a DVD Video disc, that's the format you need the files in. There are loads of tools that'll take your AVI, Quicktime, MP4 files and turn them into DVD Video format - i.e. DVD Flick, ConvertXtoDVD. After that, it's simple.

bkf is a windows backup archive yeah? Assuming it's small enough to fit on a disc, you could use Build mode to burn it to one. It'll stay as / still be a bkf file once it's on the disc.

That kprobe screenshot looks like a lot of mine where Force HT wasn't enabled in the iHAS B/C/D drives, or when the drives just couldn't overburn / FHT didn't work in the same way in older drives. If it burns, verifies and kprobe's ok, you're probably good to go.

That's odd, I've never seen a drive lose it's eeprom settings when it loses power. As you're burning mkm-003, you don't need OS enabled - you're only burning at 4x. You also don't need OPC enabled. The OPC history is stored in the drive. It may just be that your drive can't handle the oversized DL media - even if the payload tool thinks it's able to enable it.

If no combination of eeprom settings makes any difference, you're probably out of luck. Verbatim double layer discs aren't recommend just about everywhere for no reason Are aren't overburning or truncating xgd2, those images are 'normal' sized.

That batch doesn't even register the file.

It's just a bad drive/firmware/media combo. They're the 3 things that control burn quality. Media tends to burn well in all drives (Verbatim), burn ok in a certain few or just be all round junk.

Ok so my GH24NS95 drive arrived. It's definitely 'Slient Play' that's causing it... plus some weird goings on in the firmware (probably bugs unless it's faulty by design). Certain things seem to make the drive spin down to 1x speed (from it's initial 2x - 6x) and no amount of trying to increase the read speed back to max (or just anything other than 1x) actually works. The drive accepts the commands to change the speed, it just doesn't actually change it! I believe I've found a workaround so now I'm just messing around with it. It's looking good so far though...

What message did you get from regsvr32?

The current date/time is used if you don't manually specify a date/time.

Stay safe and just leave it where it is. It'll potentially help stop certain nasty things from happening on your PC. Instead, right click 'Command Prompt' (Start -> All Programs -> Accessories -> Command Prompt) and select 'Run as administrator'. Now type that same command line (regsvr32 mscomctl.ocx) in there and just press Enter. If you still get an error, tell us what it says.