LIGHTNING UK!

That disc looks like it has already been written to.

Multiple burns at the same time are fine if your machine can cope with it. If you can use the Write Queue (i.e. you've already made the images), an autoloader (not duplicator) would save you having to be in front of the PC changing discs etc.

That's great. Now, did you actually have a question? If so, perhaps you'd be so kind as to provide us with a useful amount of information. You could start by posting a log - as per the pink box up the top

What controller have you attached that drive to? Maybe it doesn't support ATAPI devices. At the moment, your drivers are rejecting the most basic 'Inquiry' command. I don't even think it's reaching the drive at all. You could try following the DMA post in the FAQ and uninstalling your IDE ATA/ATAPI controllers from within Device Manager and then rebooting.

There's a good chance that disc is copy protected... and ImgBurn can't read copy protected discs.

Burnt by a LiteOn then I assume

What was written under 'Disc Control Blocks Information' then? One is for (used on/by) DVD-R, the other is for DVD+R. So you shouldn't ever see both

Yes (or No ) If it's present on the disc (only some drives write it - and it's nothing to do with the software used), it'll show up in the disc info box on the right (in Read mode at least). It should either be under the heading of... Recording Management Area Information or Disc Control Blocks Information

The madFlac one works just fine - and that's what's recommended in the guide. The less formats supported by a codec (or rather the tighter its focus), the less chance there is of it messing something else up.

Can you post the entire log for that session and not just a snippet please. Thanks. That said, there's nothing I or the software can do if your drive just wont burn stuff. Perhaps there's something wrong with it?

I suggest you read the thread we linked you to again. Your log shows the burn+verify was successful.

http://forum.imgburn.com/index.php?showtopic=12200

If you read the guide, sure. http://forum.imgburn.com/index.php?showtopic=5555

You do the combining in DVD Shrink, not ImgBurn.

It can write single session/track MDS images but that's it.

Copy + paste everything from the log window when it's at the point it won't get past please.

The problem is exactly what it says. ImgBurn doesn't create an MDS for CD discs so I assume the image came from elsewhere. Mount it in DAEMON Tools, use ImgBurn's Read mode to make a new BIN/CUE image and then burn that.

Download the SPTD installer from http://www.duplexsecure.com/ Run it and select uninstall. You're using an old version of ImgBurn btw. You should update it.

If the aone golds were ok before and this batch uses the same dye as the old ones, maybe you just got a faulty one? Try your luck again with the aones. If they fail again, try the verbs.

That was another max speed (6x) burn. You should try the other supported speeds - 3x, 4x. (As Cynthia hinted at in post #4) Then read this: http://forum.imgburn.com/index.php?showtopic=8000

Then you might like to try the 5.22 firmware update available here: http://www.firmwarehq.com/LG/GWA-4161B/files.html Try cleaning the drive with a cleaning discs too. If it still doesn't work after doing those, you should take ianymaty's advice from post #3 and invest in a new drive.

Post the log please - as per the pink box up the top

Out of interest, what machine did that drive come in? Something made by HP?

The real info you need is in the ReadMe.txt file. Why are you using Build mode to copy a disc? Use Read mode. /EJECT ejects the device you're reading from or writing to. You're outputting to an image file so there's no 'device' being used. (The 'source' is not a device)

For the stuck device, read this post in the FAQ. http://forum.imgburn.com/index.php?showtopic=59&view=findpost&p=972 As for the crash... what does it look like? Are you prompted to send a crash report? Thinking about it, how are you even able to close it if it's stuck waiting for your system/drive to process a command? You might just be running into a standard Windows timeout where it asks if you want to close and restart the app. Post a screenshot or something that will help us see what you're seeing.