Just chiming in, on windows, you need to create a bitcoin.conf file and define your rpc username and pw in order to be able to launch 'bitcoin.exe -daemon', then you use the username and pw you specify here to call diablo's miner



likely located in C:\Users\[your win username]\AppData\Roaming\Bitcoin\bitcoin.conf in win7

And I cannot recall where that would go in XP off hand, but wherever the rest of the bitcoin stuff is stored


Also, I don't think that java is appended to PATH by default, so you will probably want to add that as well to use 'java' from the command line


win32 patched getwork binaries at:
http://bt.irlbtc.com/view/1334.0 No longer needed

Does this miner have the 100% CPU usage problems that are present when using SDK 2.2 on linux?

With m0's on 2.2, I get around 50% usage for X, 50% usage for python (out of 200%) and the desktop is unusably slow.

For mine, I get around 15% X usage, 75% usage for Java, and the desktop is smooth as silk.

Where can I enter the IP from RPC host?
Thanks

Nice work!

I have a feature request. If m0mchil's miner can't connect to Bitcoin (because it is not running) it will tell you so and wait for it to come up. This miner just closes.

Could you change this? It makes things easier when you want to run it after startup, because Bitcoin takes a while. It's also nice if you have to restart BC, because you want to change some parameter or want to switch to an other version.

Gentoo Linux. There may be some bus/CPU issues here, since my system has an Atom D510, and only 1x PCIe slots.

This is great news. Time for me to dip my toes into OpenCL mining :-)

Hmm, Windows 7 64-Bit, Radeon 4870 here.

m0mchil's poclbm is ~1000khashes/s faster and my desktop stays more reponsive than with yours.
I guess I'll stick to poclbm ;P

I guess -w defines the worksize, but what exactly does -v do ?

After much thought, I'm not sure why you're having this issue, especially if m0's works well. Try running with -f 30; this will lag your desktop, but will reduce the overhead caused by OpenCL itself. You can go down to -f 2 safely if needed, it just slows down X.