LIGHTNING UK!

No, it's how the DVD+RW disc format works. Like I said, a new DVD+RW needs formatting before the drive will accept any 'write' commands. It's probably why DVD+RW support 'direct overwrite' and DVD-RW discs need to be erased before you can write to them again. If you send a 'write' command to the drive and an unformatted disc is in it, it'll just error out and say the disc hasn't been formatted. ImgBurn always tells you exactly what it's doing... that's how I like it. Other software may not mention there's an unformatted disc in the drive and just format it in the background... but that doesn't mean they don't also need to send the 'format' command before sending any 'write' ones.

I found the problem, it was due to the label control losing focus when the open/save dialog box pops up... but it wasn't losing it entirely, just enough for a certain bit of code to not get called. When it totally loses focus the progress bar and character count get set back to zero. If it had focus, the progress bar and character count would have been updated when the project changed the value of the labels. Being stuck somewhere in the middle of the two, neither of those happened - doh!

You can't. Mount the NRG in something like DAEMON Tools.

If it does that 10 times out of 10 (using new discs each time) with each OS, I may start to believe your machine is lying about the error.

DVD-RW don't need formatting, just DVD+RW.

They don't need to be formatted before use, just DVD+RW.

The formatting thing is a drive / media requirement. If you try to issue 'write' commands to a drive containing an un formatted DVD+RW disc, the drive will just error out saying it hasn't been formatted. ImgBurn takes care of the formatting process automatically and the discs should only need formatting once. After that, you can just overwrite whatever's on them.

Liteon drives do that sometimes. Powering them down fixes it - just as it did for you

I wouldn't expect a real 'write error' to be anything to do with the OS you're running. They should be the result of your drive not liking the discs you're attempting to burn to... so purely a hardware thing. 'RITEKF1' aren't good quality discs. Perhaps try burning at 4x instead of 'MAX' (8x) ?

You can't build an Audio CD image with ImgBurn, it'll only burn one directly to disc. You could burn to disc and then read that disc back to a BIN+CUE image.

I'd already tried that based on what you'd said in your initial post.... but.... I was loading the project via the 'load most recent project' option as it was easier It works fine when doing that, but not when using the actual 'Load project' option. I'll will dig a little deeper now

You can set the initial folder of the DLE window in the Settings -> Build tab -> Page 2. Otherwise it starts at the 'Desktop' level.

85 I believe, not really that many.

Sorry db, I've been unable to reproduce this. If I load a project file with a different value in the volume label fields to what's currently configured in the GUI, the character count and progress bar get updated instantly. I tried it loading an IBB with the volume label field being the currently selected/focused (and visible), and also with having switched off the 'labels' tab. The progress bar and character count changed straight away when the labels tab was visible and also when it wasn't. Is there anything special I should be doing to reproduce it?

The program should start up in whichever input mode you last used. It does default to 'standard' if you've never used it before though.

Nope, it goes on the disc 'as-is'. You have to use Advanced input mode for that.

I'm not going to change how it works. It simply isn't worth it.

Use the current version of the program. Try both write speeds your drive claims it supports that media at - 4x and 8x. Invest in some better discs - verbatim or Taiyo Yuden. The 'RITEKF1' discs you're using now are just cheapo / low quality ones. Try cleaning the drive with a cleaning disc and just replace it if it fails to burn the decent verbatim / Taiyo Yuden discs too.

That may well be something I haven't considered. The event that gets called when the field is changed manually probably isn't firing and thus the values / bar aren't being updated. I'll check it and fix it. Thanks

I added each one individually.

The CCD references the IMG file and you only have to select the CCD, ImgBurn does the rest automatically. ImgBurn doesn't make use of the SUB file though, you'll need to burn the CCD with CloneCD (which is what made the image in the first place) if you need accurate subchannel info (and you may well do).

Just click ignore twice as you appear to have been doing anyway. Tracks recorded in TAO mode often have 2 unreadable sectors at the end of them.... I'm not sure why the software isn't dealing with that automatically, I'm pretty sure it does normally! Have you tried reading the disc in your other drive?

It isn't a stopwatch you can just 'pause', it simply compares the start time to the end time and the duration is whatever the difference is.

1. Please post a log where I can see the actual error. It's saved automatically when you close the program. Access it via the 'Help' menu. I can't help without the proper / full error details. 2. Where are the files stored that you're burning? Is it a slow / external drive? It's taking quite a while to read 500MiB from it. So that's 22 seconds to read 500MiB = 22MiB/s Then during the burn when you run into buffering issues... So that's 48 seconds to read 500MiB = 10MiB/s It's then taking over a minute for the seemingly excessive drive activity to subside. Either your source drive is busy with other stuff or it's just plain slow.

Update ImgBurn and try again.