Whats new in the Setiathome 4.08, does it fix the graphics window not useing the settings problem.

---

> Whats new in the Setiathome 4.08, does it fix the graphics window not useing
> the settings problem.
>
Yes, it is supposed to fix the graphics window problem. I don't remember what else is new or fixed in it.

---

BOINC WIKI

Thanks John,

The WU's haven't started to run yet on one of my slowest machines, I'll just have to be patient

---

Not much luck getting 4.08. When I connected, I got:

SETI@home - 2004-11-19 14:05:09 - Requesting 338833 seconds of work
SETI@home - 2004-11-19 14:05:09 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-11-19 14:05:29 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-11-19 14:05:29 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2004-11-19 14:05:29 - Started download of setiathome_4.08_windows_intelx86.exe
SETI@home - 2004-11-19 14:05:38 - Finished upload of 07mr04aa.20227.26946.442312.195_2_0
SETI@home - 2004-11-19 14:05:38 - Throughput 9103 bytes/sec
SETI@home - 2004-11-19 14:05:38 - Started download of setiathome_4.08_windows_intelx86.pdb
SETI@home - 2004-11-19 14:06:00 - Giving up on download of setiathome_4.08_windows_intelx86.pdb: Downloaded file had wrong size: expected 4869120, got 0
SETI@home - 2004-11-19 14:06:00 - Started download of 03mr04ab.23410.18032.1009650.51
SETI@home - 2004-11-19 14:06:00 - MD5 computation error for setiathome_4.08_windows_intelx86.pdb: -108
SETI@home - 2004-11-19 14:06:00 - Checksum or signature error for setiathome_4.08_windows_intelx86.pdb
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 03mr04ab.23410.18032.1009650.51_4 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.94_0 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.92_0 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.93_0 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.63_1 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.79_2 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.80_0 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.55_2 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.56_2 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.65_1 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.81_0 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.57_2 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.82_0 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.58_2 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.67_2 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Unrecoverable error for result 08mr04aa.19693.17584.928404.83_0 (app_version download error: couldn't get input files:
setiathome_4.08_windows_intelx86.pdb: MD5 computation error
)
SETI@home - 2004-11-19 14:06:00 - Deferring communication with project for 1 minutes and 15 seconds
--- - 2004-11-19 14:07:54 - May run out of work in 4.00 days; requesting more
SETI@home - 2004-11-19 14:07:54 - Requesting 339115 seconds of work
SETI@home - 2004-11-19 14:07:54 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-11-19 14:08:45 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-11-19 14:08:45 - Message from server: Not sending work - last RPC too recent: 179 sec
SETI@home - 2004-11-19 14:08:45 - No work from project
SETI@home - 2004-11-19 14:08:45 - Deferring communication with project for 10 minutes and 0 seconds

.... and so on ....

by the way, I never did try to update again, so I don't know why I got those "RPC to0 recent" messages. Just enabled the network connection, right clicked update, and watched the message screen.

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

There are connecting problems with the scheduler:

SETI@home - 2004-11-19 23:10:43 - No schedulers responded
SETI@home - 2004-11-19 23:12:00 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-11-19 23:27:50 - No schedulers responded
SETI@home - 2004-11-19 23:29:12 - No schedulers responded
SETI@home - 2004-11-19 23:31:34 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded


See also this thread.

OK, I see it isn't just me. I see there's a new thread "Admin please read" that others are having problems.

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

4.13
app_version download error: couldn't get input files:

setiathome_4.08_windows_intelx86.exe
-120
signature verification error




:( all is bad

---

Mit freundlichen Grüssen, Arnold
BZH Café

I've got same problem
http://setiweb.ssl.berkeley.edu/workunit.php?wuid=4471558
http://setiweb.ssl.berkeley.edu/workunit.php?wuid=4470869
http://setiweb.ssl.berkeley.edu/workunit.php?wuid=4473745
stderr out

4.13
WU download error: couldn't get input files:
08mr04aa.19693.18112.409674.122: MD5 computation error


0
0








all this when it downloaded 4.08 and i'm down to my last WU

Anyone know what happens when you have WU's identified as "4.08" application and only have the 4.07 client (the 4.08 client download failed but some WU's downloaded)? Guess I may find out.

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

> Anyone know what happens when you have WU's identified as "4.08" application
> and only have the 4.07 client (the 4.08 client download failed but some WU's
> downloaded)? Guess I may find out.
>

My guess is that it'll try to download the client again when it needs it.

---

It will download automatically, when you need more WUs
Do not dump what you have in que I suspect that is what
causing current problems

---

> It will download automatically, when you need more WUs
> Do not dump what you have in que I suspect that is what
> causing current problems
>

I think you're probably right. It's hard to believe everyone needs work units all at once. I have 10 computers running, all set for 3 days and I'm ok. Just because there's a new client available, there's no need to dump your current queue to get it.

I think Berkeley would be better off NOT to announce new clients and let everyone get it as needed.

> I think Berkeley would be better off NOT to announce new clients and let
> everyone get it as needed.


Why does Berkeley make changes on Fridays?
Even the message boards are slowed down.
A month from now people will be wining about no credit...

---

> Anyone know what happens when you have WU's identified as "4.08" application
> and only have the 4.07 client (the 4.08 client download failed but some WU's
> downloaded)? Guess I may find out.
>
==========

4.13 is actually the Client, 4.07 or 4.08 is the application. There is really no need to do anything, when you run out of 4.07 application Wu's then you will get 4.08 application Wu's the next time you download some Wu's.

I already envision thousands of people dumping their 4.07 Wu's because they think they need the 4.08 Wu's and then all the dumped Wu's will have to be sent back out again.

I have probably 400 or more 4.07 Wu's on my Pc's yet and I plan on just running them out and get the 4.08 when I need more work and everybody else should do the same...

Mine apparently d/l'd the 4.08 client, then went for some 4.07 WUs. Result: client error for 4 WU, resulting in 0.00 credits each.

> Mine apparently d/l'd the 4.08 client, then went for some 4.07 WUs. Result:
> client error for 4 WU, resulting in 0.00 credits each.
>
The WUs are the same. This sounds like a bad dl of something. If this continues you may have to reset.

---

BOINC WIKI

> I think Berkeley would be better off NOT to announce new clients and let
> everyone get it as needed.

I completely agree.

---

> > Mine apparently d/l'd the 4.08 client, then went for some 4.07 WUs.
> Result:
> > client error for 4 WU, resulting in 0.00 credits each.
> >
> The WUs are the same. This sounds like a bad dl of something. If this
> continues you may have to reset.
>

John,
Have you sucessfully D/L'd the 4.08 app? The WU's are not the same, as they are ID'd for each app. My system also failed to sucessfully D/L the 4.08 app. Now I have a mix of about 10 4.07 app WU's and 10 4.08 WU's and when I run out of 4.07 app WU's I'll be dead in the water again. These guys shouldn't release new software on Fridays. I'm not going to reset until the DEV's give the "go ahead" because it screws people out of processing time.

Dead in the water in about 15 hours.

Was sucessful on second attempt to D/L 4.08 app. Am now running 4.08 app with occasional Upload and Download errors. Did see something new though, it now seems to be cleaning up the D/L WU failures on it's own..this is great.

i had three consecutive dl errors in the last hours on 4.07 wus. a problem that i have never experienced before. lets see what the new 4.08 is bringing..

---

I just noticed I got a 4.08 WU..

Didn't see to be any problem, but I do only run the boinc_cli version of boinc...

---