| Jim Reisert : DX4WIN | Convert QSX Frequency in Log |
The qsxfix program re-formats the QSX frequency in your logbook.
Version 1.2 of the program was released on 4 August 2009. Click on this link to download the program.
This is a simple utility to re-format the "Notes for this QSO" field in your logbook. It modifies the QSX frequency slightly so it won't be "stripped" by the DX4WIN 8.x multiple-QSL operation, "Set Freq from note"
The original format of a QSO note containing a QSX frequency is like the following:
10,109/10,111KHz <any other text>
where first frequency is the receive frequency, and the second frequency is the transmit frequency. After running the program, the QSO notes field will look like this:
10,109KHz QSX 10,111KHz <any other text>
Then after conversion by DX4WIN 8.x, during which the first frequency found in the "Notes for this QSO" field will be moved to the Freq field, what will be left is:
QSX 10,111KHz <any other text>
After downloading the program, extract (unzip) the QSXFIX.EXE file to your old DX4WIN\SAVE directory.
Now, in DX4WIN, go to File | Import/Export, select DX4WIN6 format, and export your log. Default is to save it it to the same name as your .DXL file.
Next, open a Windows "CMD" (command) window, and navigate to your DX4WIN "SAVE" directory using the cd command, i.e.:
cd c:\program files\dx4w707\save
Run the program by typing:
qsxfix <yourcall>.DXQ [<othername>.DXQ]
The first argument is the name of the file you exported in DX4WIN6 format. Do not include the <>. The second argument is optional. If you don't specify the second argument, then the output file will be named <yourcall>.qsx.DXQ. The optional second argument should end in .DXQ so that the DX4WIN import routine can find it.
After the program finishes, the output will look something like this:
Convert QSX Frequencies in DX4WIN log - Version 1.1
Jim Reisert, AD1C - Aug 3 2009 22:46:21
Can't determine QSX frequency: 144,050KHz S3/S2 - 40s burst
Can't determine QSX frequency: 14,021KHz KW good QSO 1/24/79
Can't determine QSX frequency: 28,750KHz KW list w/ DL2OC
Can't determine QSX frequency: 7,005KHz KW 200W - 1/4 wave GP
Can't determine QSX frequency: 3,800KHz KW beat K1ZM/W1WEF
Can't determine QSX frequency: 7,044KHz KW VE/LM
Can't determine QSX frequency: 24,896KHz 500W his first USA/12M
Can't determine QSX frequency: 21,260KHz KW Becky/Susie
Can't determine QSX frequency: 14,291KHz 100W worked me as AD1C/0
Wrote 86733 QSOs to ad1c.qsx.DXQ
The program uses pattern-matching techniques to ensure that it only modifies QSX frequencies and nothing else. It will print out warning messages if it finds a '/' character in the QSO note, but doesn't satisfy the requirements for being a QSX frequency.
Next, go into DX4WIN and save your log. It's good to save it to a different name just in case something bad happens.
Go to File | Import/Export and select the DX4WIN6 format. Click on File | Import and select the file you created from the program (<call>.qsx.DXQ or <othername>.DXQ). When you see the selection box for "Options for duplicate QSOs", choose "Imported QSO replaces existing QSO (SLOW)". Then click on the OK button. After the import is complete, you will get an information pop-up, "No Notes file found." You can ignore (dismiss) it. The next information box will say "Import finished" and report the number of duplicate QSOs that were processed. If there are any errors (there should be none), search for "Error:" in the "Notes for this QSO" field.
If you want to import the .DXQ file into an empty log, first copy the <yourcall>.DXN file (which contains callsign notes) to <yourcall>.qsx.DXN. Then you can import both the QSO data and callsign notes. However, this empty log will NOT have any of your group names or selections defined.
I realize that running a program like this which makes wholesale changes to your logbook can be frightening. Like all software, use at your own risk.
Please contact me with any questions or concerns.