SETI upgrade from 3.03 to 3.08

[Ben98SentraSE]

Hey all. I'm still out here crunching about 75 WUs a day quietly for the team. I'm evaluating Mozilla as a browser and mail client now so the Outlook 2000 problem may be taken care of and I could really start crunching big time for the team. One thing I notice is that I'm still on the CLI version 3.03. I have used Flexinstaller to put the client on PCs on my network. Can I just rerun Flexinstaller to go to those machines with the new exe in my local folder and it will push out the new version to the clients?

Thanks!

Oh, and I thought "SETI 1" was supposed to end in the first half of the year. What's the status of this?

 

[Freewolf]

No one is really sure when seti1 will end yet and most of us is still using 3.03 because it is faster then the new version and there is a way to fix the problem without upgrading to the new version.

 

[Freewolf]

http://www.deception.net/phpbb/viewtopic.php?t=1639

There's a thread here about it and how to fix it.

 

[Assimilator1]

Thread linked

Hi Ben
Haven't seen you about for a while but I noticed your strong steady output

As freewolf said most of us have stuck to v3.03 cos its faster ,about 15% faster on av Ar WUs ,VHAR are about the same ,& VLAR WUs below 0.1xx (I think) are a bit slower but as you know there aren't too many of them.

It would be interesting to see if v3.08 has fixed the outlook2k problem though ,maybe you could try it on 1rig?

Just thought ,for a big fleet like yours it may be worth having at least 1 v3.08 client to feed all the VLAR WUs too (via SETIQ)?

 

[Ben98SentraSE]

SETIQ can feed VLAR WUs to a particular client? THAT is tight. I have SETIQueue 3.03.2.2b. Should I upgrade?

 

[Assimilator1]

That is the latest SETIQ still

I know you can enable '3.03 VLAR routing' for SETIQ , I it avoids v3.03 CLI clients so it shouldn't route VLAR WUs away from v3.08.
To enable it ,log on ,then go to
Reports/Queues ,click on Que name (not number) & then 'click to edit' ,you

From SETIQs site:-

3.03 VLAR Routing - The default is None. If set to "Avoid win-cmdline" when SetiQueue downloads a VLAR workunit from the seti@home server for this user for a 3.03 revision win-cmdline queue, it will route it to any other 3.03 queue for the user that's not already at 150% capacity. (picking the one that needs to the most or least depending on how you look at it). This feature is present because the Windows cmd-line client is particular inefficient at processing VLAR workunits then other clients. A VLAR WorkUnit is one with an Angle Range of less then 0.15.

He hasn't updated this since before v3.08 was released so presumable v3.08 will get VLAR WUs