|
3
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - updated Nov 18 with latest poclbm & Stratum
|
on: November 20, 2012, 12:00:51 PM
|
|
It's a pretty vague error... looking at the changes I made I can't figure out what could cause that. You say it worked on the last guiminer? One thing you could try is deleting your miners and creating new miners just to see if that does anything.
Another thing you could try is to run poclbm from the command line and see if that works correctly, in case there was an issue with the latest poclbm. If you look in the console when you start tup you can see the command to use, something like:
poclbm.exe kiv:pass@localhost:8332 --device=1 --platform=0 --verbose -r1
|
|
|
|
|
4
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - updated Nov 18 with latest poclbm & Stratum
|
on: November 19, 2012, 12:15:41 PM
|
Hi subSTRATA, thanks for reporting the issue. I added a "Set Bitcoin data directory" option to the solo utilities, and as well it accepts any .EXE file for the bitcoin executable. To use it, set the bitcoin executable and data directory correctly before launching the bitcoin-qt.exe. Your bitcoin.conf needs to be set up properly in the other data directory as well, the "create solo password" option only knows how to write to the default data directory. Let me know if you experience any problems, but it seemed to work on my machine. Hey everyone, a new version of the miner is available from the download link on the first post or here: guiminer-20121118.exe (self-extracting archive) The main point of this update is to get the latest poclbm version including Stratum support. Welcome back! Have you looked at or eventualy fixed this issues? |
|
|
|
|
5
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - updated Nov 18 with latest poclbm & Stratum
|
on: November 19, 2012, 02:23:39 AM
|
Hey everyone, a new version of the miner is available from the download link on the first post or here: guiminer-20121118.exe (self-extracting archive) The main point of this update is to get the latest poclbm version including Stratum support. I removed support for the old Phoenix since I didn't have time to get GUIMiner working with the latest Phoenix 2; so if you're happily mining on old Phoenix then you don't need this release  As always donations are appreciated; my address remains the same at 1MDDh2h4cAZDafgc94mr9q95dhRYcJbNQo. While I still love Bitcoin I'm not mining any more myself and am really busy in my personal life, so this release is purely for the benefit of you guys, the community. If anyone has issues please report them in this thread or PM and I'll try to help out. Cheers! |
|
|
|
|
9
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - updated Aug 24 with new miner versions
|
on: September 06, 2011, 10:57:21 AM
|
Thanks to everyone reporting on the miner invisible. It looks like if you save while the miner is invisible, it will stay offscreen when you open the program again. Because the miner settings are stored in a separate folder (AppData), re-installing won't clear the settings and the problem persists. I'll find a permanent fix to this for the next version, in the meantime big thanks to celcoid for the workaround |
|
|
|
|
10
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - updated Aug 24 with new miner versions
|
on: August 27, 2011, 10:59:33 PM
|
In previous versions you would use the --backup flag. In the current version they changed it so you don't need to specify a flag, just put the info in the box. You can use multiple backups just by separating them with spaces. How to use a backup pool aka fallback support:
Fallback support is in the OpenCL miner only. In the flags, specify the info of the backup pool or pools. For example if I want to fallback to my account on slush's pool, I would write:
Kiv.GPU:mypass@api.bitcoin.cz:8332
When you do this do you pass a flag? In other posts it looks like --backup= is used. Do we to specify that in the flags? as in --backup=Kiv.GPU:mypass@api.bitcoin.cz:8332 |
|
|
|
|
13
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - updated Aug 23 with new miner versions
|
on: August 24, 2011, 07:49:33 PM
|
|
Thanks for the issue reports guys, I'll look into it and do another release today or tomorrow. Guess I didn't test thoroughly enough... maybe I should have dedicated beta testers or something.
Known issues so far are:
- slush pool refresh balance missing
- shares accepted staying at 0
- "AttributeError: 'HttpTransport' object has no attribute 'failure'"
|
|
|
|
|
14
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - Phoenix 1.5 and new, faster poclbm
|
on: August 23, 2011, 06:49:10 PM
|
A new version of the miner is available; I've updated the download link on the first post, or you can get it here: guiminer-20110823.exe (self-extracting archive)Changes: - Update poclbm (OpenCL miner) to the latest version. This changes the format of a backup pool. In the "extra flags" you just enter your backup (or backups) like this: Kiv.GPU:mypass@api2.bitcoin.cz:8332 - Update Phoenix to the latest version. See their thread for details on changes. - Remove ufasoft miner from the GUIMiner bundle. It's still supported, but you'll have to download it separately. I apologize for the inconvenience to ufasoft miner users, but I decided to do this since only a few percent of users were using ufasoft and due to recurring false positive issues from antivirus programs. - Added "duplicate miner" option when right clicking on a miner tab. This is to make it easier to clone miners to multiple GPUs. - Limited maximum scrollback in the console window to 5000 lines. On machines with low RAM, this will prevent running out of memory after a long period of continuous operation. - Add more pools to the server list, though balance update doesn't work for all of them. I'm looking at ways to handle the large number of pools that are popping up better. - Fix Linux bug where the window could not be restored after minimizing. |
|
|
|
|
16
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - Phoenix 1.5 and new, faster poclbm
|
on: July 06, 2011, 10:39:47 AM
|
Did you install the new GUIMiner in the same place as the old one? "The directory name is invalid" probably means it's looking for phoenix.exe in a folder that doesn't exist. Check the "Ext Path" on the miner and see if it's still correct. If that doesn't work you can also try deleting your Phoenix miner info and creating a new one pointing to the right place. Prevoius guiminer, apart from phoenix connection problems, ran fine for me. I downloaded the newest one today (and deleted all files from previous versions), and when I wanted to run it I got the message 'Errors occured: see the logfiel xxx for details' This is the log file, anyone know what's wrong? File "subprocess.pyo", line 621, in __init__
File "subprocess.pyo", line 830, in _execute_child
WindowsError: [Error 267] The directory name is invalid
Traceback (most recent call last):
File "guiminer.py", line 2221, in <module>
File "guiminer.py", line 2212, in run
File "guiminer.py", line 1696, in __init__
File "guiminer.py", line 1915, in load_config
File "guiminer.py", line 938, in start_mining
File "subprocess.pyo", line 621, in __init__
File "subprocess.pyo", line 830, in _execute_child
WindowsError: [Error 267] The directory name is invalid
ERROR:root:Exception:
Traceback (most recent call last):
File "guiminer.py", line 2212, in run
File "guiminer.py", line 1696, in __init__
File "guiminer.py", line 1915, in load_config
File "guiminer.py", line 938, in start_mining
File "subprocess.pyo", line 621, in __init__
File "subprocess.pyo", line 830, in _execute_child
WindowsError: [Error 267] The directory name is invalid
Traceback (most recent call last):
File "guiminer.py", line 2221, in <module>
File "guiminer.py", line 2212, in run
File "guiminer.py", line 1696, in __init__
File "guiminer.py", line 1915, in load_config
File "guiminer.py", line 938, in start_mining
File "subprocess.pyo", line 621, in __init__
File "subprocess.pyo", line 830, in _execute_child
WindowsError: [Error 267] The directory name is invalid
ERROR:root:Exception:
Traceback (most recent call last):
File "guiminer.py", line 2212, in run
File "guiminer.py", line 1696, in __init__
File "guiminer.py", line 1915, in load_config
File "guiminer.py", line 938, in start_mining
File "subprocess.pyo", line 621, in __init__
File "subprocess.pyo", line 830, in _execute_child
WindowsError: [Error 267] The directory name is invalid
Traceback (most recent call last):
File "guiminer.py", line 2221, in <module>
File "guiminer.py", line 2212, in run
File "guiminer.py", line 1696, in __init__
File "guiminer.py", line 1915, in load_config
File "guiminer.py", line 938, in start_mining
File "subprocess.pyo", line 621, in __init__
File "subprocess.pyo", line 830, in _execute_child
WindowsError: [Error 267] The directory name is invalid EDIT: just tried back the previous version.... and it doesnt work either! I'm running a HD 5850 and HD 6850 atm, going back to stock settings doesn't help. OS: Win 7 Pro 64-bit SP1 mobo: Asus P5Q-E EDIT_2: all right, managed to run it if I don't click 'ok' on the error message, and after I switch from Phoenix to poclbm Anyone can help? I'd really like to be able to run phoenix againa, because poclbm is too heavy for my CPU ( Q9300@3.25) - 25% load. |
|
|
|
|
17
|
Bitcoin / Mining software (miners) / Re: SCAM: CoinMiner at bitcoin-miner-pro.com steals wallet
|
on: July 04, 2011, 12:36:07 AM
|
Site's down now.
Sometimes when visiting it I get an error, other times it goes through. Looks like the server reliability is not great. I'm still able to access the site now. well, I hope you consider changing the license of GUIminer to something that makes it stay free software, but prohibits malicious redistribution of that code.
At least you could then file a lawsuit against them, for copyright issues.
The license is GNU GPL and I believe they are already in violation of it (though I'm no lawyer), at least by not distributing the source code to their modified version. Also, be sure to get a whois output for their domain and report their doings to the registrar. then do a whois on the ip-address where the site is hosted and write some mail to their hoster.(if domain registrar and hoster are not the same company). These usually react fast to complaints. They react even faster to DMCA complaints(in case you really change your license)
I tried a whois and apparently they're with ezinom.com. I guess that's who I can write mail to? |
|
|
|
|
18
|
Bitcoin / Mining software (miners) / SCAM: CoinMiner at bitcoin-miner-pro.com steals wallet
|
on: July 03, 2011, 11:53:42 PM
|
It's come to my attention that a miner called CoinMiner is being distributed at bitcoin-miner-pro.com. This is nothing more than my own GUIMiner with a wallet stealing trojan attached. DO NOT DOWNLOAD this miner unless you want to lose all your coins and maybe worse. It will not increase your mining speed or do anything else magical except send your wallet to some scammers. I'm very upset that my free software is being used in this way and have contacted the site owners, but I don't expect that they will be very cooperative. I just wanted to warn people not to use it, and if anyone wants to DDOS their site that would be cool. (Joking) |
|
|
|
|
20
|
Other / CPU/GPU Bitcoin mining hardware / Re: GUI mining - updated host address for slush's pool
|
on: July 02, 2011, 03:12:18 AM
|
I'm not sure I follow what you're trying to do. I'll try to paraphrase: Your primary pool is an "other" pool with some port specified in the Port text box (let's say 8333). Your backup pool has a different port than 8333, let's say 8332. For me, I am able to put it in the extra flags like this and have it work: --backup=Kiv.GPU:mypass@api.bitcoin.cz:8332 The port for the backup pool is supplied by me after the colon, while the port for the primary will come from the Port text box. Let me know if this helps at all, maybe I misunderstand or you're having a different issue I seem to fail at using a pool with different port as backup for an "other" pool. It appends the port specified in the field, and leaving that blank makes poclbm refuse to start so it doesn't help adding the port for the main pool in the address field.
|
|
|
|
|
Show Posts
