I installed the Windows binary distribution of CGMiner - 3.3.1, I believe, was the current release at that time. I read the README, and downloaded the Zadig binary linked on page 1, and installed the WinUSB driver for my block erupters, and for my BFL devices. I then (just to be careful) rebooted the PC. All devices appeared to be using the correct WinUSB drivers, so I then started CGMiner. The devices were all recognized, and seemed to function as expected. Over the next few days, however, I found that at least one Block Erupter would stop working after, on average, ~2-3 hours. CGMiner would be constantly printing a communications error with the failed device, and the device itself would have an LED that was fully on constantly. Manually unplugging and re-plugging the device would fix the problem, and CGMiner would autodetect the newly-reinserted device.
So what did I do wrong? I did not try CGMiner under Linux, but whether or not that works would not change the fact that there was a problem with the Win 7 configuration, and that is the problem I reported.
Can someone just go delete every post related to this moron in this thread ...
I answered it with my very first post.
https://bitcointalksearch.org/topic/m.2960179
Quote from: xyzzy099 on August 18, 2013, 10:23:09 PM
Wrong version? Wrong libusb.dll? You built it yourself and didn't follow the libusb instructions?
... and cgminer will be rock solid on linux also if you do it as per instructions.
You were running an old version of cgminer for fucked if I know what reason.
So indeed you are a complete fucking waste of time here
3.3.2 came out on the 9th of August that used a replacement fixed libusb ...
Actually I was mistaken when I said 3.3.1 was current at that time. I just checked and verified that I had 3.3.2 installed on the Windows machine, if you really even care about this issue. Actually, it looks like the last version I installed - which would be the one I was using when I initially posted - was 3.3.4.