LIGHTNING UK!

Hi, There are a number of translations that have yet to be updated for the current ImgBurn base language file release. If you are able to update any of the following, please do! Bosnian Catalan Croatian Danish Estonian French Greek Hebrew Japanese Korean Latvian Norwegian (Bokmal) Slovenian Spanish (Traditional Sort) Thai

Read it properly! Just because the subject says 'From Administrator' doesn't mean it is. Would people be equally fooled if it said 'From Santa Claus' ?

If all drives produce the exact same error on all media (including the verbs) and at all 'supported' speeds, it's probably time for you to reinstall windows. What you could try first though is burning something via a linux live cd. If you install Wine you can even do it via ImgBurn. What motherboard do you have? Have you tried installing the latest bios / chipset drivers / controller drivers? The drives shouldn't really be showing up as 'Fibre'.

Please note that this one isn't quite right yet and I rejected it.

My desktop gets like that sometime too but then I just give up and clear it off again... even if it takes half an hour!

In your honest opinion, is this better / more complete than the one on the website? Last time I looked at it, the other one still had loads of English stuff in it.

Damn, you've already done them! Thanks though. I was just coming back to say I've fixed it I see you like your desktop icons

Oh well, try some different discs then. A firmware update might fix the issue too. What drive do you have?

Is there any way you can get a screenshot? (shrink it down to something like 30%) I use multimonitor too (2nd is hdtv) but the nvidia drivers make them 2 different desktops. Mine are around the other way though, the bigger is the primary. I'll have a play around and try to reproduce the error.

Does it recognise blank DVD-RW's? Can you burn to them? I'm just wondering if you even have a DVD burner or if it's just a DVD reader / CD burner.

It's not ImgBurn's job to recognise media, it's the drives. So if you can't do anything when there's a DVD-R in the tray, it means your drive probably doesn't support the dye being used by that disc. Try some others.

You know 2.4.4.0 is out now, right?

Make a new thread two please, don't hijack this one.

Guys, PLEEEEEEEEEEEEEASE don't put translations in here! Make a thread (called something like 'French v1.0.07 by WillCroPoint') in the 'Translations' forum and just update that when you have a new release. This single large thread is becoming a nightmare!

It's supposed to center itself around the main window.... where is that exactly?!

It depends on the drive. Sometimes it helps, sometimes it makes things worse. Either way, the default is DAO/SAO. As for the speed... 8x is normally the ideal speed for SL media. That's using decent stuff though - which yours isn't. Not only that, laptop drives are never any good really.

They've probably implemented a workaround for it. If possible, try reverting to an older driver for whatever controller your drive is on.... do you know which chipset your motherboard uses?

Isn't that a replication master image? No, you can't burn those with ImgBurn.

Default is 'AWS' which unless you've configured the 'Automatic Write Speed' feature properly will end up as being 'MAX'. Burn at 8x or 12x for best results.

Well there no reason for the 'default' to be Incremental then. It certainly isn't programmed that way!

Without seeing a log, it's hard to say. If they skip it normally means the player can't read the disc properly. You can improve the quality of the burnt disc by: 1. Updating the firmware on your drive. 2. Burning slower (although this isn't always the case). 3. Using better media - Verbatim and Taiyo Yuden are the best.

That's not a normal response from a drive during burning. It could be that your controller drivers are messing things up and that's a bogus error code. ImgBurn is then retrying and of course the retry is invalid because those sectors have already been written to.

You might have a virus / malware that's messing things up. I haven't seen anything of this error in the past 3 years... then all of a sudden there's a rush of people with the same issue - that *never* happens!

Look in eventviewer, do you see any errors recently?

I don't know, I never looked. Soon as I knew what was happening I just deleted them all.