|
Matt, in your case, it appears that the program does not like being behind your proxy server. If you remove the program from the Startup group, it will stop trying to load at boot. Looking over the error, it appears that it is unable to determine the IP address for the hostname. I may look into providing the program with the IP address of the server, rather than the hostname.
I am looking into the CPU usage issue...I normally run distributed.net on my computer, so it was taking the spare CPU cycles rather than the QANotify process. I do know that it takes a rather large amount of CPU cycles during update checks, but that is because of the overhead involved in processing the XML data. I'll see what I can come up with...
[EDIT]
I'm not sure about the CPU usage still, but it does only appear to eat up unused cycles. I can say that the app has passed a Norton 2003 antivirus scan, as well as running the same in the Development Environment as in a compiled version. I have a feeling that .NET is spawning a new thread for one of the functions I'm calling, and it's not terminating correctly. I'm not sure though...
[/EDIT]
__________________
Nate Smith
nsmith@smythsoft.com
12 seasons, 4 teams, and more time logged behind the scorekeeper's table than I care to remember...
returning for 2011? only time will tell...
Last edited by Nate Smith : 17-12-2002 at 08:45.
|