LIGHTNING UK!

Your drive made a duff burn. The disc didn't close properly and so the TOC (table of contents) was messed up. That's why it then said the disc layouts do not match. By all means try another disc. If the same happens again, check your verbs are the 'made in Singapore' ones. You could then try cleaning the drive. If all else fails (even a totally different spindle of verbs), consider purchasing a new drive - yours may have developed a fault.

Indeed, there's nothing stopping the program from working under a non-admin user. In fact, more of it would work on Vista as a standard user (UAC turned on) because you're still allowed SPTI access. Even if some things don't work (maybe the 'computer information' stuff?), it should still load up and work just fine but with reduced functionality.

Thanks, I'll get round to uploading it to the site tomorrow, honest!

I realise that. I'm just saying that even if I have the same model drive as you, it doesn't mean they'll burn EXACTLY the same. The age of the unit, environment it lives in, amount it's been used etc also plays a part. Likewise, you can burn and scan 50 discs from the same pack and none of them will give identical results.

Have you mentioned this to the DVDInfoPro author?

It'll be down to the same problem - whatever that might be! Currently, I only display the 'Creating Graph Data Thread...' text when the program is about to burn something. If it takes 11 mins for your machine to create the performance counters when you burn it'll take 11 mins when you read too.

No 2 drives are the same, no 2 discs are the same.

I'd say to give up then and stick to using the software that works on your system.

Discovery mode wouldn't be any different to Write mode. I assume that to erase the disc you did actually use Tools -> Drive -> Erase -> Full, yeah? Does the drive still say 'DVD-ROM' when you look at the 2 bitsetting options for DVD+RW media in the bitsetting window? Beyond that I really have no more ideas. Go and speak to the firmware hackers at cdfreaks and see what they have to say.

Nope.

Check your CPU usage when it's burning too. Is it high?

As mentioned above, you can tell ImgBurn to use ElbyCDIO for its I/O interface. You could also try telling it to use the 'Incremental' write type in the settings.

So there's some issue with creating the performance counters on your pc. Take a look in event viewer and see if you can spot any warnings / errors around the same time that you started a burn.

Once you've told the drive to perform bitsetting on DVD+RW to DVD-ROM you'll need to do a full erase in ImgBurn. Unlike with DVD+R, booktyping on DVD+RW doesn't appear to happen when you write to the disc normally, it does it when you complete a full erase.

Thanks for keeping us updated. If they went into details, please feel free to share them!

Yup, just delete both.

Never gonna happen, sorry!

Yes that's fine. Of course if it's failing in this same place all the time then test mode isn't going to make any difference as nothing has been burnt onto the disc. Can you also please attach the cue file you're attempting to burn (you might need to zip it up).

Are you able to burn other audio images (CUE files) with ImgBurn? Please try burning it again, but before you click the 'Write' button, press the F8 key to enable debug mode.

Those logs are the same ones. Where are your Verbatims from? The ones made in Singapore are the best. You could try burning at 4x but then it might just be that your drive needs cleaning / is on its way out (that model is getting on a bit now!)

original silvers ones that you buy.

That blank disc doesn't look blank - i.e. it's been used before and something's failed. Put a new disc in and try again... then post the new log if it still fails. That said, basically all you do in these situations is update the firmware on the drive and switch to decent discs (Verbatim or Taiyo Yuden).

Right well that one looks ok so now I need another one... Click the same 'Image Information' button you did just then, but this time hold down 'control' (CTRL) whilst you're doing it. The program should then actually analyse the files before bringing up the box. Another scrolling screenshot of that one would be very helpful

Check your 'Filter Drivers' then - look in the Tools menu.

So delete that one then.