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

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

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

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

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

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)

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

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!!

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

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

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

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

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