Originally Posted by dougm216
So Cyber how did you fix it? I gave up months ago trying to get this to work, even doing what I think you are suggesting.
In my case, running Win7 x64, ColorHCFR 184.108.40.206 seemed to be conflicting with a version libusb-1.0A.dll & libusb-1.0A_x64.dll files which still existed somewhere on my system but was no longer used by Argyll CMS or otherwise. As mentioned above, the inf installer will claim to install successfully, but not replace these files, causing ColorHCFR 220.127.116.11 to not detect anything is amiss and attempt to use a driver which it's not compilable with. Everything crashes and burns at that point.
How I initially got it working after installing from the HFCR i1pro.inf, was first deleting libusb-1.0A.dll & libusb-1.0A_x64.dll from my System32 & SysWOW64 directories. Then from ..\HCFR Calibration\Drivers\ I copied libusb-1.0A.dll to SysWOW64 & renamed libusb-1.0A_x64.dll to libusb-1.0A.dll and copied it to System32. I then started HFCR 18.104.22.168 and my i1pro was finally detected properly.
At that point I went to device manager, right-clicked on the driver installed by HFCR, and uninstall with delete drivers for this device. To make sure all instances were gone, I search C:\ for libusb-1.0A and deleted any instances in System32, SysWOW64, Windows' driver repository, and so on. I then re-installed the driver inf from ..\HCFR Calibration\Drivers\ and now it installed properly and HCFR 22.214.171.124 was happy. This is optional, but I also changed my device name in the HFCR inf from "Eye-One Pro (Argyll)" to "Eye-One Pro (HFCR)" to make it easier to switch back in forth to the Argyll CMS driver which also used "Eye-One Pro (Argyll)".
That said, I have no idea if your Spyder 2 driver issue is the same I was experiencing with my i1pro.
Ultimately I think the solution here, would be to recompile HCFR with LibUSB 126.96.36.199
and create a new inf files so it can co-exist with Argyll CMS 1.5.x without swapping drivers all the time. Argyll CMS 1.5.x only uses the LibUSB 188.8.131.52 sys driver, but doesn't care if you install the corresponding LibUSB 184.108.40.206 dll files as well, if HCFR still requires the DLL files. Currently LibUSB 220.127.116.11 sys+dll will still cause HCFR to crash and burn, and not detect an incorrect driver. At the very least, you should put in place some additional checks for incorrect LibUSB driver version, catch the exception, and throw an error message to the user. I'd be mildly concerned about HCFR doing damage to the device when there is a driver mismatch, since HCFR actually makes my i1pro produce short "beep" sound internally after this access failure occurs, which can't be good.
[Edit: I'm still seeing high-res luminance readings which are ~4% higher than Argyll CMS high-res. Only ColorHCFR 18.104.22.168 standard-res measured luminance matches Argyll CMS closely.]
[Edit2: HCFR 22.214.171.124 randomly hangs completely in the middle of taking a measurement. Seems to have a higher tendency to occur when taking an extreme number of measurements]