Tigggger:  All great ideas. I'm trying to get a minor update out quick, so these ideas won't be included. I don't want to rush them and potentially break something. I'll make sure they're in the next major update.


chickenthr33:  Yeah there were some problems with the text resizing. I already fixed it so it should work in the next update. It is still considered experimental so it does not save font sizes, so they will need reapplied each time CGWatcher is opened for now.


duz: CGWatcher gets stats from the miner, so if you want to zero them you can send the miner the "zero" command (you can do this in the Tests tab). Alternatively, you could restart mining obviously.


MineRock:  I'm not sure what prompt you're referring to. When you modify the active profile while mining and are asked if you want to restart the miner, I got rid of the messagebox that would show the results of whether the miner restarted successfully or not. Instead it shows a notification in the main window, which does not need clicked on. When you modify the config file in use, it asks you if you want to restart to use the new config file because I imagine sometimes the user may want to finish out the current config file then use the new one next time it is restarted. If you can give me more detail on which prompt I'll get it removed or make a setting to remove it.


TheUniporn:  Which cards are you running? And when you say "reopening cgminer", do you mean CGWatcher restarting it? If so, make sure the setting "Kill miner process during restart instead of sending 'quit' command" is enabled (you have to click Save Settings to save anything in the Settings tab.) I don't think it is CGWatcher that is freezing your PC... it is the miner. CGWatcher just launches the miner, and the miner is what sets your GPU clock speeds, fan speeds, voltage, etc. based on your config settings.


MineRock:  Efficiency is defined as number of shares returned/work item. This was dropped from cgminer's UI, which means it probably no longer provides useful information and perhaps was not updated to reflect changes in mining over the past 6 months. This is why I chose this stat to be replaced by a custom stat if you wish.


tangmonkey:  You can create scheduled actions to trigger when a specified program starts or stops running.


If anyone emails me and I don't get back to you within a week, please don't hesitate to email me again. Users for both CGWatcher and CGRemote have grown significantly over the past couple months and it's possible that occasionally something gets lost in the pile (except for donations for CGRemote, which I do stay on top of). Thanks for your patience, and I assure you I am trying my hardest to get every fix and feature made as soon as possible. I may or may not have some exciting news in the next two weeks regarding both of these projects.

Can you please email the file called cgwatcher.log from your cgwatcher folder? Also include a debug report in the email (go to Tests tab, click Create Debug Report button). I'm working on a minor update right now that fixes some things so I'll try to find and fix any scheduler-related problems as well.

Justin

Yeah, I'll be making a lot of things resize with the window in the coming versions. I only recently changed it to allow resizing since some users have Windows set to display text at 125% or 150%, which really messes with everything.



Did you check to see if the startup entry was created (check startup folder or registry)? An easy way to tell is to open Run window and type msconfig and press Enter. When the System Configuration window opens, click on the Startup tab. If the entry is being created successfully, then it may be Kaspersky preventing it from running. I did a lot of testing on a Windows 7 computer using the new startup options, and they should work - especially if you're running CGWatcher as Administrator (although if you're only creating entries for the current user you should have no problems even if not running as Administrator).

I have CGWatcher set to log any time idle begins or ends, so check your log to verify it isn't working. The number of seconds the system is idle is provided by Windows, so there is not too much I can do about it if other applications are causing this number to reset (which seems to happen on my own PC because the log will show the computer going idle, then not idle, then back to idle several times throughout the night (nobody touching the computer).

As far as font size, Windows really makes a mess of things with this and I haven't found a way to override this setting yet. So what I did was created two utilities in the Tests tab - one will decrease all text in the main window by 1 font size, and the other will increase all text in the main window by 1 font size. You can run these as many times as you want, but for 125% you should only need to decrease text size once. This feature is still experimental so if it resolves this issue I will apply it to other windows and save the font size so it is applied automatically when CGWatcher starts (right now you have to run the utility each time you launch CGWatcher). You can find the utility in the Tests tab, about halfway down the window is a drop-down list with various reports and utilities. Select the one that says "decrease text size" and click Submit. Please let me know how this works for you.

You can disable the validation by clicking the checkbox in Config File Editor. The validation tries to make sure you have the same number of settings as you do GPUs, which could be the problem. For a while there was a problem with the device setting in config files, so I ignored it in Config File Editor. I guess I should go back and take it into account now. If you know the setting is correct, just disable the validation and save anyway.



I've just finished in-app bug reporting for CGRemote, so that will probably also be added to the next version of CGWatcher. You just type in a description of the problem and click Submit, and it takes care of collecting data and sending it to me.

You can disable the automatic updating of coin profitability data in the Coin Manager window (go to Settings tab, click 'Other Tools...' button and select Manage Coins from the popup menu). This data is updated in a background thread so it should not cause the main window to stop responding.

Are you using the most recent version (1.3.4.4)? You can create a debug report by going to the Tests tab and clicking the 'Create Debug Report' button. Please email this to me rather than posting here, because it is quite a bit of data. Also, if you can attach the file called cgwatcher.log to the email, that would also be helpful and appreciated.

Do you have the monitor set to restart the miner at a set interval? Or a scheduled action? There is not enough of the log here to see what is going on. After this occurs, go to the Tests tab and click the 'Create Debug Report' button. Email this to me (my email is in the readme). This should help show what is happening if this is unexpected behavior.

On a related note, I've just finished adding in-app bug reporting to CGRemote, so it should probably be in the next CGWatcher update also to make reporting issues easier.



Thanks... always nice to see a post reply that isn't some sort of problem.

mb0erman, please start the miner with CGWatcher to reproduce this problem, wait one minute (make sure miner is started and CGWatcher is done waiting for it to start and is connected to it), then go to the Tests tab and click the 'Create Debug Report' button. Send this report to my email (in the readme).

While you're in the Tests tab, go to the drop-down list next to the 'Create Debug Report' button and select 'Show last miner start configuration' from the list and click the Submit button. This will show you the exact settings CGWatcher used when launching the miner last, and will also show the config file/arguments you set in the profile. If you notice something wrong in the settings CGWatcher used, please let me know. You do not need to send this information as it is already included in the debug report.

Thanks.

Share difficulty allows devices with higher hashrates to get work with a higher difficulty instead of a lot of work with low difficulty. For example, let's say a GPU gets diff1 work (the lowest difficulty). It hashes and gets one diff1 accepted share every minute. Now we buy an ASIC that mines 100x faster than the GPU. Instead of sending the ASIC 100x the work, we can just send it diff100 work that it has to solve to get one diff100 accepted share. This saves a lot of overhead. Pools pay in diff1 equivalent, so 100 diff1 shares should be paid the same as one diff100 share.




I answered this in the post you created. I would suggest trying a different pool because I believe the issue is coinotron.




What are you doing (or what is it doing) when this happens? What do you mean by "getting data"? If after it comes back you can create a debug report and send it to me, I'd really appreciate it. That will hopefully show in the log what happened. You can create a debug report by going to the Tests tab and clicking 'Create Debug Report' button, and my email address is in the readme.




I understand that may be unexpected behavior, but it is doing what it says it will do. If you stop the miner using the Stop or Pause Mining button, this option should not start the miner. It only launches the miner when it closes unexpectedly, or when CGWatcher starts - which is by design and was asked for by users.



I'm working on coin stuff for CGRemote right now, and it will probably all make it's way into CGWatcher as well. It's not as simple as combining the data - I either need to give the user an option to select which provider to use for each field, or create scheduling options for both data providers. I'm going with the first one... I just need time to code it.




If you set a scheduled action to trigger when the most profitable coin changes, it will do just that - with no regard for which coins you're mining. The action is triggered, and if set to switch to the most profitable, for example, it will look at all of your profiles and switch to the most profitable.

If you set a scheduled action to trigger when the most profitable profile changes, it will only be triggered when the most profitable coin that you're mining (and is linked to a profile) changes.

I'm not sure if I answered your question. If not, please try to explain a little more and I'll give it another shot. A list of your profiles and their coins would be helpful.

I recommend using the latest version because it may have fixes and improvements over older versions. But I leave links to older versions on the download page in case a new version introduces a problem, or some people prefer not to change things unless they need to.

Where is your CGWatcher folder located? If you put the CGWatcher folder inside any of the following folders, it may cause permission issues with Windows and you might have to run CGWatcher as Administrator for it to work properly:

C:\Program Files
C:\Program Files (x86)
C:\ProgramData
C:\Windows
C:\Users\<username>\Desktop

If that isn't the problem, in the latest version go to the Settings tab, then click the Storage sub-tab. Make sure CGWatcher is able to write to both of these files (that they are not inside any of the folders listed above).

And as a last resort, try running the latest version as Administrator, which should clarify whether this is a permissions issue or not.

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.

Are you using bfgminer? And are you mining a scrypt coin? If so, bfgminer does not report a valid number for total miner diff1 shares. I'll be changing the way this is reported in the next version.

A diff4 share is equivalent to 4 diff1 shares. Your pool gives you work of a certain difficulty, which you must meet or exceed to have the share accepted. The higher your hashrate, usually the higher difficulty shares you get. But you get paid in diff1 equivalent shares, so a diff4 share should earn the same as four diff1 shares.




I would suggest using System Configuration (Windows key + R, type in msconfig and press Enter). Go to Startup tab, uncheck the old CGWatcher startup entry. The System Configuration shows combined startup entries (registry + startup folder).

If you want to remove the entry, I'd recommend using Autoruns, which allows you to disable or delete startup entries. It provides a comprehensive list of all of the places an application can set itself to start automatically.

In the registry, CGWatcher creates an entry in HKCU\Software\Microsoft\Windows\CurrentVersion\Run for the current user, or HKLM\Software\Microsoft\Windows\CurrentVersion\Run for all users. You'll probably need to run CGWatcher as Administrator to save or remove the HKLM entry. Previous versions of CGWatcher would try to save to HKLM, and it would appear to work when in reality Windows actually creates a virtual registry and sticks it in some WoW3264Node key (I can't remember where exactly). If you're familiar with the registry and regedit, you could do a Find for CGWatcher.

Is there anything in the CGWatcher log when this happens? (You may have to check "Show Debug Entries" in the Log tab to see everything). The miner always fails at re-enabling the GPU... at least from my experience. CGWatcher tries to watch for this happening and when it does, it will try to restart the GPU, which usually fixes the problem. If there is something preventing the GPU from restarting, it should be logged.

There is a short period of time that the GPU must return to the acceptable range before CGWatcher will restart it, so it will not happen instantly. Next time this happens, wait 5 to 10 minutes and if the GPU is not restarted, go to the Tests tab and click 'Create Debug Report'. Send that report to me via email (my email address is at the top of the readme).

I'll make a note to fix this in the next update. I don't have the code in front of me and I thought I had handled any culture settings, but apparently I missed something. This is why I added the setting to disable formatting, just in case. At least that works. One out of two ain't bad.

Are you using the latest version of CGWatcher (1.3.4.4)? You can turn off formatting of coin data values in Coin Manager. This is the only field formatted as currency, so I'll have to see if there is something causing this. What is you system's culture settings?... specifically, what characters do you use for group and decimal separators? (eg. en-us default group separator is "," and decimal is ".") This can also be found in CGWatcher's Report tab and debug report. This field should be formatted using your system settings.

Sorry about the delayed response, I'll hopefully answer everyone's questions here:


Dekker3D: You should look into setting variables on your miners, so they can all use the same profiles and/or config files, but each can be customized. More information on variables can be found here: http://manotechnology.blogspot.com/2013/08/web-config-files.html. Let me know if you have any questions.


mb0erman: It looks like you're setting the same values for all three GPUs, but one of them doesn't like these settings. It may be the voltage as Tigggger said. You can set individual values for each card by separating them with commas. Example setting three GPU clock speeds to three different values:



burgergold: It looks like Tigggger answered this one too, but you would put those in a batch file. Then in Profile Manager, instead of selecting the executable (.exe) miner file for "Miner Path", you select the batch file.


bouncemeister, Chillance: Tigggger answered this too. There is a new setting in the latest version of CGWatcher to kill the miner when restarting it, as opposed to shutting it down (which restores clock speeds and voltages to original values). This means the voltage should stay the same through the restart. Other than the ability for the user to change voltage manually in the Devices tab, CGWatcher does not make any changes to voltage.


Uniphase21: You should not need dummy plugs. CGMiner and CGWatcher should detect all GPUs, whether they have a monitor plugged into them or not. However, Windows and CCC may only show GPUs that monitors are plugged into. Fortunately, CGMiner and CGWatcher don't care what Windows thinks.


Chillance: The "best price" is provided by your selected coin data provider (coinchoose or coinwarz). If the data in CGWatcher consistently does not match the data on your provider's website, please let me know. Because this information changes often, they may occasionally not match. But if you refresh coin data at the same time you check the website, they should show the same values.


Tigggger: Thanks for the help.

Those settings apply to bfgminer also. Bfgminer is a fork of cgminer, so the config settings and api commands are the same for most things. Over time they grow further apart, but as of now this will enable the API in both miners.

Thanks, I really appreciate this. If you think you might find CGRemote useful and are not already in the beta, email OR PM me your email address and I'll send you the info and a download link.

If you're on Windows, CGWatcher can restart the miner if the hashrate falls below a certain value or percentage.

I'm not sure what you're asking, but if you're on Windows you can use CGWatcher to launch cgminer and it will enable the API automatically. In CGWatcher's Tests tab you can access the API directly, or there are features throughout the program that provide an interface to the API.

https://bitcointalk.org/index.php?topic=185553.0

http://www.cgwatcher.com

If you just want to enable the API to access it with your own software, add the following to your config file:


You may need to add a comma to the end of the second line depending on where in the config file you put it (if there are more settings below it.) You can change the IP to the IP your software is running on, or add more IPs by separating with a comma:

In the GPU tab, there is a small link under the hashrate that says "Incorrect hashrates for this GPU?"  Click this link to open the GPU Map window. This window allows you to map GPUs manually.

You may need to also use the gpu-map setting in cgminer to map openCL:ADL correctly.

You can read more about GPU mapping in cgminer and CGWatcher here: https://bitcointalk.org/index.php?topic=159267.420