开云体育

I have read the instructions and used them before to change QSO's in bulk ie QTH, but for some reason I can't seem to figure out how to change LOTW and eQSL from "N" to a blank. I did get QSL changed using the drop down menu in MOD, but the others are not listed in the drop down. Above the section with the drop down for MOD there is a place that has four spaces for Caption title and syntax (I think that is what it was) where you can save it to use again. I placed them in there and saved it as A-Index, but it didn't change the QSO's. I know I am missing something simple. Sorry Dave for my ignorance. TIA, Walt ~ WB7UOF

When I direct SpotCollector to load a special callsign file in .txt format, it appears to do so, showing that the file is being loaded, but the resulting list is empty. The file is in the same format I used on the computer with my previous DXLab installation, and the options are the same. There are no column headings (Callsign, Tag List, Expires), and I am unable to enter any text in the last row (the one with an * in the first column). Jim N7US

Can DXLab do this, or does anyone know of how I can make this happen? I plan on doing a "Special Event Station" And of course we will be logging all the contacts that are made. Now I know there are many web site that you can UP-Load your finished log, And it will plot on a map all the locations that are in the log. Done that many times. And we want to do something similar to that BUT.... We want it to happen Live. Like say we contact AA6YQ, and log him. Then in real time, or as fast as possible he gets plotted on the map. A Map that anyone can view. Does anyone know of any way that this can be done? Joe WB9SBD

https://shorturl.at/UqPK9 New case is coming along, did you get the images of the build and what screws are needed? -- Paul

I downloaded credits today and received this in the report. How do I go about fixing it? 73 Stan KM4HQE Log file = C:\DXLab\DXKeeper\Databases\KM4HQE.mdb DXCC Account = 1 Number DXCC QSO# Confirm Callsign Entity Code Date Band Mode Action 1 1127704703 card 4S7AB 315 2022-01-23 30M DATA no exact match found in log, new Entity-Band 2 1127704702 card 4S7AB 315 2023-07-23 17M DATA no exact match found in log, new Entity-Band 3 1127704701 card 4S7AB 315 2023-04-23 15M DATA no exact match found in log, new Entity-Band Total DXCC Credits 1521 DXCC Credits already linked 1515 DXCC Credits already marked as duplicates 3 Results if an AutoLink operation had been performed instead of an Analyze operation DXCC Credits missing information 0 DXCC Credits matching no QSOs 3 DXCC Credits matching multiple QSOs 0 DXCC Credits matching an already linked QSO 0 DXCC Credits matching one QSO but card/LotW ambiguous 0 DXCC Credits newly linked 0 DXCC Credits newly linked with card granted new credit 0 DXCC Credits newly linked with LotW granted new credit 0 DXCC Credits remaining unlinked 3

I imported my log from WI into my log down here in NC and now new Marathon entities won't go into the DX Marathon Realtime. 73 Dwight NS9I

The current version of DXKeeper provides an "IOTAmem4win update" checkbox in the IOTA panel on the Configuration window's Awards tab. DXKeeper's Reference Documentation describes this checkbox thusly: ------- This panel's IOTAmem4win checkbox determines whether generating an IOTA progress report will also create IOTA_Worked and IOTA_Confirmed update files for IOTAMem4WIN in DXKeeper's Reports sub-folder. The URL to which IOTAMe4WIN links http://www.rsgbiota.org/downloads.php4 produces a "page no longer exists" error if one attempts to traverse it. There is no mention of IOTAMem4WIN in the current IOTA-World documentation: https://www.iota-world.org/iota-directory/iota-programme-rules/iota-programme-application-procedures.html My understanding is that DXKeeper's current submission support for IOTA award applications provides the necessary ability to convey QSOs to IOTA-world for IOTA award credit; the file generated for submission to IOTAMem4WIN is not used. In the next version of DXKeeper, the IOTA panel on the Configuration window's Awards tab contains 3 new checkboxes: - Mixed - HF - VHF To avoid expanding the size of DXKeeper's Configuration window when the Awards tab is selected, I plan to make room by removinig the "IOTAmem4win update" checkbox. If there's a reason to not remote this checkbox, please let me know. 73, Dave, AA6YQ

This one is particularly sneaky! ClickFix: How to Infect Your PC in Three Easy Steps 73, Dave, AA6YQ

I'm trying to import ADIF files into DXKeeper. I have errors I need to fix for a single QSO with Hawaii that shows "<CNTY:8>HI,Kauai". I've been trying to learn how to properly fix this error without success. Any help will be appreciated. What have I done wrong? The original CQ Magazine references are no longer available. County Hunter seems to have taken over. I suspect there is an authoritative source I have not found. ERROR summary: <CNTY:8>HI,Kauai References: https://adif.org/315/ADIF_315.htm https://adif.org/315/ADIF_315.htm#Primary_Administrative_Subdivision * https://countyhunter.com/counties.htm My error notices: 1. invalid primary administrative subdivision: HI: <BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor> 2. invalid secondary administrative subdivision: HI,Kauai: <BAND:3>10m<CALL:6>KR1STA<CNTY:8>HI,Kauai<COMMENT:16>ARRL SS SSB 2002<CONT:2>NA<CQZ:1>4<DXCC:3>291<FREQ:9>28.632500<ITUZ:1>7<MODE:3>SSB<OPERATOR:6>KG6JOT<PFX:3>KR1<QSL_SENT:1>Y<LOTW_QSL_SENT:1>Y<QSO_DATE:8>20021116<TIME_ON:6>233600<RST_RCVD:2>59<RST_SENT:2>59<STATE:2>HI<TIME_OFF:6>233600<APP_LOGGER32_QSO_NUMBER:3>552<COUNTRY:3>USA<eor> Thanks Rich, NU6T

When uploading QSOs to LoTW, previously logged QSOs recovered to DXKeeper from OneDrive log backup are uploading to LoTW without any errors. However, New QSOs, logged since the recovery are being disabled thus: "Disabled QSL Queue entry for 9K2GR on 2025-03-13 at 23:22:08 - station location "Williston, Florida" specified in QSO's QTHID item "w4ndx" doesn't match station location "W4NDX" selected on the QSL Configuration window's LotW tab" I have chased this around until I am dizzy. How do I resolve this? Bruce, W4NDX. -- Bruce - W4NDX

Can I spot with notes from WinWarbler? say working a POTA station... I log him from WW then go to dxkeeper right click on his call to get the spot with notes to come up and inform that he is pota. I did not find in on a quick search. I did expand the layout on WW and did find I have a POTA window Tx for the software... before the suite...and learn something new all the time. Powerful! Tnx dave. Murf n7uvh

I need some help in configuring Grid tracker to save my FT8 contacts to DXkeeper. Any suggestions would be greatly appreciated. Al KA9OUT

Running W10 22H2 ... I have not seen anything here and know that this IS NOT A WINDOWS SUPPORT LIST but, for better or worse, Windows is the dongle that makes the DXLab suite work (N1MM+ Logger, too, and if it wasn't for these two software packages ...) I've seen the traffic about W11's crapulence of late but don't remember seeing anything about W10 ... Oh, and I have no plans to take the forced upgrade to W11 come fall ... -- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!

Just saw C6AJB on 17M FT8. DXView shows the last time on s 2023-03-21. The drop-down menu on JTAert shows the same. When I go to LOTW online and look up the last on time it shows 2025-03-12. This is just one example. I usually use 6-9 months for what I consider an active LOTW member. I have found out I need to check online if a call appears that I want to work. I've seen several calls, where DXView or JTAlert show the last upload more than 2 years ago but when I check online the last upload was within a month or so. I update the LOTW file with every new release. I know this isn't a DXLab or JTAlert issue but just a heads up to folks. Tom-KQ5S

Unfortunately I had to do a clean reset of Winows 11, now I have been reinstalling and configuring my applications. SpotCollector is now local spotting my FT8 decodes and I would like to stop it from doing that as I use SC for DX hits only. Can someone please tell me how to stop it? Please excuse my lack of comuter knowledge. Thanks Richard / N5YPJ

Hello all...I purchased a Laptop Win11 computer as I was ready to transfer my DX labs and various other application for my shack computer. I spent a $1000 dollars for 32 gigs ram and 1TB SSD and found that the computer would not connect to the internet. The network adapter was not stable and would not allow connection for more than a minute....The computer slowed down to a crawl and would not turn off or restart. Then the BSOD would show up while restarting then the computer would reboot and connect for a minute and then lose all internet connectivity. My computer guys who are hams told me that it is systemic and wished me well. Conclusion I think at this time with the plethora of issues with this operating system I am going to pay the, I hope, yearly fee for the Win10 support. I worked two weeks for nothing. I pulled the battery out of the Lap top and put it with the other dead computers. I can only hope the MS stabilizes this software or junks it like Win 8, but flogging a dead horse is a waste of time and has seriously impacted time on the air. I have also been told that a large number of hams are switching to Linux and abandoning MS. In conclusion I enjoy running DX Labs and have done so for 12 years. It is my sincere hope that MS stabilizes this software so that it is able to run DX Labs as well as my other Ham peripherals on a stable operating platform. Thanks for the bandwith for my rant...I am out a grand and frustrated beyond belief. BTW I am not feeling lucky. Jim K5KND

Hello Dave: As always, thank you for a great series of software. QRZ.com and the US Postal Service list a particular Louisiana Parish exactly as Saint Tammany. In contrast, countyhunter.com, HamCall.net, and DXKeeper Capture use the spelling of "St. Tammany". That works out well for my county chasing. Numerous county spelling differences occur nationally. QRZ.com XML is used by me. My question: what magic does DXKeeper do to actually make this spelling adjustment from QRZ.COM to DXKeeper Capture when logging a contact? Or something else is in the mix. Any comments will be appreciated! Many thanks and 73, Neil W3ZQI

This release - more gracefully handles Messages window memory consumption - improves the handling of mswinsck registration failures - remove superfluous Shift label from the Main window's "User-defined Controls" panel (tnx to Don WB6BEE) - prevents an errorlog.txt file entry when a Filter Group can't be selected for the current mode - supports the Icom IC-7760 (tnx to Bill AB4BJ and Mike N9ID - supports the Flex 8400 and 8600 when connected via FlexCAT (tnx to Larry KB1VFU) - when controlling an Icom transceiver with Spectrum-Waterfall support, provides a new "Callsign & Freq Sections" subpanel in the Colors panel on the Spectrum-Waterfall Configuration window that when set to "black" displays the "Spectrum-Waterfall" window's "DX Callsign" and "Frequency Axis" sections with a black background. (tnx to Tom KQ5S) --- This enables configuration of a fully-dark "Spectrum-Waterfall" window: https://www.dxlabsuite.com/commander/Spectrum-Waterfall-Dark-Spectrum.jpg - clicking a Band button in the Bandspread or Spectrum-Waterfall window after the transceiver frequency has not changed for an interval longer than the specified dwell time pushes the transceiver frequency on the current band's stack (tnx to Don WB6BEE) - extends the duration of "saved frequency" announcements in the Bandspread and Spectrum-Waterfall window's Band panels from 1 second to 3 seconds (tnx to Don WB6BEE) - updates the Configuration.htm documentation file Notes 1. Update your firewall and anti-malware applications to consider this new version of Commander to be "safe" - 0 of 72 antivirus scanners accessible via Virus Total detected malware <https://www.virustotal.com/gui/home/upload> - 0 of 13 antivirus scanners accessible via Jotti detected malware <https://virusscan.jotti.org/> 2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of <http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking> 3. After upgrading, to revert to the previous version of Commander, see <http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion> Commander 16.1.0 is available via the DXLab Launcher and via http://www.dxlabsuite.com/download.htm 73, Dave, AA6YQ

+ AA6YQ comments below Actually, I have an Elecraft K4D that it works with. + Commander support for the Elecraft K4 was introduced in August 2021. 73, Dave, AA6YQ

FYI: https://www.zdnet.com/article/windows-january-updates-trigger-audio-glitches-bluetooth-bugs-and-more/ 73, Dave, AA6YQ