|
Group (I've also posted this on the FT8 site)
I have been using WSJT-X with both N1MM and Logger32 for some time now with no problems.
This past weekend I dismantled my setup and used it at a club setting, through a dummy load to demonstrate Digital Contesting using: N1MM, MMVARI and WSJT-X.
Today I put the station back to regular use in my radio room.
Problem when trying to use it with Logger32 is showing up. Note: working just fine with N1MM.
Hamlib error: Command rejected by the rig while setting frequency.
I keep getting the above error message whenever I either use the Tune or TX buttons. When the TX stops, the above error message shows up.
To the best of my knowledge the only thing that changed was when I opened Logger32 today it updated to the latest version. I thought maybe this was causing the problem so I went in and did a roll back to the previous version, and the message still pots up.
I have gone through all the setting in Logger32 and they are good. I also went through all the setting in WSJT-X and all were set as to the way there were before, no changes.
From what I can see while using WSJT-X to control the radio, it changes bands and modes with not problem and the radio responds to the changes.
When I TX it sends the message, no problem. Only when TX stops does this message appear.
Any suggestions as to why this message keeps popping up?
Bob/VE1RSM
|
|
|
Re: Name Field Automatically Filled in?
Hi Aki
Thank you very much for your help. Just what I was looking for. It's always amazing what Bob has built into Logger32.
73, Peter - HB9PJT
|
|
|
Re: Name Field Automatically Filled in?
Peter
Right click on Logbook Entry Window.
Click Setup.
Click Setup QSO Mask
Check Name box upper and/or lower then click Apply.
73
toggle quoted messageShow quoted text
On 2020/03/03 18:03, Peter Sidler -
HB9PJT via Groups.Io wrote:
Is there a way to configure Logger32 to automatically fill the
name field in the new QSO with the name of the last QSO from the
same callsign? Thanks for helping.
73, Peter - HB9PJT
|
|
|
Name Field Automatically Filled in?
Is there a way to configure Logger32 to automatically fill the name field in the new QSO with the name of the last QSO from the same callsign? Thanks for helping.
73, Peter - HB9PJT
|
|
|
Re: FT8 spots in DX Spot Window
Good morning how to disable the command: SET/SKIMMER after to enable the cluster ?
73 sv9rgi Giannis
|
|
|
Re: Can't edit contacts in the logbook
That's interesting Aki!!
I'll keep an eye on it when another update comes along to see if
that changes anything.
73
Ken ZL4NR
toggle quoted messageShow quoted text
On 2/03/2020 4:01 pm, ja1nlx wrote:
Ken
I am glad to hear that.
I made testing with "Auto golist lookup" checked and do not
see your problem....
Maybe something different between our settings.
73
On 2020/03/02 10:31, Ken McVie wrote:
Aki, I think I found the problem!!
As you probably saw, Jim Altman sent me a link for a program to
compare two files, so I downloaded this & entered the two
files. It found a few differences in the whole INI file, mostly
to do with window positions. But one difference was that the OLD
INI file had the Golist auto lookup checked, & the earlier
version didn't.
I then opened L32, & checked the auto lookup for Golist,
& the program went back to not being able to edit anything
in the logbook page. I then unchecked the auto lookup of Golist,
& I can edit anything in the logbook page again!! So there
is a tie up between the Golist lookup being on or off that is
causing this problem.
Once again, many thanks to Aki, & Jim for the help.
73
Ken ZL4NR
On 2/03/2020 11:49 am, ja1nlx
wrote:
Ken
As you say it may be better for you to copy/paste older
Logger32.ini on current one.
73
On 2020/03/02 7:24, Ken McVie
wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!
I have 63 lines in that section of the INI file, do you mean
to delete them all?? If I do this, will it mean I have to
reset all those parameters?? I could print out a copy I
guess, which would make it easier to "remake" the list bit
by bit, testing as I go to see where the problem lies.
In the 'UPDATE' files of L32, I have a INI file dated early
February, could I exchange this for my current one & see
what happens??
I tried changing the Page Index & the Page Index Column
numbers to what you sent me, & that didn't make any
difference.
73
Ken ZL4NR
On 28/02/2020 10:09 pm, ja1nlx
wrote:
Ken
Delete Logger32.ini.
Rename Logger32.ini.OLD to Logger32.ini again.
Open Logger32.ini with text editor.
Maybe something wrong in [wndLogbookPage Settings]
section.
Delete all lines in this section. Run Logger32. How now
?
[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3
73
On 2020/02/28 17:59, Ken
McVie wrote:
That works ok. Now how do I find the difference in the
two INI files??
73
Ken
On 28/02/2020 9:53 pm,
ja1nlx wrote:
Ken
Try with virgin Logger32.ini.
Look for Logger32.ini in the Logger32 folder.
Rename it Logger32.ini.OLD.
Run Logger32. Try edit in Logbook page window. How
now ?
73
On 2020/02/28 17:44, Ken
McVie wrote:
I should add that I have done this lots in the past
without trouble.
73
Ken ZL4NR
On 28/02/2020 9:38 pm,
ja1nlx wrote:
Ken
What you see when you click any line. I see the
line highlighted with Yellow back color.
This color depends on your setting.
73
On 2020/02/28 16:18,
Ken McVie wrote:
Using
version 3.50.408 on W10 Home desktop computer.
I used to be able to click on a [for instance]
name in the logbook alongside a callsign, &
change it for something else. Now I can't change
anything on a QSO line by clicking on it.
I have a QSO with Rarotonga which shows the IOTA
number as OC-124 -- it should be OC- 013
according to the QSL card that I have received,
& I can't find a way of changing this.
Is anybody else seeing this behaviour of not
being able to edit a line in the logbook??
Any thoughts much appreciated.
73
Ken ZL4NR
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
|
|
|
Re: Can't edit contacts in the logbook
Ken
I am glad to hear that.
I made testing with "Auto golist lookup" checked and do not see
your problem....
Maybe something different between our settings.
73
toggle quoted messageShow quoted text
On 2020/03/02 10:31, Ken McVie wrote:
Aki, I think I found the problem!!
As you probably saw, Jim Altman sent me a link for a program to
compare two files, so I downloaded this & entered the two
files. It found a few differences in the whole INI file, mostly to
do with window positions. But one difference was that the OLD INI
file had the Golist auto lookup checked, & the earlier version
didn't.
I then opened L32, & checked the auto lookup for Golist, &
the program went back to not being able to edit anything in the
logbook page. I then unchecked the auto lookup of Golist, & I
can edit anything in the logbook page again!! So there is a tie up
between the Golist lookup being on or off that is causing this
problem.
Once again, many thanks to Aki, & Jim for the help.
73
Ken ZL4NR
On 2/03/2020 11:49 am, ja1nlx wrote:
Ken
As you say it may be better for you to copy/paste older
Logger32.ini on current one.
73
On 2020/03/02 7:24, Ken McVie
wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!
I have 63 lines in that section of the INI file, do you mean
to delete them all?? If I do this, will it mean I have to
reset all those parameters?? I could print out a copy I
guess, which would make it easier to "remake" the list bit by
bit, testing as I go to see where the problem lies.
In the 'UPDATE' files of L32, I have a INI file dated early
February, could I exchange this for my current one & see
what happens??
I tried changing the Page Index & the Page Index Column
numbers to what you sent me, & that didn't make any
difference.
73
Ken ZL4NR
On 28/02/2020 10:09 pm, ja1nlx
wrote:
Ken
Delete Logger32.ini.
Rename Logger32.ini.OLD to Logger32.ini again.
Open Logger32.ini with text editor.
Maybe something wrong in [wndLogbookPage Settings]
section.
Delete all lines in this section. Run Logger32. How now ?
[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3
73
On 2020/02/28 17:59, Ken McVie
wrote:
That works ok. Now how do I find the difference in the two
INI files??
73
Ken
On 28/02/2020 9:53 pm, ja1nlx
wrote:
Ken
Try with virgin Logger32.ini.
Look for Logger32.ini in the Logger32 folder. Rename
it Logger32.ini.OLD.
Run Logger32. Try edit in Logbook page window. How
now ?
73
On 2020/02/28 17:44, Ken
McVie wrote:
I should add that I have done this lots in the past
without trouble.
73
Ken ZL4NR
On 28/02/2020 9:38 pm,
ja1nlx wrote:
Ken
What you see when you click any line. I see the
line highlighted with Yellow back color.
This color depends on your setting.
73
On 2020/02/28 16:18,
Ken McVie wrote:
Using
version 3.50.408 on W10 Home desktop computer.
I used to be able to click on a [for instance]
name in the logbook alongside a callsign, &
change it for something else. Now I can't change
anything on a QSO line by clicking on it.
I have a QSO with Rarotonga which shows the IOTA
number as OC-124 -- it should be OC- 013 according
to the QSL card that I have received, & I
can't find a way of changing this.
Is anybody else seeing this behaviour of not being
able to edit a line in the logbook??
Any thoughts much appreciated.
73
Ken ZL4NR
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
|
|
|
Re: Can't edit contacts in the logbook
Aki, I think I found the problem!!
As you probably saw, Jim Altman sent me a link for a program to
compare two files, so I downloaded this & entered the two files.
It found a few differences in the whole INI file, mostly to do with
window positions. But one difference was that the OLD INI file had
the Golist auto lookup checked, & the earlier version didn't.
I then opened L32, & checked the auto lookup for Golist, &
the program went back to not being able to edit anything in the
logbook page. I then unchecked the auto lookup of Golist, & I
can edit anything in the logbook page again!! So there is a tie up
between the Golist lookup being on or off that is causing this
problem.
Once again, many thanks to Aki, & Jim for the help.
73
Ken ZL4NR
toggle quoted messageShow quoted text
On 2/03/2020 11:49 am, ja1nlx wrote:
Ken
As you say it may be better for you to copy/paste older
Logger32.ini on current one.
73
On 2020/03/02 7:24, Ken McVie wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!
I have 63 lines in that section of the INI file, do you mean to
delete them all?? If I do this, will it mean I have to reset
all those parameters?? I could print out a copy I guess, which
would make it easier to "remake" the list bit by bit, testing as
I go to see where the problem lies.
In the 'UPDATE' files of L32, I have a INI file dated early
February, could I exchange this for my current one & see
what happens??
I tried changing the Page Index & the Page Index Column
numbers to what you sent me, & that didn't make any
difference.
73
Ken ZL4NR
On 28/02/2020 10:09 pm, ja1nlx
wrote:
Ken
Delete Logger32.ini.
Rename Logger32.ini.OLD to Logger32.ini again.
Open Logger32.ini with text editor.
Maybe something wrong in [wndLogbookPage Settings] section.
Delete all lines in this section. Run Logger32. How now ?
[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3
73
On 2020/02/28 17:59, Ken McVie
wrote:
That works ok. Now how do I find the difference in the two
INI files??
73
Ken
On 28/02/2020 9:53 pm, ja1nlx
wrote:
Ken
Try with virgin Logger32.ini.
Look for Logger32.ini in the Logger32 folder. Rename it
Logger32.ini.OLD.
Run Logger32. Try edit in Logbook page window. How now
?
73
On 2020/02/28 17:44, Ken
McVie wrote:
I should add that I have done this lots in the past
without trouble.
73
Ken ZL4NR
On 28/02/2020 9:38 pm,
ja1nlx wrote:
Ken
What you see when you click any line. I see the
line highlighted with Yellow back color.
This color depends on your setting.
73
On 2020/02/28 16:18, Ken
McVie wrote:
Using
version 3.50.408 on W10 Home desktop computer.
I used to be able to click on a [for instance] name
in the logbook alongside a callsign, & change it
for something else. Now I can't change anything on a
QSO line by clicking on it.
I have a QSO with Rarotonga which shows the IOTA
number as OC-124 -- it should be OC- 013 according
to the QSL card that I have received, & I can't
find a way of changing this.
Is anybody else seeing this behaviour of not being
able to edit a line in the logbook??
Any thoughts much appreciated.
73
Ken ZL4NR
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
|
|
|
Re: Can't edit contacts in the logbook
Thanks Jim, I'll give that a try.
73
Ken ZL4NR
toggle quoted messageShow quoted text
On 2/03/2020 1:47 pm, Jim Altman wrote:
Google WinMerge. Its free and will compare
two files line by line allowing movement from one file to the
other.
JA1NLX
I renamed my L32 INI file to OLD, & then copied &
pasted the earlier edition into the L32 folder. Opened L32,
& all seems to be working again!!
So I then opened both INI files in Notepad, & went thru
each line [63 of them] to compare [visually] & I can't see
any difference!! Is there a program for comparing files that
might show where the fault lies??
Many thanks for the help Aki, appreciated.
73
Ken ZL4NR
On 2/03/2020 11:49 am, ja1nlx wrote:
Ken
As you say it may be better for you to copy/paste older
Logger32.ini on current one.
73
On 2020/03/02 7:24, Ken McVie wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!
I have 63 lines in that section of the INI file, do you
mean to delete them all?? If I do this, will it mean I
have to reset all those parameters?? I could print out a
copy I guess, which would make it easier to "remake" the
list bit by bit, testing as I go to see where the problem
lies.
In the 'UPDATE' files of L32, I have a INI file dated
early February, could I exchange this for my current one
& see what happens??
I tried changing the Page Index & the Page Index
Column numbers to what you sent me, & that didn't make
any difference.
73
Ken ZL4NR
On 28/02/2020 10:09 pm, ja1nlx wrote:
Ken
Delete Logger32.ini.
Rename Logger32.ini.OLD to Logger32.ini again.
Open Logger32.ini with text editor.
Maybe something wrong in [wndLogbookPage Settings]
section.
Delete all lines in this section. Run Logger32. How now
?
[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3
73
On 2020/02/28 17:59, Ken McVie
wrote:
That
works ok. Now how do I find the difference in the two
INI files??
73
Ken
On 28/02/2020 9:53 pm, ja1nlx
wrote:
Ken
Try with virgin Logger32.ini.
Look for Logger32.ini in the Logger32 folder.
Rename it Logger32.ini.OLD.
Run Logger32. Try edit in Logbook page window. How
now ?
73
On 2020/02/28 17:44, Ken McVie
wrote:
I
should add that I have done this lots in the past
without trouble.
73
Ken ZL4NR
On 28/02/2020 9:38 pm, ja1nlx
wrote:
Ken
What you see when you click any line. I see the
line highlighted with Yellow back color.
This color depends on your setting.
73
On 2020/02/28 16:18, Ken
McVie wrote:
Using version
3.50.408 on W10 Home desktop computer.
I used to be able to click on a [for instance]
name in the logbook alongside a callsign,
& change it for something else. Now I
can't change anything on a QSO line by
clicking on it.
I have a QSO with Rarotonga which shows the
IOTA number as OC-124 -- it should be OC- 013
according to the QSL card that I have
received, & I can't find a way of changing
this.
Is anybody else seeing this behaviour of not
being able to edit a line in the logbook??
Any thoughts much appreciated.
73
Ken ZL4NR
|
|
|
Re: Can't edit contacts in the logbook
Google WinMerge. Its free and will compare two files line by line allowing movement from one file to the other.
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ken McVie Sent: Sunday, March 1, 2020 7:45 PM To: hamlogger@groups.io Subject: Re: [hamlogger] Can't edit contacts in the logbook JA1NLX
I renamed my L32 INI file to OLD, & then copied & pasted the earlier edition into the L32 folder. Opened L32, & all seems to be working again!!
So I then opened both INI files in Notepad, & went thru each line [63 of them] to compare [visually] & I can't see any difference!! Is there a program for comparing files that might show where the fault lies??
Many thanks for the help Aki, appreciated.
73
Ken ZL4NR On 2/03/2020 11:49 am, ja1nlx wrote: Ken As you say it may be better for you to copy/paste older Logger32.ini on current one. 73 On 2020/03/02 7:24, Ken McVie wrote: JA1NLX,
Sorry for the delay in replying, life got in the way!!!!
I have 63 lines in that section of the INI file, do you mean to delete them all?? If I do this, will it mean I have to reset all those parameters?? I could print out a copy I guess, which would make it easier to "remake" the list bit by bit, testing as I go to see where the problem lies.
In the 'UPDATE' files of L32, I have a INI file dated early February, could I exchange this for my current one & see what happens??
I tried changing the Page Index & the Page Index Column numbers to what you sent me, & that didn't make any difference.
73
Ken ZL4NR
On 28/02/2020 10:09 pm, ja1nlx wrote: Ken Delete Logger32.ini. Rename Logger32.ini.OLD to Logger32.ini again. Open Logger32.ini with text editor. Maybe something wrong in [wndLogbookPage Settings] section. Delete all lines in this section. Run Logger32. How now ? [wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3 73 On 2020/02/28 17:59, Ken McVie wrote: That works ok. Now how do I find the difference in the two INI files??
73
Ken On 28/02/2020 9:53 pm, ja1nlx wrote: Ken Try with virgin Logger32.ini. Look for Logger32.ini in the Logger32 folder. Rename it Logger32.ini.OLD. Run Logger32. Try edit in Logbook page window. How now ? 73 On 2020/02/28 17:44, Ken McVie wrote: I should add that I have done this lots in the past without trouble.
73
Ken ZL4NR On 28/02/2020 9:38 pm, ja1nlx wrote: Ken What you see when you click any line. I see the line highlighted with Yellow back color.
This color depends on your setting. 
73 On 2020/02/28 16:18, Ken McVie wrote: Using version 3.50.408 on W10 Home desktop computer.
I used to be able to click on a [for instance] name in the logbook alongside a callsign, & change it for something else. Now I can't change anything on a QSO line by clicking on it.
I have a QSO with Rarotonga which shows the IOTA number as OC-124 -- it should be OC- 013 according to the QSL card that I have received, & I can't find a way of changing this.
Is anybody else seeing this behaviour of not being able to edit a line in the logbook??
Any thoughts much appreciated.
73
Ken ZL4NR
|
|
|
Re: Can't edit contacts in the logbook
JA1NLX
I renamed my L32 INI file to OLD, & then copied & pasted the
earlier edition into the L32 folder. Opened L32, & all seems to
be working again!!
So I then opened both INI files in Notepad, & went thru each
line [63 of them] to compare [visually] & I can't see any
difference!! Is there a program for comparing files that might show
where the fault lies??
Many thanks for the help Aki, appreciated.
73
Ken ZL4NR
toggle quoted messageShow quoted text
On 2/03/2020 11:49 am, ja1nlx wrote:
Ken
As you say it may be better for you to copy/paste older
Logger32.ini on current one.
73
On 2020/03/02 7:24, Ken McVie wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!
I have 63 lines in that section of the INI file, do you mean to
delete them all?? If I do this, will it mean I have to reset
all those parameters?? I could print out a copy I guess, which
would make it easier to "remake" the list bit by bit, testing as
I go to see where the problem lies.
In the 'UPDATE' files of L32, I have a INI file dated early
February, could I exchange this for my current one & see
what happens??
I tried changing the Page Index & the Page Index Column
numbers to what you sent me, & that didn't make any
difference.
73
Ken ZL4NR
On 28/02/2020 10:09 pm, ja1nlx
wrote:
Ken
Delete Logger32.ini.
Rename Logger32.ini.OLD to Logger32.ini again.
Open Logger32.ini with text editor.
Maybe something wrong in [wndLogbookPage Settings] section.
Delete all lines in this section. Run Logger32. How now ?
[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3
73
On 2020/02/28 17:59, Ken McVie
wrote:
That works ok. Now how do I find the difference in the two
INI files??
73
Ken
On 28/02/2020 9:53 pm, ja1nlx
wrote:
Ken
Try with virgin Logger32.ini.
Look for Logger32.ini in the Logger32 folder. Rename it
Logger32.ini.OLD.
Run Logger32. Try edit in Logbook page window. How now
?
73
On 2020/02/28 17:44, Ken
McVie wrote:
I should add that I have done this lots in the past
without trouble.
73
Ken ZL4NR
On 28/02/2020 9:38 pm,
ja1nlx wrote:
Ken
What you see when you click any line. I see the
line highlighted with Yellow back color.
This color depends on your setting.
73
On 2020/02/28 16:18, Ken
McVie wrote:
Using
version 3.50.408 on W10 Home desktop computer.
I used to be able to click on a [for instance] name
in the logbook alongside a callsign, & change it
for something else. Now I can't change anything on a
QSO line by clicking on it.
I have a QSO with Rarotonga which shows the IOTA
number as OC-124 -- it should be OC- 013 according
to the QSL card that I have received, & I can't
find a way of changing this.
Is anybody else seeing this behaviour of not being
able to edit a line in the logbook??
Any thoughts much appreciated.
73
Ken ZL4NR
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
|
|
|
Re: DX spots have stopped
Here is another follow-up. I managed to get DX spots working again. I had entered PSK in the Setup Bands and Modes matrix, but failed to put in a frequency. This caused the failure of the spots to enter the DX spots window.
After a restart of Logger32, the band data now correctly follow the frequency. G-d's in her heaven, all's right with the world.
73,
Jan, KX2A
|
|
|
Re: Can't edit contacts in the logbook
Ken
As you say it may be better for you to copy/paste older
Logger32.ini on current one.
73
toggle quoted messageShow quoted text
On 2020/03/02 7:24, Ken McVie wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!
I have 63 lines in that section of the INI file, do you mean to
delete them all?? If I do this, will it mean I have to reset all
those parameters?? I could print out a copy I guess, which would
make it easier to "remake" the list bit by bit, testing as I go to
see where the problem lies.
In the 'UPDATE' files of L32, I have a INI file dated early
February, could I exchange this for my current one & see what
happens??
I tried changing the Page Index & the Page Index Column
numbers to what you sent me, & that didn't make any
difference.
73
Ken ZL4NR
On 28/02/2020 10:09 pm, ja1nlx wrote:
Ken
Delete Logger32.ini.
Rename Logger32.ini.OLD to Logger32.ini again.
Open Logger32.ini with text editor.
Maybe something wrong in [wndLogbookPage Settings] section.
Delete all lines in this section. Run Logger32. How now ?
[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3
73
On 2020/02/28 17:59, Ken McVie
wrote:
That works ok. Now how do I find the difference in the two INI
files??
73
Ken
On 28/02/2020 9:53 pm, ja1nlx
wrote:
Ken
Try with virgin Logger32.ini.
Look for Logger32.ini in the Logger32 folder. Rename it
Logger32.ini.OLD.
Run Logger32. Try edit in Logbook page window. How now ?
73
On 2020/02/28 17:44, Ken McVie
wrote:
I should add that I have done this lots in the past
without trouble.
73
Ken ZL4NR
On 28/02/2020 9:38 pm, ja1nlx
wrote:
Ken
What you see when you click any line. I see the line
highlighted with Yellow back color.
This color depends on your setting.
73
On 2020/02/28 16:18, Ken
McVie wrote:
Using
version 3.50.408 on W10 Home desktop computer.
I used to be able to click on a [for instance] name in
the logbook alongside a callsign, & change it for
something else. Now I can't change anything on a QSO
line by clicking on it.
I have a QSO with Rarotonga which shows the IOTA
number as OC-124 -- it should be OC- 013 according to
the QSL card that I have received, & I can't find
a way of changing this.
Is anybody else seeing this behaviour of not being
able to edit a line in the logbook??
Any thoughts much appreciated.
73
Ken ZL4NR
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
|
|
|
Re: Can't edit contacts in the logbook
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!
I have 63 lines in that section of the INI file, do you mean to
delete them all?? If I do this, will it mean I have to reset all
those parameters?? I could print out a copy I guess, which would
make it easier to "remake" the list bit by bit, testing as I go to
see where the problem lies.
In the 'UPDATE' files of L32, I have a INI file dated early
February, could I exchange this for my current one & see what
happens??
I tried changing the Page Index & the Page Index Column numbers
to what you sent me, & that didn't make any difference.
73
Ken ZL4NR
toggle quoted messageShow quoted text
On 28/02/2020 10:09 pm, ja1nlx wrote:
Ken
Delete Logger32.ini.
Rename Logger32.ini.OLD to Logger32.ini again.
Open Logger32.ini with text editor.
Maybe something wrong in [wndLogbookPage Settings] section.
Delete all lines in this section. Run Logger32. How now ?
[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3
73
On 2020/02/28 17:59, Ken McVie wrote:
That works ok. Now how do I find the difference in the two INI
files??
73
Ken
On 28/02/2020 9:53 pm, ja1nlx
wrote:
Ken
Try with virgin Logger32.ini.
Look for Logger32.ini in the Logger32 folder. Rename it
Logger32.ini.OLD.
Run Logger32. Try edit in Logbook page window. How now ?
73
On 2020/02/28 17:44, Ken McVie
wrote:
I should add that I have done this lots in the past without
trouble.
73
Ken ZL4NR
On 28/02/2020 9:38 pm, ja1nlx
wrote:
Ken
What you see when you click any line. I see the line
highlighted with Yellow back color.
This color depends on your setting.
73
On 2020/02/28 16:18, Ken
McVie wrote:
Using
version 3.50.408 on W10 Home desktop computer.
I used to be able to click on a [for instance] name in
the logbook alongside a callsign, & change it for
something else. Now I can't change anything on a QSO
line by clicking on it.
I have a QSO with Rarotonga which shows the IOTA number
as OC-124 -- it should be OC- 013 according to the QSL
card that I have received, & I can't find a way of
changing this.
Is anybody else seeing this behaviour of not being able
to edit a line in the logbook??
Any thoughts much appreciated.
73
Ken ZL4NR
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
|
|
|
David Perry <bumbledp@...>
|
|
|
Re: Logger 32:new computer
On Fri, Feb 28, 2020 at 10:52 PM, Bryan Sanders wrote:
Where would I need to go once I load logger 32 on the new computer.
Zip databases and logbook, zip user files. 2 icons on tle left on iconbar in L32. Install L32 on new computer, unzip backup created earlier. Recalculate statistics. Update. Done. No need to use adi file at ll. Mike
|
|
|
David
Use LogPrint utility. It reads exported ADIF and print it.
73
toggle quoted messageShow quoted text
On 2020/02/29 16:47, David Perry wrote:
I tried to save my l32 log pages so that I can print them.out and
keep with my old log books. I failed...
How do I do this? When I tried to export or save as one of the
various file types offered - which types I dont understand- it
kept trying to OPEN a file from my pc. rather than save as.
I just want to save and print. Is there an easy way?
David G4YVM
|
|
|
David Perry <bumbledp@...>
I tried to save my l32 log pages so that I can print them.out and keep with my old log books. I failed...
How do I do this? When I tried to export or save as one of the various file types offered - which types I dont understand- it kept trying to OPEN a file from my pc. rather than save as.
I just want to save and print. Is there an easy way?
David G4YVM
|
|
|
Re: Another DVK question.
I've clugged the problem by editing the .wav file using Audacity to
insert a few milliseconds of dead air at the start of the file.
73, VE6LB
toggle quoted messageShow quoted text
On 28/02/2020 16:16, Gerry VE6LB wrote:
This post triggered my interest in using the L32 DVK again. I
noted something that I've likely just overlooked in HELP.
I'm PTTing my FTdx9000D by radio command and find clicking a DVK
macro button, there is a no voice delay before PTT activates and
this cuts off the first couple letters of my call.
73, Gerry VE6LB
On 28/02/2020 07:56, Andy VA3PL
wrote:
Thanks Bob for
implementing <ESC> to DVK. Work fine.
I do have more request
when you in the mood to do it... 🙂
1-Can we have more
buttons. Twelve would be nice to have or as many as in CW
machine.
2-Can we have
staggering capability (multiple pressing of the same or other
buttons). Same way as in CW machine.
3-Can we have buttons
associated with F# (function) keys same way as in CW machine.
EG: F1 call CQ, F2 his report....and so on. You know what I am
talking about.
Then perhaps it should
be renamed to Digital Voice Machine or DVM...
🙂
SMILE
Thanks
SeventyThree
Andy SP9KR
--
73, Gerry VE6LB ve6lb@...
ve6lb.ve6hams.com
--
73, Gerry VE6LB ve6lb@... ve6lb.ve6hams.com
|
|
|
Re: Logger 32:new computer
Don’t forget the config files for the individual windows/functions. In addition to the Logger32.ini there are several INI,DB and TXT files that complete the full package. Hence the recommendation to make a full backup so all necessary files will be saved. Another way to transfer the program is to copy the entire Logger32 folder to the new computer, then run the 3.50 full install in your new folder and it will copy the necessary operating system files and leave your config files intact.
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Larry Fravel
Sent: Friday, February 28, 2020 5:36 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger 32:new computer Copy your old logger32.ini into the new installation and you should be OK. I would also create an .adi file of your old log and once the install is up and running with all the updates and club log updates then copy the .ini file and import the .adi file. You should be in business. May have to reset you clusters but that should do it. Larry K8YYY --
Today is a good day to have a GREAT Day!
|
|
|
