LIGHTNING UK!

Works fine for me too. Once it's saved the queue file and shut down, open the queue file in notepad and see what it contains. btw, nothing you've burnt will be saved in the queue files (even if it's visible in the queue window), only new stuff.

Try with the firmware update first, if that doesn't fix it then you'll need to buy verbatims. Next time you buy discs, buy verbatims / taiyo yudens anyway. The only way to be 'sure' is to try it. We make no promises here

Update your firmware too. http://drivers.softpedia.com/progDownload/...load-14355.html DL13 is the latest.

lol I never bother with any of that rubbish, just run the update. The drive won't accept the firmware until it's been written and double checked anyway.

Are you sure MVD is the file extension being used? It's not one I've ever heard of / seen. In any case, unless it's an image file ImgBurn won't burn it - because ImgBurn doesn't convert / encode anything.

Can you please repeat that with some decent media - you said you had Verbatim somewhere. The L-EC uncorrectable error isn't going to be there because the program couldn't get exclusive access of the drive, it'll be there because the disc are just generally crap or the burner's support for them isn't what it should be.

In a normal batch file they should run sequentially. It's only when I see people using the 'start' command to run ImgBurn that there's a problem (unless the call 'start' with the '/wait' switch). i.e. Start ImgBurn.exe /MODE BUILD..... Start /wait ImgBurn.exe /MODE BUILD......

That's the thing though, the retries probably don't mean anything because I doubt there's actually any problem - or at least not where the drive is concerned. Your drivers are messing up the communication path between the software and the drive. The best thing you can do now is get one of those Silicon Image cards I mentioned and put all this 'driver hell' behind you.

ImgBurn is a GUI app, CLI functionality is a bonus and goes on top of whatever the GUI is configured for (i.e. read in from the settings). I really have no intention of ever changing that or disabling things, it's just not worth it. If you're using CLI surely you should have enough of an idea of what you're doing to not get confused anyway? The command line length limit is something like 32k characters (under an NT based OS when using Unicode). If you ever create a line that long I'd like to see it!

Ah crap, ignore that. I've just looked at the specs / a picture of your board and the jmicron ports are probably the 2 esata ones you have on the backplate. Take a quick trip to ebay and get yourself one of those silicon image cards I mentioned earlier (Something with a Silicon Image 3112, 3512 or 3114 chipset on it). They're only about

Hmm, sorry I though that with a motherboard like that you'd actually know your way around the inside of a PC... I guess you don't. Find your optical drive in the case and then follow the SATA cable from it back to the motherboard. There will only be 2 cables, one for power that goes to the power supply and another for data (the sata cable) that goes to the motherboard. Where it ends will be where the SATA connectors are. Now you've seen an SATA connector, look for some other ones just like it. Sometimes they'll be a different colour if they're on a different controller. i.e. you might have 4 that are one colour (the ones on the nvidia chipset) and 2 that are a different colour (on the jmicron chipset). Simply unplug the SATA cable from it's current location on the board and plug it into one of the other sata ports - one that's connected to the jmicron chip. As you're already on the latest motherboard bios you already have the latest jmicron bios available to you. That is to say, when you update your motherboard bios you will automatically be updating the jmicon one as well if ASUS have included an update for it.

You have to update the motherboard bios to update the jmicron controller bios. To move the drive to the jmicron controller you need to physically open the case and move the cable so it's on the port that goes with the jmicron controller and not the nvidia one (refer to your motherboard manual). btw, do you really have the 1109 bios for your board? The ASUS site only goes up to 1104 and that came out on the 24th Sept 2008. http://dlcdnet.asus.com/pub/ASUS/mb/socket...xtreme/1104.zip

ImgBurn doesn't look at / care about the code page. There's nothing in my code that's anything to do with this stuff. There are lots of people out there (even a couple of the beta team members) running non english OS's and they've never mentioned this problem... and I'm quite sure they would have done.

Did you actually move the drive to the jmicron controller?

Nope, if it only lists 8x as a supported speed then 8x is all it'll burn at. You'd have to hack/modify the firmware to change that - and that's beyond the scope of this forum.

So it's on the nvidia chipset then? Seems these latest nvidia drivers are as buggy as ever then... you're not the first person to provide logs where the real error codes from the drives are getting lost / messed with. btw you can get updated jmicron drivers from here: ftp://driver.jmicron.com.tw/jmb36x/Win2k_xp_Vista/ I'd almost be tempted to update the drivers for the jmicron and then move the burner over to it. I assume that bios is current? No doubt it'll update the jmicron bios aswell so it's a good idea to keep it up-to-date. Another option would be to get a silicon image 3112, 3512 or 3114 PCI card with base bios and put the drive on that. (That's what I've done)

You don't need to create them, ImgBurn does it as and when it needs to - i.e. if you ever actually try and save (or it tries to save) a Queue or Project file.

I very much doubt that BwgBurn picks up on the same errors that ImgBurn does, the 'Program Memory Update Failure' thread at the top of this forum kinda shows that. If the drive has problems then 99.9% of the time it comes down to the drive / firmware / media combo. Getting the 'No Additional Sense Information' error could also be a driver issue. How exactly is that drive connected in your PC? By that I mean which controller is it attached to? What's the model number, which driver/bios version is installed?

Icy-Dock ones work fine with 1TB drives, that's what I run in mine.

It'll work fine if Wine is configured correctly.

lol bad edit of the topic title... it's not anywhere near the 2nd layer and an I/O error is not a crash it's your drives way of saying it doesn't like something.

Try again at a different 'supported' speed - i.e. 4x, 6x, 8x. After that, try again with Verbatim 2.4x DVD+R DL (MKM-001-00 dye, made in Singapore). They are the only DL discs we recommend and the rest are rubbish by comparison. If you still have problems when you've done all that, please provide us with a new log from the Verb burns.

Pass! I've never seen that before. Are you sure it's not caused by something on your machine? Have you tried loading the german language file? (obviously it's not running in that screenshot)

Reinstall ASPI. http://www.adaptec.com/en-US/speed/softwar.../aspi32_exe.htm If that doesn't work, Google 'ForceASPI'.

Read the FAQ. You have DMA issues.