LIGHTNING UK!

ImgBurn can't copy Audio CDs yet and if you just dragged + dropped the CDA files into Build mode, that was never going to work as they're not real files.

It'll offer retries. If that doesn't work, no it's not possible.

Switch the 'Write Type' in the Settings to 'Incremental' rather than 'DAO'. It shouldn't make a different but for some system/drive/firmware/media combo's it does. It's also possible Nero doesn't look for / detect errors during these final stages. The program isn't actually doing anything at this point, it's just polling the drive to see if the operation (in this case, 'Sync Cache') has completed yet. The drive reported a 'Write Error' and so ImgBurn simply tells you about it.

I was hoping to see all the info if that's ok! I need to see it from when it *doesn't* work so I can figure out why.

It would appear the drive just isn't initialising the disc properly the first time around then. Eject + reinsert the tray (when you've got one of the blanks in it) and then copy + paste the info from the panel on the right in the main ImgBurn window.

See if changing the write type in the setting to incremental helps. Or change the I/O Interface to Elby.

Yeah configure build mode how you want it and save it as a project file (IBB files) from the option in the File menu. The just read the 'ReadMe.txt' file in the program directory to find out how to load an IBB via CLI. or in the most simple way possible, add something like this to a batch file. ImgBurn /MODE ISOBUILD /SRC "C:\Disc1.ibb" /START /CLOSE ImgBurn /MODE ISOBUILD /SRC "C:\Disc2.ibb" /START /CLOSE ImgBurn /MODE ISOBUILD /SRC "C:\Disc3.ibb" /START /CLOSE Run the batch file and then your images will be created / burnt one after the other.

You can easily get around this current limitation by making IBB files and loading them via a batch file using the available command line options.

When the main buffer is below the value of 'Main' and the device buffer is below the value of 'Device' (for a certain preset period of time), buffer recovery kicks in and waits for: 1. The buffer to refill. 2. The hdd activity (Average Disk Queue length) to reach the the value of 'Avg Disk Q'. (This is a performance counter that you can monitor in the same way you do CPU usage).

All these errors are what the drive returns in response to me sending it some data to burn. They're displayed exactly as reported by the drive. Basically, the drive returns a status (sense) code made up of a couple of numbers (known as ASC and ASCQ). I then translate those numbers into English - going by what the MMC specs say it means. i.e. ASC 0xC0, ASCQ 0x00 = 'Write Error' ASC 0x30, ASCQ 0x05 = 'Cannot Write Medium - Incompatible Format' I don't have any more info than that. If the drive reports a 'Write Error', it obviously failed to write to the disc for some reason. Slow the burn down and/or try other discs until you find some it likes. If it doesn't like anything, buy another drive. btw, stick the buffer back to what it defaults to (40mb). 10mb is a bit stingy for someone with 1GB of RAM!

I just made it adjustable for a laugh! No ok, not really If the machine itself gets suck doing something (more important to it than providing ImgBurn with CPU cycles and access to preform I/O), no amount of buffer will prevent a buffer underrun. A big buffer does mean that once it recovers, the remaining bit will last that bit longer and might prevent further buffer underruns whilst reading from the hdd gets back to full flow. On the other hand, if the machine is reading from a slow (very close to burning speed - but must be slightly fast obviously) source drive, the big buffer can help.

Remember that the brand name stamped on a disc doesn't mean anything, it's the dye that's important. There's every possibility that 2 different brands could use the same dye. So although you think you're buying different discs, you're not.

If one drive works and the other doesn't I'd say the 'other' drive has an issue reading the discs. It could be a generic issue with DL media in the 'other' drive or it could be that you're using crappy Ritek DL discs rather than decent Verbatim ones.

It's... [Host Adapter ID] : [Target ID] : [Lun] (Lun = Logical Unit Number - I think! That's for when there are multiple drives within one device - i.e. when it's a changer or something) A Target ID of 0 would be 'Master', 1 would be 'Slave'. Host Adapter ID can be any given number though so you can't look at it and say for sure it's on the primary channel or the secondary channel. Also note that USB devices are listed as [0:0:0] because this SCSI ID field doesn't really apply to them - at least not under SPTI. Personally I'd just ditch the Sony DVDROM and be done with it!

Try the 1.01 firmware. http://lgodd.lge.com/fwdrv/DVD-WRITER/GSAH50L_101.exe You should also ditch the Ricoh DL discs and start using Verbatim 2.4x DVD+R DL's instead. They're much more reliable / consistent.

You'd use Read mode for that, not Build mode. Build mode is for files on the hdd really.

As you can see from the log, that's the last command sent to any of the drives - and it hasn't been processed. There's nothing I can do about it I'm afraid. The issue is with that Sony DVD-ROM / it's firmware / the cable it's on / the driver etc. Try the S1.7 firmware from here. http://forum.rpc1.org/dl_firmware.php?download_id=180

No, 6x is the slowest your drive can do. That info is shown in the info panel on the right within ImgBurn's main window. Try the KS0B firmware http://forum.rpc1.org/dl_firmware.php?download_id=2056

Unplug all the other drives and just leave the Pioneer in there. It should be on the end of a decent 80 wire cable and the jumper should be set to 'Master'. Look in the tools menu and bring up the Filter Driver screen. Press the clipboard button and then 'Paste' into your next post. If the error isn't from the drive, it must be something a driver is doing. You could also think about doing a motherboard bios update and ensuring you're running the latest chipset / ide drivers.

That depends on if the MDS contains useful info. Chances are you can delete the MDS (well, move them to another folder) and then just burn the ISO - it'll only potentially be an issue if the images were double layer ones. Or if you're really desperate, hex edit the MDS file and change the file name stored at the end of the file to whatever the new one (of the ISO file) is.

ImgBurn won't copy protected discs.

There's a forum called 'Guides'. I'm sure you'll find something useful in there.

If you can't burn Verbs at 2.4x without getting the error, either the drive is still screwed or the media you've got is faulty. It shouldn't be *that* hard to get a working burn.

You can but what's this got to do with ImgBurn - a burning program?! Google it or visit one of the many DVD related websites / forums.

If you're only using USB 1.0, you seriously need to consider getting some sort of USB 2.0 card in your PC/Laptop. When you burn on USB 1.0 (as chewy said), you're limited to 1mb/s - and 1x DVD speed is about 1.3mb/s. So basically your drive can't even burn at 1x. Every time your drive runs out of data in it's cache (which at below 1x speed is ALL the time!!) it's having to perform linking as part of it's burnproof feature. That's something you want to avoid if possible as it'll be reducing the quality of the burn. Personally I'd forget about burning DVD's until you're up and running on USB 2.0.