LIGHTNING UK!

One was probably a CD image.

This the luck factor kicking in. Of course luck could be working in either direction so maybe you were unlucky on the ones that failed rather than the other way around as I mentioned earlier. Do check the state of the burning surface before you stick the discs in the tray too. Often they have dirt / dust on them and that would cause the burn to fail. Your drive would only ever burn at 4x max as that's all it can handle. Physically setting the write speed to 4x shouldn't make any difference.

You've got quite a chunk of weird stuff going on there, rather than just a spike as one would tend to expect. Anyway, the graph shows exact figures with no manipulation going on, we were talking about the value in the log which is captured differently and is averaged ever so slightly. The log value is also the one that I tweaked.

Don't forget that as soon as the disc has finished burning, the 'file handle' is closed and then Windows releases the memory. It's not lost forever

No, there is no timeout logic - also, what limit do you put on these things? a 1x burn could take an hour. Most people would have given up by then. It's pretty pointless anyway as even if ImgBurn closes nicely, the drive still won't respond until you reboot. Drives don't really like stopping mid burn. If you don't issue the correct sequence of commands, you get a 'Command Sequence Error' error! lol Also, you can put the drive in a state where it won't respond to command, in which case you have to reboot - no two ways about it. As such, I made it so ImgBurn still performed the normal functions it would do if it were a successful burn. ('Normal functions' are basically just 'Sync Cache' and then one or more of the 'Close Track / Session / Disc' commands. That's it.) Because there are limits to how much you should burn to a DVD, most of the drives will automatically pad out what you've burnt if it's not up to the lower limit allowed. This is what can seem to take ages. Some drives are nice and provide a % complete value. Others do not.

No 2 discs are ever the same. You could be being lucky when it does burn, and unless you do a proper PIPO scan after you've burnt it, you have no real way of knowing how good the burn is. You could try putting the real LiteOn 852 firmware on the drive, that might be better than Sony's version.

Ok I couldn't find a problem with this so please let me know your thoughts after reading what I wrote earlier.

You could try some other media, MCC-003-00 is 8x rated and your drive only supports it at 4x. That leads me to believe it's just not 100% supported on your drive. Various reports on google etc tend to say the drive isn't very good in it's own right. Shame you're working with a laptop, desktop users have far more choice.

Either way, this is f all to do with ImgBurn and so doesn't belong here.

Just try burning another one. I very much doubt ImgBurn would fail 10 times out of 10 when Roxio works every single time. If it does, let me know and I'll try to see what's causing it.

The third one down is indeed an ISO image. Just like when you double click an ISO file and ImgBurn loads up, the 'Open' button is doing the same thing.

You're circumventing copy protection. That IS illegal I'm afraid. Fair use etc only applies if the manufacturers haven't added copy protection to stop you from copying it. All (well, 99%) of DVDs have copy protection on them. In any case, if you're getting an error during the burn, it's not due to what you're burning. The drive doesn't give a monkies about what's being written to the disc. If you're not willing to attempt another burn, load a disc in the drive and copy + paste the info from the window on the right in ImgBurn.

Yup, no reason for that not to work.

Yeah I could do a 'MRU' type thing for the log folder. As for appending, it is of course possible, but would eventually slow down the saving process due to the way the logs are handled. I'd basically have to load up the entire existing file into memory, add the new log lines onto the end of it and then save it back down to the hdd as a file. I really don't want to have to load up + resave a 100mb text file!

With DVD+R DL, it could be very different. The drive will tend to finish off burning what it needs to in order to make the disc 'compatible'. That could end up being a huge chunk of the disc. In any case, you need to understand that ImgBurn isn't hanging, your drive / the I/O subsystem is. If the drive never returns either an error or a success, the program continues waiting for one. As soon as it gets such a thing, it'll be fine once again.

I don't get a slowdown, some others may do. Up to you if you want to use 1.2.0.0 or not. It's not going to break anything.

It'll format the disc is it's not displaying 'Formatted: Yes' in the info window on the right. You only need to do it once, just do it!

Thanks for finding it Rippraff

If your firmware is already up-to-date, all you can do is buy better media, or at least some your drive likes a bit more.

Ah, if it's intel, that's pretty easy. Just get the chipset INF utility from: http://downloadfinder.intel.com/scripts-df...44&submit=Go%21 Get the top one and install that. For the IDE one, I'll need to know which exact chipset your motherboard uses. If you can get a screenshot of the Device Manager window with that system branch expaned, that would help There is a setting in ImgBurn that will tell you the current state of AutoInsert / Run / Play within your machine. It's on the 'I/O' tab in the settings. Ensure that's ticked. Then you can look at other autoplay settings via Microsoft's little 'Tweak UI' program. http://www.microsoft.com/windowsxp/downloa...ppowertoys.mspx

Sorry, I don't like to make my program work on a drive by drive basis, it makes updating it for new models a right pain in the arse. You can get a little CLI tool that does this whenever your PC boots up. You should be able to find it on cdfreaks forum - in the LG subforum probably.

Yes, this is a burning application. Not much point displaying a DVDROM (which your other drive appears to be) in that drop down box is there.... after all, it's can't burn anything! As you're saying it CAN burn disc (as it's a CD writer), it must not be returning the correct info for what it can or can't do. Please can you show me the 'Capabilities' window (screenshot or something). You do that via a right click on that same box - when in 'Verify' mode - which should display both drives (well, all 4 actually) And after that, press F8 and then restart the program and then save the log to a text file and attach it here please. It'll contain loads more debug information that I can look through. I'll look into why your drive is only reporting it can 'read' things and not 'write' them. Much appreciated

Obviously you're aware that ImgBurn doesn't just have to burn 1 ISO when it's open. I can't specifically save just the part of the log that applies to 1 image being burnt, because it's not stored like that internally - to me, it's just one long list. So, I'm sorry but I cannot do this.

Finalising is just 1 command that's sent to the drive. It's then down to the drive to actually perform that process. All ImgBurn does is poll the drive every second to see if it's finished. When you think it has got stuck, press the F8 key and see if these 'polling' commands are still being sent to the drive. The program only waits for it to finish (continues polling) if the drive reports any 1 of 3 'status' values - there are LOADS of other it could return if there was a problem, so for it keep polling, the drive really must still be reporting that it's busy finalising the disc. None of that stuff has been changed.

I've found some weirdo documentation in the microsoft DDK (driver development kit) that has given me something else to try. Like the last time, there's no way for ME to know if it'll work or not unless YOU actually try it! You will of course have to re-enable that option in the settings if/when you try out the next version (1.2.1.0)