Tech Report Diskless Frankenbot

 

Jeffry55 Wine Folding Tutorial

 


Home

About Us

Contact Us


THE BASIC REQUIREMENTS:

1. 30 MB of free disk space

2. A compatible Linux Operating System

3. The correct winehq rpm file

4. The Windows XP Console Client for Folding (FAH502-Console.exe)

5. Enable viewing hidden & backup files in Linux. In FC2, click the red hat, navigate to Preferences, then More Preferences, then File Management & check the box to show hidden & backup files. Note: Other Linux flavors may be different. For Fedora Core 3 (FC3), the cool thing is you can double click the wine icon after download and it will auto-install like in windows.

For Linux, Fedora Core 2 (FC2), the current correct file is wine-20050111-1fc2winehq.i386.rpm. The file is routinely updated so the 20050111 part may be different. You can find it at winehq.com. Note: Be sure to select the correct file for your operating system. Name of files, folders and directories are case sensitive in Linux. Example: To “cd” to the Desktop be sure to capitalize the ‘D’.

You will not need the Wine Tools for this install. The download size of the Wine file is 14.4 MB. Installed it will be 20 – 30 MB. I downloaded the wine rpm file to my desktop while logged as user “jeff”. You can also log in as the “root”. Perform the following to install wine: Note: Do not include quotation marks when typing in listed commands. Note: Press enter after typing in commands.

The following instructions assume a wine install for Fedora Core 2 (FC2). Change the rpm number to match what you downloaded for your Linux version. Login in as the root. Open a terminal window by right clicking on the desktop, or as an alternate, you can press ctrl+alt+F2 to transfer to the Terminal Mode logon screen.

1. From the prompt type “rpm -i wine-20050111-1fc2winehq.i386.rpm” (rpm –i is the install command). It will take a little time to run through the install sequence.

2. When the install finishes, you can type “rpm -q wine” (rpm –q is the query command). You should get “wine-20050111-1fcewinehq” which is the version number. This is a way to verify that Wine installed successfully.

3. Type the command “wine” and hit return. This will build the default wine directories and files.

4. The Wine installation will create a set of Directories inside the “root” folder/directory, the path will be "/root/.wine/drive_c/Program Files”.

5. You can switch back to the X/ Graphical Mode with alt+F7 or navigate in the Terminal Mode using the “cd” command (change directory). I prefer the Graphical Mode for making directories/folders & moving files because it is more like Windows. Note: The format to use in the Terminal Mode is not consistent for all subdirectories. You can cd root or cd /root or cd “root” or cd /”root”. Sometimes you have to try different syntax to navigate. I don’t know why. Note: You can use the ls –a (list all) command to view the contents of a directory while in the Terminal Mode. There are two ways to go from here. You can work in the Terminal Mode and create a Folding@Home directory in the “Program Files” directory or you can make a folder on your desktop while logged in with a username. I chose to work from the Desktop in the X/Graphical Mode while signed in as user “jeff”. I feel it is easier & there are fewer instructions. I also have auto-start script that works from that configuration.

GRAPHICAL MODE MAKING A “WINE” FOLDER

1. Log into the Graphical Mode as a user.

2. Make a folder on your Desktop and name it “wine”.

3. Move, copy or download the Windows Console F@H client (FAH502-Console.exe) into the wine folder.

4. Rename the F@H client to FAH502.exe to make it shorter.

5. You will need to stop the Linux F@H client if you have it running. Open a Terminal window by right-clicking on the Desktop & select “Terminal Window”.

6. Type “killall FAH502-Linux.exe”. The command will work from any directory. It will take a minute or two for the command to execute.

7. Type “top” in the Terminal Window to verify that the FahCore has stopped.

8. While in the Terminal Window, navigate (cd home/jeff/Desktop/wine) to the wine folder. Type wine FAH502.exe -forceasm -advmethods -verbosity 9 to start the F@H client (the –switches are not required). Pay close attention to the spacing between the words, dashes & numbers.

9. The F@H client should execute. Fill in username, Team number (2630 of course), use the default “no” answer for the remaining questions except answer “yes” to the greater than 5MB work unit question if your PC can handle large WUs.

10. You should see the processes of downloading a new core, getting a protein, etc.

11. You are now folding with wine!

12. Open a second Terminal Window.

13. Type “ps x | grep “wine”. This will do a search for any process outputs with “wine” in it. You should see a path like this: “/usr/sbin/wine-preloader”.

14. Type “ps x | grep “wine-preloader”. This will do a search for any process outputs of the wine preloader. You should see FAH502.exe amongst the text displayed.

15. The wine preloader does not show activity in FC2 when you use the ‘top’ command. It does show up in FC3.

16. Be sure to leave your PC in the Terminal mode to maximize folding efficiency (ctrl+alt+F2). You pay a 6% CPU usage fee while in the X/Graphical mode.


SETTING UP AUTO-START OF THE WINE-F@H CLIENT

This script is based on user name “jeff” and that the wine folder is on the Desktop for “jeff”. Change according to your setup.

Auto-start script for the rc.local file:

sudo -u jeff sh -c "cd ~jeff/Desktop/wine;

wine FAH502.exe –forceasm –advmethods –verbosity 9 >>folding.log 2>&1 &"

BIG NOTE: My experience with Linux is limited. I have cobbled together the knowledge of others to arrive at this script. I know it works.

I do not know at this time the script format for auto-start with the FAH502.exe file in the root/.wine/drive_c/Program Files/Folding@Home directory.

sudo -u jeff sh -c "cd /root/.wine/drive_c/Program Files/Folding@Home;

wine FAH502.exe –forceasm –advmethods –verbosity 9 >>folding.log 2>&1 &"

The above should work? Once you have verified that the auto-start script is functioning, you can log out of the Graphical Mode and login using the “fail-safe” mode. The fail-safe mode consumes minimum resources so you get maximum folding performance. You will find the fail-safe mode as an option when you click on the session icon at the initial sign-on screen for FC2.

TERMINAL MODE MAKING A “FOLDING@HOME” DIRECTORY

1. Navigate to the Program Files directory and make a Folding@Home directory with the mkdir command if in the Terminal Mode. (mkdir Folding@Home).

2. Move or copy the Windows Console F@H client (FAH502-Console.exe) into the Folding@Home directory.

3. Rename the F@H client to FAH502.exe to make it shorter.

4. You will need to stop the Linux FAH client if you have it running. Type “killall FAH502-Linux.exe”. The command will work from any directory. It will take a minute or two for the command to execute.

5. Type “top” to verify that the fahCore has stopped.

6. Type “q” to quit the top command

7. Navigate to the root/.wine/drive_c/Program Files/Folding@Home directory or to the home/jeff/Desktop/wine folder. Type wine FAH502.exe -forceasm -advmethods -verbosity 9 to start the F@H client (the –switches are not required). Pay close attention to the spacing between the words, dashes & numbers.

 8. WARNING: If you have opened a terminal window using the ctrl+alt=F2 method, a glitch occurs that prevents you from typing when the F@H client launches.

9. Press ctrl+c and then enter. Type “logout” and press enter. You will not see the text as you type.

10. Login in again as the root and you will be able to type. (Hurrah!)

11. Navigate to the Folding@Home directory.

12. Type “ls” to list the contents of the directory and look for the client.cfg file. 13. Type nano client.cfg. Nano is the Text Editor in the Terminal Mode.

14. Edit the Username, team number and add bigpacket=yes if you are enabling large Work Units.

15. Press “esc” to save the file. Then press x to exit the editor. A list of nano commands is at the bottom of the page.

16. Type “more client.cfg” to show the client.cfg file again to do a quality check to ensure you made all the corrections ………………….….correctly.

17. Use the up/down arrow keys to scroll through your recent commands to find “wine FAH502.exe –forceasm –advmethods –verbosity 9 and press enter. (the - switches are not required)

18. The F@H client should execute and you should see the processes of downloading a new core, getting a protein, etc.

19. You are now folding with wine!

20. Open a second terminal session by pressing ctrl+alt+F3 & login as the root.

21. Type “ps x | grep “wine”. This will do a search for any process outputs with “wine” in it. You should see a path like this: “/usr/sbin/wine-preloader”.

22. Type “ps x | grep “wine-preloader”. This will do a search for any process outputs of the wine preloader. You should see FAH502.exe amongst the text displayed.

23. The wine preloader does not show activity in FC2 when you use the ‘top’ command. It does show up in FC3.

24. Type “less /root/.wine/drive_c/”Program Files” /Folding@Home/FAHlog.txt” to display the Fahlog.txt file. You can navigate through the file with the pageup, pagedown, home & end keys.

25. Type ‘q’ to exit/quit the display of the file.

26. Be sure to leave your PC in the Terminal mode to maximize folding efficiency (ctrl+alt+F2). You pay a 6% CPU usage fee while in the X/Graphical mode.



Folding Farm status