- Why Does DX4WIN Need Callsign Exceptions? - 10 March 2005
- Printing Directly on QSL Cards with DX4WIN - 5 June 2005
- Using the Dymo 310/330/400 Label Printer - 5 April 2006
- Label Formats for A4 Paper Size - 15 April 2006
- Using QRZ and QRZ.COM with DX4WIN - 13 June 2006
- DX4WIN Data Protection Strategies - 11 October 2006
- Managing Multiple Callsigns in DX4WIN - 13 November 2006
- Working with LoTW - 8 January 2011
- MMTTY and DX4WIN - 7 December 2006
- Master Calls - 18 December 2006
- Upgrade Tips - updated 1 January 2018
- Counting Entities in DX4WIN - updated 17 April 2011
- Contest Log Conversion - 21 February 2007
- Adding a New Entity to DX4WIN - 27 December 2007
- How to Import a File into DX4WIN with a Custom Filter - 13 November 2008
- DXCC Award Tracking - 11 January 2009
- Removing Duplicate QSOs - 19 March 2011
- DX4WIN Membership Lists - 2 June 2011
- Filters, Groups and Selections
- Analyze DX4WIN Country File Differences
- Integrating VE7CC CC user with DX4WIN
- CQ DX Marathon
- ICOM PW-1
- National Parks on the Air
- Islands on the Air (IOTA)
- Make it Easier to Import your WSJT-X log Using a Symbolic Link
- Add LoTW Status to Callsign/Mgr Lookup
- Identity DX4WIN QSOs missing from LoTW
- QSL Manager Database
- Combining Logs/Groups/QSLs
- How to Clear Upload Date
- Find Unanswered QSLs
- Print Address Labels for Direct QSLs
- Picking a Subset of Labels to Print
- ADIF Import Populates "Recvd" Field
- Installing and Running DX4WIN on Windows Vista/Windows 7/Windows 8
- CW Announcements of DX Spots
- Moving DX4WIN to Another Computer
- Simplify Importing from WSJT-X by Using a Symbolic Link
- Quick Tips (even shorter notes)
Kostas, SV1DPI sends this procedure for
merging two logs but making it easy to separate the two come QSL time:
- Open the logbook containing the QSOs you want to merge (import) from
- QSO -> Multiple QSO Operations -> Set Group Number, and set all QSOs to the next unused group number in your main log (see step #6 below)
- Save the log
- Open the logbook containing the QSOs you want to merge (import) into
- File -> Import/Export -> File -> Merge DX4WIN log, and choose the logbook from step #1 above
- Filter -> Edit Group Names, create a new group number (should match #2
above) and give it a unique name. Now all the QSOs from step #1 above will
have a unique group name and number, so you can tell them from your main log
- File -> Preferences -> Rep/Lab, add the text "%%" in a row. This will print the group name on your labels
- Labels -> Print QSL Labels and check the Print Group Names box
- Save your new log
The most common mistake is to forget step #8 above.
Kostas, SV1DPI suggests, "In the QSO
window, navigate to QSO -> Multiple QSO Operations -> Set Upload Date. Put
spaces in the date field and press OK! Maybe neither Paul knows it (hi hi). I
was waiting that the known trick 01/01/1901 would work but spaces works OK."
To search for QSLs you've sent but have not received, use F8 to search for
"Conf" = "N" and "QSL Date" = "01/01/1902" (or any date which is the earliest
date for which you want to search). This will ignore QSOs where the QSL Date is
blank (no QSL sent).
This may depend on the setting of one of your preferences. File ->
Preferences and click on QSO tab. Under Searching -> QSO Date, make sure it's
set to "Greater Equal".
When printing QSL labels, DX4WIN can also print address labels in-line. To
print address labels for stations with no QSL manager, the QSL "Method" field in
the QSO record must be set to "Direct" and the "QSL Mgr" field in the QSO record
must be set the same as the "Callsign" field. DX4WIN will not print "CALL via
CALL" on the QSO label, but it will print a corresponding address label for the
Dick Flanagan K7VC suggests, "Give the QSOs you want to print an immediate
label for a different QSL Method. It doesn't matter what that method is (Direct,
Ignore, $$$$, etc.) so long as it is unique to those QSLs you want immediate
labels for. Then specify that method when you go to print labels. Those will
then be the only labels that will be printed and all other label flags will be
DX4WIN can only import received serial numbers from an ADIF file into the
logbook "Recvd" field. If you want to import other received contest information
to that field, you will have to edit the ADIF file in a plain text editor (like
Notepad or Write) before importing the file. For example, you can modify an ADIF
file from the ARRL DX SSB contest (where transmit power is sent by DX stations)
by doing a search-and-replace. Change all occurrences of "RX_PWR" in the ADIF
file to "SRX" and then save the file. When you import this file into DX4WIN, the
received transmitter power will be stored in the "Recvd" logbook field. See the
ADIF specification to determine the name of the field that you want to
Or you can use this program.
You can install DX4WIN on Vista as a user (not administrator). The first time
you run DX4WIN, run it as an Administrator by right-clicking on the program icon
and choose "Run as Administrator". DX4WIN will then be able to copy the vichw11
driver into the Vista driver directory. Now you can run the program normally
without administrator privileges.
DX4WIN has a feature to announce needed DX spots in CW, using your PC's
speaker (the one on the motherboard, not the soundcard). In order to do this,
you must install the LPT driver.
Navigate to your DX4W### directory.; Then locate the Drivers directory and
double-click to open it. Inside there you should find lptdriver.exe.
Double-click on the driver program to install it. The default installation
directory may be "C:\dx4w803\lptdriver". Change the path to
match your DX4WIN installation, for example "E:\dx4w805\lptdriver".
You may be asked to reboot your computer after the driver is installed.
After re-starting DX4WIN, open your Preferences (File |
Preferences) and select the Packet1 tab. Locate the "Audio / Voice"
selection box and choose "CW speaker", then save your preferences.
It is really easy to move (copy) DX4WIN to another computer. This is not the
recommended way of installing DX4WIN, then copying/merging your existing data,
but does work:
- Using a USB flash drive, copy the DX4W### directory from your old hard drive
to the USB flash drive.
- Put the USB flash drive into the new computer.
- Copy the DX4W### directory from the USB flash drive to the SAME PATH on the
new hard drive. For example, if the old DX4WIN was installed in C:\Hams\DX4W805,
then create a C:\Hams directory on the new computer, and copy the DX4W805
directory from the USB flash drive to this new directory you created.
- Create a desktop shortcut to the DX4WIN.EXE program by navigating to your
DX4W### directory. Find the DX4WIN application (DX4WIN.EXE) and right-click on
it. Choose "Send to Desktop".
You should now be able to run DX4WIN by double-clicking on the desktop
- In Packet1 preferences, add your callsign to "Callsign Alert". When
someone tries to "talk" to you via a DX spot (by spotting your callsign),
the spot will be highlighted. (Jim AD1C)
- Edit the DX4WIN.TCP file to put your favorite node at the top. Then when
you start DX4WIN, just a couple ENTER keys in the Packet Window will start
the connection. (Jim AD1C)
- In Packet 2 preferences, under warning patterns, ON4MA has
""yourcallsign de *.* "" in the first warning pattern box, so it looks
like "ON4MA DE *.*". If someone sends you a talk over the cluster, a warning
window is opened. In the second, he has "NEW MAIL HAS *", the same warning
window is opened and shows you when new mail has arrived. Handy if you are
not in the shack. (Marc ON4MA)
- To make the radio frequency appear in the "Notes for this QSO" field, go
to the QSO window, then select QSO -> Contest Mode. Put the text "$$" (no
quotes) in the "Text to add to QSO note" field. Now the frequency of your
computer-controlled radio will be logged with your QSO.