• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Properly close SMP Client

GhosT15

GhosT15

Weaksauce
Joined
Jul 9, 2010
Messages
81
I've been looking around and googling, the most common answer is hitting the X on the console or using Control + C. I've tried these methods but I still get the "Core improperly shut down" message.

I use my i7 as my main computer so I need to occasionally reboot or shut down SMP for generally short periods of time. I'd like to be able to "Shut it down properly"

I noticed that because of this my i7 has been underperforming, using "basic loops". Recently joined up to help the hoards D, so any help to optimize this beast the better!

Anyone have and advice?


 
Last edited:
Good question, i just hit the X myself but usually have to redo the last couple of frams. i see no performance hit though.
 
lehmann said:
Good question, i just hit the X myself but usually have to redo the last couple of frams. i see no performance hit though.
Click to expand...

I noticed the frames for the same work unit (bigadv) went from 40-42/Frame to 55/Frame

Thats a huge difference, Between that and... Starcraft 2 I barely finished that BigAdv before the deadline

 
Use the -forceasm flag to stop the client from switching to standard loops after a shutdown. I have been doing this for a while now and have not had any problems. Ctrl-C is probably better than just closing the command shell. I don't know of any other ways to shut it down.
 
musky said:
Use the -forceasm flag to stop the client from switching to standard loops after a shutdown. I have been doing this for a while now and have not had any problems. Ctrl-C is probably better than just closing the command shell. I don't know of any other ways to shut it down.
Click to expand...

Oh, nice. Thanks! I'll give that a shot

 
Yup, just use ctrl-C. Unlike the Linux client, the Windows SMP client appears to be solid and will pick right back up from your last saved check point. For me, I have the checkpoint intervals set at 15 minutes.
 
Control+C
Ignore the message, it's a bug. (kinda?) :)
http://fahwiki.net/index.php/Common_Error_Messages#Previous_termination_of_core_was_improper
Previous termination of core was improper

This is more of a status message than an error message, but it is often viewed as a problem, so it will be added here. The message usually appears in the fahlog like this, with time stamps preceeding each line:

Code: 
Preparing to commence simulation 
- Ensuring status. Please wait. 
- Looking at optimizations... 
- Working with standard loops on this execution. 
- Previous termination of core was improper.

The most common symptom of this message, other than this message in the log, is the client folding much slower than normal. Without SSE optimizations, each percentage complete takes 2-3 times longer.

The most common cause of this message is when a client was not shut down gracefully (quit or ctrl+c), often occuring after a computer reset or hard boot or power outage. Restarting the client should correct the problem. Adding the -forceasm client switch is another option to prevent this from happening again.

Note: This status message is also seen in the SMP client log, but is only cosmetic as the SMP client has -forceasm hard-coded on and does not suffer the typical slowdown when not running client optimizations like the CPU client. Again, strictly a cosmetic issue and does not affect SMP client performance.
Click to expand...

(by cpu client I would assume they mean the classic uniprocessor client)
 
i just close the client.. never bothered to pay attention if there was an error message or not and never had a problem with the WU's.. but i also have mine set to checkpoint every 5 minutes so i dont lose all that much time on the WU..
 
You must log in or register to reply here.
Back
Top