TrackSnakeLA wrote:When re-staring Awasu, I often have to again re-enter the registration code.
The license key is stored in your CONFIG.INI file which is just a bog-standard INI file. If you have to re-enter it, this means it's either gone or has been corrupted. Awasu does write out to this file during a sync load so if you're killing it in Task Manager, it may well have only partially written out the file. The bit with the license code will have not been written out, hence the next time you start Awasu, it asks you to re-enter.
This leads me to strongly suspect that your AV is causing the problem. The way Awasu writes out the INI file is not particularly efficient (this will be addressed post-2.3) although it's generally not a problem under normal circumstances. However, I wouldn't be surprised if your AV is intercepting and checking every single write to the INI file (IIRC, this has come up before) which is causing the slowdown. This ties in with your report that sync eventually completes if the AV is turned off.
Sync load is a very resource-intensive process and while it's been made more efficient in 2.3, you can certainly expect to see heavy CPU usage, especially when it's sync'ing the Program Options (less so when it's doing each channel). However, it's all done in low-priority background threads so your PC should still be usable.
TrackSnakeLA wrote:Would there be some settings changes to Symantec's programs which might help Awasu?
IIRC, there is some setting to tell it to not check activity in a specified directory. I think setting this to the Awasu installation directory stops it from going bananas every time Awasu touches the disk (which it does a lot).
TrackSnakeLA wrote:Also, the Awasu.log file seems to be empty when I open it in Notepad, so what am I missing that I could send you?
Have you created the file in the correct location (e.g. C:\Program Files\Awasu\Users\YOUR-NAME)? Is it exactly as I gave above?
Another possibility is that the output is being buffered somewhere. Exit Awasu, make sure it's finished in Task Manager, and then check the file again.
I think it's worth getting this log file going. Awasu records timestamps every time it logs something and I suspect we will see things happening very slowly as the AV get its paws into everything