Date   

Re: 5 questions

Gary Hinson
 

1. Why  L32 not able to always display the DX spots, despite being connected to VE6DXC? CAT works fine. Making a right-click over the VE6DXC at the bottom, shows that it is connected.

 

DX cluster spots can be filtered by Logger32.  Do you have any cluster filters in use, Radhames?  Right-click the DX Spots window then check under Setup à DX Spot Blocking/Pass Filters … ( have not any cluster filters in use. All options are unmarked....Looks like it's without an internet connection. Think that VE6DXC is the default DX spot source for L32. I don't know if from logger I could access other different sources, other than the VE6DXC)

 

It sounds as if you are having a problem with that specific cluster, Radhames.  I guess the feed is unreliable.

 

You can select any DXcluster you like, Radhames, using the Telnet connection pane I gave in my reply to your second question … 

 

To see the Telnet connection pane, right-click in the Telnet window, then go to Setup, then Setup remote hosts

 

 

 

 

2. Is it possible to have other sources available for DX spots, other than VE6DXC?

 

Yes … but I think not directly in Logger32: (I understand) I believe Logger32 can only connect to one DX cluster at a time (if that’s what you mean). (I was not talking about at a time or at once. I wanted to say to other DX cluster different to VE6DXC from logger) One solution is to install and run VE7CC’s Cluster User program on your computer: (I just to download it. I will try to test it) it can connect to several DX clusters in parallel, combining all the spots and passing them on to other programs (such as Logger32) through the local network.(Please teach me how passing them to Logger32. I will appreciate)   Logger32 on my PC connects to a DXcluster called “Local”, which is where Cluster User sends the spots: (I will try to do it. Hope it works)

 

 

 

Look for lists on the web of DXcluster nodes with their addresses and port numbers, Radhames.  If it helps, I find VE7CC’s cluster good overall, QRV 24x7 except occasionally while Lee is contesting.  His cluster address is VE7CC.net port 7373.   

 

These are the 4 clusters I use most of the time, often connecting to 2 in parallel through the Cluster User program, sometimes more than 2:

 

 

 

3. For what reason  I only have comm port 3 available?

 

Errr, sorry, I do not understand your question.  Do you expect Logger32 to give you extra comm ports? (No, of course. I understand comm ports does not associate to a specific software but to the Window operating system. In my case, my Toshiba laptop only "say" to me, it has only the comm port 3, and none more. Since I came from Mac world to Window, I don't understand too much about comm ports, how to get others, etc.  As I only have comm port 3, if I open other software that uses the same port, then I have to close L32 to allow the new app can use it. Hope you understand better now)  

 

Windows normally selects Com addresses for physical or virtual communications ports that exist on the system – one address per port.  If you want another port address, the obvious way is to add another port e.g. plug in a USB to RS232 adapter dongle.

 

 

4. Why does the SUMMARYQSObyM hode utility only show a few years through 1992 to 2009 (9,367 contacts) when I have many thousands QSOs logged from 1978? (16,704)

 

[Aki is helping you with this] Yes. Aki did contact me. He is a very kind person that likes to help unexpert L32 users. He suggestion me send my ADIF log. I will send it him shortly today. In a few minutes)

 

 

5. What to do to have other ports that could be used with L32 and other applications, simultaneously?

 

Sorry, I do not understand this question either.  Maybe someone else can help, or you might explain what you mean.    

 I wanted to say or I meant that if I had two or more ports available, then I could use L32 simultaneously with other software. Because L32 uses my only port, which is comm port 3. Other programs use the same port, so I can't use them at the same time as Logger. Maybe you understand me better. My English is bad, I'm sorry.

 

Your English is OK Radhames.  My Spanish is terrible!

 

It sounds as if you want to share the single CAT connection to your rig between more than one CAT control program. 

 

I agree with John:

 

I think the OP in the above might be referring to port splitting / sharing (not sure of the correct term myself) for which he may need to look at the following;

http://com0com.sourceforge.net/

http://www.eterlogic.com/Products.VSPE.html

 

In my case, I am using an Elecraft K3 radio with a single RS232 serial connection via a USB-serial adapter and a “physical” port address of Com 3.  On my PC, I run “LP Bridge v1.1.0” software which connects through Com3 to the K3 … and also creates several “virtual” com ports so that other programs can share the K3 CAT connection:

 

 

As I write this, I have three virtual com ports open, Com11 (used by JTDX – which needs to be on virtual Com Port #1), Com12 (for Logger32) and Com13 (for N1MM+ when I am contesting).  LP Bridge handles them all OK, in parallel, with just a few little problems (occasionally it crashes, and it is slow to change bands, often losing the change mode command if sent at the same time) … but I believe it only works with the K3.  For other radios, you would need to find another com-port-sharing utility.

 

73s & GL Radhames

Gary  ZL2iFB

 

 


New HFAUTO Version 3.9.3.5 Confirmed Working with Logger32 Version 3.50.406

Terry Glagowski / W1TR / AFA1DI
 

Dear Logger32 Users with W1TR HFAUTO software…

The new HFAUTO Version 3.9.3.5 Confirmed Working with Logger32 Version 3.50.406

Available at:

http://www.glagowski.org/radio/Software.htm

 

73, Terry / W1TR  :  )


Re: 5 questions

HI3B Radhames
 




From: hamlogger@groups.io <hamlogger@groups.io> on behalf of John Munton - G7SSE <johng7sse@...>
Sent: Tuesday, January 21, 2020 1:02 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] 5 questions
 
"5. What to do to have other ports that could be used with L32 and other applications, simultaneously?"

I think the OP in the above might be referring to port splitting / sharing (not sure of the correct term myself) for which he may need to look at the following; (I just to talk with a local computer technician. He said to me that for my proposal I need to bu a device adaptor from USB to DB9.   I forgot to ask him what DB9 means, but I guess it means 9 new possibilities to have new comm ports. with this device then he said to me that I can assign a new or different comm port to be used by another application. Then I could use it simultaneously it with Logger32, which could use the old the comm port 3. Hope you understand better now)

http://com0com.sourceforge.net/

http://www.eterlogic.com/Products.VSPE.html

73, John - G7SSE

--
HI3B


Re: 5 questions

HI3B Radhames
 

Thanks Gary for your suggestions, 
shortly commented below.


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Gary Hinson <Gary@...>
Sent: Monday, January 20, 2020 11:44 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] 5 questions
 frrrr

1. Why  L32 not able to always display the DX spots, despite being connected to VE6DXC? CAT works fine. Making a right-click over the VE6DXC at the bottom, shows that it is connected.

 

DX cluster spots can be filtered by Logger32.  Do you have any cluster filters in use, Radhames?  Right-click the DX Spots window then check under Setup à DX Spot Blocking/Pass Filters … ( have not any cluster filters in use. All options are unmarked....Looks like it's without an internet connection. Think that VE6DXC is the default DX spot source for L32. I don't know if from logger I could access other different sources, other than the VE6DXC)

 

 

 

2. Is it possible to have other sources available for DX spots, other than VE6DXC?

 

Yes … but I think not directly in Logger32: (I understand) I believe Logger32 can only connect to one DX cluster at a time (if that’s what you mean). (I was not talking about at a time or at once. I wanted to say to other DX cluster different to VE6DXC from logger) One solution is to install and run VE7CC’s Cluster User program on your computer: (I just to download it. I will try to test it) it can connect to several DX clusters in parallel, combining all the spots and passing them on to other programs (such as Logger32) through the local network.(Please teach me how passing them to Logger32. I will appreciate)   Logger32 on my PC connects to a DXcluster called “Local”, which is where Cluster User sends the spots: (I will try to do it. Hope it works)

 

 

 

3. For what reason  I only have comm port 3 available?

 

Errr, sorry, I do not understand your question.  Do you expect Logger32 to give you extra comm ports? (No, of course. I understand comm ports does not associate to a specific software but to the Window operating system. In my case, my Toshiba laptop only "say" to me, it has only the comm port 3, and none more. Since I came from Mac world to Window, I don't understand too much about comm ports, how to get others, etc.  As I only have comm port 3, if I open other software that uses the same port, then I have to close L32 to allow the new app can use it. Hope you understand better now)  

 

 

4. Why does the SUMMARYQSObyM hode utility only show a few years through 1992 to 2009 (9,367 contacts) when I have many thousands QSOs logged from 1978? (16,704)

 

[Aki is helping you with this] Yes. Aki did contact me. He is a very kind person that likes to help unexpert L32 users. He suggestion me send my ADIF log. I will send it him shortly today. In a few minutes)

 

 

5. What to do to have other ports that could be used with L32 and other applications, simultaneously?

 

Sorry, I do not understand this question either.  Maybe someone else can help, or you might explain what you mean.    

 I wanted to say or I meant that if I had two or more ports available, then I could use L32 simultaneously with other software. Because L32 uses my only port, which is comm port 3. Other programs use the same port, so I can't use them at the same time as Logger. Maybe you understand me better. My English is bad, I'm sorry.

73s & GL Radhames

Gary  ZL2iFB

 


--
HI3B


Re: "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

Bob
 

Both WSJT and JTDX work as expected for me. I recommend using JTDX, it is (IMHO) superior, and has solved the problem you report for others. SeventyThree(s).

On January 21, 2020 at 10:12 AM Joe Ivey <jivey0218@...> wrote:

My problem is after the Log Entry Window is populated either manually or from the Lookup Window everything is fine. When I log from WSJTX, all of the information is not carried over to the Logbook. QTH, Name, and State is not logged. If I hit ENTER before logging then everything is logged.

W4JSI, Joe

 

-----------------------------------------

From: "Bob"
To: hamlogger@groups.io
Cc:
Sent: Monday January 20 2020 3:37:12PM
Subject: Re: [hamlogger] "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

... not quite ... First, on the UDP BandMap window, click CONFIG and check the ENABLE CALLSIGN LOOKUP WHEN CLICKING ON WJT/JTDX. Now, when you double click on a callsign on WSJT/JTDX Band Activity window, the Logbook Entry Window in Logger32 will be populated with the callsign. Then, automagically the Callsign lookup will complete and populate the Logbook Entry Window with additional information (if you're lucky). SeventyThree(s).
On January 20, 2020 at 4:30 PM Gary Wilson <k2gw@...> wrote:

I kind of have the same issue.  Please clarify this first step:

"When you type W5IDX in Logbook entry window, do you see auto lookup window ?

 

and Name, State etc are populated in Logbook entry window ?"

I do, but they only after I hit "return".  Is that what you mean? Or should they instantly fill in?

 


 

 


Re: "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

Joe Ivey
 

My problem is after the Log Entry Window is populated either manually or from the Lookup Window everything is fine. When I log from WSJTX, all of the information is not carried over to the Logbook. QTH, Name, and State is not logged. If I hit ENTER before logging then everything is logged.

W4JSI, Joe

-----------------------------------------

From: "Bob"
To: hamlogger@groups.io
Cc:
Sent: Monday January 20 2020 3:37:12PM
Subject: Re: [hamlogger] "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

... not quite ... First, on the UDP BandMap window, click CONFIG and check the ENABLE CALLSIGN LOOKUP WHEN CLICKING ON WJT/JTDX. Now, when you double click on a callsign on WSJT/JTDX Band Activity window, the Logbook Entry Window in Logger32 will be populated with the callsign. Then, automagically the Callsign lookup will complete and populate the Logbook Entry Window with additional information (if you're lucky). SeventyThree(s).

On January 20, 2020 at 4:30 PM Gary Wilson <k2gw@...> wrote:

I kind of have the same issue.  Please clarify this first step:

"When you type W5IDX in Logbook entry window, do you see auto lookup window ?

 

and Name, State etc are populated in Logbook entry window ?"

I do, but they only after I hit "return".  Is that what you mean? Or should they instantly fill in?

 


 


Re: 5 questions

John Munton - G7SSE
 

"5. What to do to have other ports that could be used with L32 and other applications, simultaneously?"

I think the OP in the above might be referring to port splitting / sharing (not sure of the correct term myself) for which he may need to look at the following;

http://com0com.sourceforge.net/

http://www.eterlogic.com/Products.VSPE.html

73, John - G7SSE


Re: 5 questions

Gary Hinson
 

1. Why  L32 not able to always display the DX spots, despite being connected to VE6DXC? CAT works fine. Making a right-click over the VE6DXC at the bottom, shows that it is connected.

 

DX cluster spots can be filtered by Logger32.  Do you have any cluster filters in use, Radhames?  Right-click the DX Spots window then check under Setup à DX Spot Blocking/Pass Filters …

 

 

 

2. Is it possible to have other sources available for DX spots, other than VE6DXC?

 

Yes … but I think not directly in Logger32: I believe Logger32 can only connect to one DX cluster at a time (if that’s what you mean).  One solution is to install and run VE7CC’s Cluster User program on your computer: it can connect to several DX clusters in parallel, combining all the spots and passing them on to other programs (such as Logger32) through the local network.  Logger32 on my PC connects to a DXcluster called “Local”, which is where Cluster User sends the spots:

 

 

 

3. For what reason  I only have comm port 3 available?

 

Errr, sorry, I do not understand your question.  Do you expect Logger32 to give you extra comm ports? 

 

 

4. Why does the SUMMARYQSObyMode utility only show a few years through 1992 to 2009 (9,367 contacts) when I have many thousands QSOs logged from 1978? (16,704)

 

[Aki is helping you with this]

 

 

5. What to do to have other ports that could be used with L32 and other applications, simultaneously?

 

Sorry, I do not understand this question either.  Maybe someone else can help, or you might explain what you mean.    

 

73s & GL Radhames

Gary  ZL2iFB

 


Re: 5 questions

ja1nlx
 

Radhames


Regarding Question 4

If you are using ver1.08 and see problem, then send your logbook adi

in ZIP format directly to me.


73


On 2020/01/21 7:20, HI3B Radhames wrote:
Hi all L32 users:

An inexperienced ask these silly questions:

1. Why  L32 not able to always display the DX spots, despite being connected to VE6DXC? CAT works fine. Making a right-click over the VE6DXC at the bottom, shows that it is connected.

2. Is it possible to have other sources available for DX spots, other than VE6DXC?

3 For what reason  I only have comm port 3 available?

4. Why does the SUMMARYQSObyMode utility only show a few years through 1992 to 2009 (9,367 contacts) when I have many thousands QSOs logged from 1978? (16,704)

5. What to do to have other ports that could be used with L32 and other applications, simultaneously?

Sorry, but I haven't found the exact information in the Help manual in Spanish

Thanks in advance.

73,

Radhames, HI3B



--
HI3B
--
73 de aki
JA1NLX


5 questions

HI3B Radhames
 

Hi all L32 users:

An inexperienced ask these silly questions:

1. Why  L32 not able to always display the DX spots, despite being connected to VE6DXC? CAT works fine. Making a right-click over the VE6DXC at the bottom, shows that it is connected.

2. Is it possible to have other sources available for DX spots, other than VE6DXC?

3 For what reason  I only have comm port 3 available?

4. Why does the SUMMARYQSObyMode utility only show a few years through 1992 to 2009 (9,367 contacts) when I have many thousands QSOs logged from 1978? (16,704)

5. What to do to have other ports that could be used with L32 and other applications, simultaneously?

Sorry, but I haven't found the exact information in the Help manual in Spanish

Thanks in advance.

73,

Radhames, HI3B



--
HI3B


Re: Logbook...where is it?

David Perry <bumbledp@...>
 

It WAS  hidden.  Find lost windows sorted it.  Thank you

D


Re: Logbook...where is it?

Bob
 

Along the top of the main Window there is a row of buttons. Put the mouse over the 5th button from the left. The Tooltip should say LOGBOOK PAGE WINDOW. Click it. If the window does not appear, then maybe it's hidden behind another window. Click VIEw | FIND LOST WINDOWS. Look down the list of open windows for LOGBOOKPAGE ... Check the entry and click FIND. SeventyThree(s).

On January 20, 2020 at 4:36 PM David Perry <bumbledp@...> wrote:

Hi guys.

Today I started using L32 for the first time but I cant seem to find my logbook page.   I've made qso and entered then alright but I cant find the logbook page now.

What menu item.is it to view the log please?

David G4YVM 

 


Re: "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

Bob
 

... not quite ... First, on the UDP BandMap window, click CONFIG and check the ENABLE CALLSIGN LOOKUP WHEN CLICKING ON WJT/JTDX. Now, when you double click on a callsign on WSJT/JTDX Band Activity window, the Logbook Entry Window in Logger32 will be populated with the callsign. Then, automagically the Callsign lookup will complete and populate the Logbook Entry Window with additional information (if you're lucky). SeventyThree(s).

On January 20, 2020 at 4:30 PM Gary Wilson <k2gw@...> wrote:

I kind of have the same issue.  Please clarify this first step:

"When you type W5IDX in Logbook entry window, do you see auto lookup window ?

 

and Name, State etc are populated in Logbook entry window ?"

I do, but they only after I hit "return".  Is that what you mean? Or should they instantly fill in?

 


 


Logbook...where is it?

David Perry <bumbledp@...>
 

Hi guys.

Today I started using L32 for the first time but I cant seem to find my logbook page.   I've made qso and entered then alright but I cant find the logbook page now.

What menu item.is it to view the log please?

David G4YVM 


Re: One page with all information for one contact

Bob
 

Svein, OK now I understand what you're looking for. Sorry, no plans to add that functionality/capability. Thans for the suggestion. SeventyThree(s).

On January 20, 2020 at 3:31 PM Svein Henriksen <la3pu@...> wrote:

Bob,

 

I do know and use all of those windows and also the Edit XXXX modes.

The logbook window is naturally in spread sheet form.

When clicking on a registered QSO, I would like all the data for fields to be displayed in a form type display for this one contact.

I have this in some databases of my own implemented in ACCESS.

Like when you use the Add QSO function, but with all the fields populated or not.

This would be nice when looking at, editing and or reviewing a specific QSO.

I still tend to get a lot of QSL cards and I like to enter all the information on there; like for example IOTA, DOK, the Japanese Guns etc.....

It is easier to do updates of multiple fields in a form type presentation.

Since there are so many field it is now necessary to scroll sideways forth and back.

I can of course rearrange the columns in the logbook window to have the one I use the most in view on the screen.

 

It was just a thought. Not really important to me, but thanks for considering my request. J

 

73 de LA3PU

Svein

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: 19. januar 2020 21:44
To: hamlogger@groups.io
Subject: Re: [hamlogger] One page with all information for one contact

 

I'm not sure exactly what you're asking for. See the picture ... Iclicked on the SM5AQD QSO in the Logbook Page Window. The Previous QSOs Window shows all QSOs with SM5AQD. The Callsign Lookup window opened with current SM5AQD information. If there was information I wanted/needed to add to the SM5AQD QSO, I can click the UPDATE QSO menu on the Callsign Lookup Window. SeventyThree(s).

 

On January 19, 2020 at 3:11 PM Svein Henriksen <la3pu@...> wrote:

Bob,

 

I wonder if you have considered or would consider introducing a function whereby clicking on one contact would bring up all information for this QSO in one window.

I personally think it is easier to edit and add information in this way instead of having one long line.

Of course there are the “Edit Notes” etc... but.....

No big deal, I was just wondering if this had been considered at all.

 

73 de LA3PU

Svein

 


 

 



 


Re: "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

Gary Wilson
 

I kind of have the same issue.  Please clarify this first step:

"When you type W5IDX in Logbook entry window, do you see auto lookup window ?

 

and Name, State etc are populated in Logbook entry window ?"

I do, but they only after I hit "return".  Is that what you mean? Or should they instantly fill in?

 


Re: One page with all information for one contact

Svein Henriksen
 

Bob,

 

I do know and use all of those windows and also the Edit XXXX modes.

The logbook window is naturally in spread sheet form.

When clicking on a registered QSO, I would like all the data for fields to be displayed in a form type display for this one contact.

I have this in some databases of my own implemented in ACCESS.

Like when you use the Add QSO function, but with all the fields populated or not.

This would be nice when looking at, editing and or reviewing a specific QSO.

I still tend to get a lot of QSL cards and I like to enter all the information on there; like for example IOTA, DOK, the Japanese Guns etc.....

It is easier to do updates of multiple fields in a form type presentation.

Since there are so many field it is now necessary to scroll sideways forth and back.

I can of course rearrange the columns in the logbook window to have the one I use the most in view on the screen.

 

It was just a thought. Not really important to me, but thanks for considering my request. J

 

73 de LA3PU

Svein

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: 19. januar 2020 21:44
To: hamlogger@groups.io
Subject: Re: [hamlogger] One page with all information for one contact

 

I'm not sure exactly what you're asking for. See the picture ... Iclicked on the SM5AQD QSO in the Logbook Page Window. The Previous QSOs Window shows all QSOs with SM5AQD. The Callsign Lookup window opened with current SM5AQD information. If there was information I wanted/needed to add to the SM5AQD QSO, I can click the UPDATE QSO menu on the Callsign Lookup Window. SeventyThree(s).

 

On January 19, 2020 at 3:11 PM Svein Henriksen <la3pu@...> wrote:

Bob,

 

I wonder if you have considered or would consider introducing a function whereby clicking on one contact would bring up all information for this QSO in one window.

I personally think it is easier to edit and add information in this way instead of having one long line.

Of course there are the “Edit Notes” etc... but.....

No big deal, I was just wondering if this had been considered at all.

 

73 de LA3PU

Svein

 


 


Re: HAM & SWL

Giuseppe Giunta
 

Ciao a tutti,

grazie Bob & Pete!

And many thanks to the whole group of developers for this piece of "jewel software"! :-)

Giu, IT9VDQ


Il 20/01/2020 00:31, n5kd ha scritto:
You can have multiple .ini files for different page layouts.

73’ Pete, N5KD.

Sent from my mobile

On Jan 19, 2020, at 13:21, Bob <k4cy@...> wrote:

The IT9VDQ logbook, and any other logbook you create using the Logger32.INI will have the structure your have configured in the Logger32.INI.  The same applies to your IT969339 logbook, it's structure will be from the SWL.INI. SeventyThree(s).
On January 19, 2020 at 1:57 PM Giuseppe Giunta <it9vdq@...> wrote:

Ciao everybody,

I decided to resume my SWL activity as IT9-60339, started in far 1974, and to add it to the poor OM activity that I'm actually able to do ... I obviously need a suitable software. To do this, after reading the help of Logger32, I created on the desktop a second .INI shortcut to Logger32.exe, naming it "C:\Logger32\Logger32.exe SWL". Opening Logger32 by this link, I created a new database, named "IT960339".

Actually the database is empty, because I have not imported my +/- 300 HRDs yet, from another software/paper. However, my Logger32 configured years ago with the IT9VDQ callsign, would need some modifications to make it suitable for a SWL, namely: one field for "Station listened" and another for "Report listened". My idea is to use "User_1" and "User_2" to add these two additional new fields, which are needed to register a valid HRD (say Call-HRD Call-in-Qso RST-1 RST-2). My (probably stupid) question is: if I play the double activity as IT9VDQ and IT960339 as SWL, jumping from one log to the another, will the different structural settings of the maps of each individual log be kept?

Trying to better explain: when I go from IT9VDQ (Date Call RSTs RSTr etc) to IT960339 (Date Call-HRD Call-in-Qso RST-1 RST-2 etc), will each of the two different structures be maintained?

Grazie, 73 de Giu, IT9VDQ



 


Re: HAM & SWL

n5kd
 

You can have multiple .ini files for different page layouts.

73’ Pete, N5KD.

Sent from my mobile

On Jan 19, 2020, at 13:21, Bob <k4cy@...> wrote:

The IT9VDQ logbook, and any other logbook you create using the Logger32.INI will have the structure your have configured in the Logger32.INI.  The same applies to your IT969339 logbook, it's structure will be from the SWL.INI. SeventyThree(s).
On January 19, 2020 at 1:57 PM Giuseppe Giunta <it9vdq@...> wrote:

Ciao everybody,

I decided to resume my SWL activity as IT9-60339, started in far 1974, and to add it to the poor OM activity that I'm actually able to do ... I obviously need a suitable software. To do this, after reading the help of Logger32, I created on the desktop a second .INI shortcut to Logger32.exe, naming it "C:\Logger32\Logger32.exe SWL". Opening Logger32 by this link, I created a new database, named "IT960339".

Actually the database is empty, because I have not imported my +/- 300 HRDs yet, from another software/paper. However, my Logger32 configured years ago with the IT9VDQ callsign, would need some modifications to make it suitable for a SWL, namely: one field for "Station listened" and another for "Report listened". My idea is to use "User_1" and "User_2" to add these two additional new fields, which are needed to register a valid HRD (say Call-HRD Call-in-Qso RST-1 RST-2). My (probably stupid) question is: if I play the double activity as IT9VDQ and IT960339 as SWL, jumping from one log to the another, will the different structural settings of the maps of each individual log be kept?

Trying to better explain: when I go from IT9VDQ (Date Call RSTs RSTr etc) to IT960339 (Date Call-HRD Call-in-Qso RST-1 RST-2 etc), will each of the two different structures be maintained?

Grazie, 73 de Giu, IT9VDQ



 


Re: Best way to change eQSL received

keith hotchkiss
 

Cancel last I have uploaded a backup which has sorted the issue.