Copyright © 2003 Team Distributed
Last modified: June 21, 2003
Best viewed 800×600
Client Installation
1. Go to http://www.distributed.net/download/clients.html and download the appropriate client program for your CPU and Operating System. For Windows 95/98/NT/2K/XP, you will want to download the “[x86/Installer]” program and during setup have it add shortcuts to the Start Menu and checkmark “Run Client at Startup.”
2. Once the client software is installed, RC5 will startup in Configuration mode. If it does not startup, click on Start, Programs, Distributed.net, Quick Command, Client Configuration to startup the configuration. These setup instructions are for client v2.9001-477-GTR-02111118 for Win32 and may be slightly different for other client versions or OSs, just look for a similar configuration option. Unix/Linux/BSD client configuration is the same. The following configuration steps seem long, but they are really easy to configure, and once you have one client configured, you can copy the finished dnetc.ini to ALL of your machines!
a. Once you are in configuration mode, you should see a window like this:
b. Choose option “1″ and you should be at the “General Clients Menu”:
c. Choose option “1″ and enter a valid email address. It must be a real, working email address, because it is where Distributed.net will email your password a little later on, and the password is required to join Team Distributed. If changes in your email address will be a common occurrence, a Hotmail or other free email service may be preferable, and you should set up an account with one of these providers before configuring the Dnet client. Here is the email address menu:
d. Once you have entered your email address you should be back at the “General Clients Menu:”:
e. Choose option “0″, and you should be back at the main menu:
f. Choose option “2″ Buffer and Buffer Update Options , you should be at the Buffer and Buffer Update Options menu:
g.Choose option “6″ Keyserver<->client connectivity options , you should see a window like this:
h. Choose option “2″ Automatically select a distributed.net keyserver. Since TeamDistributed runs a proxy server in order to provide real-time stats, you will want to disable this. Change the option to “No”. You should see a window like this:
i. You should now be back at this menu:
j. Choose option “3″ Keyserver hostname, you should be at the Keyserver hostname menu. Type in www.TeamDistributed.com and press enter.
k. You should now be back at this menu, ensure option “2″ is “no” and option “3″ is “www.TeamDistributed.com“. For option “4″, Keyserver port, enter “2064″. If your network configuration does not permit you to use this port, you may set option “3″ to 63.162.87.200 and set option “4″ to use port 8080 instead.
l. DIALUP USERS ONLY: Choose option “9″ Dial-up Link detection options. I recommend using the “1″ Dial-up detection mode. This will automatically send/receive packets when you are connected to the internet–you will not have to do anything but connect to the internet. You should see a window like this:
n. Choose option “0″ Return to Buffer and Buffer Update Options , you should be at the Buffer and Buffer Update Options menu:
o. ATTENTION: You will EITHER use THIS step or the NEXT step. Choose option “13″ Fetch time threshold (in hours). You can see I have my client set to 0 hours (RC5=0). This tells the client to use the Fetch Work threshold instead. If you would like to use the time thresholds, just change the “0″ to however many “hours” of packets you want to download (the client computes how many you will need by averaging your clients keyrate over a period of time and determining how many packets you will need for X hours of work). If you get online daily, 24 hours is good–but if you go on vacation or only get on the internet every few days, change this number to 48 or 72 hours. This will ensure your RC5 client does not run out of work units to crunch.
p. Alternatively, you may use the Fetch Work threshold, which is based on packets instead of time. This options tells the client to buffer X packets between communications with the keyserver. As you can see, I use “1″ for this option, so my clients flush completed work immediately to the team proxy (since the team proxy is on the same LAN as the rest of my machines). You will want to buffer at least three or four blocks so your clients don’t run out of work in the not-unlikely event of a network outage here at the TeamDistributed.
q. Return to the main menu and select option 9, Load-Work precedence, and make sure it reads: RC5-72,OGR=0. That will ensure your client does RC5 blocks only. Once you have double-checked the option 12 line, you can simply hit option “0″ Return to main menu. Then choose “0″ Save settings and exit. This will save your RC5 configuration. If you installed the client using the installer, Dnet will automatically start now.