The working Cylib is 2005-10-11(vc6_7) can work in 32bit windows7
Compile the App with latest Cylib, 32bit Application can not control USB device in 64bit windows7(64bit driver).
USB suite 3.4.7:
In 64bit Windows 7, Control center: list the USB device correctly.
But the tool Cydesc both x86 and x64 can not access the USB: device count = 0
Now the 32bit App can works on 64bit Windows7, By using 3.4.7Kit 64bit driver and change Vid&pid, Do not change other file.
I used my driver, only substitute one sys file, the INF in my driver doesn't contain the GUID of cy68013. but App used it
The 64bit doesn't work, but 32bit Cyusb.sys driver(version 184.108.40.206)works. I do not know the detailed difference. Anyway, I will use the new driver.
Control center is coded to get handle to device bound to CyUSB.sys irrespective of GUID. CyConsole looks at the registry to populate the list of GUIDs used with CyUSB.sys and then uses them to get handle to the device.
Have you tried using a GUID in the inf file and then using that in the host application to get the handle?
Thanks for your help.
Because in the SDK 3.4.7, The driver is not signed. I downloaded A WHQL Signed driver, The version is 3.4.5
The GUID in INF file is different from 3.4.7 driver. " AE18AA60..." <--> "AE18A550..."
When the GUID changed to same value as 3.4.7, the Cyconsole can detect the device.
does the Console bounded to the fixed GUID: " AE18AA60..." .
I need the App be compatile with earlier versions.
I will use the default GUID as used before, even it may be not suitable for specified application.
I'm not able to gauge the full picture.
Latest SuiteUSB has CyAPI.lib for x64 as well. If you use a GUID and use that to get handle to your device it should work. The CyConsole issue you're facing is most probably due to lot of GUIDs and different names for CyUSB.sys in the registry of the PC that you're using.