Vista 64 driver update frequency and latency

DanNeely

Supreme [H]ardness
Joined
Aug 26, 2005
Messages
4,854
Since vista64 only accepts signed drivers, I'm wondering how long the signing process takes and how frequently card makers run their updated drivers through it.
 
I haven't had any problem with whql or beta drivers off of nvidia's website and they are quite frequent. I believe every time Jen-Hsun Huang takes a dump they must release a driver.
 
I don't think it slows down driver development at all. Once the company purchases their verisign license, it's business as usual.
 
OK. I think I'm confused about what MS was doing. The stated benefits were increased stability and to keep malware drivers out entirely. If the company making the driver is able to sign them itself though I can't see how the first is supposed to work, and using a verisign cert would let any malware author who has swiped a few grand buy it's way into being able to write keylogging drivers.
 
OK. I think I'm confused about what MS was doing. The stated benefits were increased stability and to keep malware drivers out entirely. If the company making the driver is able to sign them itself though I can't see how the first is supposed to work, and using a verisign cert would let any malware author who has swiped a few grand buy it's way into being able to write keylogging drivers.


Nvidia is a multi-billion dollar corporation, they have a vested interest in releasing functional drivers.
 
Nvidia is a multi-billion dollar corporation, they have a vested interest in releasing functional drivers.

True. Not all companies are as enlightened though. If you give a global carte blanche to hardware makers to release 'beta drivers' on their own recognisance the companies whose bad drivers have been causing BSODs for years will simply never release anything not beta, or only release most of thier functionality in beta form to avoid having to make it bug free. Going the other way and splitting the industry into companies that are trusted to police themselves and others that need to prove everything to MS first is just begging for lawsuites from those in the lesser group.
 
If this is not about graphics drivers, which are released in 64-bit at the same time as 32 by both ATi and nVidia, shouldn't this belong in the OS forum?
 
The way the thread's drifted probably. I originally posted here because GFX cards were the area where non timely updates would have the most severe impact. There's generally minimal impact to using year old mobo or audio drivers.
 
I think the signed driver issue is really more an accountability issue than an actual quality control procedure. I'd guess MS has provided some basic information and testing procedures to the companies, and required them to register with VeriSign, and if there's a major screw-up, MS will not be so cooperative in the future, and you'll see more of "so-and-so has better drivers, and more timely than so-and-so," or at least you would if there were more than two major gfx cards manufacturers.

And I've actually seen, for all the hardware I've purchased, 64/32 drivers released together, all the time, no exceptions. Granted all my stuff is newer, but it seems like the 64 bit issues are mostly a thing of the past, except for legacy programs and hardware. Makes me regret not going 64 myself.
 
And I've actually seen, for all the hardware I've purchased, 64/32 drivers released together, all the time, no exceptions. Granted all my stuff is newer, but it seems like the 64 bit issues are mostly a thing of the past, except for legacy programs and hardware. Makes me regret not going 64 myself.

Thank you. That's exactly what I wanted to know. When I build my new box, I'm not planning on keeping any hardware except my possibly my tvtuner.
 
Back
Top