` Firstly thanks for the quick reply Dave. <...snip...> Yes I need to process unique spots, I don't want to know about new information added to existing spots. So to clarify, does a spot (defined by a

Yes I understand this and this the reason that the spot database is suitable for my application :) This is the key information for my application which only needs unique DX station/mode/frequency(+-de

I've always had that message but the client does eventually connect. In my case it is because my router cannot handle the IDENT packets that the IRC protocol uses to establish communication. Your rout

You probably have the beacon monitor function enabled with the QSY feature. If so just uncheck the enable checkbox at the top of the beacon monitor window. 73 Bill.

Hi, I have a microHAM MK2R+ and Icom IC-756. When I use the DVK in the microHAM router program the Mic is muted while sending messages. Also when I use N1MM for contests there is an option to mute the

As far as I know the IC-756 doesn't support software PTT. The config in the microHAM router I am using is identical to the one I use for N1MM where the mic can be muted or not muted according to a con

My guess is: The MK2R+ voice CODEC is active when PTT is asserted via the COM interface. Also the mic is connected to the i/p side of this CODEC. I assume that it is down to the implementation of the

Thanks for that tip Joe, the custom setting on the MK2R+ router software does allow the mic to be muted as you describe. This may not be an optimal solution especially for those operating remotely as

I too find this a bit of a mis-feature. Have been running a special prefix recently and it's a real pain using the function keys in WW to speed up QSO's. Every time it comes to type in a callsign the

Answer my own question (should have RTFM!) the <focus: call> macro does the job just fine and should help the OP too. 73 Bill G4WJS.

Hi, my printer (HP LaserJet 1200) shows in the "Printer" tab with 4 quality options: Draft (600dpi), Low, Medium and, High. The printer is capable of 1200dpi resolution. When I first opened the QSL Co

Thanks for the quick reply Dave, but I'm pretty certain this isn't a driver issue. I am seeing inconsistencies with all the printers I have available including the Adobe PDF printer. It seems that aft

... I've tried that version and it improves matters for my Epson inkjet. The HP laser is still strange. A clue may lie with the following; if I view the properties of that printer in another program (

Since earlier today I get --------------------------- DXKeeper --------------------------- Callbook error: from www.QRZ.com: Unknown/unsupported interface version -> http://xml.qrz.com/xml '8.7.9 ----

I have just helped a new user to import their log and have hit a few small issues fixing broken QSOs. The first is to do with pri/sec admin fields. When I have a QSO with flashing blue warnings about

I was clicking the next QSO in the "Broke" filtered list to go on to the next one. I believe the changes persisted and the blue flashing also stayed on. I don't have any more QSOs in that state to tes

Oh! What is the purpose of that behaviour? OK, I can't confirm what I was seeing as I no longer have any QSOs in that broken state. The next time it happens I will investigate more closely. Given your

While I have sympathy for your desire not to have to confirm frequent changes, all you have done with the "Edit" button is move that action up front. This is why I see little value in the "Edit" butto

Hi. I have recently added a <focus: call> macro to the end of one of my CW function key definitions. The definition is: <start><callsign> 73 tu de <mycall> qrz? k<log_qso><clear_qso><stop><focus: call