Originally Posted by slegrand

Subject says it all... I've just been given clearance to spill the beans...

But some caveats upfront..

1. Device 0 *must* be a supported CUDA and DirectX display device. It's a client quirk, and there is a workaround in development, but for now, those are the rules.

2. If all your GPUs are CUDA devices and they are all extended onto the desktop, you can just use -gpu n where n is the display device number and it will work just like an ATI client, which means follow the ATI multi-GPU FAQ and you'll be folding away.

3. In the event that 2 above is not the case, there is an override. Skip the -gpu flag and instead set the environment variable NV_FAH_DEVICE=n where n is the CUDA device you wish to use. You may find yourself also playing with CPU affinity here to get the right mix, but that's why we provided the power tools here so to speak. And also it provides a way for anyone with a tesla server/board out there to run F@H today.


3. set VAR=value is the proper syntax. If you put spaces in this, it won't work, i.e. set VAR = value is incorrect.

4. You need to set these variables either in a script that launches the client, or before you launch the client. Doing so after starting the client will have no effect until it is stopped and restarted.

I'm sure we're about to see some quirkiness, but that's what betas are all about... Have fun!

Originally Posted by friedrim A new Nvidia core (v1.07) has been posted at http://www.stanford.edu/~friedrim/FahCore_11.exe. Scott has added support for a new environment variable, NV_FAH_CPU_AFFINITY, that allows the user to directly set the processor affinity mask or set it to zero to disable all affinity settings. The CPU affinity is set with individual bits (it's a mask, not a CPU selector): setting NV_FAH_CPU_AFFINITY to 1 ==> CPU 0 2 ==> CPU 1 3 ==> CPU 0 and 1 4 ==> CPU 2 8 ==> CPU 3 15 ==> CPUs 0-3 etc If this variable is undefined, the default behavior is exhibited. A primer on Windows environment variables is at http://www.chem.gla.ac.uk/~louis/software/faq/q1.html. Please test it by manually deleting an existing core. Thanks.

Originally Posted by ENTERPRISE

I would reccomend opening task manager and closing the process ''IntelFanboy.exe''

Originally Posted by ENTERPRISE

"fold for the cause, fold for the people"

Originally Posted by Havegooda

So this means we can use SLI? Or run it on X2 cards?

~Gooda~

Originally Posted by markt

but I'll have to wait til a tutorial is out,cool though.