Welcome to the MacNN Forums.

Bockie · Mar 30, 2002, 11:04 AM

I have tried everything I know to start working with FAH. I've followed the instructions on the Team page, I've followed the instructions on MacAddict4Life's page...nothing works!

I remove the .bin from the file; I chmod the file; I place the client in it's own folder; I cd to that folder; I ./ the client...Command not found ?!?

Please help a Folding newbie, will ya?

Shaktai · Mar 30, 2002, 01:03 PM

Originally posted by Bockie:
I have tried everything I know to start working with FAH. I've followed the instructions on the Team page, I've followed the instructions on MacAddict4Life's page...nothing works!

I remove the .bin from the file; I chmod the file; I place the client in it's own folder; I cd to that folder; I ./ the client...Command not found ?!?

Please help a Folding newbie, will ya?

I had the same problem and in the end just went with the Graphic client which is just as fast as the CLI when ran "hidden". I did eventually the CLI working, but for the life of me can't remember how.

Welcome to Folding.

reader50 · Mar 30, 2002, 01:15 PM

after cd'ing to the client folder, try typing "ls" (lowercase "LS") to get a directory listing. It's possible the client binary has a file extension, which the Finder is hiding from you. If so, ditch it. I have very little use for filename extensions.

Edit: oops, it's a bare binary, and you already got rid of the extension. Try the "ls" command anyway, to see what folder you are in, and the exact spelling of the client's filename. One or the other has to be where the problem is.

[ 03-30-2002: Message edited by: reader50 ]

Bockie · Mar 30, 2002, 01:49 PM

Originally posted by reader50:
after cd'ing to the client folder, try typing "ls" (lowercase "LS") to get a directory listing. It's possible the client binary has a file extension, which the Finder is hiding from you. If so, ditch it. I have very little use for filename extensions.

Edit: oops, it's a bare binary, and you already got rid of the extension. Try the "ls" command anyway, to see what folder you are in, and the exact spelling of the client's filename. One or the other has to be where the problem is.

[ 03-30-2002: Message edited by: reader50 ]

I already tried the ls and ls -al. The file is still showing as .bin even after renaming the file without the extension. I don't know remember how to rename via UNIX...haven't looked it up-I'm lazy today. :o

Could that be the problem?

reader50 · Mar 30, 2002, 02:28 PM

Originally posted by Bockie:
I already tried the ls and ls -al. The file is still showing as .bin even after renaming the file without the extension. I don't know remember how to rename via UNIX...haven't looked it up-I'm lazy today. :o

Could that be the problem?

It's definitely the problen. You probably have "hide extensions" turned on in the Finder. You would have to turn that off for a rename that dumps the extension.

The other option is to live with the problem, like the windoze folks do. Launch it with the extension: "./folding.bin"

Shaktai · Mar 30, 2002, 02:46 PM

Originally posted by reader50:

It's definitely the problen. You probably have "hide extensions" turned on in the Finder. You would have to turn that off for a rename that dumps the extension.

The other option is to live with the problem, like the windoze folks do. Launch it with the extension: "./folding.bin"

Now I remember what I did. I selected the file, and then did a get info. It showed the .bin there, so I deleted it under get info, and then was able to get it to work. Deleting it under the file name only in the finder, did not remove the actual extension.

doughboyj · Mar 30, 2002, 05:42 PM

Shaktai is right. Get info (command+I) and go to the name and extension option and take off the .bin from there then it should work for you.

Bockie · Mar 30, 2002, 10:57 PM

Originally posted by reader50:

It's definitely the problen. You probably have "hide extensions" turned on in the Finder. You would have to turn that off for a rename that dumps the extension.

The other option is to live with the problem, like the windoze folks do. Launch it with the extension: "./folding.bin"

It works, so I'll just live with the extension.

At least I'm now folding!

wheeles · Mar 31, 2002, 04:52 AM

Here's a basic UNIX command line primer. Given time you might start to actually like the command line.

If you need to change a name in UNIX open up the Terminal.app then type 'mv' followed by the filename and then the new filename like so.

<BLOCKQUOTE>code:<HR><pre>
mv folding.bin folding
[/code]

If you aren't already in the same directory as the file you will need to specify the whole path to the new and old filenames or change directory to where the file is before issuing the mv command. You can find out where you are by typing:

<BLOCKQUOTE>code:<HR><pre>
pwd
[/code]

This stands for 'print working directory'.

To change directory type cd (followed by a space) and then either type the directory name with its full path or drag the desired directory folder from the Finder to your Terminal.app which should result in something like:

<BLOCKQUOTE>code:<HR><pre>
cd /Applications/Folding
[/code]

Hit return and you should then be able to type that mv command above.

If you don't want to change directory you can always just type mv (followed by a space) and then drag the folding binary to the Terminal.app (this doesn't actually move the binary anywhere, just saves you having to type the whole path). Type another space and drag it again. Now all you have to do is hit backspace a few times to get rid of the '.bin' ending and you are done like so:

<BLOCKQUOTE>code:<HR><pre>
mv /Applications/Folding/folding.bin /Applications/Folding/folding
[/code]

Incidentally you might need to make the binary executable. To do that type:

<BLOCKQUOTE>code:<HR><pre>
chmod +x /Applications/Folding/folding
[/code]

Hope this helps to de-mystify things for a few people.

Bockie · Mar 31, 2002, 10:00 AM

Originally posted by wheeles:
Here's a basic UNIX command line primer. Given time you might start to actually like the command line.

Thanks for the refresher...It's been several years since I've had day-to-day workings with UNIX, so I'm still a little rusty. This will help lots of others I'm sure!