LIGHTNING UK!

MCC-004-00 (from Verbatim - right? Any other brand are probably the ones that didn't meet up to Verbatim's standards) are one of the best dyes available. There are 3 things that go towards making a decent burn... the drive, the firmware on the drive and the media. I'd be amazed if your drive really couldn't burn such top quality media when told to do so at a more realistic/decent speed.

If the original disc has mp3's on it, it's not the same as a true Audio CD. There's no such thing as an Audio DVD in the sense that it'll play exactly like an Audio CD would in your standalone CD player. The Audio DVD's that do exist are a totally different format and you need special authoring packages to make them. What you need to do (if you really want a true CD-DA Audio CD) is to split the songs up onto multiple CD's. With MP3 being a compress format, you can fit loads on a CD but to play them back you need a player that supports MP3. Those types of discs are just burnt as data discs in Build mode.

Burn faster... i.e 8x or something. Slower doesn't always equal better quality, especially if the drive has been designed to burn the discs at faster speeds rather than slower.

'mp3' is too short for a search term. Most of them need at least 4 characters.

You should tell ImgBurn not to retry when finalisation fails and to just ignore the error, then the disc should work ok in your player.

What makes you think it's empty? You know that any OS before Vista needs a special driver to be able to read/understand UDF 2.50 yeah?

Nope

What exactly were you changing?!

post the log.

The default settings are the best anyway, that's why they're the defaults! That said, if your hardware was behaving itself properly, there's nothing you could change to actually stop it from working.

On the server I guess.

Don't forget to burn AND verify!

That top one looks very much like it would have been the designated LB cell on the original. You can't just go by the LBA as that's always subject to change depending on padding used within the file system - even originals use padding sometimes. You can use ImgBurn to show you the pgc, cell etc of the source disc. Just look in the Tools -> Drive menu. Or use Tools -> ISO... on the source image file (if you made one)

Does the status bar actually say it's deleting the buffer? If not, what does it say?

What error message do you get when you try? Maybe the drive just doesn't support it at all.... time to invest in a new one maybe?

The log windows opens by default on a fresh install, so obviously it was closed somewhere along the line. I recommend you keep it open as I use it to tell you things! Make sure you verify your burns by ticking the 'Verify' box just above where the 'Go' button is. This is very important when you think you're having issues.

It's the drivers that are getting stuck here (hence why the entire machine is unresponsive), not ImgBurn. Hopefully that tells you where the issue is!

It's a dell machine yeah? Use 10GE instead. http://support.euro.dell.com/support/downl...mp;fileid=73793

The error is coming from Windows itself in response to an API function call. Run chkdsk on the drive and see if it finds a problem.

Nope, it's CLI or nothing.

If you don't want to limit yourself, just mount the ISO in a virtual drive program like Virtual CloneDrive or DAEMON Tools and then use any playback software you want.

Well all you really need to do is attempt to make it booktype to DVDROM. If it accepts the command to do that then you'll have your answer without ever having to burn anything.

Yes, 1.A3 is correct for the ND-1100 drive you have. Your drive only writes to DVD+ (plus) format discs. The readme is simply saying the firmware update doesn't change that fact. (Your drive is VERY old now)

If you put the disc back in now, does the drive see it or does the statusbar still read 'Medium Not Present' somewhere?

Confusing logs there... one minute it's Vista x64, the next it's XP SP2! It looks like the drive is on an nvidia controller yeah? You've already tried updating / reverting the drivers? Have you tried burning in safemode? You can update SPTD to 1.56 from the duplexsecure website.