That guy is 10 and should not be installing software on his father's computer without permission - I'm not sure you can say that he is a good example

But, there is an exe installer further up in the post created by theGECK. I will try the SFX mode today too suggested by dishwara.

Sure, this is doable.

Sorry, this is a bug that snuck in. There'll be a new version this weekend with it fixed.

The GUI itself has no performance hit, it's just that poclbm is running code meant for a GPU on a CPU.

I didn't take the effort to incorporate ufasoft's miner or other optimized CPU miner into the GUI since I don't think CPU mining has a future, but if this is something you really want, I invite you to either implement it yourself (I accept patches) or offer a bounty for it.

Hi, I haven't seen this happen. I'll check around for anything that could have caused it. It's probably not from overclocking - you should get an error about verification failed if your GPU is sending out bad shares.

Sorry about that, I meant to keep compatibility with old settings but I guess I didn't totally succeed. You can find the settings file on Windows at:

C:\Users\<your username>\AppData\Roaming\poclbm

If you like I could have a look at your file and see what broke, but just deleting it and then entering the info again should work.
 

Not sure, I haven't experienced this. It would be nothing to do with the GUI portion in any event, so it's not really my area

Hey everyone, a new version of the GUI is available:

    poclbm-gui-20110313.7z

Changes since the previous version:

- Updated to latest poclbm code supporting long polling.
- Builtin support for several popular pools; currently slush, deepbit, BitPenny, and bitcoinpool. You can pick the pool name from a dropdown and it will automatically use the right host and port; it also provides a link to the pool website. List of servers is stored in servers.ini and is customizable.

- In summary panel, click on the miner name to go to that tab.

- Don't display stale shares in the status if there are no stale shares.

- The default miner, username, and password is configurable from an INI file (defaults.ini). This allows pool owners to create custom miner packages that include your login credentials already.

- Support for custom interfaces for each pool. Currently for BitPenny there is no registration required and so the Username/Password field becomes a single field for the receiving address. In the future, look for more custom features on different pools.

- Fix bug where if you had a single miner open and opened the summary panel, the miner would disappear. Thanks to OneFixt for reporting this.

Great to see long polling arrive! I will update my GUI this weekend with support for it.

Sure, I'll include that in the next version.

Glad you're enjoying it The dropbox of common flags is a good idea; I listed the Radeon one in the tooltip because I felt that was the most common case. I found -f1 was hardly even worth using (gives me 184MHash instead of 182MHash) but it could be included.


Unfortunately, the -4way flag isn't supported right now, because the miner the GUI uses is poclbm which is purely an OpenCL miner. When you are CPU mining on it, it is actually running OpenCL code on your CPU which is the reason it's not as efficient as code specifically written for CPU. If you ask me it's pretty cool that it works at all

It would be significant work to add a second miner to the GUI that supports 4way - not only do I have to integrate it into the code, I have to keep it updated, test it, and include it in the package. Which is not to say I won't do it - only that as the difficulty increases I question whether CPU mining will be a viable option in the future. Certainly writing lots of code to benefit the poorest miners is a questionable method of getting donations

From the generation calculator here, you may as well not bother with just an i7. At 2 MHash:

Average   1301 days, 1 hour, 23 minutes

Ah, that makes sense. The GPU miner needs a percent or two of CPU in order to prepare work and send it to the GPU, and if a CPU miner is hogging all the resources then it won't be able to keep the GPU busy.

That's odd... you're using the same flags in both cases? If so, can you try running the poclbm.exe that comes with the GUI and see if that does the same thing? I don't have an Nvidia card to test on but I haven't heard of anyone else with your problem.

Hey everyone, a new version of the GUI is available:

    poclbm-gui-20110306.7z

Changes since the previous version:

- New summary tab lists information about all your miners on one page as well as total hash rate.
- Miners can be started automatically when the GUI starts; this option can be checked/unchecked from the summary page.
- Smaller download (removed useless Tk files).
- Miner tabs show on the status bar the last time a share was accepted.
- Update poclbm to m0mchil's latest version 201103.beta.

Someone had asked about an option to start the GUI when Windows starts; this can be done easily from within Windows by making a shortcut to guiminer.exe in the "Startup" folder of the Start Menu.

Enjoy!

Thanks, that's a good idea and the page doesn't look bad to scrape.

Is there any way to export my transaction history to a spreadsheet? CSV format would be fine, basically what I want to do is export the table seen in the bitcoin client that lists each transaction time, receiving address, and amount. Then I can tally up the coins received at each address over time.

I wasn't able to find anything on the forums to do this, but maybe my search-fu is just weak. Any pointers would be appreciated!

Glad you liked it and I appreciate the feedback. Some thoughts:


Sure, this is a good idea. I will make this a toggleable feature (like the console) since I suspect that the average user only has one or two miners going. Maybe this information should also be available in the tray icon, I don't know.


The problem with switching based on stale is that currently deepbit doesn't report when a stale share is submitted. So even though slush might report 1% of stale, it's possible that deepbit has a much higher stale percentage. If deepbit starts to report stale shares, I'll revisit this.

I also know that some people are working on "push" mining where you don't have to poll the server so much. I wonder if that will make stale shares a non-issue; maybe someone more knowledgable can comment on that.


What I do is run two tabs at once (slush and deepbit right now) on a single device. Then if either server is down for any amount of time, the other one will still be able to use the full GPU.

The only issue with this method is there's no way to control the priority of each miner - each gets a random amount of time. I would like to look into this in the future but right now I have no idea how OpenCL tasks are scheduled on the GPU.

My hope is that as pools grow more sophisticated, server down time will be reduced enough that we won't have to worry about it.


Great, any amount makes me feel appreciated I'm hoping to release a new version in the next couple days, so stay tuned.

I haven't tried it with stream sdk 2.1. Maybe m0mchil can confirm this, but perhaps stream sdk 2.2 or higher is required?

I don't have a 5970, but my understanding is the 5970 is just two 5870s together on one card with an internal crossfire bridge and a slight downclocking. So I think Cypress x2 is the correct report.