Date   
Re: Spots window is always behind log page at startup

Michael Herron
 

Thanks. All back to the way I want it to be now.
Mike K7MH.

On Dec 17, 2019, at 3:43 AM, Bob <k4cy@...> wrote:


Mike, The DX Spots Window and the Logbook Page window are both MDI Child Windows (they can't be positioned outside the main Logger32 Window. As child windows their on-top position is relative and transient. The last opened window appears on-top, but putting the focus on a not on-top child window makes it on-top. So, in your case, So, in your example, the DX Spots Window is opened before the Logbook Page Window. While the best solution is size/position the child windows side by side so that all are visible, try this - Close the Logbook Page Window and the DX Spot Window (in any order. Now open the Logbook Page Window and then the DX Spot Window (in the order I said). Close Logger32. Open Logger32. Is the DX Spot Window on-top of the Logbook Page Window? SeventyThree(s).

On December 16, 2019 at 11:45 PM Michael Herron <k7mh@...> wrote:

Should my spots window always be behind the log page on startup  of the program? I have tried to lock it to the log entry window but it still does it. I  am not sure if it is just that way or not. 

It seems to me that some time ago I had it so that on startup, both the log entry and spots windows would always be on top of the log page. 

Mike K7MH.


 

Re: Latest TQSL Update does not allow L32LogSynch to open

Gary Hinson
 

Ouch

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 18 December 2019 07:19
To: hamlogger@groups.io
Subject: Re: [hamlogger] Latest TQSL Update does not allow L32LogSynch to open

 

More dangerous than crawling around on an active volcano taking selfies?  SeventyThree(s).

On December 17, 2019 at 12:14 PM Gary Hinson <Gary@...> wrote:

Another option is to run Logger32, L32LogSynch and tQSL as a normal user, not admin.  None of them need admin rights for normal everyday activities … but, at present*, Logger32’s occasional automatic updates fail at the final step: it does the backups and downloads and unpacks the updates correctly but can’t then replace the Logger32.exe & other files in the program directory.  I simply do that last bit manually and relaunch Logger32.  Alternatively I could give Logger32 admin rights temporarily just to complete its update, then revert to non-admin for normal use.

 

Resetting the system clock is another activity that I think needs admin rights but I use Meinberg NTP to keep my clock accurate so that doesn’t affect my use of Logger32.

 

As an information security pro by day, I cringe when I see people recommending others to run stuff with admin rights, or exclude stuff from antivirus, or skip backups, or otherwise disable system security controls.  For me, it’s the equivalent of “Go play in the street, kids” or “Do you get a tingle when you lick the socket?”! 

 

73

Gary   ZL2iFB

 

* Most programs update themselves automatically without needing admin rights.  Clearly it can be done … but would require changes to Logger32’s updater.

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: 18 December 2019 03:57
To: hamlogger@groups.io
Subject: Re: [hamlogger] Latest TQSL Update does not allow L32LogSynch to open

 

If you run Logger32 using the “Run as Administrator setting than any other program that connects to it needs to be run using the same setting. Once you have set LogSync to run that way then TQSL needs to be set that way. The author of Tqsl doesn’t think that a program needs to be run as Administrator ever but the way Microsoft has setup security there are times it needs to setup up that way for programs to talk to each other. Just set TQSL to use the Run as Administrator setting and everything will be ok.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jeff Wilson via Groups.Io
Sent: Monday, December 16, 2019 4:08 PM
To: hamlogger@groups.io
Subject: [hamlogger] Latest TQSL Update does not allow L32LogSynch to open

 

A couple of days ago (Dec 13) I got a TQSL Update popup and installed it.
It says to NOT run in administrator mode.  So I did this in the properties/compatibility
tab and made sure the option was unchecked.  But now every time I Open L32,
the L32LogSync starts to open then stops at a mostly blank L32LogSync window.
I have to move this window out of the way to see another popup that says do NOT
open TQSL in Admin mode and then gives 3 options:

Exit TQSL so I can re-run as a normal user.
Allow TQSL to continue this time.

Always allow running as Administrator.

So I click "Allow TQSL to continue this time" and everything works as it did before
the TQSL Update.


Latest L32LogSync update is installed and L32LogSync is set to open as Admin.
Has been working flawlessly until this TQSL Update.
Changing L32LogSync to also NOT run as Admin did not solve the problem.


Are other seeing this or what did I do wrong?
I will try reinstalling TQSL as I did set the update installer to open as Admin.

Thanks
Jeff VE3CV

 

 

 


 

Re: Latest TQSL Update does not allow L32LogSynch to open

Bob
 

More dangerous than crawling around on an active volcano taking selfies?  SeventyThree(s).

On December 17, 2019 at 12:14 PM Gary Hinson <Gary@...> wrote:

Another option is to run Logger32, L32LogSynch and tQSL as a normal user, not admin.  None of them need admin rights for normal everyday activities … but, at present*, Logger32’s occasional automatic updates fail at the final step: it does the backups and downloads and unpacks the updates correctly but can’t then replace the Logger32.exe & other files in the program directory.  I simply do that last bit manually and relaunch Logger32.  Alternatively I could give Logger32 admin rights temporarily just to complete its update, then revert to non-admin for normal use.

 

Resetting the system clock is another activity that I think needs admin rights but I use Meinberg NTP to keep my clock accurate so that doesn’t affect my use of Logger32.

 

As an information security pro by day, I cringe when I see people recommending others to run stuff with admin rights, or exclude stuff from antivirus, or skip backups, or otherwise disable system security controls.  For me, it’s the equivalent of “Go play in the street, kids” or “Do you get a tingle when you lick the socket?”! 

 

73

Gary   ZL2iFB

 

* Most programs update themselves automatically without needing admin rights.  Clearly it can be done … but would require changes to Logger32’s updater.

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: 18 December 2019 03:57
To: hamlogger@groups.io
Subject: Re: [hamlogger] Latest TQSL Update does not allow L32LogSynch to open

 

If you run Logger32 using the “Run as Administrator setting than any other program that connects to it needs to be run using the same setting. Once you have set LogSync to run that way then TQSL needs to be set that way. The author of Tqsl doesn’t think that a program needs to be run as Administrator ever but the way Microsoft has setup security there are times it needs to setup up that way for programs to talk to each other. Just set TQSL to use the Run as Administrator setting and everything will be ok.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jeff Wilson via Groups.Io
Sent: Monday, December 16, 2019 4:08 PM
To: hamlogger@groups.io
Subject: [hamlogger] Latest TQSL Update does not allow L32LogSynch to open

 

A couple of days ago (Dec 13) I got a TQSL Update popup and installed it.
It says to NOT run in administrator mode.  So I did this in the properties/compatibility
tab and made sure the option was unchecked.  But now every time I Open L32,
the L32LogSync starts to open then stops at a mostly blank L32LogSync window.
I have to move this window out of the way to see another popup that says do NOT
open TQSL in Admin mode and then gives 3 options:

Exit TQSL so I can re-run as a normal user.
Allow TQSL to continue this time.

Always allow running as Administrator.

So I click "Allow TQSL to continue this time" and everything works as it did before
the TQSL Update.


Latest L32LogSync update is installed and L32LogSync is set to open as Admin.
Has been working flawlessly until this TQSL Update.
Changing L32LogSync to also NOT run as Admin did not solve the problem.


Are other seeing this or what did I do wrong?
I will try reinstalling TQSL as I did set the update installer to open as Admin.

Thanks
Jeff VE3CV

 

 



 

ERROR 6

David Bonnet
 

HI
I have this pop-up, anyone can help me please?

error on line 208
error 6 overflow in procedur radio frequency holder_change of form MDIForm1

thanks
73 david F8CRS

Re: Latest TQSL Update does not allow L32LogSynch to open

Gary Hinson
 

Another option is to run Logger32, L32LogSynch and tQSL as a normal user, not admin.  None of them need admin rights for normal everyday activities … but, at present*, Logger32’s occasional automatic updates fail at the final step: it does the backups and downloads and unpacks the updates correctly but can’t then replace the Logger32.exe & other files in the program directory.  I simply do that last bit manually and relaunch Logger32.  Alternatively I could give Logger32 admin rights temporarily just to complete its update, then revert to non-admin for normal use.

 

Resetting the system clock is another activity that I think needs admin rights but I use Meinberg NTP to keep my clock accurate so that doesn’t affect my use of Logger32.

 

As an information security pro by day, I cringe when I see people recommending others to run stuff with admin rights, or exclude stuff from antivirus, or skip backups, or otherwise disable system security controls.  For me, it’s the equivalent of “Go play in the street, kids” or “Do you get a tingle when you lick the socket?”! 

 

73

Gary   ZL2iFB

 

* Most programs update themselves automatically without needing admin rights.  Clearly it can be done … but would require changes to Logger32’s updater.

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: 18 December 2019 03:57
To: hamlogger@groups.io
Subject: Re: [hamlogger] Latest TQSL Update does not allow L32LogSynch to open

 

If you run Logger32 using the “Run as Administrator setting than any other program that connects to it needs to be run using the same setting. Once you have set LogSync to run that way then TQSL needs to be set that way. The author of Tqsl doesn’t think that a program needs to be run as Administrator ever but the way Microsoft has setup security there are times it needs to setup up that way for programs to talk to each other. Just set TQSL to use the Run as Administrator setting and everything will be ok.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jeff Wilson via Groups.Io
Sent: Monday, December 16, 2019 4:08 PM
To: hamlogger@groups.io
Subject: [hamlogger] Latest TQSL Update does not allow L32LogSynch to open

 

A couple of days ago (Dec 13) I got a TQSL Update popup and installed it.
It says to NOT run in administrator mode.  So I did this in the properties/compatibility
tab and made sure the option was unchecked.  But now every time I Open L32,
the L32LogSync starts to open then stops at a mostly blank L32LogSync window.
I have to move this window out of the way to see another popup that says do NOT
open TQSL in Admin mode and then gives 3 options:

Exit TQSL so I can re-run as a normal user.
Allow TQSL to continue this time.

Always allow running as Administrator.

So I click "Allow TQSL to continue this time" and everything works as it did before
the TQSL Update.


Latest L32LogSync update is installed and L32LogSync is set to open as Admin.
Has been working flawlessly until this TQSL Update.
Changing L32LogSync to also NOT run as Admin did not solve the problem.


Are other seeing this or what did I do wrong?
I will try reinstalling TQSL as I did set the update installer to open as Admin.

Thanks
Jeff VE3CV

 

Re: Latest TQSL Update does not allow L32LogSynch to open

Rick Ellison
 

If you run Logger32 using the “Run as Administrator setting than any other program that connects to it needs to be run using the same setting. Once you have set LogSync to run that way then TQSL needs to be set that way. The author of Tqsl doesn’t think that a program needs to be run as Administrator ever but the way Microsoft has setup security there are times it needs to setup up that way for programs to talk to each other. Just set TQSL to use the Run as Administrator setting and everything will be ok.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jeff Wilson via Groups.Io
Sent: Monday, December 16, 2019 4:08 PM
To: hamlogger@groups.io
Subject: [hamlogger] Latest TQSL Update does not allow L32LogSynch to open

 

A couple of days ago (Dec 13) I got a TQSL Update popup and installed it.
It says to NOT run in administrator mode.  So I did this in the properties/compatibility
tab and made sure the option was unchecked.  But now every time I Open L32,
the L32LogSync starts to open then stops at a mostly blank L32LogSync window.
I have to move this window out of the way to see another popup that says do NOT
open TQSL in Admin mode and then gives 3 options:

Exit TQSL so I can re-run as a normal user.
Allow TQSL to continue this time.

Always allow running as Administrator.

So I click "Allow TQSL to continue this time" and everything works as it did before
the TQSL Update.


Latest L32LogSync update is installed and L32LogSync is set to open as Admin.
Has been working flawlessly until this TQSL Update.
Changing L32LogSync to also NOT run as Admin did not solve the problem.


Are other seeing this or what did I do wrong?
I will try reinstalling TQSL as I did set the update installer to open as Admin.

Thanks
Jeff VE3CV

 

Re: Spots window is always behind log page at startup

Bob
 

Mike, The DX Spots Window and the Logbook Page window are both MDI Child Windows (they can't be positioned outside the main Logger32 Window. As child windows their on-top position is relative and transient. The last opened window appears on-top, but putting the focus on a not on-top child window makes it on-top. So, in your case, So, in your example, the DX Spots Window is opened before the Logbook Page Window. While the best solution is size/position the child windows side by side so that all are visible, try this - Close the Logbook Page Window and the DX Spot Window (in any order. Now open the Logbook Page Window and then the DX Spot Window (in the order I said). Close Logger32. Open Logger32. Is the DX Spot Window on-top of the Logbook Page Window? SeventyThree(s).

On December 16, 2019 at 11:45 PM Michael Herron <k7mh@...> wrote:

Should my spots window always be behind the log page on startup  of the program? I have tried to lock it to the log entry window but it still does it. I  am not sure if it is just that way or not. 

It seems to me that some time ago I had it so that on startup, both the log entry and spots windows would always be on top of the log page. 

Mike K7MH.


 

Spots window is always behind log page at startup

Michael Herron
 

Should my spots window always be behind the log page on startup  of the program? I have tried to lock it to the log entry window but it still does it. I  am not sure if it is just that way or not. 

It seems to me that some time ago I had it so that on startup, both the log entry and spots windows would always be on top of the log page. 

Mike K7MH.

Latest TQSL Update does not allow L32LogSynch to open

Jeff Wilson
 

A couple of days ago (Dec 13) I got a TQSL Update popup and installed it.
It says to NOT run in administrator mode.  So I did this in the properties/compatibility
tab and made sure the option was unchecked.  But now every time I Open L32,
the L32LogSync starts to open then stops at a mostly blank L32LogSync window.
I have to move this window out of the way to see another popup that says do NOT
open TQSL in Admin mode and then gives 3 options:

Exit TQSL so I can re-run as a normal user.
Allow TQSL to continue this time.
Always allow running as Administrator.

So I click "Allow TQSL to continue this time" and everything works as it did before
the TQSL Update.

Latest L32LogSync update is installed and L32LogSync is set to open as Admin.
Has been working flawlessly until this TQSL Update.
Changing L32LogSync to also NOT run as Admin did not solve the problem.


Are other seeing this or what did I do wrong?
I will try reinstalling TQSL as I did set the update installer to open as Admin.

Thanks
Jeff VE3CV


Re: ham cap does not memorize lat+lon under L32

ic8pof
 

HI Bob tnx fer info, I have forgotten to that part ;-) , all ok
73
Phil

Re: ham cap does not memorize lat+lon under L32

Bob
 

The Logger32 settings for your QTH are used by HamCap. On the Logbook entry Window right click on the Callsign field. Click SETUP. Click MY QTH LAT/LONG. SeventyThree(s).

On December 11, 2019 at 12:57 PM "ic8pof via Groups.Io" <ic8pof@...> wrote:

HI All  after having passed to win10-64b from w7-32b  I am experiencing an issue in the HAM CAP v 191
as it does not mantain the LAT&LONG values I enter in the settings window.
The ham-cap ini file has not indications in degrees so I do not know how to change manually.
Have you any suggestion please.
73
Phil IC8POF

 

ham cap does not memorize lat+lon under L32

ic8pof
 

HI All  after having passed to win10-64b from w7-32b  I am experiencing an issue in the HAM CAP v 191
as it does not mantain the LAT&LONG values I enter in the settings window.
The ham-cap ini file has not indications in degrees so I do not know how to change manually.
Have you any suggestion please.
73
Phil IC8POF

Test

John Pink
 

Please ignore!

testing my email

larry fields
 

For some reason not seeing emails here to the groups so please disregard.

Thanks and 73
Larry Fields: du1/n6hpx
Manila PHILIPPINES
n6hpx/du1@...

Retired looking for more work
Office:(63)46-571-5687
cell:    (63)916-756-7781
=====================================================
member:
American Radio Relay League W1AW
Philippine Amatuer Radio Association DX1PAR
Philippine Radio Pyramid Society DX1PRS 
=====================================================
owner:
=======================================================
LICENSED HAM RADIO OP:
DX1PRS GROUP 145.340 mhz & 7165 khz
DX1PAR HF NET  7095.00 khz
(0900,1100 & 2300 utc)
========================================================
DU1/N6HPX:QRX DX1PAR 7095
DX1PRS 7165 khz evening
DX1PRS 145.340 mhz
DX1L 431.9,
SIMPLEX 144.6, 145.600
2M 144.225 SSB ,
APRS n6hpx(-08)
=============================================================
SATELLITE:
APRS N6HPX-2 GATEWAY











Anyone in Marion County Florida a subscriber here?

Bob
 

If you are in Marion County (or an adjacent County) and have experience with tower ordinances/permissions, please eMail me directly at k4cy@...  Apologies for the bandwidth. SeventyThree(s).

Re: Help file corrections

Hew Lines
 

Many thanks Jim. That is exactly the type of issue I am looking for. I can't keep track of link changes myself, there are simply TOO MANY of them :-)). Leting me know of any you guys find  enables me to fix them one at a time.

73 Hew VA7HU


On 12/8/2019 2:45 PM, Jim Altman wrote:

DX Spots Window

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Sunday, December 8, 2019 5:04 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Help file corrections

 

Jim

Which topic are you referring to ?

73

On 2019/12/09 5:42, Jim Altman wrote:

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

Re: Auto-update version 3.50.403

larry fields
 

is the updater always slow down loading seems to take a while to finish

Thanks and 73
Larry Fields: du1/n6hpx
Manila PHILIPPINES
n6hpx/du1@...

Retired looking for more work
Office:(63)46-571-5687
cell:    (63)916-756-7781
=====================================================
member:
American Radio Relay League W1AW
Philippine Amatuer Radio Association DX1PAR
Philippine Radio Pyramid Society DX1PRS 
=====================================================
owner:
=======================================================
LICENSED HAM RADIO OP:
DX1PRS GROUP 145.340 mhz & 7165 khz
DX1PAR HF NET  7095.00 khz
(0900,1100 & 2300 utc)
========================================================
DU1/N6HPX:QRX DX1PAR 7095
DX1PRS 7165 khz evening
DX1PRS 145.340 mhz
DX1L 431.9,
SIMPLEX 144.6, 145.600
2M 144.225 SSB ,
APRS n6hpx(-08)
=============================================================
SATELLITE:
APRS N6HPX-2 GATEWAY











Re: Help file corrections

ja1nlx
 

Jim

Thanks. We will correct these in the next update.

73

On 2019/12/09 7:45, Jim Altman wrote:

DX Spots Window

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Sunday, December 8, 2019 5:04 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Help file corrections

 

Jim

Which topic are you referring to ?

73

On 2019/12/09 5:42, Jim Altman wrote:

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

Re: Help file corrections

Jim Altman
 

DX Spots Window

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Sunday, December 8, 2019 5:04 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Help file corrections

 

Jim

Which topic are you referring to ?

73

On 2019/12/09 5:42, Jim Altman wrote:

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

Re: Help file corrections

ja1nlx
 

Jim

Which topic are you referring to ?

73

On 2019/12/09 5:42, Jim Altman wrote:

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX