Something about this was bothering me, so as a reality check I surveyed all my hosts for what BOINC thinks it has available for disk space from the client_state file compared to what Windows reports from Explorer, the Drive Property Dialog, and chkdsk. I found that the difference was insignificant, and most likely due to FS changes between when I checked in Windows and when BOINC wrote to client_state file the last time.
In any event, my experience with browser caches is they may soak up a ton of disk space, but when you clear it, the space is immediately released and reported as free by Windows. In addition I've never seen IE, Netscape, or Firefox reserve more disk space than it actually needed at the time.
So the only difference between my hosts, and Paolo's is that I don't run and/or install applications on the system partition and I'm assuming he only has one partition and/or drive.
So my guess is since this is a work oriented machine, something that is normally in use is forcing Windows to commit a range of memory that is overflowing into swap space and thus causing the reduction in free disk space due to that.
Something about this was
)
Something about this was bothering me, so as a reality check I surveyed all my hosts for what BOINC thinks it has available for disk space from the client_state file compared to what Windows reports from Explorer, the Drive Property Dialog, and chkdsk. I found that the difference was insignificant, and most likely due to FS changes between when I checked in Windows and when BOINC wrote to client_state file the last time.
In any event, my experience with browser caches is they may soak up a ton of disk space, but when you clear it, the space is immediately released and reported as free by Windows. In addition I've never seen IE, Netscape, or Firefox reserve more disk space than it actually needed at the time.
So the only difference between my hosts, and Paolo's is that I don't run and/or install applications on the system partition and I'm assuming he only has one partition and/or drive.
So my guess is since this is a work oriented machine, something that is normally in use is forcing Windows to commit a range of memory that is overflowing into swap space and thus causing the reduction in free disk space due to that.
Virtual Memory Functions in Windows
Alinator