LIGHTNING UK!

Yeah my board is meant for 1333. I got an ip35 pro to replace my d975xbx2 just for a laugh until the x38 ones come out.

I hope you didn't delete the two filters shown in your post?! Those two are fine and are supposed to be there.

Before doing anything else, buy some Verbatim 2.4x DVD+R DL discs and use those instead. They're FAR better than all the others and to be honest, you're lucky the ones you're using now burnt at all.

I don't know why they'd be bad overclockers, almost all the memory makers use the Micron D9 chips and Crucial is of course owned by them!

You don't need a screenshot of the filter drivers window, just click the 'clipboard' button and then 'paste' the text into your reply.

The standard DVD Video one - i.e. 1.02 I may well support newer ones eventually but there's not really a massive need for it right now.

lol I assumed it wasn't a DVD Video disc because it was too obvious in DVDShrink how to load the ISO! Of course even if it couldn't, you could mount the ISO in DEAMON Tools and shrink it from the virtual drive.

Hmm that's an odd error for an SATA drive! It might well be driver related but only you can really test that - and I'm not sure you could if you're relying on the NVidia ones to get the RAID working. You'd have to try going back to the default MS ones, before then putting the latest NVidia ones back on again. You should also check your filter drivers via the 'Tools' menu. To help with the 'Media change notification' message I need to know what the exact error was. I can promise you that installing ImgBurn has not done anything to cause it to come up. ImgBurn is just an exe, if it's not running, NOTHING to do with ImgBurn is running and there's no way in the world it could break other programs.

ImgBurn is a burning tool, it'll never compress anything. What goes in = what goes on the disc. The whole idea of an ISO is that it's a disc image and is written to a disc 'as-is'. If you ever wanted to compress it, you'd need to take it back a level so you've just got the raw files and then compress those before then making a new ISO.

indeed, it's probably corrupt now.

You don't choose a size, ImgBurn knows it based on the files. Leave the settings on the 'Media' tab at the default values. Leave the layerbreak option in the setting on 'Automatic'. In fact, you don't ever need to change away from the default settings - they're the ones that work! You only change them when you 100% know what you're doing, the defaults cannot possibly do what you want to achieve and you know the exact setting you need to change in order to correct that.

There's only one worth using - Verbatim 2.4x DVD+R DL. Media Code: MKM-001-00

Sorry, when I said 'look', I meant go and enable it. Without that, the program doesn't issue any commands to set the read speed - i.e. it'll use whatever the drive defaults to. I've made some changes in that department since 2.3.2.0 so the next version might be better for you anyway. That said, I don't recall seeing this issue myself when I burn CDs so maybe not all drives suffer in this way.

There's no code within ImgBurn to do anything special with duplicators / changers. Assuming they look like a normal drive, there's no reason for them to not work though - even if it's just as a simple (single) drive.

This might well be part by design, part not. Go into the settings and look on the verify tab for the option about setting the read speed.

If the drive supported the discs properly it wouldn't be saying this for an empty disc: It would also be listing how much free space was left. Try looking for a firmware update or something - failing that, get 8x discs as that's all your burner appears to have been designed for.

Easy mistake to make. You're not the first person to make it and I'm sure you won't be the last!

Seriously, don't waste your time. I have no interest in doing anything with the languages at the moment. There are far more important / interesting things I'd rather be working on. When I'm ready for it to be translated I'll be sure to let everyone know - just don't hold your breath.

lol I think you guys are underestimating the size of the project. Defining language variables and populating those from text files at runtime is probably how I'd do it, but it would take me forever and would be the most mind numbingly boring task I could ever hope to not do. Unless there's some magical way of clicking a few buttons and it doing all the string extraction for me, I very much doubt this will be done before the next millennium. Building a program from scratch with translations in mind is one thing, it's easy to keep up with them when the system is already in place. Converting what is basically a legacy application in one go is something entirely different.

Your drive must be having an issue with it. Copy + paste everything from the box on the right side of the main screen.

I think they're at 1000 now as the cpu is slightly overclocked to 3ghz (from 2.66). The next divider up took them over the 1066 rated speed and I really wasn't fussed about that bit extra - overclocking really isn't my thing. Takes far too much time to get things just right and I can't be doing with all the machine reboots / power cycles. I only really got them because I wanted 4GB in the machine and the 4GB of GSkill 6400 HZ I had were total crap and wouldn't work together in any of my boards. The GSkill are now sitting in my cupboard collecting dust

There's nothing to 'help' with. It's not possible to translate anything at this time - it'll all hard coded. All you can do is use a resource hacker / editor and manipulate stuff that way.

Oh dear, you had to take the bait didn't you

Not really, no. (and that's knowing it would only take me 2 seconds) Whilst screensavers might have been a problem in the windows 3.11 days, they're hardly taxing to a modern machine. So long as people aren't crazy with their screensaver timeout values (i.e. 1 minute), it really shouldn't be an issue. At 1 minute I'd find the continual interruptions more of an inconvenience than anything else! Mine is set at 15 mins (5 more than the windows default I believe) and I can honestly save I've never once seen it as a problem. Of course if your screensaver is set to play some mega 3D quake style timedemo, fair enough you might have a reason to want it disabled during burning! That said, I bet a lot of people are encoding etc whilst burning and I know from IBG graphs I've seen that it really isn't an issue even then.

It means Verbatim = Good, Ritek = Rubbish!