|
|||||||
|
OFFICIAL: SlickDeals.net Folding@Home Team Getting Started, Discussion, Bragging, and Community Support Thread
moved to wikimod: please remove this post Last edited by darksarcasm; 11-20-2010 at 11:51 AM.. |
| 11-04-2006, 04:32 PM | |
|
|
[onlinehome.us]
[onlinehome.us]
I always recommend manually scanning downloaded files for viruses before running them. Most antivirus software offer the option to scan specific files in the right-click menu. Right-click the downloaded file and select scan for viruses (your antivirus software may not have this feature).
[onlinehome.us]
if you are prompted by your software firewall to grant access (or unblock) the F@H client, select the option that allows the program to access the internet.


if the F@H system tray icon does not appear when you turn your computer on (make sure you click the little arrow to show all the icons), then the program is not running, and you will need to manually add a shortcut to your startup folder. This will most likely be the case if you downloaded the beta graphical client, which does not appear to go through an installation. This will work for Windows 2000/XP, not sure about Vista: open "My Computer" and browse to the EXE file, right-click the EXE file, select "Create Shortcut", right-click over the shortcut, select Cut. Go to Start, Programs, right-click over the "Startup" folder, select Paste.
[fah]Redsolar[/fah]
[fahuid]214548[/fahuid]
-config Use this option to access the console client setup options, make changes as needed, and then start folding. Supported in client versions v3.x, 4.x, 5.x. -configonly Use this option to access the console client setup options, make changes as needed, and then exit the client. Supported in client versions v3.x, 4.x, 5.x. -delete x Deletes the work unit from position x in the queue. Positions are 0-9. This switch is usually not necessary, and is only to be used as a last resort when the only way to continue folding is to delete a work unit. Supported in client versions v3.x, 4.x, 5.x. -license Displays the EULA (end user license agreement). This switch does not work well added to a Windows shortcut. Run it from a Command Prompt. Supported in client versions v3.x, 4.x, 5.x. -queueinfo Instructs the client to write information to the fahlog.txt file about any work units in the queue, and then exit. Positions are 0-9. Supported in client versions v3.x, 4.x, 5.x. In addition to the usual client startup text, this switch displays information for each work unit in the queue. Data fields include the status (READY/FINISHED/EMPTY), originating server IP and port, date when the unit was received (local time in GMT), deadline date if the server sent that information, and WU Tag info. -send x Attempts to send the individual work unit in position x back to the project work servers then exit the client. Positions are 0-9 or "all" to "-send all". This switch is not commonly used as each time the client is started, it attempts to upload all completed work units to the project servers. This switch is generally useful for sending leftover results files prior to client removal, or when Sneakernetting. Supported in client versions v3.x, 4.x, 5.x, 6.x. -verbosity x Sets the detail level of the output written to screen and to the fahlog.txt. Options are from 1 to 9 (max). The default is 3. Level 9 is helpful for diagnosing problems and helpful when reporting them to the F@h development team. Supported in client versions v3.x, 4.x, 5.x, 6.x. -oneunit Instructs the client to exit following the completion of one work unit. The client will attempt 3 uploads before exiting. This is recommended when planning to shut down a machine for a few days (e.g. for a vacation), or are planning to un/re-install F@H after finishing the current work unit. Supported in client versions v3.x, 4.x, 5.x, 6.x. Note: If the client is started again with this switch, the client will download new work, finish, upload, and quit again. This switch is not persistent from one startup to the next. Also, if the current work unit errors out, the client may download a new work unit. -oneunit does not take affect until a work unit is completed. -forceasm Instructs the fahcore to use processor optimizations, such as SSE or 3DNow+ assembly instructions if possible, even if the core has previously determined the computer may not be handling the client well. Stable systems do not need this switch, although it may be helpful for stable systems running on not-so-stable power grids without UPS intervention. Supported in client versions v3.x, 4.x, 5.x, 6.x. This switch will add this warning to the fahlog. -forceSSE This switch has been discontinued, and replaced by -forceasm. Instructed the fahcore to use SSE optimizations if possible, even if the core has previously determined the computer may not be handling the client well. Supported in client versions 3.25 and 4.x only. -advmethods Instructs the client to request work units from new late-stage beta test projects, before they are broadly released to the folding community. Please post any observations (positive or negative), questions, or issues at the Folding forum. Supported in client versions v3.x, 4.x, 5.x, 6.x. -local Instructs the client to read its configuration information from the local directory in the client.cfg file rather than, on Windows, from the installation directory specified in the registry, or, on Macintosh, from the Library/Folding@home directory. This switch is vital on Windows and Macintosh running multiple clients on a machine. This switch has no meaning on Linux and is ignored. Supported in client versions v3.x, 4.x, 5.x, 6.x. Information such as the user name, team name, proxy information, and Machine ID are maintained in the client.cfg file. The flag ensures that work from multiple clients do 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). For assistance setting up multiple clients on one machine, see the entry on installing multiple clients. This switch is also required when switching from the GUI to console client. -help Instructs the client to list the available command line flags and then exit. Supported in client versions v3.x, 4.x, 5.x, 6.x. Linux Specific Options -smp Sets the universal client v6 beta for Linux to run SMP work units. The client will default to run CPU client work units without this switch. -freeBSD For use by those wishing to use the Linux client on a machine running FreeBSD. See our FAQ for details on how to do this, but with this flag, all Cores downloaded will automatically be branded as being a Linux executable. IIRC, this option is no longer supported in v5.91 and above. -openBSD For use by those wishing to use the Linux client on a machine running OpenBSD. See our FAQ for details on how to do this, but with this flag, all Cores downloaded will automatically be branded as being a Linux executable. IIRC, this option is no longer supported in v5.91 and above. Windows Specific Options -pause Instructs the windows client to pause after finishing and trying to send current unit. Allows a user to shut down after finishing a unit, by pressing Ctrl-C, without then getting new work to process. Supported in client versions v3.x, 4.x, 5.x, 6.x. Similar to the more commonly used -oneunit flag, but without the automatic client exit. -service Sets the client to run in service mode (for programs such as firedaemon). This prevents the client from exiting when it detects the current user is logging out. If this option is used when the client is not run as a service then it will run normally, but will not shut down automatically if the user logs out, and a "Wait for program to close." dialog box will be displayed. Supported in client versions 5.x, 6.x CPU console client. This switch is more commonly used by 3rd Party service installers. -svcstart This flag is used if you configure the console client to be run as a service (through the standard client Configuration). The user should NOT give this flag manually, it is automatically given by the Windows scheduler and is just listed here for information. Supported in client version 5.x, 6.x CPU console client. -gpu x This switch is used with the GPU client, to run on the specified display number (x = 1,2,3,4). For use with multiple GPUs, and/or with multiple GPU clients. v5.91, v6.x.
|
console > graphical
<edit> bean's tear, blood and possibly pain free guide to update your GPU2 and 5.91 beta client. These are the clients I will be using: Windows XP/2003 GPU Console client (6.20) [stanford.edu] Windows XP/2003/Vista/2008 SMP client console version 6.22 beta2 for MPICH (32-bit or 64-bit) [stanford.edu] 1. Stop the current client you are updating and backup everything first! 2. Stop the MIPCH2 Service (services.msc) for SMP as well. 3. Install the new program from the above repository into the folder with your work. 3a. I put the GPU client in the Application Data\Folding@home-gpu 4. I've renamed my clients 'fah.exe' and 'fahGPU.exe' just for easier CLI tasking, optional. 5. Run each client using the -configonly switch. 6. Setup each client how you want but make sure to use the following additional parameter is necessary. 6a. SMP: -local -smp -forceasm -verbosity 9 6b. GPU: -verbosity 9 7. Change each service like the following replacing 'Administrator' with the login information you used for installation: ![]() 8. Check your services to make sure they all checkout and try them out. Credit for full service install (5.91) is here [xtremesystems.org] </edit> Last edited by bean; 08-02-2008 at 09:16 AM.. |
|
Console version Installation and Configuration for Intel Mac Users:
Most of the console prompts offer a pre-determined default value which you can select by just pressing the Enter Key. I cannot verify that these default values will remain the same for each operating system or version of the service, so I provided a recommended value for each setting. The values I recommended may not work best for everyone, but they should work well enough to get anyone up and running quickly and easily with a minimal amount of problems. 1) Open a new terminal window. 2) Copy/paste the following into the terminal, and wait for the program to download. If the program does not automatically launch after its downloaded and unzipped, press Enter. Code:
mkdir ~/Library/Folding@home cd ~/Library/Folding@home curl -O http://www.stanford.edu/group/pandegroup/folding/release/FAH6.00beta1-OSX-Intel-Console.tgz tar xzf FAH6.00beta1-OSX-Intel-Console.tgz chmod +x ./fah6 echo "cd ~/Library/Folding@home" > StartFaH echo "~/Library/Folding@home/fah6 -smp -local -verbosity 9" > StartFaH chmod +x StartFaH ./StartFaH 4) "Team number" = 49191. 5) "Passkey" = press the Enter key to leave blank. 6) "Ask before fetching/sending work" = no. 7) "Use Proxy" = no. 8) "Acceptable size of work assignment and work result packets" = normal. 9) "Change advanced options" = yes. 10) "Core Priority" = idle. 11) "Disable highly optimized assembly code" = no. 12) "Interval, in minutes, between checkpoints" = 15. 13) "Memory, in MB, to indicate" = press the Enter key to use the default (max) setting. 14) "Set -advmethods flag always, requesting new advanced scientific cores and/or work units if available" = no. 15) "Ignore any deadline information" = no. 16) "Machine ID" = 1, unless this is an additional installation of F@H then enter a unique number for each computer. For example, on the first computer enter 1, on the second computer enter 2, on the third 3, etc. 17) The installation is now complete and the console application is running. At this time you will have a terminal window open showing some status and logging information. Do not close the F@H terminal window otherwise the application will stop. Leave the terminal application running all the times. To get it out of the way, just right-click over the Terminal icon in the dock and select Hide. 18) To automatically start the application: a) Go to System Preferences, Accounts, select your user account, select Login Items. b) Drag-drop the StartFaH file located in ~/Library/Folding@home. c) Select the Hide checkbox if you do not want the terminal window visible. You can stop now you are done! 19) To reconfigure the software: a) Shutdown the Folding application by closing the terminal window. b) Open a new Terminal window. c) Copy/paste the following into the terminal window and press Enter: Code:
~/Library/Folding@home/fah6 -smp -config e) Don't forget to restart the Folding application once you have finished the configuration: copy/paste the following into the terminal window and press Enter: Code:
~/Library/Folding@home/StartFah Last edited by darksarcasm; 12-01-2008 at 10:34 PM.. |
|
CUDA 181.20 is out.
Direct Link XP [nvidia.com] Core 1.19 Thread Manual Download [foldingforum.org] Direct Download [stanford.edu] Last edited by bean; 01-29-2009 at 06:05 PM.. Reason: EUE Rep Comments |
|
Built with SD's support:
-Intel e6320 1.8ghz (oc @2.8ghz). -Intel e5200 2.5ghz (oc @4.0ghz). -XFX 9500GT (oc @690ghz). -4GB Crucial Ballistix Tracer. Which is put to use on Stanford's Folding@Home Project. |
|
|
Yes, the folding bug got me and I am currently running five 9800gx2 in two builds plus some minor extra contributions. I was hoping it could inspire at least the previous big folders to keep up and someone else having spare computing power to add to the production.
![]() I have some hardware issues to fight with so my PPD will probably drop some. What rigs are you running? I am impressed with all the 1920-pointer mr slickdeals keep submitting. Now, go team slickdeals! |
|
Folder 1: AMD BE-2400 MSI Crossfire Motherboard ($28 )2 x eVGA 8800gs 384mb Folder 2: Intel e7200 Abit IP-35E 1 x XFX 8800gs 384mb Folder 3: (at mom's house) Intel Q6600 Asus G31 Motherboard 1 x eVGA 9600gso 384mb Main Rig: Intel Q6600 Asus P5B Deluxe PNY 9800gtx Folder in progress: Intel E6600 MSI P6N Diamond 1 x PNY 9600gso 768mb 1 x eVGA 8800gs 384mb Will probably remove the 2x8800gs from folder 1 and put them in the P6N Diamond for now (if I ever get around to it), turn off folder 2 and put it's card in folder 1. Then I've gotta finish a new computer to replace my main rig, and once that's done I can put the 9800gtx from my main rig in folder 1... man, this gets complicated. I run SMP clients on the Q6600 at my mom's house, and also on the E6600 that is in progress. Don't know why, but I can't get the SMP client to run on the e7200 build - it just crashes, so I gave up. Running SMPs on the BE-2400 was too slow (risk missing deadlines) and the PPD per watt numbers weren't favorable. I've been getting a lot of EUEs on the GPU clients lately, on all of my systems and none of them are overclocked - so I think something is up with the newer WUs. I have to babysit them a little and restart the clients to get them running again (otherwise they stop for 24 hours). It's very frustrating to be adding GPUs to the folding effort but still have my PPD drop because of unstable work units.
Last edited by Mackowitz; 01-28-2009 at 09:36 AM.. |
|
|
dempa's push is inspiring!
i am in the same boat with raven with when i am folding. i also turn off the gpu client when i am gaming but leave the cpu's on even thru gaming. i find the gpu client not being able to throttle back as well as the cpus. um, since i recruited two friends to not only join in the project but also team SD could i tally up their PPD to mine? ![]() that would make about 4000-5000 ppd total! not
|
|
i was @ 12 or 15k total ppd.... i let all the clients go till they crashed or eue....i'm left with one linux client that runs perfectly... they all started to consume too much of my time (and money) to keep them running, if it were more stable i'd be more apt to get my ppd back up.
|
| Thread Tools | Search this Thread |
|
|