[Dx4win] Fwd: Finding callsigns that were too long in DX4WIN 8.05

[kostas sv1dpi]

This is an email from AD1C to beta testers which will be very useful if 
you want to correct mistakes in loooooong calls. 805 could not keep 
calls longer than 12 characters. 901 can do it. So it is time to correct 
them. But which were these calls? The answer below from our beloved Jim 
AD1C...


Hi Folks,

Another tip:

DX4WIN 8.05 only supported callsigns of 12-characters or less.  DX4WIN 
9.01 supports callsigns up to 16 characters long.  So some of the calls 
in your old log may be truncated, and you will want to fix them in your 
9.01 log.

To find these long callsigns, search for a string of 12 question mark 
characters in the Callsign field of the QSO window.  This will filter 
your log to only callsigns that are exactly 12 characters long.  You can 
do this in either 8.05 or 9.01, but it's easier in 9.01 because you can 
make the corrections at the same time:


​
You will find a number of calls that are exactly 12 characters long and 
are OK, such as these:

  * HB0/DL1GGT/P
  * PJ6/PA3GIO/M
  * 5Z4/UA4WHX/A
  * XF1/F9IE/XF3

Yet here some callsigns from my log that are truncated and will need to 
be fixed:

  * XF3/F6AOI/XF (compare to the last callsign above) [*]
  * HF55PKZDARBR (correct call is HF55PKZDABROWA)
  * VE100VIMY/VE (correct call ends in VE#)
  * VE100VIMY/VO (correct call ends in VO#)
  * VE100VIMY/VY (correct call ends in VY#)


[*] busted call, it should be XF1/F6AOI/XF3.  I did not notice the 
problem even though I have a QSL card (somewhere)!  Here are the correct 
calls from the RSGB IOTA database; the top three are all too long for 
DX4WIN 8.05:

  * XF1/F5TYY/XF3
  * XF1/F6AOI/XF3
  * XF1/F6BFH/XF3
  * XF1/F9IE/XF3

Especially take note of any call that ends in a '/'.  It's probably 
missing /A or /P at the end.

When editing the callsign in your log, also clear any Upload Dates, and 
set either the LoTW or eQSL flags to 'Y'.  This will force the updated 
QSO, with the correct callsign, to be exported for your next LoTW or 
eQSL upload.

One way to tell if the call is now correct is that there may finally be 
a manager listed in the QSL Mgr field.

Hopefully, you took good notes so you know what the correct long 
callsign should be.  If you can't figure it out, I have most all DX 
spots made since 1997, so I can search the call for you.

73 - Jim AD1C

p.s. here is a list of calls from the DX4WIN QSL manager database that 
are longer than 12 characters:

HF55PKZDABROWA
OM2015TITANIC
ON500MERCATOR
PA0GAM/OH0/OJ0
PG540BUFFALO/J
VE100VIMY/VE1
VE100VIMY/VE2
VE100VIMY/VE3
VE100VIMY/VE4
VE100VIMY/VE5
VE100VIMY/VE6
VE100VIMY/VE7
VE100VIMY/VE8
VE100VIMY/VE9
VE100VIMY/VO1
VE100VIMY/VO2
VE100VIMY/VY0
VE100VIMY/VY1
VE100VIMY/VY2

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu 
<mailto:jjreisert at alum.mit.edu>>, http://www.ad1c.us