Title: Help connecting to pool and using gui miner problem Post by: mrpsychotic on June 16, 2011, 09:28:41 PM I have recently downloaded bitcoin and i want to run it with a pool (btc guild) but i am having troubles. I believe these troubles stem from the prrogram I am using to try and connect to the pool which is guiminer.
When I open it up, the first thing I see is the default screen where I type all of the fields and get this message: 2011-06-16 14:15:30: Listener for "Default": 16/06/2011 14:15:30, Problems communicating with bitcoin RPC. One interesting thing that I tried was creating a miner instead of using the default, in which case I get this message: 2011-06-16 14:17:46: Running command: C:\Users\Sean\Downloads\guiminer\miners\puddinpop\rpcminer-cuda.exe -user=##### -password=##### -url=http://btcguild.com:8332 2011-06-16 14:17:46: Listener for "mrpsychotic_1" started 2011-06-16 14:17:46: Listener for "mrpsychotic_1": Client will start 1 miner threads 2011-06-16 14:17:46: Listener for "mrpsychotic_1": Work will be refreshed every 4000 ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": 1 CUDA GPU devices found 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Setting CUDA device to first device found 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Loading module bitcoinminercuda_20.cubin 2011-06-16 14:17:56: Listener for "mrpsychotic_1": CUDA initialized 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (16,16) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (16,16) 1149ms prev best=9223372036854775807ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (16,32) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (16,32) 400ms prev best=1149ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (16,64) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (16,64) 345ms prev best=400ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (16,128) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (16,128) 290ms prev best=345ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (16,256) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (16,256) 269ms prev best=290ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (32,16) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (32,16) 1059ms prev best=269ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (32,32) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (32,32) 366ms prev best=269ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (32,64) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (32,64) 322ms prev best=269ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (32,128) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (32,128) 273ms prev best=269ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (32,256) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (32,256) 260ms prev best=269ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (64,16) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (64,16) 1009ms prev best=260ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (64,32) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (64,32) 337ms prev best=260ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (64,64) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (64,64) 309ms prev best=260ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (64,128) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (64,128) 265ms prev best=260ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (64,256) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (64,256) 256ms prev best=260ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (128,16) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (128,16) 981ms prev best=256ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (128,32) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (128,32) 322ms prev best=256ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (128,64) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (128,64) 302ms prev best=256ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (128,128) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (128,128) 259ms prev best=256ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (128,256) 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Finding best configuration step end (128,256) 254ms prev best=256ms 2011-06-16 14:17:56: Listener for "mrpsychotic_1": Done allocating CUDA resources for (128,256) Where the ##### were filled in with my information. This doesnt appear to have any error message, but when I go back out of the console to the worker screen it says shares: 0 accepted on the bottom left and connecting... on the bottom right without doing anything as far as i can tell. On the btc guild website they say that connecting to them in this way hooks you up with the overcrowded texas server, so I have tried using the "other" option and putting the california server url to try and get around this but it has no effect. On a similar post i saw people recommending someting about running bitcoin.conf or using adding a -server to the end of my bitcoin client target. For the first part, when I try searching bitcoin.conf from the start menu, it says no results were found. Also, when i and the -server thing to the end of my target nothing seems to work in guiminer and and when i try to open the client it directs me to open or change something in the appdata. The problem is I am running windows 7 and unlike my previous computer, I can find no such appdata folder. I am also running bitcoin 3.23 i believe. Title: Re: Help connecting to pool and using gui miner problem Post by: AWOLRanger on June 16, 2011, 09:46:12 PM The appdata folder is hidden in Windows 7, but you can go to C:/users/yourname and then type /appdata in the menu bar and it will go to the folder.
Title: Re: Help connecting to pool and using gui miner problem Post by: InstaGx on June 16, 2011, 09:50:28 PM The appdata folder is hidden in Windows 7, but you can go to C:/users/yourname and then type /appdata in the menu bar and it will go to the folder. Alternatively, navigate to %appdata% from anywhere. Title: Re: Help connecting to pool and using gui miner problem Post by: mrpsychotic on June 16, 2011, 10:35:48 PM OK thanks, what do you recommend i do there?
Title: Re: Help connecting to pool and using gui miner problem Post by: mrpsychotic on June 16, 2011, 10:39:58 PM Unfortunately, when i went to appdata i saw bitcoin in the roaming folder but still no bitcoin.conf
Title: Re: Help connecting to pool and using gui miner problem Post by: mrpsychotic on June 17, 2011, 03:28:37 AM Wtf i cant even click to mine in the main bitcoin client
|