3 ms·

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 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."

jnky 11y ago
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.