LIGHTNING UK!

What does ImgBurn say when you're in read mode with that disc in the drive? Does it display the disc info in the box on the right? If so, copy + paste it all. A screenshot of the main window would help too.

This thread is a year old. Make a new one, post a log / screenshots of the problem and we'll try to help.

You already know the answer. http://forum.imgburn.com/index.php?showtopic=8000

Do another clean install of Vista and don't touch a single thing after the initial install. Install ImgBurn and then try it. I'd be interested to see if the 100% default install makes those drives show up as 'Fibre' still.

I guess you've never used the program before... or at least never paid any attention to what it's doing. There are 2 operations going on there... 1. Writing the disc. 2. Verifying the disc. The stuff in the log *should* make that obvious - because it actually says 'Writing Sectors' in one and 'Verifying Sectors' in the other. So in answer to your question, yes it's perfectly normal.

Ah see now when I first saw it I thought it was a wildcard type operator. Like as in *.*

Why the star though?! I don't calculate the MD5 of each individual piece of a split file, that's why that bit won't work.

'few' meaning 'one' - right? It only came out last Friday Post a copy of your latest burning session log so we can see what's happening. The time it takes to perform these actions is totally down to the drive - oh and yes they're necessary.

If ImgBurn's discs couldn't be read before you installed the UDF 2.50 driver but Nero's could, yes it means the Nero ones weren't UDF 2.50. ImgBurn can read and write BD discs just fine, I see no reason to resort to using Nero at all. But hey, I'm a little bias and this is the ImgBurn Support Forum.

You could do but Blu-ray is supposed to use 2.50.

FYI, I've fixed the issue that caused your odd GUI fonts problem. The SystemParametersInfo(SPI_GETNONCLIENTMETRICS...) function was failing because it was being called with its structure size set to a value that's not supported on any OS prior to Vista. I also took this opportunity to make the GUI font a configurable option (although it always was, via a certain registry key).

Go for a manual clean then... take it apart and use one of those cotton things on a stick to clean it. Just dip the cotton thing in some alcohol (vodka?!) / white spirit / nail varnish remover first. Oh and BE CAREFUL!

You could try with some 2.4x Verbs instead but it shouldn't really have an issue with those 8x ones (unless you got a duff spindle?). Maybe the drive is just faulty?

Nope because that means Windows caches everything which would normally slow things down - that's why the flags are available in the API functions to start with. Not only that, there's no real point in the OS attempting to cache the kind of file reads/writes that ImgBurn has to do (one time only stuff and normally on huge files). You're getting awful transfer rates considering that's a raid array. Is it software or hardware raid?

What you have to remember is that a service pack is more than just hotfixes. They'll no doubt drop support for anything prior to SP3 soon just as they did with things prior to SP2 not so long ago.

Ah see the lfFaceName is a fallback if the function 'SystemParametersInfo(SPI_GETNONCLIENTMETRICS, 0, &ncm, 0)' fails (or all the values appear to be blank strings). When that fails, it's asks the status bar which font it's using and uses that. So the question is, why is it failing on your machine? ....I think I know and I'm working on a solution right this second

*sigh* How many threads do you need about the same thing? http://forum.imgburn.com/index.php?showtopic=9972

Traitor!!!

Or keeping it within the ImgBurn family, go and read the 'Audio CD' guide in the Guides forum. http://forum.imgburn.com/index.php?showtopic=5555

I assume this is happening with all images now, not just one?

That's interesting as the file hasn't changed since May 2008.

I don't get why you think you need to verify a read? The drive will report an error if it can't give ImgBurn the data for a sector. That's the whole point in error correction.

He's jokiing, don't take everything you read so seriously!

Have you tried at the other speeds the drive supports on that media? i.e. 4x, 6x, 8x and 10x?

Tools -> Settings -> I/O -> Reading - Always Use Buffered I/O.