LIGHTNING UK!

What makes you think that? On the off chance that you're trying to burn a 9GB image, I have to just remind you that ImgBurn doesn't compress anything. It's simply a burning tool whereby what goes in = what comes out.

Blimey, that drive is about a thousand years old. Rather than keep buying new discs you might like to think about replacing the drive instead. When it says erase has failed, are you presented with any sort of error box before hand? It's strange that it would error out and not actually log an error message!

In what way exactly? What does it say it's doing when you think it's hung?

If you can't find a firmware update, clean the drive or buy yourself a new one.

I don't know how it determines empty from full so I can't really help here. If in doubt, I guess use the full format option. Quick erase would just write a bunch of zeroes to the first few hundred sectors.

You can't.

For log files, look in the 'Help' menu within the ImgBurn application. Terminating imgburn forcefully doesn't normally solve any issues. If the drive has got stuck doing something then it's not ImgBurn that's hanging, it's the entire I/O system. ImgBurn is simply waiting for a responce to a command it issued to the drive. When it gets one it'll carry on as normal. You might be able to fix this issue by updating the firmware on the drive or by switching to some decent media that the drive doesn't have a problem with.

You can't I'm afraid, there are no such options. Use the GUI, make an IBB file (project file) and use that via CLI if you must.

post a copy of the log. Normally it's a case of updating the drives firmware, slowing the burn down or using different discs that your drive actually likes.

Not wanting to get your hopes up, I'm 110% sure it'll never be made open source - even after I've finished with it / died.

ImgBurn offers the same functionality as that booktype tool within it's own booktype options. It can also adjust the overspeed, hyper tuning etc features.

The drive does it anyway when you send the first write command to it - so it's totally optional.

ImgBurn won't copy discs that are protected, so no it won't copy Buffy. PS2 games are not protected against copying but the console won't play backups unless you 'tweak' it - and that's not a topic for this forum.

As it happens, I've already implemented new code for such occasions. If the disc isn't empty, it no longer uses the LB info. Of course that isn't an issue at the write stage (rather than calculate) because I already know the disc is empty or the write button wouldn't be enabled. That's why it appeared to be a calculate issue and not one with write - but it's actually running identical code both times.

ImgBurn automatically sets the booktype to DVDROM for all discs when burnt with supporting drives (Samsung being one of them). You don't ever need to touch the settings. If you want to leave one as 'normal' (no real reason to), you'd need to turn off the automatic bitsetting option on the 'Write' tab in the settings. When it's OFF, you must then set the booktype manually for every single burn you do.

Ok, this really makes no sense. The MinL0DataZoneCapacity value is calculated by dividing the total size of the image by 2. It should work out to the same as (MaxCapacity - MaxPadding) / 2 There's ONLY 1 way that value can be changed between when it's first calculated and when it's displayed in the debug log - and that's when it's overridden by a forced GUI setting. The forced GUI setting is used twice. Once during initialisation, where it's taken from the profile selected on the media tab. So if you're on DVD+R DL, that would be 0. (It's the Double Layer - Min Sectors value) The other time is when you're building direct to a disc and it's read from the media currently in the drive. So all I can think is that you're burning 2 DL discs, the first has finished but is still in the drive - ImgBurn reads that LB address from it and as this is fixed in place, it becomes the new minimum L0 size value. So the 'old' discs minimum LB is being used as the new minimum in the 'Calculate' function and either you're lucking and ImgBurn can still align some cells with the fixed LB position or it can't (hence the failures you mentioned). You then change the disc to a blank one and hit the 'Write' button. The program has a complete different set of min/max values to work with and everything works as it should do. *Technically*, ImgBurn isn't doing anything wrong as it's basing it's calculations on what you've provided it with - i.e. a burnt disc!

It is indeed odd... maybe I'm making up random numbers if there's no disc in the drive and output is set to 'Device'. Now I have more info to go on, I'll look into it. Thanks

The 'Current Media (For DVD+RW Media)' is for DVD+RW media only (hence the name!). You need to change the one that says 'Drive (For DVD+R DL Media)'.

hap e burf day

If the manual methods don't work, the auto one won't either (as it automates the same functions). Are you really using DVD-R DL? You can't booktype DVD- (minus) media.

I believe it is a liteon drive, yes. As to why bitsetting from that tab won't work... I have no idea.

If there's no disc in the drive it goes by the details on the media tab for sizes of media etc. Those values are changing and they shouldn't do because they're read from the media. If the min/max values are different, so will the LB ones be. So if you calculate when there's a disc in the drive, they'll come out the same as when you hit the write button - but possibly not if you calculate when there isn't. So switch back to 'output' -> 'image file' and look at the Advanced -> Media tab. You may find your 'double layer' profile doesn't match the media you're using.

ImgBurn is burning tool, not a transcoding / authoring tool. What goes in = what comes out.

The Samsung drives don't tell you what the current setting is - hence why it says the drive doesn't report it. You can only find out after the burn has actually happened. Is should all be automatic now so just forget about it and burn.

Did you change something? It seems to think you did.