LIGHTNING UK!

I don't want to write a dll to handle shell extensions and that's the only way to do it - this has been mentioned several times before. Number 4 is already possible though... but it won't work unless you run ImgBurn as admin once.

You switch to read mode and look at that same 'File System(s)' bit of info.

In Build mode you mean? It's in the tooltip.

Please burn another disc, but this time press the F8 key before you hit the write button. When it's finished, press F8 again. Save the log and upload it again. Thanks!

Read this guide! http://forum.imgburn.com/index.php?showtopic=5592

Thanks, I've uploaded it to the website.

Ah yes, I had a feeling it was that. So if UDF isn't used in the first place, I guess it should work too? If you do use UDF then you need to make sure you've disabled unicode support - but then don't blame me if you need it on a later burn with unicode filenames and forget to enable it again

I thought it might be easier if everyone had a forum to chat about this translation stuff in rather than just a single thread... so here it is!

1.0.0.6 -> 1.0.0.7 Language_File_1.0.0.7_Differences_Report.zip

1.0.0.5 -> 1.0.0.6 Language_File_1.0.0.6_Differences_Report.zip

Below you'll find the 'differences' reports (made in Beyond Compare) so you can see what has been added/changed/removed between versions. It's very important that you look at them carefully and use them to pick up on where the existing text for items has been edited. The reason being, the DKLang program only makes totally new (or deleted) entries obvious. If I add a new item to an existing combobox and you don't pick up on it, you could make bad things happen! You must make the changes in the correct order - so if you're updating a language file based on v1.0.0.5 and the current base file version is v1.0.0.7, you need to apply the changes from the v1.0.0.6 report before then moving on to do the ones in v1.0.0.7. If you're having a hard time understanding what I mean, please make a new thread in this forum.

The difference is something stupid and already possible with the given options (AFAIK). It's just down to you to figure out what it is by comparing a disc burnt in each in IsoBuster and seeing what's different. If you burn with the file system set to 'ISO9660 + Joliet', doesn't it work anyway?

You'd have to see how your player likes them to be named.

No, the 'Bootable' bit in brackets means it's bootable. You can't check it in read mode unless you've already burnt the image or mount it in a virtual drive. So basically, just load the ISO in Write mode and see if it says 'Bootable' in the 'File System(s)' bit.

Sounds like you're in Write mode - which is for burning disc images. An avi file is not a disc image. You want Build mode.

Because you don't have the 'Calculate MD5' option enabled on the General tab (it's disabled by default). If it's not calculating the value in the first place, it can't then write out the md5 file btw, not being someone that really uses MD5's, I have no idea on the actual file format you're supposed to use. I just guessed quickly based on output from IsoBuster. It also won't work with split files... again, this is because I have no real idea on how the MD5 files work and what goes into them.

Yeah it would appear to be a bug in their latest beta driver. If you can find a way to report it to them, by all means do it! You could also copy + paste what I put above so they can see the times involved and that clearly something isn't right!

Ok so basically your drive/driver is only processing 1 command per second. Go back to the WHQL driver if you're saying that one works ok (rather than the beta you're on now).

Looking forward to it.

If you search for devices again (via the tools menu) does it take another 20 odd seconds? If so, press F8 and then search again. Save the log window contents to a file and upload it.

Stick a (1) and (2) after it or something! All that matters is that it's in there.

The number of spaces doesn't matter (at least not with 2.4.4.0). It's saying N/A for booktype because the function is failing - as per your previous post. Do none of the booktype options work?

So you have 2 drives? I'd assumed that once that one had been disabled, ImgBurn would just show 'No devices detected!'. In any case, if the drive is taking ages to become ready it's probably because it can't read the disc you've put in it. What type of disc are you trying to read/write? Post the new log too please (along with the filter driver stuff).

It'll make it if the image is less than 1GB too, because that's what DT needs for it to be made to look like a DVD.

Well it's either made in unicode format or it's made in ansi format... so really that setting has nothing to do with it being made or not.