Containing files?

Anyone know how to keep boinc from spewing work files all over my home directory? Even if I put it in its own directory it keeps putting its files in my home folder.

Ah, I see. Perhaps one could also get it to put files in a specific separate directory by doing, say:

cd boinc/boincfiles
../boinc_3.18

I've been struggling like hell with this Command line version, but I'd also like to understand how to do this... can somebody explain in simple terms? as if for their grandma... unless she does *nix too... ;-) please?

Here's how I solved this problem.

I created a folder in the Applications folder called BOINC.
I moved all the BOINC files from my Home folder, and the BOINC application to this folder.
Using TextEdit, I created a script file containing the following:

cd /Applications/BOINC/
/Applications/BOINC/BOINC

I converted it to plain text with the "Make Plain Text" command from the Format menu, and saved it as "Launch BOINC" without an extension, in my BOINC folder.

I used the Finder's "Get Info" command to change the "Open with" property of Launch BOINC to "Terminal". You will have to switch the Enable filter at the top of the selection window to "All Applications" first, or else the Finder will grey out Terminal. Now you can launch the Launch BOINC script by double-clicking it.

> Here's how I solved this problem.
>
> I created a folder in the Applications folder called BOINC.
> I moved all the BOINC files from my Home folder, and the BOINC application to
> this folder.
> Using TextEdit, I created a script file containing the following:
>
> cd /Applications/BOINC/
> /Applications/BOINC/BOINC
>
> I converted it to plain text with the "Make Plain Text" command from the
> Format menu, and saved it as "Launch BOINC" without an extension, in my BOINC
> folder.

Was this all that had to go into the script file or is there any other coding needed, please? Is there any reason you created it in Text Edit rather than AppleScript?

I'm asking this as I'm new to all this technical stuff, which we didn't had to know to run the earlier version of SETI@home.

(BTW I already twigged the Get Info method of forcing Terminal to open the program.)

> Using TextEdit, I created a script file containing the following:
>
> cd /Applications/BOINC/
> /Applications/BOINC/BOINC
>

I've done all that, but Terminal won't run the script. Double-clicking the file will launch Terminal, but nothing else happens after that. Is there something I'm missing, such as a file extension or permission or something?

> > Using TextEdit, I created a script file containing the following:
> >
> > cd /Applications/BOINC/
> > /Applications/BOINC/BOINC
> >
>
> I've done all that, but Terminal won't run the script. Double-clicking the
> file will launch Terminal, but nothing else happens after that. Is there
> something I'm missing, such as a file extension or permission or something?
>

You need to make it executable, I think.
In terminal, change directory to the location of this text file, then type

chmod +x [filename]

That should do it, I think

> You need to make it executable, I think.
> In terminal, change directory to the location of this text file, then type
>
> chmod +x [filename]
>
> That should do it, I think
>

Ah, got it. I had been launching BOINC with Applescript, like this:
******************************
tell application "Terminal"
activate
do script "cd /Applications/BOINC/; /Applications/BOINC/BOINC" in window 1
end tell
******************************

Same difference, I guess.