My latest run on Monday the 4 cores were all brought into use at all times but only one at a time would reach 100%. The whole installation took two hours on the RPi4 4GB and incidentally four hours on the RPi3B+.
So how do I update your script that is already on my rpi, I know how to “git pull” in the Kstars folder to update that but how do I update the actual script I already have downloaded....just run “git pull” in the AstroPI3 folder..?.
oh yes absolutely. git pull is the method to update the script to the latest version since it is a git repo. The system update script should do that as well, but if you just want to update the script, git pull is the way to go.
I also fixed a samba issue yesterday. The Raspbian script was using the method I used to get samba working on an ubuntu system. But really it needed the method I used on Manjaro since the needed packages were not all in apt. Also the method I used on Manjaro was simpler, and I think I might just change all of them to go that route. . . So I changed the samba setup for raspbian. You will get all the recent updates by doing a git pull.
Was this during the make commands when it was building the astro software? And did you update the script to the latest version first? It does seem to be much faster since this change.[/quote]
Sorry - I now remember cronky wasn’t running during the make process! Apologies.
A option that I think would be good for this script, is to be able to chose between installing the latest nightly Kstars or the stable version, as personally I prefer the stable versions... but that is not a criticism at all as the script is superb..
Before, we disabled all drive mounting to allow DSLRs to connect with a config file, but the camera mounting should now be disabled in a different way, so you should be able to delete this file now.