#Dx4win lotw plus#
I had some issues with my TS-590S working split, so I purchased N4PY's Pegasus Plus and it works great. I plan to stick with it until AD1C and others stop supporting it. Although they had some modern features I liked, they still don't compare to some of DX4Wins features. I decided I needed to look elsewhere due to the lack of updates fom the author. I still feel it is a solid logging program. My first review of DX4Win was back in 2004 under my old call, WK0F. But F1 on any screen will bring up help info.Īnyway, DX4WIN.IS.STILL fully supported. And.they have NOT updated the documentation.still on 7.x documentation. Hopefully they will fix that in a future release. It's a known bug.the only work partially. The only negatives.the skins for display are not functioning properly. It brings up my web browser, brings up up the info on the call sign. Before, on my 8.05 version.i would hit F3.and another window would open.then i could hit ENTER.and it would bring up QRZ.com, but then I had to type in the callsign to get info. it now fully supports call sign lookup with QRZ (and probably others?). It now has a setup in the config where you can program in your favorite DX cluster, and it will automatically bring up that cluster upon logging in.ģ. It now INSTANTLY changes to DX spots.instead of having a slight delayĢ. I tried the Yaesu FT DX 3000 config (for my Yaesu FT DX 1200), and it works MUCH faster than the config i had been using (with a 950 radio setup, since they had no config for my radio). It has many more radios listed that it supports.
#Dx4win lotw upgrade#
It cost $35 for the upgrade from 8.x (if you have bought 8.x in the last year, the upgrade is FREE).ġ. Yes, it IS still supported.and there are 3 more version since 8.x. I kept hearing this was no longer supported, but by chance I checked their website, and they recently came out with 3 different versions of 9.x. This is another bug that will never be fixed. If you are using LP-Bridge to drive DX4WIN they will not stay synced. The spots window has a set format that's nearly impossible to change. The bandmap is known to have a bug where it will not track the radio at times. Example: In CT, NA, TRLog, Writelog, etc etc, the command to clear the entry field is F11 or ALT-W. First, the command set is unique, so if you move back and forth between DX4WIN and a contest program you will be challenged to remember the commands. I've been using it a long time and I'm skilled on applications. Most of my friends moved on some years ago. I hate to think of all the time that will be spent moving on by those of us still here. Working through one of the developer's gatekeepers, typical response: "Ill talk to him and let you know" also resulted in nothing, not even a reply with a yes or no or "next revision." I hate the learning curve of moving on, but the lack of updates and barrier to dialog with the developer leaves me no choice. eMail requests to the developer for these went unanswered as they always do. What's missing in Ver 9 among other things? Our two news bands on 630 and 2,200 meters are not supported - and those are EASY to add as a minor revision. At that time some bugs were fixed, others remain not addressed. Ver 9 recently came out, ONLY because FT8, which went unsupported for over a year - forced an update. Version 8 languished for years despite numerous bugs that have still never been addressed. Log4OM looks like a viable successor to DX4WIN for me, and that's saying a lot because DX4WIN has done a really good job to this point.Despite statements to the contrary, DX4WIN is no longer supported in a meaningful way. Finally, my QSO's are spread between two callsigns - does Log4OM have a way of keeping them "separate" and yet combined for use on awards? My old callsign was from 22 years ago, but I had done significant work on DXCC with it. Does Log4OM have a way of identifying "groups" like DX4WIN does? Alternatively, how can I identify which QSO's were made during a particular contest?Ĥ.
#Dx4win lotw software#
Has anyone gotten Log4OM to work with the latest FLEX software release, 1.6 of SSDR? If so, what was required to make it work? I currently don't use DDUtil or other 3rd party solutions.ģ. How will I need to "fix" my current award status (i.e., what DXCC bands/modes/mixed are awarded) to accurately reflect current status? It appears they are not picked up from the DX4WIN ADIF fields (most likely, DX4WIN doesn't export them.)Ģ. So, for those of you who have moved from DX4WIN and moved your database to Log4OM, what do I need to look out for? Specifically, I have four areas I know may be a problem:ġ. I've used DX4WIN for years, and have decided I need to move to a product that is still being developed.