Sorry for skanti report!
?
I have downloaded the latest version off L32 from the website and installed on to my new PC that works fine. When i click to run L32 it opens and begins to load, then i get the windows error message.
?
Its a complete new installation from scratch, I lost my last PC completely just went bang and died! so there was no copying off files etc involved, I managed to recover my log from clublog and LoTW so my intention was simply to install L32 and start a new log by importing the adif from clublog
?
I have AVG antivirus but i already had that on the last machine which as mentioned before was all ok. Everything just looks different on Windows 10?
Screen looks like this:
?
|
Then I have no idea what the problem is. SeventyThree(s).
On 03/24/2025 12:09 PM EDT Jean-Claude ROUGE via groups.io <j-cl.rouge@...> wrote:
?
?
I have done it, I get the same thing, it does not work.
73's.
J-Cl
Le 24/03/2025 ¨¤ 16:11, Bob via groups.io a ¨¦crit?:
Look in the default Logger32 directory for a file called CW.INI and rename it to OLD.CW.INI. Now restart?the CW Machine and try and setup WinKey2. SeventyThree(s).
On 03/24/2025 10:34 AM EDT Jean-Claude ROUGE via groups.io <j-cl.rouge@...> wrote:
?
?
Hello,
I want to use CW machine with Winkeyer 2 in the window config.
When I click on Keyer Setup, the CW Machine window closes ant it is impssible to access to thr Winkeyer 2 config window.
I read the help file page 640 but I found nothing that could help me.
Any idea ?
Tks for help.
73's.
Jean-Claude? F6HDH
?
|
I have done it, I get the same thing, it does not
work.
73's.
J-Cl
Le 24/03/2025 ¨¤ 16:11, Bob via
groups.io a ¨¦crit?:
toggle quoted message
Show quoted text
Look in the default Logger32 directory for a file
called CW.INI and rename it to OLD.CW.INI. Now restart?the CW
Machine and try and setup WinKey2. SeventyThree(s).
On 03/24/2025 10:34 AM EDT Jean-Claude ROUGE via groups.io
<j-cl.rouge@...> wrote: ?
?
Hello,
I want to use CW machine with Winkeyer 2 in the window
config.
When I click on Keyer Setup, the CW Machine window
closes ant it is impssible to access to thr Winkeyer 2
config window.
I read the help file page 640 but I found nothing that
could help me.
Any idea ?
Tks for help.
73's.
Jean-Claude? F6HDH
?
|
Look in the default Logger32 directory for a file called CW.INI and rename it to OLD.CW.INI. Now restart?the CW Machine and try and setup WinKey2. SeventyThree(s).
On 03/24/2025 10:34 AM EDT Jean-Claude ROUGE via groups.io <j-cl.rouge@...> wrote:
?
?
Hello,
I want to use CW machine with Winkeyer 2 in the window config.
When I click on Keyer Setup, the CW Machine window closes ant it is impssible to access to thr Winkeyer 2 config window.
I read the help file page 640 but I found nothing that could help me.
Any idea ?
Tks for help.
73's.
Jean-Claude? F6HDH
?
|
I have no idea. Time for a new logging program I suspect. SeventyThree(s).
On 03/24/2025 10:34 AM EDT Richard Zalewski W7ZR via groups.io <dick.w7zr@...> wrote:
?
?
I broght this up before but continue to have a problem.? If I want to delete a QSO from log (usually a QSO within last 5 min) I select the QSO.? Then it asks am I sure.? I say yes.? Then the program quits.? When I bring up the program again and ask to delete the QSO for the second time it works fine.??
|
You ay you're trying to install Logger32 on a new PC. This replay assumes (always dangerous) that you have actually successfully?completed the installation process, and now you're attempting to run Logger32 -
?
How far does Logger32 get before it craps out? What windows are opened. What does the splash screen say is happening?
?
After the new install of Logger32 on the PC, did you then copy some files from your old PC to the new PC? If you did, is it possible/probable that you copied something to the new PC doesn't like- A file path that doesn't exist on the new PC, a serial port that doesn't exist on the new PC, etc?
?
If you are running the latest Logger32 v4 on your old PC, look at the following in the help file. Otherwise, go to
Section 2.12 on page 68.
?
SeventyThree(s)
On 03/24/2025 10:06 AM EDT MM0EAX via groups.io <mm0eax@...> wrote:
?
?
Hello All
?
I purchased a new PC with Windows 10, For Many years i used Windows 7 and had Logger32 working great. I am attempting to install Logger32 v4 on my new PC but no matter what i do as soon as i open the program windows tells me it encountered a problem and shuts down? Ive googled endlessley for a solution for weeks now and know that Logger32 aint the issue but Windows 10. I have read all the stuff about running as administrator etc but everytime i download and install the program it comes with that shield symbol and off i go on another endless loop!
Windows 10 is still double dutch to me so just wondering if any experts out there that can explain what im doing wrong somewhere along the line??
As far as i can see it seems that Logger32 download is the only one that ive had issues with as ive more or less downloaded and installed everything that i had on my win 7 machine
?
Regards Dave
|
Hello,
I want to use CW machine with Winkeyer 2 in the
window config.
When I click on Keyer Setup, the CW Machine window
closes ant it is impssible to access to thr Winkeyer 2 config
window.
I read the help file page 640 but I found nothing
that could help me.
Any idea ?
Tks for help.
73's.
Jean-Claude? F6HDH
|
I broght this up before but continue to have a problem.? If I want to delete a QSO from log (usually a QSO within last 5 min) I select the QSO.? Then it asks am I sure.? I say yes.? Then the program quits.? When I bring up the program again and ask to delete the QSO for the second time it works fine.??
|
Hello All
?
I purchased a new PC with Windows 10, For Many years i used Windows 7 and had Logger32 working great. I am attempting to install Logger32 v4 on my new PC but no matter what i do as soon as i open the program windows tells me it encountered a problem and shuts down? Ive googled endlessley for a solution for weeks now and know that Logger32 aint the issue but Windows 10. I have read all the stuff about running as administrator etc but everytime i download and install the program it comes with that shield symbol and off i go on another endless loop!
Windows 10 is still double dutch to me so just wondering if any experts out there that can explain what im doing wrong somewhere along the line??
As far as i can see it seems that Logger32 download is the only one that ive had issues with as ive more or less downloaded and installed everything that i had on my win 7 machine
?
Regards Dave
|
Re: DX spot map, wrong country
... or you could block DX Spots where the comment contains EL99IA<>?That should tame the KJ4E DX Spots until someone can convince him of the folly of his ways. SeventyThree(s).
On 03/23/2025 9:39 PM EDT Bob <k4cy@...> wrote:
?
?
... but you can block DX Spots by KI4E. SeventyThree(s).
On 03/23/2025 9:32 PM EDT Bob <k4cy@...> wrote:
?
?
As you say Gary, CQCW is not a valid gridsquare, so setting the DX Spot bullshit filter to remove gridsquares may (or may not) address the problem. We can't win them all, but it's not through lack of trying. SeventyThree(s).
On 03/23/2025 8:21 PM EDT ZL2iFB via groups.io <zl2ifb@...> wrote:
?
?
Hi Tony.
?
From what you've said there, it seems the LU DX spot is being mapped using the spotter's grid which he gave in his spot comment.
?
The conventional format for those kind of comments is AA11aa<>BB22bb indicating the grids at the spotter and DX ends, respectively.??
?
Since "CQCW" is not a grid, I guess EL99ib is being used for mapping the spot, even though it is not an LU grid.
?
Similar anomalies happen whenever a spurious grid is provided e.g. one mis-logged in a previous QSO, perhaps obtained from a confirmation or simply a typo.? There is no automated check that the grid corresponds to the DXCC entity, simply that it is a valid grid.? ?
?
73
Gary?
?beater/tester &?
Honor Roll &? checker
Hi Gerald.
?
It just happened again @22:39 UTC?on 23rd March.
KJ4E spots LU4DYI on 50105.0
Comments: "EL99IB<>CQCW"
Spot appeared in southern US on the DX Spot map and for info EL99 is FL.
-----------------------------------
LU4DYI Also spotted by K1UTI? @22:36 with no comments and the correct map location.
?
Both are non-RBN source.
?
Will post a few more when seen again.
?
73, Tony G2NF
?
?
?
?
|
Re: DX spot map, wrong country
... but you can block DX Spots by KI4E. SeventyThree(s).
On 03/23/2025 9:32 PM EDT Bob <k4cy@...> wrote:
?
?
As you say Gary, CQCW is not a valid gridsquare, so setting the DX Spot bullshit filter to remove gridsquares may (or may not) address the problem. We can't win them all, but it's not through lack of trying. SeventyThree(s).
On 03/23/2025 8:21 PM EDT ZL2iFB via groups.io <zl2ifb@...> wrote:
?
?
Hi Tony.
?
From what you've said there, it seems the LU DX spot is being mapped using the spotter's grid which he gave in his spot comment.
?
The conventional format for those kind of comments is AA11aa<>BB22bb indicating the grids at the spotter and DX ends, respectively.??
?
Since "CQCW" is not a grid, I guess EL99ib is being used for mapping the spot, even though it is not an LU grid.
?
Similar anomalies happen whenever a spurious grid is provided e.g. one mis-logged in a previous QSO, perhaps obtained from a confirmation or simply a typo.? There is no automated check that the grid corresponds to the DXCC entity, simply that it is a valid grid.? ?
?
73
Gary?
?beater/tester &?
Honor Roll &? checker
Hi Gerald.
?
It just happened again @22:39 UTC?on 23rd March.
KJ4E spots LU4DYI on 50105.0
Comments: "EL99IB<>CQCW"
Spot appeared in southern US on the DX Spot map and for info EL99 is FL.
-----------------------------------
LU4DYI Also spotted by K1UTI? @22:36 with no comments and the correct map location.
?
Both are non-RBN source.
?
Will post a few more when seen again.
?
73, Tony G2NF
?
?
?
?
|
Re: DX spot map, wrong country
As you say Gary, CQCW is not a valid gridsquare, so setting the DX Spot bullshit filter to remove gridsquares may (or may not) address the problem. We can't win them all, but it's not through lack of trying. SeventyThree(s).
On 03/23/2025 8:21 PM EDT ZL2iFB via groups.io <zl2ifb@...> wrote:
?
?
Hi Tony.
?
From what you've said there, it seems the LU DX spot is being mapped using the spotter's grid which he gave in his spot comment.
?
The conventional format for those kind of comments is AA11aa<>BB22bb indicating the grids at the spotter and DX ends, respectively.??
?
Since "CQCW" is not a grid, I guess EL99ib is being used for mapping the spot, even though it is not an LU grid.
?
Similar anomalies happen whenever a spurious grid is provided e.g. one mis-logged in a previous QSO, perhaps obtained from a confirmation or simply a typo.? There is no automated check that the grid corresponds to the DXCC entity, simply that it is a valid grid.? ?
?
73
Gary?
?beater/tester &?
Honor Roll &? checker
Hi Gerald.
?
It just happened again @22:39 UTC?on 23rd March.
KJ4E spots LU4DYI on 50105.0
Comments: "EL99IB<>CQCW"
Spot appeared in southern US on the DX Spot map and for info EL99 is FL.
-----------------------------------
LU4DYI Also spotted by K1UTI? @22:36 with no comments and the correct map location.
?
Both are non-RBN source.
?
Will post a few more when seen again.
?
73, Tony G2NF
?
?
?
?
|
Re: DX spot map, wrong country
On Sun, Mar 23, 2025 at 08:31 PM, Tony G2NF wrote:
?
It just happened again @22:39 UTC?on 23rd March.
KJ4E spots LU4DYI on 50105.0
Comments: "EL99IB<>CQCW"
Spot appeared in southern US on the DX Spot map and for info EL99 is FL.
-----------------------------------
LU4DYI Also spotted by K1UTI? @22:36 with no comments and the correct map location.
?
Tony,
?
I followed up on your data and did a search on dxsummit and was able to see that the problem does appear related to the spotter including their own grid square.
?
Since "Info" column format is not officially defined, sometimes it ends up being a case of GIGO (Garbage In / Garbage Out).?
?
?
 ?Spotter |
 ?Freq. |
 ?DX |
 ?Time |
 ?Info |
 ?Country |
|
KJ4E
|
50120
|
LU1XAV
|
17:30 23 Mar 25
|
EL99IB<>FD58JI Hrd
|
Argentina
|
|
KJ4E
|
50125
|
PY3SOL
|
00:06 14 Mar 25
|
EL99IA<>GG30OH hrd
|
Brazil
|
|
KJ4E
|
50072
|
KF5KOI/B
|
22:29 19 Feb 25
|
EL99IA<>EM00TA 579
|
United States
|
|
KJ4E
|
50065
|
KE5JXC/B
|
22:28 19 Feb 25
|
EL99IA<>EL39SP 599
|
United States
|
|
KJ4E
|
50072
|
KF5KOI/B
|
21:39 19 Feb 25
|
EL99IA<>EM00TA
|
United States
|
|
KJ4E
|
50080
|
KC5SQD/B
|
21:38 19 Feb 25
|
EL99IA<>EL29GO
|
United States
|
|
KJ4E
|
50065
|
KE5JXC/B
|
21:28 19 Feb 25
|
EL99IA<>EL39SP
|
United States
|
|
KJ4E
|
50010
|
K8MMM/B
|
14:28 14 Feb 25
|
EL99IA<>EN91
|
United States
|
|
KJ4E
|
50125
|
W5VB
|
17:21 02 Feb 25
|
EL99IA<>EM12SW
|
United States
|
|
KJ4E
|
50125
|
N1WRK
|
22:28 01 Feb 25
|
EL99IA<>FN41SR
|
United States
|
|
KJ4E
|
50075
|
WB2VVV/B
|
22:26 01 Feb 25
|
EL99IA<>FN41
|
United States
|
|
KJ4E
|
50077
|
WI2RES/B
|
18:46 28 Jan 25
|
EL99IA<>FN31BE
|
United States
|
|
KJ4E
|
50062
|
AD9OV/B
|
17:42 18 Jan 25
|
EL99IA<>EM58IX
|
United States
|
?
?
--
Gerald, VE1DT
|
Re: DX spot map, wrong country
Hi Tony.
From what you've said there, it seems the LU DX spot is being mapped using the spotter's grid which he gave in his spot comment.
The conventional format for those kind of comments is AA11aa<>BB22bb indicating the grids at the spotter and DX ends, respectively.??
Since "CQCW" is not a grid, I guess EL99ib is being used for mapping the spot, even though it is not an LU grid.
Similar anomalies happen whenever a spurious grid is provided e.g. one mis-logged in a previous QSO, perhaps obtained from a confirmation or simply a typo.? There is no automated check that the grid corresponds to the DXCC entity, simply that it is a valid grid.? ?
73 Gary? ?beater/tester &?
Honor Roll &? checker
Hi Gerald.
?
It just happened again @22:39 UTC?on 23rd March.
KJ4E spots LU4DYI on 50105.0
Comments: "EL99IB<>CQCW"
Spot appeared in southern US on the DX Spot map and for info EL99 is FL.
-----------------------------------
LU4DYI Also spotted by K1UTI? @22:36 with no comments and the correct map location.
?
Both are non-RBN source.
?
Will post a few more when seen again.
?
73, Tony G2NF
?
?
|
Re: DX spot map, wrong country
Hi Gerald.
?
It just happened again @22:39 UTC?on 23rd March.
KJ4E spots LU4DYI on 50105.0
Comments: "EL99IB<>CQCW"
Spot appeared in southern US on the DX Spot map and for info EL99 is FL.
-----------------------------------
LU4DYI Also spotted by K1UTI? @22:36 with no comments and the correct map location.
?
Both are non-RBN source.
?
Will post a few more when seen again.
?
73, Tony G2NF
?
?
|
Re: DX spot map, wrong country
Tony,
?
Can you provide any actual examples?
?
--
Gerald, VE1DT
|
DX spot map, wrong country
Hi all,
?
Have you ever wondered why a spot icon is placed in the wrong country in the DX Spot map window?
This only occurs from Non-RBN sources.
Seems to happen a lot some times, then nothing for days etc.?
?
If a spot is sent to the cluster with a Locator (6 fig) in the comments then that locater appears to take precedence over the country location which is OK, unless the spot includes the locator of the sender and not the DX.?
?
Also happens when both locators are sent in the comments, perhaps it only take the 1st one?
?
Trivial I know, but may throw up other issues.
?
73, Tony G2NF.
?
|
Best I could find was 17 QSOs. My tests were not visual observations, I actually debugged the code, and it is only executed once. It is possible/probable that creating a large list of 1000+ QSOs an the fly, loading them into a grid, then adjusting the grid up 990 (or so) rows to show the last QSO, is a little taxing on the PC graphics causing the title bar on the form to repaint.
?
Keep an eye on the Logbook details window so you don't run out?of space. Also, you might consider rebuilding your logbook periodically to improve its performance. With a big log like that, First made an ADIF backup and hide it under the mattress. Then, before going to bed start the rebuild.
?
SeventyThree(s).
On 03/22/2025 1:41 PM EDT Joe N3XLS via groups.io <n3xls@...> wrote:
?
?
I must be seeing the action that you describe. There is no blinking or flashing of the window as you say its only the number appearing and disappearing to finally appear after its done processing. Plus I only see it on the guys that have 1000+ previous.? The number never changes, its always the same. But with 180k+ that is a long haul of data to be counting up and be searching for all those QSOs.? I doubt logger32 was ever meant or thought of to be tallying large amounts of QSO's from the same operator in the thousands. So I'm probably an edge case here.?
?
I'm afraid to say my logbook is becoming one of those big data repositories. I might dwarf some of the other power users on this forum though. I think I remember someone here posted they had more than 300k+ QSOs in their logbook. So we are probably all the edge cases for the stuff that was never dreamed of getting that large. ?
|
I must be seeing the action that you describe. There is no blinking or flashing of the window as you say its only the number appearing and disappearing to finally appear after its done processing. Plus I only see it on the guys that have 1000+ previous.? The number never changes, its always the same. But with 180k+ that is a long haul of data to be counting up and be searching for all those QSOs.? I doubt logger32 was ever meant or thought of to be tallying large amounts of QSO's from the same operator in the thousands. So I'm probably an edge case here.?
?
I'm afraid to say my logbook is becoming one of those big data repositories. I might dwarf some of the other power users on this forum though. I think I remember someone here posted they had more than 300k+ QSOs in their logbook. So we are probably all the edge cases for the stuff that was never dreamed of getting that large. ?
|
Thanks for the observation. I checked the code and Previous QSOs are displayed only once. Then, after that if there are more QSOs than visible rows on the form the caption of the form is modified to include the number of QSOs. That too is executed only once. Finally, the grid adjusts the top row visible so that the most recent QSO is on the last mine. This too is executed only once.
?
Reading the logbook, populating the grid, modifying the caption, adjusting the grid to show the last QSO at the bottom, is all done without taking a breather for the graphics to catch up. There should be little or no blinking or flashing of the window while the QSOs are loaded and displayed.
?
Maybe others have similar observations? SeventyThree(s).
?
?
?
?
On 03/22/2025 12:25 PM EDT Joe N3XLS via groups.io <n3xls@...> wrote:
?
?
Bob,
I have an operator in my log that has been worked a lot. When logger32 looks up this callsign it looks like its totaling the QSOs up 3 different times.? Because the number appears and disappears two times then finally appears. Just figured i let you know since it seems like maybe there is some bug in the code causing it to fire off 3 times.
?
Joe
N3XLS
|
Gerald Boutin
ZL2iFB
Joe N3XLS