- Joined
- Oct 31, 2001
- Location
- Lost Angeles
I only have the single and dual cpu versions finished, so be patient for the quad install.
One-Click is rollin', in my 5.0, rag top down so my hair can blow..
If you are running XP/XP Home/W2K(all versions) on a single cpu computer, do this:
1. Download the Single CPU version.
2. Unzip the file to a floppy or to a directory (folder) on the desktop.
3. Edit the client.cfg with notepad and change "Wedo" to your folding username. Only use Notepad to edit the client.cfg files.
4. Click the .exe file.
5. Fold
6. Repeat as often as humanly possible.
Poof, your folding.
Dually/HT is rollin' the 5.0 too:
You will do everything noted in the above section except use the Dually/HT version of the One-Click:
Download the Dually/HT CPU version.
The only other change is that there are two client.cfg files to edit, both of which need your username (again, use notepad to edit this file). The client.cfg's have different names, but don't worry, when you hit the .exe after editing the One-Click changes the names of the files and copies them into the correct directories.
*Note: With some W2K and XP Home rigs you have to reboot to get the service running. So if you use the One-Click and don't see FAHCore_XX.exe running after a minute in the task manager, just reboot.
This will overwrite any previous One-Click version so if you've already used an OC, fire away.
Furthermore, these versions use the new "bigpackets" flag in the client.cfg (formerly known as the -advmethods flag in the registry. You can disable this by editing the client.cfg and changing the "yes" to a "no".
Speaking of the registry, I used the following four flags:
-local -service -verbosity 9 -forceasm
I like the extra goodies I get from the verbosity flag and I don't like the client downshifting into a form of "safe mode" after a power failure, thus, the -forceasm flag.
Foldeth On-eth
Wedo
One-Click is rollin', in my 5.0, rag top down so my hair can blow..
If you are running XP/XP Home/W2K(all versions) on a single cpu computer, do this:
1. Download the Single CPU version.
2. Unzip the file to a floppy or to a directory (folder) on the desktop.
3. Edit the client.cfg with notepad and change "Wedo" to your folding username. Only use Notepad to edit the client.cfg files.
4. Click the .exe file.
5. Fold
6. Repeat as often as humanly possible.
Poof, your folding.
Dually/HT is rollin' the 5.0 too:
You will do everything noted in the above section except use the Dually/HT version of the One-Click:
Download the Dually/HT CPU version.
The only other change is that there are two client.cfg files to edit, both of which need your username (again, use notepad to edit this file). The client.cfg's have different names, but don't worry, when you hit the .exe after editing the One-Click changes the names of the files and copies them into the correct directories.
*Note: With some W2K and XP Home rigs you have to reboot to get the service running. So if you use the One-Click and don't see FAHCore_XX.exe running after a minute in the task manager, just reboot.
This will overwrite any previous One-Click version so if you've already used an OC, fire away.
Furthermore, these versions use the new "bigpackets" flag in the client.cfg (formerly known as the -advmethods flag in the registry. You can disable this by editing the client.cfg and changing the "yes" to a "no".
Speaking of the registry, I used the following four flags:
-local -service -verbosity 9 -forceasm
I like the extra goodies I get from the verbosity flag and I don't like the client downshifting into a form of "safe mode" after a power failure, thus, the -forceasm flag.
Foldeth On-eth
Wedo
Last edited:
