This unit is messing with me ! Even if I change my ID, I'm getthing that unit right after the new one! I did take a break trying to let that unit expire, but I'm guessing it take a bit more than a month.
[EDIT: clarification]
Search found 4 matches
- Wed Jan 05, 2011 7:07 pm
- Forum: Issues with a specific WU
- Topic: Project: 6505 (Run 2, Clone 57, Gen 85) [Updated]
- Replies: 8
- Views: 1344
- Mon Dec 06, 2010 9:07 pm
- Forum: Issues with a specific WU
- Topic: Project: 6505 (Run 2, Clone 57, Gen 85) [Updated]
- Replies: 8
- Views: 1344
Re: Project: 6505 (Run 2, Clone 57, Gen 85)
My bad. I forgot to delete the files BEFORE changing the machine ID... And yes, that worked.
- Sat Dec 04, 2010 5:20 am
- Forum: Issues with a specific WU
- Topic: Project: 6505 (Run 2, Clone 57, Gen 85) [Updated]
- Replies: 8
- Views: 1344
Re: Project: 6505 (Run 2, Clone 57, Gen 85)
I did try, with no luck.
- Fri Dec 03, 2010 4:27 am
- Forum: Issues with a specific WU
- Topic: Project: 6505 (Run 2, Clone 57, Gen 85) [Updated]
- Replies: 8
- Views: 1344
Project: 6505 (Run 2, Clone 57, Gen 85) [Updated]
[04:25:18] Project: 6505 (Run 2, Clone 57, Gen 85) [04:25:18] [04:25:18] Assembly optimizations on if available. [04:25:18] Entering M.D. [04:25:24] Gromacs error. [04:25:24] [04:25:24] Folding@home Core Shutdown: UNKNOWN_ERROR [04:25:28] CoreStatus = 79 (121) [04:25:28] Client-core communications ...