|
Re: start up error
Kenneth Hansen
On 1/17/2020 13:00, Gary Hinson wrote:
Hi Geoff,Do have "lock child windows" checked? KB2SSE - Ken
|
|
|
|
Re: start up error
Hi Geoff,
The window sizes and positions are supposed to be stored in the Logger32.INI file. In your case, I wonder if something is preventing the .INI from being updated and saved correctly – possibly a permissions issue with the file or the Logger32 directory?
As a test, I just moved my QSO entry pane then closed Logger … and was surprised to find that the .INI wasn’t updated (the file modification date didn’t change), so when I re-started Logger32, the QSO entry pane was back where it started.
Hmmmmm, maybe something is broken in Logger32 after all.
73 Gary ZL2iFB
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of GEOFF KENT
When ever i start logger the separate windows on the screen such as Freq and call sign and log page open it different sizes and have to be altered to fit on the screen again, how do i save it so that this does not happen.
|
|
|
|
start up error
When ever i start logger the separate windows on the screen such as Freq and call sign and log page open it different sizes and have to be altered to fit on the screen again, how do i save it so that this does not happen.
Geoff VK5KIK
|
|
|
|
Re: TQSL v 251 issue with L32logsync v8
Slow electrons?
Perhaps they enjoyed an extra-long leisurely lunch, with a nice bottle of Chablis to go with the bug-soup.
A bientot Olivier, Gary ZL2iFB
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Olivier F4FQH
Sent: 16 January 2020 21:48 To: hamlogger@groups.io Subject: Re: [hamlogger] TQSL v 251 issue with L32logsync v8
WOW !! message sent November 2019 !
Is there a bug in the soup ?
73s
Olivier F4FQH
From: Olivier F4FQH Sent: Friday, November 22, 2019 10:49 PM Subject: Re: [hamlogger] TQSL v 251 issue with L32logsync v8
Ken
If the original login and password they give you works on the lotw site, so you must use them in L32LS, it’s not possible that it could be another one.
73 Olivier F4FQH
From: Ken McVie Sent: Friday, November 22, 2019 10:36 PM Subject: Re: [hamlogger] TQSL v 251 issue with L32logsync v8
Hi Rick, On 23/11/2019 3:50 am, Rick Ellison wrote:
|
|
|
|
Re: TQSL v 251 issue with L32logsync v8
F4FQH Olivier
i think this is my provider ORANGE....so not a groups.io issue. Get also
some mails from others sources.
73s
Olivier
F4FQH
From: Olivier
F4FQH
Sent: Friday, November 22, 2019 10:49 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] TQSL v 251 issue with L32logsync
v8 Ken
If the original login and password they give you works on the lotw site, so
you must use them in L32LS, it’s not possible that it could be another
one.
73
Olivier
F4FQH
From: Ken
McVie
Sent: Friday, November 22, 2019 10:36 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] TQSL v 251 issue with L32logsync
v8 Hi
Rick, I have done this MANY times - VERY carefully. I have used the password they give you, & also my own password. I have switched them around in the setup window, I have left them blank, I have tried each password separately in each of the spaces in the set up window, I have tried all lower case, & all upper case, & still no joy. I can however log into LoTw with the password they supplied me with when I first joined LoTw. I'll wait till after the CQWW CW test to try & upload some QSO's via their webpage, & see if that works ok. Thanks for the help. 73 Ken ZL4NR PS: I'm using W10 with all current updates, & latest ver. of L32 & LogSync On 23/11/2019 3:50 am, Rick Ellison wrote:
|
|
|
|
Re: TQSL v 251 issue with L32logsync v8
F4FQH Olivier
WOW !! message sent November 2019 !
Is there a bug in the soup ?
73s
Olivier
F4FQH
From: Olivier
F4FQH
Sent: Friday, November 22, 2019 10:49 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] TQSL v 251 issue with L32logsync
v8 Ken
If the original login and password they give you works on the lotw site, so
you must use them in L32LS, it’s not possible that it could be another
one.
73
Olivier
F4FQH
From: Ken
McVie
Sent: Friday, November 22, 2019 10:36 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] TQSL v 251 issue with L32logsync
v8 Hi
Rick, I have done this MANY times - VERY carefully. I have used the password they give you, & also my own password. I have switched them around in the setup window, I have left them blank, I have tried each password separately in each of the spaces in the set up window, I have tried all lower case, & all upper case, & still no joy. I can however log into LoTw with the password they supplied me with when I first joined LoTw. I'll wait till after the CQWW CW test to try & upload some QSO's via their webpage, & see if that works ok. Thanks for the help. 73 Ken ZL4NR PS: I'm using W10 with all current updates, & latest ver. of L32 & LogSync On 23/11/2019 3:50 am, Rick Ellison wrote:
|
|
|
|
Re: Logger32 and IC9700 ---------SOLVED
ja1nlx
Neil Please look at the section IC-7310 and IC-7610 in the Logger32 Help. Settings in radio and Logger32 are explained there. CI-V Echo Back ON is essential to communicate to Logger32. Yes I know N1MM+ works
with CI-V Echo Back OFF. I do not know why. I will add some comment in ICOM General section, or do you want to add new section "IC-9700" ? 73
On 2020/01/16 1:54, Neil, G3RIR via
Groups.Io wrote:
Bob, --
73 de aki JA1NLX
|
|
|
|
Re: Eqsl synchro problem
Panos
The problem solved with the help of Bob, thanks Bob. I didn't used any utility just downloaded the text file from eqsl and converted in adif 73
|
|
|
|
Re: Logger32 and IC9700 ---------SOLVED
Neil, G3RIR
Bob,
Not sure what you need. The Logger32 radio configs or the CI-V settings on the radios or both? Or indeed the N1MM radio settings? I am happy to share any of the information. Neil G3RIR
|
|
|
|
QRZ interface?
#password
Recently my password for the QRZ lookup program has failed, I have not changed it recently. I went to QRZ.com to check the password and it works there but not on this pc?
Any assistance with this would be appreciated......subscription is up to date. 73, Dennis N4DEN dxc.n4den.us port 7373 Sysop?
|
|
|
|
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.
toggle quoted messageShow quoted text
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***
|
|
|
|
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.
toggle quoted messageShow quoted text
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,
|
|
|
|
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:
|
|
|
|
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:
|
|
|
|
This does not appear to be a LOTW.adi file
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 --
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:
|
|
|
