I told you yesterday that your problem was most likely that missing dll. I also told you in private why the reference is missing from the Lunatics installer, and that it definitely is going to be back in in the next one. As far as the <platform> tag is concerned IIRC it is required on 64 bit BOINC but not on 32 bit BOINC. A Lunatics 32 bit installer made app_info.xml therefore does not contain <platform> tags, but the 64 bit version will have them. [actually it has both <platform>windows_intelx86</platform> and <platform>windows_x86_64</platform> entries for full compatibility].
AP6_win_x86_SSE_CPU_r555.exe is the optimised AP app from the Lunatics team. Eric has access to sources, should he wish to make that stock. 6.01 is not 'fairly old' it is the original stock application. In any case with those i7 of yours you will probably find that ap_6.01r557_SSE2_331_AVX.exe is faster. Troubleshooting app_info.xml for SETI is best done on the SETI boards - takes about 5 minutes of crosschecking against a working sample to discover what's wrong. >________________________________ > Von: Charles Elliott <[email protected]> >An: 'Eric J Korpela' <[email protected]>; [email protected]; 'Rom >Walton' <[email protected]> >CC: [email protected] >Gesendet: 14:33 Freitag, 10.August 2012 >Betreff: Re: [boinc_dev] Error Messages > >Thank you all for your help. I finally found the problems after at least 6 >hours, most of it an all-nighter, of blood, sweat, and tears. The error for >task 05oc11al.8626.23417.12.14.170_1 ( - exit code -1073741515 (0xc0000135)) >message was caused by a missing DLL, but I copied that <app_version> . ></app_version> entry verbatim from an installer, so I don't understand how >it was wrong. The other problem, the flushing of all the Astropulse WUs, >was caused by the lack of a <platform>windows_intelx86</platform> line in >the <app_version> . entry for >astropulse_6.04_windows_intelx86__opencl_nvidia_100.exe. That entry too was >copied verbatim from the <app_info> file used before the switch to all >non-anonymous platform apps. Apparently 7.0.28 requires it, but the >previous version, possibly 7.0.25, assumed it. > > > >The reason no one could find the error messages in any results returned to >the Beta site is because I turned off the network before starting Boinc. > > > >Eric: Just to let you know I am using AP6_win_x86_SSE_CPU_r555.exe instead >of astropulse_6.01_windows_intelx86.exe to process the Astropulse CPU WUs >because the latter takes 30 hours to process a WU and the former only a few >hours, and I cannot believe you are really testing of >astropulse_6.01_windows_intelx86.exe, since it is fairly old. I will switch >back if asked, but not happily. > > > >Again, thanks to everyone for their help. > > > >Charles Elliott > > > >From: [email protected] [mailto:[email protected]] On Behalf Of Eric J >Korpela >Sent: Thursday, August 09, 2012 11:29 AM >To: Charles Elliott >Cc: [email protected] >Subject: Re: [boinc_dev] Error Messages > > > >I think there are some competing philosophies here. The message you list >isn't intended for the user to see or act upon, because it appears to be one >that you have enabled for debugging purposes. When not using app_info.xml, >there isn't anything a user can do about such errors. > > > >0xc0000135 one of the Windows error codes for "application failed to start" >which is essentially the same as "unrecoverable error". The BOINC client >doesn't know why and probably can't give you much help. In this case it's >probably because you there's something wrong with your app_info.xml. Or >maybe there's something wrong with one of the binaries or libraries. Check >the stderr files in the project and or slot directories for help, > > > > > >On Thu, Aug 9, 2012 at 8:08 AM, Charles Elliott <[email protected]> >wrote: > >On July 9, 2012 Eric Korpela promulgated this edit: > > > >" ><mailto:SETI@home%20Beta%20Test:%20Stop%20using%20anonymous%20platform%20in% >20Seti@home%20beta.> SETI@home Beta Test: Stop using anonymous platform in >Seti@home beta." > > > >Then on August 8, 2012 he promulgated: > > > >"SETI@home Beta Test: You may resume using anonymous platform applications ><mailto:SETI@home%20Beta%20Test:%20You%20may%20resume%20using%20anonymous%20 >platform%20applications%0bis%20SETI%20beta.> >is SETI beta." > > > > > >So, returned the app_info.xml file that had been in the >.\projects\setiweb.ssl.berkeley.edu_beta to that folder, made sure every >file mentioned in the app_info.xml file was in the >setiweb.ssl.berkeley.edu_beta directory, and restarted Boinc. Boinc erased >all (hundreds) of Astropulse work units and printed this message dozens of >times in the Event Log: > > > >09-Aug-2012 10:06:42 [SETI@home Beta Test] [sched_op] Reason: Unrecoverable >error for task 05oc11al.8626.23417.12.14.170_1 ( - exit code -1073741515 >(0xc0000135)) > > > >Two questions: > > > >1. Virtually every textbook ever written in Computer Science says that >error messages should tell the user exactly what is wrong and how to fix it. >All the above error message tells is how to convert -1073741515 decimal to >hexadecimal. Thanks, but I already knew that. What is the source of the >error exit code -1073741515 (0xc0000135) is referring to and how do I fix >it? > >2. Where is the documentation for app_info.xml? All a search on >"app_info.xml" returns is tens of thousands of questions about the file. > > > >Charles Elliott > > > >_______________________________________________ >boinc_dev mailing list >[email protected] >http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >To unsubscribe, visit the above URL and >(near bottom of page) enter your email address. > > > >_______________________________________________ >boinc_dev mailing list >[email protected] >http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >To unsubscribe, visit the above URL and >(near bottom of page) enter your email address. > > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
