To handle suspend/resume, see http://msdn.microsoft.com/library/defau ... adcast.asp
. The short form is that Windows already sends a WM_POWERBROADCAST to your main application window. All you have to do is to start processing them.
If I were designing it, I'd have a single delay-first-fetch field in the appropriate configuration dialog, and I'd apply this delay at initial start-up and also upon resume-from-suspend.
I'm surprised this isn't an issue for all laptop users. I suspend and resume twice a day (work to home; home to work). Maybe everyone else reboots?
Along the same lines, it would be really spiffy if Awasu would refrain from issuing error toast when there is no active network connection. I'd prefer to just leave Awasu running whenever my laptop is running. Now, when I'm out of touch of my work LAN or my home wireless, I have to shut Awasu down in order to skip the errors. (I do want to see them if I'm networked!)