‘So Much Hardware!

You’ve no doubt noticed the frankly amazing rate at which new hardware, particularly motherboards, is being produced at these days: It’s like there’s a race on to produce better and better hardware. The leading players appear to be motherboards in first place, closely followed by graphics cards, and processors aren’t far behind.

When a new processor begins manufacture, every motherboard manufacturer makes a variety of motherboards initially to accommodate that processor and get the very best from it. They also utilise the latest chipset designs, many of which are purposely designed to operate in tandem with a particular type of processor. The production run continues with more specifically-designed boards, possibly utilising newer chipsets; tailing off as the processor in question, and/or its socket designation, becomes less utilised in favour of something newer.

Graphics cards are more in a league of their own; with the onus on the manufacturer to use one of the recently-introduced graphics chips from the graphics-chip manufacturers to give the best performance on screen in high resolutions and fast frame-rates, from complex multi-processor-core-utilising games software.

Unique Drivers

…And with each new hardware design comes a new set of software in the form of drivers; although having said that; recently companies such as Via Technologies, in the case of motherboard chipsets; and nVidia, in the case of graphics cards, have done fairly well in producing an all-in-one driver software package that fits pretty well all of their recent products. An example of this is Via Technologies’ site Viaarena; where a driver package of this sort, one-size-fits-all, cab be used to drive pretty much any recent Via chipset.

- But that’s not the case with every manufacturer; and even a number of the products manufactured by such companies as mentioned above are so particularly specialised that they have their own individual driver.

The good thing is that, in the case of motherboards and graphics cards, the manufacturer usually provides a CD or DVD with the product that has all the necessary drivers on it. When you install the board or card, you just simply install all the necessary other drivers from the disc. You’ll also find that the manufacturer provides a download for these drivers on their website also: This is a subject that we’ll be returning to later in this article, as there is something particularly important about that fact.

Motherboard drivers mainly relate to the chipset used on that particular type of board, as well as to the onboard soundcard and any other chipset-associated graphics-circuitry if included. Also the SATA and PATA controllers, and the RAM controllers, need a driver – as does the processor itself, in relation to the specific motherboard build as well as a unit in its own right too.

Windows in the Equation

Operating systems such as Windows, particularly Windows XP onwards, were designed to cater for drivers to some extent, and, when installed, attach a driver to each device to allow it to at least function something like correctly and identify itself, so that the operating system can be properly installed. – But that doesn’t always happen.

Windows XP was launched in 2001, and contained compatible drivers for most if not all of the technology in use in 2000. With a bit of forethought, Microsoft also created basic drivers that would at least run future hardware to some extent also. – But this doesn’t mean that Windows XP will install every driver necessary to run your system proficiently and optimally on install: As years have gone by, technologies have appeared which, although largely backwards-compatible with XP, are built for Windows Vista, or more recently Windows 7; which uses a very similar kernel to Vista anyway.

- So when you install no-frills Window XP and nothing else on your box, it runs. – Perhaps the functionality of a number of devices is impeded; for instance the graphics card is only able to work with a couple of screen resolutions, at a set monitor frequency, but nevertheless it runs. The reason for this is that it installs drivers to your devices that make them work with the XP kernel. These drivers, however, aren’t specially designed for the hardware that they’re driving in most cases, and they’re old.

-She’s Boasting Again…

I’ve just installed the RTM version of Windows 7 64-bit, after previously running the 64-bit RC version. – Both versions instantly recognised all of the hardware in my self-built computer, and so it should: the hardware I used was a Gigabyte motherboard that had been around a few months, as had the Gigabyte 256MB GDDR3 graphics card, the 8GBs of DDR2 800MHz RAM, the AMD triple-core Phenom processor, and so on. – All fully 64-bit capable, designed for use with Vista, and therefore Windows 7… – Except for two pieces of hardware in particular: The Realtek onboard sound-card needed a Realtek High-Definition Audio driver, which even Windows 7 didn’t carry in its arsenal: Result = no sound. Also there was no decent driver for the chipset: While Windows installed one that made it work, it didn’t have the necessary custom-designed driver that was required: The nVidia nForce System Management driver. – Both of these I had to install from the CD that came packed with the motherboard.

Soon Windows 7 will start initially installing only make-do drivers that allow the hardware to function very basically with the kernel. – The good thing about Windows 7 is that if it can’t immediately find a decent driver for a piece of hardware, then it will, after installing the best  driver it can find that works, go straight online to Windows Update to try to find a better driver there.

Another thing is that even Windows Update isn’t always that accurate: Yesterday, for instance, I was offered a replacement driver in Windows 7 for my Realtek ethernet connection as an optional update. The replacement driver was a year older than the one that was already installed, which was installed from the motherboard driver CD, and it didn’t work: result = no ethernet connection. I rolled back the driver and the ethernet port instantly started working again.

On that note; there are some automated driver-update services out there, which are supposed to always keep your computer up to date with the latest drivers. – These are also rather fallible: One of them that I used to use told me that my then Via chipset’s drivers were old, and it replaced them with Intel chipset drivers, so that it wouldn’t start. – ‘Not good.

In short; automated driver update services such as this, like most AI of this point in time time, occasionally have a brain-fart, and mess up big time.

(Windows XP will also go to Windows Update and find drivers; but not by default: You have to set the operating system to do this manually after installation; and even then XP will only chase down a better driver than the one already installed if you ask it to. If a piece of hardware doesn’t have a driver that isn’t available on the XP CD, or that piece of hardware has just been installed without a driver, XP will go to Windows Update to look for a better driver, sometimes automatically if set right; sometimes only if you prompt it to do so.)

Windows Update doesn’t have every type of hardware driver, though, so there’s a 50/50 chance that the operating system will have no luck there. Also, Windows Update doesn’t have all the latest versions of the drivers that it does have ready to be used: If it has a newer version of the driver that you have installed, then it’ll upgrade it; but just because it’s newer doesn’t mean that it’s the newest applicable driver.

‘Time for an Update?

This is where the manufacturer’s website that I mentioned earlier comes into play: –

If you look in Device Manager, then you’ll see details of the driver version that you currently have installed, who made the driver, the date that the driver was released, the hardware that it’s driving, who made the hardware, the hardware’s model number, etc.

Every now and then a hardware manufacturer’s research and development team will discover a flaw in a driver that was previously unnoticed. They’ll rewrite the driver to eradicate that flaw and improve performance of the product. – Either that or they’ll discover a security vulnerability in it and write it out. Having rewritten and tested the new driver version, they’ll release it to the public, so that their customers get better performance from their product.

Unless you keep a lookout for new drivers you could miss out on such performance-gains. – Which is where an occasional visit to a manufacturer’s website can be very helpful. If you rely on Microsoft Update then you’ll get the odd update; but it won’t be anything like new, and you’ll probably miss out on many new driver versions.

The above paragraph applies particularly to chipset drivers and graphics drivers; so keep a lookout for new versions of the drivers that you’re using especially in the case of those devices.

- So in the best geeky tradition, always keep your drivers up to date, and you’ll always get more from your box.

Have you checked your drivers recently? Do you keep an eye on your drivers?