Of cause I will allways support science in any way I can.
Being a systemsprogrammer for 20 years, I was annoyed by a few things, though.
First of all, the program did not ask me where to download to. (My c: drive is currently overworked, and I allways manage the machine. Others DOES MOST CERTAINLY NOT.
Secondly it has been a practice for 20 years not to interrupt other peoples machines - even though any license might have been signed - without prior warning of the interrupt.
Otherwise a very fine project though.
Michael Edahl
economist,B.Sc.; therapist, B.A.; stud.scient.
Copyright © 2024 Einstein@Home. All rights reserved.
not that user friendly
)
For Item 1, yes it would be nice if you could put the program on the system drive and the data files elsewhere, but an easy workaround is to simply install BOINC on a different drive initially. You may as well take MS to task over this as well, since by default Windows will stuff everything on the system drive. In my case, I typically install BOINC on it's own drive/partition for added security.
Regarding Item 2: When it comes to "interrupting" your machine, this is a highly subjective term. FWIW, the only time I have noticed an impact from BOINC running is when doing something else computationally or graphically intensive and even then it's almost undetectable except when gaming.
In any event, there are preferences you can set to eliminate the minimal impact on other work you may be doing on the machine. This is not to say there are not specific situations where BOINC should not be run on a host, but that's something the user has to determine.
Alinator