Even when I set it to "Run Always", it will vary from just sitting there, barely doing anything, to sometimes running in real time. I prefer it to run in real time, since my system can handle it(2.6 gHz Celeron, 256 mb RAM), but the percentage completed hasn't gone up more than a percent in 3 days!! The old client was never this slow. It has logged more than 6 and a half hours of cpu time (should be way more since I want it always running, but it only seems to do that when it wants to), and my first (BOINC) work unit is not even 25% finished! Also, for some inexplicable reason it had made it to more than 50% finished, and then suddenly reset back to zero! I did almost 180 units in six months on the old client, and that was without it running all the time. Can someone please tell me if this is just a peculiarity with certain work segments? So far I am very frustrated with BOINC; I don't feel like it's accomplishing anything.

remember that boinc runs at lowest priority... dont ahve anything else running on your computer.... if you have 200/xp you can increase the priority


ttyl
Jeff

thanks, i failed to mention that i tried that in windows task manager, setting it to "real time", and it froze my system (xp, btw). stupid me, i then remembered that i'm supposed to use services.msc (i think), but can't seem to find boinc or seti on the list to change the priority... a little help here would be appreciated. :)

also, about not running anything else (which is not going to be an option), do you mean to get BOINC to run in real time? why is this the case when i was able to run the old client in real time with most of my RAM used up by other tasks with no problems?

two corrections: i had only completed 128 untits, not 180. sorry about the typo. and second, the "inexplicable" reset in BOINC was caused by the system lock up. i realize this now, because i just tried setting it's priority to real time again through task manager, and the same thing happened. i goofed. but i'm still confused as to why BOINC won't run as fast as the old client, which i'm switching back too for the meanwhile...

nevermind about the results resetting from the lock up; i restarted boinc and it went back to the previous percentage. it HAD just suddenly went back to zero while it was working before. i have been reading up online about setting prorities, and found real time to be a no-no, so i will try a lesser prority. but i still never had to deal with any of these problems with the old client... start it up, and it immediately (unlike BOINC) begins to work, fast and smooth. Bah.

ok, i set it to "BelowNormal" priority, holding my breath that it wouldn't crash, and that seemed to do the trick. it's running in real time now (microsoft could actually TELL people that "real time" priority has nothing to do with a program running in REAL TIME), with all of my other regular programs open. Thanks a lot! I took the long way round, but your tip worked.

You SERIOUSLY need to use and learn that there is a "edit post button" in here sir....