hamlogger@groups.io

Home Messages Hashtags

Between

and

DVK Andy VA3PL #79035 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
More All Messages By This Member
Re: DX spots have stopped KX2A #79034 JA1NLX, I renamed Logger32.INI (sic) to Logger32.INI.old. Logger32 started as if it were the first time. I connected to K2LS, which was already in Telnet, and did a sh/dx in the telnet window. A dx list appeared in Telnet, but there were no entries in the DX spots window. 73, Jan, KX2A
More All Messages By This Member
Re: DX spots have stopped Jim Hargrave #79033 Jan, Did you press <Enter> after your !callsign? Jim – w5ifp- toggle quoted messageShow quoted text -----Original Message----- From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of KX2A Sent: Friday, February 28, 2020 7:27 AM To: hamlogger@groups.io Subject: Re: [hamlogger] DX spots have stopped JA1NLX, I typed !KX2A into the callsign field in the entry window and nothing happened in the DX Spot window or in the telnet window. That is an exclamation point in front of my callsign. 73, Jan, KX2A
More All Messages By This Member
Re: DX spots have stopped ja1nlx #79032 Jan It looks DX spot window not working. Try virgin Logger32.ini and see whether DX spot are displayed in DX spot window. Virgin Logger32.ini ? Yes look for Logger32.ini in Logger32 folder. Rename it to Logger32.ini.OLD. Run Logger32. Logger32 open with default settings. Connect to any telnet host and see whether DX spot are displayed in DX spot window. 73 toggle quoted messageShow quoted text On 2020/02/28 22:26, KX2A wrote: JA1NLX, I typed !KX2A into the callsign field in the entry window and nothing happened in the DX Spot window or in the telnet window. That is an exclamation point in front of my callsign. 73, Jan, KX2A -- 73 de aki JA1NLX
More All Messages By This Member
Re: HamCap 2020 SSN.dat Michael Harris #79031 Just go to the obvious place, the source of the application: http://www.dxatlas.com/Download.asp Scroll down to Ssn.dat toggle quoted messageShow quoted text On 28/02/2020 10:03, Gerald Boutin wrote: On Fri, Feb 28, 2020 at 03:43 AM, Gary Wilson wrote: If you use the add on HamCap program for propagation prediction, you may find that it doesn't work beyond December 2019. That's because the predicted sunspot numbers within it ended in December 2019. See https://swling.com/blog/2020/01/ham-cap-and-voa-prop-fixing-ssn-look-up-files/ for a replacement SSN.dat file that can simply be pasted into it's app data directory to update it. This solved the problem for me. 73 Gary, K2GW Gary, Thanks for the reminder. However, the link you referenced is pointing to data from VP9KF's "guesses" in 2018. I would recommend instead using the updated SSN number info for Hamcap directly from the Hamcap author's site. http://www.dxatlas.com/Download.asp -- Gerald, VE1DT
More All Messages By This Member
Re: DX spots have stopped KX2A #79030 JA1NLX, I typed !KX2A into the callsign field in the entry window and nothing happened in the DX Spot window or in the telnet window. That is an exclamation point in front of my callsign. 73, Jan, KX2A
More All Messages By This Member
Re: HamCap 2020 SSN.dat Gerald Boutin #79029 On Fri, Feb 28, 2020 at 03:43 AM, Gary Wilson wrote: If you use the add on HamCap program for propagation prediction, you may find that it doesn't work beyond December 2019. That's because the predicted sunspot numbers within it ended in December 2019. See https://swling.com/blog/2020/01/ham-cap-and-voa-prop-fixing-ssn-look-up-files/ for a replacement SSN.dat file that can simply be pasted into it's app data directory to update it. This solved the problem for me. 73 Gary, K2GW Gary, Thanks for the reminder. However, the link you referenced is pointing to data from VP9KF's "guesses" in 2018. I would recommend instead using the updated SSN number info for Hamcap directly from the Hamcap author's site. http://www.dxatlas.com/Download.asp -- Gerald, VE1DT
More All Messages By This Member
Re: Can't edit contacts in the logbook Ken McVie <kenmc@...> #79028 These are the settings in my OLD .INI file Logbook Page Index = 45 Logbook page Index column = 0 I will play again tomorrow, it's bed time here. Many thanks for the help so far!!! 73 Ken 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
More All Messages By This Member
Re: Can't edit contacts in the logbook ja1nlx #79027 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 toggle quoted messageShow quoted text 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
More All Messages By This Member
Re: Can't edit contacts in the logbook Ken McVie <kenmc@...> #79026 That works ok. Now how do I find the difference in the two INI files?? 73 Ken toggle quoted messageShow quoted text 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
More All Messages By This Member
Re: Can't edit contacts in the logbook ja1nlx #79025 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 toggle quoted messageShow quoted text 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
More All Messages By This Member
Re: Can't edit contacts in the logbook Ken McVie <kenmc@...> #79024 I should add that I have done this lots in the past without trouble. 73 Ken ZL4NR toggle quoted messageShow quoted text 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
More All Messages By This Member
Re: Can't edit contacts in the logbook Ken McVie <kenmc@...> #79023 Yes I see the same, but then I can't edit anything. As soon as I click on a box to edit it, the logbook page just goes back to the latest QSO entered. 73 Ken ZL4NR toggle quoted messageShow quoted text 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
More All Messages By This Member
Re: Can't edit contacts in the logbook ja1nlx #79022 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 toggle quoted messageShow quoted text 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
More All Messages By This Member
HamCap 2020 SSN.dat Gary Wilson #79021 If you use the add on HamCap program for propagation prediction, you may find that it doesn't work beyond December 2019. That's because the predicted sunspot numbers within it ended in December 2019. See https://swling.com/blog/2020/01/ham-cap-and-voa-prop-fixing-ssn-look-up-files/ for a replacement SSN.dat file that can simply be pasted into it's app data directory to update it. This solved the problem for me. 73 Gary, K2GW
More All Messages By This Member
Can't edit contacts in the logbook Ken McVie <kenmc@...> #79020 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
More All Messages By This Member
Problem with WAZ Highlights in DX Spot Window Greg - WC0M #79019 I have been running the latest update (v3.50.408) on Windows 10. I noticed that even though I have WAZ credits in all 40 zones, the Spots Window highlights are indicating that I need many zones for WAZ. When I rollback to v3.50.407 the problem goes away. I noticed that the issue popped up immediately after applying the DXCC award to track from Phone to Mixed sometime after the update. I tried recalculating statistics to no avail. I tried switching between Mixed, Phone and CW in v3.50.408 and the problem persists. In v3.50.407 when I switch, the appropriate changes are applied. A picture is attached from v3.50.408 and from v3.50.407. In My setup I use orange for the WAZ highlight. The v3.50.408 picture shows a lot of orange highlights that should not be there. Has anyone else seen this problem? Thanks Greg - WC0M
More All Messages By This Member
Re: DX spots have stopped ja1nlx #79018 Jan Try this. Type !KX2A in callsign field in Logbook Entry Window and hit Return key. Is KX2A displayed in DX Spot Window ? 73 toggle quoted messageShow quoted text On 2020/02/28 9:37, KX2A wrote: Jim, I followed these links: DX spots-> Setup -> DX spot -> blocking/pass filters -> tabbed display. I created the following: Spotting cont. : no checks Destination cont. : no checks Band: blocked 60 M and 6 M and higher Mode: no checks DX: no checks Originator: one US station blocked Comment: blocked "Please" Dupes: no checks Result was still no spots to DX spots grid 73, Jan, KX2A -- 73 de aki JA1NLX
More All Messages By This Member
Re: DX spots have stopped KX2A #79017 Jim, I followed these links: DX spots-> Setup -> DX spot -> blocking/pass filters -> tabbed display. I created the following: Spotting cont. : no checks Destination cont. : no checks Band: blocked 60 M and 6 M and higher Mode: no checks DX: no checks Originator: one US station blocked Comment: blocked "Please" Dupes: no checks Result was still no spots to DX spots grid 73, Jan, KX2A
More All Messages By This Member
Re: Comments from DX spots n5kd #79016 Ah…. I found it. I had checked the box that says “Transfer DX comments to this field”. You pointed me the right way… Thanks Aki. 73’ Pete, N5KD. Sent from Mail for Windows 10 toggle quoted messageShow quoted text From: ja1nlx Sent: Thursday, February 27, 2020 11:22 PM To: hamlogger@groups.io Subject: Re: [hamlogger] Comments from DX spots Pete What is adif field for User field 5 ? I do not duplicate this though... 73 On 2020/02/28 8:08, n5kd wrote: Good evening, I have a small issue since I upgraded to version 408 (I think that’s when it started). When I click on a DX spot, the comments from that spot are being transferred into my log entry window in the “User field 5”. It overwrites the preset text I have in there. Is it just me? I have checked my settings for user field setup, and QSO masks. I don’t think anything has changed my end. So, currently my rig is being logged as a “Bingo”. Must be a new Yaesu or something. 73’ Pete, N5KD. Sent from Mail for Windows 10 -- 73 de aki JA1NLX
More All Messages By This Member

3101 - 3120 of 82114

Home Messages Hashtags About Features Pricing Updates Terms Help Twitter