 |
January 01, 2014, 06:30:33 PM |
|
CGWatcher does not do anything as far as pools go. CGWatcher just makes it easier for you to manage your miner settings. If you want to verify that CGWatcher started cgminer with the correct settings, start the miner with CGWatcher, wait for cgminer to start, then go to the Tests tab in CGWatcher and select "Show settings at last miner start" (or something worded similar to this) from the drop-down list halfway down the window and click Submit. It will show you what config settings you set, and what config settings it actually used... which will almost always be identical, but there are some occasions where it makes small changes (like enabling the miner's API). If the config settings it actually used are incorrect, please let me know.
Also make sure that CGWatcher and cgminer are not inside any of the following folders, because it can cause permission issues when CGWatcher is trying to write to the temporary config file it uses:
C:\Program Files
C:\Program Files (x86)
C:\ProgramData
C:\Windows
C:\Users\<username>\Desktop
But CGWatcher doesn't do anything pool-specific. I've used coinotron as recently as a week ago while using CGWatcher. If the stats on coinotron didn't show a hashrate, I'd guess it was a coinotron issue. CGWatcher reports the hashrate that cgminer tells it. If cgminer is reporting a hashrate and accepted shares, then it's probably an issue with the pool's frontend. Also, as you may already know, pools generally update reported hashrates at intervals like 5 minutes, 10 minutes, etc.
|
