walt
Newbie
Karma: +0/-0
Offline
Posts: 16
|
|
« Reply #2 on: July 29, 2015, 11:15:45 AM »
|
|
|
Frustrating isn't it? Just went through the same experience yesterday.
The only positive thing to come out of it was getting familiar with modifying vid and pid numbers in the FTDI inf files for Windows XP. Also, after plugging in the new cable, ftdibus.inf is the first driver you give it, this adds a "USB Serial Converter" entry under "Universal serial bus controllers". Then device manager finds a new COM port, and you give it the ftdiport.inf .
ftdibus.inf installs with no errors, but installing ftdiport.inf results in an error: "This device cannot start. (Code 10)".
Time for a cable with an FTDI chip. Hopefully it will be genuine FTDI, or again there might be problems.
|
|
|
Logged
|
|