This is really just to test that our new mailing list is working properly. Dave AA6YQ and I have had quite a few discussions via private e-mail regarding various facets of DXLab. I can tell you first

Ron PA1ZX DXForecast http://members1.chello.nl/~r.a.f.eberson/DXF

Dave, Take a look at the following link http://www.ea4tx.com/index_en.htm which is some developers information on the rotor control that Ron asked about. From what I can gather it is not an RS232 inte

Dave, I have been trying the new capture window and like it very much. This morning, I got the run time error from CI-V commander without WinWarbler running. What I had open was CI-V commander, DXKeep

I've added additional error trapping to this version -- hopefully the runtime error 6 crash W3ZJ's been experiencing will be replaced by an entry in the error log that helps me track down the root cau

Our man Kurt, OE1002419, noticed that both the FR and LZ callbook URLs had changed, tracked down the new URLs, and sent them my way. So we have him to thank for the updated Pathfinder searches now ava

The primary purpose of this release is to correct the defect in Hygain DCU rotator support reported by Julio below. I learned from Ed at DataMatrix (the developers of ProLog) that the "set bearing" an

Dave, When I click on a callsign in DXKeeper, obviously I have worked the guy, but the progress window does not always indicate any contact with his country. Also, I have worked 3G0Y 8 times on 80,30,

Along with the DXCC database support described below, this release also includes updated online help, which is accessible via http://www.qsl.net/dxkeeper/Help/index.htm . If you've installed DXKeeper

DXKeeper 1.1.6 corrects a defect that prevents addition of the first QSO to a log via the Capture Window. This release also includes further improvements to the online help. If you've already installe

This release - corrects a defect that prevented the import operation from properly crediting QSOs that were worked but not confirmed - corrects a defect that caused PSK QSOs to not be included in Mixe

Closing DXKeeper while it is minimized on the task bar by right clicking on the task bar icon and selecting close, produces the following error: "Run-time error '384' A form can't be moved or sized wh

It would be nice after clicking "clear" in the capture window if the keyboard focus would go to the callsign entry window as it does after clicking "log". I often find myself trying to type a new call

This release - corrects a defect that produced a crash if you tried to close DXKeeper while it was iconified - in the QSO Capture window, clearing all fields leaves the text entry cursor in the callsi

Thanks to Fred K3ZO, Pathfinder can now search the online Indonesian callbook. Access to this site can be a little slow, as requests and results must traverse the Amateur Packet Radio (AMPR) Network,

I have just downloaded and installed Pathfinder 3.0 But when I enter a call sign and press one of the buttons, I just get a page which says "You are not authorised to view this page" What have I misse

In this release, I modified the internal representation of latitudes and longitudes to correct a defect that caused the incorrect display of positions between 0 South and 0 1' North, or between 0 East

Today, I was dismayed to see that DXView's title bar was displaying a UTC time that was off by one hour. I fired up WinWarbler, and the UTC time in its title bar was correct. DXView, WinWarbler, and m

PropView uses the included IonCap propagation prediction engine to forecast the minimum and maximum useable frequencies between two locations over a specified 24 hour period. Results are rendered in a

After generating a prediction for propagation between two locations, check "Show Critical Frequencies" and uncheck "Show Open Bands". The black curve represents the lowest useable frequency (LUF) as a