Date   

DXCC Award Grids

PETER DOUGHTY
 

Hello

I have been using the various DXCC award grids to map my stats with the contacts shown as W C G as appropriate for decades.

For each I have had the background of the slots being red, yellow and green as appropriate. Out of the blue I have lost the red background for 'confirmed' contacts though this is still in places such as IOTA logging and across all the other windows show no change. Even on the DXCC grids the worked and granted slot backgrounds are still in place.

Can anyone tell me how I did this and how I can get this back again?

73s

Peter G3TKK


Re: Any Help appreciated

Bob
 

... also, as you're a CW only operator, you can zoom all the BandMaps to show only the spectrum of interest, then filter out all the modes du jour so that only your preference is visible (sort of like sanitizing the bands). SeventyThree(s).

On 07/04/2020 2:24 PM Michael Buckle via groups.io <mikejohnb@...> wrote:


Thanks Bob, I really appreciate your efforts on this subject, I will look into the CW Machine. I shut down the PC and restarted again, Bingo, CW is selected but only for a short time, then it reverts back to RTTY. Most frustrating. I will now check your suggestions, Thanks again.

On 04/07/2020 16:26, Bob wrote:
If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).
On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


Bob

I have checked the Mode on the input window and have posted another screen shot below.

I only use CW, I don't any other settings relating to RTTY or any other mode.

The strange part here is, this is identical to the mode on the input screen when the main Monitor window is selected and, when clicked, does not set to RTTY and sets as CW. I will try and see if there is anything I can do on the Radio settings. What would happen if I deselect all other modes or at least the RTTY mode???


On 04/07/2020 15:49, Bob wrote:
Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 
On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: VSPE splitter ports not visible to logger32

Bob
 

Logger32 version 3.50.xx supports COM1 - COM16. It is in the Help File. SeventyThree(s).

On 07/04/2020 6:07 PM Ignacy Misztal <no9e@...> wrote:


I created a VSPE splitter for serial rotor ports to use them by multiple applications and remote. I tried port 16 and 32. Both work with rotor controls and n1mm but not logger32.
The message is:
Invalid port 32.
These ports do not show in device manager.
Ignacy NO9E


VSPE splitter ports not visible to logger32

Ignacy Misztal
 

I created a VSPE splitter for serial rotor ports to use them by multiple applications and remote. I tried port 16 and 32. Both work with rotor controls and n1mm but not logger32.
The message is:
Invalid port 32.
These ports do not show in device manager.
Ignacy NO9E


Re: Any Help appreciated

Michael Buckle
 

Thanks Bob, I really appreciate your efforts on this subject, I will look into the CW Machine. I shut down the PC and restarted again, Bingo, CW is selected but only for a short time, then it reverts back to RTTY. Most frustrating. I will now check your suggestions, Thanks again.

On 04/07/2020 16:26, Bob wrote:
If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).
On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


Bob

I have checked the Mode on the input window and have posted another screen shot below.

I only use CW, I don't any other settings relating to RTTY or any other mode.

The strange part here is, this is identical to the mode on the input screen when the main Monitor window is selected and, when clicked, does not set to RTTY and sets as CW. I will try and see if there is anything I can do on the Radio settings. What would happen if I deselect all other modes or at least the RTTY mode???


On 04/07/2020 15:49, Bob wrote:
Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 
On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: Any Help appreciated

Bob
 

If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).

On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


Bob

I have checked the Mode on the input window and have posted another screen shot below.

I only use CW, I don't any other settings relating to RTTY or any other mode.

The strange part here is, this is identical to the mode on the input screen when the main Monitor window is selected and, when clicked, does not set to RTTY and sets as CW. I will try and see if there is anything I can do on the Radio settings. What would happen if I deselect all other modes or at least the RTTY mode???


On 04/07/2020 15:49, Bob wrote:
Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 
On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: Any Help appreciated

Michael Buckle
 

Bob

I have checked the Mode on the input window and have posted another screen shot below.

I only use CW, I don't any other settings relating to RTTY or any other mode.

The strange part here is, this is identical to the mode on the input screen when the main Monitor window is selected and, when clicked, does not set to RTTY and sets as CW. I will try and see if there is anything I can do on the Radio settings. What would happen if I deselect all other modes or at least the RTTY mode???


On 04/07/2020 15:49, Bob wrote:
Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 
On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: Any Help appreciated

Bob
 

... also, what is/was the comments associated with the HB9CHB DX Spot? If the comments indicated RTTY, that would put the radio on RTTY. SeventyThree(s).

On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: what is bad in bad.adi?

Gerry VE6LB
 

First line of bad.adi


On July 4, 2020 7:36:01 a.m. MDT, "Ilya Zozin,4Z1UF" <4z1uf@...> wrote:

 After attempt to import LoTW report I've got many rejects. The note says that bad.adi created and it will be noted why these Q's are rejected.
 I don't see any note and cannot find anything wrong. 

What is wrong?

73,
Ilya, 4Z1UF



--
Sent from my Android device by VE6LB with K-9 Mail.


Re: Any Help appreciated

Bob
 

Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 

On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Any Help appreciated

Michael Buckle
 

All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: what is bad in bad.adi?

Michael Harris
 

At the start of each bad.adi qso record listed there is a line "error in the......" Usually for me county entries are most common. Given that counties are of no interest to me I just find that part of the record and delete it. I save the file, copy it to wherever your lotw reports are downloaded too and rename it new.adi thereafter just import it into L32 like you would normally do.

I do all my exporting and importing of lotw files manually. No automation

Regards,

Mike VP8NO

On 04/07/2020 10:36, Ilya Zozin,4Z1UF wrote:
 After attempt to import LoTW report I've got many rejects. The note says that bad.adi created and it will be noted why these Q's are rejected.
 I don't see any note and cannot find anything wrong.
What is wrong?
73,
Ilya, 4Z1UF


Re: what is bad in bad.adi?

Bob
 

Without looking at the bad.adi file, it's difficult to tell. SeventyThree(s).

On 07/04/2020 9:36 AM Ilya Zozin,4Z1UF <4z1uf@...> wrote:


 After attempt to import LoTW report I've got many rejects. The note says that bad.adi created and it will be noted why these Q's are rejected.
 I don't see any note and cannot find anything wrong. 

What is wrong?

73,
Ilya, 4Z1UF



what is bad in bad.adi?

Ilya Zozin,4Z1UF
 

 After attempt to import LoTW report I've got many rejects. The note says that bad.adi created and it will be noted why these Q's are rejected.
 I don't see any note and cannot find anything wrong. 

What is wrong?

73,
Ilya, 4Z1UF



Re: Logbook Window Font Colour

G4RRM Pete
 

Thank you

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Vilhjalmur Sigurjonsson
Sent: 04 July 2020 11:37
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logbook Window Font Colour

 

Its View | Grid appearance etc.

It is chapter 1 in the Help ;)

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of G4RRM Pete
Sent: laugardagur, 4. júlí 2020 10:30
To: Logger32 (hamlogger@groups.io) <hamlogger@groups.io>
Subject: [hamlogger] Logbook Window Font Colour

 

Hi All

 

Sorry to ask, but can someone tell me where I find the option to change font colour in the Logbook window please?

It escapes me right now!

 

 

 

73

Pete

G4RRM

 


Re: Logbook Window Font Colour

Vilhjalmur Sigurjonsson
 

Its View | Grid appearance etc.

It is chapter 1 in the Help ;)

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of G4RRM Pete
Sent: laugardagur, 4. júlí 2020 10:30
To: Logger32 (hamlogger@groups.io) <hamlogger@groups.io>
Subject: [hamlogger] Logbook Window Font Colour

 

Hi All

 

Sorry to ask, but can someone tell me where I find the option to change font colour in the Logbook window please?

It escapes me right now!

 

 

 

73

Pete

G4RRM

 


Logbook Window Font Colour

G4RRM Pete
 

Hi All

 

Sorry to ask, but can someone tell me where I find the option to change font colour in the Logbook window please?

It escapes me right now!

 

 

 

73

Pete

G4RRM

 


Re: strange resut in v3.5 and in v4

Jim Altman
 

No worry, thanks.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: Friday, July 3, 2020 1:55 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

No I have not added that to the eQSL upload yet. Been busy and haven’t been back to work on it.

 

73 Rick

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Altman
Sent: Friday, July 3, 2020 12:56 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

Thanks Rick, its really not a problem, but I would assume eQSL has to do the same thing and doesn’t take nearly as long.  Same number of q’s to each.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: Friday, July 3, 2020 11:59 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

Hi Jim..

This is because after the LOTW upload each qso gets checked in the tqsl log file that it was uploaded correctly and then if it was uploaded correctly it sends a message to Logger32 to change the LOTW flags from LOTW Send being turned off and LOTW Sent being turned on. There is no way to do this in bulk so it has to be done singlely for each qso.

 

73 Rick N2AMG

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Altman
Sent: Friday, July 3, 2020 9:58 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

As long as we are on the subject of LogSync, I have noticed this most recent version seems to take a long time to get the focus back from LOTW send.  All the other functions return the focus quickly.

 

Thanks for your app and regards, happy 4th de w4uck.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: Friday, July 3, 2020 9:53 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

Nick..

What version of Logsync are you running?? And is your time set correctly??

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of NICK K. PLUMIDAKIS
Sent: Friday, July 3, 2020 1:15 AM
To: hamlogger@groups.io
Subject: [hamlogger] strange resut in v3.5 and in v4

 

 

 

Hi to all.

In the past 4-5 days every time that I am loading l32 I am getting this strange reply from W10??? .

If I will de energize the L32syn the tag is not coming.

Any Idea why???

Best 73’s

DE

Nick

 

 

Virus-free. www.avast.com


Re: strange resut in v3.5 and in v4

Rick Ellison
 

No I have not added that to the eQSL upload yet. Been busy and haven’t been back to work on it.

 

73 Rick

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Altman
Sent: Friday, July 3, 2020 12:56 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

Thanks Rick, its really not a problem, but I would assume eQSL has to do the same thing and doesn’t take nearly as long.  Same number of q’s to each.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: Friday, July 3, 2020 11:59 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

Hi Jim..

This is because after the LOTW upload each qso gets checked in the tqsl log file that it was uploaded correctly and then if it was uploaded correctly it sends a message to Logger32 to change the LOTW flags from LOTW Send being turned off and LOTW Sent being turned on. There is no way to do this in bulk so it has to be done singlely for each qso.

 

73 Rick N2AMG

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Altman
Sent: Friday, July 3, 2020 9:58 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

As long as we are on the subject of LogSync, I have noticed this most recent version seems to take a long time to get the focus back from LOTW send.  All the other functions return the focus quickly.

 

Thanks for your app and regards, happy 4th de w4uck.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: Friday, July 3, 2020 9:53 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

Nick..

What version of Logsync are you running?? And is your time set correctly??

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of NICK K. PLUMIDAKIS
Sent: Friday, July 3, 2020 1:15 AM
To: hamlogger@groups.io
Subject: [hamlogger] strange resut in v3.5 and in v4

 

 

 

Hi to all.

In the past 4-5 days every time that I am loading l32 I am getting this strange reply from W10??? .

If I will de energize the L32syn the tag is not coming.

Any Idea why???

Best 73’s

DE

Nick

 

 

Virus-free. www.avast.com


Re: strange resut in v3.5 and in v4

Jim Altman
 

Thanks Rick, its really not a problem, but I would assume eQSL has to do the same thing and doesn’t take nearly as long.  Same number of q’s to each.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: Friday, July 3, 2020 11:59 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

Hi Jim..

This is because after the LOTW upload each qso gets checked in the tqsl log file that it was uploaded correctly and then if it was uploaded correctly it sends a message to Logger32 to change the LOTW flags from LOTW Send being turned off and LOTW Sent being turned on. There is no way to do this in bulk so it has to be done singlely for each qso.

 

73 Rick N2AMG

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Altman
Sent: Friday, July 3, 2020 9:58 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

As long as we are on the subject of LogSync, I have noticed this most recent version seems to take a long time to get the focus back from LOTW send.  All the other functions return the focus quickly.

 

Thanks for your app and regards, happy 4th de w4uck.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Ellison
Sent: Friday, July 3, 2020 9:53 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

Nick..

What version of Logsync are you running?? And is your time set correctly??

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of NICK K. PLUMIDAKIS
Sent: Friday, July 3, 2020 1:15 AM
To: hamlogger@groups.io
Subject: [hamlogger] strange resut in v3.5 and in v4

 

 

 

Hi to all.

In the past 4-5 days every time that I am loading l32 I am getting this strange reply from W10??? .

If I will de energize the L32syn the tag is not coming.

Any Idea why???

Best 73’s

DE

Nick

 

 

Virus-free. www.avast.com

2261 - 2280 of 82860