Date   

ODP: [hamlogger] Four instances of LogSync

Andy VA3PL
 

Thanks a lot Rick for an answer.
He will run one instance of LogSince at the time and I am helping him to set it up.

Andy SP9KR


Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Rick Ellison <rellison@...>
Wysłane: poniedziałek, 29 marca 2021 17:55
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] Four instances of LogSync
 

I do not see why he could not run the different instances of LogSync in separate directories. I am not sure if there would be any interactions if he tried running all 4 at the same time tho..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Andy VA3PL
Sent: Monday, March 29, 2021 11:43 AM
To: hamlogger@groups.io
Subject: [hamlogger] Four instances of LogSync

 

Hi

Friend of mine manages four callsigns. Two of his and two for his wife.

Because of difficulty managing LOTW for each calsign using LogSince he would like to have four separate instances of LogSinc? One for each callsign.

EG: He has four instances of Logger32 and he would like to have separate instances of LogSync in each Folder for Logger32.

Can it be done this way?

 

Andy SP9KR

Retirement is the best job I've ever had


Virus-free. www.avast.com


Re: Four instances of LogSync

Rick Ellison
 

I do not see why he could not run the different instances of LogSync in separate directories. I am not sure if there would be any interactions if he tried running all 4 at the same time tho..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Andy VA3PL
Sent: Monday, March 29, 2021 11:43 AM
To: hamlogger@groups.io
Subject: [hamlogger] Four instances of LogSync

 

Hi

Friend of mine manages four callsigns. Two of his and two for his wife.

Because of difficulty managing LOTW for each calsign using LogSince he would like to have four separate instances of LogSinc? One for each callsign.

EG: He has four instances of Logger32 and he would like to have separate instances of LogSync in each Folder for Logger32.

Can it be done this way?

 

Andy SP9KR

Retirement is the best job I've ever had


Virus-free. www.avast.com


Four instances of LogSync

Andy VA3PL
 

Hi
Friend of mine manages four callsigns. Two of his and two for his wife.
Because of difficulty managing LOTW for each calsign using LogSince he would like to have four separate instances of LogSinc? One for each callsign.
EG: He has four instances of Logger32 and he would like to have separate instances of LogSync in each Folder for Logger32.
Can it be done this way?

Andy SP9KR
Retirement is the best job I've ever had


Re: Lookup_QRZRU_XML ver1.01

Valery Prodanov
 

thanks Aki

73


Re: Lookup_QRZRU_XML ver1.01

ja1nlx
 

Valery

QRX for next version....

73 de aki
JA1NLX

------ Original message ------
From: "Valery Prodanov" <ur5wca@...>
Date: 2021/03/29 21:38:59
Subject [hamlogger] Lookup_QRZRU_XML ver1.01

Hello everybody.  I have a question for Aki JA1NLX.

I use the Lookup_Qrzru_XML VER1.01 utility


изображение.png

But <State> and <County> are displayed in one window.

L32 writes that this error has to be corrected by hand.

Can I do separately <State> and <county>?


--
Best regards!
Valery P. Prodanov
UR5WCA
73!


Lookup_QRZRU_XML ver1.01

Valery Prodanov
 

Hello everybody.  I have a question for Aki JA1NLX.

I use the Lookup_Qrzru_XML VER1.01 utility


изображение.png

But <State> and <County> are displayed in one window.

L32 writes that this error has to be corrected by hand.

Can I do separately <State> and <county>?


--
Best regards!
Valery P. Prodanov
UR5WCA
73!


Re: Bug in V4 ?

Dave Colliau
 

Mine is fine
Dave n8dc

On 03/29/2021 8:32 AM Bernd DL9YAJ <dl9yaj@darc.de> wrote:


Hi all,

when i click on "Manually ADD QSOs" the program will close instantly.

The short-Cut "Ctrl-M" does the same?

A known bug? Using V 4.0.248 under Win10 Pro 64 Bit

73s Bernd, DL9YAJ




Bug in V4 ?

Bernd DL9YAJ
 

Hi all,

when i click on "Manually ADD QSOs" the program will close instantly.

The short-Cut "Ctrl-M" does the same?

A known bug? Using V 4.0.248 under Win10 Pro 64 Bit

73s Bernd, DL9YAJ


Re: select a few items to export

UPU VRTWO
 

Hi,

Many thanks ,

ADIF Master is good software, fast to delete the item and export, make the adi file very small.

73 SZE-TO wing


Re: select a few items to export

Fabio IZ8MBW
 

Hi.
When you export ADIF with Logger32 you can specify "Partial Log" and select a date range or QSO number range.
More you can specify the ADIF fields in "Setup custom ADIF fileds".

Or you can export ADIF and after edit the ADIF file with "ADIF Master" software: https://www.dxshell.com/software.html


73s
Fabio, IZ8MBW



On Monday, March 29, 2021, 04:43:02 AM GMT+2, UPU VRTWO <vr2upu@...> wrote:


Hello,

   Use Logger32 to export a adi file include 20 items detailed, how to select only few items for export my adi file, it does not need very detailed, this adi file is used for WSJTX JTDX.

WSJTX JTDX's adi file required items : <call> <gridsquare> <mode> <rst_sent> <rst_rcvd>
<qso_date> <time_on> <time_off> <band> <freq>

73 de SZE-TO Wing VR2UPU


Re: Import non ADIF-Log to new V4, help needed

Peter Cleall
 

Decided to do a v4 new install. Backed up old files on memory stick. Then purged system of v3.

downloaded v4 and it appears to have all normal functionality. Added backed up adi file. All good.  It all works well. Closed logger.

next time I open it. It starts to open , it flash’s part of the screen and starts to show blank log book and within seconds completely closes down. 

Any my ideas as to what I have done wrong?

peter g8afn 


select a few items to export

UPU VRTWO
 

Hello,

   Use Logger32 to export a adi file include 20 items detailed, how to select only few items for export my adi file, it does not need very detailed, this adi file is used for WSJTX JTDX.

WSJTX JTDX's adi file required items : <call> <gridsquare> <mode> <rst_sent> <rst_rcvd>
<qso_date> <time_on> <time_off> <band> <freq>

73 de SZE-TO Wing VR2UPU


Re: telnet spots only works for 25 lines

Fred-K0FG
 

There is grey background all around the dx spots page so no the bottom of the dx spots screen is not hidden.

Just updated from V3 to V4 and it works the same way as V3 worked.

Thanks for your help.

Fred, K0FG


Re: telnet spots only works for 25 lines

Jan
 

Fred

Are you sure that the window is not behind the lower tast bar(s)?

73
Jan
PA4JJ

Op 28-3-2021 om 20:12 schreef Fred-K0FG:
Hi Bob.
My DX spots window is in the lower right corner of my screen and it only shows the upper 25 spots, out of 31 being displayed.  The last 6 spots show no info about the spots, no popup with direction, name, needs, etc, no info popup window.  If I unlock child windows and drag the DX spots screen upward a couple inches then the entire displayed spots work properly.  When I drag the DX spots back to the lower right corner then the last 6 spots do not display info again.

I only need to drag the DX spots window up maybe 1/2 inch and some of those lower spots begin to act properly.  And the farther up I drag the screen the more spots work correctly until I move the window up perhaps 1 inch and then all of the spots work correctly.

Maybe a Windows 10 thing?  Running the latest version.   But the spots show up they just don't display info. 

I can live with it, just info for you in case others have the same problem.

Thanks for the wonderful Logger32, I use it all day, every day.

Fred, K0FG

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Re: telnet spots only works for 25 lines

Fred-K0FG
 

Hi Bob.
My DX spots window is in the lower right corner of my screen and it only shows the upper 25 spots, out of 31 being displayed.  The last 6 spots show no info about the spots, no popup with direction, name, needs, etc, no info popup window.  If I unlock child windows and drag the DX spots screen upward a couple inches then the entire displayed spots work properly.  When I drag the DX spots back to the lower right corner then the last 6 spots do not display info again.

I only need to drag the DX spots window up maybe 1/2 inch and some of those lower spots begin to act properly.  And the farther up I drag the screen the more spots work correctly until I move the window up perhaps 1 inch and then all of the spots work correctly.

Maybe a Windows 10 thing?  Running the latest version.   But the spots show up they just don't display info. 

I can live with it, just info for you in case others have the same problem.

Thanks for the wonderful Logger32, I use it all day, every day.

Fred, K0FG


Re: Import non ADIF-Log to new V4, help needed

Gary Hinson
 

Well done Bernd: 'v4 working and no QSOs missing' is what we like to hear!

73
Gary ZL2iFB

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bernd DL9YAJ
Sent: 29 March 2021 02:37
To: hamlogger@groups.io
Subject: Re: [hamlogger] Import non ADIF-Log to new V4, help needed

Hi Gary,

thank you for answer. Read in the manual to register manually the x.ocx file, but no way! Several other files ask also for registration. As solution, i installed the V 3.5 on my PC and copied the zipped lookbook files from my backup into the c:\logger folder. After that "new"
installation all works well and i am able to export the log into ADIF.
After that i deinstalled the V3.5 and installed again the new V4.x and import the ADIF file. All works well at the moment and no qso is missing. The rest now is cosmetics!

Thank you very much for help.

Best 73s Bernd, DL9YAJ


Am 27.03.2021 um 05:05 schrieb Gary Hinson:
Hi Bernd.

That message means the v4 installation did not correctly register the file. You can register it manually: there is an FAQ about a soundcard issue involving manually registering a file that was not properly registered, in the User Manual section 2.10 (which I may need to update). https://www.logger32.net/files/Logger32_v4_User_Manual.pdf

73
Gary ZL2iFB

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bernd
DL9YAJ
Sent: 26 March 2021 01:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] Import non ADIF-Log to new V4, help needed

Hi Gary,

yesterday i have time work for my problem.

I started my old V3.50.397 but not from the installed drive c:\logger32 , because i have installed the new V4 on the c: \logger32 path.
So i start the logger32.exe from my backup d: drive. All is working ok but when i want to export log to ADIF i get a error message, see the attachment.

Any idea?
or is the only way to install the old version to the normal install
path
c:\logger32

73s Bernd, DL9YAJ

Am 22.03.2021 um 00:36 schrieb Gary Hinson:
Hi Bernd.

First, be very careful with that USB stick! I recommend COPYING the files onto your new hard drive, then removing the USB stick to a safe place. Work with the on-disk copies, so if something goes very wrong, at least you haven't lost the log on USB.

The v3 to v4 migration process makes a one-time change to the v3 database structure, bringing it up to v4, and then updates are applied (ideally automatically). So, I think you should be able to restore the v3 files, then run the v4 migration.

If that doesn't work out, then yes you may need to restore a working v3 installation first, export your log as an ADIF, then install a fresh v4 installation and import the ADIF log.

Personally, I would take the latter option anyway, generating an ADIF file from a v3 installation AND saving a safety copy of that ADIF.

ADIF log backups give us more options for recovering our logs if, for some reason, either the ADIF file or Logge32 has problems. Being plain text, for one thing, ADIF files can be edited manually in a simple editor such as Notepad. ADIF-compliant programs such as ADIF Master and TQSL provide various integrity checks and functions. The size of the ADIF directly relates to the size of the log, so if the ADIF generation is truncated prematurely for some reason, it will output a smaller file than the previous ADIF output - a big clue that something went wrong!

73 GL
Gary ZL2iFB


-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bernd
DL9YAJ
Sent: 22 March 2021 04:13
To: hamlogger@groups.io
Subject: [hamlogger] Import non ADIF-Log to new V4, help needed

Hi,

after a SSD crash i want to start with a new V4 full install.

The last version on my old defect HD was 3.50.391 ! I found an Fullbackup on a USB-Stick made at that version. The backup has many files amongst them several LogbookBackup_FULL_001.ZIP up to LogbookBackup_FULL_006.ZIP. Unfortunately i have NO ADIF from my log!

Now i read in the new V4 help file how to migrate old logs to the new V4, but only in ADIF!

Is it neccesary to install first the old 3.5.391 version to export the log to ADIF or is there a way to import the log from my old backup?

Best 73s

Bernd, DL9YAJ




















Re: Import non ADIF-Log to new V4, help needed

Bernd DL9YAJ
 

Hi Gary,

thank you for answer. Read in the manual to register manually the x.ocx file, but no way! Several other files ask also for registration. As solution, i installed the V 3.5 on my PC and copied the zipped lookbook files from my backup into the c:\logger folder. After that "new" installation all works well and i am able to export the log into ADIF. After that i deinstalled the V3.5 and installed again the new V4.x and import the ADIF file. All works well at the moment and no qso is missing. The rest now is cosmetics!

Thank you very much for help.

Best 73s Bernd, DL9YAJ


Am 27.03.2021 um 05:05 schrieb Gary Hinson:

Hi Bernd.

That message means the v4 installation did not correctly register the file. You can register it manually: there is an FAQ about a soundcard issue involving manually registering a file that was not properly registered, in the User Manual section 2.10 (which I may need to update). https://www.logger32.net/files/Logger32_v4_User_Manual.pdf

73
Gary ZL2iFB

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bernd DL9YAJ
Sent: 26 March 2021 01:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] Import non ADIF-Log to new V4, help needed

Hi Gary,

yesterday i have time work for my problem.

I started my old V3.50.397 but not from the installed drive c:\logger32 , because i have installed the new V4 on the c: \logger32 path.
So i start the logger32.exe from my backup d: drive. All is working ok but when i want to export log to ADIF i get a error message, see the attachment.

Any idea?
or is the only way to install the old version to the normal install path
c:\logger32

73s Bernd, DL9YAJ

Am 22.03.2021 um 00:36 schrieb Gary Hinson:
Hi Bernd.

First, be very careful with that USB stick! I recommend COPYING the files onto your new hard drive, then removing the USB stick to a safe place. Work with the on-disk copies, so if something goes very wrong, at least you haven't lost the log on USB.

The v3 to v4 migration process makes a one-time change to the v3 database structure, bringing it up to v4, and then updates are applied (ideally automatically). So, I think you should be able to restore the v3 files, then run the v4 migration.

If that doesn't work out, then yes you may need to restore a working v3 installation first, export your log as an ADIF, then install a fresh v4 installation and import the ADIF log.

Personally, I would take the latter option anyway, generating an ADIF file from a v3 installation AND saving a safety copy of that ADIF.

ADIF log backups give us more options for recovering our logs if, for some reason, either the ADIF file or Logge32 has problems. Being plain text, for one thing, ADIF files can be edited manually in a simple editor such as Notepad. ADIF-compliant programs such as ADIF Master and TQSL provide various integrity checks and functions. The size of the ADIF directly relates to the size of the log, so if the ADIF generation is truncated prematurely for some reason, it will output a smaller file than the previous ADIF output - a big clue that something went wrong!

73 GL
Gary ZL2iFB


-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bernd
DL9YAJ
Sent: 22 March 2021 04:13
To: hamlogger@groups.io
Subject: [hamlogger] Import non ADIF-Log to new V4, help needed

Hi,

after a SSD crash i want to start with a new V4 full install.

The last version on my old defect HD was 3.50.391 ! I found an Fullbackup on a USB-Stick made at that version. The backup has many files amongst them several LogbookBackup_FULL_001.ZIP up to LogbookBackup_FULL_006.ZIP. Unfortunately i have NO ADIF from my log!

Now i read in the new V4 help file how to migrate old logs to the new V4, but only in ADIF!

Is it neccesary to install first the old 3.5.391 version to export the log to ADIF or is there a way to import the log from my old backup?

Best 73s

Bernd, DL9YAJ



















V4 and WPX

Hubert CRETOIS
 

Hello,
Since I installed the V4 on my computer with windows 7, I noticed that some cluster spots informed me, by a color code, that I did not have various WPX although I had already contacted it as
can indicate the cross and after having recalculated the statistics several times, the problem is the same ... (see photo). Who would have the solution to my problem?
Tnx for your help.

73 de F4FIP


Re: Ic 7300 - unable to connect

Julian GW4JBQ
 

Glad your up and running Kev.


Re: Ic 7300 - unable to connect

Kev Haworth
 

Firstly . Thank you to each and every one of you who has replied either through the group or in private.

Your input was very welcome.

I can now connect! I had recently completed a Windows update and after that had installed, all went well.

Now to get my head round working a log again..

Thanks 

Kev

1321 - 1340 of 84646