Urgent folding problem 4threads?

Psycho Sonny

Psycho Sonny

Psycho Sonny

Caporegime
Joined
21 Jun 2006
Posts
38,367
15:15:28] - User name: Psycho_Sonny (Team 10)
[15:15:28] - User ID: 55BD6A2C08794574
[15:15:28] - Machine ID: 1
[15:15:28]

A potential conflict was detected:

Process 1920 is currently running and may also be a client with Mach. ID 1.
Program will now exit. Upon restart, this check will not be done --
you may wish to check that no client is currently running in
E:\FOLD 1 before restarting.


[15:15:28] - User name: Psycho_Sonny (Team 10)
[15:15:28] - User ID: 55BD6A2C08794574
[15:15:28] - Machine ID: 8
[15:15:28]
A potential conflict was detected:
Process 1936 is currently running and may also be a client with Mach. ID 8.
Program will now exit. Upon restart, this check will not be done --
you may wish to check that no client is currently running in
E:\FOLD 2 before restarting.


on both my threads i just got this message what do i do i have no idea about the folding software/console?
 
hmm I sometimes get that message when the client gets a bit confused - however I've never seen it on both cores at the same time

have you set it to run as a service? if so then you don't need to run the program manually as it starts when your computer does
 
I find right clicking on the my computer icon and selecting manage is an easyier way at getting too the services. (right click my computer - select manage - select services and applications - select services - right click on FAH@C: from services list - select properties - general tab - middle drop down selection box - select manual) exit out and reboot as billy said
 
I get this sometimes on my dual-core system even though the machine IDs are set correctly. Normally I just ignore it and start the services again. With any luck it will be fixed in v6 of the client!
 
Mattus said:
I get this sometimes on my dual-core system even though the machine IDs are set correctly. Normally I just ignore it and start the services again. With any luck it will be fixed in v6 of the client!
Click to expand...

I get this too, occaisonally. As Mattus said, I just stop and re-start the client/s that have an issue.

Dunc
 
clients were already stopped just restarted them and both are runing fine, so there is no apparent reason why this happened nor any solution to it, my comp was on for 5hrs before i noticed it, imagine if it had been running for days
 
Psycho Sonny said:
clients were already stopped just restarted them and both are runing fine, so there is no apparent reason why this happened nor any solution to it, my comp was on for 5hrs before i noticed it, imagine if it had been running for days
Click to expand...
Indeed it is a serious problem, shame it seems to random as I'm sure otherwise it would have been sorted out long ago
 
You must log in or register to reply here.
Back
Top Bottom