How do I install the Windows CPU console client? (a guide for newbies)

The CPU console client, also known as the Command Line Interface (CLI) client, or the "no nonsense text only console" is distributed as software only and is not packaged as a "Windows Installer." Follow the instructions below for installing the F@h client on Windows XP and versions prior to XP. For Vista, see the Vista CPU Setup procedure.


 * Create a new folder in a location easy to remember. A good choice is: C:\Program Files\FAH\


 * Download the CPU console client into the new directory you just created. When downloading, do NOT select "Run" but rather select "Save As." Do not save the F@h executable to the desktop.


 * Double click the fahconsole_x.x (where x.x is the latest version) to launch the console client.


 * Answer the client setup questions.


 * Enter your User Name and Team #. You can check to see if a username is already taken on the Download page.  If you have not already joined a team, leave the default setting of 0 (zero) for now.  You can always change it later if you join a team.
 * Answer each additional setup question carefully. The default settings are usually recommended until you become more familiar with how each setting affects the client, or unless you know the default answer needs to be changed.


 * Do NOT answer yes to the "Use Internet Explorer Settings? question, or the "Request work units without deadlines?" question. Answering yes may prevent the client from downloading or uploading work units.


 * The console window must remain open while the client is running but you can minimize it to the Task Bar so you don't see it (or run the client as a service, see next item). The proper way to stop the client is to select the fah window, and press ctrl+c. This will stop the client and close the window.


 * Even if you plan to run the client as a service, it's recommend you run the client interactively for a few weeks before you switch to a service. In any case, it's a good idea to create a shortcut on your desktop to start the client manually. (How_do_I_create_a_Windows_shortcut?)  If you do start to run the client as a service, do NOT forget to remove the shortcut from the Startup folder.  Forgetting to do this has a potential to corrupt work units.


 * If you want the client to start automatically after a reboot, you will need to create a shortcut to in the Startup group. It can be a copy of the one you created on the desktop.


 * If you have previously installed the GUI client you must add the -local flag to any shortcut that doesn't already have one.

That pretty much wraps it up. The more you run the client, the more you help the F@h project, and the more points you score.