Arctic Feezer 7x
Results 1 to 1 of 1

Thread: Follow up to the sticky above.

  1. #1
    POC.Folding Member

    reQuiem is offline

    Last Online
    15-09-2011 @ 07:22
    Join Date
    Mar 2008
    CPU: Q6600
    M/B: EVGA 790i
    RAM: 2 Gigabytes OCZ 1800mhz.
    GPU: 9800GX2 Quad Sli 2Gb (650/1025/1620)
    • reQuiem's Full Spec's
      • Case:
      • Kandalf LCS
      • PSU:
      • Thermaltake ToughPower 1000W
      • Cooling:
      • LCS - Cpu only at mo / GPU's soon / Mosfits soon / Northbridge soon. XSPC Dual drive clear resevoir with built-in pump 750lph. Standard CPU block. Planning a dual loop water cooling system.
      • Sound:
      • Xonar D2X
      • OS:
      • Vista SP1 & XP SP2
    Thanked 1 Time in 1 Post
    Points: 3,048, Level: 15
    Points: 3,048, Level: 15
    Level completed: 99%,
    Points required for next Level: 2
    Level completed: 99%, Points required for next Level: 2
    Overall activity: 5.0%
    Overall activity: 5.0%

    Default Follow up to the sticky above.

    These are advanced command line switches guys and should only be used if you understand the F@H client.

    One thing I must say though is that those of us who are running multiple processes need to use the second too last command line switch as with-out it the multiple clients we run use the registry information and can sometimes conflict with each other I have noticed some of my WU failing with-out any prior cause.

    Console Client Configuration Options

    -config Allows users to change their configuration information. This includes user & team names (reflected in the stats), whether or not to ask before a network connection is made to fetch/send work, set up proxy servers, preferred work unit type (Folding/Genome), process priority, CPU usage requested (5-100%), whether or not to use assembly loops, whether or not to use deadline information, and Machine ID changes.

    -configonly Same as above, but quit following configuration instead of beginning work.

    -delete x Delete item #x from work queue. This option should only be used if there is a serious error with the current unit that the client does not automatically recover from (e.g. crash-inducing). This should not normally happen, and if it does, we would be grateful if you could send us the FAHlog.txt file from the unit that causes the error.

    -license Displays the end-user license agreement -queueinfo Get information on queued work units. Includes for each unit the status (READY/FINISHED/EMPTY), unit type (Folding/Genome), originating server, and date when the unit was received (local time in GMT), as well as deadline if the server sent that information.

    -send x Send result #x back to server. Exits after trying to send unit (successfully or unsuccessfully). Use "-send all" to send all results outstanding. If unit x is not a completed work unit then the client exits without doing anything.

    -verbosity x Sets the output level, from 1 to 9 (max). The default is 3. This option should be used if the user wishes to see more detailed client output, particularly useful if there is a problem which needs to be reported to the F@H client development team.

    -oneunit Instruct the client to quit following the completion of one work unit. -forceasm Instruct the core to use SSE/3DNow assembly instructions if possible, even if it has previously made the determination that the machine may not be handling this well.

    -advmethods Request to be assigned work units from new projects, before they are broadly released to the rest of Folding@home. As among the first to try out new advanced simulations, you may wish to post any observations (positive or negative), questions, or issues at the user Forum.

    -local Use configuration files from local directory. This option has no meaning on Linux, but is vital on Windows and Macintosh for running multiple clients on a machine. It instructs the client to read its config information from the client.cfg file in the current directory rather than, on Windows, from the installation directory specified in the registry, or, on Macintosh, the Library/Folding@home directory. Information such as the user name, team name, proxy information, machine ID are maintained in the client.cfg file. The flag ensures that work does not conflict. Use "-local" only if you are planning on running more than one instance of Folding@Home on the same machine (this is only useful if you are running on a multi-processor machine). Create as many directories as there are processors on the machine, copy the exe files and client.cfg file into each of these directories, run "FAH3Console -local -config" on each and specify unique machine IDs for each directory (under the Advanced Settings option). From then onwards you may run each copy by switching to its directory and running with the -local flag.

    -help Print out the command line flags available and then exit.

    Please use with due care, if your not sure don't use them if you happen to use them and get undesired effects PM me and I'll endevour to help you fix it.
    Last edited by reQuiem; 13-06-2008 at 19:15.

Remove Ads

Sponsored Links

Posting Permissions

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

Similar Threads

  1. FluidMark released, more PhysX benchmarks to follow
    By News Team in forum Hardware News
    Replies: 2
    Last Post: 13-08-2008, 19:22
  2. First dual-core Celeron shipping, more to follow
    By News Team in forum Hardware News
    Replies: 0
    Last Post: 23-01-2008, 00:17

Search tags for this page

There are currently no search tags.
Click on a term to search for related topics.

Tags for this Thread