MMM
Results 1 to 25 of 57

Thread: FAH Setups

Hybrid View

  1. #1
    Xtremely High Voltage Sparky's Avatar
    Join Date
    Mar 2006
    Location
    Ohio, USA
    Posts
    16,040

    Arrow GPU directions!

    I got it jimwah

    Known working drivers are the Catalyst 6.5, 6.10, 6.11, 7.2, 7.3, 7.4, and 7.5. If one version doesn't seem to work for you, try another one of these. Don't bother with any others because they won't work at all, or they won't work as well.

    1. Download the GPU client console version from Stanford's site.

    2. Put the file where you want to run it, i.e. C:\FAHGPU

    3. Go to run and punch in "C:\FAHGPU\FAH5.91beta2-console.exe" -configonly (don't forget the quotes, and the filename will change with new versions)

    4. Here are the settings I used that seem to work well:
    > User name: your name
    > Team number: 36362
    > Launch as a service: no (this client does not support service mode)
    > Ask before getting work: no
    > Use IE settings: no
    > Use proxy: no
    > Allow 5MB or larger WU: yes (not sure if this affects anything)
    > Change advanced options: yes
    > Core priority: idle
    > CPU usage requested: 100
    > Disable optimized code: no
    > Pause if battery used: no (shouldn't matter, I don't know of any laptops with X1900's)
    > Interval between checkpoints: default
    > Memory to indicate: full amount
    > request WU's without deadlines: no
    > set -advmethods: no (again, not sure if that affects anything)
    > ignore deadline info: no
    > machine ID: normally 1, but anything different than any other clients

    5. Create a shortcut someplace - like on the desktop so you don't forget to start it - and put in "C:\FAHGPU\FAH5.91beta2-console.exe" -local as the command line.

    6. Run it!

    Notes:
    1. You MUST have a whole CPU core dedicated to the GPU. This is just a limitation at this point and there isn't much we can do about it. It is possible this may be reduced in the future but I'm not sure.
    2. If you start up a game it'll automatically kill the client, so you'll have to start it back up afterwards. I've noticed that sometimes it won't kill the client, if it doesn't you'll be able to tell because the game will run like crap
    3. My X1900XT with no tweaks would do a WU in about 14 hours, or about 565 PPD. The X1900GT will be slower because it has 12 fewer pixel shaders which is what the client uses to fold.

    The latest version of ATItool forces the card into 3D mode, which can help you complete WU's much faster. Using it got me down to about 12 hours for a WU, but the downside is the fan is running faster (more noise) and the card gets MUCH hotter. I used the fan control in ATItool to set my fan at 55% which was noisier but kept the card in the 70's, only a few degrees warmer than before. Of course you can use ATItool to overclock but MAKE CERTAIN that it is FULLY STABLE otherwise you'll end up with system crashes, EUE's, or both.
    Last edited by Sparky; 06-23-2007 at 11:04 AM.
    The Cardboard Master
    Crunch with us, the XS WCG team
    Intel Core i7 2600k @ 4.5GHz, 16GB DDR3-1600, Radeon 7950 @ 1000/1250, Win 10 Pro x64

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •