PDA

View Full Version : client troubles

Daniel, Laura, and Nora
10th May 2003, 16:13
Anyone else having trouble with the client lately? I find that it seems to stop processing after submitting a batch of work. It remains among the active processes and can't be shut down but its not using CPU time. What happened to the foolproof, rock-solid DF I once knew? Its not the protein and not the client so I suspect there must be a server problem. Mike, any inside news?
ohms18k
10th May 2003, 16:23
Yes I had one of those yesterday D, just froze up doing nothing.
Hans Arne Iversen
10th May 2003, 16:26
I haven't had any problems with it, but there is a thred about it here (http://www.free-dc.org/forum/showthread.php?s=&threadid=3019)
BennyRop
10th May 2003, 16:29
One of the recent patches from M$ is said to cause problems with WinXP. I had one of my win98se beta clients corrupt itself after the last patch I loaded onto that machine. Post with enough details - and we might get Howard to talk to M$ about this.
ohms18k
10th May 2003, 16:43
Originally posted by BennyRop
One of the recent patches from M$ is said to cause problems with WinXP. I had one of my win98se beta clients corrupt itself after the last patch I loaded onto that machine. Post with enough details - and we might get Howard to talk to M$ about this.

It was the client on my server running W2k that froze. The client on my XP machine has never froze.
Daniel, Laura, and Nora
10th May 2003, 17:08
Its my NT clients that are freezing. No OS updates on those boxes whatsoever since sp6.
phil
11th May 2003, 06:49
Run the clients with the -if switch which will run them off network. To upload, stop the client and use a shortcut with the upload switch (I forget what it is). After upload, restart the client with the -if switch.

The problem is indeed contacting and uploading to the server. By doing it the above way, when the client can't upload the work it will just quit instead of "hanging".
MikeTimbers
11th May 2003, 07:24
Yeah, I have seen this a lot. There seems no rhyme nor reason for it as within a set of identical machines some work perfectly and some freeze at an upload point. As Phil says, run off-line and then upload from time to time. I have also found that running not as a service is more reliable than the service.