GPUminer now with added files for less technical users.

[Akarbb]

I'm uploading a .zip that I made by using the poclbm GPU miner.  It includes the standard file, with all rights and credit to that files creator whose name escapes me right now.  But I included a preconfigured bitcoin.conf file as well as batch files to start the bitcoin client in server mode and to start the poclbm client for solo mining.  I added a readme file explaining how to do everything!

Feedback is appreciated

http://rapidshare.com/files/454552832/poclbmsolo.zip

[1714956889]

1714956889

[LMGTFY]

I'm uploading a .zip that I made by using the poclbm GPU miner.  It includes the standard file, with all rights and credit to that files creator whose name escapes me right now.  But I included a preconfigured bitcoin.conf file as well as batch files to start the bitcoin client in server mode and to start the poclbm client for solo mining.  I added a readme file explaining how to do everything!

Feedback is appreciated

http://rapidshare.com/files/454552832/poclbmsolo.zip

I'd suggest moving the "change your default username and password" sentence from the end to just after you discuss dragging and dropping bitcoin.conf - too easy for a lazy user to miss it, otherwise... :-)

What would be really cool would be a bit of auto-magic config so that a user can run a script, enter their username and password, and bitcoin.conf etc gets updated with the username/password they entered.

Beyond that, I'm not on Windows so can't really test further but it looks sound and anything to make life easier has to be good.

[Akarbb]

I will most likely change that.  By default though, if the file paths are correct, the batch files will work without any changes after they drag and drop the .conf file.  As for an autoscript, I'll look into it, I have a few programming buddies that might be willing to help.

[LMGTFY]

I will most likely change that.  By default though, if the file paths are correct, the batch files will work without any changes after they drag and drop the .conf file.  As for an autoscript, I'll look into it, I have a few programming buddies that might be willing to help.

I assumed things would work, but I also think it's essential that default passwords get changed - otherwise it's too easy to harvest IP addresses and then try connecting with YOURUSERNAME and YOURPASSWORD. Easy to use is good, but easy to crack isn't :-)

[grue]

I will most likely change that.  By default though, if the file paths are correct, the batch files will work without any changes after they drag and drop the .conf file.  As for an autoscript, I'll look into it, I have a few programming buddies that might be willing to help.

I assumed things would work, but I also think it's essential that default passwords get changed - otherwise it's too easy to harvest IP addresses and then try connecting with YOURUSERNAME and YOURPASSWORD. Easy to use is good, but easy to crack isn't :-)

that would require the RPC port to be forwarded, which is rare.

[LMGTFY]

I will most likely change that.  By default though, if the file paths are correct, the batch files will work without any changes after they drag and drop the .conf file.  As for an autoscript, I'll look into it, I have a few programming buddies that might be willing to help.

I assumed things would work, but I also think it's essential that default passwords get changed - otherwise it's too easy to harvest IP addresses and then try connecting with YOURUSERNAME and YOURPASSWORD. Easy to use is good, but easy to crack isn't :-)

that would require the RPC port to be forwarded, which is rare.

Assuming that the client was behind a properly configured router, yes. This isn't going to be an issue for all users, but ideally it wouldn't be an issue for any users.