Instead of returning the free disk space where the slots reside, the client seems to return the free space of the boot disk instead.

HTH

---

Instead of returning the free disk space where the slots reside, the client seems to return the free space of the boot disk instead.

Your observation surprises me. I've always had an impression that the client returns free space of the disk where BOINC is installed. Which works for me on both Windows and Linux machines with mixed disk setups ... even on Windows I install BOINC in various places, but never where BOINC installer wants to ;)

Are you sure you're not playing something funny with placement of slots directory? Is it on the same disk as the rest of boinc install?

---

Metod ...

Are you sure you're not playing something funny with placement of slots directory? Is it on the same disk as the rest of boinc install?

In the set up I have, the directory "C:\\Program Files", where BOINC is installed under and runs at, is mounted on another drive which is not assigned any letter. BUt instead of returning the available space in "C:\\Program Files", it returns the free space of "C:\".

Indeed, this is an unusual set up, but it was the only way I could figure out to have "C:\\Program Files (x86)" when it boots Windows XP x64 and "C:\\Program Files" when it boots Windows XP x86 contain the same applications so that I didn't have to have separate copies of them.

Perhaps the Windows API can't tell which free disk space to return in my set up, but hopefully the developers will take a look at it.

HTH

---