请问我在哪里能找到需要的信息来编程地安装CyPress驱动程序？

在32位操作系统中，您应该能够通过安装程序实现这一点。在64位，你必须签署司机。
当做，
阿南德



     以下为原文
   In 32-bit OS you should be able to achieve this through installer. In 64-bit you'll have to sign the driver.
    Regards,
    Anand

这样做的过程被称为“软件第一安装”方法。意思是在硬件插入之前安装驱动程序。驱动程序和其他相关文件放在适当的位置，当设备***入时，它自动绑定到驱动程序。这就是你要找的吗？
为了这个微软提供了一堆工具，
驱动程序安装框架WIX安装程序首先需要创建MSI或其他安装程序，并使用DIFX API或WIX并合并安装文件来安装驱动程序。



     以下为原文
  The procesdure to do this is called "Software First Install" method. Meaning you install the driver before your hardware is plugged in. The driver and other associated files are put in appropriate location and when the device is plugged it automatically binds to the driver. Is this what you are looking for?
    In order to this Microsoft providea a bunch of tools,
   

    

• DIFX - Driver installation Framework    
  
• WIX Installer   
  

    First you need to create an MSI or other installer and used DIFX API or WIX and merge the installation files to install the driver. 

请注意，对于32位WindowsXP、WIN7和Vista，驱动程序不需要签名，因此您需要做的是将CysB.SIS文件和INF文件（带有VID PID和其他信息）放置在Windows搜索的适当位置。但是在64位机器的情况下，您需要从微软中签出设备驱动程序。你需要让你的USB设备固件运行起来。U.B.ORG提供了一套测试WHQL认证的固件的工具。这个结果必须发送给微软，他们将提供一个.CAT文件。此文件需要包含在安装程序中。
希望这有帮助。



     以下为原文
   Please note that for 32 bit Windows XP, Win7 and Vista the driver need not be signed, hence all you need to do is put the CyUSB.sys file and the INF file(with your VID PID and other info) in proper location where windows searches. But in case of 64 bit machines, you need to get your device driver signed from Microsoft. You need to have your USB device firmware up and running. USB.org provides a set of tools to test your firmware for WHQL certification. The results of this must be sent to Microsoft and they will provide you a .CAT file. This file needs to be included in your installer.
    Hope this helps.

谢谢你的回复！
我看了一下DIFX API，我打算使用它。唯一的事情是我们通过ClickOnce部署应用程序（而不是Windows安装程序包），因此我们不能合并安装文件。我认为，即使在软件安装之前安装了驱动程序，即使硬件未***入，它也应该工作。
但是，如果用户在之前插入它，而Windows错误地识别它，我以后如何在编程窗口强制使用正确的驱动程序呢？



     以下为原文
    Thanks for your replies!
         I had a brief look to DIFX API and I'm planning tp use it. The only thing is that we deploy the application through ClickOnce (instead of a Windows Installer package) hence we cannot merge installation files. I suppose that it should work even if I install the driver at a later stage with respect to the software installation providing that the hardware is not plugged in before.
     But in case the user plug it in before and Windows recognizes it wrongly, how can I later on programmaticaly force Windows to uset the right driver?