LIGHTNING UK!

It's just how new LG drives report the buffer level during a burn. I don't know why they've started to do it (just report 50% rather than 100%) but they have - my BH12LS38 does exactly the same. If you require a more detailed answer, you'd have to contact LG and ask them why the drive behaves like that. It's a hardware thing, not a software thing. Maybe it's a bug in the firmware or maybe they've done it on purpose.

It's not a 'problem' so to speak, it's just what the new LG drives seem to do.

Do all 3 of the options listed under 'close'. There's nothing more you can do.

We need to see a log please - as per the pink box up the top

There's a thing called 'dc erase' but it only works on Nu-Tech drives.

By the looks of it you could do with installing some extra memory in that machine. There's hardly any left when you load the program and then you're telling ImgBurn to use a 71MB buffer. Had your buffer levels not depleted like that, maybe the burn would have worked. You might like to try enabling the 'Overspeed' option in the eeprom settings (Advanced Settings within ImgBurn) and burning at 4x instead of 2.4x.

It compares at sector level (and byte level within each sector). Although it is semi aware of where certain files start/end on the disc, it doesn't work with the individual files or just compare file data between what's on the disc and what's on the hdd. When using Build mode, the virtual disc image (file system + file data) is constructed on-the-fly in memory and fed to the common burning code (that burns disc images - i.e. Write mode). Whatever it does to your files (in memory) during the build/burn as part of making up that virual disc image gets repeated during the verify phase.

Put the buffer size down to a lower value. The default is 40mb and you appear to be on 512mb.

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

Right click the drive selection drop down box. You'll find the option on the context menu. Or you can do Tools -> Drive in the menu at the top. Or you can click the little icon down the bottom right with a cog and box with a tick in it.

Where were your discs made? Look on the packaging. The ones from Singapore seem to be the best. I'm sorry but there's no magic fix for the issue. You're doing things the drive/media were never designed for.

Try turning off 'Perform OPC Before Write' in the settings and use the 'Advanced Settings' feature to 'Clear OPC History' from the drive's eeprom. If it still failing, yeah the drive is probably faulty.

Doesn't your player support both formats? Normally it's NTSC players that don't support PAL, not the other way around. My PAL ones have always supported NTSC. For that reason, I've never had to convert between the two and can't actually help you with your problem. You'd be better off asking your question at a video related forum - Doom9, Videohelp etc.

Turn off the 'overspeed' eeprom option and try again.

The app works fine in XP and playing stuff is nothing like burning stuff. I can't help you if you don't provide more info. Can't you put the drive on the real motherboard SATA controller? Which controller card do you actually have?

Sorry, no. It's a Windows only app. I understand you have things like Parallels and VMWare Fusion available to you though. There might also be a way of getting 'Wine' installed and it can run via that - just as it does on Linux based operating systems.

I've no intention of doing anything Metro related.

I'm not seeing a hang at 'finalising disc' in your log. You aborted before the 'sync cache' command was sent. If the 'sync cache' command hasn't been sent, the burn hasn't finished and the program is still burning (or waiting for something). You'd have to capture a screenshot of the main window so I can see the current status. Can you reproduce the issue by burning the exact same project again?

That would be due to the new XGD3 disc format - support for which was added in the 13146 dashboard (May 2011). This isn't an xbox forum. If you want all the details on it, please visit one of those instead (or just Google it).

You'll have to burn them back onto 8 CDs then. CDA files don't actually exist, they're Microsoft's way of making a pointer to to the raw CDDA sectors on the disc. Just drag+dropping them in Explorer won't do anything. ImgBurn can't magically make 8 Audio CDs fit into 1 - unless only 1/8th of the space is used on each original disc (highly unlikely!)

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

I'm guessing the original CDs were playable in a standard Audio CD player... if you've 'ripped' the discs (to mp3 files or whatever), that's not going to still be the case and that's why you can now fit 8 discs worth on 1 disc.

Try another full erase on the disc too.

There will be a message in the status bar of the main window... that's what it's doing and what your system is stuck on. It's probably due to the controller you've attached the drive to.

Some errors are expected, don't worry about them - and don't keep watching the I/O debug log, it's not meant for end user consumption and will only make you paranoid!