I'm sorry about being MIA... aside from it being a very busy month, I don't remember seeing an email indicating there were no comments on this thread. I'll try to answer as many as I can, but if I don't answer your question I recommend posting to the new support forum at http://www.minerremote.com/support.

If you have a Windows password and want mining to resume automatically after restart, you can enable Windows to automatically login when started. This probably isn't a good idea if you're concerned about security (or privacy on a shared computer), but it allows you to still have a password if one is needed for remote software, network shares, etc.

More information: http://pcsupport.about.com/od/windows7/ht/auto-logon-windows-7.htm
The public IP address in CGWatcher doesn't actually do anything other than to try to help you in setting up CGRemote (if you're connecting to CGWatcher over the Internet). If it doesn't return the correct public IP address, you can simply Google "what's my IP".
In the latest version of CGWatcher, you can disable the automatic refreshing of coin profitability data (from CoinChoose or CoinWarz) in the Coin Manager window. To open the Coin Manager window, go to the Settings tab, click the "Other Tools..." button, then select "Manage Coins". In the Coin Manager window, click on the Settings tab then disable the automatic refresh.
On a related note, if you're using the latest version of CGRemote with CGWatcher, you can have CGRemote automatically send coin profitability data to all of your miners running CGWatcher. This means only one API call is needed for all of your rigs.
If stopping cgminer/bfgminer using CGWatcher causes a bluescreen or crash, you can set CGWatcher to kill the miner process instead of shutting it down. Shutting the miner down using the 'quit' command, as CGWatcher has always done, usually causes a crash if you're using the new R9 series AMD cards because of changes to how they work with ADL. Setting CGWatcher to kill the process instead means the miner never gets a chance to shutdown and therefore doesn't crash. This does mean though that the miner is not able to restore clock speeds, fan speeds, and voltages to their original values. I recommend trying sgminer, a new cgminer fork focused solely on GPU mining, as it has reportedly fixed this problem.
If you want support for additional cgminer forks (e.g. scrypt-jane, whatever else there is out there now) I need information on the changes made to their API. I don't mind updating CGWatcher to work with these forks, but I need some help for the users here because I don't have the time to follow all of them myself.

As some of you may have read, I've joined a company called CoinMyne and CGWatcher and CGRemote have come with me. This will allow me to devote all my time to working on these projects. I'll be moving to LA this week so I might not be able to get to your questions or problems right away, but I will try to catch up once the move is over. I recommend joining the new support forum at http://www.minerremote.com/support, where we're building a community and repository of information and answers. Please try searching for your problem to see if it has been asked and answered already before making a new thread. There is also no newbie jail so everyone is able to post their questions or feedback.