Not "bad". And not necessarily greater performance. That really wasn't the point. But you'll lessen the possibility of another device conflicting with the video card during the installation if you'll wait until the other devices are already installed, such as the sound card, mouse driver, NIC card, etc.
Most people tend to install the video card driver first, simply to make it easier to see the entire display while working in the system. But after having done many installations, on hundreds of different configurations, it has become very apparent to me that installing a third-party video card driver last in the sequence allows a much greater chance for system stability, and will avoid most conflicts, which are not ordinarily encountered when running strictly with the default Windows drivers for a device.
You won't get much performance out of that video card if it locks up and drops you back to the desktop.
This started to become particularly important when the GeForce cards were first released, IMO.
As for the other items in the sequence, such as a service pack, hotfixes, and chipset drivers ... this creates a more stable environment for adding other components.
For example, installing a modern game in Win2K without first installing the compatibility updates is probably not the best sequence of events. And it might not run well if the chipset drivers aren't installed, and the CD-ROM is stuck in PIO mode. And if the video card is conflicting with the sound card, even if the system is ACPI, sudden reboots are at the very least, disturbing. And wouldn't you want the latest DirectX files already on the drive before installing the video card drivers, just in case the system accidently sets the AGP texturing in PCI mode? It's nice to have the diagnostic program already in place before upgrading the device.
Look at it as assembling the entire system, piece by piece, as with software building blocks. Every part of a stable system depends on another, whether it's correctly setting the CMOS after adding a hard drive, but before installing the OS ... or checking for updated firmware for an optical device before installing burning software and a software DVD player.
It's surprising, but many people who like to build computers are fairly meticulous about installing the hardware, but once this is finished, really have made no deployment plans on how the operating system, drivers, and programs should be installed. It becomes a guessing game at that point. Patches? Sound card drivers? Modem drivers? The old scanner software? Or maybe just stop, relax, and play a little solitaire?
You'd be amazed how many people don't even have a disk prepared with the drivers for the system. (Well, maybe not you, dh.) They just start downloading, and updating as they go, in kind of a random fashion. And if a conflict or a incompatibility issues arises, they can't even make a good judgement call about they were doing at the time. Who knows what did what to whom, and when?
How many times have you seen. "It just suddenly stopped working! All I did was ..."
Yep, I've heard that tune before, one or twice. And nearly all of that is software-related.
You catch my drift?
Toejam31
<font color=red>My Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new"><font color=green>Toejam31's Tantalizing Tantric Toy</font color=green></A>
<font color=red>Second Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new"><font color=green>Toey's Dynamite DDR Duron</font color=green></A>
____________________________________________________________
<font color=purple>"Procrastination on your part does not constitute an emergency on my part."</font color=purple>