Can I run BOINC under XP in a limited environment, so that file access to files outside its own directory tree is prohibited? If yes, how?

To give an example, under Linux I've setup a different user "boinc" and everything runs under this account. So right now, a rogue BOINC proj executable can only "harm" other BOINC files (under ~boinc/), but can cause no harm to the system and ordinary users.

Btw, would it be possible for BOINC/Linux to chroot()? so the reach of any child processes is limited (like Unix ftp daemons have been doing for anonymous users)

---

How-To: Join Distributed Computing projects that benefit humanity

Any ideas on the "sandbox" i.e. limited account, allowed to write under its own home-dir only and chroot() issue?

Btw, after spending some time on this, I've created a HowTo: Join Distributed Computing projects that benefit humanity document, where I categorise the various projects and give special weight to BOINC.

---

How-To: Join Distributed Computing projects that benefit humanity