toggle quoted messageShow quoted text
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
On 21/02/2020 4:06 pm, Rick Ellison
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.
just been trying different things to determine actually whqt
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
If I Boot L32 and then seperately Boot Fldigi...L32 closes
Could I have something set incorrectly in the L32/Fldigi
It is almost sure to be something I have either not done or
On 20/02/2020 9:57 pm, ja1nlx wrote:
When you close Logger32, close LogSync first manually then
Keep watching for a several days in this way.
On 2020/02/20 17:46, alan wrote:
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
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.
On 20/02/2020 8:51 pm, ja1nlx
If you are running other programs like LogSync etc
then close those program first,
then close Logger32. What you see ?
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
On 20/02/2020 3:26 pm, Bob
Still five weeks unil April
1st. We're starting early this year.
After a recent windows
crash and reinstallation of windows 10
I seem to have Logger32
computer is an I3 windows
I use the utility program
to load FLdigi and Log Sync and everything
My problem is when I try to
exit the program it fails to do so whether i
or click on the X to shut
it down and I finish up force closing it. It
doesnt appear to do any
as it boots up fine next
Is there something I have
missed setting it up again or where would I
It is not a major problem
as everything seems to be working ok
Thanks in advance for any