Forum > Windows
help i guess.
(1/1)
Fubar:
I put together a new system.
i7 920
evga x58 sli
raid 0 - corsair p128
12gb corsair trip chan ddr3 c8 mem
windows 7 6.1 7100 build
When I went to transfer my boinc stuff, it went fine. After weeks I decided to use an optimized version. However when I installed this app it wipe everything; every single time. I stopped and exited making it quit the work units. I proceeded to install, it went fine. I started up boinc and it gave a page of errors cannot find work for windows 603x86. Smart as i am i made a backup, so i restored it and bam it work; so i tried to install again. Everything gets wiped. The program asks me to assign an id or project whenever it gets restarted after lunatics install.
So does anyone know whats going on?
Raistmer:
check app_info.xml in SETI project directory in boinc data folder.
Is it ok?
And try to install BOINC not in default place (at least BOINC data folder) but in something like C:\BOINCdata or even better D:\BOINCdata..
Windows sometimes too smart and deny access to needed folders if it thinks it's system location. So better to avoid places known to Windows, especially in new (more "user friendly and smart") versions...
Fubar:
C:\ProgramData\BOINC\projects\setiathome.berkeley.edu
app_info.xml:
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8b_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8b_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
Josef W. Segur:
That app_info.xml is OK. The problem comes about because the project doesn't have separate applications for the windows_x86_64 platform, so the work downloaded for stock uses an <alt_platform> mechanism to enable use of the windows_intelx86 applications. The <alt_platform> mechanism isn't available in app_info.xml so the work is deleted because you no longer have windows_intelx86 applications.
It is possible to put <platform>windows_intelx86</platform> entries in app_info.xml for each app_version, but that causes other problems under some circumstances. We've thought about doubling the number of app_version sections to have both platforms listed for each, but that's untested.
I think I'd edit BOINC's client_state.xml if I were making that transition. First I'd do the optimized install, then change the platform for each <result> listed in client_state.xml to windows_x86_64 before starting BOINC again. Since you are smart enough to make a backup, you might try this approach.
Joe
Fubar:
Thank you I will try tonight.
What would that be: (i only took out flops in the edit)<result>
<name>31jl09ad.17185.10701.4.10.52_0</name>
<final_cpu_time>4508.094000</final_cpu_time>
<final_elapsed_time>4449.757933</final_elapsed_time>
<exit_status>0</exit_status>
<state>2</state>
<platform>windows_intelx86_64</platform>
<version_num>603</version_num>
<fpops_cumulative>32607330000000.000000</fpops_cumulative>
<wu_name>31jl09ad.17185.10701.4.10.52</wu_name>
<report_deadline>1252781903.000000</report_deadline>
<file_ref>
<file_name>31jl09ad.17185.10701.4.10.52_0_0</file_name>
<open_name>result.sah</open_name>
</file_ref>
</result>
And I just change the platform?
THANK YOU it now works.
Navigation
[0] Message Index
Go to full version