<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I wondered how long that would last.<br>
<br>
Lots of people were very angry with FTDI on this one. I can
understand them not wanting their driver to work with counterfeit
chips, but they went too far.<br>
<br>
As I understand it, they are going to do the same thing as Prolific
and prevent the driver from working with counterfeit chips going
forward. In the interim, MS has rolled back the FTDI driver on the
Windows auto-update service (so no one will get the "bad" driver
going forward) while FTDI is preparing a new version of the driver
to go out soon that will simply error out when it detects a fake
chip (no more bricking).<br>
<br>
<br>
<div class="moz-cite-prefix">On 10/24/2014 02:17 PM, n4lbl wrote:<br>
</div>
<blockquote
cite="mid:CANR7-Zuc2NLhgU7nkdbtk9cf3p5un0ajwjZvnv-LRcx8oSRFdw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">
and it changes.....</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)">/.
FTDI Removes Driver >From Windows Update That Bricked
Cloned Chips</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><a
moz-do-not-send="true"
href="http://hardware.slashdot.org/story/14/10/24/1330252/ftdi-removes-driver-from-windows-update-that-bricked-cloned-chips">http://hardware.slashdot.org/story/14/10/24/1330252/ftdi-removes-driver-from-windows-update-that-bricked-cloned-chips</a></div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,102)"><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 22, 2014 at 1:32 PM, Aubrey
Turner <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:aubrey.c.turner@gmail.com" target="_blank">aubrey.c.turner@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">The common
wisdom with regards to USB-to-serial cables seems to be that<br>
one should pick FTDI over Prolific because of all the
Prolific<br>
counterfeits in circulation. It seems that this is now
becoming a<br>
problem with FTDI, as well.<br>
<br>
Up to now it was not a problem for the end-user. FTDI has
decided to<br>
change that with their latest driver, which changes the
configuration of<br>
a "fake" FTDI chip so that it is rendered useless (at least
without a<br>
bit of fiddling with configuration tools and device IDs on
Linux or XP).<br>
<br>
I hadn't realized that FTDI had such an issue with fake
chips until I<br>
read this article. Some of the comments point out that the
end-user of<br>
the device has no way of knowing whether the chip is genuine
or not.<br>
Further, as noted above, many in the radio programming
community<br>
purchased devices touted as having FTDI chips in good faith
as an effort<br>
to avoid the counterfeits Prolific chips.<br>
<br>
Anyway, if you suddenly have issues with your FTDI
USB-to-serial<br>
adapter, take a look and see if the PID has been changed to
0. If so,<br>
then you may have been affected by this new driver.<br>
<br>
Sources:<br>
-<br>
<a moz-do-not-send="true"
href="http://hackaday.com/2014/10/22/watch-that-windows-update-ftdi-drivers-are-killing-fake-chips/"
target="_blank">http://hackaday.com/2014/10/22/watch-that-windows-update-ftdi-drivers-are-killing-fake-chips/</a><br>
- <a moz-do-not-send="true"
href="http://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/"
target="_blank">http://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/</a><br>
- <a moz-do-not-send="true"
href="http://forum.arduino.cc/index.php?topic=270175.0"
target="_blank">http://forum.arduino.cc/index.php?topic=270175.0</a><br>
_______________________________________________<br>
chirp_users mailing list<br>
<a moz-do-not-send="true"
href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a moz-do-not-send="true"
href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users"
target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
chirp_users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a>
<a class="moz-txt-link-freetext" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a>
</pre>
</blockquote>
<br>
</body>
</html>