Thank you, mdude77! That is exactly what I was hoping to find. Yes, Windows for me most of the time these days.
Edit: I just noticed that my problem arose because I was thrashing around at
http://p2pool.org/ rather than
http://p2pool.in/ - each is useful in its own way.
Any advice you can give as to how we could make p2pool.org experience more helpful for new users would be appreciated
OK. Here's a start, while I still have "beginner's mind".
When I found out the Guild might be closing, I started to Google search for peer to pool alternatives - something that had been in the back of my mind for a long time. I was surprised to find few hits for the search phrases I tried - stuff like "p2pool antminer" and "p2pool tutorial" although perhaps not exactly these phrases (I forget). In general, I found a lot of single-issue hits but only one Big Picture hit, namely p2pool.org which looked like the centre of the p2pool universe to my rookie eye. I spent a lot of (useful) time there without noticing that it had an important link to p2pool.in
Eventually I got to p2pool.in and it seemed to have exactly the step-by-step instructions I wanted. So far I have not got them working but chances are I've overlooked or misread something. Anyway, still with "beginner's mind", looking at the instructions on p2pool.in
First I see a header for Download P2pool binary (Windows in my case). Great - this is going to be easy. Download went fine.
Then I see a header Getting Started (odd - I wonder why the download came first - still looks easy though).
Set up Bitcoin-QT. No problem. I already have it. Oh - it needs a conf file - I can do that. What's in it? RPC name and pw - I can do that (but a total rookie would be baffled, I think). Hmmn - it gives a specific name and pw. Must I use those exact ones? Nah - can't be - must be just an example. Where is the same pw to be used by the miner? skim, skim, can't find it. That's odd. When will this pw actually get used? Keep reading.
Click on Example for Windows. It's well done, but it's stuff I already know - finding the elusive conf file and the old dotconfdottxt issue.
Now what? Run run_p2pool.exe downloaded earlier. I can do that. I'll run it as administrator, just in case. Hmmn - small window pops up and closes before I have a chance to see what was in it. Looks like it might have been a command prompt console thing. Not what I was expecting. Frantic quick reading - no clues found. Quick look at Task Manager - no obvious new process running. Taking a guess - I'll set up a batch file and run it there to see if I can get it to stay on the screen. Nope, still disappears quickly. Time to RTFM - found a readme file in the download. Yikes - it is very Python-intensive - but, but - I thought the compiled version would avoid all that stuff.
Time to step back and think about it a bit.
That's it for now - I hope this is useful.
Edit: Update. Thought about things a bit, found an old one-page tutorial here:
https://bitcointalksearch.org/topic/p2pool-beginners-guide-64329From it I cribbed the idea of putting a pause in my batch file so I could see what was happening before the window closed. Added timeout /T 300 to the batch file. Bingo. Lots of useful detail had scrolled away before, including an error message - looks like I put my new conf file in the wrong folder. Doh!
Edit: Update. Moved the conf file and the run_p2pool.exe is running fine now in its batch file command window. I notice it is donating 1% automatically to devs. Hmmn - I thought the tutorial said 0.5%. Oh well, it is settable and I don't yet know what a fair amount would be. I am seeing lots of "lost peer" and "failure" messages. That does not worry me yet, since I have not pointed any miners at it. Might alarm beginners though.
Edit: Update. I set up an Antminer S2 to test things out, following advice under Run Miners at p2pool.in and adapting it to the S2 - which seemed easy but has not worked out yet. In the LuCI interface for my Ant, pool 1 shows
http://127.0.0.1:9332/ with a
BTC addy as username and an arbitrary password. Alas, the Ant shows the pool is "dead" and is mining on one of the centralized failover pools. The run_p2pool.exe continues to run in its command window. It scrolls pretty fast but seems OK, given that I don't really know what "normal" might look like. It shows the pool at 5578TH/s, for instance.
I seem to be stuck now - getting close though. I'll think about it some more.