tpdooley
09-04-2003, 03:40 AM
While reading various team's folding forums, I've noticed numerous complaints about losing lots of points because the client stopped running and the files ended up corrupted. If they were on gen 175, they lost the chance to do the last 75 generations, because it all got erased and they started again. Some clients are corrupted and complaining about bad ram; yet a new client installed in a new directory on the machine run fine without the ram complaints.
On my team, we have a fellow that is switching DF machines in his farm to one of the @H projects whenever he finds a corrupted DF client.
Other than starting threads in the Bug forum here; saving the problem client directories (in case theres something you want to look at in the client directory); a full description of the hardware and OS with a list of any programs running; and a little more detail on what symptoms the system displayed.. other than that.. what would you like us to do, that will allow you to track down some of the sources for these problems and get the client back to the reliability we had near the end of Phase I? :)
On my team, we have a fellow that is switching DF machines in his farm to one of the @H projects whenever he finds a corrupted DF client.
Other than starting threads in the Bug forum here; saving the problem client directories (in case theres something you want to look at in the client directory); a full description of the hardware and OS with a list of any programs running; and a little more detail on what symptoms the system displayed.. other than that.. what would you like us to do, that will allow you to track down some of the sources for these problems and get the client back to the reliability we had near the end of Phase I? :)