3 ms·
Somebody, somewhere had to install a driver. And, because you could never count on it, you can't design to it. Now, since most things use a Prolific chip, you
by bsder 8y ago
Somebody, somewhere had to install a driver. And, because you could never count on it, you can't design to it.
Now, since most things use a Prolific chip, you only have to install the driver for one device and you pick up a ton of them.
But it has to be installed by somebody, and that means all of the silliness that goes along with Windows driver installation.
- oarsinsync 8y agoFTDI chips have their driver deployed by default on most Windows, Mac and Linux installs. It's nice being able to buy a USB/serial cable and it just work, without needing to deploy any drivers at all. Check it out!
- swish_bob 8y agoHad to install FTDI drivers on (an admittedly old) Windows laptop 3 weeks ago before I could use it to talk to the Cisco gear I was reconfiguring ...
- InitialLastName 8y agoIIRC the FTDI chips use a non-standard com driver on Win 7. IF you want your device (with your VID and PID) to show up as a serial port, you need to associate your device with the usbserial driver, which at the very least requires a custom .inf.