600 Pointer!!!!!!!!!!!!!!

[SmokeRngs]

I guess it's like Hito said, if there was an error shutting down the core previously it turns SSE boost off.
Looking at the logs I see this is what matters:

[23:30:49] Preparing to commence simulation
[23:30:49] - Ensuring status. Please wait.
[23:31:06] - Looking at optimizations...
[23:31:06] - Working with standard loops on this execution.
[23:31:06] - Previous termination of core was improper.
[23:31:06] - Going to use standard loops.
[23:31:06] - Files status OK
[23:31:09] - Expanded 2966018 -> 16166417 (decompressed 545.0 percent)
[23:31:11] 
[23:31:11] Project: 1141 (Run 45, Clone 22, Gen 8)
[23:31:11] 
[23:31:24] Entering M.D.
[23:31:48] (Starting from checkpoint)
[23:31:48] Protein: p1141_RIBO_FSpeptide_HEL_nospring
[23:31:48] 
[23:31:48] Writing local files
[23:31:48] Completed 118785 out of 250000 steps  (48)
[00:22:43] Writing local files

VS.

[11:36:19] Preparing to commence simulation
[11:36:19] - Looking at optimizations...
[11:36:19] - Files status OK
[11:36:24] - Expanded 2966018 -> 16166417 (decompressed 545.0 percent)
[11:36:25] 
[11:36:25] Project: 1141 (Run 45, Clone 22, Gen 8)
[11:36:25] 
[11:36:30] Assembly optimizations on if available.
[11:36:30] Entering M.D.
[11:36:53] (Starting from checkpoint)
[11:36:53] Protein: p1141_RIBO_FSpeptide_HEL_nospring
[11:36:53] 
[11:36:54] Writing local files
[11:36:54] Completed 135000 out of 250000 steps  (54)
[11:36:59] Extra SSE boost OK.

The second one is the same thing Hito posted, I'm just showing the difference for anyone else who might have had this problem.
If it sees there was an error the last time it ran, it uses standard loops, which I guess turns off SSE boost.
So -forceasm doesn't actually force it to use SSE, only if there wasn't an error previously.
At least now I know, "And knowing is half the battle."

Actually, that is exactly what -forceasm is for. If you are running the clients as a service, you will need to edit the registry and change the registry entry for them to use the -forceasm switch. I had an occasional problem because of this before I added the -forceasm switch to the registry entry.

 

[Hito Bahadur]

I think that what -forceasm really does is bypass the check that will lead to turning off SSE boosts. Same thing really by technically different.

 

[rottweiler]

nope, I have edited the registry, both ImagePath entries look like this:
E:\Files\Folding\CPU1\FAH502-Console.exe -svcstart -advmethod -forceasm

except the other one has CPU2.
Is there another entry to edit?

 

[Kvothe]

That's what you need to have. Sounds like you have a handle on it, so now, should something go south (power outage, etc) SSE should be turned on each time the client restarts. As Hito stated, it should be on for just about all of the WU's except the Tinkers.

 

[rottweiler]

I understand that it should always be on, but I have had my registry edited like that for a while now.
So it did not prevent the check from happening and turning off SSE boost.
Has anyone else encountered this problem?
Maybe I should start a new thread as this was not the original intent of this one.

 

[psychosonik]

OMG... some people get way too into this stuff.

download exe
double click
that's it

points != getting chicks

You can also do it manually. Take the amount of time it takes to complete one frame: (For this example we will say 12 minutes)

60min/hour / 12min/Frame = 5 Frames/hour

Find out the number of frames and the total points of your Protein (We'll use P972 for this example):
http://vspx27.stanford.edu/psummary.html

P972: Double Gromacs, 122 Points/WU, 100 Frames/WU

122 Points/WU / 100 Frames/WU = 1.2 Points/Frame

5 Frames/Hour * 1.2 Points/Frame = 6 Points/Hour (PpH)

6 Points/Hour * 24 Hour/Day = 144 Points/Day (PpD)