LIGHTNING UK!

Making an ISO from scratch is actually quite hard DVD Decrypter didn't build one from files, it read the sectors into one. The two are VERY different! This will happen one day, I'm just not sure when. I may even do a temp version using mkisofs or something.

Damn it! I've been through all my spindles and didn't find any TYG02's I've got some old TYG01's and some Yunden000-T03-00... they're about the closest.

Maybe they're fake TY discs?! I can't imagine the real thing bombing out on you all the time like that. I'll raid my cupboard and see if I've got any with that media id, and then try burning a few of them myself.

No, they're two separate programs and will continue to function as such.

Look at the 'Supported Write Speeds' bit in the information panel on the right. Your drive/firmware/media combination is the limiting factor. The program will always try to set the drives speed to the one you tell it to. It's up to the drive to use that speed or one that it DOES actually support.

Cheers, yeah I'd noticed myself that the logic was VVVVERRRY wrong for this! I don't think I'd actually changed it / updated it for ImgBurn supporting queues. It has been fixed for some time now in beta versions. I hope to have 1.2.0.0 out soonish.

I'd be amazed if you could burn 5 with ImgBurn, have them all fail, burn 1 with nero, have it work and then burn 5 more with ImgBurn and have them all fail. The odd one here and there is just drive / firmware / media issues. The burn has started - which means its not a program issue. After that point, there is only one way to get the drive to write stuff - by sending lots of write commands. In that sense, which program you use makes no difference. Manufacturers tend to do more work (firmware wise) with current media - i.e. stuff that burns at 16x. So take spinningwheels advice and try out some newer media. The cdfreaks forums will give you a good idea of what works and what doesn't on Liteon drives.

http://www.benq.co.uk/serviceandsupport/do...duct=750&type=B Down the bottom of the page... BSOB firmware. That other firwmare site might not have it listed yet.

You can have the program autosave the log (to a unique file) when it closes. Just look in the settings. That's the best I can offer right now.

The content of the file is irrelevant. The drive just sees it as data, it doesn't know/care what it is. The program itself works fine with the drive, I have a 1640 myself that I perform testing with - that said, I'm running BSOB firmware. So... update your firmware and try again.

Show us a log of you actually burning something. It's handy if we can see the error. btw, your drive is probably a 1640 - as 1240 doesn't exist!

My previous post still stands. For you, it could be as simple as ejecting and reinserting the disc.

If you're going to ask for help, please at least be using the correct program! Try getting some other media. A quick look over at the LiteOn forum on cdfreaks.com should show you what works and what doesn't on those drives.

It will already do this as part of the 'calculate optimal' option. To see where it thinks it will go, select tools -> iso -> display ifo layer break information.

No idea what's causing the problems you're experiencing! The only time discs don't work on players is if they don't support the media. It could also be you're using DVD+R and not bitsetting to DVDROM. Make sure you use quality media, cheapo stuff often works at the start, then gets progressively worse towards the end. Show us the log of you burning a disc and maybe we'll be able to spot potential problems.

ImgBurn can't be used for burning audio cds.

Your drive's firmware doesn't support the media you're putting into it - or at least it hasn't been able to initialise the disc on that attempt. This is a hardware/firmware/media issue.

'Verify' always comes in handy here too!

When it's ready

It's in the 'File' menu too.

Unlikey, software plays no part in the burn quality - unless it's turning on/off special drive features - which ImgBurn doesn't touch. Why don't you use the 'Graph' feature in ImgBurn to see how it thinks the burn went. It may at least show you where the drive was slowing itself down.

please copy + paste the full log.

bin files come with a cue file - because they can be complex images. You should use a CUE burning program for them really. If ImgBurn can't burn the bin directly, it wont be able to burn the ISO version of it either.

The next version already has support for burning to different drives, one after the other. As for suggestion 2... something will happen eventually but I'm not sure what.

Image content is not really relevant. The program 'should' burn anything. If it's not, you may need to update your drives firmware / buy better media.