Hi Paul
I agree of course with everything that you say; but the /SAN is on the QSL
card
The real problem is DX4WIN correctly identifies it as Corsica in the logging
program, but it is the ADIF export file from DX4WIN that is causing the
errors.
If they were consistent, then I would know how
I may be wrong about this, but I don't believe DX4Win uses the numeric
entity code.
It's problematical anyway because it is NOT standard... there are 2
lists, ADIF and ARRL DXCC. The trouble is ARRL only assigns the code
after the country is recognized for DXCC. ADIF assigns the code as soon
On 12/28/2009 7:08 AM, Mel wrote:
I may be wrong about this, but I don't believe DX4Win uses the numeric
entity code.
It's problematical anyway because it is NOT standard... there are 2
lists, ADIF and ARRL DXCC. The trouble is ARRL only assigns the code
after the country is recognized for
It appears that ADIF has changed some of it's numerical codes in the
last couple of years. When I attempted to do a reconciliation a while
back (last couple of years) there were some entities that definitely did
not match. I did some research at the time. When I checked, the ARRL
numbers and
I was suggesting, indirectly, that Dave ensure he is using an up to date
adif.pmp file...
The reason I suggested this is, for a long time, I was only updating my
.cty file and thought he might have made the same mistake.
Jim Reisert AD1C wrote:
On 12/28/2009 7:08 AM, Mel wrote:
I also find
Mel
I don't think it is small errors that caused the problem I reported; it was
DX4Win log interpreting , say TK0KP/SAN as Corsica as displayed; and the
ADIF export interpreting it as the ADIF code for Sweden.
I checked it with the ADIF web page; so I understand what is screwed, but
not how it
Hello all.
About the strange errors in ADIF export, I made the following test:
1. I added TK0KP/SAN to my log. Dx4win (v8.03) tried to assign it to
Sweden, but I writed down TK in the prefix cell (I guess Dx4win created
an exception for this call).
2. I exported part of my log (i.e. only
Can't get the ic7800 and dx4win(8.03) to send audio in psk mode (it works in
lsb or usb and rtty also)
have tried the suggestions from Joe but no luck!
anyone have this working ??
BR
LA5SJA
Geir Eriksen
Mob 95102334
Fra: micro...@yahoogroups.com [mailto:micro...@yahoogroups.com] På
Doug,
The function key messages remain the same from your previous
version. You can edit them with Alt-E when your are in the PSK
respectively MTTY window. Alt-H and search for function keys to
get help.
73,
Kjell, PB3SM - SM6CPI
-Original Message-
From:
Well, like most things I mess up, pure cockpit error The box was not
checked. And, yes, I know LoTW doesn't yet work for CQ awards, but I track
things anyway. Just how I choose to do it.
Thanks to all who replied.
Steve
In a message dated 12/27/2009 9:00:28 P.M. Central Standard
So has anyone else got any thoughts about the issue with CW keying
locking up in version 8.03? As I posted to this list, I've tried
literally every combination of using CW Keying PTT on both DTR and RTS
with no luck. I've tried a completely clean install on the same computer
with the same
For those who are using the DX4WIN Keyer to Key your rigsAnd have newer
computers that do not have LPT-1 ports, just USB
How do you do it?
I finally got a USB to Serial cable that would drive the Band Change on the
FT-920, and now I am ready to Key the rig using DX4WIN.
Thanks and HNY
Jim,
Noticed difference with QSL addresses DX4 vs. QRZ
example look up DL1QW
73 Bernie/WO2N.
DL1QW refers to QRZ for his mailing address okay
__
Dx4win mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help:
Hello Hugh
1) the simplest solution is to buy a usb to serial adapter and make a
homemade interface like manual says to key cw. The problem is that cw maybe
is not so good especially when the prossesor load is too high.
2) one better is to buy a pci card to put inside your cimputer and use the
Ver 8.03 - I opened DX4WIN today and all of a sudden I have the RTTY
window open - and I can't get rid of it. I can minimize it, but Alt F4
won't get rid of it and I can't remove it with any of the usual methods.
Any suggestions?
Thanks
Greg
K9IG
Just as a follow-up, I switched the keying from COM3, which is on an
added-on card to COM1, which is the serial port located on the
motherboard (on the off chance there was something odd about the serial
port drivers) and unfortunately it made no difference.
On 12/28/2009 4:04 PM, David, K2DBK
On Mon, Dec 28, 2009 at 4:59 PM, Greg Clark put...@yahoo.com wrote:
Ver 8.03 - I opened DX4WIN today and all of a sudden I have the RTTY
window open - and I can't get rid of it. I can minimize it, but Alt F4
won't get rid of it and I can't remove it with any of the usual methods.
In your
That was it Jim - gone now. I've never even opened the RTTY pref tab before so
was perplexed. Appreciate the assist.
Greg
K9IG
From: Jim Reisert AD1C jjreis...@alum.mit.edu
To: Greg Clark g...@k9ig.com
Cc: dx4win@mailman.qth.net
Sent: Mon, December 28,
I can't figure how how it would have been set all of a sudden, but
I'm glad it's fixed now.
- Jim
On Mon, Dec 28, 2009 at 5:44 PM, Greg Clark put...@yahoo.com wrote:
That was it Jim - gone now. I've never even opened the RTTY pref tab before
so was perplexed. Appreciate the assist.
Greg
I suggest the K1EL WinKeyer USB. I wished that I had gotten one of these
sooner.
Too many times my computer would do too much other stuff at the same
time as the program was generating CW. Too much stuttering, and
long/short dits/dahs was the result. I had been using LPT1 and Comm port
keying
I have started working on DX4WIN.CTY #73. You can read the release
notes here:
http://www.country-files.com/dx4win/release.shtml#73
Again, I appreciate all the contributions of Alan, G3PMR of
Club Log.
I plan to release the new file the weekend of January 2/3. Please send
me any changes
21 matches
Mail list logo
