I found quite a lot of info at support.microsoft.com/kb/330174 suggesting techniques that may avoid delayed write failures where they are occurring, including turning off the disk cache. That suggests to me that disk failure is not necessarily around the corner and obviously I hope so. Maybe the specs of the flash drive installed is just not up to snuff.
Evidently, I guessed correctly that Awasu gives the disk a thrashing when updating. That is why I tried changing ChannelUpdateAgentConcurrency. Incidentally, I had stopped using Awasu some time ago with 2.3 which sometimes was dreadfully slow on this netbook but so far 3.0 seems a lot faster. Both have your beautiful GUI which make it a pleasure to use, especially with my minimalist template - See viewtopic.php?f=2&t=20469
where I gave details yesterday. At least one other Awasu user likes it.
I have not changed the compression by turning it off but will do if and when I find out that it can be done dynamically without losing the drive and the operating system. Also, if I do a defrag, that might move the location of Awasu.db. I did run the MS error checking on the drive but that indicated nothing, though I appreciate that is not conclusive. I did not find any other diagnostics I could run.
We are getting off Awasu territory here, but I would love to reinstall vanilla XP Home, a disk for which I have from my previous desktop prior to acquiring my current Dell desktop and, at the same time remove the partition Dell have set up for their version. However, that is not something they tell you how to do and I am scared getting into territory which is unfamiliar to me. My netbook has their version of XP Home whereas the desktop uses XP Professional which I would gladly forego to be in control of my PC as well as my netbook.