Saturday, July 18, 2026

How to Restore HamClock - Inovato Quadra HamClock migration to the new server -

 


HamClock is alive on a new server. If you are on the old server, the hamclock could be deprecated at any time. I followed the standard instructions but started losing space weather updates and looked into to the problem. The information/instructions on the hamclock.com website for migrating didn't work because a reboot resulted in the new server address being overwritten. This is because a script called "runner" is what actually opens the program and sets the parameters. This script must be modified for the program to boot to the new server. Note that the terminal program uses up down arrow keys to move the cursor for editing, not a mouse.

Here is the process I used. 

Click on the lock icon to the right of the date and exit the program. 

Open the terminal program by clicking on the terminal icon. After the $ sign, type: sudo nano /usr/local/bin/hamclock-runner. This will open the runner script and allow it to be edited.

Locate this line: exec=$(hamclock -f on). Change it to exactly this:

exec=$(hamclock -b hamclock.com:80 -f on)

Scroll down and locate the Launch Command "exec=$(hamclock-4k -f on). Change it to exactly this:

exec=$(hamclock-4k -b hamclock.com:80 -f on) 

Press Ctrl + O to save the file

Hit Enter to confirm the file name

Press Ctrl + X to exit the nano editor

Fire up HamClock

Once you close the editor, you can test it immediatly by clickin the hamclock icon. 


I want to acknowledge WB0OEW (sk) for developing the program and Bruce W4BAE and team for migrating it to a new server. This is a GREAT program!





Creating Goggle Gmail App Password for Less Secure Apps - Solved

On September 30, 2024, Google pulled the plug on "less secure apps"—and just like that, one of the email accounts connected to my main inbox stopped working. Same thing happened to my co-workers. Frustrating? Absolutely. And to make things worse, Google’s help docs on this issue have been... let’s just say, not very helpful.

If you're in the same boat and have been tearing your hair out trying to fix it (been there), I’m sharing what finally worked for me—hopefully it helps you too.


Here is the process for adding a "less secure" email account to gmail:

Log into a gmail (or google workplace) account you want to add to your primary. ie zsmith@workplace.com

Go to manage account and click on security.

Add two factor verification.  NOTE: 2F must be turned on for app pw option to appear!

Once added, return to two factor and select app passwords.

Name the app password, i.e. "NGO email" and click create.

Save the 16 digit app password. The spaces must be removed.

Log into your primary gmail account i.e. jsmith@gmail.com

Click on settings (gear icon).

Select accounts> send mail as> add another email address

In the pop up window enter smtp.gmail.com; your NGO email address, port 587, and TLS security. Enter the 16 digit app password (no spaces) instead of your NGO gmail password. "Enter" should provide an email sent notice.

Respond "confirm" to the confirmation email sent to your NGO email.

You should now be able to respond to incoming NGO emails with your @NGO email address automatically (assuming that you have set your NGO account to forward incoming mail to your primary account). 

I suspect there are others who would like to implement this process as it obviates the need to bounce between two accounts.