View Single Post
Old 03-11-2009, 18:51   #57 (permalink)
Black_Daimond
No Life Poster
 
Black_Daimond's Avatar
 
Join Date: Sep 2005
Location: The Netherlands Antilles
Age: 46
Posts: 758
Member: 179391
Status: Offline
Thanks Meter: 57
To much!

Quote:
Originally Posted by Lead View Post
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.

I have just used a PC with Xp instead. I will study this part about changing Cable ID later. No time for it now.

Thank you any way "Lead"
  Reply With Quote
 
Page generated in 0.14068 seconds with 6 queries