LIGHTNING UK!

Run something like HD Tune on your hdd and post the benchmark graph please. Before you start it though, go into the option and make sure it's set for a full test. 3 x 12x burns would be ~50mb/s at peak speeds... to me, that seems an awful lot for a normal mechanical hdd to handle when random accessing 3 image files (plus usual windows I/O going on in the background).

I won't pretend to actually know what I'm doing here but maybe the obvious 'firmware' folder isn't actually the right place for them? Searching all files on the disc for 'firmware' seems to have loads of hits in the file 'dists\squeeze\non-free\binary-amd64\Packages' and opening that file in notepad shows it pointing at firmware files in the folder 'pool\non-free\f\firmware-nonfree'. Are you perhaps meant to put your files in there and add their info to the 'Packages' file so it knows they exist?

Correction, you need ISO9660:1999 and Joliet. Without Joliet the installer just fails a bit later on complaining about a 'Release' something or other.

Ok so it's an AMD controller. Do you have their latest chipset/sata controller drivers installed? Get them from the AMD website. Have you tried burning at 4x?

I'm guessing the installer/bootloader doesn't work with Joliet (or UDF) and so relies on the Rock Ridge file system for long file names. As ImgBurn doesn't support that you're left with using ISO9660:1999. So set the 'File System' to 'ISO9660' and then click the '1999' link on Advanced -> Restrictions -> ISO9660. Build a new image and then try that one.

That's not building it but don't worry now, I see the issue. It brings up the first menu but just keeps reloading it when you select an option from it.

Do you have the log from when you built the new ISO please?

Right click the drive selection box and pick 'Family Tree'. Close the prompt it brings up and then copy + paste the family tree info from the Log window.

It's all in here. http://forum.imgburn.com/index.php?showtopic=8000

Can you point me at the exact image file you downloaded? I assume you've tried building a new disc without changing anything (adding in your extra bits) and it still wouldn't boot?

It won't be what I thought it was then. Don't make that change. Post the log please - as per the pink box up the top

Does the error suggest it's to do with reading a file? Do you have a 3tb external drive that you're reading from by any chance? It's fixed ready for the next release but for now you can work around it by turning on the 'Reading - Always use buffered I/O' option in the Settings (I/O tab).

Yeah I'm talking about the super old Windows 9x based operating systems - so 95, 98 and Me.

You can either just copy the contents of the disc to an appropriatly named folder on your backup drive using Explorer or use the 'Create Image File From Disc' option in ImgBurn to make a complete image of the disc (an ISO) and save that on your backup drive. You don't lose quality when copying discs, no. The data is digital so assuming it can be read correctly from the source disc (error correction can/will be used where required - internal to the drive), it'll be faithfully reproduced on the next disc you burn. The exception to the rule would be Audio CDs where there's no normal error correction available and different drives offset the data in different ways. If Reading + Writing doesn't equal out to an offset of 0 then you'll effectivly lose a tiny bit of data each time you make a copy (and then make a copy of the copy etc).

Does it really throw that 'Invalid floating point operation.' error every single time? It's actually a compiler bug and not something I can fix without updating to a newer version of my development environment - which then kills support for some older operating systems. Here's the info I found on it - http://blog.excastle.com/2007/08/28/delphi-bug-of-the-day-fpu-stack-leak/ If you are always getting the error in that same place, try turning off the 'Capture Graph Data' option in the Settings. It might just be enough to work around the issue - if that chunk of code isn't ever called, it can't error out!

I know what you mean but the two things happen at totally different times (with lots of stuff in between) and there's currently no interaction between the code that causes each of them to pop up. I will see if there's anything I can do when I revisit those sections.

I'm not seeing an error, I just see you aborting. Is the 'error' that it never finishes? Obviously you're messing around with a modified firmware and the drive doesn't behave quite as it should do when burning MKM-003-00. You will have to try various settings (eeprom/advanced ones) until you find some that work reliably for you. Do you know what make the sata controller is that you've attached the drive to? The image you're burning is not the problem, data is data to a drive.

Can you post the log please - as per the pink box up the top Ideas / suggestions can be found here - http://forum.imgburn.com/index.php?showtopic=8000 (to save me repeating them over and over again)

I don't really know what you want us to say here. Everything we have to say on the matter of burning DL discs can be found in the thread I assume you were referring to as 'spiel on verbatim discs'. http://forum.imgburn.com/index.php?showtopic=8000 If the drives are failing to burn at 'max' speed (8x in the case of your HP one), try again at the other speed(s) they claim to support on that MID (4x in the case of the HP one). You know you have to ignore the packaging on DL media yeah? Those discs use the 'MBIPG101-R10-65' MID/dye - which of course isn't RICOH. They might have used a RICOH MID/dye at one point but they certainly aren't now. Your drive knows / understands nothing of the data it's burning (so having a small file in the middle of a VTS set is totally irrelevant), data is data.

What makes you think you've got an Asus DRW-22B2L? The log certainly doesn't show it. If that log isn't current (it does say November 2011), please post the correct one. You should also read this - http://forum.imgburn.com/index.php?showtopic=8000

No offence but you aren't really in a position to make comments on the program as a whole or speak on behalf of all the other tens/hundreds of thousands of users. Software doesn't burn discs, the drive (and its firmware) does. That's why you'll never see any software update saying it's improved burn quality or added support for a specific disc (not format of disc, that's different) - they're things that get implemented / tweaked in firmware. You haven't actually mentioned the error you keep seeing (why not post a log so we can look?) but if the burn fails then that's down to the drive. Anyone that actually knows the ins and outs of burning will agree with me and confirm that.

ImgBurn can't cause this, it's not a driver. You'd have to analyse the memory / mini dump file that Windows created in order to find the root cause of the problem. Try using this - http://www.nirsoft.net/utils/blue_screen_view.html

There are tons of guides in the Guides section that tell you how to burn DVD Video discs - none of them involve / force you to use drag+drop.

Getting stuck on 'Analysing Tracks' is a known but as yet not easily reproducible (at my end anyway) problem. The 'img' Vs 'bin' issue is because you've turned on the option to create a CCD layout file. The data file must have the 'img' file extension for Virtual CloneDrive / CloneCD to recognise the file and work.

ImgBurn burns as-is. If you want the avi playable in a standard dvd (one that doesn't support avi files) then you need to convert it to DVD Video format using something like DVD Flick or ConvertXtoDVD and burn the VIDEO_TS folder.