Thanks Larry, All the calls are linked in LOTW to give credit to one call for awards etc.� so that part is fine. Yes have certs for all of them.��� My award totals etc are all fine

I read something the other day that suggested that SSDs might have a limited life in high write situations which seems a bit odd but if true would suggest that the page file would not be a

-----Original Message----- Sent: Saturday, December 16, 2017 2:23 PM To: dxlab@... Subject: Re: [dxlab] Multiple call signs In the "Auxiliary" part of DXK are three fields - station

Again, the race condition is in WSJT-X. It sends split commands in the after xx:58 (or xx:13/xx:28/xx:43/xx:58 in the case of FT8) without any consideration for the USB slot time, time necessary for

The root cause is that you evidently have WSJT-X controlling RX-TX switching independently of Commander. If you're going to use Commander for transceiver control, then use it for all transceiver

-----Original Message----- Sent: Saturday, December 16, 2017 2:04 PM To: dxlab@... Subject: [dxlab] Sorta OT: SSD upgrade I know it's somewhat off-topic, but the collective experience

I have found the solution to my problem of “losing xmit split” while in QSO. The computer interface to my TS-2000 is a West Mountain RigBlaster Pro. I am set up to use WSJT-X PTT via RTS on a

I have an I7 processor running Win 10 64 bit and have been using a 240 GB SSD for quite a while. The system and all programs run off of the SSD and I have 1 TB hard drive where most data is stored.

In most cases the SSD does not do that much. Boot time and App load times will drop and maybe drop dramatically but execution of the program will often see little or no improvement. SSD choice

I neglected to mention that you would need to upload the changes to LoTW assuming you have certs for the various callsigns. Getting certs takes only a few days normally. Your LoTW QSO count will be

Are your other calls from the same DXCC entity? If so setup multiple MYQTHs and assign the appropriate MYQTH to the different call signs. See http://www.dxlabsuite.com/dxlabwiki/ManageMultipleQTHs

In the "Auxiliary" part of DXK are three fields - station callsign, operator call sign, and owner callsign. You need to change the station callsign. If you know the dates of operation by callsign you

Several weeks back I moved from DXbase log to DXkeeper,� it took me a little while to adapt to the new logging,� and it far exceeds what I was hoping for,� great job and thanks very

Whoa, I did look there, but it didn’t register. At that point I wasn’t thinking adif. I was looking for a field name. It dawned on me later, when I thought about exporting, that the adif name

I know it’s somewhat off-topic, but the collective experience here has helped me out many times. I am running my radio software on an off-lease Lenovo small form factor desktop. It is an i5 and

Yes, you took the long way around. Look in the "Details Panel" section of <http://www.dxlabsuite.com/dxkeeper/Help/Items.htm> 73, Dave, AA6YQ

Hi Guys, I noticed errant entries in the "owner call" field in the Details panel of DXKeeper (not the Auziliary panel). I wanted to find all instances of these entries but could not find an search or

-----Original Message----- Sent: Saturday, December 16, 2017 9:52 AM To: dxlab@... Subject: Re: [dxlab] Glitch with eQSL Thank you Joe i will and will let you know. 2 questions related

As Joe W4TV said, check both the "Initialize eQSL sent to 'R' for each logged or imported QSO" and the "Initialize LoTW sent to 'R' for each logged or imported QSO" box. The next question is "how did

Yes, you will need to set the eQSL_Sent and LotW_Sent boxes to R in order to have them picked up by the "Add Requested" process. I do not know. However, if "Add Requested" was working previously and