LIGHTNING UK!

Yeah basically the burn was so bad that the TOC cannot be read (this is an internal drive function, not something ImgBurn performs) - or wasn't ever fully written in the first place - probably caused by the write errors etc. Nothing much we can do about it. Update the firmware and perhaps change to different media, that's all you can do. You need to find a combo of what works for you.

Your drive might not support SAO (session at once) burning and that's what ImgBurn uses. The drive probably dates back a good few years and ImgBurn just doesn't support it at this time (it probably predates the MMC specs).

ImgBurn will always tell the drive to burn at whatever speed you have selected. It's then down to the drive to say if that speed is one of the 'supported' ones or not. If it's not a supported speed it'll just use (or at least should do!) the closest speed to it.

Blimey that's insane! I thought all the appropriate flags were already being passed to that API so that it displayed the box in the new explorer format. I assumed it would already be resizeable as a default windows thing.... I guess not! (I also see you're not getting the 'places' bar on the left of that 'open' dialog box). Thanks for picking up on it. EDIT: Ah yes, I was correct in my thinking. The box would normally be resizeable from just adding the flag to make it use the new 'explorer' format - only because I've also quite recently added a 'hook' to it (so I can position the box etc) the resizeable flag must then be added manually. This has now been done ready for the next version.

Depending on which one you mean, it's part of the main screen, I can't change the size. Hit the little green arrow and it'll grow a bit. If you mean the std windows open file dialog boxes, they already are resizable. There are too many options within build mode to make a queue system feasible right now.

It's doesn't delete it if the burn fails. ....but, a failure on the sync cache / finalise disc bits is not considered a burn failure. Hence why it says operation completed successfully in the log. That's the bit I need to fix, not the delete bit so to speak.

Sorry, I've been sitting on this new version for a while now. I've not been able to spend much time on it lately and I still have 1 or 2 tiny things to finish off before I can release it. When they're done, it's done.

Add your files and click the calculate button. The Information page tells you the size of the resulting ISO file and what media you'll need to burn it onto (at a minimum - i.e. you can still burn a 600mb iso onto a dvd) If you're burning direct to disc it won't let you burn if it's too big for the currently inserted media.

You've got discs your drive doesn't support. Update the drives firmware or buy some different ones.

There's no reason I can think of as to why you WOULD NOT do bitsetting. So if the drive supports it for SL media, do it. Personally, I see no point in doing it on DVD+RW, but then I guess it depends on how you use those sorts of discs. DVD+R and DVD+R DL, fine, bitset away - and it doesn't matter *what* you're burning.

Did you do what I said within ImgBurn's settings? Click Tools -> Settings. Select the 'Write' tab. Change 'Write Type' to 'Incremental'. Then try burning again. It might work, it might not - it's worth a shot though.

Being DVD-R, Nero will probably burn it using the 'Incremental' write mode so it can pretend to perform a short leadout. Some drives do seem to work better using that mode than when using DAO - even though DAO is more the standard one. Buggy firmware I guess. So you could even try that option in ImgBurn. In the 'Write' tab within settings. 'Write Mode' has a drop down box. Good to see your drive is once again misreporting the supported speeds on the media. Had enough yet?!

The media types tab is nothing to do with the images / media supported by the program. It's purely there so that when you build a DVD DL image (and aren't burning direct to disc) it knows how to deal with the layerbreak.

It really doesn't matter if you've been using those discs all along - what matters is what's happening now (and I'm prefectly capable of looking at screenshots! ) Discs change, drives ware out. For all you know, you could have been right on the edge of creating coasters with all the ones you've burnt. Now you're over that edge and it's all going wrong. The only constant thing here IS the software - so no, it's not losing its mind. Your drive is the one with the problem here. The sizes, speeds supported etc are all read from the drive. What it reports is what gets displayed - end of story. You asked 'what does that error mean?', erm well it says 'Write Error' down the bottom so I'm gonna go with that! Your drive errored out complaining of a write error - meaning it couldn't write to the media. I'm not sure how else I can put it Where did you get your drive from? Was it just in your PC when you got it? What brand is your PC? The first thing you do in these situations is check you're running the latest firmware. http://forum.rpc1.org/dl_firmware.php?download_id=2279 From that link I can see there's a v1.05 available.

I've never actually seen any philips DL media before. They're certainly not very common and that's probably why you're experiencing problems - the firmware hasn't been tweaked to burn them correctly.

It's normal and by design.

It all depends on which button you click in build mode. One browses for files, the other browses for folders. If you ended up with an ISO as a file on the last cd/dvd you burnt, either you used Build mode or the ISO you burnt (in Write mode) DID actually contain another ISO file!

Setting it to 2.4x wasn't why it worked, it just would have worked anyway. Your drive only supports those discs at 2.4x so it wouldn't have mattered what you'd set it to, it would always burn at 2.4x. Sorry to be a pain but this forum isn't the place to ask questions about why your disc isn't working in your 360. Obviously 360's aren't meant to play backups as standard and we don't talk about anything naughty here!

I've done about 60 Verbatim DL discs in that very same drive without 1 failure. So if your drive fails on those too, RMA it!

Try some discs other than TTG02, your drive still doesn't seem to like them - although at least it's reporting some better 'supported' write speeds now. We recommend Verbatim (MCC dye) or Taiyo Yudens.

This one is pretty simple....don't use anything other than Verbatims for DL burning. Ok, they do cost more but at least they work!

You'd also do well to try and burn at a slower speed. 16x over USB is pushing it and that's probably why you're seeing so many of these buffer issues in your log. Try 8x or 12x.

I cannot modify the phyiscal layout of an ISO file. Once it has been made, it has been made! All the file system pointers expect a file to begin / end at a certain position. For a prebuilt ISO a Cell must already just happen to start on an LBA that's a multiple of 16 for ImgBurn to suggest it as a potential layer break position. So that's what happens in Write mode. When you're in Build mode, I have control over the positioning of files so I can apply padding to the file system to MAKE a cell start on an LBA that's a multiple of 16. That's why it gives you more choices. If DVD Shrink makes an ISO and ImgBurn finds a potential layer break position, from my point of view, you have nothing to worry about. When ImgBurn cannot locate a Cell to use for the physical layer break, it WILL tell the user. This issue is not limited to DVD Shrink, any program that makes a double layer ISO would really need to align a cell properly so it can be used for the layer break position.

The balloon only comes up if the app is in the system tray - but it's only there for 10 seconds and so easily missed. The message box pops up regardless of application state. There's nothing in the code to tell it to shove the message to the front of the z order, that's something windows appears to be doing all by itself. btw, I just built a few test images and the 'operation successfully completed' box didn't pop to the front of the z order for me, my currently active window (which happened to be IE) stayed at the front.

You can't erase write once media (WORM) and all DVD+R DL discs are write once media. So if your drive crapped out on the 2nd layer, the disc is now pretty much useless.