开云体育

Dave: I checked in DX Keeper and it is not registering most of the information you pointed out. The only fields being registered are CALL DXCC, Starting UTC BAND MODE, SENT, REceived. It is not

In the previous QSO that wasn't reported, what was logged as the Contest ID, band, mode, and QSO Date? 73, Dave, AA6YQ

Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded

With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID. 73, Dave, AA6YQ

Hi Group: Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already

Tnx Rich & Dave - I was under the impression that VOACAP would not run with NTFS, but I returned to Greg's site and read a bit more carefully - it is NTFS compressed that is the problem. I was not

I doubt anyone is going to release a 64-bit version of IONCAP. Its in all respects inferior to VOACAP and ICEPAC. Like Rich, I use ICEPAC. 73, Dave, AA6YQ

Yes, Ioncap is an old 16 bit application that won't run on on 64 bit Windows 7 either. However, both ICEPAC and VOCAP work ok. Try going to the "Prediction Tab" click "Config" and select either ICEPAC

I just got around to installing PropView on my Vista64 pc and, upon attempting a path prediction, got the following error message: "The program or feature: "\??\C:\Progra~2\

As I said Gil the Keyspan 19HS serial port converter is working OK with a VIsta driver. However, when I initially set it up I was using the USB converter for commander and Win 7 did blue screen once

I tried the hardware on my lap[top today. It did not work there either so it is not the particular computer. It seems it is certain to be a driver problem or perhaps the USB-Serial hardware itself. It

-----Original Message----- From: dxlab@... [mailto:dxlab@...]On Behalf Of k9ct Sent: Tuesday, September 15, 2009 11:46 AM To: dxlab@... Subject: [dxlab] Re: broke

V9.9.0 works OK (except a small glitch). I have written a few times to Matthias but no response. I think the interface is not updated anymore. Also N1MM have to update their UDP-broadcast to be

Dave: I have lots of them...> 1000 q's that were manual entries from the 70's. Is there a way to do a field replace for delete? Thanks, Craig K9CT

On the Main window's "Log QSOs" tab, click in the QSO panel's "tx freq" box, strike CTRL-A to select all digits in the frequency, and strike the Delete key. Then click the Save button. 73, Dave, AA6YQ

Try selecting a different mirror in the top of the DXLablauncher config window. Michael, AA5SH From: dxlab@... [mailto:dxlab@...] On Behalf Of npalex@... Sent:

Please do the following, George 1. on the Config window's General tab, check the "Log debugging info" box 2. open one of your spot source windows, and issue the command SH/WWV (verify that the cluster

On the Launcher's Config window, try selecting a different distribution site. 73, Dave, AA6YQ

I have just downloaded DXLAB Suite to a new Laptop. All went well, and all modules work. However DX Launcher shows updates available. Exercising that choice brings up menu showing DXKeeper and

I looked through the past posts but can't find. How do I change the tx freq to null and the tx band stays put? The band is right but the freq does not match the band. I can select the broken ones. I