7/7/2005 10:35:52 PM|SETI@home Beta Test|Unrecoverable error for result 01dc03ab.18159.160.509654.141_1 ( - exit code -1073741795 (0xc000001d))

:(

---

Help support Seti@home

7/7/2005 10:35:52 PM|SETI@home Beta Test|Unrecoverable error for result 01dc03ab.18159.160.509654.141_1 ( - exit code -1073741795 (0xc000001d))

:(

Your processor doesn't seem to use sse instrunctions. fftw (fft library used in setiathome enhanced 4.02) needs sse. So you may want to try osecw-402-mmx-r2.zip which doesn't use sse.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

well I hope the 4.02 version is fixed to solve many headaches....
(I was using default version incase you didn't know)

---

Help support Seti@home

well I hope the 4.02 version is fixed to solve many headaches....
(I was using default version incase you didn't know)

I know. The default (official) version 4.02 uses fftw, thus requires sse. You'll find a file named fftw.dll or something like that in the project folder. I don't know about 4.00 (but it's obsolete now.)

---

Luckiest in the world. WMD = Weapon of Mass Distraction

well I hope the 4.02 version is fixed to solve many headaches....
(I was using default version incase you didn't know)

I know. The default (official) version 4.02 uses fftw, thus requires sse. You'll find a file named fftw.dll or something like that in the project folder. I don't know about 4.00 (but it's obsolete now.)

*realization dawns*

So my p2 mmx's can only participate in this beta thanks to your optimized app ?
if thats the case i hereby double my thanks Tetsuji =)

---

<a href="http://www.boincsynergy.com"><img src="http://www.boincsynergy.com/images/stats/comb-950.jpg"></a>

----snip-------
So my p2 mmx's can only participate in this beta thanks to your optimized app ?
if thats the case i hereby double my thanks Tetsuji =)

maybe yes.....it's "beta" and that it may take a LOOONG time depending on the WUs you receive :) It took 10 hours for my most aggressively optimized client to crunch the reference work unit (modified by hand) even on 2.8G P4. Fortunately I haven't received such a weird WU here yet, but some people have seen some.

And my mmx client doesn't use fftw (because I cannot compile fftw w/o sse on Windows), so I'm afraid it's slow.....

---

Luckiest in the world. WMD = Weapon of Mass Distraction

And my mmx client doesn't use fftw (because I cannot compile fftw w/o sse on Windows), so I'm afraid it's slow.....

anything is better than nothing , so thanks again =)

---

<a href="http://www.boincsynergy.com"><img src="http://www.boincsynergy.com/images/stats/comb-950.jpg"></a>

I tried your version but it failed to run with the following errors...

7/8/2005 8:47:49 AM|SETI@home Beta Test|Unrecoverable error for result 01dc03ab.18159.208.178408.99_1 (app_version download error: couldn't get input files: setiathome_4.02_windows_intelx86.exe -200 )

it then redownloaded the default version...

I restarted after installing the new version....

BoB

---

Help support Seti@home

I tried your version but it failed to run with the following errors...

7/8/2005 8:47:49 AM|SETI@home Beta Test|Unrecoverable error for result 01dc03ab.18159.208.178408.99_1 (app_version download error: couldn't get input files: setiathome_4.02_windows_intelx86.exe -200 )

it then redownloaded the default version...

I restarted after installing the new version....

BoB

Did you also include the app_info.xml file, this has to be in the Seti beta folder as well or you will get just what you discribed.

---

I tried your version but it failed to run with the following errors...

7/8/2005 8:47:49 AM|SETI@home Beta Test|Unrecoverable error for result 01dc03ab.18159.208.178408.99_1 (app_version download error: couldn't get input files: setiathome_4.02_windows_intelx86.exe -200 )

it then redownloaded the default version...

I restarted after installing the new version....

BoB

Did you also include the app_info.xml file, this has to be in the Seti beta folder as well or you will get just what you discribed.

It was there....

---

Help support Seti@home

I tried your version but it failed to run with the following errors...

7/8/2005 8:47:49 AM|SETI@home Beta Test|Unrecoverable error for result 01dc03ab.18159.208.178408.99_1 (app_version download error: couldn't get input files: setiathome_4.02_windows_intelx86.exe -200 )

it then redownloaded the default version...

I restarted after installing the new version....

BoB

doesn't it mean boinc cannot find setiathome_4.02_windows_intelx86.exe ? When you install it, stop the core client, then put app_info.xml and setiathome_4.02_windows_intelx86.exe in the project folder and restart core client...I have no other idea.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

Just a thought, did you have this WU already in progress before you switched over to Tetsuji's optimized version? It will error out any work that is in progress and start a fresh WU from scratch. The one that it starts from scratch should be ok.

---

I have installed as a service... thats why I restarted after install....

3 wu's errored out with that message then it went and downloaded the orig which I can't run....

I have stoped work for now untill I can get this resolved....

---

Help support Seti@home

I have installed as a service... thats why I restarted after install....

That's why you can't just change the science application. You have to stop the Boinc service before you can do this, or all your units will error out again.

Stop the service before you add anything to the \\projects\\setiweb.ssl.berkeley.edu_beta directory. Then restart the service.

---

From the news:

July 11, 2005
We're having problems reported running the Windows client on older machines (those without SSE capability). I was under the apparently mistaken impression that FFTW checks at run-time to see whether SSE is avaliable. I will be compiling a 2.03 version today that will not include SSE in the FFTW Library. Until I find a way to include both SSE and non-SSE together, we'll need to use the non-SSE version.

A generic question regarding updates to the beta client. When problems like this are found (after all that is what beta testing is all about) what is the best policy regarding existing work in the cache? Should it be aborted and the CPU time given to live projects until a new beta client is released?

I am happy to help with the beta testing but it would be great to know the best thing to do in such a situation as it does not make sense to continue running an old beta client if the CPU is not going to help the beta program any further.

Thanks.

---

At moments like that it's best to reset the project, Appetiser. Yes you lose all the ongoing units, but you won't be penalized for them, as far as I know. ;)

Now the only question remains: When will the new app be ready?
(Less than an hour to shutdown for at least 17 hours!)

---

<b>4</b>.03 for Windows was just released. Right in time for the project to go down! ;)

---

I didn't have a problem with 4.02, got some 4.03 which all error out [only on one of my computer].
AuthenticAMD
AMD Athlon(tm) Processor

---

I didn't have a problem with 4.02, got some 4.03 which all error out [only on one of my computer].
AuthenticAMD
AMD Athlon(tm) Processor

I saw the errors. Probably it's because 4.03 still contains SSE instructions, and reported it to devs.......i can't believe it happened again.

another frustration is although I am trying to download 4.03 client to check the client, the client isn't downloaded; only WUs are downloaded in the project folder. What the hell is going on here and what are the admins/devs doing?