I had milkyway 0.7 running on each core of Comp ID 8849 when one task started to report:
nm_stripe79_fr1_24_1228957746_0 exited with zero status but no 'finished' file

Process Monitor shows a sharing violation on C:\ProgramData\BOINC\slots\4\boinc_lockfile at about the same time.

Is this the information that you are looking?

Aha Travis - API call problem?

yeah thats what it looks like. although it's strange it's only happening on certain versions of windows. it also might be that the app is crashing somewhere, hence the no 'finished' file.

s

Ok. I've been able to resolve this by adding the boinc data directory to the exception list for Symantec AntiVirus. This problem seems to only occur on Windows XP 32bit machines.

Ok. I've been able to resolve this by adding the boinc data directory to the exception list for Symantec AntiVirus. This problem seems to only occur on Windows XP 32bit machines.

I don't have that problem. Maybe it's a combination of a few things that lead to it. Or a diff. version/year of nortons av?

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

I had milkyway 0.7 running on each core of Comp ID 8849 when one task started to report:
nm_stripe79_fr1_24_1228957746_0 exited with zero status but no 'finished' file

Process Monitor shows a sharing violation on C:\ProgramData\BOINC\slots\4\boinc_lockfile at about the same time.

Is this the information that you are looking?

Aha Travis - API call problem?

yeah thats what it looks like. although it's strange it's only happening on certain versions of windows. it also might be that the app is crashing somewhere, hence the no 'finished' file.

s

Ok. I've been able to resolve this by adding the boinc data directory to the exception list for Symantec AntiVirus. This problem seems to only occur on Windows XP 32bit machines.

Hmm, I have Symantec 9 and 32bit XP without this problem.

---

Re: WU errors.

I'm running Windows Vista Premium and Trend Miro Security Suite which has 'Prevent Unauthorized Changes' enabled. Their is a facility to add or block programs or processes. After detaching and re-attaching the WU's seem to be running ok so far. If you could advise me of the aforementioned I will add them to the trust list if I get any further errors and see if that does the trick.

With regards to it being an OS issue is possible but is more likely to be Firewall/Anti-virus software being of various aggressive scanning methods unique to the Manufacturer, Hence the erratic reports.

---

All man born has the right to life and no man born has the right to take that life.

That's the same problem I'm seeing. It only happens on windows XP and windows 2008. If I let it go for a day or so, there can be 20+ instances of the .07 app running in task manager.

This problem does not happen on my Vista x64 box or my Windows 2003 x64 box.

do you know what file it's trying to get a lock on that it can't?

I recall in the pre-BOINC days SETI had this problem and it was traced to some bloody Windows index thingy that was happily locking .txt files to take a peek inside, which is why all seti's files are now suffixed sah.

I wonder if folk who get these random lock errors have any other BOINC projects with problems (not that I can think of any others with TXT files just now).

I've also been getting the problems from the previous message on one machine where I had to set the processor usage to less than 100%. The machine runs Vista Premium 32-bit and I run other BOINC projects. This problem only started to occur after I made the CPU usage change and does not happen on other machines that are running at 100%.

Possibly, it is related to the suspends to lower the usage, but might also be related to the fact that the longer running tasks now periodically give up the machine to other projects.

Also, changing the Keep App in Memory setting does not seem to impact the problem.

What happened to the new stock version. Prior to this new stock version my athlos 3000 computers were doing a work unit in just over an hour. Prior to that stock version they were doing the work units in about 1 hour and 8 min. So there was a noticable increase in speed between the two stock versions. Now with the "NEW" stock version, the amount of time has risen again to about 1 hour and 8 min. It seems to me that there was a decrease in speed with this newer optimised version of MW.

I have also seen performance changes on my athlon 64 - 6000 X2, mainly that on some occasions the cpu time slows down to a crawl (like 5 actual seconds for each CPU second) and the work units say that it still took 36 min to complete, but in fact thay are actually taking longer. Work units from other BOINC projects such as GPU@home and ABC@home do not behave this strangely.

The newer faster application has reverted back to its slower cousin.

I haven't noticed any problems with this application except for its lack of speed. I have an Intel E4300 running at stock 1.8GHz with 64bit Linux doing work in approx. 25 minutes (with a properly optimised app).

Compare that with an overclocked E4300 (2.4GHz) running 32 bit WinXP with the standard app taking around an hour per work unit.

At stock speeds (both 1.8GHz) that would be 25 minutes vs. 80 minutes. Far from optimized if you ask me...

---

Join the #1 Aussie Alliance on MilkyWay!

Stock app takes me anywhere from around 80 to 90 mins per WU, the optimized app was taking around 14 to 18 mins. Quite a difference...

Problem still going on.

Stock app takes me anywhere from around 80 to 90 mins per WU, the optimized app was taking around 14 to 18 mins. Quite a difference...

That is what I saw as well with my P-4 HT's, my Q6600 quad was doing an optimized in about 4-8 mins. I have NNT'd all MW machines for the time being.

Looks like I got some Milkyway spillage into SETI.
http://setiathome.berkeley.edu/result.php?resultid=1131907775

---

me@rescam.org

Looks like I got some Milkyway spillage into SETI.
http://setiathome.berkeley.edu/result.php?resultid=1131907775

hmmm, yust yesterday I read about CDPN spilling into seti (or vice versa)...

---

mic.

Looks like I got some Milkyway spillage into SETI.
http://setiathome.berkeley.edu/result.php?resultid=1131907775

Server side it looks like we're crunching more results than before the credit reduction... around 2.9-3.0 a second.

---

Looks like I got some Milkyway spillage into SETI.
http://setiathome.berkeley.edu/result.php?resultid=1131907775

Server side it looks like we're crunching more results than before the credit reduction... around 2.9-3.0 a second.

Do not expect that to continue well after your cut of credits...

That's life... :)

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)