I put a copy of your message on the dev thread.
Thank you for your repport.
For what it's worth, I don't think the unhandled exception error messages are anything to do with BoincStudio. They are to do with the particular combination of Akos' optimised science app and some particular sequences of results. If you look through the S41.xx discussion thread, there are at least three separate people, myself included, who are reporting these errors on specific result files whilst other files are being processed under the same conditions error free. It seems to be only a very small range of result files that are giving problems. In my experience I've just seen only one result file (z1_1269.0) give this problem.
I'm running BS_0.5 without issue on two separate machines that are using S41.07 and are running overclocked and are getting 100% validated results. There are no unhandled exception errors with these two machines. I'm running BS purely to get beyond the 32/day quota. Both machines were plagued with long runs of short results and were running out of work. I'm very grateful to the developers of BS for providing this very useful trick. You don't need a fast machine to run out of work. One of the machines is a Duron 1200 which is hardly the latest technology. I think it's quite cool to look up my machine list and see CPUID 430276 being reported as having 4 CPUs :). I've also noticed one of my PIIIs that is now being refused work. Looks like I might be owning a multi-CPU PIII shortly. Should bring a great price on eBay :).
I have run BS on one machine to investigate its ability to monitor other machines in a farm. I had no problems with the installation and attaching to other machines was pretty easy to figure out. I found that having used BoincView previously helped a great deal with understanding the RPC mechanisms. I'm amazed that you have got so far so quickly and I'm very impressed with the quality of the development to date. My sincere congratulations to all concerned!!
The folks that developed this app have done such a great job. I thought I would ask them if one more step is possible. I have created an extra instance of my fastest CPU to keep it crunching E@H WUs. Right now swicthing involves a lot of manual intervention (which I will inevitably screw up). I was wonderlng if you could run the Boinc and E@H from two directories? One would run as the main app and the other as backup.
I would like to thank to ThierryH and his mates for developing this great tool. English version is nice and now I can crunch E@H with the full power. Very convenient!
The folks that developed this app have done such a great job. I thought I would ask them if one more step is possible. I have created an extra instance of my fastest CPU to keep it crunching E@H WUs. Right now swicthing involves a lot of manual intervention (which I will inevitably screw up). I was wonderlng if you could run the Boinc and E@H from two directories? One would run as the main app and the other as backup.
Thanks again
I think we're just going to have to wait until the S4 run is over, and when the S5 run begins there should be a higher MDQ to match the speed of the new apps. Until then we might just have to "fake" our way to more work.
There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman
For what it's worth, I don't think the unhandled exception error messages are anything to do with BoincStudio. They are to do with the particular combination of Akos' optimised science app and some particular sequences of results. If you look through the S41.xx discussion thread, there are at least three separate people, myself included, who are reporting these errors on specific result files whilst other files are being processed under the same conditions error free. It seems to be only a very small range of result files that are giving problems. In my experience I've just seen only one result file (z1_1269.0) give this problem.
Thanks for idea, Gary - re-running BS 0.5 in the morning and got it running ('problematic' WU(s) are completed I guess).
Also dumb question: where should we report new md5 for other project's applications?
Good. English language
)
Good.
English language will enable usage for more BOINCers.
One more - Czech translation for BS 0.5 is on the following link
http://boinc.cz/download/cestiny/boincstudio_cestina.rar
credit goes to 'dejv'
RE: I put a copy of your
)
For what it's worth, I don't think the unhandled exception error messages are anything to do with BoincStudio. They are to do with the particular combination of Akos' optimised science app and some particular sequences of results. If you look through the S41.xx discussion thread, there are at least three separate people, myself included, who are reporting these errors on specific result files whilst other files are being processed under the same conditions error free. It seems to be only a very small range of result files that are giving problems. In my experience I've just seen only one result file (z1_1269.0) give this problem.
I'm running BS_0.5 without issue on two separate machines that are using S41.07 and are running overclocked and are getting 100% validated results. There are no unhandled exception errors with these two machines. I'm running BS purely to get beyond the 32/day quota. Both machines were plagued with long runs of short results and were running out of work. I'm very grateful to the developers of BS for providing this very useful trick. You don't need a fast machine to run out of work. One of the machines is a Duron 1200 which is hardly the latest technology. I think it's quite cool to look up my machine list and see CPUID 430276 being reported as having 4 CPUs :). I've also noticed one of my PIIIs that is now being refused work. Looks like I might be owning a multi-CPU PIII shortly. Should bring a great price on eBay :).
I have run BS on one machine to investigate its ability to monitor other machines in a farm. I had no problems with the installation and attaching to other machines was pretty easy to figure out. I found that having used BoincView previously helped a great deal with understanding the RPC mechanisms. I'm amazed that you have got so far so quickly and I'm very impressed with the quality of the development to date. My sincere congratulations to all concerned!!
Cheers,
Cheers,
Gary.
Ok I have a very dumb
)
Ok I have a very dumb question, what program opens RAR files ;o(?
BOINC Wiki
There are several. If you are
)
There are several. If you are using windows and search for a app. Otherwise google rar.
RE: what program opens RAR
)
A nice free one for windows is 7-zip.
The folks that developed this
)
The folks that developed this app have done such a great job. I thought I would ask them if one more step is possible. I have created an extra instance of my fastest CPU to keep it crunching E@H WUs. Right now swicthing involves a lot of manual intervention (which I will inevitably screw up). I was wonderlng if you could run the Boinc and E@H from two directories? One would run as the main app and the other as backup.
Thanks again
I would like to thank to
)
I would like to thank to ThierryH and his mates for developing this great tool. English version is nice and now I can crunch E@H with the full power. Very convenient!
RE: The folks that
)
I think we're just going to have to wait until the S4 run is over, and when the S5 run begins there should be a higher MDQ to match the speed of the new apps. Until then we might just have to "fake" our way to more work.
There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman
RE: RE: what program
)
or 'WinRAR', Google it - there's tons of hits...
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: For what it's worth, I
)
Thanks for idea, Gary - re-running BS 0.5 in the morning and got it running ('problematic' WU(s) are completed I guess).
Also dumb question: where should we report new md5 for other project's applications?