LIGHTNING UK!

If the drive is locked for exclusive usage, the program won't be able to do anything with it (the OS handles it and rejects attempts to use it) and it won't get added to the source/destination box. As such, there's no way for you not to have changed it from the bh16 to bh10 as it wouldn't be in the box to begin with.

No, it works with optical drives.

I just meant the 'Verify' checkbox that's enabled by default (meaning you've disabled it) in the 'Destination' box in Write mode. The disc appearing empty is totally down to the drive. It's messed something up, either in writing the disc or in reading it, and is therefore still appearing empty. ImgBurn simply reports what the drive tells it.

You should verify your burns. It'll pick up on issues like this. Don't think that just because a drive appears to support the burnermax commands, that it'll actually be able to produce a working 'over burnt' disc. It's pretty much just liteon drives that can do it - and a specific optiarc model designed for it.

The streaming bit is used to make the drive write to them quickly and not perform automatic write verification. So if it's coming back as unsupported, they may just take longer to burn. A better way of achieving the same 'faster' burns is to format without spare areas - as is the default setting in the program. Could you post the log from that format attempt please?

Your issue is outside of ImgBurn. I assume you've tried turning your machine totally off and on again? It could be driver related. Go into device manager, remove the ide/Atapi controller and reboot.

No, It's not a cli app. The cli options automate the gui, that's all.

Post the log from the burn please.

Exactly.... other computers. The drive in that one doesn't appear to like them. Each drive is different.

Then you should buy another drive. If yours can't burn mkm-003-00, it has problems.

You had this via email, but I'll post it here too. This sort of thing is only ever an issue between the hardware and the media. The software only tells the drive what it needs to write. There are a couple of settings that can be changed that may effect how the drive does its job.... 1. The 'perform opc before write' option on the write tab in the settings. 2. The 'write type' option on the write tab in the settings. You could try it on incremental. Assuming like for like configuration of programs, there should be no difference between them in terms of getting a working disc.

It would appear so. Where did that disc actually come from? As you're just trying to make a bootable USB stick, it doesn't really matter how you create the image you feed into Microsoft's tool, it's going to rip it apart and just put the files on the stick anyway.

There's quite a difference there between the file system sectors and the disc / track sectors. For Microsoft's tool to work, I believe they need to be the same. You'll have to rebuild the ISO using Build mode as you have been doing and forget using Read mode on that disc.

So the image you get from Read mode ('Create image file from disc') isn't being accepted by Microsoft's tool? Can you please post the log from that read operation. Can you also please copy and paste all of the disc information from the box on the right when you're in Read mode with that disc in the drive. This issue is normally caused by the drive padding the end of the disc to a multiple of the ECC block size (16 sectors).

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

Is it a DVD video disc? Is it a pal or ntsc disc? Your issue is not related to the actual burning phase.

That'll probably be due to copy protection.

Sorry, I have no experience of such things.

In a sound editing program. Audacity maybe?

Play around with the hardware read error retries option. The time taken to report a read error is down to the hardware, not ImgBurn.

It's probably the 48khz bit that's stopping it from working. 44khz is normal and that's what audio CDs are.

They must be in a format your machine can't convert. What's the format of them? Open them in mediainfo and have a look.

I'd attempt to crossflash it if I were you. That may depend on the availability of certain files though. Maybe the people on the MyCE forums will be able to help?

The LTS from Drive#1 is wrong... a bug in its firmware or whatever. I don't know why that one works and the other one doesn't though, sorry.

It's nothing to do with what you're burning (a game or whatever), your drive just errors out (reporting a 'Write Error') when it tries to burn them.