• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Version 3.06 of seti client released. (GUI)

B

Baldy18

Diamond Member
Windows version 3.06 is a special Windows release. It fixes a bug in the GUI client which prevented automatic retries after an unsuccessful attempt to connect to the server while in screensaver mode. This bug was brought to light and exacerbated by the current bandwidth crisis.
Version 3.06 has a couple of other minor changes:

It fixes a typo in HTTP headers. This may enable SETI@home to work through transparent proxies. If you are behind a transparent proxy and version 3.06 is still unable to connect, please email us.
Some workunits produce large (> 60KB) result files. Previous versions can't send these files, so users don't get credit (and, since our server doesn't get results, it keeps sending the work units over and over). This is fixed.
The previous Windows release was version 3.03.

To download version 3.06, click here.

You can find this info here and here.

Looks like nothing major and version 3.03 will continue to work but now you can get credit for those WUs that have large result files.🙂

[EDIT] Looks like this is just an update to the GUI and no changes have been made to the CLI version which is still 3.03.🙁
 
As long as they don't make any more changes that affect crunching time, I'm still trying for a sub 10 hour average (damn K6-300 I was running back in the day 🙂 ).
 
damn K6-300 I was running back in the day 😉

You too? that was what I started with. Nothing like 28 hr WU's 🙂
 
1 more client to add to my collection😉

Looks like this is just an update to the GUI and no changes have been made to the CLI version which is still 3.03.

Don't worry about it Baldy ,as long as 'it ain't broke don't fix it!' 😉
 
It still amazes me that they continue to ensure that the GUI is bug-free while the rest of the clients stumble along bug-ridden.
rolleye.gif
:disgust:
 
Does Berk. have a percentage anywhere listing # of w/u's submitted via cli vs screensaver? I'm just curious how many people run it vs the cmd line. I'm sure most "hardcore" users are running the cli but I'm sure the # of people who d/l the screensaver and forget about it are significant.
 
Total Statistics
is your starting point.
If you're looking on the Platforms-link we'll see:
1: Pentium/windows: 54% of all results...
2: i386-winnt-cmd: 20% of all results...

Now, the "pentium"-part is often wrong, since all win32-gui is showing up under this heading, regardless of amd, intel, or thatever.
With other 50% of all results, of course the gui-version is first updated then a problem pops up...

Another interesting statistics, 1 result is place 2070392 of 3571473. In other words, 33.816% haven't managed to return anything. :Q

 
I'm suprised no one thought of this: The reason why there wasn't an update to the CLI client is probably because it doesn't have this bug.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top