Message boards :
Number crunching :
64 bit BOINC client & BOINC MANAGER for Windows XP64
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · 6 · Next
Author | Message |
---|---|
Travis Giles ![]() Send message Joined: 23 Aug 02 Posts: 48 Credit: 30,171,171 RAC: 123 ![]() ![]() |
Having problems with the new 5.7.5.32 32 bit windows BOINC client after I copy the files from the zip file I get the following error message. (The application failed to initialize properly (0xc0150002). Click on OK to terminate the application) I reject your reality, and substitute my own. SETI@home classic workunits: 5,000 SETI@home classic CPU time: 15,019 hours ![]() |
![]() ![]() Send message Joined: 15 Apr 99 Posts: 1546 Credit: 3,438,823 RAC: 0 ![]() |
Having problems with the new 5.7.5.32 32 bit windows BOINC client after I copy the files from the zip file I get the following error message. (The application failed to initialize properly (0xc0150002). Click on OK to terminate the application) I'll take a look at it..wait 15 minutes and i'll update the download link... I'll post here when i uploaded it... still not sure why i doesn't ork for you .. sorry for all the trouble... ![]() Join BOINC United now! |
![]() ![]() Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 ![]() |
return_results_immediately was meant for debugging purposes only. Since it was used for other than that, it was removed from the stock client. It does add load to the servers as a large portion of the time is spent per connection to the scheduler rather than per result. John....I appreciate your concerns but I see the following. By the way I only crunch for Seti. Cpu is crunching along and suddenly a real short work unit comes in with a return time that is really close. You know the ones that give 10 to 20 credits or so and don't take long to crunch. I don't have a problem with crunching the new work first or EDF as it is known. Cpu drops what it is doing to crunch the new work unit. This new work unit usually will finish well before it's original estimated time. When this work unit finishes the estimated crunch time for the remaining work units in the cache is suddenly increased NOT decreased. I have seen the remaing cache work times be increased by more than 1 hour for each work unit in the cache! If you have a cache of 4 day's like I carry suddenly you have a cache of 6 day's or more WITHOUT having downloading anything. Now the cpu just keeps on crunching the cache but does not return anything until the cache is down below 4 day's again. In other words it can crunch for day's without contacting Berkeley and returning the finished work. Seems the predicted time for a work unit can increase by any number of minutes, even more than 60 in one jump but only reduces by a few minutes or even seconds after another work unit is finished. This is why I like the return_results_immediately function. At least I keep returning finished work while the cache estimated work time is decreased back to the original 4 day estimate. Boinc....Boinc....Boinc....Boinc.... |
![]() ![]() Send message Joined: 15 Apr 99 Posts: 1546 Credit: 3,438,823 RAC: 0 ![]() |
Having problems with the new 5.7.5.32 32 bit windows BOINC client after I copy the files from the zip file I get the following error message. (The application failed to initialize properly (0xc0150002). Click on OK to terminate the application) I've uploaded a new version... this one runs fine on my dual P3 / 500MHz WinXP machine.. please download it again an report if it works noe.. ( the ziped file is larger than before).... make sure you refresh your browser and cleanr browser caches ! ![]() Join BOINC United now! |
![]() ![]() Send message Joined: 15 Apr 99 Posts: 1546 Credit: 3,438,823 RAC: 0 ![]() |
...and your debuging the code ...of course ... ;) ![]() Join BOINC United now! |
Travis Giles ![]() Send message Joined: 23 Aug 02 Posts: 48 Credit: 30,171,171 RAC: 123 ![]() ![]() |
I get the same error message with the new zip file I reject your reality, and substitute my own. SETI@home classic workunits: 5,000 SETI@home classic CPU time: 15,019 hours ![]() |
![]() ![]() Send message Joined: 15 Apr 99 Posts: 1546 Credit: 3,438,823 RAC: 0 ![]() |
I get the same error message with the new zip file Not sure what happens on your side ... the host i'm trying it on is a P3/500 MHz with Windows XP no service packs applied (tested it on an athlon 64 too worked well ...) OK now one more try .. i totaly recompile the client ... give me some minutes... i'll let you know, when i'm done... ![]() Join BOINC United now! |
![]() ![]() Send message Joined: 15 Apr 99 Posts: 1546 Credit: 3,438,823 RAC: 0 ![]() |
I get the same error message with the new zip file OK onw ...last try ... 5.7.5.32-3 is now on my page ... works well on my dual p3/500 win xp no service packs... and on my notebook athlon64 xp SP2... try it or ... ![]() Join BOINC United now! |
![]() ![]() Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 ![]() |
Crunch..........I am getting the following error. This occurs on two remote and headless boxes on my LAN so I use the remote login for windows XP. Could not start the Boinc service on local computer. Error 14001: This has failed to start because the application configuration is not correct. Reinstalling the application may fix this problem. This using your -3 version also. Boinc....Boinc....Boinc....Boinc.... |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 ![]() |
return_results_immediately was meant for debugging purposes only. Since it was used for other than that, it was removed from the stock client. It does add load to the servers as a large portion of the time is spent per connection to the scheduler rather than per result. I have no problem with you using return_results_immediately, I know that you are developing various clients (and your work is appreciated). The problem is with general use - it does tend to eat resources at the server side. ![]() ![]() BOINC WIKI |
Travis Giles ![]() Send message Joined: 23 Aug 02 Posts: 48 Credit: 30,171,171 RAC: 123 ![]() ![]() |
I still get the same error message thanks for the help and your work I reject your reality, and substitute my own. SETI@home classic workunits: 5,000 SETI@home classic CPU time: 15,019 hours ![]() |
OzzFan ![]() ![]() ![]() ![]() Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 ![]() ![]() |
John....I appreciate your concerns but I see the following. By the way I only crunch for Seti. You may have your reasons, but I don't see what is wrong with not contacting the Berkeley servers for over 4 days or more. I have a 7 day cache, and sometimes I don't contact for over 5 or more (sometimes all 7). Once your computer works through it's cache, it will download more when it needs to. Why insist on keeping the cache full at 4 days for the entire duration? Let BOINC manage the cache and return results when it needs to. That's my opinion. |
Hans Dorn ![]() Send message Joined: 3 Apr 99 Posts: 2262 Credit: 26,448,570 RAC: 0 ![]() |
I get the same error message with the new zip file Hi Crunch3r, I gave the 32 bit version a try under wine:
The missing libraries listed there might be useful for debugging the Windows issues you see ATM Regards Hans |
zombie67 [MM] Send message Joined: 22 Apr 04 Posts: 758 Credit: 27,771,894 RAC: 0 ![]() |
Having problems with the new 5.7.5.32 32 bit windows BOINC client after I copy the files from the zip file I get the following error message. (The application failed to initialize properly (0xc0150002). Click on OK to terminate the application) I'm getting the same problem with (only) one of my 13 windows machines. I tried v3, but no change. Interestingly enough, I deleted those files, reinstalled (repaired) using 5.4.11. But returned WUs still show as 5.7.5. The Get Info from BOINCmgr says it's really running 5.4.11. http://setiathome.berkeley.edu/result.php?resultid=418613884 Dublin, California Team: SETI.USA ![]() |
![]() ![]() Send message Joined: 15 Apr 99 Posts: 1546 Credit: 3,438,823 RAC: 0 ![]() |
Hi Folks, sorry for the trouble, but finaly i found out what was going wrong. The new 5.7.5.32 fixed boinc client is on my page now. ![]() Join BOINC United now! |
zombie67 [MM] Send message Joined: 22 Apr 04 Posts: 758 Credit: 27,771,894 RAC: 0 ![]() |
Hi Folks, Worked like a charm. Question: For those machines that v1 worked on, do I need to upgrade them? In other words, is there the potential that something will fail over time? Or, since it installed without the issue, I have nothing to worry about? Thanks again! Dublin, California Team: SETI.USA ![]() |
![]() ![]() Send message Joined: 15 Apr 99 Posts: 1546 Credit: 3,438,823 RAC: 0 ![]() |
Hi Folks, There's nothing to worry about. You can safely use the previous version, if it allready worked for you. ![]() Join BOINC United now! |
Travis Giles ![]() Send message Joined: 23 Aug 02 Posts: 48 Credit: 30,171,171 RAC: 123 ![]() ![]() |
Thanks Crunch3r works just fine now that fixed all the problems I had. I reject your reality, and substitute my own. SETI@home classic workunits: 5,000 SETI@home classic CPU time: 15,019 hours ![]() |
![]() ![]() Send message Joined: 28 Apr 00 Posts: 579 Credit: 130,733 RAC: 0 ![]() |
Crunch3r et al, For those using VS 2005 you'll need to add some additional code to the S@H app which can be found here: http://boinc.berkeley.edu/app_debug_win.php#Common0xc000000d Microsoft redesigned a bunch of stuff to reduce buffer overflows and the like, one of the things they did was enforce parameter validation for the CRT functions used in writing portable applications. So when you see a 0xc000000d error code with an application that was compiled using VS2005, that is part of the problem. ----- Rom BOINC Development Team, U.C. Berkeley My Blog |
SETI User Send message Joined: 29 Jun 02 Posts: 369 Credit: 0 RAC: 0 ![]() |
Hello Folks, Hello Crunch3r, on which Boinc Version I must install your files... The 5.4.11 or the 5.7.5? ![]() Now I use V5.3.12.tx36 with 'among other things' "delete_overdue"... You know, if a deadline of a WU is like the date/time it'll be deleted. It's possible to add/change this feature to delete a WU, because Boinc see it'll not be finished and reported in the deadline? "process_priority" it's a good feature, or you think it's not needed? ![]() If good, you would like to add this feature too? Greetings! ![]() |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.