Date   

Re: Auto-update v4.0.236 is on-line ...

n5kd
 

Hi Patrick

The upgrade from version 3.xxx to 4.xxx is only available at the Logger32 web page. It is not an automatic update.

 

https://www.logger32.net/

 

Be careful to follow the instructions. Be sure to export your logs as ADIF file first, and save a copy.

 

73’ Pete, N5KD.

 

From: tk5ep
Sent: Sunday, January 24, 2021 9:57 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Auto-update v4.0.236 is on-line ...

 

Hi,
Not available here with 3.50.424....

73 Patrick

 


Virus-free. www.avg.com


Re: Auto-update v4.0.236 is on-line ...

tk5ep
 

Hi,
Not available here with 3.50.424....

73 Patrick


Re: Log search problem

ct1fjo nuno <ct1fjo@...>
 

Hi all...

Sorry for my late answer....

Aki, in logbook page, I've select search qso.

When I try to scroll up and down, only goes up.

If I press shift at the same time, it does work, but on previous versions, I didn't need to do that.



73

Cts
Nuno Silva


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Ken McVie <kenmcvie2@...>
Sent: Friday, January 22, 2021 6:28:06 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Log search problem
 

Works fine here with both QSO number & date.

Update also went smoothly. Did a recalc. but not sure it was necessary. All ports & sound systems working as before. W10 op. system.

Many thanks Bob [& others involved] for a great program.

73

Ken ZL4NR


On 22/01/2021 5:22 pm, Chris G4FJW wrote:

Just realised this problem only occurs when sorting by QSO number if you sort by date the scrolling is fine.

Chris.. G4FJW

On 22/01/2021 03:18, Chris G4FJW wrote:

I think what Nuno means is that you can't scroll back through QSOs in the logbook window with the scroll wheel,  forwards scroll is OK and shift/scroll works.

Chris.. G4fjw 

On 22/01/2021 00:35, ja1nlx wrote:

Nuno

You mean "Search for QSO" in Logbook page window ?

It works for me. Give us step-by step how you search ?

73

On 2021/01/22 8:59, ct1fjo nuno wrote:
Hi all

I upgraded from version 3.50.424 to version 4.0.132 according to the instructions in the help. Everything was working as before including the search for QSO in the log. When the program made an automatic update to version 4.0.235, the search function in the log, the cursor only makes up making the search difficult. Has anyone checked this problem ??

Cts
Nuno Silva
--
73 de aki
JA1NLX


Re: DLL problem from Vsamex.dll causes the crash Logger32 go down when telnet to the cluster is ON

Bob
 

VSAMEX.DLL is the database engine. I have connected to IK5PWJ-6 Telnet cluster all day. No problems. 73.

On 01/23/2021 1:31 PM Alex Del Chicca <ik5pwj@...> wrote:
 
 

Hi all,

the error that causes the Logger32 program to close as explained in the msg. that I report below,

is shown in the Windows 10 PRO 64 Bit Event Viewer that I am using.

 

Below I insert the msg. Error found in Windows Logs / Application Level / Error / General:

Logger32.exe

    4.0.0.235

    60033d98

    Vsamex.dll

    6.4.0.0

    5ef1b226

    c0000005

    0004c1f8

    3eb4

    01d6f1a815c7ee68

    C: \ Logger32 \ Logger32.exe

    C: \ Logger32 \ Vsamex.dll

    60a100e9-fd17-4058-b14a-fc25b3d571f3

 

And in Windows / Application Level / Error / Details:

 

Name of the application that generated the logger32.exe error vers 4.0.0.235, timestamp: 0x60033d98

Module name etc .....

Exception code: 0x c0000005

Error offset 0x0004c 1f8

....

Path to the module that generated the error: C: \ Logger32 \ Vsamex.dll

 

So ….i’s    Vsamex.dll    that causes the Logger32.exe program crash to close

Anyone know why and how to solve this problem?

Thanks

73 Alex ik5pwj.

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Alex Del Chicca via groups.io
Inviato: sabato 23 gennaio 2021 17:24
A: hamlogger@groups.io
Oggetto: [hamlogger] Logger32 go down when telnet to the cluster is ON

 

Hi to ALL,

I upgraded from the latest version 3.5 to version 4.0 without any errors.

After doing database maintenance and updating statistics, I updated to ver. 4.0.235 without problems.

 

The open windows are: Operator :, Dx Spots, Worked / Confirmed Logbook page, Previous QSOs and Telnet for IK5PWJ-6 cluster connection,

I also opened the CW Machine window.

Unfortunately after some time, sometimes 30 min. others after an hour the Logger32 program closes, leaving only the window outside

the Logger32 Window of the CW Machine open.

 

In practice the window of Logger32 disappears.

 

I then made several tests, reinstalling the logger32 vers. 4 from vers. 3.5 where I had previously deleted all the log

and then reinstalled the ik5pwj log from the previously saved adif file.

 

Unfortunately, the problem reoccurred by going the Logger32 program down and always remaining the CW Machine -Software window.

 

At this point I did a test and I disabled the connection via telnet to the cluster no longer receiving the spots both

in the Telnet window and in the DX Spot window.

 

Well .... the Logger32 program ran for hours without closing.

I am sure that the block depends on the right spots that the telnet receives and sends to the DX Spots window,

because if I reactivate the telnet connection and the spots start to arrive again, the program goes down again.

 

What's up ? and how can this problem be eliminated?

 

When I use the same configurations on the latest version of the program vers. 3.5 .... everything works,

including telnet and spot-free spots or whatever.

 

Thanks for any Help

73 Alex ik5pwj.

 


Re: Auto-update v4.0.236 is on-line ...

NICK K. PLUMIDAKIS
 

Now it is O.K.

Best 73’s

DE

Nick

SV1VS

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, 23 January, 2021 19:59
To: hamlogger@groups.io
Subject: [hamlogger] Auto-update v4.0.236 is on-line ...

 

<no text>


DLL problem from Vsamex.dll causes the crash Logger32 go down when telnet to the cluster is ON

Alex Del Chicca
 

Hi all,

the error that causes the Logger32 program to close as explained in the msg. that I report below,

is shown in the Windows 10 PRO 64 Bit Event Viewer that I am using.

 

Below I insert the msg. Error found in Windows Logs / Application Level / Error / General:

Logger32.exe

    4.0.0.235

    60033d98

    Vsamex.dll

    6.4.0.0

    5ef1b226

    c0000005

    0004c1f8

    3eb4

    01d6f1a815c7ee68

    C: \ Logger32 \ Logger32.exe

    C: \ Logger32 \ Vsamex.dll

    60a100e9-fd17-4058-b14a-fc25b3d571f3

 

And in Windows / Application Level / Error / Details:

 

Name of the application that generated the logger32.exe error vers 4.0.0.235, timestamp: 0x60033d98

Module name etc .....

Exception code: 0x c0000005

Error offset 0x0004c 1f8

....

Path to the module that generated the error: C: \ Logger32 \ Vsamex.dll

 

So ….i’s    Vsamex.dll    that causes the Logger32.exe program crash to close

Anyone know why and how to solve this problem?

Thanks

73 Alex ik5pwj.

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Alex Del Chicca via groups.io
Inviato: sabato 23 gennaio 2021 17:24
A: hamlogger@groups.io
Oggetto: [hamlogger] Logger32 go down when telnet to the cluster is ON

 

Hi to ALL,

I upgraded from the latest version 3.5 to version 4.0 without any errors.

After doing database maintenance and updating statistics, I updated to ver. 4.0.235 without problems.

 

The open windows are: Operator :, Dx Spots, Worked / Confirmed Logbook page, Previous QSOs and Telnet for IK5PWJ-6 cluster connection,

I also opened the CW Machine window.

Unfortunately after some time, sometimes 30 min. others after an hour the Logger32 program closes, leaving only the window outside

the Logger32 Window of the CW Machine open.

 

In practice the window of Logger32 disappears.

 

I then made several tests, reinstalling the logger32 vers. 4 from vers. 3.5 where I had previously deleted all the log

and then reinstalled the ik5pwj log from the previously saved adif file.

 

Unfortunately, the problem reoccurred by going the Logger32 program down and always remaining the CW Machine -Software window.

 

At this point I did a test and I disabled the connection via telnet to the cluster no longer receiving the spots both

in the Telnet window and in the DX Spot window.

 

Well .... the Logger32 program ran for hours without closing.

I am sure that the block depends on the right spots that the telnet receives and sends to the DX Spots window,

because if I reactivate the telnet connection and the spots start to arrive again, the program goes down again.

 

What's up ? and how can this problem be eliminated?

 

When I use the same configurations on the latest version of the program vers. 3.5 .... everything works,

including telnet and spot-free spots or whatever.

 

Thanks for any Help

73 Alex ik5pwj.


Re: Auto-update v4.0.236 is on-line ...

Dave Colliau
 

All good now
Dave N8DC

On 01/23/2021 1:19 PM Dave Colliau <n8dc-8@...> wrote:
 
 
Im at 235 and no updates.
Dave N8DC
On 01/23/2021 12:58 PM Bob <k4cy@...> wrote:
 
 
<no text>


Re: Auto-update v4.0.236 is on-line ...

Dave Colliau
 

Im at 235 and no updates.
Dave N8DC

On 01/23/2021 12:58 PM Bob <k4cy@...> wrote:
 
 
<no text>


Re: Auto-update v4.0.236 is on-line ...

NICK K. PLUMIDAKIS
 

Dear Bob Hi.

I am getting err msg as att.

Best 73’s

DE

Nick

SV1VS

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, 23 January, 2021 19:59
To: hamlogger@groups.io
Subject: [hamlogger] Auto-update v4.0.236 is on-line ...

 

<no text>


Re: V4. When using WSIT-x Manual Logging

Bob
 

... but when operating wsjt-x there is no radio control involved. So, theoretically, two radios or twenty radios operating wsjt-x makes no difference. What has not been described is what is the anticipated role of the logging program in this hypothetical setup. Is it simply a repository for the QSOs? SeventyThree(s).

On 01/23/2021 12:57 PM n5kd <n5kd@...> wrote:
 
 

Logger32 only does one radio at a time, but it easy to use CTRL-T to toggle between them.

 

N1MM+ will do two radios at the same time when set to SO2R operation. However it doesn’t do the other good stuff that L32 does. It’s a contest program after all.

 

73’ Pete, N5KD.

 

From: k4cvl
Sent: Saturday, January 23, 2021 5:07 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] V4. When using WSIT-x Manual Logging

 

I have a question that perhaps one of more members of the group can answer.  I am looking for a logging program that will allow me to use TWO radios at the same time, allowing BOTH access to the logbook, that will log at the same time if necessary.  I am using the Yaesu FTDx101MP now with a Flex 6700.  I was using Logger 32 with my FT-5000 radio, but thought I would try using  Log4OM for logging to see if it will do the trick. A buddy who is really good at IT stuff says that it can work in the way I want it to, but has yet to make it work. I run TWO radios and TWO PCs on my home network.  I want to put the logging software on both and operate with both being able to work as the other.  Does anyone know FOR SURE if Logger 32 or any of the many logging programs out there will do this?  - Mike, K4CVL

 

 

 


Virus-free. www.avg.com


Auto-update v4.0.236 is on-line ...

Bob
 

<no text>


Re: V4. When using WSIT-x Manual Logging

n5kd
 

Logger32 only does one radio at a time, but it easy to use CTRL-T to toggle between them.

 

N1MM+ will do two radios at the same time when set to SO2R operation. However it doesn’t do the other good stuff that L32 does. It’s a contest program after all.

 

73’ Pete, N5KD.

 

From: k4cvl
Sent: Saturday, January 23, 2021 5:07 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] V4. When using WSIT-x Manual Logging

 

I have a question that perhaps one of more members of the group can answer.  I am looking for a logging program that will allow me to use TWO radios at the same time, allowing BOTH access to the logbook, that will log at the same time if necessary.  I am using the Yaesu FTDx101MP now with a Flex 6700.  I was using Logger 32 with my FT-5000 radio, but thought I would try using  Log4OM for logging to see if it will do the trick. A buddy who is really good at IT stuff says that it can work in the way I want it to, but has yet to make it work. I run TWO radios and TWO PCs on my home network.  I want to put the logging software on both and operate with both being able to work as the other.  Does anyone know FOR SURE if Logger 32 or any of the many logging programs out there will do this?  - Mike, K4CVL

 

 


Virus-free. www.avg.com


Re: Ver 4 crashes with L32Log Sync.

Tom Wylie
 

 NO, mine is working perfectly.

Tom 
GM4FDM 

On Sat, 23 Jan 2021, 14:17 Chuck Kraly K0XM, <k0xm@...> wrote:
I have updated to Ver4  completely and noticed that JTDX-TCP to L32 works but every now and then L32 will crash when sending to LOTW, or Clublog, Or QRZ (i run all 3). Has anyone else seen this?
Chuck K0XM


Re: V4. When using WSIT-x Manual Logging

John Owens
 

Logger32 will do all that you want, and more. The unfortunate thing is that it is free so you can't take advantage of a money back guarantee. I have been using it for 18 years now, and don't use but a small part of what it can do. It is very well supported, with about 1 rev/wk. They just did a major revision to 4.0, but the full install is still not available from their website, but soon will be (week or so). Only an upgrade from previous 3.50xx . 
 
The new version is much faster, and the databases are bottomless. I use it for direct control of JTDX and RTTY. I have 16250 QSO's in my log now which is rather small considering that I am not into contesting. I have 124 countries on FT8 now, and 172 on RTTY, all worked and logged directly from L32. Millions of  satisfied customers, and great help through their reflector. You will never have to pay for it. 

On 01/23/2021 9:07 AM k4cvl <mryan001@...> wrote:
 
 

I have a question that perhaps one of more members of the group can answer.  I am looking for a logging program that will allow me to use TWO radios at the same time, allowing BOTH access to the logbook, that will log at the same time if necessary.  I am using the Yaesu FTDx101MP now with a Flex 6700.  I was using Logger 32 with my FT-5000 radio, but thought I would try using  Log4OM for logging to see if it will do the trick. A buddy who is really good at IT stuff says that it can work in the way I want it to, but has yet to make it work. I run TWO radios and TWO PCs on my home network.  I want to put the logging software on both and operate with both being able to work as the other.  Does anyone know FOR SURE if Logger 32 or any of the many logging programs out there will do this?  - Mike, K4CVL

 


L32 v.4 Sound card data window wont open mmtty

Borut Gaberscek
 

HI.

Tray to work rtty from a long time.....when I press the sound card button, mmtty it refuses to open. When I press the option in VIEW/show sound card data, l32 switch off completely.

How to fix this? 

73 de Borut s50b


Re: V4. When using WSIT-x Manual Logging

k4cvl
 

I have a question that perhaps one of more members of the group can answer.  I am looking for a logging program that will allow me to use TWO radios at the same time, allowing BOTH access to the logbook, that will log at the same time if necessary.  I am using the Yaesu FTDx101MP now with a Flex 6700.  I was using Logger 32 with my FT-5000 radio, but thought I would try using  Log4OM for logging to see if it will do the trick. A buddy who is really good at IT stuff says that it can work in the way I want it to, but has yet to make it work. I run TWO radios and TWO PCs on my home network.  I want to put the logging software on both and operate with both being able to work as the other.  Does anyone know FOR SURE if Logger 32 or any of the many logging programs out there will do this?  - Mike, K4CVL

 


Logger32 go down when telnet to the cluster is ON

Alex Del Chicca
 

Hi to ALL,

I upgraded from the latest version 3.5 to version 4.0 without any errors.

After doing database maintenance and updating statistics, I updated to ver. 4.0.235 without problems.

 

The open windows are: Operator :, Dx Spots, Worked / Confirmed Logbook page, Previous QSOs and Telnet for IK5PWJ-6 cluster connection,

I also opened the CW Machine window.

Unfortunately after some time, sometimes 30 min. others after an hour the Logger32 program closes, leaving only the window outside

the Logger32 Window of the CW Machine open.

 

In practice the window of Logger32 disappears.

 

I then made several tests, reinstalling the logger32 vers. 4 from vers. 3.5 where I had previously deleted all the log

and then reinstalled the ik5pwj log from the previously saved adif file.

 

Unfortunately, the problem reoccurred by going the Logger32 program down and always remaining the CW Machine -Software window.

 

At this point I did a test and I disabled the connection via telnet to the cluster no longer receiving the spots both

in the Telnet window and in the DX Spot window.

 

Well .... the Logger32 program ran for hours without closing.

I am sure that the block depends on the right spots that the telnet receives and sends to the DX Spots window,

because if I reactivate the telnet connection and the spots start to arrive again, the program goes down again.

 

What's up ? and how can this problem be eliminated?

 

When I use the same configurations on the latest version of the program vers. 3.5 .... everything works,

including telnet and spot-free spots or whatever.

 

Thanks for any Help

73 Alex ik5pwj.


Re: CQWPX

Nicola Favero
 

Same problem here ! 

 

logger 3.250.424 

 

Logger 3_50_424.jpg

 

logger 4.0.235 : stop at 5k pfx

 

Logger 4_0_235.jpg

 

73

 

Nick i3fiy

 

Da: hamlogger@groups.io [mailto:hamlogger@groups.io] Per conto di Preben Dall Larsen
Inviato: venerdì 22 gennaio 2021 06:45
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] CQWPX

 

Hi Gary and Carlo,

v4.0.235
Recalculation done.

I see the same, however, mine stops at UP0
and with a total of 5001 PFXs worked!

 

billede.png


73
Preben OZ5UR


Ver 4 crashes with L32Log Sync.

Chuck Kraly K0XM
 

I have updated to Ver4  completely and noticed that JTDX-TCP to L32 works but every now and then L32 will crash when sending to LOTW, or Clublog, Or QRZ (i run all 3). Has anyone else seen this?
Chuck K0XM


V4. When using WSIT-x Manual Logging

DamianM0BKV
 

I have a change with V4. When using WSIT-x in that the populated Logger32 logbook entry window, that occurs automatically, when 'Enable TX' is activated on the WSIT-x window (so as to start a QSO not call CQ) disappears equally fast when '73' is received from the contact without waiting for the MANUAL LOg the QSO from me. all populated QSO information from QRZ with name is lost unless I manually repopulate the Logger32 logbook window again from the callsign if it's still in the UDP Bandplan Window before I manually log. With V3 this didn't happen. If I set auto Log (with V4) on receive of 73 it probably is OK but I like to manual log.
Otherwise, V4 works great Bob. Damian M0BKV

1841 - 1860 of 83973