On 09/06/2022 9:55 PM Bob Helms <bob6wire@...> wrote:

Bob,

Let me provide some more info on the error I'm getting. According to the Windows Event Log it is a Event ID 1001 error.  See  https://qa.social.technet.microsoft.com/wiki/contents/articles/3115.event-id-1001-windows-error-reporting.aspx

Here's the Event Log details in XML of one of my attempts to run Logger32:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Windows Error Reporting" />

  <EventID Qualifiers="0">1001</EventID>

  <Version>0</Version>

  <Level>4</Level>

  <Task>0</Task>

  <Opcode>0</Opcode>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2022-09-06T22:29:11.0210421Z" />

  <EventRecordID>59506</EventRecordID>

  <Correlation />

  <Execution ProcessID="0" ThreadID="0" />

  <Channel>Application</Channel>

  <Computer>TT</Computer>

  <Security />

  </System>

- <EventData>

  <Data>1688371320123507508</Data>

  <Data>1</Data>

  <Data>APPCRASH</Data>

  <Data>Not available</Data>

  <Data>0</Data>

  <Data>Logger32.exe</Data>

  <Data>4.0.0.289</Data>

  <Data>61d070a7</Data>

  <Data>StackHash_45b8</Data>

  <Data>0.0.0.0</Data>

  <Data>00000000</Data>

  <Data>c000041d</Data>

  <Data>PCH_D6_FROM_unknown+0x00000000</Data>

  <Data />

  <Data />

  <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9636.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97DD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER982C.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9859.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER98E7.tmp.txt</Data>

  <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Logger32.exe_6432e5498b18ac456dec6a91ed9571940bd021_a1ee11c6_7dd8d40b-0b87-4fc8-b6ed-6134f9e84d50</Data>

  <Data />

  <Data>0</Data>

  <Data>895bb3df-9bb6-44bc-a50a-df5bf8f18d2a</Data>

  <Data>268435456</Data>

  <Data>ea0f93b94e66b456176e4cc530eb4334</Data>

  <Data>0</Data>

  </EventData>

  </Event>

On 09/06/2022 5:57 PM Bob Helms <bob6wire@...> wrote:

I'm unable to get v4.0.289 full install to run on Win 10 Home V21H2 with

16 GB DRAM. I'm using C:\Logger32 for folder and have set Logger32.exe,

Logger32autoinstaller.exe and autoinstaller.exe all to run as administrator.

The download and install (English language selected) showed no errors

but when I start Logger32 by double-clicking the desktop icon I see the

'splash screen' with version number and US English menus loaded followed

by the main Logger32 screen for a couple of seconds the then all windows

close without any errors visible and nothing is shown to be running in

the Windows task manager.

This PC has never had Logger32 on it and I haven't created a logbook on

it yet. I've been using Logger32 under Windows 7 on another PC for 2+

decades.

I've attached a 'Logger32 v4.0.289 won't run.jpg' screen grab.

Thanks in advance for help on how to correct this.

Bob, AF5Z

On 09/06/2022 5:57 PM Bob Helms <bob6wire@...> wrote:


I'm unable to get v4.0.289 full install to run on Win 10 Home V21H2 with
16 GB DRAM. I'm using C:\Logger32 for folder and have set Logger32.exe,
Logger32autoinstaller.exe and autoinstaller.exe all to run as administrator.

The download and install (English language selected) showed no errors
but when I start Logger32 by double-clicking the desktop icon I see the
'splash screen' with version number and US English menus loaded followed
by the main Logger32 screen for a couple of seconds the then all windows
close without any errors visible and nothing is shown to be running in
the Windows task manager.

This PC has never had Logger32 on it and I haven't created a logbook on
it yet. I've been using Logger32 under Windows 7 on another PC for 2+
decades.

I've attached a 'Logger32 v4.0.289 won't run.jpg' screen grab.

Thanks in advance for help on how to correct this.

Bob, AF5Z

My 3A6M log has no operator.
When trying to open it, I am asked to give an operator callsign. I enter 3A6M.
The log is EMPTY, and shows no QSO....

When I say this operaor callsign business only give problems, here is another example....

Now, how do I get my 3A6M log back.... ??

Paul F6EXV

On 09/06/2022 11:35 AM mm0eax via groups.io <mm0eax@...> wrote:

Hello All
Im using latest version of L32, I cant view USACA by (LoTW & QSL) like i can other awards?? Only option i get is EQSL, QSL or Both. Help file says (And gives example) that clearly shows (LoTW & QSL) as an option. As far as i can see i have all setup ok can anyone help please??

Regards MM0EAX

On 2022/09/05 17:12:40, Lee W4EIS <2thkeeper@...> wrote:

GOT IT!!!!!

Thank you!

Al mal tiempo, buena cara

On Sep 5, 2022, at 3:08 AM, ja1nlx <ayoshida0205@...> wrote:



Lee

This is DX spot window (not DX Call window)

If you do not see this window then

Click "View" in main menu and click "Show DX spots"

73 de aki

JA1NLX

On 2022/09/05 17:00:17, Lee W4EIS <2thkeeper@...> wrote:

Be easy with me but can you tell me where or how to access the DX Call Window

Thank you for your early morning support

Al mal tiempo, buena cara

On Sep 5, 2022, at 2:04 AM, ja1nlx <ayoshida0205@...> wrote:



Lee

Right-click on DX spot window, click Setup, then click Tooltips.

73 de aki

JA1NLX

On 2022/09/05 16:01:30, Lee W4EIS <2thkeeper@...> wrote:

I give up. Searched tooltips fonts, right clicked on different windows on status bar and DX bar and never can see how to change tooltip font size 

Al mal tiempo, buena cara

On Sep 4, 2022, at 4:34 PM, Bob <k4cy@...> wrote:



No, it is fixed. You can adjust the font size of the tooltips, So, if the text in the status bars it too small, just set the tooltips to a large font size and move the mouse over the unreadable field on the status bar and read the tooltips. SeventyThree(s).

On 09/04/2022 5:21 PM Lee W4EIS <2thkeeper@...> wrote:

Finally figured it out 

Question:  got the visually impaired, is there a way to increase the size of the status bar?

Al mal tiempo, buena cara

On Sep 2, 2022, at 12:30 PM, Bob <k4cy@...> wrote:

If the callsign entered is recognized as being valid the short/long path beam headings are calculated and shown. The want/need status has no bearing (no pun intended) on if the heading is shown or not.

When calculating beam headings for US Stations, several factors are taken into consideration. First we look for a gridsquare and use that. If no gridsquare is found then the US County is used for the calculation. If no County is found then the US State is used for the calculation. If no State is found then Logger32 crosses its fingers and uses the standard US call district as the basis for calculation.

SeventyThree(s).

On 09/02/2022 1:04 PM Lee W4EIS <2thkeeper@...> wrote:

Bob

That line shows  “Not credited for DXCC_MIXED”. Will it not pull directions for a US station?

Al mal tiempo, buena cara

On Sep 2, 2022, at 7:38 AM, Bob <k4cy@...> wrote:

With a callsign in the logbook entry window, you can see the short/long path headings here. SeventyThree(s).

On 09/02/2022 8:07 AM Lee W4EIS <2thkeeper@...> wrote:

I have Logger32 linked to my QRZ account. I can’t see how to determine the short distance from my QTH to station being worked so I can adjust my rotor direction

Suggestion?

Lee

W4EIS 

Al mal tiempo, buena cara

On Sep 5, 2022, at 3:08 AM, ja1nlx <ayoshida0205@...> wrote:



Lee

This is DX spot window (not DX Call window)

If you do not see this window then

Click "View" in main menu and click "Show DX spots"

73 de aki

JA1NLX

On 2022/09/05 17:00:17, Lee W4EIS <2thkeeper@...> wrote:

Be easy with me but can you tell me where or how to access the DX Call Window

Thank you for your early morning support

Al mal tiempo, buena cara

On Sep 5, 2022, at 2:04 AM, ja1nlx <ayoshida0205@...> wrote:



Lee

Right-click on DX spot window, click Setup, then click Tooltips.

73 de aki

JA1NLX

On 2022/09/05 16:01:30, Lee W4EIS <2thkeeper@...> wrote:

I give up. Searched tooltips fonts, right clicked on different windows on status bar and DX bar and never can see how to change tooltip font size 

Al mal tiempo, buena cara

On Sep 4, 2022, at 4:34 PM, Bob <k4cy@...> wrote:



No, it is fixed. You can adjust the font size of the tooltips, So, if the text in the status bars it too small, just set the tooltips to a large font size and move the mouse over the unreadable field on the status bar and read the tooltips. SeventyThree(s).

On 09/04/2022 5:21 PM Lee W4EIS <2thkeeper@...> wrote:

Finally figured it out 

Question:  got the visually impaired, is there a way to increase the size of the status bar?

Al mal tiempo, buena cara

On Sep 2, 2022, at 12:30 PM, Bob <k4cy@...> wrote:

If the callsign entered is recognized as being valid the short/long path beam headings are calculated and shown. The want/need status has no bearing (no pun intended) on if the heading is shown or not.

When calculating beam headings for US Stations, several factors are taken into consideration. First we look for a gridsquare and use that. If no gridsquare is found then the US County is used for the calculation. If no County is found then the US State is used for the calculation. If no State is found then Logger32 crosses its fingers and uses the standard US call district as the basis for calculation.

SeventyThree(s).

On 09/02/2022 1:04 PM Lee W4EIS <2thkeeper@...> wrote:

Bob

That line shows  “Not credited for DXCC_MIXED”. Will it not pull directions for a US station?

Al mal tiempo, buena cara

On Sep 2, 2022, at 7:38 AM, Bob <k4cy@...> wrote:

With a callsign in the logbook entry window, you can see the short/long path headings here. SeventyThree(s).

On 09/02/2022 8:07 AM Lee W4EIS <2thkeeper@...> wrote:

I have Logger32 linked to my QRZ account. I can’t see how to determine the short distance from my QTH to station being worked so I can adjust my rotor direction

Suggestion?

Lee

W4EIS 

Al mal tiempo, buena cara

On 2022/09/05 17:00:17, Lee W4EIS <2thkeeper@...> wrote:

Be easy with me but can you tell me where or how to access the DX Call Window

Thank you for your early morning support

Al mal tiempo, buena cara

On Sep 5, 2022, at 2:04 AM, ja1nlx <ayoshida0205@...> wrote:



Lee

Right-click on DX spot window, click Setup, then click Tooltips.

73 de aki

JA1NLX

On 2022/09/05 16:01:30, Lee W4EIS <2thkeeper@...> wrote:

I give up. Searched tooltips fonts, right clicked on different windows on status bar and DX bar and never can see how to change tooltip font size 

Al mal tiempo, buena cara

On Sep 4, 2022, at 4:34 PM, Bob <k4cy@...> wrote:



No, it is fixed. You can adjust the font size of the tooltips, So, if the text in the status bars it too small, just set the tooltips to a large font size and move the mouse over the unreadable field on the status bar and read the tooltips. SeventyThree(s).

On 09/04/2022 5:21 PM Lee W4EIS <2thkeeper@...> wrote:

Finally figured it out 

Question:  got the visually impaired, is there a way to increase the size of the status bar?

Al mal tiempo, buena cara

On Sep 2, 2022, at 12:30 PM, Bob <k4cy@...> wrote:

If the callsign entered is recognized as being valid the short/long path beam headings are calculated and shown. The want/need status has no bearing (no pun intended) on if the heading is shown or not.

When calculating beam headings for US Stations, several factors are taken into consideration. First we look for a gridsquare and use that. If no gridsquare is found then the US County is used for the calculation. If no County is found then the US State is used for the calculation. If no State is found then Logger32 crosses its fingers and uses the standard US call district as the basis for calculation.

SeventyThree(s).

On 09/02/2022 1:04 PM Lee W4EIS <2thkeeper@...> wrote:

Bob

That line shows  “Not credited for DXCC_MIXED”. Will it not pull directions for a US station?

Al mal tiempo, buena cara

On Sep 2, 2022, at 7:38 AM, Bob <k4cy@...> wrote:

With a callsign in the logbook entry window, you can see the short/long path headings here. SeventyThree(s).

On 09/02/2022 8:07 AM Lee W4EIS <2thkeeper@...> wrote:

I have Logger32 linked to my QRZ account. I can’t see how to determine the short distance from my QTH to station being worked so I can adjust my rotor direction

Suggestion?

Lee

W4EIS 

Al mal tiempo, buena cara

On Sep 5, 2022, at 2:04 AM, ja1nlx <ayoshida0205@...> wrote:



Lee

Right-click on DX spot window, click Setup, then click Tooltips.

73 de aki

JA1NLX

On 2022/09/05 16:01:30, Lee W4EIS <2thkeeper@...> wrote:

I give up. Searched tooltips fonts, right clicked on different windows on status bar and DX bar and never can see how to change tooltip font size 

Al mal tiempo, buena cara

On Sep 4, 2022, at 4:34 PM, Bob <k4cy@...> wrote:



No, it is fixed. You can adjust the font size of the tooltips, So, if the text in the status bars it too small, just set the tooltips to a large font size and move the mouse over the unreadable field on the status bar and read the tooltips. SeventyThree(s).

On 09/04/2022 5:21 PM Lee W4EIS <2thkeeper@...> wrote:

Finally figured it out 

Question:  got the visually impaired, is there a way to increase the size of the status bar?

Al mal tiempo, buena cara

On Sep 2, 2022, at 12:30 PM, Bob <k4cy@...> wrote:

If the callsign entered is recognized as being valid the short/long path beam headings are calculated and shown. The want/need status has no bearing (no pun intended) on if the heading is shown or not.

When calculating beam headings for US Stations, several factors are taken into consideration. First we look for a gridsquare and use that. If no gridsquare is found then the US County is used for the calculation. If no County is found then the US State is used for the calculation. If no State is found then Logger32 crosses its fingers and uses the standard US call district as the basis for calculation.

SeventyThree(s).

On 09/02/2022 1:04 PM Lee W4EIS <2thkeeper@...> wrote:

Bob

That line shows  “Not credited for DXCC_MIXED”. Will it not pull directions for a US station?

Al mal tiempo, buena cara

On Sep 2, 2022, at 7:38 AM, Bob <k4cy@...> wrote:

With a callsign in the logbook entry window, you can see the short/long path headings here. SeventyThree(s).

On 09/02/2022 8:07 AM Lee W4EIS <2thkeeper@...> wrote:

I have Logger32 linked to my QRZ account. I can’t see how to determine the short distance from my QTH to station being worked so I can adjust my rotor direction

Suggestion?

Lee

W4EIS 

Al mal tiempo, buena cara

On 2022/09/05 16:01:30, Lee W4EIS <2thkeeper@...> wrote:

I give up. Searched tooltips fonts, right clicked on different windows on status bar and DX bar and never can see how to change tooltip font size 

Al mal tiempo, buena cara

On Sep 4, 2022, at 4:34 PM, Bob <k4cy@...> wrote:



No, it is fixed. You can adjust the font size of the tooltips, So, if the text in the status bars it too small, just set the tooltips to a large font size and move the mouse over the unreadable field on the status bar and read the tooltips. SeventyThree(s).

On 09/04/2022 5:21 PM Lee W4EIS <2thkeeper@...> wrote:

Finally figured it out 

Question:  got the visually impaired, is there a way to increase the size of the status bar?

Al mal tiempo, buena cara

On Sep 2, 2022, at 12:30 PM, Bob <k4cy@...> wrote:

If the callsign entered is recognized as being valid the short/long path beam headings are calculated and shown. The want/need status has no bearing (no pun intended) on if the heading is shown or not.

When calculating beam headings for US Stations, several factors are taken into consideration. First we look for a gridsquare and use that. If no gridsquare is found then the US County is used for the calculation. If no County is found then the US State is used for the calculation. If no State is found then Logger32 crosses its fingers and uses the standard US call district as the basis for calculation.

SeventyThree(s).

On 09/02/2022 1:04 PM Lee W4EIS <2thkeeper@...> wrote:

Bob

That line shows  “Not credited for DXCC_MIXED”. Will it not pull directions for a US station?

Al mal tiempo, buena cara

On Sep 2, 2022, at 7:38 AM, Bob <k4cy@...> wrote:

With a callsign in the logbook entry window, you can see the short/long path headings here. SeventyThree(s).

On 09/02/2022 8:07 AM Lee W4EIS <2thkeeper@...> wrote:

I have Logger32 linked to my QRZ account. I can’t see how to determine the short distance from my QTH to station being worked so I can adjust my rotor direction

Suggestion?

Lee

W4EIS 

Al mal tiempo, buena cara

On Sep 4, 2022, at 4:34 PM, Bob <k4cy@...> wrote:



No, it is fixed. You can adjust the font size of the tooltips, So, if the text in the status bars it too small, just set the tooltips to a large font size and move the mouse over the unreadable field on the status bar and read the tooltips. SeventyThree(s).

On 09/04/2022 5:21 PM Lee W4EIS <2thkeeper@...> wrote:

Finally figured it out 

Question:  got the visually impaired, is there a way to increase the size of the status bar?

Al mal tiempo, buena cara

On Sep 2, 2022, at 12:30 PM, Bob <k4cy@...> wrote:

If the callsign entered is recognized as being valid the short/long path beam headings are calculated and shown. The want/need status has no bearing (no pun intended) on if the heading is shown or not.

When calculating beam headings for US Stations, several factors are taken into consideration. First we look for a gridsquare and use that. If no gridsquare is found then the US County is used for the calculation. If no County is found then the US State is used for the calculation. If no State is found then Logger32 crosses its fingers and uses the standard US call district as the basis for calculation.

SeventyThree(s).

On 09/02/2022 1:04 PM Lee W4EIS <2thkeeper@...> wrote:

Bob

That line shows  “Not credited for DXCC_MIXED”. Will it not pull directions for a US station?

Al mal tiempo, buena cara

On Sep 2, 2022, at 7:38 AM, Bob <k4cy@...> wrote:

With a callsign in the logbook entry window, you can see the short/long path headings here. SeventyThree(s).

On 09/02/2022 8:07 AM Lee W4EIS <2thkeeper@...> wrote:

I have Logger32 linked to my QRZ account. I can’t see how to determine the short distance from my QTH to station being worked so I can adjust my rotor direction

Suggestion?

Lee

W4EIS 

Al mal tiempo, buena cara

On 09/04/2022 5:21 PM Lee W4EIS <2thkeeper@...> wrote:

Finally figured it out 

Question:  got the visually impaired, is there a way to increase the size of the status bar?

Al mal tiempo, buena cara

On Sep 2, 2022, at 12:30 PM, Bob <k4cy@...> wrote:

If the callsign entered is recognized as being valid the short/long path beam headings are calculated and shown. The want/need status has no bearing (no pun intended) on if the heading is shown or not.

When calculating beam headings for US Stations, several factors are taken into consideration. First we look for a gridsquare and use that. If no gridsquare is found then the US County is used for the calculation. If no County is found then the US State is used for the calculation. If no State is found then Logger32 crosses its fingers and uses the standard US call district as the basis for calculation.

SeventyThree(s).

On 09/02/2022 1:04 PM Lee W4EIS <2thkeeper@...> wrote:

Bob

That line shows  “Not credited for DXCC_MIXED”. Will it not pull directions for a US station?

Al mal tiempo, buena cara

On Sep 2, 2022, at 7:38 AM, Bob <k4cy@...> wrote:

With a callsign in the logbook entry window, you can see the short/long path headings here. SeventyThree(s).

On 09/02/2022 8:07 AM Lee W4EIS <2thkeeper@...> wrote:

I have Logger32 linked to my QRZ account. I can’t see how to determine the short distance from my QTH to station being worked so I can adjust my rotor direction

Suggestion?

Lee

W4EIS 

Al mal tiempo, buena cara

On Sep 2, 2022, at 12:30 PM, Bob <k4cy@...> wrote:



If the callsign entered is recognized as being valid the short/long path beam headings are calculated and shown. The want/need status has no bearing (no pun intended) on if the heading is shown or not.

When calculating beam headings for US Stations, several factors are taken into consideration. First we look for a gridsquare and use that. If no gridsquare is found then the US County is used for the calculation. If no County is found then the US State is used for the calculation. If no State is found then Logger32 crosses its fingers and uses the standard US call district as the basis for calculation.

SeventyThree(s).

On 09/02/2022 1:04 PM Lee W4EIS <2thkeeper@...> wrote:

Bob

That line shows  “Not credited for DXCC_MIXED”. Will it not pull directions for a US station?

Al mal tiempo, buena cara

On Sep 2, 2022, at 7:38 AM, Bob <k4cy@...> wrote:

With a callsign in the logbook entry window, you can see the short/long path headings here. SeventyThree(s).

On 09/02/2022 8:07 AM Lee W4EIS <2thkeeper@...> wrote:

I have Logger32 linked to my QRZ account. I can’t see how to determine the short distance from my QTH to station being worked so I can adjust my rotor direction

Suggestion?

Lee

W4EIS 

Al mal tiempo, buena cara