Quote from: noncecents on September 06, 2013, 08:04:27 PM

Quote from: Zanatos666 on September 06, 2013, 07:54:48 PM

Quote from: noncecents on September 06, 2013, 07:49:20 PM

Quote from: Zanatos666 on September 06, 2013, 07:31:57 PM

Quote from: noncecents on September 06, 2013, 07:26:32 PM

I tried it both ways. It doesn't make a difference. QED.

You said in you OP that it says you do not have privileges to run this. Have you tried right clicking and running the shortcut as an administrator?

The problem isn't user privileges.

bfgminer was originally written for posix-compliant operating systems that consider all devices to be files where you can set access to them by user permissions.

Windows doesn't have the capability to limit access to USB devices by user privileges.

User privileges are only available at the filesystem level, and since Windows doesn't consider non-storage devices to be filesystem components it's not possible to restrict permission to them.

This is not the same as the privileges required to install drivers for a device. You must have administrative privileges to install a device driver. Windows assumes that if you have administrative privileges to install the driver you should be allowed to access the device even without elevated privileges.

Because of this the application doesn't know the difference between being blocked from accessing the device by the OS because of user privileges and the device not responding due to any of the issues I listed in my original post.

It only checks if the hardware is responding. If it doesn't accept commands the application assumes it's because of privileges and displays the reported error.

That said, the most likely cause of this error is that the device was detected by Windows when it was plugged in because your hub provides enough power for the USB interface, but the device can't be accessed because the hub cannot provide enough consistent power to operate the FPGA.

I was able to determine this was a problem by testing with both USB2.0 powered hubs and USB3.0 powered hubs.

Try replacing your hub with a USB3.0 hub. The worst case scenario is that you send the hub back to Amazon with free shipping because it didn't fix the problem. On the other hand, if it does fix your problem you've only lost the cost or opportunity.

Good info to know. So it seems like his solution is to back out the amount of BE's he has plugged into the hub as they are exceeding its power.

I don't recall saying that.

What I said was:

Try replacing your hub with a USB3.0 hub. The worst case scenario is that you send the hub back to Amazon with free shipping because it didn't fix the problem. On the other hand, if it does fix your problem you've only lost the cost or opportunity.

Even with one Block Erupter plugged in it's possible that if the hub can't provide adequate and consistent power for the device, even if the device were to operate, you might encounter lots of hardware errors that would significantly reduce your efficiency.

Block Erupters are already very low return mining devices. Even under ideal operating conditions I have seen that they return about 1.4% errors. Reducing the efficiency even further would just be shooting yourself in the proverbial foot.

Okay, well I was implying that he could try that, instead of sending his hub back, even if its down to only one. If it is a power per port issue, then the easiest way he can find out if he has everything configured to work is if he can get at least 1 up and mining. If he cannot, then all he would be doing by sending back his hub is wasting his time and becoming more frustrated.

Here is a good source for tested hubs and how many BE's they can run

https://bitcointalk.org/index.php?topic=253749.0