I have tried to use the add on program SETI@BOINCWatch(.NET 2.0) as listed on the Participate section of the Seti@home site but have been having a few problems. The most serious is that about four work units were returned with computer errors. Has anyone else had any problems with this program or suggest any solutions?

Many Thanks

I have tried to use the add on program SETI@BOINCWatch(.NET 2.0) as listed on the Participate section of the Seti@home site but have been having a few problems. The most serious is that about four work units were returned with computer errors. Has anyone else had any problems with this program or suggest any solutions?

Many Thanks

I've never hear of that add-on. Scanning your 4 results, this is the message I see...

SETI@home error -1 Can't create file -- disk full?
in checkpoint()

You may want to check your preferences to make sure you have alloted enough disk space for BOINC. However, since you completed a result after the 4 failed ones, you may just be ok.

EDIT - You may want to reach out to the developer if you are having issues with their app.

---

Wendy



Click Here for BOINC FAQ Service

I have tried to use the add on program SETI@BOINCWatch(.NET 2.0) as listed on the Participate section of the Seti@home site but have been having a few problems. The most serious is that about four work units were returned with computer errors. Has anyone else had any problems with this program or suggest any solutions?

Many Thanks

I've never hear of that add-on. Scanning your 4 results, this is the message I see...

SETI@home error -1 Can't create file -- disk full?
in checkpoint()

You may want to check your preferences to make sure you have alloted enough disk space for BOINC. However, since you completed a result after the 4 failed ones, you may just be ok.

Seems more like a sharing violation to me, like the Seti@BOINCWatch holds a lock on a file (or has a certain file opened) while the science app needs to write to or wants to overwite (checkpoint) it. AFAIK there's a copy/rename/kill procedure for e.g. the client_state.sah that assures all data to be written - or erroring out...

HTH
Andy

I have tried to use the add on program SETI@BOINCWatch(.NET 2.0) as listed on the Participate section of the Seti@home site but have been having a few problems. The most serious is that about four work units were returned with computer errors. Has anyone else had any problems with this program or suggest any solutions?

Many Thanks

I've never hear of that add-on. Scanning your 4 results, this is the message I see...

SETI@home error -1 Can't create file -- disk full?
in checkpoint()

You may want to check your preferences to make sure you have alloted enough disk space for BOINC. However, since you completed a result after the 4 failed ones, you may just be ok.

Seems more like a sharing violation to me, like the Seti@BOINCWatch holds a lock on a file (or has a certain file opened) while the science app needs to write to or wants to overwite (checkpoint) it. AFAIK there's a copy/rename/kill procedure for e.g. the client_state.sah that assures all data to be written - or erroring out...

HTH
Andy

The URL for the app listing is http://boinc.berkeley.edu/addons.php

There is quite a bit of disk space for seti. My local preferences are to allow it 1Gb, so I don't think that is a problem. Perhaps it is something to do with
the dot-net environment which through googling tends to not have a good press, but perhaps this is just prejudice by people who like me don't really know what they are doing... :o)

The application is supposed to give similar functionality to the original seti@home client, in that you are able to log your work unit results and then look for the best signal components - Gaussians, spikes etc. A bit more inclusive than just crunching work units and feeling a glow of altruism.

Perhaps I will try the .NET1 package instead although I feel a bit bad about generating wu errors.

Anthony

I have tried to use the add on program SETI@BOINCWatch(.NET 2.0) as listed on the Participate section of the Seti@home site but have been having a few problems. The most serious is that about four work units were returned with computer errors. Has anyone else had any problems with this program or suggest any solutions?

Many Thanks

I've never hear of that add-on. Scanning your 4 results, this is the message I see...

SETI@home error -1 Can't create file -- disk full?
in checkpoint()

You may want to check your preferences to make sure you have alloted enough disk space for BOINC. However, since you completed a result after the 4 failed ones, you may just be ok.

Seems more like a sharing violation to me, like the Seti@BOINCWatch holds a lock on a file (or has a certain file opened) while the science app needs to write to or wants to overwite (checkpoint) it. AFAIK there's a copy/rename/kill procedure for e.g. the client_state.sah that assures all data to be written - or erroring out...

HTH
Andy

The URL for the app listing is http://boinc.berkeley.edu/addons.php

There is quite a bit of disk space for seti. My local preferences are to allow it 1Gb, so I don't think that is a problem. Perhaps it is something to do with
the dot-net environment which through googling tends to not have a good press, but perhaps this is just prejudice by people who like me don't really know what they are doing... :o)

The application is supposed to give similar functionality to the original seti@home client, in that you are able to log your work unit results and then look for the best signal components - Gaussians, spikes etc. A bit more inclusive than just crunching work units and feeling a glow of altruism.

Perhaps I will try the .NET1 package instead although I feel a bit bad about generating wu errors.

Anthony

Anthony - If you look at the link to the app, you will see that it is a BETA application from someone outside of the BOINC Development team.
SETI@BOINCWatch(.NET 2.0)

---

Wendy



Click Here for BOINC FAQ Service

Hmmmm....

Rooting around on the site a little bit it looks like there hasn't been much work on it lately. Based on the copyright date I saw, accessing the BOINC data with the deprecated method of direct file access (as Jakob suggested) seems to be a likely answer here for the issue.

FWIW, all current GUI Manager/Monitors use RPC exclusively now, since the old way won't fly anymore for the most part on any modern OS (including Vista).

Alinator