Duh...

[kaltag]

I've had my new 1700 machine folding for a few days now and I was wondering why it had only finished WUs and then I remember that I didn't turn on the -advmethods and -forceasm flags. So now they're on and frame times have dropped nicely :D. Pardon my idiocy.

P.S. With this new machine up I may just break the top 100 :D

[Turd Furguson]

LOL!!

[emericanchaos]

oh yeah.... good idea. i should check mine too.

[Rottys-R-Us]

That's what you get for trying to go h20, LOL :)

[kaltag]

Oops I didn't notice I forgot the 6 before WUs in my post too...LOL my memory is absolutely horrible!!!!

[MLMIB]

okay, now I feel like an idiot, what are those?

[MLMIB]

the -advmethods and -forceasm flags that is

[kaltag]

-advmethods=requests only Gromac WUs although you won't always get them but usually do.

-forceasm=forces the folding core to use SSE instructions instead of the slower 3DNOW! which will help increase production.

Hope that helps ya :D

[MLMIB]

but where do I do this? I have the graphical client....

[Tismedt]

You need to switch to the console client. Check the FAQ sticky for exact instructions

[kaltag]

Actually the arguments work for the graphical client as well. which is what the 1700 is running right now. What you have to do is go to the start menu then locate the F@H link in startup. Right click on the link and that will bring up it's properties. Where it says target just put a space then -advmethods space -forcasm after the directory that's already there and then apply and save. It should look like this: C:\Folding@Home\winFAH.exe -forceasm -advmethods . Your directory may be different though.