<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">If they had simply said, sorry this is
a fake FTDI and refused to work, I would agree with you.<br>
<br>
But they don’t. They deliberately go out of their way to 'break'
the fake FTDI chip, no warning or anything. <br>
<br>
This is malicious and probably illegal, wilful property damage
comes to mind.. <br>
<br>
The main issus is that 95% of consumers have no idea there was
even fake chips, let alone that they had one. And it;s the
customer this is punishing. The seller of the chips doesn’t care,
they already have the money from the consumer.<br>
<br>
<br>
<br>
<br>
<br>
On 27/10/14 15:35, Charles Manning wrote:<br>
</div>
<blockquote
cite="mid:CAE21AQoQ6S0HB4KDT4L-=rsPVKYDUXjvUcOagQrbsPKeU8wJnw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>I cannot see how either MS or FTDI are to blame or can be
seen to be illegal.<br>
<br>
</div>
That driver works fine with a legitimate product.<br>
<br>
Someone has chosen to build a product which pretends to be an
FTDI chip, but is not. They're not paying for all FTDI's
software engineering etc (as good or rubbish as they might
be). They're just trying to mimic the FTDI to encourage people
to use software in a way that does not conform to the
licensing policy.<br>
<br>
</div>
USB.org issues VIDs specifically so that software can identify
the product it is working with. If you produce a product that
hi-jacks some elses VID and that driver does not work, or even
breaks, your device then it is YOUR fault.<br>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Oct 27, 2014 at 3:16 PM, Mark
Beckett <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:m.beckett@amuri.net" target="_blank">m.beckett@amuri.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I've been
getting emails from my overseas contacts for the few days.<br>
<br>
This is some other info regarding what was a deliberate and
possibly illegal move by FTDI.<br>
<a moz-do-not-send="true"
href="http://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/msg535270/#msg535270"
target="_blank">http://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/msg535270/#msg535270</a><br>
<br>
I did find this one which shows the internals of both
genuine and<br>
non-genuine which is interesting.<br>
<a moz-do-not-send="true"
href="http://zeptobars.ru/en/read/FTDI-FT232RL-real-vs-fake-supereal"
target="_blank">http://zeptobars.ru/en/read/FTDI-FT232RL-real-vs-fake-supereal</a><br>
My view is FTDI have overstepped the mark by
making them non<br>
functional, regardless of the copyright/you're using our
driver.<br>
The end-user probably has no idea of what is inside the
device they<br>
just brought.<br>
FTDI should have detected the device as not genuine
and refused to<br>
load the driver for it.<br>
The customer would then have returned the product to the
supplier,<br>
and the corrective action could then take place.<br>
This 'fix' has probably signed the end for FTDI,
given that other<br>
products that are available, and that their product is
not cheap to<br>
start with.<br>
MS are equally to blame since they have deployed a driver
that<br>
knowing renders devices useless that were working and are
not theirs<br>
to mess with.<br>
By changing the device, it no longer works on other OS's,
which is<br>
well beyond their software agreements no matter how you
read their EULA.<br>
Hopefully someone decides to sue them, maybe someone who
already<br>
dislikes them and has big pockets ....<br>
In a twist of irony, it seems the FTDI software
(FT_prog) will<br>
happily talk to the non-genuine device to write the
VID/PID, and I<br>
have a copy of the older version if anyone gets trapped.<br>
<br>
While Volker may think he's quite safe using Linux, the
issue is if the device was connected to a windows box with
the new drivers, it won't work on his linux box now, since
the PID has been set to zero.<br>
<br>
I have some sympathy for FTDI, but using Microsoft to
deliberately reset the PID has gone too far, it should have
simply refused to talk to the device.<br>
And if you read some of the various blogs, it was FTDI that
pulled it, most likely because of the backlash/fallout that
was coming.<br>
<br>
It shouldn't affect any Arduino UNO or true clone as they
use an Atmel 8U2 or 16U2 to interface to the USB.<br>
Since there are some who suggest not to use 'cheap chinese
knock-offs' they won't have to worry either.... :-)<span
class="HOEnZb"><font color="#888888"><br>
<br>
Mark</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
Mark Atherton wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Another gem from Julian.<br>
<br>
... and there could be quite some fallout with the
Arduino community.<br>
<br>
I am still dwelling on the consequences of FTDI's
actions.<br>
<br>
-mark<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Subject: Heard about the FTDI caper?<br>
To: Mark Atherton <<a moz-do-not-send="true"
href="mailto:markaren1@xtra.co.nz" target="_blank">markaren1@xtra.co.nz</a>><br>
<br>
<<a moz-do-not-send="true"
href="http://brainwagon.org/2014/10/24/ftdi-gate/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+brainwagon+%28brainwagon%29"
target="_blank">http://brainwagon.org/2014/10/24/ftdi-gate/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+brainwagon+%28brainwagon%29</a>><a
moz-do-not-send="true"
href="http://brainwagon.org/2014/10/24/ftdi-gate/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+brainwagon+%28brainwagon%29"
target="_blank">http://brainwagon.org/2014/10/24/ftdi-gate/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+brainwagon+%28brainwagon%29</a>
<br>
<br>
Hi Mark<br>
<br>
Just read about this...J<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
Chchrobotics mailing list <a moz-do-not-send="true"
href="mailto:Chchrobotics@lists.linuxnut.co.nz"
target="_blank">Chchrobotics@lists.linuxnut.co.nz</a><br>
<a moz-do-not-send="true"
href="http://lists.ourshack.com/mailman/listinfo/chchrobotics"
target="_blank">http://lists.ourshack.com/mailman/listinfo/chchrobotics</a><br>
Mail Archives: <a moz-do-not-send="true"
href="http://lists.ourshack.com/pipermail/chchrobotics/"
target="_blank">http://lists.ourshack.com/pipermail/chchrobotics/</a><br>
Web site: <a moz-do-not-send="true"
href="http://kiwibots.org" target="_blank">http://kiwibots.org</a><br>
Meetings 3rd Monday each month.<br>
<br>
When replying, please edit your Subject line to
reflect new content.<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
Chchrobotics mailing list <a moz-do-not-send="true"
href="mailto:Chchrobotics@lists.linuxnut.co.nz"
target="_blank">Chchrobotics@lists.linuxnut.co.nz</a><br>
<a moz-do-not-send="true"
href="http://lists.ourshack.com/mailman/listinfo/chchrobotics"
target="_blank">http://lists.ourshack.com/mailman/listinfo/chchrobotics</a><br>
Mail Archives: <a moz-do-not-send="true"
href="http://lists.ourshack.com/pipermail/chchrobotics/"
target="_blank">http://lists.ourshack.com/pipermail/chchrobotics/</a><br>
Web site: <a moz-do-not-send="true"
href="http://kiwibots.org" target="_blank">http://kiwibots.org</a><br>
Meetings 3rd Monday each month.<br>
<br>
When replying, please edit your Subject line to reflect
new content.<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Chchrobotics mailing list <a class="moz-txt-link-abbreviated" href="mailto:Chchrobotics@lists.linuxnut.co.nz">Chchrobotics@lists.linuxnut.co.nz</a>
<a class="moz-txt-link-freetext" href="http://lists.ourshack.com/mailman/listinfo/chchrobotics">http://lists.ourshack.com/mailman/listinfo/chchrobotics</a>
Mail Archives: <a class="moz-txt-link-freetext" href="http://lists.ourshack.com/pipermail/chchrobotics/">http://lists.ourshack.com/pipermail/chchrobotics/</a>
Web site: <a class="moz-txt-link-freetext" href="http://kiwibots.org">http://kiwibots.org</a>
Meetings 3rd Monday each month.
When replying, please edit your Subject line to reflect new content.</pre>
</blockquote>
<br>
</body>
</html>