Folding Forum

Yes, spaces before each dash.

You can place the shortcut wherever you like. I usually keep mine in Quick Launch, but it can be on your desktop, in a folder on your desktop, wherever you want.

You do not want to crunch both clients in the same folder. That is why you need to add the -local switch.

If your new console is here:
C:\ProgramFiles\FAH2

The target box should have this in it:

C:\ProgramFiles\FAH2\XXXXXXXX.exe -local -verbosity 9 -config

XXXXXXXXX.exe would be the name of the console client file you downloaded.

We are adding the -config switch just to make sure it lets you enter your configuration choices. Don't forget to enter your folding name, team number and the #2 machine ID. The other choices are your preferences, but don't tell it to get WUs w/o deadlines. There are none.

When you get it running, open FAHlog.txt (from the new client's directory) in notepad and paste the contents in a message here, so we can check to make sure all looks right.

After losing the unit I was working on [grrrr], the program tried to download another unit which aborted also. Did I read in one of the links that if you close the console client, you lose your work?

Here's the log from my graphical client, if that helps:

[19:10:32] Successfully sent unit 02 to Collection server.
[19:10:32] - Preparing to get new work unit...
[19:10:32] + Attempting to get work packet
[19:10:32] - Connecting to assignment server
[19:10:33] - Successful: assigned to (171.64.65.111).
[19:10:33] + News From Folding@Home: Welcome to Folding@Home
[19:10:33] Loaded queue successfully.
[19:10:46] + Closed connections
[19:10:46]
[19:10:46] + Processing work unit
[19:10:46] Core required: FahCore_81.exe
[19:10:46] Core found.
[19:10:46] Working on Unit 03 [December 3 19:10:46]
[19:10:46] + Working ...
[19:10:46]
[19:10:46] *------------------------------*
[19:10:46] Folding@Home Gromacs Simulated Tempering Core
[19:10:46] Version 1.10 (Oct 4, 2007)
[19:10:46]
[19:10:46] Preparing to commence simulation
[19:10:46] - Looking at optimizations...
[19:10:46] - Created dyn
[19:10:46] - Files status OK
[19:10:47] - Expanded 469769 -> 2292782 (decompressed 488.0 percent)
[19:10:47] - Starting from initial work packet
[19:10:47]
[19:10:47] Project: 4105 (Run 14, Clone 3, Gen 1)
[19:10:47]
[19:10:47] Assembly optimizations on if available.
[19:10:47] Entering M.D.
[19:10:53] Protein: p4105_villinwt_unf_Amber03_Extended
[19:10:53]
[19:10:53] Writing local files
[19:10:53] Extra SSE boost OK.
[19:10:53] Writing local files
[19:10:53] Completed 0 out of 1500000 steps (0)
[19:33:21] Writing local files
[19:33:21] Completed 15000 out of 1500000 steps (1)



[00:00:29] Completed 1110000 out of 1500000 steps (74)
[00:23:40] Writing local files
[00:23:40] Completed 1125000 out of 1500000 steps (75)
[00:47:09] Writing local files
[00:47:09] Completed 1140000 out of 1500000 steps (76)
[00:50:18] - Checksums don't match (work/wudata_03.xtc)
[00:50:19] Premature end of file when checksumming (2685200 bytes left)
[00:50:19] - Could not calculate checksum (work/wudata_03.xtc)
[00:50:20] Checksum not what expected.
[00:50:20]
[00:50:20] Folding@home Core Shutdown: FILE_IO_ERROR
[00:50:23] CoreStatus = 75 (117)
[00:50:23] Error opening or reading from a file.
[00:50:23] Deleting current work unit & continuing...
[00:50:27] - Preparing to get new work unit...
[00:50:27] + Attempting to get work packet
[00:50:27] - Connecting to assignment server
[00:50:40] - Successful: assigned to (171.64.122.83).
[00:50:40] + News From Folding@Home: Welcome to Folding@Home
[00:50:40] Loaded queue successfully.
[00:59:35] + Closed connections
[00:59:40]
[00:59:40] + Processing work unit
[00:59:40] Core required: FahCore_79.exe
[00:59:40] Core found.
[00:59:40] Working on Unit 04 [December 5 00:59:40]
[00:59:40] + Working ...
[00:59:40]
[00:59:40] *------------------------------*
[00:59:40] Folding@Home Double Gromacs Core
[00:59:40] Version 1.91 (April 11, 2006)
[00:59:40]
[00:59:40] Preparing to commence simulation
[00:59:40] - Looking at optimizations...
[00:59:40] - Created dyn
[00:59:40] - Files status OK
[01:00:01] - Expanded 9511153 -> 34521892 (decompressed 362.9 percent)
[01:00:01] - Starting from initial work packet
[01:00:01]
[01:00:01] Project: 3903 (Run 2307, Clone 4, Gen 1)
[01:00:01]
[01:00:02] Assembly optimizations on if available.
[01:00:02] Entering M.D.
[01:00:11] Protein: IBX in water
[01:00:11]
[01:00:11] Writing local files
[01:00:31] Extra SSE2 boost OK.
[01:00:34] Writing local files
[01:00:35] Completed 0 out of 25000 steps (0)
[01:02:13] iles
[01:02:14] Completed 0 out of 25000 steps (0)
[01:06:19]
[01:06:19]
[01:06:19] Folding@home Core Shutdown: FILE_IO_ERROR
[01:06:22] CoreStatus = 75 (117)
[01:06:22] Error opening or reading from a file.
[01:06:22] Deleting current work unit & continuing...
[01:06:26] - Preparing to get new work unit...
[01:06:26] + Attempting to get work packet
[01:06:26] - Connecting to assignment server
[01:06:27] - Successful: assigned to (171.65.103.162).
[01:06:27] + News From Folding@Home: Welcome to Folding@Home
[01:06:27] Loaded queue successfully.
[01:08:52] + Closed connections
[01:08:57]
[01:08:57] + Processing work unit
[01:08:57] Core required: FahCore_78.exe
[01:08:57] Core found.
[01:08:57] Working on Unit 05 [December 5 01:08:57]
[01:08:57] + Working ...
[01:08:57]
[01:08:57] *------------------------------*
[01:08:57] Folding@Home Gromacs Core
[01:08:57] Version 1.90 (March 8, 2006)
[01:08:57]
[01:08:57] Preparing to commence simulation
[01:08:57] - Looking at optimizations...
[01:08:57] - Created dyn
[01:08:57] - Files status OK
[01:09:02] - Expanded 3062168 -> 16578197 (decompressed 541.3 percent)
[01:09:02] - Starting from initial work packet
[01:09:02]
[01:09:02] Project: 2427 (Run 11, Clone 84, Gen 16)
[01:09:02]
[01:09:03] Assembly optimizations on if available.
[01:09:03] Entering M.D.
[01:09:11] Protein: p2427_Ribo_Cl_aux
[01:09:11]
[01:09:11] Writing local files
[01:09:16] Extra SSE boost OK.
[01:09:17] Writing local files
[01:09:18] Completed 0 out of 250000 steps (0)


Btw, in the old forum, you could condense these long passages from the log. Can you do it here, and how do you do it?

Thanks again for your patience.

I was hoping to see the startup part of the log, too. Can we see that, too, please?

As for condensing the data, no, the code tags don't seem to work like that in this version of the forum software.

Sorry, posted my graphical log before I saw your responses.

I'm confused about something - [OK, more than a few things] are folders and directories the same or different?

You do not want to crunch both clients in the same folder. That is why you need to add the -local switch.

So, with one in \ProgramFiles\Folding@Home and the other in
\ProgramFiles\FAH2, am I OK?

When you get it running, open FAHlog.txt (from the new client's directory) in notepad and paste the contents in a message here, so we can check to make sure all looks right.

The new client's directory? Will this become self-evident?

OK - here I go!!!

Thanks again.

Unfortunately, if you had the two units crunching on top of one another, that could have caused the WU corruption, sorry. Make sure both clients start using the -local switch.

Shutting down the console client should always be done by getting mouse focus on the console window and then doing Ctrl-C simultaneously to stop the client.

And you should also put your folders right on the C drive, not under the Program Files.

Mine are C:\cpu1 and C:\cpu2.

Sorry, I am using directory and folder interchangeably. I try to remember to always say folder for those who cut their teeth on Windows, but my start was with the DOS command line, so I forget.

So, with one in \ProgramFiles\Folding@Home and the other in
\ProgramFiles\FAH2, am I OK?

You should be, but C:\FAH2 would be better. To be safe, make sure the console client starts with the -local switch added to the command (target) line. Make sure the second (console) client is configured as machine ID #2. The -verbosity 9 switch will put more data in the log for troubleshooting.

The new client's directory? Will this become self-evident?

The FAHlog.txt for the old client would be here:


C:\ProgramFiles\Folding@Home
(or, more likely here: C:\Program Files\Folding@Home )


The FAHlog.txt for the new console client should be here:

C:\ProgramFiles\FAH2
(or, more likely here: C:\Program Files\FAH2 )


That looks odd to me, though. If you have these folders in the default Program Files folder created by the Windows install, then there would be a space between Program and Files.

Also, if you are running Vista instead of an earlier version of Windows, it would be better not to put the client in the Program Files folder because of permissions issues which would complicate things for you.

If you are running Vista, put the new client in C:\FAH2 and skip the Program Files folder.

I tried adding the -config switch to the target in the shortcut. I get an error message when I click OK

"\Program Files\FAH2\FAH504-Console.exe -local -verbosity 9 -config specified in the Target box is not valid. Make sure the path and file name are correct."

I closed the box, and double clicked on the short cut and got a log file, which I can't seem to copy, and interestingly enough, it's the program that's running on my graphical client. At the start it says:

"The file FAHlog.txt has been locked by the operating system and cannot be opened for writing (possibly because it is open in another application.) Before you next run F@H, please ensure F@Hlog.txt is not open anywhere, or simply delete it. For now FAHlog2.txt will be used."

And once again, the graphical client program crashed. What if I try downloading the console to a new folder not in Program Files?

Oh, and I'm on XP.

Make 2 shortcuts for each client, one to run and one to configure.

Run- use -local -verbosity 9 flags
Configure- use -configonly flag

-configonly will let you run through the configuration and then closes without starting the client. After you configure, use the run shortcut to start the client.

\Program Files\FAH2\FAH504-Console.exe -local -verbosity 9 -config specified in the Target box is not valid. Make sure the path and file name are correct

I don't see a drive letter in that path. Is there a space between the hyphen and config? If so, that's a problem.

Also, if you place the fah folder withing the Program Files folder, things get complicated. You have to enclose the actual command with quotation marks because of the space in Program Files, so your command line would look like this: "C:\Program Files\FAH2\FAH504-Console.exe" -local -verbosity 9 -config

This is the reason I suggest C:\FAH2\FAH504-Console.exe -local -verbosity 9 -config

Without the space in the folder name, you don't need to worry about the quotes or placing them correctly.

What if I try downloading the console to a new folder not in Program Files?

I never install FAH in the Program Files folder even though it wouldn't really confuse me. There are a number of reasons why it isn't the best idea for someone new to computers. I don't know what the Microsoft guys were thinking.

Yes, as we've said above, keep it simple. Short folder name. Create it directly at the root of the drive. Don't put it in another folder.

Like this:

C:\FAH2

Or whatever short name you want.

And then the full startup command would be:

To configure and then run the client ...
C:\FAH2\FAH504-Console.exe -local -verbosity 9 -config

or

To configure the client without running it ...
C:\FAH2\FAH504-Console.exe -local -verbosity 9 -configonly

or

To run the client without configuring it ...
C:\FAH2\FAH504-Console.exe -local -verbosity 9

Please note the edits in my posts.

I think we're moving along...

I tried downloading in my new folder C:\FAH2a and immediately noticed one difference when I went to the short cut to add the flags. In my first try, there were quotation marks on either side of the file name. Now there are none. And I took the advice of making one short cut config only. However, it starts off assuming I'm using machine id 1 (blows right by that part). How do I get it to let me tell it it's really id 2?