Has anyone tried getting drivers signed - Page 1
Forum section: electronics / general

author: Neilm
author_rank: Super Contributor
timestamp: February 02, 2012, 08:28:35 pm
content: I am currently working on a project that we are considering using a USB interface using an FTDI chip. It would look much nicer if the user plugs the unit in and Windows shows our company name as it installs.Has anyone ever tried to get a driver signed for the Windows? If not, does anyone know how one would go about it, or know a website with more information?YoursNeil

author: AlphZeta
author_rank: Regular Contributor
timestamp: February 02, 2012, 08:35:56 pm
content: Have you checked Microsoft's site for more information (http://msdn.microsoft.com/en-us/windows/hardware/gg487317)?According to the site, "Components must be signed by a certificate that Windows "trusts" as described in the white papers on this site"

author: PeterG
author_rank: Frequent Contributor
timestamp: February 02, 2012, 11:44:51 pm
content: Depending on volume, you can order FTDI chips with your company/product names pre programmed.I have seen FTDI chips that can read the required info from an eeprom.(i am not sure these are still available).Regards

author: Psi
author_rank: Super Contributor
timestamp: February 03, 2012, 12:06:28 am
content: The FT232 chip eeprom can be programmed with a tool from their website.You can change names and things.I've not found a way to change the name that appears in device manager (it might be possible) but you definitely can change the text that appears when you plug the device into a pc for thefirsttime.The popup where it goes "Windows has found new hardware and is searching for a driver" will display the name of the device it found.

author: PeterG
author_rank: Frequent Contributor
timestamp: February 03, 2012, 12:39:04 am
content: If you really want to have your product and company details to show up, you first need to apply and receive a unique PID and VID from the USB crowd. then you can develop the relevant drivers and spend many $$$ getting them signed by Microsoft.When it comes to USB, developing the hardware is the easy bit.Regards

author: kiyotewolf
author_rank: Contributor
timestamp: February 03, 2012, 01:21:08 am
content: How about just include an installer that says.."HEY.. OUR COMPANY IS INSTALLING YOUR DRIVERS"with a splash screen, and be done with it.~Paul

author: mikeselectricstuff
author_rank: Super Contributor
timestamp: February 03, 2012, 01:21:33 am
content: Showing your product name during installation is no problem - You can get a PID from FTDI to use with their VID - this is programmed into the chip, and the driver .INF files modified. The whole user install process will show the device name you programmed so it looks like any other USB device.You should also use the D2XX API to avoid the user having to mess with COM port mappings. On most FTDI drivers you can configure it to not expose virtual COM ports via the config options set when prgramming the VID/PID into the chip.If you care about the driver signing stuff, there is a process to get their drivers with the your PID signed, which I think is much simpler than the normal signing process as there is no change to the actual driver code.This FTDI appnote explains the process

author: Neilm
author_rank: Super Contributor
timestamp: February 03, 2012, 04:04:38 pm
content: Thanks for this info. At first glance it doesn't look too bad. I suspect that the devil is in the detail though.Neil

author: Simon
author_rank: Unknown
timestamp: February 03, 2012, 10:41:07 pm
content: any particular reason why you need to suck up to micro$oft ? I've installed plenty of programs and devices from well known companies and it said in their install instructions to just click the trust button when windows says that it does not "know" the driver. An example was the driver for Nero's virtual CD/DVD Drive/burner so don't worry about being "unprofessional", even the pros don't give a toss about the "windows club"

author: baljemmett
author_rank: Unknown
timestamp: February 03, 2012, 11:24:24 pm
content: Quote from: Simon on February 03, 2012, 10:41:07 pmGood luck doing that on a 64-bit systemYou have to be running the 64-bit versions of the OS in a special test mode before they'll accept an unsigned driver, I believe.

author: Psi
author_rank: Super Contributor
timestamp: February 04, 2012, 12:02:01 am
content: i've installed stuff on win7 x64 which came up with a warning about non-signed code and asked for permission to install.And i don't remember doing anything special with my win7 except maybe disabling UAC (may not be relevant).

author: elliott
author_rank: Regular Contributor
timestamp: February 04, 2012, 06:46:31 am
content: Quote from: Simon on February 03, 2012, 10:41:07 pmYou could even treat it as a feature, since unsigned drivers reduce the cost of the product. "We didn't pay the Microsoft tax and passed the savings on to you."

author: amyk
author_rank: Super Contributor
timestamp: February 04, 2012, 10:59:40 am
content: Quote from: Psi on February 04, 2012, 12:02:01 amApplications are OK non-signed (but it complains), drivers are enforced to be signed.

author: Simon
author_rank: Unknown
timestamp: February 04, 2012, 11:01:55 am
content: I've installed no end of cheap devices like those bought on ebay where i have just clicked the trust this driver option. It is just a way of microsoft trying to screw money out of hardware manufacturers as well as bewildered users. Join the Ms club, where we make your products look better by not accusing them of being unsafe !