LIGHTNING UK!

It's probably down to whatever drivers you've got installed for the controller the drive is connected to.

Go back and verify that first disc again in the standalone 'Verify' mode. As you burnt it from files (via Build mode) you'll obviously need to uncheck the 'Verify Against Image File' checkbox. The PIPO scan for the disc looks fine so I'm not really sure why the drive would be returning L-EC errors when ImgBurn attempts to read those sectors. As software has no say in the burn quality you might like to take this problem to the optiarc forum over at cdfreaks, where fellow 7191A users can comment. It is of course not unheard of that some drives perform better on certain media as certain speeds - especially where new drives are tailored to burning quickly (to the point of overspeeding) on the better MID's. btw, you're probably better off (for the sake of accuracy) doing PIPO scans at 4x on that drive.

No, the nero log won't help. It's enough to just change the Write Type in ImgBurn and try again.

Your drive doesn't appear to like those discs and is just reporting a 'Write Error' when it tries to burn them See if you can locate a firmware update for it. Where are those verbatim discs manufactured? (look on the packaging) If all else fails, maybe now would be a good time to invest in a newer drive.

Burn one with test mode switched on and see if it then reaches full speed. If it does, it would appear the drive is slowing itself down as a result of WOPC (i.e. it's determined the burn quality sucks and it's trying to correct it). How are the buffers up until when it slows itself down? Are they on a steady figure?

It's a known problem with wv files, the program isn't treating them as files that need decoding. It's fixed for 2.4.2.0

To add to number 1, it doesn't support multi-session so there's no point in leaving it open.

It's no bug, I can assure you of that. If your drive won't burn nicely in DAO mode, switch to Incremental in the settings (write tab). That's what Nero seems to use. If that works, your drive is just duff. It should work equally well with both write types.

Shop online for discs, it's much easier!

Data discs don't have layer breaks.... well, the disc always has a physical one but you don't need to do anything special with it - unlike for DVD Video discs. If it's freezing all the time then your player probably can't read the disc properly - no software will fix that. You need a nice drive / firmware / media combo to get good burns. For DL stuff you should only be using Verbatim DVD+R DL media. The 2.4x (MKM-001-00) stuff works best - and look out for 'MIS' (made in Singapore) as the ones from other places aren't always as good.

Is this the problem? I've no idea what that error message translates to but it's probably 'Access Denied' and that's covered in the FAQ. Basically you've got another program running that's using the drive and ImgBurn can't lock it for it's own exclusive usage.

This isn't really something that interests me right now I'm afraid. It's probably easier if you just adapt the little program you wrote so it feeds the list of folders / files to ImgBurn instead of mkisofs. ImgBurn's CLI stuff is detailed in the readme.txt

ImgBurn doesn't compress anything, so no, that's not possible.

We can only see the same things you can. The drive errored out during the write and said that there was some form of 'Write Error' - that's to say, it couldn't burn to the disc. It's an old drive and the media is quite new... I'm not even sure the drive really supports it, hence the single '4x' write speed being offered.

There is no queue for build mode, nor can you make the program spread files over multiple discs. That basically leaves you with option 3. Just call ImgBurn 4 times via CLI (1 at a time though obviously) and pass the name of the project file or list of the files/folders to backup.

You only change the transfer length to fix a very specific problem / error - and it's not the one you're having.

If it's 912MB, I guess that answers question 1 - you need to use a DVD. An ISO can only be burnt onto 1 disc, it doesn't span them.

Maybe the drive is failing?

There's an option in the GetOpenFileName API function flags to not change the current working directory of the parent process. I added it to ImgBurn some time ago but apps that don't will need to be closed before the handle to the folder get released.

Check with the manufacturer of you laptop and see if there are any firmware updates available for your drive. Then try getting some different discs - either Taiyo Yuden or Verbatim.

Thanks, that was very generous of you I'm not sure my answer was worth quite that much though

Is the disc actually in the drive at that point?! (of course it *should* be unless you've removed it) The drive doesn't think it is.

What's the message in the status bar after the tray has been ejected / inserted and you've waited for 30 seconds / 1 minute? Get some of the 32x ultra speed verbatims. My 760 doesn't have a problem with those.

It burns in the first phase, then it verifies. Keep the log window open, it tells you what the program is doing.

pxhelp20 is a very common filter and it's probably best that you just make sure you've installed the latest version of software that uses it (even WinAmp does) rather than removing it.