graghgin!

after much frustration and fighting, ive managed to get F@H to use 100% of my CPU.

However, FAH log stats says it took one instance a little over 13 mins to do one frame (1/100), and the other instance doesnt appear to be doing anything.

Como1
Protein p1540_FSnat_305_GSsq
Protein Core Gromacs
Credit
Deadline
Current Frame 2 of 100 (98 left )
Time Per Frame 13 mins, 13 sec
Time Left 21 hours, 35 mins
Client Version
Core Version Version 1.70 (October 24, 2004) SSE Enabled
User Name netman86
Team Number Team 32
Est. PPD 0.00 (1.09 WUs)
Est. PPW 0.00 (7.63 WUs)

Como2
Protein p1140_RIBO_FSpeptide_EXT_nospring
Protein Core Gromacs
Credit
Deadline
Current Frame ? of 100 (NaN left )
Time Per Frame 0 mins
Time Left 0 mins
Client Version
Core Version Version 1.70 (October 24, 2004) SSE Enabled
User Name netman86
Team Number Team 32
Est. PPD ? (? WUs)
Est. PPW ? (? WUs)


Its driving me NUTS.

if i reboot, im afraid nne of this will work anymore, i swear its impossible to uninstall a windows service.

that second one is a 600 point WU and will take longer compared to the first WU

how can you tell? they are both 100 frames...


The first one is is at 39 mins, the second is at 4. At least its working

Yes, the 2nd one is a protein inside the ribosome that's more complicated, and therefore worth more points. Pretty much it will take you longer to do, but the points will make up for it.

Como said:

how can you tell? they are both 100 frames...


The first one is is at 39 mins, the second is at 4. At least its working

Click to expand...

I used Electron Microscope III to manage all my folding machines...

I think its Fah log stats acting screwy. Look in the FAH directories for a file called FAHlog.txt and post the last 20 lines or so.

-Andy

em3 was screwy, this one is too...but it IS folding. the logs look fine, except i dont see why it should take this thing 16 mins to a frame....oh well.

It's fine, it all depends on the WU. My 1800+ @2205 MHz is taking 38min a frame on a p1134_RIBO_FSpeptide_EXT.

-Andy