View Single Post
Old 03-11-2009, 16:51   #55 (permalink)
Lead
No Life Poster
 
Lead's Avatar
 
Join Date: Aug 2008
Age: 48
Posts: 3,292
Member: 1841
Status: Offline
Thanks Meter: 468
Thumbs up

Hi Black_Daimond,

the issue is caused by Windows Vista x64 itself.
There is a known limitation of this operating system - it accepts signed drivers only.
Since the only way to properly sign these drivers is revealing our identity, it is not an acceptable option.
Therefore, the only way to manage this situation is to change the USB device ID from UC-10 to Generic FTDI. Then you would be able to use generic signed drivers from http://www.ftdichip.com (look for approved CDM drivers) with your instance of Windows Vista x64 OS.
On the FTDI home page there is a special utility for editing cable EEPROM content that allows for changing the device ID, among other things.
The ID for UC-10 cable is E268, all you need to do is to change it to generic one of 6001 under 32-bit Windows. The vendor ID should remain unchanged (0403).

I'll not go into details, this is an advanced operation which involves a risk of putting the cable to unusable condition, therefore you should discuss it with more skilled people around you, if the information provided above does not suffice to you.

Best regards,
Lead.
  Reply With Quote
 
Page generated in 0.12644 seconds with 6 queries