I apologize for the late response... it's been a pretty busy month as some of you may have heard. I'm back home after a week in Miami for the Bitcoin Conference, and now I have a few weeks to pack everything and move to Los Angeles. We've created a new support forum at http://coinmyne.proboards.com so you may find posting there more helpful, as information will be better organized.

Quote from: alphateam on January 23, 2014, 10:43:29 AM

Hi, milone, sorry for late answer, the cgwatcher app wolder was in c:\
config files was in c:\users\myname\desktop\profilcgwatch\ <== perhaps the problem.

I try today to move the profile folder and the cgwatcher folder in "my documents" folder. Still the same

See my log files

Thx and sorry for my bad english

I would suggest trying to save a config file outside of the user folder, so somewhere like C:\Configs for example. I'm still learning what quirky behavior Windows 8/8.1 brings in terms of permissions.

Quote from: Mikk36 on January 23, 2014, 04:43:41 PM

milone, would you happen to know what might be wrong when CGWatcher doesn't see a GPU as active?
https://dl.dropboxusercontent.com/u/54281287/cgwatcher_inactive_device.png

Click on the link that says "Incorrect hashrate for this GPU?" to open the GPU Map window. Here you can map the ADL device to the OpenCL device. It should be fairly straight forward since you only have one GPU.

Quote from: Ntrain2k on January 26, 2014, 08:38:06 PM

I've set a scheduled action to switch over to a different profile(server) if the main one is not responding and it works great. Is there a way to set the same action to switch back if the backup server is down as well?

I can set the same rule, but with the wording I think they might conflict?

Also, I liked on the previous version where it showed what coin was being mined in the top mining bar. Anyway to set that back?

Thanks!

Yeah I believe they may conflict. I would suggest setting backup pools in your miner config rather than using the scheduler to handle backup pools. This feature is already built into cgminer/bfgminer, and by default will switch to a backup pool if the previous pool goes down. It will then check occasionally to see if that previous pool is back up, and if so, switch back to it.

Showing the coin at the top has not been removed. If CGWatcher is able to determine the coin being mined, it will display it. If you're referring to multi-coin pools, if the pool is not currently providing the information then CGWatcher can't display it. For example, the data hashco.ws provided me is down at the moment, so it cannot display the current hashco.ws coin. I've emailed them and hopefully it is something they can fix quickly.

Quote from: kimocoin on January 27, 2014, 05:44:22 PM

Quote from: kimocoin on January 14, 2014, 11:41:36 AM

I downloaded CGwatcher 1.3.4.6 yesterday and my problem with the blank window hasn't occurred since. If it does occur again, I will try your test build.

Today was the first time since my previous post that I had the problem again.
The problem happened about an hour before I got home. When I got home I noticed it was more quiet than "normally". All gpu fans were running @ low rpm's.
Both cgminer 3.7.2 & cgwatcher 1.3.4.6 were frozen with empty windows.
When I closed the cgminer window, cgwatcher unfroze and it restarted cgminer, after which the cgwatcher overheat protection kicked in with fans @ 100%, as my gpu's were @ 90 Celsius.
Haven't rebooted this miner since it happened. But everything appears to be normal.

If you haven't already, please download the latest version (1.3.5.2) as it should have some additional handling for a blank miner window.

Quote from: Vyker on January 28, 2014, 09:37:20 PM

Hi Milone, great app!

I'm getting - in my Event logs for System - every 10secs a WinRing0_1_2_0 alert.

Is this normal?

I'm trying to troubleshoot my miner disappearing 5 of my 6 GPU's without powering off. They just disppear from the miner, and mine on card.

Any thoughts? am I wasting my time tracking WinRing0_1_2_0?

Thanks

Yeah, this is from CGWatcher. Specifically, from the OpenHardwareMonitor library CGWatcher uses to detect GPUs and get their stats (clock speeds, fan speeds, etc.) It is nothing to worry about, and the events do not take up any significant space even though there are a lot of them listed. I don't believe it is possible to disable the events being logged unless I find another method of getting this information. As for now it's a relatively easy way and there's a lot on the to-do list so it may be a while before I can look into alternative methods.