3 ms·
What specific piece of equipment was affected? (not doubting - just curious, as I've not come across specific examples of people being affected by this driver)
by jameshart 12y ago
What specific piece of equipment was affected? (not doubting - just curious, as I've not come across specific examples of people being affected by this driver)
- drzaiusapelord 12y agoThis guy in /r/sysadmin claims 35 devices nuked: http://www.reddit.com/r/sysadmin/comments/2k6wjk/fyi_ftdi_deployed_a_driver_update_through_windows/ http://www.reddit.com/r/sysadmin/comments/2k6wjk/fyi_ftdi_de...
- tedunangst 12y agoSo, in other words, they didn't damage your equipment.
- jameshart 12y ago35 devices put together by students doing EE projects... well, that's annoying, but they are at least direct consumers/users of the counterfeit components - presumably they have the option/ability to replace the chip with a genuine one once they source one. I've yet to hear of any end user finding that a commercially purchased peripheral has been bricked by this driver because its manufacturer used counterfeit parts, though. Would be fascinated to hear about such an example.