I have WLOC 2 Beta running on three different machines and I had defined the backup profile for each machine. I did not realize that upgrading to the beta would result in a loss of those profiles (which took a fair amount of time to set up). I think you should address that in the final release by at least informing users before they upgrade that they will lose their backup configurations (or even better, find a way for them to retain the configurations).
In addition to losing the previous work, I have a new problem in that I am unable to modify the backup configurations on 2 of the 3 machines. When I click on the "Change This" box next to the "What: All File Types" my systems get scanned (with the message that my system is being scanned for new or changed files) and I then get a message telling me that no files were found. So I am stuck with the only option of backing up all file types, which I don't want to do or no backup.
I like the idea of the hub, but I want to use a hard disk on a machine with an x64 processor as the hub. However, since OneCare won't run on a 64 bit machine, I am not sure how or if I can use the hard disk on that machine as the hub. Will you be offering 64 bit support for OneCare in the near future? If not, can you tell me if it is possible to use the hub feature where the data is stored on a machine that is not running OneCare?
Finally, you might want to consider tweaking your color system for the icon in the program tray. Because of the backup problem, I am getting an orange icon. The problem is that I cannot rely upon the icon color to tell me if anything new has happened to lower my system status. I would recommend considering something like a modified orange/red icon, perhaps bold or inverted color when something new arises that would revert to the standard color after the user opens the OneCare window and acknowledges the "new" problem/condition.
---Andrew
