Frequently asked questions
Tip: use your web browser's SEARCH feature to search for topics of interest on this page. In most browsers, this feature can be accessed by hitting <CTRL-F> or selecting the Edit > Find menu item.
Can I use my logbook from another logging program with Win-EQF* ?
In almost every case, the answer is YES. In Win-EQF*, the import/export utility (called File-EQF) is available from the File pulldown menu. This utility allows you to take a logbook file from another program, and convert it into the format required by Win-EQF*. Many logbook programs are listed on the menu of File-EQF for direct conversion, including CT, NA, Hyperlog, Logic 3, HamRad, and KAGOLD. Also provided is a dBase file import and export, a common format recognized by many programs such as Microsoft Access. Also, ADIF is fully supported.
For many other logging programs, the ASCII text import capability can be used. The ASCII text menu allows you to setup for the format of the information to be converted; the column numbers where the callsign, RST, name, QTH, and other fields are located and how many characters are in each. The ASCII import feature of File-EQF has been used to convert logs from WJ2O, WF1B, Easy DX, TR, AcuTerm, MicoHam, Super Duper, and others. Any logbook program that can generate a text file report of your log will support this method.
Win-EQF* also generates the Cabrillo contest logbook format.
Does Win-EQF* work with Windows 7 or Windows 8 ?
Keywords: Windows 7, Windows 8, compatibility, Win7, Win8, compatible
Rest assured it does - in 99% of the cases! Win-EQF* is not specifically tailored for the Windows 7/8 platform, rather it is a general Win32 application. The author uses a Windows 7 machine for development and testing of Win-EQF*.
While the short answer is "yes", the long answer is: "it depends". It depends on your system as a whole, what third-party system management / OEM / vendor "helper" applications are active, etc. - just like it does for any Win32 system. As such we recommend that you download Win-EQF* and give it a try - remember, you've got a FREE 30-day trial period. If you're already a Win-EQF version 1.xx user, just install Win-EQF* to a different folder (e.g. Win-EQF2) and it will co-exist with your version 1.xx program - and you'll be able to uninstall it if you for some reason don't like it.
If you happen to be running Windows VISTA, Windows 7 or Windows 8 / 64 bit and everything else fails, try installing XP Mode (Microsoft Virtual PC - a license is probably included in your Microsoft Windows installation). There is also one known issue with Win7/64 and Win8/64.
Using XP Mode, there has been reports of Win-EQF* reporting a TVICH32 driver error when trying to access a CW keyer through the LPT port (line printer port). In this case, turn the feature off by selecting Setup > Station #1 (or #2) CW keyer > Built-in keyer > NONE or assign it a COM port instead of an LPT port (different CW interfaces are required for COM and LPT ports - please refer to the user's manual).
Does Win-EQF* work with Windows 95/98/ME?
The last Win-EQF* version which supported the legacy Windows 9x/ME operating systems, was version 2.18 (no longer available for download). We're proud, though, to have supported the legacy Windows versions several years longer than Microsoft did.
How does Win-EQF* determine the latitude/longitude of a DX station?
Win-EQF* makes a "best attempt" at determining the latitude and longitude of the station you're logging. The result can be seen in Google Maps (<ALT-G> from the logging screen), giving different location estimates varying with the degree of accurancy in the location data known to Win-EQF*.
- If no callbook is connected or if the callbook doesn't return any location data (grid square), Win-EQF* will use the coordinates provided by its own PREFIX.LIB for the actual prefix; this provides a rough position estimate.
- If you're logging a US or Canadian station, Win-EQF* will use the coordinates provided by STATES.LIB from the moment the STATE field contains meaningful information. Normally, this will result in a position estimate near the state capital.
- If Win-EQF* knows the grid square, either from a callbook or by you entering it manually, the calculated position will be quite accurate; the position is estimated to be at the center of the grid square.
- For non-NA stations, only (1) and (3) apply.
In short: Win-EQF* will provide an accurate location pinpoint only if you know the grid square of the station you're currently logging. Please note that some callbooks provide erroneous location data.
What's the address of the contest calendar used by Win-EQF* ?
Win-EQF* makes use of WA7BNM's excellent contest calendar (Contest > Contest Calendar).
The contest calendar can be found right here.
Does Win-EQF* use an open file format?
Win-EQF* stores all QSO data in a plain text file. The file format is well documented. You can rest assured that your QSO data is not locked away in a proprietary database format. The file format is very structured, as such it is not recommended to attempt editing the logbook file manually with a text editor.
Win-EQF* also comes with the File-EQF* utility, supporting conversions between several logbook formats - including the ADIF standard.
What TNCs and data controllers will work with Win-EQF* ?
Win-EQF* works with any TNC that can be controlled using the COMMAND mode of operation. This is sometimes called "terminal" operation, because the computer software mimics the action of a terminal program. Practically all TNC's support this method of operation, including AEA, Kantronics, and MFJ.
Some programs use the "HOST MODE" of operation with TNC's. If you use other TNC software, be sure that software is set to return the TNC to COMMAND mode after it exits. A common parameter controlling this behavior is called "HOST MODE ON EXIT", which should be set to off or false for proper TNC operation with Win-EQF*.
You can configure Win-EQF* to recognize your TNC on any COM port and at any baud rate. (Win-EQF*, since it is a Windows program, does not care about the IRQ).
Can Win-EQF* use both a TNC and a Telnet DX cluster at the same time?
Win-EQF* was never intended to run both a TNC and an intenet/telnet cluster at the same time. Select one or the other in the Win-EQF* setup menus. Or opt for a supplement, such as DX Telnet or BandMaster.
How can I apply filtering to spots from the DX Cluster?
In addition to the filters which can be defined in Win-EQF*, you can also define "clusterside" filters.
Learn more >>
Can Win-EQF* connect via CC Cluster?
Keywords: VE7CC, CC Cluster, filtering
Win-EQF* can make use the CC Cluster client's excellent capabilities. The CC Cluster client provides a number of easy-to-use DX Cluster-related functions, including easy-to-apply filtering. The CC Cluster client is available for FREE.
Just start the CC Cluster client as normal, then follow these simple (one-time) steps to allow the cluster data to be shared with Win-EQF* or other applications running locally on your PC:
CC Cluster setup:
- Select the Configuration > Ports/Logging Program menu item
- Check the Enable Telnet option
- Check the Use Port 7300 option (or specify a different port, if required)
- If Windows comes up with a security warning, make sure that you check Unblock - otherwise the "local server" won't work
- Select the Setup > Telnet > Direct Internet Telnet (Sites) menu item
- Click the [NEW TELNET SITE] option
- As a new hostname/address, enter 127.0.0.1:7300
(that is: one two seven dot zero dot zero dot one colon seven three zero zero)
- If you assigned a different port number in CC Cluster (i.e. not 7300), make sure that you specify that one instead - just replace the "7300" value with whatever port number you assigned
For later use, make sure that you start the CC Cluster client before starting Win-EQF*.
Technically, it will be the CC Cluster client which connects to the DX Cluster - while Win-EQF* receives data passed from the CC Cluster client (without actually knowing that it's not directly connected to a "real" DX Cluster). Cluster commands issued via the terminal in Win-EQF* will work as usual.
How to create a macro for use in the Win-EQF* terminal window?
Macros for Win-EQF* are just plain text files, named 5.KEY, 6.KEY, etc. based on which function key you hit to run the macro (F5 = 5.KEY, F6 = 6.KEY, etc.)
Create the text file in your Win-EQF* folder using EditPad, Windows Notepad or any other plain text editor.
Will the WKUSB (WinKeyer USB) work with Win-EQF* ?
WKUSB works just as well as the original COM port WinKey with Win-EQF*. Check out K1EL's great keyer products. Access keyer settings for the WinKey keyer with <CTRL-K>.
How can I send CW from Win-EQF* ?
Win-EQF* has a built-in CW memory keyer, with eight memories and a CW keyboard. Win-EQF* can send QSO information from the logging screen directly to the keyer. In order to use the keyer, only a simple interface is required, which uses a single transistor and resistor. Plans for the interface are included with the program. This is the same interface used by popular contest programs like CT and NA. NOTE: this feature is limited to the Win32 platform only. It will not work in Win64 environments.
Win-EQF* can use either a COM or LPT port for the CW interface.
Win-EQF* cannot send CW from its internal keyer to a USB-to-serial-line converter (including "out of the box" solutions such as the microHAM Digi Keyer and the RigExpert TINY - when connected via USB). Win-EQF* uses an IRQ for talking to the COM port for the internal keyer. USB converters do not provide an IRQ (interrupt) for Win-EQF* to use.
If you have a true COM port on your PC you can use it for the internal keyer. If not, you'll have to consider the options below.
Win-EQF* also support the USB MicroHam CW keyer interface, and the K1EL WinKey keyer. The RigExpert PLUS interface also works beautifully. They all work fine via USB ports.
No echo from the WinKey CW keyer when sending CW?
Your WinKey chip needs instructions to echo sent characters back to the client application (Win-EQF*).
Run the wktest utility and check Serial Echo in the ModeReg frame. The wktest utility is available for free from K1EL.com.
Can a serial-line CW keyer and rig control share the same COM port?
Win-EQF* can use the same COM port for the internal CW keyer and the rig interface. It's only when using WinKey for CW that you have to use a separate COM port, since WinKey and the rig control both use the data lines.
You'll find settings for DTR and RTS in the Win-EQF* setup for rig control. These were added so you can turn off the handshaking and use those signals for CW keying or PTT.
Please also see "How do I send CW from Win-EQF*" above.
Sending CW using the RigBlaster PLUS interface
The RigBlaster PLUS interface provides a number of services, including a CW keyer. Win-EQF* supports the WinKeyer feature of the RigBlaster PLUS. When configuring Win-EQF* to work with the RigBlaster PLUS, make sure that you select the COM port for the WinKeyer, not the COM port for the CW via PTT interface which is also provided by the RigBlaster PLUS. The latter one is not supported by Win-EQF*.
How to transfer a Win-EQF v. 1.xx logbook & settings to v. 2.xx ?
Simply use the File > Backup function in your version 1.xx Win-EQF program. Then close Win-EQF v. 1.xx, start the new Win-EQF* v. 2.xx and use the File > Restore menu item. You will be prompted wheter you want to also restore the program settings (answering YES will apply your v. 1.xx program settings to the 2.xx version).
How can I transfer logs from another logging program to Win-EQF* ?
Check to see if your logging program will export the logbook into the ADIF format.
ADIF is a standard and well-documented file format that Win-EQF* will easily import. Once you create an ADIF file, you use the Win-EQF* File > Import/Export log menu, select ADIF Standard as the type to import from, and Win-EQF* as the type to export to.
If you can't create an ADIF file from your logging program, contact LA6VJA and we'll see what we can do.
ADIF export from Win-EQF* - mode translations?
In Win-EQF*, mode description is limited to five characters.
Most ADIF mode descriptors longer than five characters will still be properly output to ADIF format from Win-EQF* when you export. For example, if the mode in Win-EQF* for a QSO is "OLIVI" then when you output to ADIF it will be translated automatically to "OLIVIA". The translation list in the Win-EQF code is updated frequently, though new modes pop up constantly. Please report missing mode translations to the Win-EQF* support forum. The ADIF specification can be found at the ADIF website.
The Logbook of the World (LoTW) from ARRL contains a program called TQSL, freely available from the ARRL website. Using this utility you can convert any five-character mode descriptor in Win-EQF* to the required form for the LoTW. All you have to do is come up with a designator of your choice that you use consistently for a given mode in Win-EQF* and match that up with a translation in the TQSL utility.
In TQSL, select File > Preference > ADIF Modes and define the required translations.
How can I export my Win-EQF* log to Excel?
You cannot export a Win-EQF* log directly into Excel or other spreadsheet software, but you can export to an ASCII (plain text) comma-separated file which in most cases can be imported into Excel / your spreadsheet software.
Use the File > Import/Export log feature, convert from Win-EQF* to ASCII (Commas). Save your exported log with a .CSV extension, then start your spreadsheet software and import the file. This should work fine in most cases!
How can I move SOME OF my QSOs to a new log?
You can create other logbooks from your current logbook using the search feature in Win-EQF*.
Hit <CTRL-F> and then select SEARCH FIELDS FOR PATTERN. When you see the menu selection box for SEARCH RESULTS OUTPUT TO, select LOGBOOK FILE and then type in the name of the logbook you want to create.
You can search for up to four different criteria to match. An easy example is to create a subset of your logbook by searching only for USA states. Select STATES, and when prompted what to search for, enter two question marks "??" so that you will search for all QSOs that have two letters entered in STATE. When the search is finished, you'll have your new logbook with USA states in it. Your original logbook will remain unchanged.
What rigs will work with Win-EQF*, and what good will it do?
Any computer-ready rig that interfaces with the computer's COM port will work with Win-EQF*. Also, most modern radios offering a USB connection (actually a "virtual COM port" provided via the USB interface) will work fine. The setup menu allows you to set the communications parameters to match your rig, on any COM port and using any IRQ. Win-EQF*'s rig interface will work fine with all USB adapaters. A unique configuration file ".RIG" method of specifying rig commands guarantees that Win-EQF* will not be obsolete when new rig models are introduced. A text editor can be used to modify or create new files for new rigs when they hit the market, without requiring modifications to the Win-EQF* program.
Win-EQF* provides automatic update of the frequency and mode display on your computer logging screen as the rig VFO is tuned. Even band plan information can be automatically displayed from the rig's current frequency. You can type frequency or mode into your log and the rig will respond. And, with a TNC in use on the PacketCluster(tm), Win-EQF* can set your rig to the frequency for the selected DX spot.
Will Win-EQF* work with my FlexRadio SDR?
Please see this brief guide [PDF, 400 kB] on how to set up PowerSDR and Win-EQF* to work together.
How to use more than two rigs with Win-EQF* ?
The RigSet utility will be of assistance - it is available for download right here.
RigSet works by letting you build a database of rigs that you want to have configured to use with Win-EQF*. You can create an icon on your desktop to invoke RigSet. Then when you invoke RigSet you are given the opportunity to define the setups for additional rigs and to change the rigs that are defined in Win-EQF.INI, the file Win-EQF* uses to store such information. By doing the rig definitions ahead of time in RigSet you only need to select the two rigs you want to have currently active in Win-EQF*; and when you exit from RigSet, Win-EQF* is started for you with those two rigs available.
Please note: Win-EQF* has a maximum of two rigs defined at any time. RigSet makes it easy to quickly switch which two rigs are currently defined in Win-EQF*.
How to connect my rig to the PC and use it with Win-EQF* ?
Simple question, tricky answer. It all depends on your rig, your PC and the interface provided by the rig vendor.
Your primary source of information should be the documentation provided with your radio. May we also suggest some Google searches?
You may need a null-modem cable/adapter, a simple serial cable or possibly a USB cable depending on your setup.
Set the RIG parameters in Win-EQF* according to those used by your radio (in general, try 8 data bits, 1 stop bit and parity N - though some experimentation is required at times). It's crucial that the baud rate as specified in Win-EQF* matches the one of your rig. Some rigs even offer user-selectable baud rates.
There are also third-party interface units, such as the microHAM Digi Keyer II, that work perfectly with Win-EQF* and provide an all-in-one solution for rig control, digital modes and CW.
Connecting to a rig via HRD is a special case.
What's a COM port?
A COM port - or a serial port - is a serial communication interface which enables data transfer to and from your computer.
The serial port is a common interface used for data exchange between your PC and various equipment in your shack (rig, TNC, rotor, antenna switch, CW keyer, ... you name it). Unfortunately, most PCs don't come with on-board serial ports anymore. Fortunately, USB-to-COM adapters are widely available, and modern radios even come with USB interfaces providing virtual COM ports).
Related Wikipedia article: http://en.wikipedia.org/wiki/Serial_port
What's the least expensive way to interface my Icom to Win-EQF* ?
Try the RS-232/TTL interface by KG7SG, as described in QST 7/1992. There are also numerous other implementations around.
New Icom rigs even come with a USB interface, providing a virtual COM port for CAT/rig control. You may have to purchase a separate USB cable, though.
Win-EQF* won't connect to my IC-9100
The Icom IC-9100 comes with two "virtual COM ports" provided via the USB interface. Make sure that you use the one named "USB1" for CI-V data. Please refer to the IC-9100 user's manual for details.
Win-EQF* won't connect to my Kenwood TS-590
First, make sure that your Kenwood is properly hooked up to your computer using either a USB cable or a straight-through serial cable. If you are able to communicate with your rig using Kenwood's ARCP-590 software, you're probably very close to having Win-EQF* work with this fine rig. Please note that the ARCP-590 software (or any other rig control software) cannot communicate with the TS-590 at the same time as Win-EQF*.
For information on how to connect your Kenwood TS-590 to your PC, refer to the user's manual or G3NRW's excellent TS-590 page.
Confirm/apply these settings:
In the TS-590
- MENU #62 USB PORT BAUDRATE = 115200
- Setup > Rig
- BAUD 115200
- 8 DATA BITS
- 1 STOP BIT
- NO PARITY
- DTR OFF
- RTS ON (seems to be required to READ FROM the radio, reason unknown)
In the Windows Control Panel
Confirm sensible settings for the Silicon Labs CP210x USB to UART Bridge, which will be the device reported by the Windows Device Manager.
Based on Windows XP:
- Select Start > Settings > Control Panel > System > Hardware > Device manager
- Expand the Ports (COM & LPT) item
- Right-click on the Silicon Labs CP210x USB to UART Bridge, then select Properties
- Port settings should read 115200, 8, N, 1, Flow control = NONE
- Click on the OK buttons and close the control panel
Other Windows versions are similar, if not completely identical.
Win-EQF* won't connect to my rig
Please verify that Win-EQF* is in AUTOMATIC LOGGING mode. Shortcut key is <CTRL-A>.
How to have Win-EQF* and HRD connect to the same rig?
Although Win-EQF* doesn't officially support HRD (Ham Radio Deluxe), there are reports that Win-EQF* and HRD can co-exist and even access rig data simultaneously.
- HRD operational and configured for rig control.
- Win-EQF* being configured to access a generic Kenwood radio - use KENWOOD.RIG (no matter what your actual rig is).
Behind the scenes, HRD uses the Kenwood protocol to send/receive rig data through vCom to other applications. "Other applications" includes Win-EQF*. Win-EQF* sends Kenwood data back through vCom, to HRD, which converts it to whatever format necessary.
Refer to the third-party section of the HRD's user guide for further details.
How do I submit QSOs for Logbook of the World using Win-EQF* ?
- Use the SEARCH feature by hitting <CTRL-F>. If you are going to submit only a portion of your logbook to LoTW, you may select either the Search only BETWEEN two DATES or Search BETWEEN QSO NUMBERS item and fill in either the dates or QSO numbers when prompted.
- Select the SEARCH FIELDS FOR PATTERN menu item and hit the ENTER key or double-click the mouse.
- On the menu for SEARCH results output to, select item 6 for ADIF File / LoTW.
- On the Search for menu, select the desired search criteria. For most cases, you would select CALLSIGN as the only search criteria, and search for an asterisk (*) in the callsign field. This finds all callsigns in the logbook, and if you chose a date or QSO number limit earlier, only callsigns for QSOs within the specified range will be found.
- When the search is finished, Win-EQF* will ask you whether you want to sign the ADIF file and upload the resulting TQ8 file to the LoTW.
If you decide to sign and upload the resulting TQ8 file, the LoTWUploader helper application will be started. The user's manual contains further details regarding the LoTWUploader.
If you don't want to sign and upload the ADIF file to the LoTW, Win-EQF* will simply open the ADIF file in your text editor. The ADIF file will be named SearchResults_YYYYMMDD_hhmmss.ADI (YYYYMMDD_hhmmss representing the date & time when the ADIF file was created). You may rename it as desired.
How to import LoTW QSL status into Win-EQF* ?
When a downloaded LoTW logbook (ADIF file) is merged with an existing Win-EQF* logbook, dupe QSOs will be eliminated and the "highest" QSL and LoTW status between the two dupe QSOs will be preserved. No data will be lost, but to be on the safe side: always make a backup copy of your logbook before importing/merging log files.
- Download the ADIF file with your QSO data from the LoTW. When downloading, be sure to check the "INCLUDE QSL detail" from the LoTW.
- Store the LoTW ADIF file in a location which you can reach from within Win-EQF*.
- Then, in Win-EQF* :
- Click on File
- Click on Import
- Click on ADIF standard file and give it the path and name for the file you downloaded from the LoTW
- Click on Win-EQF* as target file type and give it the name of the .LOG file you want to import this data to
- Choose append (or replace, if you want to start a new log file)
- F1 to begin conversion
- Hit enter after prompt "enter optional data"
- Hit enter after "make notepads"
- Click on OK to import all QSOs when prompted for "QSO numbers to convert"
- When prompted for the operator callsign, make sure that it matches the one already in your Win-EQF* logbook. This is essential if you're importing LoTW QSO data and want to update the LoTW sent/received status for existing QSOs in your log.
Win-EQF* will do the conversion and add the new QSOs to the specified .LOG file. You then hit ESC to return to Win-EQF*.
This seems like a lot of steps but Win-EQF* is leading you and you can do it in less than 20 seconds.
As always, it's easy to experiment and yet keep your logbook safe with Win-EQF*. Before you try the LoTW import, make a backup of your current log selecting File > Backup logbook. IF something goes wrong, you can simply restore the log and be right back where you started.
What's the LoTWUploader?
Introduced in Win-EQF* version 2.22, the LoTWUploader is a helper application which will take care of the somewhat tedious process of interacting with the TQSL program. It will also upload the signed TQ8 files to the LoTW server. From version 2.31 it also offers uploads to HamQTH.com and ClubLog.
It is required that you first download and install the TrustedQSL software suite from the ARRL website and acquire one or more certificates to sign your ADIF files before submitting them to the LoTW.
The LoTWUploader can upload TQ8 files to the LoTW server using a secure web page (HTTPS) or via email. Both options require some initial setup and the LoTWUploader will prompt you for a few required details. If you later need to re-configure the LoTWUploader, simply select File > Forget LoTW username/password & settings and then sign an ADIF file - you'll be asked to provide the required details again.
If the resulting TQ8 (or ADIF) filesize exceeds 2 MB, you'll receive a warning that the file may be too large. If the upload fails, try creating two smaller ADIF files (re-do the search and filter by QSO numbers) and sign/upload the two files separately. As a rule of thumb, 10,000 QSOs will normally fit into approximately 1.65 MB when converted to the TQ8 format.
Known ClubLog and HamQTH.com issues
- Max upload size is 10 MB.
- Uploads are not cumulative; each upload totally overwrites the previous one.
- From the upload has completed until the file shows up in the "processed" list, there's a delay depending on the current server load.
- From the upload has completed until the file shows up in the "processed" list, there's a delay of approximately 10 minutes.
How does Win-EQF* interact with eQSL?
There's no entry for eQSL, just QSL SENT or RCVD, which is used also your normal paper QSLs.
BTW, there are separate fields for LoTW Sent and Rcvd, but nothing for eQSL.
When will support for HRDlog.net be available?
Once their documentation is properly in place, support may be added for the HRDlog.net service.
How to enter satellite QSO data?
QSO information for a satellite QSO should include:
FREQUENCY = 145.8 (uplink frequency to transmit to satellite)
MODE = SAT (This is REQUIRED for Win-EQF* to know it's a satellite QSO)
TRACK = AO-27 FM (Always satellite name then a space and transmission mode)
The above refers to the Win-EQF* logging screen info that must be entered, so that the ADIF export works correctly.
Why is the Win-EQF* CONTEST multiplier scoring not correct for some contests?
For contest scoring, Win-EQF* (since it is more general-purpose oriented than for contest use) does have some shortcomings. The good news is that for most contests that accept Cabrillo entries, the scoring is handled by the contest sponsor by reading the Cabrillo file electronically and calculating the score using their rules. As long as the complete exchange appears in the Cabrillo log, your score will end up correct when the contest sponsor reads the file. The score you indicate in the Win-EQF* Cabrillo file usually isn't used for anything, but you may calculate it manually and enter the score there if you like.
How to send contest serial number exchange in WPX-CW?
First be sure you have Win-EQF* set up for the contest, since each contest keeps the setup for the CW memories separate.
- Hit <CTRL-K> to access the CW keyer menu (or use the menu Operation, CW Keyer item).
- Hit F10 to record a CW memory.
- Hit a number key (1 thru 8) to decide which memory number to record.
- Type in the exchange you want to send, including the "%N" to send the serial number.
- Hit the Enter key to save the CW memory.
Here is an example of the keyer memory: %C TU %S %N K
This would send an exchange such as "W6BSY TU 599 FL 002 K".
Assuming that your PC has a separate keypad for numbers, the numeric keys are the easy way to send your CW memories while on the logging screen. This is true for contest or casual operating.
Just make sure that your NUM LOCK is turned on at your keyboard. Also, check the Setup menu, Options, Numeric Keypad (Keyers). Select the Keyer Memories option there.
To send from memory #1 while logging, just hit the "1" number key on the numeric keypad. Also, you can hit the big "0" number key while logging to type in text to be sent to the morse keyer, without going to the keyer screen.
I haven't received a registration code?
If you haven't placed an order for and paid for Win-EQF* version 2, you won't receive a registration code. Nothing comes for free.
For program version 3.xx, you'll no longer need a registration code - meaning that you won't get one.
How can I transfer Win-EQF* to a new computer?
Follow these easy steps to move Win-EQF* to your new computer:
- Backup your log files (File > Backup logbook)
- Install Win-EQF* after downloading the FULL PROGRAM from www.win-eqf.com
- Restore your log files (File > Restore logbook)
Does Win-EQF* require an online license activation?
Win-EQF* only interacts with the callbook servers you choose and a telnet DX cluster of your choice. Your callsign/user ID is only used for logging in to these sites.
How do I make the Win-EQF* window larger?
Keywords: screen size, window size, font size, font, maximize window
The size of the Win-EQF* window changes depending on what screen font is used. To use the maximum screen font available, run the Win-EQF MAX.EXE file (won't work on small laptop displays). Please note that there is no way to run Win-EQF* in a TRUE full-screen mode. This is a Windows/operating system limitation, applying to Windows versions 2000 and beyond.
In Windows NT/2000/XP/Vista/7, the Win-EQF* properties can be set by changing the settings on the shortcut to Win-EQF*. The Windows 9x/ME platforms are no longer supported.
Right-click on the Win-EQF* or Win-EQF* CONTEST shortcut, then select the Properties menu, and select the Font tab. Towards the center of the Font dialog window, there will be a place to select the font to use, and whether to use a bold font.
Typically there will be just a couple of fonts to pick from - hopefully at least two so you have some choices.
Pick a font, then from the size selection box, click on various sizes while observing the window preview display just left of it. The window preview shows the size of the Win-EQF* window in comparison to the desktop size. Pick a font size that gives you a large enough Win-EQF* window, but not too large or scroll bars will appear on the window frame.
Win-EQF* will not work properly if the window size is so large that scroll bars appear. Once you've made your selections, click on Apply and OK buttons, and start Win-EQF*.
Regarding console fonts, there is only a limited font selection available. Read this article for further information.
Download K1XN's step-by-step guide [PDF, 63 kB]. Please also refer to the Win-EQF* user's manual, "advanced topics".
How to ignore a QSO when doing award updates?
Simply put a "-" (hyphen or minus sign) in the log for that QSO in the QSL SENT field, the QSO will then be ignored for DXCC, VUCC and other awards updates. Suitable if you work a maritime mobile station (/MM) which would not count towards the DXCC award (etc.).
Where can I find the Win-EQF* user's manual?
You'll find the user's manual in the Win-EQF* program group. Just how you navigate to the program group depends somewhat on your Windows version and your Windows settings, but in general you'll find it by means of clicking...
- The Windows START button (normaly in the lower-left corner of the screen)
- (Possibly the ALL PROGRAMS menu item)
- Win-EQF user's manual
Again, the exact "path" cannot be determined due to the many Windows flavours out there, combined with differing user settings. In the worst case, if you can't locate anything at all - use the Windows search function and search for a file named Win-EQF.PDF.
Which mode designators are recognized?
Win-EQF* will recognize these mode designators.
Can Win-EQF* sort my outgoing QSL cards?
Not your cards, but the printing order of your QSL labels can certainly be arranged alphabetically.
- Operation > Sort Logbook > CALLSIGN.
- File > Print > Print QSL Labels > Print QSOs with P in QSL SENT (typically).
Your labels will be printed in the same order as they appear in your logbook (according to your choice in step 1 - sorting). If a QSL MANAGER callsign has been entered, it will not affect the sorting and the card has to be put into the correct sequence manually.
If you'd like to detail your equipment on the labels, just specify it in your QSL Comment Line:
Print > Label Options > QSL Comment Line - Enter one time only. Feel free to include any macros (refer to the user's manual for details).
Also keep in mind that you can make extracts from your log with the Operation > Search Logbook feature. Let's say that on 30m you're using a dipole antenna and on 20m you're set up with a 5-el. Yagi - then you'll make one logbook extract for 30m and one for 20m.
Having loaded the 30m log, you print your QSL labels with a comment line detailing your dipole antenna. Loading the 20m log, you update the comment line with details on your Yagi and print your QSL labels for that band.
Try experimenting with your log - with a little practice you'll find that you can manipulate your log data easily and tailor your extracts to your specific needs. As always, make backups of your main log(s), preferably to external media, before experimenting.
Also, make sure that you have checked out the advantages of using a dedicated label printer. Details regarding dedicated label printers can be found in the user's manual.
What's a master log, as defined by Win-EQF* ?
If a master log is selected in Win-EQF* (Setup > Callsign Database > Master Log Lookup) and a logbook called MASTER.LOG is present in the \LOGS folder, Win-EQF* will check the MASTER.LOG for any previous QSOs prior to checking any other installed callsign databases.
If all your QSOs happen to be in your main logbook, you really don't need the master log feature, but if you have your contacts spread over several logbooks it may be useful.
Most users, though, will probably prefer to keep all their QSOs in one single logbook.
Does Win-EQF* interface with GlobalQSL?
ADIF files generated by Win-EQF* have been used with GlobalQSL without problems of any kind.
Can I change the contents of the bandplan files?
Yes, please feel free to do so.
Win-EQF* v. 2 onwards includes a README.TXT file in the BANDPLANS subfolder, which details the layout of the .BPL files as well as a few other important items to keep in mind.
Bandplan files which you believe to be of interest to other users, are most welcome to firstname.lastname@example.org.
What happened to the "window close" button?
The upper-right-hand "window close" (X) button has been disabled as of version 2.
Please select File > Exit (or <ALT-F>, X) instead. This ensures a graceful exit from Win-EQF*, ensuring that all files are closed, buffers properly flushed, etc.
Customized label settings ... gone ?!?
If you have modified the custom label setup file (DDOCML.INI), please be adviced that new patches to Win-EQF* will overwrite your own custom file.
You'll need to keep a copy of the DDOCML.INI file separate so you can restore it to your Win-EQF* folder after installing the patch. Note: Win-EQF* will automatically include the DDOCML.INI in the backup archive (ZIP file) when you select File > Backup from the menu.
How to print labels using a dot-matrix printer?
Keywords: sprocket-fed labels, dot-matrix printer, Windows printer driver, form-feed, form feed, blank page
Win-EQF* still supports printing QSL/SWL/address labels onto "old-style" sprocket-fed labels using dot-matrix printers (using label definition no. 1 or 2 from the File > Print > Label Setup (Size) menu in Win-EQF*).
Thanks to the Windows printer drivers, however, there is often an extra form feed command issued after each label, resulting in a number of blank labels being fed through the printer. This problem has its roots outside Win-EQF* and can only be addressed by modifying the properties of the printer driver (model-specific printer driver - or the Generic Text printer driver).
A proven procedure to get rid of the unwanted form feed command - tested in Windows XP:
- Select Start > Settings > Printers and Faxes
- Select the File > Server Properties menu item
- Check the Create a new form option
- Enter an appropriate name in the Form name field, such as MyLabel (which will be used in this example)
- Set the Height of the new label to an appropriate value (e.g. 0,9375 in)
- Click the Save form button followed by the Close button
- Right-click on the printer you intend to use for label printing and select Properties, then --
- Set the General > Printing Preferences > Advanced > Paper size to MyLabel (or whatever you named your new label definition)
- Set the Advanced > Printing Defaults > Paper/Quality > Paper Source to Cont. Feed - No Break
- Set the General > Printing Preferences > Paper/Quality > Paper Source to Cont. Feed - No Break
- Click OK, OK and then close the Printers and Faxes window
Labels will now be printed without a form feed command being issued after each label.
Can Win-EQF* print QSO data directly on QSL cards?
Not as of today. You might be able to define your own label format and make Win-EQF* believe you're printing labels when you're actually printing directly on cards.
There is also a utility called QSLMaker by WB8RCR which interfaces with Win-EQF*. You can design your own QSL card with QSLMaker and then import the log data from Win-EQF* for printing.
What label printer do you recommend for use with Win-EQF* ?
The Brother QL-570 is known to produce very nice results and is fully supported by Win-EQF*.
For large-quantity label printing, using Avery label sheets fed into your ordinary laser or ink-jet printer will probably be the best option.
Printing QSL labels with a Dymo label printer
Although Win-EQF* doesn't natively support the Dymo label printer, N9EF has provided this excellent guide to printing QSL labels using the Dymo:
- Select the Avery 4010 label format (File > Print > Label Setup (size) )
- Select to print using the landscape format (from the print dialog)
Is there a way to turn off DUPE CHECKING?
How do I turn SCROLL LOCK on and off?
SCROLL LOCK is a key on your keyboard, a leftover from the good old days. Win-EQF* uses the SCROLL LOCK key to turn dupe/previous QSO checking on/off.
Look for a key called SCROLL LOCK, SCRLCK, SCRLK, SCRL or SCR. On some laptops with reduced-size keyboards, you may have to hold down a function (Fn) key to access the underlying SCROLL LOCK of a dual-function key.
If you can't find the SCROLL LOCK key on your keyboard, don't worry too much. Starting with version 2.13 of Win-EQF*, <CTRL-J> will do the same job.
How can I add the HAM FONT to Win-EQF* ?
The process for adding fonts to Win-EQF* is quite simple:
- The font you want to install into Win-EQF* has to be installed on your PC.
- In Win-EQF*, select File > Print > Font > New Font.
- Click OK.
- You'll now see a list of all your fonts.
- Select the font to add.
- Click OK.
Experience has shown that the standard Windows font called Monitor is well suited for label printing. The HAM FONT is also preferred by a number of users.
I'm only getting partial data from QRZ.com when doing a database lookup!
If you're a registered user with QRZ.com but not getting the full data from QRZ.com into Win-EQF* when doing a database lookup, chances are that your subscription to QRZ.com has expired. An expired subscription returns only the operator's name from the database lookup.
Please note that if you renew your subscription with QRZ.com, it might take some time until your full privileges are restored.
What's the THOMSON10kW doing in my Win-EQF* TRACK field?
It's there as an example. Some users rename the TRACK field to RIG, for the purpose of identifying which rig they were using during the QSO.
To change the default values of a number of logbook fields:
Setup > Options > Default Reports and Values.
To change the names of custom logbook fields:
Setup > Options > Custom Log Fields.
The Thomson10kW transmitter is described here, by the way.
What is OPERATOR: MY1CALL ?
The OPERATOR: MY1CALL is shown in the lower-left corner of the Win-EQF* program window. It has nothing to do with who is the registered user of the Win-EQF* software, rather it is used to determine "the callsign used" for a particular QSO. Multiple operator callsigns can be defined, just left-click on the OPERATOR text and you will be able to define or select your operator callsign.
The MY1CALL callsign is provided as a default value only, and it should be changed before you log your first QSO. If you have already logged a handful of QSOs as MY1CALL, don't worry - the search/replace function is there to assist you. Simply press <CTRL-F> and perform a search/replace operation, searching for MY1CALL as operator and replacing it with your proper callsign.
How to automatically make backup copies of my logs?
A suggestion is offered here, providing an almost ready-to-run example which will automatically create backup copies of your Win-EQF* logbook files.
What's a QTH locator?
Keywords: grid locator, QTH locator, maidenhead locator, location
We'll leave it to external resources to explain this one:
Where are my log files stored?
Keywords: Windows VISTA, Windows 7, backup, restore, UAC, Virtual Store
I have copied my log files from my old computer to my new computer, into the Win-EQF* subfolder called .\LOGS. Still I can't locate them from within Win-EQF* using my new Windows VISTA/7 computer. Why?
Thanks to a new security feature included in Windows VISTA and Windows 7, the Win-EQF* subfolders are placed in the Windows Virtual Store. Win-EQF* knows nothing about this process, which is entirely controlled by the operating system. To learn more about the virtual store, follow the links below.
The easy solution, though, is to perform a BACKUP operation from your old system (using Win-EQF's File > Backup menu), backing up EACH log file and associated awards, etc. onto a USB memory stick, floppy disk or whatever media you prefer. Then perform a RESTORE operation (using Win-EQF's File > Restore menu) on the computer you want to move your logs to. Virtual store or not, your log files will be there if you follow this simple procedure.
Submitting a log file to LA6VJA
To aid in problem tracking, LA6VJA will sometimes ask for a copy of your logbook file(s).
Please submit a copy of your logbook file(s) only after requested to do so - following the procedure laid out below:
In order for the log file(s) to arrive safely, without email clients or MTAs interfering with the structure of the logbook files (the log files used by Win-EQF* must adhere to a very strict format, otherwise they'll show up garbled after being emailed) - please use the File > Backup logbook function in Win-EQF* to produce a ZIP archive, then email the resulting ZIP archive to email@example.com.
Also - an important note about privacy and user data:
- All files submitted are virus scanned before they are opened.
- NO SUBMITTED FILES are EVER shared with other Win-EQF* users, beta testers, etc.
- All received files are DELETED after use. Once the problem has been identified/data converted, etc. - LA6VJA will delete all received data.
- The ZIP arhives created with the File > Backup logbook function ALSO contains various .INI files (Win-EQF* program settings) which in turn MAY contain data you don't want to share (such as a scrambled version of your QRZ.com username/password). Rest assured, any ZIP files and their contents are deleted as soon as I don't need them anymore. Also, if the INI files are not relevant to the problem at hand, feel free to manually delete them from the ZIP archive before emailing the ZIP file to LA6VJA. Very often, only the embedded .LOG and .NOT files are of interest.
How to run Win-EQF* with administrator privileges
Running Win-EQF* with full administrator privileges shouldn't be required for day-to-day use, but if desired, this Microsoft TechNet article describes how it can be achieved.
DYNAZIP error message
If you encounter the "insert the last disk of the backup set" message during a log RESTORE operation, this is probably a result of interference from a different DYNAZIP library than the one provided with Win-EQF*.
Two cures are known for this issue, which seems to occur only when attempting to RESTORE a logbook from a USB memory stick:
- Manually copy the logbook archive (.ZIP file) to the hard drive and then restore the logbook from that location.
- Uninstall the third-party application called BACKUPMAKER.
QSO DATA INTERFACE (MixW interface)
The QSO Data interface is available in Win-EQF* program versions >= 2.20. It has been tested with MixW versions 2.18, 2.19, 2.20 and 3.01b. Please refer to the user's manual for further details.
NOTE: the Win-EQF* and MixW log files are NOT compatible (...and never intended to be!)
Mode translations - MixW QSO Data interface
Using the QSO Data interface provided with Win-EQF*, QSOs from the MixW operating/logging screen can be added directly to your Win-EQF* logbook.
A number of digital modes have names/designators exceeding the capacity of the five-character mode field in Win-EQF*. As such, the QSO Data interface provides a "mode translation" mechanism based on key/value-pairs specified in the MixWInterface.INI configuration file. The file resides in the Win-EQF* program folder and can be edited with any text editor (such as Notepad).
Locate the [MODETRANSLATIONS] section in the MixWInterface.INI file and edit/add the entries according to your preference. The file format is rather straightforward, namely MixWMode=Win-EQFMode, as shown in the example below:
Where no mode translations are specified, the QSO Data interface will simply return the leftmost five characters of the MixW mode designator.
Starting/stopping the QSO Data interface
The correct sequences for starting/stopping the QSO Data interface - in order to avoid possible problems occuring when different applications compete for access to the COM port(s) for CAT/rig control, PTT control, CW operation, etc.
Starting the QSO Data interface and connecting to MixW:
- Start Win-EQF*
- Hit <CTRL-I> in Win-EQF*
- Start MixW
- Click Connect to MixW in the QSO Data interface application
Stopping the QSO Data interface and reverting to normal operation:
- Quit MixW
- Quit the QSO Data interface application
- Return to Win-EQF* and hit <ESC> to exit interface mode
Keyboard shortcut for starting MixW
In most Windows versions, you can easily add keyboard shortcut keys to your favourite programs. Just right-click on the program shortcut of your choice, select Properties and then apply an appropriate key combination of <CTRL>-<SHIFT>-something. Voila - you can now start your favourite program from just about anywhere in Windows, without having to fuzz around with the mouse.
My QSO wasn't imported into Win-EQF* !
The MixW DDE server is somewhat ineffective when it comes to propagating relevant values via DDE. It seems to be necessary to move out of the data-entry fields by means of clicking on another field in the MixW logging form. Also, some values may "hang on" for a while after saving a QSO. As of Win-EQF* version 2.20, the locator field will not be imported due to shortcomings in the MixW DDE server.
You can monitor what data has been made available from MixW by watching the QSO Data interface, which will display the values currently being reported by MixW.
If Win-EQF* has insufficient data to process a QSO when it is saved in MixW, the QSO will not be imported into the logbook.
Norton/McAfee/etc. lists the win-eqf.com website as malicious (virus/trojan/malware, etc.)
Keywords: virus warning, trojan warning, malware warning
False positives. Please note that www.win-eqf.com redirects to a sub-site on the bitwrap.no server. This behavior is intentional and correct.
Users are encouraged to take the appropriate action with their software vendors.
The same problem applies to the Win-EQF* install files, available from the above website. Antivirus software may for unknown reasons claim that the installer files contain a virus. There is no known workaround except temporarily deactivating the antivirus software.
Please also refer to: nsis.sourceforge.net/NSIS_False_Positives
Problems with Win-EQF* keyboard shortcuts
Before reporting any keyboard issues, please read this document (PDF, 230kB).
Keywords: keyboard, non-US, keyboard layout, shortcut keys.
Why does Win-EQF* calculate incorrect beam heading and GC distance?
When used with callbook CDs or internet callbook servers, many of the Win-EQF* logging fields are auto-populated with data from the callbook.
Some of the callbook providers do not indicate missing (NULL) values in a proper way. For instance, one callbook reports any station with unknown latitude/longitude to be located in grid square JJ00aa (0 degrees E/W, 0 degrees N/S).
Win-EQF* will always try to calculate the most accurate GC path possible. If a grid square is returned by the callbook, Win-EQF* will calculate the GC path to the center of that grid square. If no grid square is returned by the callbook or if Win-EQF* is not used with a callbook at all, Win-EQF* will use its own PREFIX.LIB and STATES.LIB to determine the approximate location of the remote station. The calculation may appear wrong, but only because the result is based on inaccurate/"best guess" location data.
I'm getting the "Could not open TVICH32 driver 0" error message. What to do?
This driver will only be launched by Win-EQF* if your setup configuration specifies that you are using a COM or LPT port for the CW, voice keyer or antenna switch interfaces. You need to turn all of these features off.
The easiest way to start over so that Win-EQF* is not using any wrong settings is to delete the "Configuration Settings" file in your Win-EQF* folder. Quit Win-EQF*, then open the ..\Win-EQF folder (normally located in C:\Win-EQF2 unless you changed it from the default location during the installation of Win-EQF*) using Windows Explorer > My Computer > [navigate to your Win-EQF* folder] and delete the file Win-EQF.INI.
When restarting Win-EQF*, you will have to reconfigure Win-EQF* via the Setup menu.
Please note that the WinKey CW keyer is not controlled via the TVICH32 driver.
I get an INITIALIZATION ERROR when running DX Atlas from Win-EQF* !
On Windows Vista and Windows 7, you'll get an INITIALIZATION ERROR when invoking DX Atlas from within Win-EQF* - unless DX Atlas is already running.
Please follow these easy steps to rectify the problem:
- Quit Win-EQF* and DX Atlas.
- Using Windows Explorer, navigate to your DX Atlas folder (normally C:\Program Files\Afreet\DX Atlas).
- Right-click on DXAtlas.EXE and select Run as administrator (acknowledge the Windows security warning).
- Quit DX Atlas.
- Using Windows Explorer, navigate to your Win-EQF* folder (normally C:\Program Files\Win-EQF).
- Right-click on Win-EQF.EXE and select Run as administrator (acknowledge the Windows security warning).
- Quit Win-EQF*.
- Start Win-EQF* by normal means.
Win-EQF* is not the cause of the problem. There seems to be an issue with Windows Vista / Windows 7 and the new security regime introduced in these systems. Reports are that also other third-party applications which invoke DX Atlas are running into the same problem.
The maximize feature won't maximize the Win-EQF* window!
Win-EQF* is a Windows console application, and Microsoft does not support the maximize button or window-resizing for console applications for Windows NT, 2000, or later versions.
This feature was lost when the Windows core was rewritten as a 32-bit operating system.
My mouse doesn't work properly in Win-EQF* !
Check the properties of your desktop shortcut to Win-EQF*.
Under Options, turn OFF the option for Quick Edit. This will allow the mouse clicks to select fields and restore normal mouse operation for a lot of other Win-EQF* features.
A number of <ALT-> key combinations don't work!
Keywords: <ALT-B>, <ALT-D>, <ALT-G>, <ALT-M>, <ALT-P>, <ALT-Q>, <ALT-R>, <ALT-W>, <ALT-Z>, Google Maps, QRZ.com, hamcall.net, Buckmaster, HamQTH.com, DX Atlas, DXAtlas, HamCAP, VOACAP, APRS
The new version 2 features which require access to your web browser will in a number of circumstances not work if you have selected Google Chrome as your default web browser.
At present there is no known work-around except selecting Mozilla Firefox or Internet Explorer as the default web browser. Other browsers may also work, but have not been tested.
There is also a known issue regarding non-standard keyboards - read more here.
The function keys (F1, F2, etc.) don't work properly in Win-EQF*
Keywords: function keys, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, Fn
Some systems come with 3rd-party/OEM add-ons which alter the expected behavior for the function keys. For example, one vendor has decided to adapt the "Apple style" keyboard functions, using the F1/F2 keys to adjust screen brightness. This issue can normally be overcome by pressing Fn and the desired function key, e.g. Fn+F1 to achieve the normal behavior of the F1 key.
Further support for this issue is out of scope for Win-EQF* support. As a general suggestion, it's a wise idea to avoid any 3rd-party/OEM add-ons which alter basic system functionality.
Win-EQF* locks up. Why?
It normally shouldn't.
Check that you're not running third-party applications such as Zone Alarm, Spy Doctor, Norton Internet Security and the likes. These applications are known to cause instability issues in Win-EQF*, slow down your system and in general bother you with a number of nuisance "warnings".
Why does Win-EQF* report the wrong location on Google Maps?
The location data is based on the PREFIX.LIB or STATES.LIB default locations. Only if you enter a grid square will the location in Google Maps and/or DX Atlas be accurate. Further details are available here.
Where can I download the registered version of Win-EQF v. 1.94S?
After February 28, 2011 - you can't.
We've arrived at this decision after having received numerous support and download requests related to Win-EQF v. 1.94S. This simply takes up too much of our time, time we'd rather spend supporting and developing Win-EQF* v. 2.
Where can I find the Win-EQF* support forum?
It can be found on Google Groups, right here:
Posting messages is available to members only. Membership is open to anyone with interest in Win-EQF* and/or Win-EQF/Log-EQF. Apply here and make sure you include your callsign in the nickname request.
How to report a problem?
- Ensure that you're running the newest version of Win-EQF*.
If the problem persists:
- First, check the Win-EQF* user's manual for a possible solution. The user's manual is included with Win-EQF*, residing in the WIN-EQF.PDF file.
- Second, check the Win-EQF* online FAQ for a possible solution.
- Third, check the Win-EQF* Google Group / online support forum for a possible solution. Feel free to post your "how do I ..." (etc.) questions in the online support forum.
Why a support forum on Google Groups?
Having Google Groups handle the behind-the-scenes keeping of members, messages, etc. allows LA6VJA to concentrate on program development and tech support instead of keeping a web-based discussion board up running 24x7.
What happened to Win-EQF by N3EQF?
On November 27, 2009, this notice appeared on Tom's web site - quoting:
Win-EQF - Going QRT After 20 Years
There aren't many ham radio programs that have lasted for more than 20 years, like Log-EQF. It has been a labor of love for most of that time, but sadly it's time to move on and let younger programmers fill the void.
There will be no further sales of Win-EQF "Log-EQF for Windows" after December 31, 2009. I will continue to provide technical support for at least one year after that, but there will be limited updates to the program.
I'm sorry if this decision disappoints some of you, but the constant work involved in supporting a Windows program for ham radio has become too time-intensive. The advent of Windows 7 was probably the last straw, on top of the never-ending changes required to accommodate new rigs, rotors, keyers, clusters, modes, contests, awards, callsign databases, etc.
I want to thank all of my loyal users for the many years of support. It's been a real pleasure meeting some of you at hamfests and club meetings. Some of those eyeball QSOs have turned into lasting friendships. In particular, many thanks to John Shelton, K1XN, for his help in recent years to keep Win-EQF in distribution and the the DXCC prefix list up-to-date.
On July 5, 2010, Tom generously donated the Win-EQF v. 1.94S source code to LA6VJA. Win-EQF will live and prosper with a new product name - Win-EQF*.
As of December 1, 2014, commercial development of Win-EQF* has been terminated. Win-EQF* version 3.00 was released on December 28, 2014 - and the program lives on as DONATIONWARE.
The DONATIONWARE concept failed miserably and the download count for version 3.00 remains very low. As of February, 2015 the decision was made to let Win-EQF* go QRT, as a consequence of too much time being spent handling support and feature requests along with no interest in the donationware concept. Further investment of time and labor cannot be justified at the expense of family, friends and chores. 73 and GL to all.