After I did the last update to DXLab Launcher, I had problems opening up both Commander and Spot Collector. All other applications work, however, I get a " Component 'MouseWheelControl.ocx' or one of

On Sat, Jul 17, 2021 at 12:16 PM, g4wjs wrote: A static IP address is one way a destination gets a unique IP address and it is useful if you want others to know where to contact you (also know as well

There's also a $5.00 book, "TCP/IP for Dummies" and an online course at udemy.com Good luck! Jim wb4gcs@... On 7/17/2021 12:06, Dave AA6YQ wrote: This

Hi Dave, I'll have a go with some analogies that may help. UDP is like sending a letter, fire and forget. You put a message (datagram) into an envelope (IP packet) and send it to a already known

+ AA6YQ comments below "The Internet Protocol (abbreviated IP) is responsible for addressing host interfaces, encapsulating data into datagrams and routing datagrams from a source host interface to a

+ AA6YQ comments below + What is a "GT Logbook"? 73, Dave, AA6YQ

All I am struggling to move to the "next level" of passing information from DXLab to various pieces of hardware via an Ethernet connection. My problem is not with DXLab per-se but rather that much

I made a mistake in serted some incorrect data in the log window of WSJTX that pops up after a successful QSO. That informaton got passed along to QRZ, LOTW and eQSL as well as showing on the Grid

# I'm not aware of there being a dedicated IOTA cluster, but if you find one, please post the particulars here. Thanks! 73, Dave, AA6YQ

+ AA6YQ comments below Is there a telnet address for IOTA spots so I can add them to SpotCollector like I do SOTA? + Are you asking if there is a DXCluster that is dedicated to IOTA spots? ++ Yes, I

+ AA6YQ comments below + Yes, that's fine too. + Good! 73, Dave, AA6YQ

Yes, immediately after I sent my last email to you I realized what I had done wrong and corrected it. Fortunately, I did back up the log before I'd started anything. I used +1d and not +24hr but I

Thanks Dave. I was able to make it work--sort of. I isolated the wrong dated QSOs and did set up the exchange for the dates but ended up zeroing out the start and end times in minutes and seconds.

Thanks Dave. I was able to make it work--sort of. I isolated the wrong dated QSOs and did set up the exchange for the dates but ended up zeroing out the start and end times in minutes and seconds.

+ AA6YQ comments below All of my DXlab apps are up to date according to Launcher. In particular DXKeeper is 16.1.9. This afternoon I working some FT8 on several bands and decided to check to see how

...via the Databases tab of DXView's Configuration window. If you have DXKeeper or SpotCollector running, terminate them; then direct DXView to upgrade its USAP database. The USAP database specifies

+ AA6YQ comment below + OK. Please place your log file (suffix .mdb) in a zip archive, attach the zip archive to an email message that describes the date/time-range or QSOs that are missing, and send

Sorry, I forgot to mention that I had done that. I always do a ctrl click when I go back to the Log Qsos tab. Paul W5PF On 7/16/2021 6:34 PM, Dave AA6YQ wrote:

+ AA6YQ comments below + As a first step, please click the X button in the Filter panel at the bottom of the Main window's "Log QSOs" tab. Did your missing QSOs re-appear? 73,

All of my DXlab apps are up to date according to Launcher. In particular DXKeeper is 16.1.9. This afternoon I working some FT8 on several bands and decided to check to see how many new QSOs I had to