Discussion in 'Windows Desktop Systems' started by dotbatman, Jan 30, 2002.

  1. dotbatman

    dotbatman Guest

    Saw this today on Lockergnome:

    "When the courier drops off a package, someone must sign for it to verify the transaction. The same holds true for drivers in Windows 2000 and XP. Despite the whining of legacy-loving lusers (local users), this is a fantastic feature. Nine times out of ten, Windows doesn't crash Windows. Buggy drivers, on the other hand, have been known to cause countless contentions. Microsoft instituted "driver signing" to stop problems before they started. If an installed driver is NOT signed, caveat clickor (let the user beware). Use VERIFIER.EXE - the Driver Verifier Manager - to gather information about and troubleshoot your system's drivers. Admittedly, this tool was specifically designed with ubergeeks (and driver developers) in mind. For details and usage guidelines, refer to article Q244617 in the Microsoft Knowledge Base. Check with hardware manufacturers to see if there are WHQL (Windows Hardware Quality Labs) certified drivers available for your device(s). They may not be optimized for speed, but stability is sometimes more important."

    Hope someone might find this helpful!
  2. Dick

    Dick Guest

    Great tip - I wish I had seen it before having to "reinvent" the wheel. I've also posted something similar after encountering application drivers that didn't want to play nice with Windows XP.

    Only problem in using it is a lack of good clear & concise instructions on how to do so. This is typical of "Microscraps" bulletins though. Have you ever found a third party write up on the verifier tool that is better? If so, I'd like to hear about it.