I can't get SMP working again

edcentricedcentric near Milwaukee, Wisconsin Icrontian
edited October 2008 in Folding@Home
My C2D lappy is giving me fits. It will fold single core fine, but dual I get this:


Note: Please read the license agreement (Folding@home-Win32-x86.exe -license). F
urther
use of this software requires that you have read and accepted this agreement.

2 cores detected
If you see this twice, MPI is working
If you see this twice, MPI is working


--- Opening Log file [September 30 13:04:12 UTC]


# Windows SMP Console Edition #################################################
###############################################################################

Folding@Home Client Version 6.22 SMP Beta2

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files\Folding@Home Windows SMP Client V1.01\Folding@home-
Win32-x86.exe
Arguments: -deino -smp

[13:04:12] - Ask before connecting: No
[13:04:12] - User name: edcentric (Team 93)
[13:04:12] - User ID: 17C79BC26FC4EABC
[13:04:12] - Machine ID: 1
[13:04:12]
[13:04:12] Loaded queue successfully.
[13:04:12]
[13:04:12] + Processing work unit
[13:04:12] Work type a1 not eligible for variable processors
[13:04:12] Core required: FahCore_a1.exe
[13:04:12] Core found.
[13:04:12] Working on queue slot 01 [September 30 13:04:12 UTC]
[13:04:12] + Working ...
[13:04:13]
[13:04:13] *
*
[13:04:13] Folding@Home Gromacs SMP Core
[13:04:13] Version 1.76 (February 23, 2008)
[13:04:13]
[13:04:13] Preparing to commence simulation
[13:04:13] - Ensuring status. Please wait.
[13:04:30] - Looking at optimizations...
[13:04:30] - Working with standard loops on this execution.
[13:04:30] - Previous termination of core was improper.
[13:04:30] - Going to use standard loops.
[13:04:30] - Files status OK
[13:04:30]
[13:04:30] Folding@home Core Shutdown: MISSING_WORK_FILES
[13:04:30] Finalizing output
[13:06:34] CoreStatus = 1 (1)
[13:06:34] Client-core communications error: ERROR 0x1
[13:06:34] This is a sign of more serious problems, shutting down.

Comments

  • edcentricedcentric near Milwaukee, Wisconsin Icrontian
    edited October 2008
    Now it looks like it is trying to fold, but what is;
    Warning: long 1-4 interactions
    ????????????????????????????????
  • SnarkasmSnarkasm Madison, WI Icrontian
    edited October 2008
    Long 1-4 interactions by themselves don't really mean anything, it's just that the calculations are getting unstable. Now as for the reason they could be getting unstable...

    Have you done anything with your computer recently? Overclocked, moved it around, cut off airflow, anything like that? If not, I'd recommend uninstalling folding, wiping out every trace of it, and starting all over. It's a quirky program, not sure what else we can do.

    Mayhaps some other folks around here have a better idea than I.
  • _k_k P-Town, Texas Icrontian
    edited October 2008
    No, run two single core clients...?
  • edcentricedcentric near Milwaukee, Wisconsin Icrontian
    edited October 2008
    WHAT, and give up all of those points?????????
    I am trying to make 2,000,000 by the end of the week.
    I may have to punt.
    I'll keep trying.
  • _k_k P-Town, Texas Icrontian
    edited October 2008
    Your not trying to run this in a 64-bit are you? Most of the SMP clients just don't want to work with the SMP flag turned on with 64. And if you can't get SMP to run running those single cores is better than nothing right now......2,205 points and counting. Where is mas0n, he needs to pop in with an answer.

    Go buy a 8800gt clock it up and run it until saturday and then go return it, that will get you there.
  • SnarkasmSnarkasm Madison, WI Icrontian
    edited October 2008
    ^ That's just not correct, k. I've run the SMP clients very successfully in x64 environments, they just take a little tweaking - for instance, not installing them to the default C:\Program Files location.

    Still, a little bit more info like that WOULD be useful. Most of the time stability errors aren't caused by x64, though - it won't even usually start if there are x64 issues.
  • _k_k P-Town, Texas Icrontian
    edited October 2008
    mas0n and I both had the same kind of trouble when trying to get SMP working, just speaking from experience thats why I put the qualifier in there.
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited October 2008
    Ed, your thread title is "I can't get SMP working again," Italics mine. I infer that you had SMP working on the given machine previously. Is that correct?

    I've never run WinSMP on a dual-core CPU, only on quad-core, but, if I had the same problem on one of my quads, this is what I'd do:

    1. completely shut down the clients, including all FAH core processes
    2. in the FAH client, delete Queue, Work, and the core
    3. run Install.bat again
    4. restart the client

    If still a no-go:

    Check that you haven't changed your Windows user login options. Remember, in WinXP WinFAH SMP must be installed for user account that has a password set (but you can have WinXP log you in automatically with TweakUI)

    If still a no-go:

    1. uninstall FAH, using the Control Panel Ad/Remove Software...
    2. re-install
    3. run install.bat
    4. re-configure

    but, before we go any further, let us know if you have or have not run SMP before on the given computer
  • edcentricedcentric near Milwaukee, Wisconsin Icrontian
    edited October 2008
    Yes, I was running SMP on this machine for about a year.
    The OS is XP pro.
    I'll go back through the drill, I may have overlooked something.
    It worked fine through my password changes.
    I'll keep you posted.
    tks ed
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited October 2008
    Have you performed/experienced any networking changes lately with the laptop?

    You might also consider reinstalling .Net. You will need 2.0. I'd also install 2.0's security updates. 3.0 will work also, but is not required.
Sign In or Register to comment.