LIGHTNING UK!

This has been fixed in the most recent release. Also, have you set the 'Write Type' to TAO for an actual reason or were you just messing around? Put it back on DAO/SAO.

That's just nit picking really though isn't it

It has to add itself to whatever's the current default application (basically treated as a redirect) because otherwise it doesn't show up as an option in the menu. If DT used something like DAEMON.Tools.Pro.ISO\Shell for .ISO files then it wouldn't be an issue. They have their way of doing things, I have mine. So I'm sorry but this is by design and I don't plan on changing it.

ImgBurn doesn't associate itself with MDX files. What you're seeing is probably a result of an MDX burning program using a single generic registry key to deal with all of the files it supports... so when ImgBurn adds itself for a different format, it's being included with that one too.

If your drive can't initialise any discs (blank or otherwise), it's probably dead.

Did you do it from scratch or just a little update for 2.5.6.0 ? To be honest, keeping up with the credits is a nightmare in itself and I'm very tempted to just ditch that column from the website.

You only think it's weird because you clearly haven't done any reading around/homework/research on that stuff in a long time. Knowledge about anything technical goes out of date very quickly. If you don't keep up with it you just revert to 'n00b' status.

On an unrelated note, there's a newer firmware available for your drive. http://www.firmwarehq.com/Lite-On/iHAS322%2B8/files.html

No such thing exists for Blu-ray. It was a flag set in IFO files and of course they don't exist unless it's a DVD Video compilation. If you're getting a pause with Blu-ray content on DVD then it's down to your player not using a sufficiently large buffer (or a difficult to read disc).

Show me a log where you've actually selected the 'Truncate' option rather than the 'Overburn' one.

That's the sole purpose of the pinned topic dealing with language file differences

I'm not seeing any attempt to 'truncate' in that log, just 2 attempts at overburning - which I'd expect to fail and it's therefore perfectly normal that it is/does.

Can you provide a screenshot of what you've actually got (from the camera) file/folder wise?

Why and where would such an option be useful?

Nope.

You should install the latest ImgBurn. What you're doing (reading a multisession/track DVD disc) will never work with previous versions of the program.

Ok so if it's intel you probably need to install the latest Intel Rapid Storage Tech drivers.

Update the drive's firmware. http://www.firmwarehq.com/Samsung/SH-S223C/files.html 2x isn't a supported write speed for your drive/firmware/media combo. Because of that, the drive would be using 4x - but 4x might not be the optimal speed for your drive/firmware/media combo. What controller is that drive connected to? Who makes it? Intel, AMD, Marvell etc. The drivers for it are blocking the booktype command. Updated drivers may fix that. btw, different versions of the program don't make your drive better or worse at burning a disc. Burning just doesn't work like that.

Try enabling the 'Perform OPC Before Write' option. I know exactly which commands CloneCD sends before a burn starts and that's one of 2 that ImgBurn doesn't also send (by default anyway).

Changing colours/shades probably means the laser power is going up and down during the burn - in an attempt to improve burn quality. All you can really do in situations like this is to (Disc Quality) scan the discs using Opti Drive Control and an appropriate Blu-ray drive (something by Lite-On) and make sure no part of the disc has really high error rates - which, over time, could turn into physical read errors (where ImgBurn's Verify phase would then fail).

No, it doesn't do raw reading/writing at all.

There's just no point in doing anything more than I've already done (allowing the configuration of software and hardware retries). SafeDisc is obviously a form of copy protection and ImgBurn will never do anything to get round that. For the odd few discs that are genuinely damaged and cannot be read by normal means, there are purpose built programs for the job - e.g. IsoPuzzle (as mentioned earlier)

Is it a DVD Video disc? (So there's a VIDEO_TS folder on the disc?) What you need is a program that can go from whatever you've got now (the format of the original disc and nothing to do with 'ISO' files) to one of formats YouTube supports. When you figure out what format the disc is in, the rest should be easy to Google.

ISO files are for burning to disc, you don't put them on YouTube. You've probably gone about things the wrong way. What's on the disc in the first place?

I believe the drives use a different laser for CD/DVD burns to BD ones, so one working and the other not working is perfectly possible. Anything is possible. There's no magic fix for when a drive keeps failing to burn discs, you just have to try and bunch of things (media, firmware, write speed, actual drive etc) until you find a combination that works.