Re:Have FTDI kicked-off round 2 of the clone wars?
by raphman_ on Monday February 01, 2016 @09:02AM
(#11011754)
The problem is that FTDI ist taking it out on the customer, and hoping that "the FTDI driver bricked my board" somehow gets those customers to (1) realize that the problem is a counterfeit chip, (2) work their way up the supply chain until they find the party at fault (or get the supply chain to take care of the problem), and (3) manage to get a replacement for the product which uses genuine FTDI chips.
Why not just pop up a small window with a message "Hey, this product seems to contain counterfeit chips. Please tell us where you bought it so that _we_ can take care of the problem."
Re:Have FTDI kicked-off round 2 of the clone wars?
by jnky on Monday February 01, 2016 @10:49AM
(#11012402)
Just FYI, but displaying a Message Box from the context of a Windows device driver is not trivial and would add significant overhead to the driver.
I'd prefer it if FTDI weren't utter douchebags around this whole ordeal. I understand they have to make money, but since when is it a problem when devices are API-compatible with existing device drivers? As far as I'm concerned, this is a rather common and generally beneficial thing.
Re:Have FTDI kicked-off round 2 of the clone wars?
by hueving on Monday February 01, 2016 @10:56AM
(#11012461)
That's because FTDI has taken the approach of fucking as many people that didn't actually do anything wrong to somehow punish the counterfeiters. How does bricking something sold 4 years ago do anything helpful?
But why do you simply accept that? Have you even complained to Farnell?
Read the sundry web forums, very few people complain to their distributor. Everyone bitches about FTDI.
And that's what's really bugging me here. In the FTDI case the problem has obviously gotten out of hand. I can totally understand that the manufacturer wants to get tougher.