Re: [Dx4win] Logging FT8 qsos in V9

Ed, Here are my answers to your questions: 1. You can enter by hand. Version 9 supports db signal reports. Just enter -01 for example instead of 599. 2. Yes, you should log FT8 QSOs using the db format for signal reports. That is the accepted norm. Even LOTW supports that format. 3. Yes,

Re: [Dx4win] Not saving updates from QRZ

I tried again to change the state and county. The state stayed SC, but the county was blank. On Sat, Feb 24, 2018 at 8:45 AM, Jim Reisert AD1C wrote: > I had this happen this morning. It's not necessarily related to QRZ. > > I had logged a QSO as K3D/MAR because I did

Re: [Dx4win] Not saving updates from QRZ

The third time (once the state had been saved), I was able to change the county and save the QSO (using ENTER) On Sat, Feb 24, 2018 at 8:48 AM, Jim Reisert AD1C wrote: > I tried again to change the state and county. The state stayed SC, > but the county was blank. > > >

[Dx4win] Logging FT8 qsos in V9

ok, newbie to FT8. Made my first FT8 Qso last night, I think (lol) WSJT has the CAT control of my FTdx5000, so when I bring up DX4win, I get the com error, and just close it a move on, so that DX4Win comes up and runs normally without CAT radio control. Not sure if this ok or not, but seems no

Re: [Dx4win] Not saving updates from QRZ

I had this happen this morning. It's not necessarily related to QRZ. I had logged a QSO as K3D/MAR because I did not know the callsign. I then changed the Call to K3TD/M and the previous QSO information came up (NC/Duplin county). I changed this to SC/Marlboro and entered 49 as the group

Re: [Dx4win] Not saving updates from QRZ

This is very repeatable. I had it happen again. Find a QSO in your log with a state/county. remember the call. Now log a fake QSO with a fake call. Go bak to the QSO you just logged, and change the call to the other call, then TAB. State/county should populate from the previous QSO. Without

Re: [Dx4win] Not saving updates from QRZ

Jim and John, I just replicated the problem here as well. I am a QRZ subscriber, so normally when making a QSO I hit Update QSO in the Callsign/Mgr lookup. But I have found it does not update with new data unless the field in the logging window is blank. For example, if I have already worked

Re: [Dx4win] Logging FT8 qsos in V9

Short version: Take the ADI file that WSJT-X creates, import into D4W making sure that it's set to "Imported QSO is ignored". Everything is imported correctly into D4W complete with correct rstS & rstR report (e.g., -15, whatever). No need to clear the file afterwards. Very simple. I don't

Re: [Dx4win] Logging FT8 qsos in V9

> 5.) Lastly I did see Jim's W10 script for moving qso automatically from > WSJT into DXWin, would that work on XP platform? I have never written such a script. -- Jim Reisert AD1C, , http://www.ad1c.us __

Re: [Dx4win] Logging FT8 qsos in V9

Jim, I think he is talking about your email from a couple of weeks ago. The one in which you talked about a way to map windows to the wsjt-x file that is hidden in Users/AppDate/ etc. I have the email saved somewhere. 73, Dave, N4QS -Original Message- From:

Re: [Dx4win] Printing duplicate qsl cards.

Hello Bill, I presume you mean that you have the defaults set to print a QSL for every QSO? File > Preferences > QSO > QSL Card box checked In this case, simply set Label to N for each duplicate QSO. You may find it easier to have your default set to No and change it to Yes for the labels you

[Dx4win] LoTW flags/tags

I'm catching up on my LoTW submissions. I would like to mark previously uploaded QSOs as having been uploaded, but without including a date (for which I don't have and don't need). Is there a way to do this? Thanks & 73, Eric W3DQ Washington, DC

Re: [Dx4win] LoTW flags/tags

dx4win consider a QSO as uploaded only when a date in Upload Date field is filled. So you need to put a date. There is no meaning what date, but it needs a date. 73 Kostas SV1DPI Στις 25/2/2018 07:24, ο ericrosenberg...@gmail.com έγραψε: I'm catching up on my LoTW submissions. I would