seems like a waste of everybody's time to run them then, Ya think?

Exit status	196 (0xc4) EXIT_DISK_LIMIT_EXCEEDED

Exit status 196 (0xc4) EXIT_DISK_LIMIT_EXCEEDED

Hello,

Please look at this computer:
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=573990&offset=0&show_names=0&state=6&appid=

Shouldn't he be "banned" for mass abort? Or at least banned from receiving GPU tasks?

201 (0xc9) EXIT_MISSING_COPROC

why dose WM do this?

that should be

why does WM do this?

To be honest, i have no experience using SLI and there are no other posts in this forum about using SLI for Milky Way.

A quick google search about BOINC and SLI brought me to this post
http://boinc.berkeley.edu/dev/forum_thread.php?id=3592

They said it is better to disable SLI when doing SETI work using CUDA
The same might be correct for Milky Way.

I have one of those. The fans are ineffective and don't do anything to lower the CPU temps, but it definitely gives good circulation around the pc.

I see version 7.2.39 is out now, you may want to try that too. BOTH are test versions, meaning they may work and they may not.

I've been running that for a while, and it works fine (after a brief hiccup with the 32-bit installer).The download link is http://boinc.berkeley.edu/download_all.php

But it won't change the behaviour of existing project applications or servers.

I see version 7.2.39 is out now, you may want to try that too. BOTH are test versions, meaning they may work and they may not.

Those 3+1 now validated :).

I am glad it is now working!!!!!

As for Windows uninstallers they have been notoriously BAD ever since Windows 2! It's the sharing files concept MS uses that causes the problems.

From the time differences I guess it was gpu (nonstop) vs. cpu (often suspended).
Since the WU is purged now, I can't verify.

Yeah it could be, I don't remember either.

Gee I don't get it, now I come home and I see boinc says one has crunched 33 hours remaining 7 hours (67%) and the other 33 hours remaining 14 hours (59%)... they are the same WUs than before, I can't see anything in boinc messages appart that the WU did resume at some point, on my account page I only see the same 2 WUs sent on the 09/01 !!

WTF ?

I think you need to figure out why it is 'suspending', since you said it is 'resuming' that means it was suspended earlier, figuring out why it suspended is the key I think.

Do you have a preference?

Access Violation (0xc0000005) at address 0x000007FEDB2A5E00 read attempt to address 0x00000010

If you want to try 7.2.37, here's a link where you can get it.

Is that nbody exe really singlethreaded?
I thought nbody was all mt plan class.

I am of the opinion that there is no inherent advantage to running MT tasks and plan to release only non-MT versions for the next n-body release.

I'm surprised that nobody posted a working app_info section for nbody. Hasn't anybody succeeded or does nobody care? ;)

<app_info> 
 
    <app>
        <name>milkyway_nbody</name>
    </app>

    <file_info>
        <name>milkyway_nbody_1.12_windows_x86_64__mt.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libgomp_64-1_nbody_1.10.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>pthreadGC2_64_nbody_1.10.dll</name>
        <executable/>
    </file_info>

    <app_version>
        <app_name>milkyway_nbody</app_name>
        <version_num>112</version_num>
        <platform>windows_x86_64</platform>
        <avg_ncpus>2.100000</avg_ncpus>
        <max_ncpus>2.100000</max_ncpus>
        <flops>13326025349.445996</flops>
        <plan_class>rh_mt_test</plan_class>
        <api_version>6.13.0</api_version>
        <cmdline>--nthreads 3</cmdline>
        <file_ref>
            <file_name>milkyway_nbody_1.12_windows_x86_64__mt.exe</file_name>
            <open_name>milkyway_nbody.exe</open_name>
            <main_program/>
            <copy_file/>
        </file_ref>
        <file_ref>
            <file_name>libgomp_64-1_nbody_1.10.dll</file_name>
            <open_name>libgomp_64-1.dll</open_name>
            <copy_file/>
        </file_ref>
        <file_ref>
            <file_name>pthreadGC2_64_nbody_1.10.dll</file_name>
            <open_name>pthreadGC2_64.dll</open_name>
            <copy_file/>
        </file_ref>
    </app_version>

</app_info> 

I don't take the lack of reply so far as a no. Maybe this can not be implemented on short notice. I would appreciate a reply, though, even a 'no'.

In the meantime I'm trying to load the cannon. Can somebody help me with a working N-Body Simulation section for an app_info.xml? The following app_info.xml was created based on the corresponding section in client_state.xml:...