Thanks. This is the third time I've tried to respond to your helpful reply. But I can't see anything from me appearing in the forum, apart from my initial query.
Turned it to be
raspberrypi_password

Sent from my SM-A505FN using Tapatalk

Thanks for all the work. I installed the scripts on a Rock64 with Debian and it works great over the network after I created a share for file transfer.
My only problem is can not find a VNC viewer I understand which will enable direct Ethernet cable access for a win10 computer to the Rock64.

I'm configuring a setup from a clean install of Raspberry OS (64bit) and found KStars Master will not compile unless I built and installed stellarsolver first. Therefore this step should be added to the script.
Also, if you have a chance, Please add Firecapture and OaCapture to setup. I have had difficulty installing them myself.
Thank you kindly.

in which script is this a problem, the raspbian one?

Yes, the raspbian script that must build kstars from source.
With the inclusion of Stellarsolver in the master, it will not build without Stellarsolver installed first as cmake looks for references to it.

Ok I updated it and ran a test, it appears to work now

I have to add I have been able to connect to Rock 64 Debian with real VNC viewer over the network from the script installation. After some additional work I have been able to connect directly to the Share on the Rock64 with a direct Ethernet link. But x11 still throws me out attempting any VNC viewing through direct Ethernet link.
Any ideas how to modify X11 install to accept direct Ethernet link VNC viewer with password.?
Ray.

Hello,

I just read a reply the 64 bit question which said, if and only if Raspberry PI 4 8G. What is the compelling reason? Are vendor products turning ARM64? Or are Linux ARM64 packages pushing the need?

So there are advantages and drawbacks to using 64 bit vs 32 bit. In a program with 64 bit, you can have larger sized variables (64 bit in fact), so if you have enormous numbers you are working with and don't really want to use double or float, like if you have a huge integer and every digit is significant. You can handle larger chunks of memory addresses in your code at once because the pointer or index you use to access that memory can have a larger value. The same could be said for hard drives and accessing files on larger systems. If a program needs to use large variables or if it is set up to handle/access larger chunks of memory or hard disk space at once on a 64 bit system, then you might see an advantage. But there also could be a cost, depending on how the program is designed, since if you have a 64 bit integer, that takes up twice as much memory as a 32 bit integer. So that part depends on the program, whether or not the programmer decided to use 32 or 64 bit int variables when 64 bit is available.

For the most part, KStars, INDI, and the imagers they use typically work with images that have numerical values for their pixels that are much much less. Some are 8 bits per pixel, some are 16 (mine is 16). So there is usually no need to use really large integers most of the time, and when we do, it would be just fine to use double or float in most cases. Certain processes on the computer could benefit from being able to address more than 4 GB of RAM at the same time, so you might see a performance benefit there if you have more than 4 GB of RAM on the system. But I doubt that you would have a hard disk large enough on a Pi to see any benefit from 64 bit in that area. Some programs might possibly do some calculations that require really big numbers and if it can use a 64 bit integer, it *might* try to take advantage of that to make the calculation go faster, but the program would need to be written in such a way to take advantage of that and this probably is not done all that often.

So yeah, I think the only case where you might see a benefit is in the ability to address more RAM at the same time, and that benefit only appears when you have more than 4 GB of RAM. And the increased cost of larger variables that some programs will use might take away some of that benefit too, but some might take advantage of the larger variables to make calculations faster. So that part is not certain.

I have bit of a hiccup building PHD Log Viewer on Raspberry OS (64bit), RPI4 8gb. Please advise.
Thank you kindly.

My Conky widget was not getting the CPU temperature. I found that vcgencmd was missing, but was easy to install.Then I found that it is installed in /usr/bin on this version of Linux and not /opt/vc/bin. So I edited my Conky config file accordingly and all is well on my end now.

I managed to get phdlogviewer to install, but not in the usual way.
I used Patrick's solution.I also found that the script generated symlink is different on my 64bit system.However even with that change, I still had issues with this error.Regardless, with Patrick's solution, the entire WxFormBuilder portion can probably be removed entirely from the Raspbian setup script.