LIGHTNING UK!

The verify screen applies to all modes. That option (of multiple copies) is not common to all of them, so it wouldn't really make sense to put it there - and that's exactly why it's not there already. I've thought of all these things before you know, I do try not to be stupid

Ok, IBB file has been updated to include the stuff from the 'Bootable Disc' tab too.

A 'Remember MRU Tab' option has now been added to the settings on the 'Build' tab for this. btw, as you'll see from going mode to mode, the tabs were actually reset on purpose (so it always went back to the information one), rather than it just not remember what you were on.

ImgBurn doesn't do CDDA images / discs so I'm not sure how useful it would be.

Those profile things are really just for dvd video double layer burns etc. It's so it knows when to start looking at layer breaks etc. I didn't add the bootable stuff into the IBB because I didn't see where it would be useful! If you're saying it is (which obviously you are), I'll add it.

Ok, simple enough fix. In the mean time, you can just press 'ctrl' whilst dragging. It'll then accept it.

I'll take a look and see what I can do / why it won't work anyway.

It's highly unlikely this will ever be implemented. There are just too many options to consider for each 'build' and it would be a crap implementation if you couldn't vary the options between queued items.

Well put it this way, there's no other possible explanation for the patterns we're seeing in your log! Exact same verify errors in different (but matching in terms of IFO -> BUP) files. Same bytes being changed in the vobs... it would just never happen like that in real life unless something was changing bits on the fly.

If you read the disc in the OS, probably nothing bad. If you read it in an old standalone that only has enough memory (and coding) to read 8 levels, it'll either crash or just not see those extra folders.

Did you take note of this warning? It looks like it's being edited on the fly.

@lfc, DVDInfoPro can create iso images in the same way DVD Dec used to. @Rosco, It would help to see the log from this failed verify of ISO1 so I can see exactly what's changed and where. ISO3 would be different from ISO1 + 2 because it has a totally new filesystem. Remember it's not reading sector by sector here (as other 'image' building tools would do), it's looking at / reading the files and then compiling (building) a new ISO from scratch.

There's nothing to verify, that's why it doesn't do it. It's not going to check your pc can write to the hdd properly, that would just be silly and way OTT. It verifies cd/dvd media because it's a well known fact that things always go wrong and quite often the drive can't read what it has just written (due to crappy media). As for batch building, this is very unlikely to ever happen. If you must batch build, look at some of the command line stuff in the readme.txt file.

This is probably on purpose as I have to actually issue commands to close that window. I do this kinda thing to prevent things from happening that shouldn't happen - i.e. being able to edit the queue at times when the program really won't like it being edited. Stay on top just means the other program windows are always behind it, even when they're active and the queue isn't.

ImgBurn can't (nor has it ever) been able to read discs. You're thinking of DVD Decrypter probably - and that project finshed over a year ago. Sorry, we can't help you with this stuff.

I think blu got his wires crossed with the (also new) 'Stats' bit in the 'Help' menu.

Oh, for the changelog I just update a txt file when I've done something worth remembering! It builds up over the 30 or so betas and then I compile it properly at the end and remove the 'between betas' stuff.

Going by the number of options, the log would be huge if I did that - that's why I decided not to! If you have added files to a folder that's then included in the 'source' box, they'll always be added. The ones that wont be are sub folders of audio_ts / video_ts etc. That of course depends on the options you have selected, which takes us back to my first point.

If I add an extra line the entire GUI has to grow and that effects all modes... so it's not quite as simple as that I'm afraid!

I ran out of room, that's why it's not there

It's set to the most compatible settings by default. There's nothing to say devices / OS's out there will support anything but those.

Consider it done.

There is no difference between the two levels so far as one working and the other not. Basically it's luck of the draw. For one you were lucky and windows thought it would try to read the disc. For the other, it decided it wouldn't bother. That's windows for you Sometimes it just needs a gentle push in the right direction.

If it so happens that the same thing occurs when you make ISO files, send me both of them and I'll take a look / compare them.

Blimey why on earth are you using incremental for your write type? The log looks fine, I can't see why there would be a problem with that image. Build an ISO and mount it in DAEMON Tools. Then see if the OS can read it. Also try out ISO Buster as suggested earlier. It may show a problem, if indeed there is one.