LIGHTNING UK!

No, it won't cause any errors... unless of course your drive opts to use a speed that it's not good at burning at. So, your drive may support 4x and 16x on some discs. You pick 8x (which isn't an option) and the drive then decides it'll use 16x (rather than 4x). If 16x produces low quality burns, you should set the speed to 4x instead and hope that's better. If your buffer keeps emptying out, you have an issue somewhere. What can't keep up with the burner? It must be the source drive or the interface (if USB 1 or 2 etc).

Yes, Build mode makes data discs.

Maybe the disc really does have 4 tracks on it ?

Do not touch the Write mode option. It’s on auto by default yeah? Leave it as such or you’ll force the program to think it’s always burning a cd. Basically, the default settings are tried and tested. They’re what works best. ImgBurn always closes and finalises disc’s. There’s a guide for audio CDs in the guides forum. If it doesn’t specifically mention anything in there about settings, you’re safe to assume it’ll just work. Dao/Sao is always preferable to Tao, so that’s default too. There’s nothing in the gui that says if a disc was recorded in Tao or dao/Sao mode. I’m not even sure such a marker exists. Yes, disc and session state/status saying ‘complete’ means the disc has been closed. Opc before Write will make thing worse as often as it makes them better. If it was really that important to issue the command before a burn, the drive would do it automatically. So based on that and years of testing, it’s off by default. It’s entirely up to you if you want to enable it or not. Feel free to do so and scan your discs for burn quality, comparing the two results.

It's down the the drive really. ImgBurn can only go by what it reports. Put the disc in the drive again and copy + paste everything from the disc info box on the right when you're in Read mode.

If that's all it says every time you attempt to use it, and on multiple discs, I'd have to guess that some I/O command(s) are getting stuck being processed by the system. ImgBurn submits them and then waits for a response. Please try following the directions in this post and then provide the log. http://forum.imgburn.com/index.php?/topic/59-faq/?p=972

You can’t manipulate the booktype setting on pioneer drives. Either they do it automatically or they don’t.

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.