Digital Signature for UMAX 1394 Scanner (Firewire)

  • Thread starter Thread starter Katie Kroutter
  • Start date Start date
K

Katie Kroutter

I am aware of the glich in W2000 Pro where it keeps asking
and there is none and won't be none.

But, where can I find the Peripheral Drivers Compatability
List wherein I can see if Microsoft has written a Digital
Signature for a UMAX 1394 Firewire Scanner.

I want to be able to download this entire document for
future issues.

Please direct me to the proper name for this when searhing
Microsoft's support center and/or resources list.

Thanks and God Bless the person who can answer this
question, I have been waiting a long time.....
 
Katie Kroutter said:
I am aware of the glich in W2000 Pro where it keeps asking
and there is none and won't be none.

But, where can I find the Peripheral Drivers Compatability
List wherein I can see if Microsoft has written a Digital
Signature for a UMAX 1394 Firewire Scanner.
Click to expand...

It's up to Umax to make the signature available to their customers,
not Microsoft.

In the meantime, just turn the digital signature option off in Win2K
(Control Panel/System/Hardware/Driver Signing/Ignore + "Apply
setting as system default".

Rick
 
Katie,

Just use an unsigned driver.

It's up to the vendor, not Microsoft, to get a signed driver, and many
vendors choose not to.

Here's the (oversimplified) process: Microsoft sets a minimum quality bar
for device drivers to get signed. Your driver must do this, your driver
must not do that, your driver must handle this properly, etc.

If a vendor wants their driver signed, they must write a driver that
conforms to those rules and submit it to Microsoft for signing. A lab tests
the driver to ensure it follows all the rules, and when testing is complete,
Microsoft will provide a signature for the driver that the vendor supplied.

Many vendors simply choose not to submit drivers for signing. There's
nothing Microsoft can do if a vendor decided not to submit a driver for
signing.

Having said that, there's nothing inherently bad about using an unsigned
driver... you just don't have any guarantee that the driver follows the
minimum rules required for signing.

-Matt
 
Matthew Mucker said:
Katie,

Just use an unsigned driver.

It's up to the vendor, not Microsoft, to get a signed driver, and many
vendors choose not to.

Here's the (oversimplified) process: Microsoft sets a minimum quality bar
for device drivers to get signed. Your driver must do this, your driver
must not do that, your driver must handle this properly, etc.

If a vendor wants their driver signed, they must write a driver that
conforms to those rules and submit it to Microsoft for signing. A lab tests
the driver to ensure it follows all the rules, and when testing is complete,
Microsoft will provide a signature for the driver that the vendor supplied.
Click to expand...

More specifically, Microsoft spends a few hours simply
making sure the drivers load properly under a set of
different conditions, and charges the vendor $10,000 per
driver/certificate.

I used to do this process for HP, it's a major scam. MS's
testing doesn't take into account 99% of what's found in the
real world. No wonder most vendors don't bother with
the cost and hassle of getting digital certs for their drivers.

Rick
 
Back
Top