Latest posts of: hot

Show Posts
Pages: [1]

on: July 16, 2011, 12:52:02 PM

There is a problem with multiple API for one pool. First API is counted twice:

on: July 13, 2011, 12:40:18 PM

The site is down or is it me?

on: July 13, 2011, 10:32:52 AM

Quote from: [Tycho] on July 13, 2011, 08:12:23 AM Quote from: error on July 13, 2011, 07:53:51 AM Quote from: dsky on July 13, 2011, 06:37:10 AM I get Error 80190191 on all cpu miners, too. Last night that worked fine - today all pcs get this error 80190191 means wrong username or password. It doesn't say whether the miner has it wrong or if Deepbit has it wrong. Check both of them The problem is in the communications library used by ufasoft. Instead of sending your login and password it tries to connect without authorization and provides credentials only after receiving error message/request from the pool. There was a workaround for this, but we had to disable it today. Currently Ufasoft Miner is disabled on deepbit.net, can you fix it?

on: July 13, 2011, 08:20:28 AM

Quote from: [Tycho] on July 13, 2011, 08:12:23 AM Quote from: error on July 13, 2011, 07:53:51 AM Quote from: dsky on July 13, 2011, 06:37:10 AM I get Error 80190191 on all cpu miners, too. Last night that worked fine - today all pcs get this error 80190191 means wrong username or password. It doesn't say whether the miner has it wrong or if Deepbit has it wrong. Check both of them The problem is in the communications library used by ufasoft. Instead of sending your login and password it tries to connect without authorization and provides credentials only after receiving error message/request from the pool. There was a workaround for this, but we had to disable it today. Is the ufasoft miner disabled forever?

on: July 11, 2011, 01:16:29 PM

OK it's working again

on: July 11, 2011, 01:13:29 PM

Poll is down for me but the site seems to work...

on: July 09, 2011, 08:31:13 PM

Quote from: rearwheels on July 09, 2011, 12:23:13 PM Quote from: hot_fever on July 09, 2011, 09:30:03 AM There is a small bug in "Your Total Hashrate", it's related with Slush poll JSON API. When worker hash rate exceed over 1000MH/s it isn't count to "Your Total Hashrate". Worker hash rate look like this: 1,000.00MH/s, so I think that the reason of this bug is coma after thousand. You are right, the coma after the thousand caused the problem, and I'm the one who put that in to pretty up the numbers. I put in the "pretty up" code too early and screwed up the addition.... Fixed. Please try and let me know. I did not manage to test this as I don't have a 1ghs system to test this. Thanks for catching this. ps...I was running high fever on and off for the past 2 weeks. It's OK now Thank you for fast reaction and great site.

on: July 09, 2011, 09:30:03 AM

There is a small bug in "Your Total Hashrate", it's related with Slush poll JSON API. When worker hash rate exceed over 1000MH/s it isn't count to "Your Total Hashrate". Worker hash rate look like this: 1,000.00MH/s, so I think that the reason of this bug is coma after thousand.

on: July 08, 2011, 10:19:57 AM

Hello I would like to contact with user rearwheels because I spot a little bug in www.btc-poolwatch.com Please whitelist me or send him this message: Quote There is a small bug in "Your Total Hashrate", it's related with Slush poll JSON API. When worker hash rate exceed over 1000MH/s it isn't count to "Your Total Hashrate". Worker hash rate look like this: 1,000.00MH/s, so I think that the reason of this bug is coma after thousand.

Pages: [1]