LIGHTNING UK!

Ok. You didn't actually say that to begin with Your issue isn't really related to ImgBurn / burning. As it burnt and verified ok, the disc should be fine. The rest is down to the source file(s). When you browse the disc in Explorer, what do you see?

what exactly is the problem? It seems to have burnt and verified ok

Post the log please... as per the pink box at the top.

It's nothing to do with the size of the image... beyond a larger image obviously taking up more space on the disc and therefore a larger area over which an error could occur. You've got an unreliable drive/media combo.

What you select goes onto the 2nd layer.

Fair point. There's no way to make it apply for a multi-copy burn. You can work around that prompt via the General tab in the settings. 'Display Warnings' -> 'Overburning'. The program will then automatically overburn or truncate, based on what's selected for 'Default Overburning Method' in the Settings... Write tab, Page 2.

You don't have the right burner for those oversized images. Also, don't mess with the settings. The defaults work fine.

Which process is using up all your cpu time? Is it actually ImgBurn? Burning isn't exactly CPU intensive, so there's no reason for it to be high unless something else on your system is causing it.

Ok so I've checked the code now. It completely masks/hides any errors - it's not really my code that writes out the txt file, it's part of my development environment - and that throws 'exceptions' (which would look like crashes). So you'll just get the success message or nothing - which is what you've already noticed.

It seems to be getting hung up on a different bit now than when you posted the initial log. Perhaps the ATI AHCI drivers can't cope with the lightscribe config request? Are there any updated ones on the website? Can you switch from AHCI mode to IDE/ATA mode and see if that makes a difference?

Do you disable UAC? Admin user or not, that’s what’ll block the program from saving to that folder. It would need to be run in the elevated state (right click, run as administrator) to work. As for returning an error... I’m not really sure if I check for that when saving the IBB. Nothing gets written to the log window, no?

A normal user can’t write to the program files directory.

The checkbox in the DLE window just adjusts the value of the drop down box based on the total size of the files you've added. It is not related to the media that may or may not be inserted at the time.

The % usage in the DLE window is an approx value based on file sizes alone and it doesn't look at the drive or media in it at all. It's based on hard-coded disc sizes, none of which include adjustments for the inclusion of spare areas - which of course are variable. The 'Calculate' feature back on the main window is the accurate one - taking into account all of the options, file system overhead, padding etc. It'll use the available/free space from the inserted disc when it can, but will not (as you've noticed yourself) update the calculated value if you eject/reinsert discs or change drives (even with the 'auto' option ticked).

The file system (udf etc) has nothing to do with any of this. An erased disc has no file system. No additional sense information doesn’t mean anything in its own right. When an I/O command fails and the sense area is blank (no additional sense information), it’s the equivalent of just saying ‘no’ and then giving no reason. Correct, in terms of bad sector reallocation, the zeroing phase is no different to a normal Write operation.

As mentioned in a previous post, I wouldn't have expected the drive to return any sort of failure/error if it's reallocating bad sectors as it goes - assuming that part itself goes ok. It should all be handled behind the scenes and software wouldn't know about it. The drive is claiming a write operation failed, but it's not returning any sort of reason for the failure (hence the 'no additional sense information' return code). So basically, I have no clue what's going on here.

Nope, no DLE editor stuff. Half of it is a 3rd party component though (the 'Explorer' side of things), so it may not be something for me to fix. In the 'Bugs' forum is just fine. Thanks.

I don't agree with that statement at all. Yes, optical discs in general are used less and less these days... but what difference does that make? ImgBurn is a disc burning program. New technology doesn't change what the program is designed for. So long as optical discs are being used, ImgBurn will be a viable option. Obviously it doesn't just do CD, it does DVD, BD, BDXL etc too. BDXL is very much 'current tech' within the optical disc field.

Considering it's been 6 years or whatever since the 2.5.8.0 release, there have been very few verified bugs reported / things fixed. The changelog for the beta (non public) version only contains 7. Your one (within the bd disc info text) is purely cosmetic and would very easily go unnoticed if you don't scroll right through the disc info text / understand what you're looking at.

1. Reallocation of bad sectors isn't ImgBurn's job, it's handled by the drive. 2. Due to the above, you should in theory never get a 'Write Error' when the drive's 'Defect Management' feature is enabled - and it's enabled when a disc formatted with spare areas is put in it. You might get an error if it's unable to reallocate the sectors (spare areas full) or if there's some other sort of issue with the drive/disc. Questions 1. I doubt software retries during the verify phase are going to make a difference to the data on the disc. Adjusting the retries value make the program make that many attempts before then prompting the user. You get rid of the prompt by using the 'ignore read errors' option - it'll still perform X retries before ignoring though, as per the retries value. 2. No... but then what you've said doesn't really apply as the software isn't doing the reallocating of bad sectors. The drive will reallocate bad sectors if defect management is active and it feels it needs to.

Boot into safe mode and see if your system still gets stuck when you attempt to load ImgBurn. Back in 'normal' mode, have you tried uninstalling the IDE/SATA controller from within Device Manager and rebooting?

ImgBurn uses the 'Track Information' values and they're not right either. LTSA is Logical Track Start Address LTS is Logical Track Size So this is just a drive / media combo issue.

Can you copy and paste everything from the disc info box on the right of the main window please?

The program’s verification process would pick up data corruption issues... which is something the drive’s internal one can’t do. It’s up to you really.

Yes, that’s just what happens when the drive burns and defect management is enabled (spare areas are present). The drive verifies as it goes.