LIGHTNING UK!

My program doesn't make it for any type of machine. It's generic in its approach. It'll add what you add to it and it won't add what you don't! (with the exception of creating AUDIO_TS / CERTIFICATE folders based on the options in the settings) If you have an AVCHD folder that just contains a BDMV folder and a CERTIFICATE folder, it makes no difference if you add the AVCHD folder or the BDMV and CERTIFICATE folders. What gets burnt to the disc will be exactly the same.

It doesn't, no. Something like that would be mentioned in the release notes! Yes, it'll no doubt get added at some point during my lifetime. I have no idea when exactly.

I'm not seeing anything in your log to suggest that's the case. If the program crashes, make it send an error report so I can look into the cause of the crash. All I see in your log is this... And that just means your drive failed to burn that bit of the disc. 'Invalid Address For Write' isn't a typical initial error code though, so it might be that your drivers (and / or filter drivers) are making the real one dissappear. What chipset does your motherboard use? Which controller do you have the drive attached to? When you're in Write mode, right click the drive selection box (in the 'Destination' box) and click 'Family Tree'. Then copy + paste what gets written into the log window.

Well you're up far too late for a school night! Try the driver thing tomorrow.

If you say you're already on the latest drivers, can you try totally uninstalling them in the hope it'll start using the default microsoft drivers instead? Did you try another cable as suggested? Oh and don't forget the firmware update.

Ok so you load the program up... then click the 'write image file to disc' button. In the 'Destination' box you'll see a drop down box that lists the name of your drive. Right click that drop down box and a menu will appear - on it you'll see a 'Family Tree' option - click it. A box will then pop up telling you some info about your machine, just close it down by clicking 'ok'. ImgBurn's Log window will have the same info in it, just copy + paste it all as you did above.

I think it's safe to say you have DMA issues. It's not normal for a drive to show us a 'Fibre' unless weird drivers are installed. Can you please right click the drive selection box and click 'Family Tree'. Then copy + paste everything from the log window. Look for updated motherboard chipset/controller drivers. It might also be worth trying another SATA cable (a short cable is better than a long one). There's an updated firmware available for your drive. http://www.firmwarehq.com/Samsung/SH-S203P/files.html

Your drive is failing to burn those discs. http://forum.imgburn.com/index.php?showtopic=8000

It's doing exactly what it says. How many files exactly? Hundreds of thousands? If you've got loads of similarly named files using 'long' names, it will take a while (converting them to 8.3 format). You'd be better off just using UDF and ditching ISO9660 + Joliet.

Thanks, uploaded to website.

Thanks, uploaded to website.

Thanks, uploaded to website.

I very much doubt you can actually do what you're trying to do. The machine would just reject it. In any case, this is not the forum to get help with technical xbox stuff like that. Try an actual xbox forum.

You'll have to wait for an updated language file.

As usual, you can download it and view the changelog by visiting the main website. http://www.imgburn.com/ Special 'Thanks' to all the beta testers, translators and donors!

1.0.0.11 -> 2.5.6.0 Language_File_2.5.6.0_Differences_Report.zip Language_File_2.5.6.0_Differences_UnifiedDiff.zip I've gone for a new numbering system that matches the program version. If you make tweaks to your file after its initial release, just bump up the last number. i.e. 2.5.6.0 would become 2.5.6.1.

You aren't. ImgBurn just burns what you give it. If what you give it is missing folders/files, that's down to you (or whatever made those folders/files in the first place). Playback compatibility is not really my concern - there are too many variations and I don't have the time or means to keep up with them all. Like I said, talk to the author of multiavchd (over at the Doom9 forums) and ask him where that certificate and 'id.bdmv' file are coming from - if not found on your hdd. http://forum.doom9.org/forumdisplay.php?f=39

ImgBurn can be told to make/add the 'certificate' folder if it doesn't exist, but it never puts anything inside it. If you can't locate that folder / file on your hard drive, multiavchd must be creating it temporarily and then removing it later on. multiavchd has lots of special tricks to create the right file/folder structure for a given player. If you want it to leave that file/folder structure intact once it has been closed down, asks its author how to do it - it's nothing to do with me.

We posted milliseconds apart ianymaty

It's on that page, you just have to pick from one of the 8 'mirror' sites.

The image doesn't fit on a DVD+R DL disc so what you're seeing is perfectly normal and to be expected.

Does it do this every time? I don't think there's anything I can do to see why you're having the problem. The only way to deal with issues like this is to have a program that can capture all the I/O that's going on and see what (if anything) gets stuck. If I/O gets stuck then it's out of my hands.

As it happens, I've already fixed this issue ready for the next release. (* but you'll never really see it) I generally don't mess around with multisession/track (non CD) discs so this problem had gone un-noticed for quite a while. As Read mode can't really be used on multisession/track DVD/HD DVD/BD discs (there's no way to burn them), it has been now blocked from doing so and I've added a prompt suggesting the user should create a new clean (single session/track) image using Build mode. I believe that almost ties in with your suggestion about making an ISO which contains the data as shown in Windows.

Sorry, I've never purchased an actual 'external' burner so I can't help you with that one. The internal drives seem to get better support and more firmware updates. That's why I'd get one of those and a generic enclosure instead.

The default is and always has been 'Auto'. Obviously it would make no sense for it to be anything else (by default) if it doesn't always work! Anyway, glad it's all sorted now and thank you for the donation