Hi all,

My Win10 updated overnight and now I get an error when I try to run cgminer: "Unsupported 16 bit application". I know nearly everyone is using linux, but it's not an option for me. Is anyone else getting this error?

Thanks,

Tony

Hi all,

I have a pair of GeckoScience Compac-2 stickiminers running on a windows 10 machine. I don't have any linux machines at home so this is what I'm stuck with. I went away on a business trip and the windows machine rebooted and my batch file doesn't restart so I had to do it manually and when I did that, I got nothing but usb write errors. I found a newer version of the code online (thank you), I'm now running 4.11.1 which tries to recover from the usb write errors and it seems to be dealing with the chips a little bit. But one has been placed in OFF mode and the other is getting write errors about 75% of the time. I searched the thread for 'usb write error' and the only hit I got was for the announcement of version 4.10.1 release indicating it would try to autorecover from this error.
Can someone offer me a suggestion or two on how to deal with this? Are the chips dead? I've been running at 156.25 MHz with no HW errors for about a year on each with fan cooling.

Thanks,

Tony

Hi again,

Thanks Dr. Haribo for clearing up my understanding of how the fees work, it makes a lot more sense to me now. To further display my ignorance, how will it work for fees when we reach the end state of all the coins being found? I assume the idea would be for bitcoin to remain a viable currency at that point? At least that's what the founder must have had in mind. Given that, was the idea that everyone would just provide hashpower for free in order to participate in the community of bitcoin when there were no more coins to be mined? Sorry if that's a stupid question.

Hi Rifleman,

I got myself confused between 'pays TxFees' and the idea that we were somehow going to get income from hashing transactions that occur on the network and we could collect income just from processing the normal transactional behavior of the network. Someone collects all those little .00002 bitcoin fees from each transaction on the web and I was thinking that these coins would go to the people doing the hashing. So even though we weren't finding a block, we would be doing useful work for the network and there would be the possibility of deriving some income from it. I thought that was what the 'pays TxFees' meant in the description of the pool. I can see now that I was mistaken and did not understand things properly. I'm fully cognizant that other pools only pay when the blocks get found. I just thought we were special in some way in that we shared in this other kind of income as well, it was a misunderstanding of how things work.

Thanks Biffa, I didn't know that. I thought that some fraction of our hashes were actually being used for generate transaction fees on the network and we would be getting those paid to the pool. I was unaware that we only earned transaction fees upon the creation of a block. Thanks again.

Hi again,

I'm happy with the payout system for blocks, I've been happy with it forever. Just cause it says newbie here doesn't mean I'm a newbie to mining or to the pool. I was just thinking about the income from the transaction fees could be distributed a little more frequently than once every block is found now that that blocks will start coming more slowly. That was my comment. I don't know if that is any interesting amount of bitcoin or not. I would say to use the say last 10 shifts format for this kind of payout scheme as well. I don't know, maybe I'm advocating uncoupling the payout of the transaction fees and the blocks from each other. Both should still be PPLNS though.

I don't know if this has been brought up before or not, but these long gaps between blocks are likely to get more frequent i would think unless the pool grows rapidly enough to keep up with the increasing difficulty. Given that possibility, would it be possible to look at paying out the fees every ten shifts or so? That way we get a little bit back every now and then no matter what.  I honestly have no clue what that would amount to.