Quote from: mmiaow on November 14, 2013, 05:03:52 AM

Quote from: ryen123 on November 14, 2013, 04:59:16 AM
Did you previously create a protoshares.conf file?

Yes, I also tried the RPC credentials in my conf file, same result.

Inside your .conf file if you have -rpcport inside, delete it. Restart wallet and try the mining client again. Make it something like this.

rpcuser=your_username
rpcpassword=your_password
rpcallowip=127.0.0.1
server=1

Quote from: ryen123 on November 14, 2013, 04:59:16 AM
Did you previously create a protoshares.conf file?

Yes, I also tried the RPC credentials in my conf file, same result.

Quote from: mmiaow on November 14, 2013, 04:55:09 AM

Quote from: ryen123 on November 14, 2013, 04:52:24 AM
Start the miner like this. Change to your own username and password.

ProtoShares-Qt.exe -server -rpcuser=your_own_user -rpcpassword=your_own_password
gw_miner.exe localhost your_own_user your_own_password

I tried that, the wallet is OK as always, and neither the miner have any output nor the %CPU gains.
Looks like the miner failed to connect to the wallet but did not crash.
Also I am using the latest version of wallet.

Did you previously create a protoshares.conf file?

Quote from: ryen123 on November 14, 2013, 04:52:24 AM
Start the miner like this. Change to your own username and password.

ProtoShares-Qt.exe -server -rpcuser=your_own_user -rpcpassword=your_own_password
gw_miner.exe localhost your_own_user your_own_password

I tried that, the wallet is OK as always, and neither the miner have any output nor the %CPU gains.
Looks like the miner failed to connect to the wallet but did not crash.
Also I am using the latest version of wallet.

Quote from: mmiaow on November 14, 2013, 04:45:23 AM

Quote from: bytemaster on November 13, 2013, 08:23:10 PM
Launch your

ProtoSHares-Qt.exe -server -rpcuser=user -rpcpassword=pass
./gw_miner.exe localhost user pass

I launched my wallet with the first line and then the solo miner with the second line.
The wallet started up successfully, but the miner did not output anything, and CPU usage rate kept 0%.
What happened here? Running Windows Server 2008 R2

Start the miner like this. Change to your own username and password.

ProtoShares-Qt.exe -server -rpcuser=your_own_user -rpcpassword=your_own_password
gw_miner.exe localhost your_own_user your_own_password

Quote from: bytemaster on November 13, 2013, 08:23:10 PM
Launch your

ProtoSHares-Qt.exe -server -rpcuser=user -rpcpassword=pass
./gw_miner.exe localhost user pass

I launched my wallet with the first line and then the solo miner with the second line.
The wallet started up successfully, but the miner did not output anything, and CPU usage rate kept 0%.
What happened here? Running Windows Server 2008 R2

i7-4770 (4GB,1 Chip) - 121 hpm (cpm??)
i7-3770 (8GB,2 Chip) - 132 hpm
Core 2 Duo - T6600 - 21 hpm

Interesting that the i7-3770 should outperform the i7-4770, I put this down to its memory being spread out over 2 chips.

Older machines achieve a much lower cpm obviously, but I think at reasonable power usage levels - so hoping we'll see large pools of old computers from individual miners, rather than capital intensive commercial mining.
 

It looked like I was able to mine to the same computer over IP, but even though it was reporting a hashrate it was using 0% of the cpu, so I switched to each computer mining to their own wallet.

I'm seeing something worrisome, though.  A bunch of miners will simultaneously show that they calculated the exact same hash!  I imagine this implies there is a ton of duplicated effort.  I've seen this quite a few times.  Is there a way to get them to work on different problems?  If I connect them to the same wallet through IP, would that fix it?

Quote from: spoonman on November 14, 2013, 01:17:47 AM
With this are we able to point more then one computer at our qt wallet?

Yes

With this are we able to point more then one computer at our qt wallet?

Quote from: bytemaster on November 13, 2013, 09:35:25 PM

Quote from: crendore on November 13, 2013, 09:21:26 PM
Hey bytemaster, i'm sorry, it does run really fast! I thought i had enabled release mode by setenv, but apparently that didn't work.

I'm getting 113 HPM now on an i7 2600k OC'd to 4.5GHZ.

Great!  So how close am I to ypool?

I can't actually run ypool's miner on OSX, i haven't figured out how to do that yet, is it even possible?

Got it installed on Arch. Benchmark runs fine... 140-150HPM 136.363 seconds on i5 3570K at 4.2GHz.

When I try to run with

Quote./gw_miner localhost USER PASS

it just says:

Quote./gw_miner: /usr/lib/libcrypto.so.1.0.0: no version information available (required by ./gw_miner)

and runs at 100% on 1 core.

Am I doing something wrong?

Sorry to say, that I think Ypool still has the edge.

My i7 2600k is benching at 79 while ypool is hovering around 85.

Yes... that is normal.  I submit hashes below a certain threshold automatically... when it finds a block it will say accepted 1.

When I run it without arguments, it benchmarks.  But when I try to connect to localhost, it reports this:

Quote./gw_miner localhost x y
/root/coyote_miner/bitcoin.cpp(88): Throw in function boost::property_tree::ptree bitcoin::detail::client::request(const string&)
Dynamic exception type: boost::exception_detail::clone_impl<bitcoin::exception>
std::exception::what: bitcoin::exception
[bitcoin::bitcoin_msg_*] = Response returned with status code 500

I installed boost 1.53 development and debug so that should include all the boost libraries.  Any ideas?

EDIT: stopping and starting bitcoind a few times and trying again resolves the issue.

Also, occasionally it will display hashes, but still say "ACCEPTED: 0."  Is this normal?