Forum > Windows
S@H V5.17
lgm:
Hi
I'm using the SSE 3 opt app for S@h, but am having severe troubles since starting to crunch for SETI Beta. I get the following messages:
|SETI@home|Can't handle task 07mr99aa.8657.16736.572166.3.136 in scheduler reply
and
|SETI@home|State file error: missing task 07mr99aa.8657.16736.572166.3.136
I've heard there is a problem with the app_info.xml file, and it arises from the inability to recognise the difference between the two project names. However, this seems a little odd, as the opt app is in the S@h folder only, and I thought it should not affect the Beta project, that being held in a separate folder.
Any help on this subject would be well appreciated.
lgm
lgm:
Isn't that just typical?
5 minutes after calling for help here, I find the answer on the SETI boads!
S@h doesn't recognise version 5.17, used by Beta.
I've edited the app_info.xml file to read version number 517, instead of 514.
Have I done good?
lgm
Simon:
Yup! :)
Happy crunching,
Simon.
lgm:
Apparently not!
Every downloaded WU I have received from S@h now has a compute error
18/12/2006 10:57:52 PM|SETI@home|No main program specified
18/12/2006 10:57:52 PM|SETI@home|Unrecoverable error for result 07mr99aa.8657.19105.865918.3.195_3 (Couldn't start or resume: -161)
My second machine hasn't had any of this trouble. It's also crunching S@h and Beta. It's a 1 Gig P3 running Server 2003.
The troublesome machine is running XP Pro SP2. It's a 2.8 Gig Celeron with 1 Gig of RAM, if that's any help.
I've been battling thiese problems for over a week now. I reformatted the HDD recently, and all was running sweetly.
It's a good job I keep my hair short, or I'd be pulling it out by now!
lgm:
The saga continues... I hope I'm not boring you!
Machine 1 (XP SP2) seems to be running ok now. I installed the version 2.0 opt app on both machines
However, machine (Server 2003) gives the following message:
No URL for file transfer of setiathome-5.15-kwsn-mmx.exe
and:
Can't initialise file transfer for setiathome-5.15-kwsn-mmx.exe
After pressing update to report a finished WU, I get the following:
Couldn't start download of setiathome-5.15-kwsn-mmx.exe
URL (null): invalid URL
I re-installed BOINC 5.4.11 on both machines, just in case there was a corruption somewhere.
Am I going insane?
You betcha!
I checked transfers, and found BOINC was attempting to upload setiathome-5.15-kwsn-mmx.exe
I aborted the transfer, and am now waiting patiently for the next problem.
If nothing else, this has increased my respect for programmers!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version