I think my Think hangs

[Jorden]

24 hours on and still at 38%? Is this anything in the direction of normal?

Jord.

[Rattledagger]

Well, if the time is counting as normal, and conformers slowly crawls upward, you're not hung. If you're running alongside genome@home, this is normal.

[windigo]

Oh my thats long... have you been restarting your agent because it reverts back to the last protien you started so if the protien has like 100,000 conformers and you switch it off at 99,999 then it has to do those again.
The longest is was stuck at a certain percentage was 17 hours but 24 thats way to much it seems hopefully youve got the cure right there bub

------------------
MSI K7TPro2 Duron 750@900
512Ram G400DH32mb
Pioneer SCSI 16xDVD
msn messenger id: mkanashta

[windigo]

Ratlledagger is right think dont like to share with other clients on of the problems with it I hear

------------------
MSI K7TPro2 Duron 750@900
512Ram G400DH32mb
Pioneer SCSI 16xDVD
msn messenger id: mkanashta

[Jorden]

11 hours on, clock still ticking (total time now at 50+ hours), and I'm still at 38%, even though it ran all by itself since my last post.

I'll let it run for another 24 hours, then it's going off!

Jord.

[Jorden]

Okay, at 62 hours something I killed the client, deleted a couple of the files in the directory (mostly the .dat and .ud files) and let it download a new unit. That's been 10 hours ago, and it's now at 37%.

Let me keep my fingers crossed

Jord.

[windigo]

LOL

btw i installed the genome thing and man it really does slow down the cancer client...but not 62 hours

------------------
MSI K7TPro2 Duron 750@900
512Ram G400DH32mb
Pioneer SCSI 16xDVD
msn messenger id: mkanashta

[Rattledagger]

windigo, I'm not currently running genome, but seti@home, and THINK is currently on 35% and 251 hours.


Yes, Jorden, I'm heading on over for the new 0.98 now...

[Jorden]

Okay, that was my testing of Think. It's been just deleted off of my PC, as it caused a crash while online, it opened up about 100 error messages in my memory and upon a reboot decided to start not from 55% it was at (and about 16 hours crunching), but from 0% and 0 hours...

Think, you are voted the weakest link... Goodbye!!

Jord.

[windigo]

hmm ive been having some of the same trouble with mine also (crashed and restarted at 0%)
i wonder waz goin on?

------------------
MSI K7TPro2 Duron 750@900
512Ram G400DH32mb
Pioneer SCSI 16xDVD
msn messenger id: mkanashta

[Rattledagger]

Well, if you're running win9x the crash can be due to resource-leakage. Coupled with fat a crash can mess up the file-system, leading to the client either re-starting, or downloading a new wu and dumps the old.