Message boards :
Number crunching :
App_info error = Critical ???
Message board moderation
Author | Message |
---|---|
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
5/16/2013 1:54:01 PM | SETI@home | Found app_info.xml; using anonymous platform 5/16/2013 1:54:01 PM | SETI@home | [error] State file error: duplicate app version: astropulse_v6 windows_intelx86 601 5/16/2013 1:54:01 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID not assigned yet; resource share 100 5/16/2013 1:54:01 PM | | No general preferences found - using defaults I can send a copy of the file if needed. |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Post the app_info, and i'll correct it for you. Claggy |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
Post the app_info, and i'll correct it for you. - <app_info> - <app> <name>setiathome_enhanced</name> </app> - <file_info> <name>AK_v8b2_win_SSE3_AMD.exe</name> <executable /> </file_info> - <app_version> <app_name>setiathome_enhanced</app_name> <version_num>603</version_num> - <file_ref> <file_name>AK_v8b2_win_SSE3_AMD.exe</file_name> <main_program /> </file_ref> </app_version> - <app> <name>astropulse_v6</name> </app> - <file_info> <name>AP6_win_x86_SSE_CPU_r1797.exe</name> <executable /> </file_info> - <file_info> <name>libfftw3f-3.dll</name> <executable /> </file_info> - <file_info> <name>ap_cmdline_win_x86_SSE_CPU.txt</name> </file_info> - <app_version> <app_name>astropulse_v6</app_name> <version_num>601</version_num> <platform>windows_intelx86</platform> <cmdline /> - <file_ref> <file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name> <main_program /> </file_ref> - <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> - <file_ref> <file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name> <open_name>ap_cmdline.txt</open_name> </file_ref> </app_version> - <app> <name>astropulse_v6</name> </app> - <file_info> <name>ap_6.01r557_SSE2_331_AVX.exe</name> <executable /> </file_info> - <app_version> <app_name>astropulse_v6</app_name> <version_num>601</version_num> - <file_ref> <file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name> <main_program /> </file_ref> </app_version> - <app> <name>astropulse_v505</name> </app> - <app_version> <app_name>astropulse_v505</app_name> <version_num>505</version_num> <cmdline>-v505</cmdline> - <file_ref> <file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name> <main_program /> </file_ref> </app_version> - <app> <name>setiathome_enhanced</name> </app> - <file_info> <name>Lunatics_x41zc_win32_cuda42.exe</name> <executable /> </file_info> - <file_info> <name>cudart32_42_9.dll</name> <executable /> </file_info> - <file_info> <name>cufft32_42_9.dll</name> <executable /> </file_info> - <file_info> <name>mbcuda.cfg</name> </file_info> - <app_version> <app_name>setiathome_enhanced</app_name> <version_num>610</version_num> <plan_class>cuda_fermi</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> - <coproc> <type>CUDA</type> <count>1</count> </coproc> - <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program /> </file_ref> - <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> - <file_ref> <file_name>cufft32_42_9.dll</file_name> </file_ref> - <file_ref> <file_name>mbcuda.cfg</file_name> </file_ref> </app_version> - <app_version> <app_name>setiathome_enhanced</app_name> <version_num>609</version_num> <plan_class>cuda23</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> - <coproc> <type>CUDA</type> <count>1</count> </coproc> - <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program /> </file_ref> - <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> - <file_ref> <file_name>cufft32_42_9.dll</file_name> </file_ref> - <file_ref> <file_name>mbcuda.cfg</file_name> </file_ref> </app_version> - <app_version> <app_name>setiathome_enhanced</app_name> <version_num>608</version_num> <plan_class>cuda</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> - <coproc> <type>CUDA</type> <count>1</count> </coproc> - <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program /> </file_ref> - <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> - <file_ref> <file_name>cufft32_42_9.dll</file_name> </file_ref> - <file_ref> <file_name>mbcuda.cfg</file_name> </file_ref> </app_version> </app_info> |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Open the app_info with Notepad (you should be able to right click and choose edit), and repost from that please. (Boinc .xml files aren't real .xml files, but text files) Claggy |
Mike Davis Send message Joined: 17 May 99 Posts: 240 Credit: 5,402,361 RAC: 0 |
Change the first version listed as 601 to something like 604 and you should be ok |
john3760 Send message Joined: 9 Feb 11 Posts: 334 Credit: 3,400,979 RAC: 0 |
You would still be left with two CPU apps,I had the same problem and had a couple of goes at deleting before I got mine to work.( in the process I became " brighter than an idiot" from " unadvanced user" ;) The read me files do state advanced user, but reading them properly and a bit of advice from people on this message board ( thanks again, you know who you are !!! ) and most people should be able to do it. John3760 |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
Change the first version listed as 601 to something like 604 and you should be ok That seemed to remove the error listing , gonna try it out and hope all is ok. Thanks ! EDIT: I'm only running a few WU's until I see how it is going to do. |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
Open the app_info with Notepad (you should be able to right click and choose edit), and repost from that please. (Boinc .xml files aren't real .xml files, but text files) If you can mark the start and stop area in the file . so I can learn how to do it myself ,like this: *( cut) <name>ap_cmdline_win_x86_SSE_CPU.txt</name> </file_info> - <app_version> <app_name>astropulse_v6</app_name> <version_num>601</version_num> <platform>windows_intelx86</platform> <cmdline /> - <file_ref> * (end cut) Or something like that... LOL |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Open the app_info with Notepad (you should be able to right click and choose edit), and repost from that please. (Boinc .xml files aren't real .xml files, but text files) You're corrupted the app_info by opening it in the wrong program. Claggy |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
Open the app_info with Notepad (you should be able to right click and choose edit), and repost from that please. (Boinc .xml files aren't real .xml files, but text files) I opened it with notepad... this is just a copy of the file . |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Open the app_info with Notepad (you should be able to right click and choose edit), and repost from that please. (Boinc .xml files aren't real .xml files, but text files) It's been opened and saved by another program first, it's laced with extra - entries, and extra spaces, dubed by Richard Haselgrove as Claggy's Space almost 5 years ago: Optimized Astropulse for Windows issues, install, questions Claggy |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
Open the app_info with Notepad (you should be able to right click and choose edit), and repost from that please. (Boinc .xml files aren't real .xml files, but text files) Ok , what do I do ? Uninstall and reinstall ? |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Ok , what do I do ? Just shut down Boinc, make sure you only have the *.aistub files for the apps you want to run in your project directory, then run aimerge.cmd (If you're used the Lunatics installer before, you'll have that program in your project directory), then post the generated app_info here. Claggy |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
Ok , what do I do ? Ok what I did was unzip them ( all the files ) into the S@H project dir , and then ran the aimerge , did I mess that up? I bet I did... :( Well I can always re-do it all. |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Ok , what do I do ? You want to make sure you're only got the *.aistub's for the apps you want to install, they all have different names, for example from the Installer: AKv8b2_SSE3_AMD.aistub AKv8b2_x64_SSE3.aistub AKv8b2_x64_SSE41.aistub AKv8b2_x64_SSSE3x.aistub APATI.aistub APAVX.aistub APHybrid.aistub APSSE.aistub MBATI.aistub MBATI_HD5.aistub MBCuda.aistub Standalone apps: AP6_win_x86_SSE_CPU.aistub (AP r1797) MBCuda.aistub (x41zc) etc You just want one .aistub for the CPU app, one for the Cuda app, one for the CPU AP app, and one for the OpenCL AP app (If you want to run it) Claggy |
Wiggo Send message Joined: 24 Jan 00 Posts: 34744 Credit: 261,360,520 RAC: 489 |
Just shut down Boinc, make sure you only have the *.aistub files for the apps you want to run in your project directory, then run aimerge.cmd (If you're used the Lunatics installer before, you'll have that program in your project directory), Now I have a question for you Claggy. If all the new app files have been extracted to the proper directory you then open the run command and navigate to the aimerge.cmd and run it it'll make the necessary app_info modifications? Sorry if I'm a bit slow but I've never seem this part properly explained for those of us who are a little mentally challenged. I've just relied on stumbling through with notepad. Cheers. |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
Ok , what do I do ? Here is the names of the files it shows in the project dir. AP6_win_x86_SSE_CPU.aistub MBCuda.aistub APAVX.aistub AKv8b2_SSE3_AMD.aistub I ran aimerge again and I'll post a copy of the app_info file in a sec. |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
<app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>AK_v8b2_win_SSE3_AMD.exe</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>603</version_num> <file_ref> <file_name>AK_v8b2_win_SSE3_AMD.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>astropulse_v6</name> </app> <file_info> <name>AP6_win_x86_SSE_CPU_r1797.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3.dll</name> <executable/> </file_info> <file_info> <name>ap_cmdline_win_x86_SSE_CPU.txt</name> </file_info> <app_version> <app_name>astropulse_v6</app_name> <version_num>601</version_num> <platform>windows_intelx86</platform> <cmdline></cmdline> <file_ref> <file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name> <open_name>ap_cmdline.txt</open_name> </file_ref> </app_version> <app> <name>astropulse_v6</name> </app> <file_info> <name>ap_6.01r557_SSE2_331_AVX.exe</name> <executable/> </file_info> <app_version> <app_name>astropulse_v6</app_name> <version_num>601</version_num> <file_ref> <file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>astropulse_v505</name> </app> <app_version> <app_name>astropulse_v505</app_name> <version_num>505</version_num> <cmdline>-v505</cmdline> <file_ref> <file_name>ap_6.01r557_SSE2_331_AVX.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>Lunatics_x41zc_win32_cuda42.exe</name> <executable/> </file_info> <file_info> <name>cudart32_42_9.dll</name> <executable/> </file_info> <file_info> <name>cufft32_42_9.dll</name> <executable/> </file_info> <file_info> <name>mbcuda.cfg</name> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>610</version_num> <plan_class>cuda_fermi</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> <coproc> <type>CUDA</type> <count>1</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>mbcuda.cfg</file_name> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>609</version_num> <plan_class>cuda23</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> <coproc> <type>CUDA</type> <count>1</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>mbcuda.cfg</file_name> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>608</version_num> <plan_class>cuda</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> <coproc> <type>CUDA</type> <count>1</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>mbcuda.cfg</file_name> </file_ref> </app_version> </app_info> |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Here is the names of the files it shows in the project dir. You don't want APAVX.aistub and AP6_win_x86_SSE_CPU.aistub, the first one is for the AP r557 app, the 2nd one is for the AP r1797 app, both are for CPU AP apps. Claggy |
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
Here is the names of the files it shows in the project dir. Ok then if I delete the apavx stub and then run the aimerge , that will take care of the problem ? Is one for intel maybe? I need all amd no intel for this PC. Which one is best for this dual core amd processor |
©2024 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.