|  
 Sample of the client configuration window. This window is the same, regardless 
        of what platform you're running the client on. If you're running the client 
        on MacOSX, you may drag 'dnetc' to a new terminal window to launch it. 
        To perform various operations with the client, space twice then type --config, 
        --benchmark, --fetch, --flush, --update where applicable. Below is what 
        you have to do in order to get up and running
 1.  Download 
        the appropriate client for your cpu/os. These can be found at http://www.distributed.net/clients.html.
 
 2.  Open 
        the client. You'll notice that the client has a CLI < command-line 
        interface>. One of the advantages to having this kind of setup compared 
        to a GUI is that client setup regardless of OS is relatively the same.
 
 3.  Type 
        1 for General Client Options and press return. Type 1 followed 
        by return to enter an e-mail address. You can choose to run your client 
        under macguy@optonline.net (my e-mail address) or your own. If you choose 
        to do it yourself, you'll have to wait until your e-mail shows up on the 
        stats (After you've flushed 1 work unit and the stats have updated [usually 
        by early morning Eastern Standard Time) and then join the team (we'll 
        get to that later).
 
 4.  Type 
        2 and press return for Buffer and Buffer Update Options. Type 4 
        followed by the return key. Create a checkpoint file called checkpoint.txt 
        or something like that. Checkpoint files save you from losing work in 
        the event of a crash.
 
 5.  While 
        still in buffer options, you'll probably want to do two things. 
        One is changing the size of the packets your computer works on (2^29=2 
        2^28 work units, 2^30=4 28 work units, 2^32=16,2^33=32). 
        The larger the packet size, the longer your computer takes to test the 
        keys to see if they can crack the encryption. For example, a 2^33 unit 
        will take 32 times longer to test than a 2^28 packet (the default), but 
        the number of work units will also be 32 times larger. The point is to 
        decrease the amount of load placed on distributed.net's infrastructure, 
        while still be credited for the same amount of work.
 
 The second is changing the number of work units your computer gets. If 
        you find that your computer just flies through work units, even after 
        you've adjusted the previous setting (please note that client works on 
        a FIFO setup (First-In-First-Out), so changes to the packet sizes setting 
        may not be noticable until after you've changed the client's settings. 
        Go to client config. Type 2, press return. Type 13, press return. If you've 
        got a fast cpu, say a g4, make rc5=4000 or so (assuming you decide to 
        do ogr-25, keep the default amount). This should
  
        6.  Next, 
        we'll be creating a log file. A log file lets you keep track of how many 
        work units your computer has checked, at what rate, etc.2]
 7.  Once 
        your e-mail address has shown up via a search on the stats, 
        click request a password.
 8.  Go 
        to Team RealMac's stats 
        page, click on I want to join this team and enter in your user id 
        [e-mail address] and password.
   |