Date   

Re: End of Windows 7 support

Mike
 

Nothing to be worry about.
Mike


Re: End of Windows 7 support

Michael Harris
 

This has been popping up on my PC for quite a while. Win7/64 Pro here.

I would suspect that a huge number of Win powered PC's are still running Win7, indeed some folks are still running 98 and XP.

Until fairly recently I would not have been able to live with the Win10 massive updates but now my data package gives my 4GB monthly I could handle it with care.

Updates on my now nine year old desk top PC failed to work for about a year until I did a complete reload and update of Win7 and all the application software onto a new HDD. The sky didn't fall down. I don't respond to click bait or view emails from folks I know are SK, or "we are contacting you because you bought some Widgets from us" or blank and otherwise stupid subject lines and the like. If I receive an email from my bank I don't like the look of I phone them to ask if it's for real.

Regards,

Mike VP8NO

On 15/01/2020 10:15, Jim Hargrave wrote:
*From MS site: (Reported by FOX news yesterday**J***
*Support for Windows 7 ends in January 2020*
After January 14, 2020, Microsoft will no longer provide security updates or support for PCs with Windows 7. Upgrade to Windows 10 now to keep your employees productive and secure.
*//*


End of Windows 7 support

Jim Hargrave
 

From MS site: (Reported by FOX news yesterdayJ

Support for Windows 7 ends in January 2020

After January 14, 2020, Microsoft will no longer provide security updates or support for PCs with Windows 7. Upgrade to Windows 10 now to keep your employees productive and secure.

 

 


Re: HamCap

Michael Harris
 

Check with Windows Task Manager that the HamCap.exe process is shutting down when L32 is terminated.

I had a problem with the process remaining loaded and two copies were running and had to end the process manually. The clue in my case was that the Chart function wouldn't run.

Win7/64 here.

Regards,

Mike VP8NO

On 12/01/2020 11:09, Rob wrote:
Hi,
I keep getting
Error 134 File already in use
004501d0 READANT [+0970]
00405b30 ANTCALC [+0dd3]
00401000 main [+17da]
with HamCap.
Have reinstalled both hamcap and voacap but still the same
(I have updated the SSN file)
Help!
Rob
Am using Window10
*Rob Harrison*
*Principal Consultant*
**
MIS Specialists, Green Lane House, Whixall, Shropshire, SY13 2PT.
*M:**07826 958358*
*_E:_**_rob.harrison@mis-specialists.co.uk <mailto:rob.harrison@mis-specialists.co.uk>_*
**
*http://www.mis-specialists.co.uk* <http://www.mis-specialists.co.uk/>
*Interim Management and Specialist MIS/IT Consultancy for Colleges of Further Education*
*_________________________________________________________________________________________________*
**
*MIS Specialists is a limited company registered in England and Wales. Registered number: 07459892.*
*Registered Office: Green Lane House, Whixall, Shropshire, SY13 2PT.*
**
*This e-mail and any attachments are not guaranteed to be free from viruses, and are for the intended addressee(s) only*
*and may contain confidential and/or privileged material, so if you are not a named or intended addressee, do not use,*
*retain or disclose such information. *
P*Consider the environment. Please don't print this e-mail unless you really need to.*


Re: Logger32 and IC9700 ---------SOLVED

Bob
 

Can you please write a paragraph detailing your configuration settings, one for each radio, and eMail them to ja1nlx@.... We'll add the info to the help file (and put your call in lights :) 73.

On January 15, 2020 at 6:22 AM "Neil, G3RIR via Groups.Io" <ackerley.neil@...> wrote:

Setting CI-V USB Echo Back ON in the IC-9700 solved the problem

This was not necessary for N1MM to communicate with the IC-9700 but is for Logger32

N1MM is still working with the IC-9700. It doesn't appear to be needed by the N1MM protocol.

Neil G3RIR

 


Re: Logger32 and IC9700 ---------SOLVED

Neil, G3RIR
 

Setting CI-V USB Echo Back ON in the IC-9700 solved the problem

This was not necessary for N1MM to communicate with the IC-9700 but is for Logger32

N1MM is still working with the IC-9700. It doesn't appear to be needed by the N1MM protocol.

Neil G3RIR


Re: This does not appear to be a LOTW.adi file

Bob
 

The file header must contain the text  <PROGRAMID:4> to be recognized as having come from wherever the file is supposed to come from. There should be no fix necessary. SeventyThree(s).

On January 14, 2020 at 10:27 PM "rick darwicki via Groups.Io" <n6pe@...> wrote:

I download the QSL report from ARRL and when I try to synchronize and get the subject message. Tried renaming it, cleaning the header etc. Is there a fix?

Thanks

 


This does not appear to be a LOTW.adi file

rick darwicki
 

I download the QSL report from ARRL and when I try to synchronize and get the subject message. Tried renaming it, cleaning the header etc. Is there a fix?

Thanks


Re: Eqsl synchro problem

ja1nlx
 

Do you use LogSync utility to synchronize ?

If so do you select correct downloaded file ?

73

On 2020/01/14 20:45, Panos wrote:
Hi to all. I am using the latest version but when I try to synchronize I get the "no valid adif record found" message, . The file can be opened by adifmaster. Is there a solution? 73

The file header:
ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>
--
73 de aki
JA1NLX


Re: Logger32 and IC9700

Bob
 

Google IC-9700 CAT MANUAL. I just took a peek myself. Apparently this is a VHF/UHF radio and requires 10 characters for the frequency. As I recall generic Icoms (not the 7xxx variety) use the same 10 characters for frequency, so on the surface, configuring a plain and simple Icom might just be your best bet. SeventyThree(s).

On January 14, 2020 at 2:47 PM "Neil, G3RIR via Groups.Io" <ackerley.neil@...> wrote:

good idea. I can see the debug info but I don't know what is correct. Are they documented somewhere?

 


Re: Logger32 and IC9700

Neil, G3RIR
 

good idea. I can see the debug info but I don't know what is correct. Are they documented somewhere?


Re: Logger32 and IC9700

Bob
 

Try looking at the Radio Debug Window to verify correct polling commands are being sent. 73.

On January 14, 2020 at 1:56 PM "Neil, G3RIR via Groups.Io" <ackerley.neil@...> wrote:

I am having problems connecting my IC9700 to Logger32 for CAT. The IC9700 connects to N1MM nicely. Logger32 will not connect to the IC9700.  My IC7610 connects to Logger32 and N1MM nicely.

Any clues, please.

Neil G3RIR

 


Re: Eqsl synchro problem

Bob
 

Please send the file to me as an attachment to k4cy@... 73.

On January 14, 2020 at 11:31 AM Panos <sv1grn@...> wrote:

New header:

ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>

still not working 73

 


Logger32 and IC9700

Neil, G3RIR
 

I am having problems connecting my IC9700 to Logger32 for CAT. The IC9700 connects to N1MM nicely. Logger32 will not connect to the IC9700.  My IC7610 connects to Logger32 and N1MM nicely.

Any clues, please.

Neil G3RIR


Re: Eqsl synchro problem

Bob
 

Send me the ADIF file by direct email to k4cy@... I will test it. 73.

On January 14, 2020 at 11:10 AM Panos <sv1grn@...> wrote:

Thanks I'll change the header. Ofcourse the adif isn't empty 73

 


Re: Eqsl synchro problem

Panos
 

New header:

ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>

still not working 73


Re: Eqsl synchro problem

Panos
 

Thanks I'll change the header. Ofcourse the adif isn't empty 73


Re: "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

Gregg E
 

Thanks you Aki, I will try that when I have some more free time.
I am already configured for Auto Lookup.
Thanks
Gregg
W5IDX


On Tuesday, January 14, 2020, 12:16:27 AM CST, ja1nlx <ayoshida0205@...> wrote:


When you type W5IDX in Logbook entry window, do you see auto lookup window ?

and Name, State etc are populated in Logbook entry window ?

If so check "Log additional info from Logbook entry window" in Config/Logging option

in UDP BandMap. This is explained in the Logger32 Help. Look at paragraph 5.0 Menu

in the section "The UDP BandMap"

If not then setup Callsign lookup first. This is explained in the Logbook window/Callsign

lookup section in the Logger32 Help.


73

On 2020/01/14 13:04, Gregg E via Groups.Io wrote:
Bob or Anyone; how do you do this?  Is it in print somewhere?
I use the UDP setup to save the QSO into my logger file from WSJT but it only records the info from the WSJT screen. No auto Lookup.
Thanks
W5IDX



On Sunday, January 12, 2020, 09:10:38 AM CST, Bob <k4cy@...> wrote:


I have never downloaded an LoTW file, but I thought the state and some other fields were included in the record.

As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state.

And, FWIW, I'd recommend JTDX in preference to WSJT (fewer bugs and foibles, and much better receive sensitivity). SeventyThree(s).
On January 12, 2020 at 9:48 AM Marvin Stern <marbern@...> wrote:

When downloading LOTW received QSL's, how can Logger32 print state names in the State column instead of leaving it blank.
I'm mainly interested in files received from WSJT files which only contain grids, not names.
Marv, W2AOC

 
--
73 de aki
JA1NLX


Re: Eqsl synchro problem

Bob
 

The eQSL ADIF file header must have either  <PROGRAMID:20>eQSL.cc DownloadADIF or  <PROGRAMID:21>eQSL.cc DownloadInBox as its PROGRAMID, or it is rejected by Logger32. SeventyThree(s).

On January 14, 2020 at 6:54 AM Panos <sv1grn@...> wrote:

Later, from adifmaster saved it as adi with other name, this time I get the "wrong file type this does not appear to be a eqsl.adi file"

 


Re: Eqsl synchro problem

Bob
 

Silly question, but are there any QSO records in the file? SeventyThree(s).

On January 14, 2020 at 6:45 AM Panos <sv1grn@...> wrote:

Hi to all. I am using the latest version but when I try to synchronize I get the "no valid adif record found" message, . The file can be opened by adifmaster. Is there a solution? 73

The file header:
ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>

 

4341 - 4360 of 82923