Comments on: Using USBTiny version 2 in Vista – driver signing http://www.adafruit.com/blog/2010/02/18/using-usbtiny-version-2-in-vista-driver-signing/ electronics, open source hardware, hacking and more... Tue, 07 Sep 2010 00:12:43 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Mike Hankey http://www.adafruit.com/blog/2010/02/18/using-usbtiny-version-2-in-vista-driver-signing/comment-page-1/#comment-10908 Mike Hankey Mon, 26 Apr 2010 19:48:28 +0000 http://www.adafruit.com/blog/2010/02/18/using-usbtiny-version-2-in-vista-driver-signing/#comment-10908 I am running Windows 7 64 bit and had drivers loaded and working in a matter of minutes using the Driver Signature Enforcement Override tool mentioned above. I had also tried setting the Group Policy to ignore unsigned drivers but this didn't seem to work for me. I am running Windows 7 64 bit and had drivers loaded and working in a matter of minutes using the Driver Signature Enforcement Override tool mentioned above.
I had also tried setting the Group Policy to ignore unsigned drivers but this didn’t seem to work for me.

]]> By: Keith http://www.adafruit.com/blog/2010/02/18/using-usbtiny-version-2-in-vista-driver-signing/comment-page-1/#comment-8770 Keith Thu, 18 Feb 2010 06:50:59 +0000 http://www.adafruit.com/blog/2010/02/18/using-usbtiny-version-2-in-vista-driver-signing/#comment-8770 "Signing with a test key" + "boot Windows in test mode" = standard procedure for testing kernel drivers. That said, there is some incorrect information in the linked article. Yes, 64-bit Vista and Win7 *require* signed drivers (and this requirement cannot be disabled), but 32-bit systems do not by default. Also, the statement "...developers have to pay Microsoft to receive verified certificates..." is misleading. Yes, driver signing certificates *do* cost money, but they're not purchased from Microsoft. There used to be a few places to get signing certs, but I think Verisign is the only source now. Unfortunately, they're expensive ($499/year). This onerous & expensive requirement effectively eliminates the possibility of creating open-source drivers for modern versions of Windows. Pity. “Signing with a test key” + “boot Windows in test mode” = standard procedure for testing kernel drivers.

That said, there is some incorrect information in the linked article.

Yes, 64-bit Vista and Win7 *require* signed drivers (and this requirement cannot be disabled), but 32-bit systems do not by default.

Also, the statement “…developers have to pay Microsoft to receive verified certificates…” is misleading. Yes, driver signing certificates *do* cost money, but they’re not purchased from Microsoft. There used to be a few places to get signing certs, but I think Verisign is the only source now. Unfortunately, they’re expensive ($499/year).

This onerous & expensive requirement effectively eliminates the possibility of creating open-source drivers for modern versions of Windows. Pity.

]]>