StarTools

Hi!

I'm an astrophoto noob. The only thing I know less about is Linux/Ubuntu.

I'm running 64-bit Ubuntu 12.04 LTS in a VMWare Fusion virtual machine on a Mac Mini host running Mavericks. I tried placing StarTools and the resources file (with read-write permissions set for both) in the /usr/share/applications folder and the /.local/share/ folder, as well as in a folder on the desktop. I'm able to run the program from the command line in all three locations with no problems.

My difficulty comes in trying to create a launcher for StarTools on the desktop. No matter where I put the program, when I try to run it from the launcher, I get an error saying that StarTools can't find the resources file or the permissions on the resources file are not set (even though they are).

I'm sure it's something really simple (like adding an argument to the launcher command), but I don't know what to do. Can anyone assist?

Thanks!
-D

Hi,

Try this;

On your desktop, right click and select 'Create Launcher'. Give it a name (e.g. 'StarTools').
Then for command, input the following;

bash -c "cd /home/user/whateverlocation/StarTools/distro/ && ./StarTools-Linux64"

Fill in the location of the StarTools executable for "/home/user/whateverlocation/StarTools/distro/" obviously...
What this does is execute two commands at once (separated by the &&); first it changes the working directory to the specified directory using cd, and then it launches the StarTools executable.
This should (hopefully) do the job.
Do let me know if you have any trouble!

Hi, Ivo:

That worked...thanks!

-David

Hi
I am having the same error message re resources not found, though in my case when running StarTools 64 bit on Windows 10.
The 32 bit version is loading fine, but I have instelled Windows 10 64 bit in order to use the 64 bit version of StarTools.
Any help greatly appreaciated.

Found another post on this so will try and see if it will run if I manually copy the files.
This also didn't work.

I then placed the files on the Desktop and it worked, so probably path related but anyway it's working now.

It may be a permissions thing; the resources file (and the folder it is located in) needs read/write permission...