Forums | MacLife

Hi & welcome

Hmm.  I don't use SetiDockling to control s@h, just to monitor progress, but  let's check a couple of things.

Your last statement puzzles me:

On another similar note, is there anyway to move the SETI files out of my "home" folder and into the SETI@HomeCLI folder?

You're saying that user_info.sah, pid.sah, work_unit.sah, state.sah, etc. are in your user (home) directory instead of the same directory as the s@h program?  If so, that would definately explain why SetiDockling isn't showing any information.  In case you didn't know, progression, etc. are in the state.sah file, which s@h updates every minute or so.

As for why s@h is creating it's files where it is, it sounds like SetiDockling isn't setting the directory before running the program.

First question(s), what user did you install s@h as?  Is it the same as the user you're currently logged in as?  is this an Administrative user?

Second, did you run s@h once manually, to set up your account with the program?

I don't check here every day, but let us know and I'll answer or someone else will chime in

Hey man,

I ran seti at home CLI first to set it up, then while the Terminal was still running I started up SetiDockling. Set up the preferences and what not.

Then I restarted the machine and started up SetiDockling and told it to start and process indefinitely.

That should run the instance through SetiDockling. I had to play around with it for a bit. Make sure that in the preferences the File path to Setiathome CLI is correct, otherwise it creates the sah files in the home directory.