<ar@...> wrote: P.S. I forgot to address your question about registration. I was able to create an account at: http://cservice.worldirc.org/live/ and I could use it to login to 'X',

Hi John, Do you have multiple instances of SpotCollector attempting to use WorldIRC at the same time? If you do, you will need to use a different username (nickname) on each - e.g. W1JA-1, W1JA-2,

Dave, In my case, I've had this problem for several weeks. I like CQDX (using it adds DX Summit as a spot source) and I miss it now that it's gone. I'm not quite ready to give up yet... Iain, Do you

The correct way Joe but can be a lot of work. 😊 Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb

Hi Scott, CI-V IC-731 mode is archaic and was only needed when the old IC-731 was used on the same CI-V bus as a more modern Icom. The IC-31 used a different frequency format in CAT commands with a

Hi Dave, This is an Icom IC-775DSP. I was just getting WinWabbler setup for the first time, so if I recall, most of my change were there. I could not get Commander or WinWabbler to transmit, so I

+ AA6YQ comments below I got back the sound, by just enabling the sound alarm setting! Of course I should have checked this before writing a post here. But I don't understand why the sound was

I got back the sound, by just enabling the sound alarm setting! Of course I should have checked this before writing a post here. But I don't understand why the sound was disabled. I have not touched

+ AA6YQ comments below Alarmsound from SC has disappeared. I have Windows 10 with latest update Version 20H2 installed 1 November. I have an Icom IC-7300 with builtin sound driver USB. Sounds from

+ AA6YQ comments below I'm not sure what I did, but now Commander, DXKeeper, and WinWabbler all show a funky format for the frequency. So now: 3.925.00 Becomes: 392,500.00 It was working fine, then

I don't know anything about the WorldIRC service, but from a quick look around, it gives me the impression of something that's dying a slow death. Their services seem to be somewhat broken - at least

Hi All, I'm not sure what I did, but now Commander, DXKeeper, and WinWabbler all show a funky format for the frequency. So now: 3.925.00 Becomes: 392,500.00 It was working fine, then I was playing

+ AA6YQ comments below I have two locations defined in TQSL: My home QTH and one in another state where I sometimes operate portable for Field Day. Historically in my DXKeeper log these locations

I *DO NOT* allow the LotW data to overwrite my log data. I have seen far too many instances of W1/W2/W3/W8/W9/W0 callsigns that have been in my log for 20+ years and confirmed suddenly appearing as

OR NOT !!! Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb

+ AA6YQ comments below + Historically, there have been complaints about the accuracy of information submitted by QSO partners, incorrect grid squares, and swapped CQ and ITU zones being the most

Dave - I also permit LoTW to override my log, for the reasons cited by Neil in his response. Dave - K9FN

FWIW ... I let it overwrite as that's what my QSO partner has set for his station location in LoTW which may be better data than what I have logged for the station previously, or that QRZ has. Neil,

Thanks for the errorlog, Rod. DXKeeper is behaving as designed: a callbook lookup will not over-write name and QTH information already present in the Capture window - information that you may have

I note that when I do an update from LotW, I get a lot of mismatched Grids, and other stuff like county; my tendency is to not let the update overwrite with LotW data; as the operation may have been