Hi predator2003,
first off, welcome. I recieved email.
I wanted to look up what you had posted in the past, and see you are coming from the woodwork out, which is pretty much what we ask our users should do so you can help us help you.
How do we check wether signing is broken?
First.. How do we know that a driver is MSFT WHQL signed? The vendor download site either claims it is, or it doesn't.
The INF has txt in it, and that "may" give you an idea, but most often won't.
(besides that, when you edit the INF, signing can break.)
There IS a way to see wether original download was signed by MSFT..
Rightclick the driver.CAT file, click tab for properties.
Then click the tab for digital signature.
If you see microsoft in there, it was submitted to the quality labs and got an approval.
(Which unfortunately... Which doesn't mean it will happily work alongside its older kin and variants.)
I personally think that the signed driver got tested on the hardware it had to work on, and does not crash with the supplied hardware.
However, we have been telling the world (and I am trying to tell MSFT) that OEM driver writers have created an impossible situation which is of interest to EVERYBODY doing roll-outs on different machines.
(Hey, not always "wildly" different. Example. A few weeks ago I saw an Nvidia driver for a Geforce 6600 would not correctly work on a different brand Geforce 6600.)
We hope to not have to break signing when we have to work around issues, and tell people they can edit DriverPacks (or even create their own private build) to fill their own need.
by the way, your English might be easier on people than mine.
The answer was 42?
Kind regards, Jaak.