Date   

Re: L32 windows disappeared

ja1nlx
 

Paul

1. Look for Logger32.ini in Logger32 folder.
2. Rename Logger32.ini.OLD
3. Run Logger32

Now Logger32 run with default settings. You must make every settings again.

If you do not like to make all settings again then follow next steps.

1. Look for Logger32.ini in Logger32 folder.
2. Open Logger32.ini with text editor.
3. Look for the line [Globals]
4. Look for the line with "Child Forms Open=..."
5. Delete this line.
6. Copy/Paste following line

Child Forms Open=+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

7. Run Logger32

I do not know this solve your problem, however you need minimum re-settings in this case.

73



On 2020/02/23 6:19, w1pr@... wrote:
I must have done something bad when I closed the L32 windows by clicking the X on the upper right corner of each window, rather than closing the program as a whole. Now when I run L32, the only window I can see is the CW Machine, which was minimized and so not victim to the X clicking. I can't get to the menu bar, setup, etc. I looked at the .ini file but failed to identify what must have changed there when I closed the individual windows. I'm reluctant to simply reinstall L32 over the present installation for fear of losing data for 2 logs/calls.  So now I'm really stuck, not to mention feeling stupid. Can anybody HELP?

Tnx & 73 de Paul, W1PR
--
73 de aki
JA1NLX


L32 windows disappeared

Paul - W1PR
 

I must have done something bad when I closed the L32 windows by clicking the X on the upper right corner of each window, rather than closing the program as a whole. Now when I run L32, the only window I can see is the CW Machine, which was minimized and so not victim to the X clicking. I can't get to the menu bar, setup, etc. I looked at the .ini file but failed to identify what must have changed there when I closed the individual windows. I'm reluctant to simply reinstall L32 over the present installation for fear of losing data for 2 logs/calls.  So now I'm really stuck, not to mention feeling stupid. Can anybody HELP?

Tnx & 73 de Paul, W1PR


Question.

Dave Colliau
 

Would it be possible to get some kind loop timer that would work in the macros for the RCP window and could be set for 10 minutes for like a CIV macro for creating ssb or cw id's ? 
TIA
Dave N8DC


Two instances of WSJT-X or JTDX connected at the same time?

Markku Oksanen
 

All
Can I have two instances of WSJT-X or JTDX at the same time feeding QSOs to the same log at the same time?
I found out after some testing that having a JTDX TCP connection and WSJTX UDP feed at the same time resets the UDP bandmap every time there is activity on the WSJTX side.  I would just like to have two stations, one with UDP bandmap and one just logging to L32 at the same time on the same PC.
Thanks!
Markku OH2RA 


Logging QSO via UDP Clears 'WAZ Not Worked This Band' Colour From DX Spots Window

Darren Collins (G0TSM)
 

As the long title says...

If I log a QSO via UDP it clears the colour from a spot that is highlighted for WAZ 'not worked this band'. Which would be correct if I had just worked that zone on the current band...

In the attached/embedded example I have some blue spots as I need zone 19 on 80M....


I then work anything on FT8 (I'm working Europeans on 60M FT8) and the blue WAZ highlights clear when a QSO is logged via UDP (In the example I've just worked Zone 14 on 60M). It doesn't clear the colour if I'm manually pressing enter for CW/SSB QSOs.


Thank You, Darren G0TSM



Re: FT8 QUESTION

martinwcf
 

Hi Larry,

 

are you using the latest version (latest upgrade)?

See ADIFMODE.txt file in Logger32 directory, open with notepad and see if FT8 mode is listed there.

 

73! Martin OK1WCF

______________________________________________________________
> Od: "larry fields" <n6hpx1@...>
> Komu: hamlogger@groups.io
> Datum: 21.02.2020 04:22
> Předmět: [hamlogger] FT8 QUESTION
>

I tried to add a QSO with a Indonesian station on the FT-8 and there is a message that pops up saying not a valid ADIF OR SUBMODE


Re: problem closing L32

alan
 

Rick

many thanks for your reply and all understood, I will get around it in the mean time by closing Fldigi first and then L32

I think that will work ok otherwise just force close L32 as I have been doing.

My appreciation for the programs yous have given us, I  have used the Gateway for years and also fcc Lookup

which always worked FB

Thanks again

Alan ZL3KR


On 21/02/2020 4:06 pm, Rick Ellison wrote:

Hi Alan..

There is probably something with the gateway. The gateway is using older controls and some of the connecting routines to Fldigi have been changed. My biggest problem why I have not gone in to fix these things is I have lost the original sourcecode for the program. I have started re-writing the program in vb.net but have not completed things yet. I have to many irons in the fire right now to sit and fully concentrate on one program at the moment.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of alan
Sent: Thursday, February 20, 2020 9:54 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] problem closing L32

 

Hi Aki

just been trying different things to determine actually whqt is happening.

I stopped the L32 utility from booting Logsync....no change, L32 has to be forced close.

I then stopped L32 utility from booting Fldigi..... L32 closes cleanly.

If I Boot L32 and then seperately Boot Fldigi...L32 closes cleanly

Could I have something set incorrectly in the L32/Fldigi Gateway program??

It is almost sure to be something I have either not done or done wrong!!

Alan ZL3KR

 

On 20/02/2020 9:57 pm, ja1nlx wrote:

Alan

When you close Logger32, close LogSync first manually then close Logger32.

Keep watching for a several days in this way.

73

 

On 2020/02/20 17:46, alan wrote:

Hi Aki,

before I qrt for the night

I closed log sync , then FLdigi which closed cleanly after confirming closure(yes/no)

and then Logger 32 closed cleanly, so maybe Logsync is causing the closure problem??

Alan ZL3KR (QRT)

 

On 20/02/2020 9:39 pm, alan via Groups.Io wrote:

Thanks Aki

I will try that when I close down for the evening in a few minutes, incidentally FLdigi does not close down

at the same time, I generally have to close that seperately also, it previously closed  with logger 32

except it asked for confirmation Yes/no to close it.

I will tell you the result tomorrow mng here when I switch back on.

Alan ZL3KR

 

On 20/02/2020 8:51 pm, ja1nlx wrote:

Alan

If you are running other programs like LogSync etc then close those program first,

then close Logger32. What you see ?

73

On 2020/02/20 16:39, alan wrote:

It would seem there is a problem asking a simple question to a minor

problem, maybe the only solution is to delete logger 32 which I have used

for many years and still do. It previously closed without hassle and now fpr some

reason it no longer does, sorry to ask such a difficult question.

Alan ZL3KR

 

On 20/02/2020 3:26 pm, Bob wrote:

Still five weeks unil April 1st. We're starting early this year. SeventyThree(s).

On February 19, 2020 at 9:15 PM alan < zl3kr.alan@...> wrote:

 

 

After a recent windows crash and reinstallation of windows 10

 

I seem to have Logger32 working ok

 

computer is an I3  windows 10 pro

 

I use the utility program to load FLdigi and Log Sync and everything

appears o be working ok.

 

My problem is when I try to exit the program it fails to do so whether i

use the exit command

 

or click on the X to shut it down and I finish up force closing it. It

doesnt appear to do any harm

 

as it boots up fine next ime.

 

Is there something I have missed setting it up again or where would I

look to find

 

what is causing it.

 

It is not a major problem as everything seems to be working ok otherwise.

 

Thanks in advance for any help

 

Alan  ZL3KR

 

 

 

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX


FT8 QUESTION

larry fields
 

I tried to add a QSO with a Indonesian station on the FT-8 and there is a message that pops up saying not a valid ADIF OR SUBMODE


Re: problem closing L32

Rick Ellison
 

Hi Alan..

There is probably something with the gateway. The gateway is using older controls and some of the connecting routines to Fldigi have been changed. My biggest problem why I have not gone in to fix these things is I have lost the original sourcecode for the program. I have started re-writing the program in vb.net but have not completed things yet. I have to many irons in the fire right now to sit and fully concentrate on one program at the moment.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of alan
Sent: Thursday, February 20, 2020 9:54 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] problem closing L32

 

Hi Aki

just been trying different things to determine actually whqt is happening.

I stopped the L32 utility from booting Logsync....no change, L32 has to be forced close.

I then stopped L32 utility from booting Fldigi..... L32 closes cleanly.

If I Boot L32 and then seperately Boot Fldigi...L32 closes cleanly

Could I have something set incorrectly in the L32/Fldigi Gateway program??

It is almost sure to be something I have either not done or done wrong!!

Alan ZL3KR

 

On 20/02/2020 9:57 pm, ja1nlx wrote:

Alan

When you close Logger32, close LogSync first manually then close Logger32.

Keep watching for a several days in this way.

73

 

On 2020/02/20 17:46, alan wrote:

Hi Aki,

before I qrt for the night

I closed log sync , then FLdigi which closed cleanly after confirming closure(yes/no)

and then Logger 32 closed cleanly, so maybe Logsync is causing the closure problem??

Alan ZL3KR (QRT)

 

On 20/02/2020 9:39 pm, alan via Groups.Io wrote:

Thanks Aki

I will try that when I close down for the evening in a few minutes, incidentally FLdigi does not close down

at the same time, I generally have to close that seperately also, it previously closed  with logger 32

except it asked for confirmation Yes/no to close it.

I will tell you the result tomorrow mng here when I switch back on.

Alan ZL3KR

 

On 20/02/2020 8:51 pm, ja1nlx wrote:

Alan

If you are running other programs like LogSync etc then close those program first,

then close Logger32. What you see ?

73

On 2020/02/20 16:39, alan wrote:

It would seem there is a problem asking a simple question to a minor

problem, maybe the only solution is to delete logger 32 which I have used

for many years and still do. It previously closed without hassle and now fpr some

reason it no longer does, sorry to ask such a difficult question.

Alan ZL3KR

 

On 20/02/2020 3:26 pm, Bob wrote:

Still five weeks unil April 1st. We're starting early this year. SeventyThree(s).

On February 19, 2020 at 9:15 PM alan < zl3kr.alan@...> wrote:

 

 

After a recent windows crash and reinstallation of windows 10

 

I seem to have Logger32 working ok

 

computer is an I3  windows 10 pro

 

I use the utility program to load FLdigi and Log Sync and everything

appears o be working ok.

 

My problem is when I try to exit the program it fails to do so whether i

use the exit command

 

or click on the X to shut it down and I finish up force closing it. It

doesnt appear to do any harm

 

as it boots up fine next ime.

 

Is there something I have missed setting it up again or where would I

look to find

 

what is causing it.

 

It is not a major problem as everything seems to be working ok otherwise.

 

Thanks in advance for any help

 

Alan  ZL3KR

 

 

 

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX


Re: problem closing L32

alan
 

Hi Aki

just been trying different things to determine actually whqt is happening.

I stopped the L32 utility from booting Logsync....no change, L32 has to be forced close.

I then stopped L32 utility from booting Fldigi..... L32 closes cleanly.

If I Boot L32 and then seperately Boot Fldigi...L32 closes cleanly

Could I have something set incorrectly in the L32/Fldigi Gateway program??

It is almost sure to be something I have either not done or done wrong!!

Alan ZL3KR


On 20/02/2020 9:57 pm, ja1nlx wrote:

Alan

When you close Logger32, close LogSync first manually then close Logger32.

Keep watching for a several days in this way.

73


On 2020/02/20 17:46, alan wrote:

Hi Aki,

before I qrt for the night

I closed log sync , then FLdigi which closed cleanly after confirming closure(yes/no)

and then Logger 32 closed cleanly, so maybe Logsync is causing the closure problem??

Alan ZL3KR (QRT)


On 20/02/2020 9:39 pm, alan via Groups.Io wrote:

Thanks Aki

I will try that when I close down for the evening in a few minutes, incidentally FLdigi does not close down

at the same time, I generally have to close that seperately also, it previously closed  with logger 32

except it asked for confirmation Yes/no to close it.

I will tell you the result tomorrow mng here when I switch back on.

Alan ZL3KR


On 20/02/2020 8:51 pm, ja1nlx wrote:

Alan

If you are running other programs like LogSync etc then close those program first,

then close Logger32. What you see ?

73

On 2020/02/20 16:39, alan wrote:

It would seem there is a problem asking a simple question to a minor

problem, maybe the only solution is to delete logger 32 which I have used

for many years and still do. It previously closed without hassle and now fpr some

reason it no longer does, sorry to ask such a difficult question.

Alan ZL3KR


On 20/02/2020 3:26 pm, Bob wrote:
Still five weeks unil April 1st. We're starting early this year. SeventyThree(s).
On February 19, 2020 at 9:15 PM alan < zl3kr.alan@...> wrote:


After a recent windows crash and reinstallation of windows 10

I seem to have Logger32 working ok

computer is an I3  windows 10 pro

I use the utility program to load FLdigi and Log Sync and everything
appears o be working ok.

My problem is when I try to exit the program it fails to do so whether i
use the exit command

or click on the X to shut it down and I finish up force closing it. It
doesnt appear to do any harm

as it boots up fine next ime.

Is there something I have missed setting it up again or where would I
look to find

what is causing it.

It is not a major problem as everything seems to be working ok otherwise.

Thanks in advance for any help

Alan  ZL3KR



--
73 de aki
JA1NLX
--
73 de aki
JA1NLX


Re: problem closing L32

Rick Ellison
 

I have another issue I am looking at with Logsync. I will look at this to..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of alan
Sent: Thursday, February 20, 2020 3:46 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] problem closing L32

 

Hi Aki,

before I qrt for the night

I closed log sync , then FLdigi which closed cleanly after confirming closure(yes/no)

and then Logger 32 closed cleanly, so maybe Logsync is causing the closure problem??

Alan ZL3KR (QRT)

 

On 20/02/2020 9:39 pm, alan via Groups.Io wrote:

Thanks Aki

I will try that when I close down for the evening in a few minutes, incidentally FLdigi does not close down

at the same time, I generally have to close that seperately also, it previously closed  with logger 32

except it asked for confirmation Yes/no to close it.

I will tell you the result tomorrow mng here when I switch back on.

Alan ZL3KR

 

On 20/02/2020 8:51 pm, ja1nlx wrote:

Alan

If you are running other programs like LogSync etc then close those program first,

then close Logger32. What you see ?

73

On 2020/02/20 16:39, alan wrote:

It would seem there is a problem asking a simple question to a minor

problem, maybe the only solution is to delete logger 32 which I have used

for many years and still do. It previously closed without hassle and now fpr some

reason it no longer does, sorry to ask such a difficult question.

Alan ZL3KR

 

On 20/02/2020 3:26 pm, Bob wrote:

Still five weeks unil April 1st. We're starting early this year. SeventyThree(s).

On February 19, 2020 at 9:15 PM alan < zl3kr.alan@...> wrote:

 

 

After a recent windows crash and reinstallation of windows 10

 

I seem to have Logger32 working ok

 

computer is an I3  windows 10 pro

 

I use the utility program to load FLdigi and Log Sync and everything

appears o be working ok.

 

My problem is when I try to exit the program it fails to do so whether i

use the exit command

 

or click on the X to shut it down and I finish up force closing it. It

doesnt appear to do any harm

 

as it boots up fine next ime.

 

Is there something I have missed setting it up again or where would I

look to find

 

what is causing it.

 

It is not a major problem as everything seems to be working ok otherwise.

 

Thanks in advance for any help

 

Alan  ZL3KR

 

 

 

--
73 de aki
JA1NLX


Re: RCP macros for KENWOOD TS-870

VASILEIOS ROVAS
 

Thanks for both radio freinds!!!!!73 SV2HXX


Re: RCP macros for KENWOOD TS-870

Jim Altman
 

You can download from the Kenwood website a complete manual of all the computer commands. 

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of VASILEIOS ROVAS
Sent: Thursday, February 20, 2020 6:52 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] RCP macros for KENWOOD TS-870

 

Thanks for quick reply worked!!!Please tell me if exist any file to read for other macros (NB,NR, etc) for this rig because i have only basic macros...Thanks a lot!!


Re: RCP macros for KENWOOD TS-870

VASILEIOS ROVAS
 

Thanks for quick reply worked!!!Please tell me if exist any file to read for other macros (NB,NR, etc) for this rig because i have only basic macros...Thanks a lot!!


Re: RCP macros for KENWOOD TS-870

ja1nlx
 

Try this....

CW  $command MD3;$

USB   $command MD2;$

LSB    $command MD1;$

FSK    $command MD6;$

73

On 2020/02/20 20:31, VASILEIOS ROVAS wrote:
Hello Hamfreinds!!!
I use logger32 with kenwood ts-870 ,need macros for RCP to change mode(USB,LSB,CW,FSK).I see in the help files but not find any details for help me!!!
73 to all.
SV2HXX
--
73 de aki
JA1NLX


RCP macros for KENWOOD TS-870

VASILEIOS ROVAS
 

Hello Hamfreinds!!!
I use logger32 with kenwood ts-870 ,need macros for RCP to change mode(USB,LSB,CW,FSK).I see in the help files but not find any details for help me!!!
73 to all.
SV2HXX


Re: problem closing L32

ja1nlx
 

Alan

When you close Logger32, close LogSync first manually then close Logger32.

Keep watching for a several days in this way.

73


On 2020/02/20 17:46, alan wrote:

Hi Aki,

before I qrt for the night

I closed log sync , then FLdigi which closed cleanly after confirming closure(yes/no)

and then Logger 32 closed cleanly, so maybe Logsync is causing the closure problem??

Alan ZL3KR (QRT)


On 20/02/2020 9:39 pm, alan via Groups.Io wrote:

Thanks Aki

I will try that when I close down for the evening in a few minutes, incidentally FLdigi does not close down

at the same time, I generally have to close that seperately also, it previously closed  with logger 32

except it asked for confirmation Yes/no to close it.

I will tell you the result tomorrow mng here when I switch back on.

Alan ZL3KR


On 20/02/2020 8:51 pm, ja1nlx wrote:

Alan

If you are running other programs like LogSync etc then close those program first,

then close Logger32. What you see ?

73

On 2020/02/20 16:39, alan wrote:

It would seem there is a problem asking a simple question to a minor

problem, maybe the only solution is to delete logger 32 which I have used

for many years and still do. It previously closed without hassle and now fpr some

reason it no longer does, sorry to ask such a difficult question.

Alan ZL3KR


On 20/02/2020 3:26 pm, Bob wrote:
Still five weeks unil April 1st. We're starting early this year. SeventyThree(s).
On February 19, 2020 at 9:15 PM alan < zl3kr.alan@...> wrote:


After a recent windows crash and reinstallation of windows 10

I seem to have Logger32 working ok

computer is an I3  windows 10 pro

I use the utility program to load FLdigi and Log Sync and everything
appears o be working ok.

My problem is when I try to exit the program it fails to do so whether i
use the exit command

or click on the X to shut it down and I finish up force closing it. It
doesnt appear to do any harm

as it boots up fine next ime.

Is there something I have missed setting it up again or where would I
look to find

what is causing it.

It is not a major problem as everything seems to be working ok otherwise.

Thanks in advance for any help

Alan  ZL3KR



--
73 de aki
JA1NLX
--
73 de aki
JA1NLX


Re: problem closing L32

alan
 

Hi Aki,

before I qrt for the night

I closed log sync , then FLdigi which closed cleanly after confirming closure(yes/no)

and then Logger 32 closed cleanly, so maybe Logsync is causing the closure problem??

Alan ZL3KR (QRT)


On 20/02/2020 9:39 pm, alan via Groups.Io wrote:

Thanks Aki

I will try that when I close down for the evening in a few minutes, incidentally FLdigi does not close down

at the same time, I generally have to close that seperately also, it previously closed  with logger 32

except it asked for confirmation Yes/no to close it.

I will tell you the result tomorrow mng here when I switch back on.

Alan ZL3KR


On 20/02/2020 8:51 pm, ja1nlx wrote:

Alan

If you are running other programs like LogSync etc then close those program first,

then close Logger32. What you see ?

73

On 2020/02/20 16:39, alan wrote:

It would seem there is a problem asking a simple question to a minor

problem, maybe the only solution is to delete logger 32 which I have used

for many years and still do. It previously closed without hassle and now fpr some

reason it no longer does, sorry to ask such a difficult question.

Alan ZL3KR


On 20/02/2020 3:26 pm, Bob wrote:
Still five weeks unil April 1st. We're starting early this year. SeventyThree(s).
On February 19, 2020 at 9:15 PM alan < zl3kr.alan@...> wrote:


After a recent windows crash and reinstallation of windows 10

I seem to have Logger32 working ok

computer is an I3  windows 10 pro

I use the utility program to load FLdigi and Log Sync and everything
appears o be working ok.

My problem is when I try to exit the program it fails to do so whether i
use the exit command

or click on the X to shut it down and I finish up force closing it. It
doesnt appear to do any harm

as it boots up fine next ime.

Is there something I have missed setting it up again or where would I
look to find

what is causing it.

It is not a major problem as everything seems to be working ok otherwise.

Thanks in advance for any help

Alan  ZL3KR



--
73 de aki
JA1NLX


Re: problem closing L32

alan
 

Thanks Aki

I will try that when I close down for the evening in a few minutes, incidentally FLdigi does not close down

at the same time, I generally have to close that seperately also, it previously closed  with logger 32

except it asked for confirmation Yes/no to close it.

I will tell you the result tomorrow mng here when I switch back on.

Alan ZL3KR


On 20/02/2020 8:51 pm, ja1nlx wrote:

Alan

If you are running other programs like LogSync etc then close those program first,

then close Logger32. What you see ?

73

On 2020/02/20 16:39, alan wrote:

It would seem there is a problem asking a simple question to a minor

problem, maybe the only solution is to delete logger 32 which I have used

for many years and still do. It previously closed without hassle and now fpr some

reason it no longer does, sorry to ask such a difficult question.

Alan ZL3KR


On 20/02/2020 3:26 pm, Bob wrote:
Still five weeks unil April 1st. We're starting early this year. SeventyThree(s).
On February 19, 2020 at 9:15 PM alan < zl3kr.alan@...> wrote:


After a recent windows crash and reinstallation of windows 10

I seem to have Logger32 working ok

computer is an I3  windows 10 pro

I use the utility program to load FLdigi and Log Sync and everything
appears o be working ok.

My problem is when I try to exit the program it fails to do so whether i
use the exit command

or click on the X to shut it down and I finish up force closing it. It
doesnt appear to do any harm

as it boots up fine next ime.

Is there something I have missed setting it up again or where would I
look to find

what is causing it.

It is not a major problem as everything seems to be working ok otherwise.

Thanks in advance for any help

Alan  ZL3KR



--
73 de aki
JA1NLX


Re: problem closing L32

ja1nlx
 

Alan

If you are running other programs like LogSync etc then close those program first,

then close Logger32. What you see ?

73

On 2020/02/20 16:39, alan wrote:

It would seem there is a problem asking a simple question to a minor

problem, maybe the only solution is to delete logger 32 which I have used

for many years and still do. It previously closed without hassle and now fpr some

reason it no longer does, sorry to ask such a difficult question.

Alan ZL3KR


On 20/02/2020 3:26 pm, Bob wrote:
Still five weeks unil April 1st. We're starting early this year. SeventyThree(s).
On February 19, 2020 at 9:15 PM alan < zl3kr.alan@...> wrote:


After a recent windows crash and reinstallation of windows 10

I seem to have Logger32 working ok

computer is an I3  windows 10 pro

I use the utility program to load FLdigi and Log Sync and everything
appears o be working ok.

My problem is when I try to exit the program it fails to do so whether i
use the exit command

or click on the X to shut it down and I finish up force closing it. It
doesnt appear to do any harm

as it boots up fine next ime.

Is there something I have missed setting it up again or where would I
look to find

what is causing it.

It is not a major problem as everything seems to be working ok otherwise.

Thanks in advance for any help

Alan  ZL3KR



--
73 de aki
JA1NLX

3161 - 3180 of 82107