LIGHTNING UK!

Correct.

You should avoid slim drives, they make for rubbish burners. Buy a generic 5.25 USB/eSATA enclosure and put a standard desktop drive in it - something like an Optiarc 7260/7280.

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

'Reserve track' (for DVD+ format media) is the other one. But neither of those should be required and you already have a successful burn! You can't make it *more* successful unless you mess around with write speeds etc in an attempt to improve the burn quality - but your drive only supports 2.4x so you're stuck. Seriously, why don't you go an ask in a thread somewhere that deals with burning exactly what it is that you're trying to burn. See what others have done and how they got it to work / not work.

Yes but single layer DVDs aren't double layer DVDs. It's apples and oranges.

Sorry Rincewind, I don't know how we can answer that question! You're right, it makes no sense that it would work fine with SL media missing the AUDIO_TS folder but not DL media. Is there no firmware update available for your player or anything? Have you tried contacting the manufacturer about the issue?

Ok, a last resort would be to play the mp3 and have another program recording it at the same time. So play in VLC or whatever and then record in audacity.

It's nothing to do with ImgBurn or its settings (except perhaps the layer break one, I have no idea). Playback issues are not our concern and are best dealt with on a forum that deals with your chosen playback device (i.e. the Wii).

Does the player connected to your TV support AVI files? If not, that's probably why it doesn't work! Use something like DVD Flick, ConvertXtoDVD or AVStoDVD to convert it to DVD Video format and then burn that instead.

It's not down to me to explain why the VirtualAlloc function may or may not fail, I didn't write it - ask Microsoft. It's a 512MB buffer, not 512KB. You've probably set both buffers to 512MB yeah... so that means you're using 512MB for the reading side and another 512MB for the writing side - making 1GB in total. That's quite a bit when you've only got 2GB available and it's supposed to be contiguous memory. I've got 16GB of RAM and I still only use the default buffer settings. Ever heard the saying 'just because you can doesn't mean you should' ?

It's quite simple, just don't use such a big buffer if your machine can't handle it. Of course I already told you that here :- http://forum.imgburn.com/index.php?showtopic=18628

Except it took almost 10 minutes for the 'MREFKTM 0TEFKLQ 1.03' drive to do what's asked of it. I suggest you look at updating / removing the program you're using for a virtual drive.

You can only write 99 tracks of CD Audio (CDDA) to a CD. You can't write CD Audio (CDDA) to a DVD - period. Try loading the broken mp3 in something like Audacity and then write out a new file.

No, the new version doesn't make the old one fail. Your drive/firmware/media combo are what made it fail. The new discs may have been different to the old ones - the 'brand' name isn't important.

You'll probably have to force the machine to power down by holding in the power button for 5 seconds or so. Are you being forced to use double layer discs? What you're burning fits on single layer discs just fine. Maybe the drive would do a better job if you used one of the other supported write speeds.

You need to update ImgBurn, your version is ancient. Then read this - http://forum.imgburn.com/index.php?showtopic=8000

There isn't, no. Sorry! It's a result of adding support for reading the potential volume name from the XML file. I've just made changes to the code to improve things though.

Until maybe the existing default app is no longer the default app and ImgBurn vanishes from the context menu. These things are done for a reason, even if you don't immediately understand or agree with them.

This has been fixed in the most recent release. Also, have you set the 'Write Type' to TAO for an actual reason or were you just messing around? Put it back on DAO/SAO.

That's just nit picking really though isn't it

It has to add itself to whatever's the current default application (basically treated as a redirect) because otherwise it doesn't show up as an option in the menu. If DT used something like DAEMON.Tools.Pro.ISO\Shell for .ISO files then it wouldn't be an issue. They have their way of doing things, I have mine. So I'm sorry but this is by design and I don't plan on changing it.

ImgBurn doesn't associate itself with MDX files. What you're seeing is probably a result of an MDX burning program using a single generic registry key to deal with all of the files it supports... so when ImgBurn adds itself for a different format, it's being included with that one too.

If your drive can't initialise any discs (blank or otherwise), it's probably dead.

Did you do it from scratch or just a little update for 2.5.6.0 ? To be honest, keeping up with the credits is a nightmare in itself and I'm very tempted to just ditch that column from the website.

You only think it's weird because you clearly haven't done any reading around/homework/research on that stuff in a long time. Knowledge about anything technical goes out of date very quickly. If you don't keep up with it you just revert to 'n00b' status.