New version of SETIWatch

[SoulAssassin]

Not sure how many people use this program, but a new version of SETIWatch was released the other day.

Download from http://members.shaw.ca/mloukko/SETI.html

Fixes:

Version 4.1.11 (Released January 12, 2002)

-Tool tips on the sky map were causing a GPF if many work units were displayed.
-Updated SETIWatch URL to point to new web site.
-Refreshing has been completely rewritten.
Since version 3 of SETI@home the state.sah file is updated every two minutes or so.
This makes the running and stop icons erratic when the refresh rate is less than two minutes.
Now during each refresh` SETIWatch check for the existence of the file lock.sah. If found AND locked by another process it knows SETI@home is running.
-Added support for caching programs like SetiStash, Seti Driver etc.
To enable this new feature go to Options, Seti Locations, Edit and check 'Using Caching Program?' SETIWatch will now traverse each directory under the location specified and look for a locked lock.sah file to determine the current running instance of SETI@home. You no longer have to add a location for each cached version of SETI@home as SETIWatch will now find the currently running instance for you.
-Added top triplet and pulse to the summary on the completed work units tab.

The first two aren't that important, the third fixes something that was only cosmetic/annoying but the fourth update is pretty major. For those who aren't familiar with the application, it lets you view the status of all your SETI clients including those on remote machines. This new version would prevent you from having to create a seperate instance within SETIWatch for each potential w/u location.


Check it out...

 

[Baldy18]

I've been using 4.1.11 for a coule days now and I sort of wish I had stuck with 4.1.7. I think it is harder to tell now if my boxes are still crunching. I had IE wig out on me and hog all resources and version 4.1.9 of setiwatch didn't help me identify the problem was going on until I had lost 12 hours of processing time.

 

[blcjr]

I wonder if any of the latest changes would fix my biggest problem with the program...the way it "hangs" and takes forever to display if there are missing state.sah files or if a computer is off. This makes it all but impossible to use for more than 20-30 computers, at best. On my herd of 100+, at any one time several of them are problems for setiwatch, and the program just "locks up" (not really, but it might as well).

-Baz

 

[SoulAssassin]

<< I wonder if any of the latest changes would fix my biggest problem with the program...the way it "hangs" and takes forever to display if there are missing state.sah files or if a computer is off. This makes it all but impossible to use for more than 20-30 computers, at best. On my herd of 100+, at any one time several of them are problems for setiwatch, and the program just "locks up" (not really, but it might as well).

-Baz >>



Nope, still the same. Wish there was an adjustable timeout value.

 

[SoulAssassin]

<< I've been using 4.1.11 for a coule days now and I sort of wish I had stuck with 4.1.7. I think it is harder to tell now if my boxes are still crunching. I had IE wig out on me and hog all resources and version 4.1.9 of setiwatch didn't help me identify the problem was going on until I had lost 12 hours of processing time. >>



Since the new version looks at the state/lock.sah in a different way (and actually tells you 100% of the time if it's running vs having to keep refreshing), .11 should have identified it right away.

 

[Baldy18]

Nope sure didn't.:|

Take forever to startup for me and I only have it monitoring 4 computers so I don't see it being able to monitor 100 without a very long wait before it gets going.

 

[Smoke]

I tried it and it seemed to hangup. I didn't like that very much so I removed it and reinstalled the previous version. 🙁